Senior Software Engineer - Onboarding Automation

Nearly all of our code is written in TypeScript. We use React on the frontend, Node/Express on the backend (running inside Docker), GraphQL/Apollo on both sides, and Postgres as our database. We use AWS (ECS, RDS, ElastiCache, Kafka, ElasticSearch, and more) and manage all of our infrastructure with Terraform.

We believe that high engineering velocity drives high product velocity (and, in turn, our success as a company). Keeping this in mind, we've invested heavily in creating a great developer experience that enables engineers to ship fast. Some highlights of our stack:

End-to-End Type Safety - We generate TypeScript types from our Postgres and GraphQL schemas so that when we change our database schema we see type errors in any incompatible frontend React components.

Full-Stack Code Sharing - Our build tooling supports seamless sharing of TypeScript files between the client, server, and other packages in our mono-repo so that we never have to define functions or configuration values twice.

Reproducible Infrastructure - We've used Terraform to manage 100% of our infrastructure since day 1 and have configured our CI pipeline to automatically deploy temporary staging environments for every pull request.

First Class Testing Utilities - We have a comprehensive library of utilities that mock production-like data and feed automated end-to-end, integration, and performance tests. Our wide-ranging test suite allows us to move fast while maintaining nearly perfect uptime.

The tooling you build will sit on top of all of this — and where it doesn't fit, you'll change the foundation rather than work around it.

We'll be direct about the bar. We're looking for evidence of all three:

🏭 You've productized an implementation process before. You've watched a team do the same painful setup for the fifth customer and replaced it with tooling — and you know the difference between a config system that scales and one that becomes a second product nobody maintains.

🧾 Configuration-as-code instincts. Versioning, diffing, validating, and promoting customer configuration through environments. Bonus if you've dealt with the schema-migration problem that shows up when config outlives the code that reads it.

🚚 Data migration under pressure. Moving real production records off a legacy system with validation, reconciliation, and a rollback plan. Mortgage pipelines are live money; a bad migration is not a Jira ticket.

(It's okay not to have all of these things - these are just some skills we are excited about!)

🏢 Multi-tenant experience. Per-tenant isolation, per-tenant rollout, and the operational discipline of running one codebase across customers who each believe their setup is the only one.

🚈 SRE-oriented mindset for infrastructure that's reliable, observable, and requires minimal toil to maintain. If a runbook step can't be automated, you want to know why.

🔒 A constant and keen eye for security risks - we store and display some of people's most sensitive personal data, and enterprise onboarding is exactly where credentials and access rules get sloppy.

🌩️ Comfort with infrastructure-as-code (Terraform, CloudFormation, Pulumi) and CI/CD systems you've extended rather than just configured.

🔧 Full-stack range. Much of this tooling needs a UI that an implementation lead or a customer admin can use without asking an engineer for help.

🕵️ Willingness to sit with the people doing the work. The best version of this role starts by shadowing an onboarding, writing down every manual step, and picking the ones worth killing first.