Software Engineer, Systems Engineer

We're building the infrastructure that will replace call centers at the world's largest financial institutions. Voice AI that handles thousands of live calls every day for Fortune 500 banks and insurers, end to end.

Call volume is 3x-ing monthly. We're hitting problems most startups never see: real-time voice AI at scale, legacy banking infrastructure, enterprise telephony, regulatory constraints.

You'll build and own core product features. Backend systems, APIs, voice infrastructure, wherever the product needs you. Code ships daily and goes live for Fortune 500 clients.

You'll work on things most engineers never touch: telephony systems, real-time voice processing, integrations with legacy financial infrastructure. The problems are hard. That's the point.

95%+ of your time will be coding and building.

We're looking for engineers who can own one of these areas: the orchestration layer that coordinates our voice AI systems, infrastructure scaling and low-level performance, security as a generalist building for Fortune 500 financial institutions, or product engineering close to users finding high-leverage wins.

Four engineers. Everyone ships to production.

We do dailies. We groom tickets. But we keep process light and in service of the work, not the other way around. We'd rather spend time building than talking about building.

We care about doing great work. Not just shipping, but shipping something you're proud of. Clean abstractions. Systems that don't page you e you wouldn't be embarrassed to open-source. We build things that last because we're the ones maintaining them.

Ownership here is real. You won't be handed tasks from a backlog. You'll see what needs to happen and do it. That's how a small team ships to Fortune 500 customers.

We hire people whose judgment we trust, then get out of their way. No passengers.

You've been through the early stages of a startup before. You know what it feels like when things are working: real customers, real revenue, a product people actually need. You also know the chaos, the pace, the things that break at the worst possible time. You've seen both sides and you want to do it again with a team that's already found traction.

You care about the craft. You want to build something good, not just something that works.

You’ll be engineer #5. Small team, high leverage. Your work ships immediately.

Real traction. Post-revenue, Fortune 500 customers, 3x monthly growth. This isn't a bet on an idea. The product works and customers are paying for it.

You’ll learn how enterprise deals work from an engineering seat. You’ll see the direct line between your code and revenue.

Early enough to shape the product, the team, and the culture.