Senior Software Engineer

What we're looking for

• 5+ years building production web applications, with real ownership of systems on both frontend and backend.
• Strong TypeScript, Next.js, Prisma and Postgres. You understand the server/client boundary, caching, and how schema and query design affect the product.
• You work with AI agents as a lead, not a typist. You run several agents on real work, know where they fail, and catch what they get wrong before it ships.
• You've improved an agent harness at your current job: better context, tools, rules, review loops or evals that measurably changed agent output. Tell us what you changed and what it fixed.
• You're curious about how your role is changing with AI, and you have opinions about it.
• You're comfortable with non-technical stakeholders. You can ask the right questions, push back on the wrong solution and explain trade-offs in plain language.
• Good technical taste: you prefer simple, boring solutions and delete code as readily as you write it.
• Professional English for daily written and spoken work.

What you'll do

• Work directly with PMs and the company's departments to understand their problems, then turn them into scoped, shippable solutions.
• Build features across the stack: Next.js (App Router, Server Components, Server Actions), Prisma and Postgres.
• Orchestrate several AI coding agents in parallel. Break work down, write the specs and context they need, review their output critically and own the result.
• Improve our agent harness: the prompts, tools, context, guardrails and evals that make agents reliable on our codebase.
• Design the contracts between frontend and backend, and keep them stable as the product evolves.
• Review code, human or AI-written, with a focus on authorization, data integrity, payments and privacy.
• Help shape how our engineering team works as AI changes what an engineer's day looks like.

Nice to have

• Infrastructure experience isn't required, but it helps.
• Google Cloud (Cloud Run, Cloud SQL, IAM, Secret Manager) or comparable AWS experience.
• Experience in regulated or privacy-sensitive domains: health, legal, insurance or government benefits.

Benefits and how we communicate

15 PTO days + your country holidays + Sick days

Good communication is non-negotiable for us. We love communication, and we dislike meetings that could have been a Slack message.

• Async first. Most of our work happens in writing. When async isn't enough, we jump on a quick huddle instead of letting a thread drag on.
• Share progress often. Post updates, blockers and decisions without being asked. If we have to ask how things are going, that's a bad sign.
• Write clearly. Your messages should give the reader enough context to act without a follow-up question.