Roles & Responsibilities The EM owns the system that produces the work. You're accountable for whether it lands, on time, at sustainable quality, with people getting better, not for whether any one project ships. This role fails when a date slips in September and nobody saw it coming.

You'll manage a team of 10+ engineers. Writing production code day to day is explicitly not part of the job, but you haven't lost your technical range: most weeks you're framing an approach and reviewing low-level design, not inventing current architecture from scratch, but you can still originate one from ambiguity when the problem genuinely calls for it.

What you'll do

- Decompose, size, and track delivery with real numbers, and call a slip early, before it's a surprise. Descope or kill something deliberately to protect a date when that's the right call
- Install process where none exists, alerting, error budgets, escape-rate tracking, estimation discipline, and get the team to actually adopt it, not just tolerate it
- Frame the right approach to ambiguous, underspecified problems: find the smallest real version, decide what's worth building for one customer versus a category, and name what you're deliberately not building




- Partner with Product to resolve in/out debates without steamrolling the roadmap or caving to it
- Manage a 10+ engineer team through the full range: a bored high performer, an under performer you have to move to a real decision, and everything in between
- Own a hiring bar without owning headcount, and hold it under real pressure to fill a seat
- Critique a design and catch the failure mode that's missing. At the top of the bar, originate the high-level shape yourself and take it down to interfaces, data model, and API contracts
- Lead your team through real production incidents: own the customer-facing response, run a postmortem that actually changes something
- Work with Support, Design, and Compliance/Finance, whose incentives genuinely differ from engineering's, and get real buy-in from them
- Manage up: deliver an uncomfortable truth to leadership, negotiate headcount or timeline under pressure, without capitulating or getting steamrolled
- Build a team people actually choose to stay on, through concrete practices, not a values poster
- Stay current on the industry through real people and sources, and tie a recent shift to a decision you actually changed

Skills: headcount,engineering manager,building,it,customer,em

📌 Engineering Manager (Bengaluru)
🏢 CG-VAK Software u0026 Exports
📍 Bengaluru