AI-Native Developer

We represent an early-stage AI company building at the frontier of how humans and AI work together. The product handles real-time voice conversations that feel indistinguishable from human. Deploys AI teammates that show up to work alongside human employees - with their own roles, voices, and performance metrics. Operates at the bleeding edge of what’s possible with conversational AI.

Most of what we’re building wasn’t technically possible 12 months ago. The team is small. The pace is fast. The impact per person is enormous.

We’re looking for an AI-native developer who wants to build at the frontier - not maintain legacy code, not ship the same feature 20 different ways, not work at a company where AI is a side project. The actual frontier. The kind of work where you’re using AI to build AI, where the tools you use are the same tools the company is racing to build, and where every week feels like the limits of what’s possible just moved again.

What you’d be building

You’d be working on things most engineers in the world don’t get to touch. Real-time voice AI that interrupts, reacts, and pushes back like a human. AI teammates that work alongside humans as actual teammates - coachable, measurable, with names and personalities and their own metrics. Live coaching systems that listen to real conversations and surface intelligence in the moment. Scoring engines that understand what makes a great conversation. Custom AI models tuned for specific domains.

You’d touch every layer of the stack. One day you might be solving a real-time latency problem. The next day you’re building a new feature in our web app. The day after that you’re designing a database schema. The day after that you’re working with an AI model that launched last week.

Do you have experience in Web applications?, The right candidate is obsessed with using AI to build software. You treat tools like Cursor and Claude Code the way other developers treat their IDE - as a multiplier that makes you 5x faster than developers who don’t use them well. You read AI release notes. You experiment with new models the day they ship. You’ve built things in the last 12 months you couldn’t have built two years ago, because you understand how AI changes what’s possible.

You don’t need a CS degree. You don’t need years of professional experience. You don’t need to have worked in voice AI or any specific domain. What you need is the right wiring - curiosity that doesn’t quit, the ability to learn anything in days instead of months, and the kind of taste that lets you take a vague problem and ship the right solution.

You have strong opinions about software. You defend them.

You don’t wait for detailed specs. You define the problem, propose the solution, and ship.

You’re drawn to hard problems. You care about building things real people use, and you want to work somewhere that lets you do that without ten layers of approval.