Senior Backend Engineer, FutureFit

• 5 to 8+ years of senior-level, hands-on experience in backend, platform, or integration engineering, with a focus on building reliable systems for complex external integrations
• Strong experience with TypeScript and Node.js
• Proven experience building and maintaining complex data integrations at enterprise or government scale (deep data integration work, not only SSO, API configuration, or cloud deployments)
• Strong understanding of asynchronous workloads and processing
• Experience developing reliable, production-grade backend systems
• Strong debugging skills using logs, metrics, and tracing
• Proficiency with at least one SQL or NoSQL database in production
• Comfort working effectively in a fully remote environment
• Experience with financial, banking, or similarly complex data integrations
• Experience with legacy enterprise or government systems

Desirable

• We’re seeking a Senior Backend Engineer (Integrations & Platform) to build the backbone our platform runs on. You’ll design scalable backend systems that power complex data integrations with government and enterprise partners, remove manual operational work, and help the team move faster with less friction
• This is a build role and an operate role: when a sync fails or a record looks wrong, you can trace it back to the cause and fix it
• Our integration footprint has grown quickly, and the most demanding piece is a bidirectional data sync with an external partner that requires sophisticated error handling, async workflows, and operational automation. You’ll start there, then turn what you build into the patterns and infrastructure we use for integration reliability across the platform
• This is hands-on, high-impact work where you’ll see results quickly: fewer production issues, faster support resolution, and systems that scale with confidence
• Complex data integrations: Design, build, and maintain deep, bidirectional data integrations with government and enterprise partners, including partners with limited documentation
• Asynchronous workflows: Build reliable async processing using queues, retries, idempotency, and eventual consistency patterns, handling duplicates, missing dependencies, and validation failures defensively
• Operational automation: Eliminate categories of manual support work through backend services, Lambda functions, and internal tools that let non-technical teammates diagnose and resolve issues themselves
• Observability: Implement structured logging, metrics, tracing, and alerting so issues surface before support tickets do
• Production reliability: Stay close enough to running systems to debug them, including code you did not write
• Reusable patterns: Establish integration standards the rest of the team can build on
• Partner collaboration: Work with external vendors on API changes and coordinated deployments
• First 30 Days: Learn and Integrate
• Build relationships with the engineering, customer success, and support teams who interact with our integration systems daily
• Deep dive into our most complex integration: the bidirectional sync architecture between our platform and external partners (APIs, data models, async workflows, error patterns)
• Get hands-on with our debugging tools: MongoDB queries for async job tracking, CloudWatch Logs Insights for distributed tracing, SQL queries for data validation
• Ship your first small fixes or improvements: resolve straightforward integration bugs or improve observability in one workflow
• Days 31 to 60: Own and Execute
• Take ownership of your first major automation initiative: eliminate a category of manual support work
• Build and deploy backend services and Lambda functions that reduce manual intervention in the integration pipeline
• Implement comprehensive observability (structured logging, metrics, and alerting) so issues surface before support tickets
• Work with the support team to validate that your automation eliminates manual work, and identify the next highest-impact opportunity
• Document runbooks and create internal tools that empower non-technical team members to diagnose and resolve common issues independently
• Collaborate with external partners on any API changes or coordinated deployments your automation needs
• Begin identifying patterns and infrastructure that can be reused across other integrations or platform systems
• Days 61 to 90: Lead and Amplify
• Measure and communicate the impact of your automation: reduction in support tickets, decrease in manual intervention time, improvement in data consistency and error rates
• Participate in architectural discussions and planning for other platform initiatives, bringing your expertise in reliability patterns, async workflows, and operational excellence
• Mentor other engineers on the patterns and infrastructure you’ve built, establishing yourself as the go-to person for integration reliability
• Present a technical deep-dive to the broader engineering team on what you’ve learned and built

• Online Application
• Initial Screen with Talent Acquisition
• Interview with Hiring Manager
• Coding Challenge
• Design Challenge
• 2nd Interview with Head of GTM
• 3rd Interview with CEO
• Final Decision
• Generally, this entire process takes around 6 weeks, although the timing can vary due to specific candidate circumstances