QA - Engineering Manager
at ArmorCode · 101-250 employees
Equity · $16M · Mar 2026
- Seniority
- Lead Manager
- Location
- Gurugram, India
- Posted
- 5d ago
javareactspringrestpostgresmongodbkafkallmci/cd
at ArmorCode · 101-250 employees
ArmorCode provides a unified exposure management and Agentic AI platform that gives enterprises consolidated visibility and control over application, cloud, infrastructure and AI security risks.
<h3><strong>About ArmorCode</strong></h3> <p>ArmorCode helps enterprises manage security risk and governance across today’s heterogeneous technology environments. The ArmorCode Agentic AI Platform gives security teams a system of action, moving from fragmented signals to owned, policy-driven, auditable decisions. Its unified exposure management capabilities deliver visibility, insight and control across four solutions: Application Security Posture Management, Vulnerability Management, Software Supply Chain Security and AI Exposure Management.</p> <p>Processing over 300 billion findings a year across hundreds of native integrations, ArmorCode unifies, prioritizes and drives remediation across applications, cloud, code, infrastructure and AI. Powered by Anya, the industry’s first agentic AI framework for enterprise security, ArmorCode is trusted by global enterprises to reduce exposure and adopt AI and modern software practices with confidence, without replacing existing tools or forcing vendor consolidation.</p> <p>ArmorCoders believe in 5 core values: Hungry. Humble. Hardworking. Honest. Human. Our organization is powered by exceptional professionals who bring fresh ideas and passion to their roles, believing that nothing is beyond reach when our "5H" principles are applied. In their work and professional relationships, ArmorCoders commit to excellence and experiences that leave an impression.</p> <h3><strong>About the Role</strong></h3> <p>This is an Engineering Manager role on our Quality Engineering team. You will be embedded directly alongside a group of product development teams, owning quality outcomes for that entire surface area.</p> <p>You will lead a team of QA engineers — a unified team where manual testing and automation are not separate functions. Your engineers each own their dev pod end-to-end: test strategy, automation coverage, shift-left practices, and quality sign-off.</p> <p>You report to the Director of Engineering and work as a peer with dev EMs, product managers, and engineering leadership — not as a downstream function.</p> <p>The most important thing about this role: AI tooling has fundamentally changed what a QA team can do. We expect this EM to be running agentic QA workflows themselves, not managing from a distance. If you haven't built agent pipelines using Claude Code, Kiro, or Codex, this role will be a stretch.</p> <p> </p> <h3><strong>What You'll Own</strong></h3> <p><strong>Your Team</strong></p> <ul> <li>Lead, mentor, and grow a team of QA engineers across different levels<br>Each engineer on your team is the single QA owner for one or more dev pods — you give them the structure, context, and support to operate with real ownership</li> <li>Drive career development: help engineers grow their automation depth, agentic tooling fluency, and — over time — product code contributions</li> <li>Hire well; raise the bar for your team and contribute to engineering-wide hiring</li> </ul> <p><strong>Quality Strategy</strong></p> <ul> <li>Own the quality strategy for ArmorCode — what gets tested, at what layer, by whom, and at what point in the cycle</li> <li>Ensure every pod has shift-left practices, automation coverage, and clear quality gates as part of the definition of done</li> <li>Surface quality risks proactively to Development teams and PMs — before code ships, not after</li> <li>Own the metrics: defect leakage, escaped defects, automation coverage, regression stability etc</li> </ul> <p><strong>Dev Partnership</strong></p> <ul> <li>Own QA planning for your development teams — define scope, effort, and timelines based on QA complexity and team capacity</li> <li>Review design docs and RFCs for quality and testability implications before implementation begins</li> <li>Partner with dev leads: quality gates and automation are built into how the team works, not added at the end</li> <li>Represent quality in cross-functional conversations with PM, DevOps, and CS</li> </ul> <p><strong>Agentic QA Engineering</strong></p> <p>We're past AI-assisted testing. The expectation for this role is agentic QA workflows — where AI agents handle test generation, execution triage, regression validation, and failure classification autonomously. Your job is to architect those workflows, not prompt an LLM manually for each test case.</p> <ul> <li>Build and operate agentic pipelines using Claude Code, Kiro, or Codex that generate, validate, and maintain test suites with minimal human intervention</li> <li>Design workflows where agents triage CI failures, classify defects, and surface only what needs human judgment</li> <li>Own the eval layer: define how you know the agent's output is correct, and set the guardrails</li> <li>Push the team from "we use AI to write tests faster" to "our test suite largely writes and heals itself"</li> <li>Stay ahead of where agentic testing is going — this space is moving fast and you're expected to bring that thinking into the org, not follow it</li> </ul> <p><strong>Automation & Execution</strong></p> <ul> <li>Your team owns both manual and automation — no handoffs between silos</li> <li>Own QA delivery: test plans, sprint readiness, release sign-off, RCA sessions</li> <li>Manage capacity, flag risks early, and ensure your dev partners have a predictable, reliable quality function</li> </ul> <h3><strong>Who you are</strong></h3> <p><strong>Must Have</strong></p> <ul> <li><strong>3–5+ years managing QA or Quality Engineering </strong>teams in a fast-moving (daily/weekly/bi-weekly releases) SaaS product startup with an <strong>overall experience of 10-15 years.</strong></li> <li><strong>Hands-on experience building agentic workflows</strong> — not just using AI coding assistants, but designing multi-step agent pipelines that operate with real autonomy. You've built or run workflows using Claude Code, Kiro, Codex, or equivalent where the agent is doing the work, not just suggesting it</li> <li><strong>Coding ability </strong>— you can read, writ