Senior Backend Developer

Design, build, and test features across our backend and frontend. You'll take part in design discussions, implementation, code review, and testing.

Technical skills

Strong TypeScript and Node.js engineering: You have built and maintained substantial TypeScript services in production.

Micro-services design experience: You have built systems composed of multiple services and you have clear understanding of service boundaries, contract evolution, error handling across service calls, and observability.

Kafka and event-driven architecture: You have worked with Kafka or a comparable event streaming platform in production. You have a good understanding of topic design, partition strategy, consumer group behavior, idempotency, ordering guarantees, and what happens when a consumer falls behind or a message cannot be processed. Bonus if you have specific experience with Confluent.

PostgreSQL: You can design a database schema, and understand transactions, indexing, and migration strategy.

AWS or equivalent cloud experience with Kubernetes: You are comfortable with operating services in AWS. You can navigate the services we use (e.g. EKS, RDS, S3, CloudWatch, IAM etc.) and you can debug a problem that crosses the boundary between your code and the infrastructure it runs on.

Unit test frameworks such as jest and vitest

Playwright or equivalent end-to-end testing experience: You have hands-on experience with test authoring frameworks such as Playwright (ideal), Cypress, Selenium, or similar.

Test design as a discipline: You can take an acceptance criterion or a user story and decompose it into a coverage strategy that includes unit, integration, and end-to-end tests in sensible proportions. You know when an e2e test is the right answer and when a unit test would catch the bug faster and more reliably.

Engineering qualities

Engineering quality as a habit: You think about testability while you design.

Strong written communication: You write high quality and easy to understand design documents, PR descriptions, Test cases etc.

Systems thinking across boundaries: You have worked across integration boundaries, have debugged problems that span multiple systems.

Comfort with ambiguity: You ask clarifying questions, surface assumptions, and do not quietly build whatever is written in the ticket.

Nice to have

Experience in healthcare, LIMS, or any FDA-regulated software environment.

Direct experience with Confluent, Redox, or EHR integration work is a real plus.

Familiarity with requirements management tools like Jama.

Hands-on experience with modern AI tools (Claude, Cursor, etc.)