Engineering Lead (Head of Engineering)

About Nogrunt

Nogrunt takes QA from raw documentation (meetings, videos, BRDs) to fully automated, self-healing test execution — with CI/CD integration and go/no-go reporting. No one else in the market reliably automates test-case-to-script generation at this accuracy and scale. Built for any team shipping custom software.

Why this role matters right nowNogrunt operates on just-in-time product delivery — we build a step or two ahead of what customers ask for, rather than managing a long, static roadmap. That focus keeps engineering costs tied to actual demand.

Rather than stopping the world for massive rewrites, we tackle technical debt opportunistically — refactoring code paths when customer requests require us to touch them.

As Nogrunt scales, engineering needs dedicated operational leadership. You will run this iterative engine as a disciplined system rather than a source of constant fire-fighting. Design decisions, cross-team coordination, and daily execution issues all need an owner who can hold the standard consistently. You will partner with the CTO to ensure what we build stays matched to real customer needs, sequencing work so we are always building and refactoring the right things at the right time.

What you'll do• Own the operational leadership of engineering — priorities, execution quality, and issue resolution across the function

- Run engineering as a series of tight, deliberate iterations — scoping each cycle to what customers need next, not what might be nice to have eventually
- Partner with the CTO on design and architecture decisions, acting as a rigorous second perspective on what should be built, how, and at what level of complexity
- Opportunistic Refactoring: Address technical debt strategically by refactoring legacy code paths during customer feature builds, keeping systems maintainable without halting delivery for pure maintenance work
- Scope Discipline: Enforce an engineering standard that favors the simplest solution for current needs, ensuring refactoring effort stays strictly proportional to the feature being shipped
- Keep a clear, current read on the gap between what customers are asking for and what we've shipped, so that gap is managed deliberately rather than discovered under pressure
- Coordinate across dev, QA, implementation, and support teams, ensuring issues are owned, tracked, and resolved without relying on informal escalation




- Establish and run the triage process for production issues and customer-facing bugs — determining priority, ownership, and resolution path
- Serve as the primary engineering point of contact for implementation and support teams — translating customer expectations into scoped, buildable work, and translating technical constraints back into terms those teams can act on
- Keep design and delivery aligned with current product capabilities and real customer expectations, guarding against building ahead of what the business actually needs
- Spot when a design or initiative is drifting from customer need or engineering standards, and course-correct it early — before it turns a manageable iteration into a scramble
- Develop enough working fluency across our stack (execution engine, extension/mobile automation layers, infrastructure, backend services) to make credible, cross-cutting calls without needing to be the top specialist in any one layer
- Pace & Rhythm: Calibrate output to match our stage — maintaining composure during busy stretches while establishing a stable, predictable delivery pattern
- Own and continuously improve the engineering process itself — how work is scoped, handed off, tracked, and closed out across teams

What success looks like in the first 3–6 months• Engineering is operating with a clear, consistently applied process for triage, coordination, and issue resolution across dev, QA, implementation, and support

- You've established a working rhythm for iteration — the team can point to a clear sequence of "what we shipped, what's next, why in that order" rather than reacting iteration to iteration
- You've identified and corrected at least one design or feature heading toward unnecessary complexity, keeping it scoped to real customer need
- You've resolved a cross-team issue (dev/QA/implementation/support) end-to-end, establishing a repeatable pattern for similar issues going forward
- The CTO treats you as a trusted second opinion on whether a design holds up against real customer needs and what the team can support
- Dev, QA,



implementation, and support teams see you as the person who keeps engineering moving and removes blockers — a source of clarity, not a bottleneck
- You've built enough working knowledge of our execution, automation, and infrastructure layers to ask sharp questions and evaluate proposed solutions critically

Who we're looking for• Significant hands-on engineering experience, including meaningful time leading or closely coordinating a team, with the judgment that comes from having shipped and supported real production software

- Real comfort with iterative, close-to-the-edge delivery — building a step or two ahead of customer need rather than working off a long, settled roadmap, and staying composed while doing it
- Track record operating as a senior partner to technical leadership — able to challenge a design with sound reasoning, not simply execute direction handed down
- A strong, practical bias toward simplicity — instinctively scopes solutions to the size of the actual problem and the iteration in front of them, not a hypothetical future one
- Experience coordinating across engineering, QA, implementation, and support or customer-facing teams in a live product environment with real customers in production
- Comfortable owning ambiguous, cross-functional issues — triaging, prioritizing, and driving them to resolution rather than escalating everything upward
- Broad technical range across the stack (backend, automation/execution systems, infrastructure) — deep enough to reason credibly across layers, without needing to be the leading specialist in each
- Robust root-cause thinking — comfortable tracing an issue across team and system boundaries rather than stopping at the first plausible owner
- Comfortable with ambiguity and incomplete specs — able to define scope and approach when there isn't a clear one given
- Grounded in customer reality — instinctively weighs what a design or fix means for the customer using it, not just its technical elegance
- Actively uses AI tools to speed up development, debugging, and root-cause analysis across the team — not as a crutch, but as a way to move faster and dig deeper
- Ownership mindset — you treat the health and output of the engineering function as yours end-to-end

Interview processIncludes a take-home problem, followed by a discussion of your approach and solution with the team.

📌 Engineering Technical Lead (Bengaluru)
🏢 Nogrunt
📍 Bengaluru