Remote Senior Software Engineer

About the role

This is the senior seat above our junior and mid-level application roles. You don't need tickets pre-scoped. You take fuzzy, high-stakes problems — "this has to work at launch," "this part of the system is going to hurt us" — and you design, ship, and leave the codebase better than you found it. We have a working product and a real team.

Responsibilities

• Own the hard problems — ambiguous features, gnarly bugs, performance, and the systems that would otherwise slow launch
• Shape architecture — where things live, what we take on, and what we refuse to overbuild
• Ship production code — you're still an engineer first; design without delivery isn't the job
• Raise the bar — code review, testing, and examples that make mid-level and junior developers better
• Unblock the team — the stuck PR, the unclear requirement, the "we've been arguing about this for a week"
• Think in launch terms — reliability, speed, and judgment about what has to be right vs. what can wait

Requirements

• 6–10+ years building and shipping production software (web, backend, or full stack) that real users depended on
• Strong across the stack enough to own a problem end to end — frontend, backend, data, and the seams between them
• Track record of technical judgment: you've designed systems, killed bad ideas, and lived with the consequences
• You make other engineers better — through review, pairing, and clear writing, not just by being the hero
• Strong fundamentals: Git, APIs, data modeling, testing, and production operations enough to debug what's live
• Strong async communicator — you can write the design, the PR, and the "here's why" so the team can move without you in the room

Qualifications

• Must-have: Must have 6–10+ years building and shipping production software (web, backend, or full stack) that real users depended on
• Nice-to-have: Startup or small-team experience where you were one of a few senior engineers
• Nice-to-have: Experience with our kinds of problems: consumer web apps, auth, payments, search, or high-change codebases
• Nice-to-have: Comfortable in fast-moving, ambiguous environments