EngineeringSoftware Engineer, Backend

Build the server that every assistant signs in to: OAuth, workspaces kept apart in Postgres, and the queue that keeps Cloudflare's copy of every app in step.

All open roles
Function
Engineering
Region
India
Type
Full-time
Experience
2+ years
Apply for this role

About the role

Behind every app on someone's phone is a server that never sees the app's data but has to get everything else right: who signed in, which assistant may change which apps, which version is current, and what each app's address answers.

You'll work across OAuth 2.1 with dynamic client registration, Postgres row-level security that keeps one workspace out of another's apps, an append-only history of every version, and the sync that writes each change to Cloudflare and retries when it can't.

What you'd do

  • Build features across the API, the database and the background queue, with their tests
  • Keep workspaces apart: row-level security, and the tests that fail if a query slips past it
  • Own the OAuth flows an assistant goes through, from registration to a revoked grant
  • Make retries and background jobs safe to run twice
  • Keep the specs and their citations in step with the code you change

What we need

  • Two or more years writing backend code that ran in production
  • Comfortable with SQL and with reading what your ORM sends
  • TypeScript or another typed language
  • You've written tests that caught a bug before a person did

Nice to have, not required

  • OAuth or OpenID Connect from the server side
  • Postgres row-level security
  • Job queues, retries and idempotency

How we work

  • Small team, thin slices, shipped weekly. Nothing sits on a branch for a month.
  • Reviews are real. Every feature ships with its tests, and a bug found in review is cheaper than one found by someone using it.
  • Private by default. A person's app data stays on their phone, and nothing we build may need to read it.
  • We only claim what ships. That applies to the product, the roadmap and the offer letter.

How hiring works

  1. 1A 30-minute call about something you've built and what was hard about it.
  2. 2A working session on a real problem from this codebase. You can drive, or we can pair.
  3. 3A conversation about how you make decisions when the evidence is thin.
  4. 4References, then an offer. We aim to answer within a week at every stage.

Apply: Software Engineer, Backend