Role summary

The BA will partner closely with our Product Manager and engineering team to capture requirements, clarify scope, and produce structured documentation (functional specs / user stories / acceptance criteria). The outcome we need is simple: engineers should be able to build with minimal back-and-forth, and QA should be able to test against clear, verifiable criteria.

Responsibilities

• Attend/participate in product and engineering discussions and convert outcomes into well-structured written requirements.  
• Produce and maintain documentation such as:
  • Feature/functional specifications (PRD/BRD-style as needed)
  • User stories with testable acceptance criteria (Given/When/Then, where appropriate)
  • Edge cases, assumptions, dependencies, risks, and out-of-scope notes
  • Process/user flows and light diagrams (as needed)
  • Release notes / change logs / knowledge base articles (as needed)
• Create and maintain Jira epics/stories/tasks with strong descriptions, links, dependencies, and clear “Definition of Done” / expected outcomes.
• Drive requirement clarity by proactively identifying gaps, inconsistencies, and open questions; follow up with the PM/stakeholders to close decisions.
• Keep documentation current as implementation evolves (change control, versioning, traceability to Jira items).

Must-have qualifications

• 3+ years experience in a BA / product documentation / technical writing role within a software team.
• Demonstrated ability to write clear, structured, detailed requirements for engineers and QA.
• Strong hands-on experience with Jira: epics, user stories, workflows, linking/dependencies, and good ticket hygiene.
• Comfort working with engineers and understanding technical constraints; able to translate ambiguity into structured requirements.
• Strong communication and stakeholder management skills.

Nice-to-haves

• Confluence/Notion documentation ownership.
• Experience creating process maps/flows (Miro/Lucidchart/draw.io).
• Familiarity with Agile/Scrum delivery environments.

What “good” looks like in this role

• Jira tickets are implementation-ready (minimal clarification needed from engineering).
• Acceptance criteria is complete and testable (QA can validate without interpretation).
• Documentation is consistent, maintainable, and discoverable.