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.
Our Benefits for India employees is- 1-Medical Insurance+Accidental Insurance+Term Life Insurance (Medical Insurance worth INR 7 lacs for you and your family.
Accidental Insurance (Applicable to only employee) – 3 times of CTCTerm.
Life Insurance (Applicable to only employee) – INR 50 lacs) 2- Provident Fund (Company will contribute INR 1800 per month for the provident fund.
) Product Documentation You will own the full PRD set across both products.
Specifically: 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 Stakeholder Liaison This role sits at the intersection of product and engineering.
You will need to move fluidly between all three: 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 Jira & Delivery Tracking Clear documentation only works if delivery stays aligned with it.
You will be responsible for maintaining that alignment: 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 While you are not required to be a project manager you do need to understand the project management methodology and timelines to ensure your deliverables are correctly prioritized and all the interdependencies are identified.
You’ll Thrive Here If You Are 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 Are 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 Are 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
This job post has been translated by AI and may contain minor differences or errors.
