Gain Ltd

SaaS

GAIN-Innovation-BusinessAnalyst

Mumbai, Maharashtra, India FULL TIME Remote Friendly
Market Sentiment
HIGH DEMAND

Neural analysis suggests this role is
optimal for Mid+ candidates.

The Brief

“GAIN- Innovation- Business Analyst at Gain Ltd. Skills: Product Documentation, Stakeholder Liaison, Jira & Delivery Tracking. Own the documentation layer between product thinking and engineering delivery. Keep Spirea and Lupine’s requirements clearly defined, consistently documented, and traceable from concept through to delivery”

What You'll Achieve.

Keep Spirea and Lupine’s requirements clearly defined, consistently documented, and traceable from concept through to delivery; Ensure data models, KPI logic, scoring methodologies, and system behaviours are described accurately enough that a new engineer can onboard from the documentation alone; Ensure commercially viable products are launched in the most expedient timelines; Ensure we work on the most important functionality and features

Industry & Context.

SaaS
Problems you'll solve

Thinks in systems; Understands that a vague requirement is a bug waiting to happen; Challenge ambiguity; Flag gaps; Hold the line on documentation quality; Spot when something doesn’t add up in a data model or system logic description

What They're Looking For.

Must Have

Own the full PRD set across both products, Write and maintain PRDs structured, unambiguous, and technically grounded without requiring engineering to fill in the gaps, Treat documentation as a living system, not a point-in-time artefact, update PRDs when scope shifts, edge cases are resolved, or new decisions are made, Document both what the product should do and what it currently does, keeping the distinction clear, Ensure data models, KPI logic, scoring methodologies, and system behaviours are described accurately enough that a new engineer can onboard from the documentation alone, Work directly with the Product Owner to translate strategic and design decisions into written requirements before they reach engineering, Partner with Engineering to ensure PRDs reflect technical constraints and implementation realities, not just product intent, Facilitate alignment when documentation, design, and build are out of sync, and own the resolution, Support cross-functional stakeholders, including marketing and commercial teams — with product context and documentation when needed, Maintain clear traceability between PRD requirements and Jira epics, stories, and bugs across both Spirea and Lupine, Write Jira tickets that are specific, scoped, and linked to source documentation, not just summaries of conversations, Proactively flag when tickets diverge from documented requirements and drive resolution before it becomes a build problem, Support sprint planning by ensuring stories are well-defined and acceptance criteria are agreed before they enter the backlog, Prioritize requirements with Stakeholders to ensure commercially viable products are launched in the most expedient timelines. Ensure we work on the most important functionality and features, Understand the project management methodology and timelines to ensure your deliverables are correctly prioritized and all the interdependencies are identified

Nice to Have

Comfortable working in a product that is being built while it’s being flown — requirements evolve, scope shifts, and the BA needs to stay ahead of that rather than behind it, Can hold the documentation standard firm even when speed creates pressure to cut corners vague PRDs create engineering debt and you know it, Understand performance marketing fundamentals well enough to write accurately about KPI logic, fatigue signals, and creative strategy without needing everything translated for you, Fluent in how ad platforms structure their data — campaign hierarchies, creative objects, objective mapping, attribution — or can get there quickly, Don’t need a formal handoff chain to do your best work — you take direction from conversations, prototypes, and design files, and you know how to shape that into a document engineering trusts, Can read a data model or system logic description and spot when something doesn’t add up, even if you’re not writing the SQL yourself, Comfortable using AI tools — including tools like Claude — to accelerate documentation, prototype UI and UX concepts, and bring product ideas to life before engineering picks them up

What You'll Do.

Own the documentation layer between product thinking and engineering delivery

Keep Spirea and Lupine’s requirements clearly defined

consistently documented

and traceable from concept through to delivery

Write and maintain PRDs

Document product functionality and current state

Translate strategic and design decisions into written requirements

Partner with Engineering on PRDs

Facilitate alignment between documentation

Support cross-functional stakeholders with product context and documentation

Maintain traceability between PRD requirements and Jira epics

scoped Jira tickets linked to source documentation

Flag ticket divergence and drive resolution

Support sprint planning

Prioritize requirements with stakeholders

Identify interdependencies

How You'll Work.

Team & Collaboration

Work closely with the Product Owner and Engineering team; Move fluidly between product and engineering; Partner with Engineering; Facilitate alignment when documentation, design, and build are out of sync; Support cross-functional stakeholders, including marketing and commercial teams

Communication Scope

Writes with precision

Process & Methodology

Understand project management methodology and timelines, Ensure deliverables are correctly prioritized, Identify all interdependencies

Full Job Description

GAIN IQ is building two SaaS tools under its product suite: Spirea, a creative intelligence and performance creative platform, and Lupine, a CRO tool. Both are actively being developed and deployed with real clients, which means the documentation layer that sits between product thinking and engineering delivery matters enormously. We’re looking for a Business Analyst who can own that layer, someone who writes with precision, thinks in systems, and understands that a vague requirement is a bug waiting to happen. You’ll work closely with the Product Owner and Engineering team to keep Spirea and Lupine’s requirements clearly defined, consistently documented, and traceable from concept through to delivery. This is not a passive note-taking role. You’ll be expected to challenge ambiguity, flag gaps, and hold the line on documentation quality even when things are moving fast. **Requirements** **Product Documentation** You will own the full PRD set across both products. Specifically: 1. Write and maintain PRDs structured, unambiguous, and technically grounded without requiring engineering to fill in the gaps 2. Treat documentation as a living system, not a point-in-time artefact, update PRDs when scope shifts, edge cases are resolved, or new decisions are made 3. Document both what the product should do and what it currently does, keeping the distinction clear 4. Ensure data models, KPI logic, scoring methodologies, and system behaviours are described accurately enough that a new engineer can onboard from the documentation alone **Stakeholder Liaison** This role sits at the intersection of product and engineering. You will need to move fluidly between all three: 1. Work directly with the Product Owner to translate strategic and design decisions into written requirements before they reach engineering 2. Partner with Engineering to ensure PRDs reflect technical constraints and implementation realities, not just product intent 3. Facilitate alignment when documentation, desig

Free ATS check

Applying for this GAIN- Innovation- Business Analyst role?

Most applicants get filtered before a human reads their resume. See if yours makes the cut.

ANONYMOUS · UNFILTERED

What do employees actually say about Gain Ltd?

Real rants from real employees. Read before you apply.

Read Company Rants →