
Head of Engineering – Agentic AI Healthcare SaaS
Xponentiate
full-time
Posted on:
Location Type: Remote
Location: India
Visit company websiteExplore more
Job Level
Tech Stack
About the role
- Delivery Outcomes
- You will oversee delivery for all products — scope management, release cadence, quality controls, and stakeholder alignment. If something is delayed, it's your responsibility. If a product ships smoothly, you can claim that success. You'll shield engineers from scope changes and give the CEO predictable delivery rather than last-minute heroics.
- Agentic SDLC & AI Governance (The Differentiator)
- This is the core of what makes this role unique. You will own the design and execution of our agentic software development lifecycle:
- - Human-agent workflow design: Define how AI agents participate in coding, testing, code review, and documentation — and where human engineers must intervene.
- - Maker-checker patterns: Build quality gates that catch AI sloppiness. Every AI-generated artifact needs a human verification step calibrated to the risk level — a UI tweak needs a different checkpoint than a database migration.
- - Agent orchestration: Determine which agents we use, how they're configured, what guardrails they operate within, and how engineers supervise their output.
- - AI tool governance: Define approved tools, IP protection policies, and ensure AI accelerates development without introducing risk — especially given the sensitivity of clinical/PHI data.
- - Continuous refinement: This model is new. You'll measure what's working, what's failing, and iterate. The playbook doesn't exist yet — you'll write it.
- Engineering Team
- You will directly manage the engineering team — hiring, performance, coaching, feedback, conflict resolution, and retention. The team is small and high-leverage; every person matters disproportionately. You'll set the culture and performance bar. Difficult conversations happen early. Engineers will want to work with you because you are fair, direct, and invested in their growth.
- System Architecture
- You own the architecture across the full stack: web applications, APIs, infrastructure, and AI integrations. You'll make trade-off calls — speed vs. rigor, refactor vs. ship, infrastructure vs. features. You should be capable of reviewing code, debugging production issues, and challenging architectural decisions with substance. In a clinical data environment, architectural choices carry compliance and safety implications — you'll factor those in.
- CI/CD and Release Engineering
- You will build the release pipeline — CI/CD, environments, quality checkpoints, deployment automation. Chaotic releases end. You'll create a system that lets the team (and their agents) ship confidently and on a predictable cadence.
- Security & Compliance Posture
- You own engineering security: access controls, secrets management, audit trails, and SDLC security. Healthcare data — especially mental health data — demands this. You'll also ensure AI-generated code and agent workflows meet audit and compliance requirements. Enforce rigor without bureaucracy.
- Hiring & Team Building
- You will build the engineering team — define roles, maintain hiring standards, run technical interviews, and make hiring calls. You're building the organization that takes the company from startup to scale. Given our agentic model, you'll also need to think differently about team composition: fewer engineers, higher caliber, optimized for agent supervision rather than raw code output.
- Your First 90 Days
- **Week 1-2:** Immerse yourself. Meet each engineer individually. Understand every product, deployment, and pain point. Map the current human-agent workflows — what's working, what's brittle. Identify delivery risks and the single biggest bottleneck. Build trust through listening, not announcements.
- **Month 1:** Establish a regular delivery cadence. Define the release process and quality standards. Create communication rhythms (standups, retros, planning). Audit the current agentic workflows — identify where AI output lacks sufficient human review. Begin surfacing risks early and reliably, relieving the CEO from delivery oversight.
- **Month 2-3:** Standardize CI/CD across all products. Implement maker-checker quality gates for AI-generated code. Design the AI governance framework — approved tools, IP protection, PHI safeguards for agent workflows. Initiate architecture assessment with a clear roadmap (not a rewrite). Begin hiring to fill gaps. Build the engineering runbook. Establish feedback and coaching routines.
- **Ongoing:** Own engineering completely. Ship reliably. Refine the agentic SDLC continuously. Grow the team. Raise the performance bar. Make the CEO confident that engineering is in expert hands.
Requirements
- First-principles thinker. You reason from fundamentals, not pattern-match from past jobs. When faced with a problem nobody has solved before — like designing quality gates for agent-generated clinical software — you figure it out.
- High learning velocity. The agentic SDLC is new territory. You may not have done this exact thing before, but you learn fast enough that it doesn't matter. You've repeatedly moved into unfamiliar domains and become effective quickly.
- Ownership-oriented. You view engineering leadership as outcome ownership, not task management. You step into chaotic delivery environments and create order — through clarity and accountability, not excessive process.
- Startup-proven. Your experience includes startups, not exclusively large enterprises. You've shipped real products to real users under real deadlines. You know the difference between building something and delivering it.
- Technically credible. You can write, review code, debug production issues, understand systems architecture at scale
- Direct and fair. You give feedback that develops engineers. You handle conflict promptly. Your teams trust you because you're honest, consistent, and keep them focused.
- Raw intellect is non-negotiable. This role demands someone who can operate in uncharted territory — designing human-agent engineering workflows, making architectural calls with clinical data constraints, and building an engineering org model that doesn't have an established playbook. We weight intellectual horsepower heavily.
- Strong academic foundations from a rigorous technical program (IIT, NIT, BITS, or demonstrably equivalent). We value the problem-solving discipline these programs develop.
- Experience building and leading engineering teams (5-15 people) at startups or high-growth companies. You've shipped SaaS products, not just maintained them.
- Familiarity with or strong interest in agentic AI workflows — using AI agents in the development process, not just as autocomplete. If you've already experimented with agent-driven development, that's a significant plus.
- Healthcare/healthtech experience is strongly preferable — especially around compliance, PHI handling, or clinical workflows. Not required, but it accelerates your ramp.
- You've thought seriously about AI governance in engineering — IP, security, quality, audit — and have opinions, not just questions.
Applicant Tracking System Keywords
Tip: use these terms in your resume and cover letter to boost ATS matches.
Hard Skills & Tools
software development lifecyclehuman-agent workflow designmaker-checker patternsagent orchestrationAI tool governanceCI/CDsystems architecturecode reviewdebuggingquality checkpoints
Soft Skills
first-principles thinkinghigh learning velocityownership-orienteddirect and fair feedbackconflict resolutionteam buildingtrust buildingclarity and accountabilityproblem-solvingintellectual horsepower