Small team. Unusual amount of surface area.
Closr is scheduling, a CRM, an outbound suite, and a realtime voice agent in one product. Anyone who joins ends up owning a whole slice of that rather than a ticket queue.
Nothing posted right now
We hire in small, deliberate bursts rather than keeping a permanent job board. When there is nothing listed here, the introduction still matters — most of our hires started as a message sent before a role existed.
Send us something real
Not a cover letter. A thing you built, a pull request you’re proud of, a teardown of a product you think is wrong, or a note about which part of Closr you’d fix first. Use the contact form and pick “Something else” as the topic.
Three things
You finish things
The last 20% — the empty state, the error path, the migration that has to run before deploy — is the part that decides whether software is real. We care much more about that than about velocity on the first 80%.
You've been the user
The best decisions in this product came from people who have actually run a pipeline, chased a no-show, or answered the same inbound question forty times. Domain scars beat framework opinions.
You write it down
We work across time zones and ship on a short cycle. Clear written thinking is not a nice-to-have here; it is the coordination mechanism.
What you'd be signing up for
- A modern TypeScript stack: Next.js, React, Tailwind, Postgres
- Realtime AI: streaming speech-to-speech, retrieval, and evaluation
- Ownership of a whole module rather than a slice of one
- Short review cycles and direct access to the people using the product
- Written proposals before large changes
- Remote-friendly, with a Malaysian home base
- Deploys that go out when they're ready, not on a train schedule
- No performance theatre
Think you'd fit?
Tell us what you'd build and why. We read everything that isn't a template.
Replies within one business day.