Lead Architect/Engineer, Back End

Role overview

A lead engineering position focused on the back-end services and data model of an enterprise platform used by healthcare marketers to plan, launch, and optimize professional and consumer engagement. The role combines hands-on technical leadership with people management, shaping how the platform scales, performs, and integrates with surrounding systems.

Responsibilities

- Own the platform's application data model across relational and NoSQL stores, including access-pattern decisions as the product grows - Define and evolve API contracts alongside front-end leadership so the interface and data model move together as one system - Direct the integration with the data warehouse, including data flow direction and cadence, keeping warehouse queries off the request path - Partner with DevOps on reliability, performance, and cost targets for back-end services - Collaborate with data science to productionize models and recommendation features built on top of platform data - Hire, mentor, and grow a team of back-end and data engineers, setting standards for code quality and CI-enforced testing - Set guardrails and review standards for AI-assisted or agentic coding practices on the team - Partner with product and design on problem definition, scope, and sequencing from the start of each effort

Requirements

- 8+ years in back-end or full-stack engineering, including 2+ years managing engineers - Hands-on experience leading a data model and access patterns for a B2B or enterprise product at scale, ideally across both a relational and a NoSQL store - Track record of hiring engineers and running a technical interview loop from scratch - Comfort directing and reviewing AI-assisted coding, with judgment about what requires human review - Experience partnering with product, design, and data science counterparts on scope and sequencing - Self-directed and adaptable, comfortable adjusting priorities as a small team ships and grows

Benefits and work setup

The organization operates a hybrid model: employees within roughly an hour of a local office attend in person two days per week, while those in regions without a nearby office may work remotely with periodic in-person collaboration sessions. Specific benefits vary by region.