Role Summary

We are looking for a Senior Business Analyst to own requirements and solution definition for, a US television and media production company whose platform runs their entire client lifecycle — agreements and payments, production planning, field shoots, post-production, client support, and billing.

You will run discovery directly with the client's US business stakeholders and convert what you learn into product requirement documents, lifecycle models, user stories, and acceptance criteria that the engineering team can build from without rework. A significant share of the platform is AI-assisted — drafting, classification, summarization, and retrieval with human review — so defining how those features behave, what a reviewer sees, and what happens when the model is wrong is core to the role, not an edge case.

The role exists to make sure requirements reach engineering complete and unambiguous the first time. You will work the 16:00–00:30 IST shift so that you sit inside the US working day, with five to six hours of live overlap for stakeholder discovery rather than a rushed hour at the end of it.

Key Responsibilities

Requirements &

- Discovery

- - Lead discovery sessions with US business stakeholders across operations, accounting, sales, support, production, and retention — surfacing undocumented process and the workarounds teams currently rely on.
- Author product requirement documents covering business problem, desired outcomes, baseline scope, user stories, acceptance criteria, and business rules, at a level of detail engineering can build from without a follow-up meeting.
- Define requirements for AI-assisted functionality — what a human reviews and when, how low-confidence output is routed, escalation paths, and the expected behaviour when the model gets it wrong.
- Model end-to-end lifecycles and status flows including decision points, prerequisites, blocked states, approvals, and exception paths.
- Specify system integrations — data moved, direction, triggers, error handling, retries, deduplication, and reconciliation across CRM, accounting, e-signature, payment, and support systems.

Solution Design &

- Approval

- - Produce the solution and experience design and progress it through the client's product and technical approval gates.
- Facilitate targeted design reviews with selected subject-matter experts and incorporate approved feedback into a revised design.
- Document assumptions, open decisions, risks, and gaps — escalating business, financial, and compliance decisions to the owner rather than resolving them silently in a specification.

Delivery &

- Release

- - Decompose approved designs into delivery projects, user stories,



and technical tasks.
- Run backlog refinement and sprint planning with the engineering team on a two-week cadence.
- Coordinate UAT with the requesting stakeholder and drive defects to closure before release.
- Produce release notes, updated SOPs, and training material so that what ships is adopted, not merely deployed.
- Maintain delivery visibility — owner, status, blockers, dependencies, and risk — at project level throughout.

Required Technical Skills Must-have and preferred skills are separated below. The preferred rows are genuinely preferred — candidates are not expected to hold all of them. Domain Skills &

- Technologies Must / Preferred Business Analysis Requirements elicitation and facilitation
- PRD / BRD authoring; user stories with acceptance criteria; business-rule definition; scope baselining and change control Must AI-Enabled Products Requirements for AI-assisted features — drafting, classification, summarization, extraction, search and retrieval, assistants; human-in-the-loop review design, confidence handling, escalation and failure paths Must Process &
- Lifecycle Modelling As-is and to-be process mapping; lifecycle and status models; state transitions; exception and edge-case paths; swimlane flows Must Integrations &
- Data Flow Cross-system requirements
- API and data-flow specification; triggers, error handling, retry, deduplication, and reconciliation Must Agile Delivery &
- Tooling Two-week sprint delivery; backlog refinement; sprint planning
- UAT coordination. Client uses Linear —
- Jira or Azure DevOps experience transfers Must Documentation &
- Diagramming BPMN, UML, or flowchart modelling; wireframing in Figma, Lucid, Miro or similar Preferred AI Implementation Concepts Prompting, retrieval-augmented generation (RAG), evaluation of model output, review-queue design Preferred Data Querying SQL sufficient to validate data and answer your own questions without engineering support Preferred Business Domain Contracts and agreements, billing, payment plans, e-signature workflows, recurring revenue Preferred Industry Domain Media, broadcast, or video production — explicitly not required; the business will be taught Preferred

Qualifications &

- Certifications

- - Bachelor's degree in Computer Science, IT, Engineering,



or Business — or equivalent practical experience.
- 6–10 years in business analysis, product analysis, or systems analysis on software delivery, where requirements you authored were used directly by engineering teams.
- Demonstrable experience on at least one product with AI-assisted functionality running in production, not proof-of-concept only.
- Experience working with international stakeholders across time zones. Direct US-client exposure is preferred but not required.

Preferred Certifications

- - CBAP or CCBA (IIBA)
- PMI-PBA
- CSPO, CSM, or equivalent agile certification

Soft Skills &

- Cultural Fit

- - Able to lead client-facing discovery and design-review calls with senior US business stakeholders — owning the conversation, not minuting it.
- Written communication robust enough to be the primary handoff across a 9.5-hour time difference. Documents must stand alone without a follow-up call.
- Comfortable working the 16:00–00:30 IST shift sustainably, and working independently with minimal supervision during the early hours before US stakeholders come online.
- Disciplined about surfacing assumptions and open decisions to the decision owner instead of resolving them quietly inside a specification.
- Able to hold scope — distinguishing a correction, a newly discovered requirement, and a future enhancement when stakeholders ask for more.

What We Offer

- - A long-term embedded engagement with a single client rather than rotation across short projects — and the depth of business knowledge that comes with staying on one account.
- Direct access to US business owners and decision-makers. You are in the room when decisions are made, not reading about them the next morning.
- Hands-on requirements work on AI features running in production — experience that is still scarce in the market and travels well.

First 6 Months –

- Priority Focus

- - Month 1 —
- Walk the client's business end to end with the people who run it; learn the intake and delivery process; deliver a first, small requirements document.
- Month 2 —
- Run discovery on a live piece of work and deliver a complete PRD with acceptance criteria and business rules.
- Month 3 —
- Produce a solution and experience design and take it through both product and technical approval.
- Months 4–5 —
- Decompose an approved design into a delivery backlog, run refinement and sprint planning, and close a first UAT cycle with the requesting stakeholder.
- Month 6 —
- Establish a repeatable requirements standard for the account so handoffs to engineering are consistently complete without depending on any one person's memory.

📌 A- Senior Business Analyst (India)
🏢 Softobiz
📍 India