Clients don't hand us clean specs. They hand us a WhatsApp message, a half-remembered conversation from a review call, and a "you know what I mean, right?" Somewhere between that ambiguity and a working sprint backlog, someone has to do the translation — without losing intent, without over-promising, and without letting the same requirement get re-interpreted three different ways by three different engineers.

That someone is this role. You're not a stenographer who writes down what the client says. You're the person who asks the one question nobody else thought to ask, catches the requirement that's really three requirements wearing a trench coat, and turns "we want it to feel more automated" into a spec an engineer can actually build against.

What you'll actually do

- Interrogate the ask, not just record it. Sit with clients (think Amazon, Dulux, Exide scale accounts) and pull out what they need, which is rarely identical to what they first say.
- Convert vague into buildable. Turn conversations, calls, and scribbled notes into structured requirement docs, user stories, and acceptance criteria that engineering can pick up without a follow-up meeting.
- Own the paper trail. Every requirement has a source, a rationale, and a sign-off. No more "wait, who asked for this?" three sprints later.
- Spot the landmines early. Flag scope creep, contradictory asks, and technically unrealistic expectations before they become a delivery retro talking point.
- Bridge, don't just relay. Sit between client stakeholders and engineering leads,



translating business language into technical scope and technical constraints back into business language.
- Close the loop. Validate that what got built actually matches what was asked — and what was meant.

What makes you good at this

- 2–5 years in business analysis, product ownership, solutions consulting, or client-facing delivery roles — ideally in B2B SaaS or enterprise software.
- You ask "why" before you ask "what." You're suspicious of any requirement that sounds too clean.
- You can write a spec a developer won't have questions about — and a summary a CXO won't need explained.
- Comfortable in ambiguity, uncomfortable leaving it unresolved.
- Basic technical fluency — you don't need to code, but you need to know what's hard, what's expensive, and what's a two-line config change.
- Bonus: exposure to distribution, retail tech, trade marketing, or channel management domains.

What you won't be

- A order-taker who forwards client emails to engineering.
- A yes-person who commits the team to scope nobody scoped.
- Invisible. This role has a direct line to how cleanly (or messily) every project starts.

Why join TRIAD

We build VMX, Redi, and BrandCore — real software running inside real distribution networks, not a demo-only pitch deck. You'll work directly with founders, sit close to enterprise accounts, and your fingerprints will be on the difference between a smooth delivery and a painful one. If you like being the person who makes chaos legible, this is your seat.

Pay: ₹300,000.00 - ₹600,000.00 per year

Advantages:

- Flexible schedule
- Paid sick time
- Paid time off

Work Location: In person

📌 Business Analyst (a.k.a. the Requirements Detective) (India)
🏢 triad technologies
📍 India