Software Engineer; Full-Stack, Backend-leaning

Join to apply for the Staff Software Engineer (Full-Stack, Backend-leaning) role at Jerry
.

At most companies, engineers wait for approvals, dependencies, and solutions to problems. , we don’t wait. If you have an idea, you can explain it, build it, and ship it—sometimes in days, not months. One engineer said, ’At other companies I made very little difference. Here, if I have a good idea, I can go do it.’ That sense of ownership is built into how we work.

We move fast, and you’ll see your fingerprints on the product right away. Engineers love touching every layer of the stack, collaborating across teams, and seeing their work reflected in real customer behavior—sometimes the same week they ship. Another said, ’Everything you do reflects immediately for the users,’ and ’And things move fast.’ We don’t do bureaucracy, politics, or oversight;

everyone writes code and sweats the details. Leaders lead by example, have high standards, and do not settle for just OK. It’s challenging work, but meaningful. You’ll juggle new and old systems, context-switch often, and learn constantly. You’ll also get more trust and autonomy than almost anywhere else. Culture is curious, collaborative, and supportive. One teammate recounted, ’I once caused a bug that wasted $20K in AWS costs, but no one blamed me.

They only cared about how to prevent it next time.’ We’re a remote‑first, global team with engineers across North America and Asia. We collaborate asynchronously, meet regularly to share context, and connect in person at global off‑sites.

Your car and your home are the two most expensive things you’ll ever own—and the hardest to manage. , we’re building the first super app to help everyday Americans take control of both. From insurance to repairs to safety, we’re reimagining what it means to own and maintain your car and home. This is a $5 trillion+ problem, and we’re the only company tackling it end‑to‑end.

Our revenue has grown 60x in the last 5 years, we’re profitable, and our goal is to scale from 5M → 50M users next.

• Build automation systems that handle complex insurance servicing tasks end‑to‑end (policy endorsements, cancellations, document uploads, reinstatements) or reduce policy cancellations, improve renewals, and ensure users always have the best coverage.
• Fast sprint cycles: ship new automations in 1–2 weeks on average.
• Compose back‑end business logic that drives automation while respecting complex insurance carrier rules.
• Design back‑end pipelines that sync customer policy data, deliver timely alerts, and power seamless re‑shopping experiences.
• Optimize and scale our internal tools (think: in‑house Docu Sign for servicing) to reduce agent intervention to nearly zero.
• Collaborate closely with product, data, and engineering ops to anticipate churn and improve customer retention.
• Work asynchronously across time zones, with minimal meetings but strong collaboration through Asana and Slack.
• Continuously improve our back‑end systems, APIs, and micro‑service architecture.

• Front‑end & back‑end:
  Type Script, Nest.js, Next.js, React, React Native, Expo
• API:
  GraphQL
• Data:
  Postgres, Dynamo
  
  DB, Clickhouse, Redis
• Infrastructure: AWS, microservices, containerised services on ECS/EKS, asynchronous processing on Lambda
• We’re refactoring major parts of our code base—simplifying old systems, rebuilding core flows, and setting up the next three years of our platform’s growth. You’ll help build the foundation for that next phase.

• Experience:
  
  At least 5 years full‑stack engineering experience building production‑grade software, ideally prior experience building large‑scale distributed systems for a fast‑growing consumer‑facing software.
• Technical strength:
  Strong foundations in data structures, algorithms, and systems design matter more than prior experience with our tech stack.
• Problem solver:
  You enjoy tackling ambiguous problems, breaking them down into actionable code, and iterating quickly.
• Ownership:
  You take responsibility for end‑to‑end outcomes and continuously improve the systems you build.
• Collaboration:
  
  Comfortable working asynchronously…