We're hiring a Backend Engineer to take ownership of a portfolio of backend projects and supporting infrastructure currently being transitioned into our team. You'll work closely with our incoming Cloud Architect and project lead to absorb the existing codebases, stabilize them under our ownership, and identify opportunities to modernize where it makes sense.
Two outcomes matter most in this role: keeping the lights on as you take ownership of these projects with zero unplanned downtime, and producing excellent documentation artifacts — co-authored with our team and the Cloud Architect — that capture how these systems actually work. Modernization is a welcome bonus, not the headline goal.
What You'll Do
- Take ownership of existing backend projects (currently vanilla JavaScript and Nuxt) and ensure continuity of service through and after the handover.
- Co-author thorough, high-quality documentation of the codebases, APIs, data flows, deployment processes, and operational runbooks. Our team will partner with you on this, and the final artifacts should be ones we're all proud of.
- Partner with the Cloud Architect on documentation and handover work, ensuring application-layer and infrastructure-layer artifacts line up cleanly.
- Identify low-effort, high-value modernization opportunities — for example, migrating projects to TypeScript — and propose a pragmatic path forward where it makes sense.
- Drive working sessions with the outgoing agency to capture institutional knowledge, surface undocumented behaviors, and validate handover artifacts.
- Participate in weekly check-ins with the project lead, Cloud Architect, and other members of the transition and documentation team to align on progress, blockers, and next steps.
- Track work, decisions, and handover items in Jira.
Required Skills
- Strong professional experience as a backend engineer, with demonstrated ownership of production systems.
- Solid command of JavaScript (Node.js) and familiarity with Nuxt or comparable frameworks.
- TypeScript experience and a clear point of view on when and how to migrate JS codebases to TS.
- Strong technical writing skills — able to document unfamiliar codebases clearly enough that the next engineer can be productive on day one.
- Excellent communication and stakeholder management skills, particularly when working across organizational boundaries.
- Comfort working in Jira for tracking tasks, tickets, and handover progress.
Nice to Have
- Experience inheriting and stabilizing codebases written by another team or agency.
- Familiarity with AWS and working alongside infrastructure/cloud engineers.
- Hands-on Terraform experience or comfort reading IaC to understand how applications are deployed.
- Testing and CI/CD experience, especially in environments without strong existing test coverage.
- Based in the EST timezone for overlap with our team and client.
Requirements
- Must pass a background check.
- Work will be performed on a pre-provisioned remote machine with access to the relevant infrastructure and tooling.