Debound · Delhi NCR

You will sit between the engineering teams building our digital platforms and the project directors, client organisations and site teams who use them. Your job is to turn how infrastructure delivery actually works into specifications an engineering team can build against, and to keep what gets built honest to what was asked for.

What you'll own

- Requirement gathering across a difficult stakeholder set. Project directors, resident engineers, client organisations and site teams each describe the same process differently. You will run the discovery, resolve the contradictions, and write the version everyone signs off on.
- Specifications and acceptance criteria. Written clearly enough that an engineer can build from them and a reviewer can test against them.
- Code and delivery review. Not as the approving engineer, but as the person who checks that what shipped matches what was specified, and who catches the edge cases nobody raised in the requirements session.
- Feasibility judgement on AI features. Deciding what is genuinely deliverable, what is a demo dressed as a product, and how to phase the difference.
- Translation in both directions. Explaining engineering constraints to non-technical stakeholders, and site realities to engineers who have never been to a project site.

What we're looking for
- Requirements and elicitation experience. Evidence of specs you have written, acceptance criteria you have defined, and scope you have held. We are more interested in ambiguity you resolved than in features you listed.
- A technical foundation solid enough to read code. A computer science degree,



or several years shipping software before moving into product or analysis. You will not write production code, but you will read pull requests and judge whether an implementation matches its spec.
- Written and spoken communication of a high standard. You will produce documents that go to senior stakeholders and to client organisations. Send us something you have written.
- Working literacy in AI and agentic systems. Enough to challenge an estimate, evaluate a vendor claim, and understand why a demo that works on ten documents may not work on ten thousand.
- Comfort with complex, regulated delivery environments. Structured processes, audit requirements and documentation standards should feel normal rather than obstructive.

Signals that would move you to the top of the list
- Infrastructure, construction, EPC or PMC domain exposure — highways, bridges, railways, urban development, power, or water.
- Experience with government or multilateral clients, and with the documentation and approval cycles they require.
- Having worked on project monitoring, ERP, GIS or field-data-collection platforms.
- Any hands-on work with LLM tooling, workflow automation, or data pipelines, however small.
- Familiarity with BIM, DPR workflows, or construction supervision processes.

What this role is not It is not a delivery or scrum-master role, and it is not roadmap authorship at a distance from the build. You will be in the detail: in requirement sessions, in the spec, in the pull request, and on site when that is what it takes to understand the problem.
- Equally, it is not an engineering role. If you want to stay hands-on writing code, this will frustrate you.

📌 Product Manager / Business Analyst - Digital & AI (Delhi)
🏢 Debound
📍 Delhi