Overview
Lead ArmorCode's engineering organization for the product, owning Development and Quality Engineering, delivery predictability and release quality, the org structure and people behind them, and engineering-level escalations on strategic enterprise accounts. Reports to the Head of Engineering.
What you'll do
- Lead Development and Quality Engineering, creating shared practices and priorities that let the two functions reinforce each other.
- Redesign org structure as the product, headcount, and AI-driven ways of working evolve, including pod structure, reporting lines, and Dev and QA boundaries.
- Hire and develop engineering managers and QA leadership, set the hiring bar, and build a bench able to run each function independently.
- Own IDPs for all direct reports and key senior engineers, with a 3-6 month review cycle.
- Own promotions, calibration, and performance processes for the org, including promotion narratives, calibration sessions, and attrition management.
- Handle escalations that span functions, such as releases delayed by both Dev and QA, or inter-team friction that blocks delivery.
- Own delivery predictability across releases: planning, sprint health, dependency management, and on-time, high-quality shipping.
- Set engineering standards for architecture, code review, branching, and release practices as headcount and product surface area grow.
- Partner with Product and other engineering leaders to commit to realistic scope and timelines, and hold the line when they aren't realistic.
- Drive technical direction for a platform that must scale across customers, integrations, and deployment models, and keep tech debt visible and managed.
- Own incident response practice for the product, including availability and accountability when production incidents involve strategic customers.
- Own engineering-level escalations for strategic enterprise accounts: debugging production issues, reviewing customer logs, coordinating fixes, and representing engineering with the customer or account team.
- Decide when an issue is ArmorCode's problem versus a third-party integration, and own the communication when that distinction matters.
- Manage follow-through on enterprise-specific requirements (private instances, dedicated tenants, custom integrations) from engineering's side.
- Own org-level quality outcomes with Dev and QA sharing accountability for what reaches customers.
- Drive shift-left practices and bring QA closer to development so quality is built in.
- Own org-wide quality metrics, including defect leakage, escaped defects, and regression stability, and report them to leadership.
- Set the vision for AI-native engineering, including how code is written, reviewed, tested, and released when agents are part of the team.
- Define org-wide standards for agentic work, including genuine autonomy versus AI-assisted work, required eval harnesses, guardrails, and where human sign-off remains mandatory.
- Make model, tooling, and vendor decisions and own the tradeoffs, including build versus buy.
- Hold managers accountable for agentic adoption through outcome review rather than code review.
- Report the org's actual agentic maturity to leadership and the plan to close the gap.
- Build the skills, hiring profile, and ways of working the org needs as AI changes what engineers do.
- Set multi-quarter engineering strategy aligned with company priorities and the ASPM market direction.
- Own the FY capacity model for the org, including maintenance load, integration overhead, headcount allocation, and the evidence-based case for budget changes.
- Define and track organizational health metrics, including delivery predictability, defect leakage, regression stability, incident resolution time, and agentic workflow adoption.
- Own quarterly OKRs and monthly business reviews, reporting progress to the India Engineering Head, the Head of Engineering, and broader leadership.
- Make build-versus-buy and vendor decisions for engineering tooling.
- Maintain an engineering rubric, an agentic maturity rubric, and a people rubric for the management layer.
What you'll need
- 12+ years in software engineering, with a strong development background and a track record of leading large engineering teams.
- Experience growing a team from a handful of people into the 40-50 range, including hard calls on org structure, not just steady-state management.
- Experience owning delivery for a product with real release cadence and customer commitments, and explaining predictability in terms of data.
- Experience leading AI/agentic adoption across a team or org, including model and vendor decisions, setting eval expectations, and distinguishing autonomous workflows from AI-assisted ones.
- Experience managing or working closely with QA, and knowing which coverage numbers mean something.
- Strong architecture judgment and hands-on comfort with cloud/AWS and scalable system design; comfortable in a war room when production breaks.
- Comfort owning enterprise customer escalations directly, representing engineering credibly to a strategic customer, and knowing when to escalate and when to absorb.
- Able to sit across the table from other engineering and product leadership and hold their own.
- Willing to write code, scripts, or tooling when that is the fastest path to unblocking the team.
Nice to have
- Experience running enterprise-grade private or dedicated cloud instances for large customers, not just multi-tenant SaaS.
- Exposure to LLM/GenAI tooling beyond general familiarity, such as prompt design, model selection, MCP or tool-call architecture, or eval harness design.
- Experience setting agentic engineering standards across multiple functions, not just within one team.
- Prior experience in a company going through real org restructuring, including navigating manager friction, attrition risk, and role ambiguity.
- Experience leading QA or a QA-to-engineering career path.
- Cybersecurity or SaaS background.
Details
- Reports to the Head of Engineering.
- Location: Gurugram.
Read the full description and apply on the company’s own careers page.