Business Analyst

Requirements: Qualifications 3+ years of experience as a business analyst or product owner on a B2B SaaS product in an agile team. Proven ability to write clear, testable user stories and acceptance criteria, and to break large features into sprint-sized work. Working SQL and the ability to read data mappings, REST APIs and integration specs (CSV, JSON, XML). Experience leading UAT and working directly with clients and partners. Hands-on experience with Azure DevOps or a similar backlog management tool (such as Jira). Daily use of AI tools for writing, analysis and test design. Demonstrated ability to work remotely across time zones, including overlap with an offshore team in Bangkok. Excellent written and verbal communication skills, with sound judgment about when to escalate to the Product Manager.

Preferred

Qualifications Experience in hospitality tech, restaurant, retail, payments or fintech. Familiarity with reconciliation, settlement, gratuity or cash management workflows. Exposure to POS systems, property management systems, OTA platforms or payment processors. Bachelor's degree in business, information systems, computer science or a related field. Core responsibilities: Role and

Responsibilities The Business Analyst is the link between the Product Manager and Evention's engineering pods, translating product requirements into clear, testable user stories and making sure each one is ready to build. The BA works closely with the Product Manager to refine features into deliverable work, so the PM can stay focused on customers, discovery and the roadmap. As the PM's day-to-day delivery partner, the BA is the first point of contact for developers' requirement questions and confirms that completed stories meet their acceptance criteria. Sitting on the Product team and working closely with the Core or Growth Product Manager, the BA supports one to three product lanes - Core: Total Recon, Tips & Gratuities and OTA Recon; Growth: Cash Management, Credit Card Optimization and new modules from pilot onward. This is not a product owner role: the BA makes recommendations on priority, scope and release timing, and the PM makes the decisions.

Requirements Ownership: Collaborate with the Product Manager to break down features into workable user stories, with business acceptance criteria written in Given / When / Then. Partner with the tech lead, who adds technical criteria and an implementation approach to each story, and confirm it meets the Definition of Ready before it enters a sprint. Elicit and document detailed requirements, including data mappings, business rules, process flows, and integration and partner specifications. Refine and sequence stories within the feature priorities set by the PM, splitting large features into stories that can be completed in a single sprint. Backlog and Delivery: Facilitate the Friday backlog review for assigned lanes, keep the Azure DevOps backlog groomed and current, and clear the weekly AI hygiene sweep. Represent the PM in Monday planning and standups; for Bangkok pods, present the PM's written sprint goal. Serve as the first point of contact for developer requirement questions, responding within one business day. Acceptance, Bugs and UAT: Review completed stories against their acceptance criteria and accept them; the PM accepts features. Plan, coordinate and lead User Acceptance Testing (UAT) with clients and partners, including test scenarios and tracking outcomes. Investigate and document bugs with reproduction steps and expected behavior traced back to the original story. Capture client requests and Support patterns and route them to the PM's intake queue for prioritization, never straight into a sprint. Client and Partner Enablement: Support clients and partners through onboarding to new releases. Create support documentation and train Evention Support and Client Success on new product behavior. AI-First Delivery: Use AI tools daily to draft stories, acceptance criteria and test cases, and take ownership of the quality of the result. Direct an AI coding agent against Ready stories for small, approved Core enhancements, with the tech lead reviewing the pull request. What This Role Does Not Own Priority, scope or release dates. The BA recommends; the PM decides. The roadmap, discovery, prototypes and POCs. The PM and tech lead own these. Technical design, code review and the Definition of Done. The tech lead owns these. Running planning, standups or retro. The pod tech lead facilitates; the Development Manager runs the release plan. Escalate to the PM when a story would change feature scope, two priorities conflict, a client asks for something outside a feature, or a release date is at risk.

Benefits: Competitive salary Opportunity to shape the HR function of a rapidly growing BPO. Work closely with a team of industry leaders who have successfully scaled BPOs in the past. Career growth and development opportunities. Please attach your CV and we will be in touch for a confidential chat. Let's do great things together!