Responsibilities
- Lead stakeholder interviews and workshops with clients and internal teams to understand goals, current workflows, and pain points.
- Document current-state and future-state processes, business rules, data definitions, and edge cases.
- Support new-project sizing by breaking scope into epics and stories that engineering can estimate with confidence.
- Identify assumptions, risks, dependencies, and open questions early, and drive them to resolution.
- Write clear user stories with testable acceptance criteria in Jira.
- Partner with the Product Manager to prioritize and groom the backlog ahead of each two-week sprint.
- Work with UI/UX design in Figma to make sure flows and screens match the requirements, and flag gaps before development starts.
- Answer engineering questions during the sprint and keep requirements current as decisions are made.
- Work with QA to make sure acceptance criteria translate into solid test coverage.
- Support sprint demos and coordinate user acceptance testing with clients.
- Keep requirements documentation organized in Google Drive so decisions and their rationale are easy to find later.
- Make sure compliance, security, and audit requirements (including SOC 2 considerations) are captured as explicit requirements, not afterthoughts.
- Act as a trusted point of contact for clients on scope and requirements questions.
- Translate between business and technical audiences clearly and without jargon in either direction.
- Surface scope changes early and help the team and client understand the tradeoffs.
Requirements
- 3+ years as a Business Analyst, Product Analyst, or similar role on software projects.
- Strong experience writing user stories and acceptance criteria in an agile/Scrum environment.
- Proven ability to run discovery sessions and turn ambiguous input into structured requirements.
- Comfort with process mapping and data modeling at a business level (flows, entities, relationships, rules).
- Hands-on experience with Jira; familiarity with Figma and collaborative docs.
- Excellent written and spoken English; comfortable leading client meetings with U.S. stakeholders.
- Enough technical literacy to have productive conversations with engineers about APIs, integrations, databases, and system constraints.
Nice to Have
- Experience in an agency, consultancy, or software services environment juggling multiple clients.
- Exposure to regulated or compliance-heavy domains (e.g., SOC 2, telecom/outbound compliance, education, fintech).
- Experience writing requirements for integrations with third-party platforms.
- Familiar