Data Analyst
This is a role for an analyst who likes variety.
This is a role for an analyst who likes variety. You'll work across several client projects in different domains – fintech, retail, energy, residential-living apps, and whatever's next. Some are still in pre-sale and discovery; others are deep in delivery. The work keeps changing, and so does what you pick up along the way.
We're an AI-forward team, and we look for analysts who think the same way – using AI to draft faster, decompose smarter, and free up time for the thinking that actually matters.
Run discovery sessions and workshops with clients and their stakeholders, asking the questions that surface what they really need
Decompose epics into features and write clear, testable acceptance criteria
Spec behavior across mobile, web, and admin/CMS – app states, offline/sync, deep links, content management, and what the user sees when data is missing or loading
Spec integrations end to end – how external systems connect, what data maps where, and how the app behaves when they're slow or down
Think through edge cases, fallbacks, and dependencies – not just the happy path
Model flows visually so the team aligns fast – BPMN, UML, sequence, flow diagrams
Pick up existing products and work out how they're built before reshaping them
Partner with the PM, architect, designer, and dev team to take a feature from idea to build, and stay with it through testing and release
Coordinate with external vendors and client-side teams when integrations or shared systems are involved
Keep requirements traceable and version-controlled – Git for the team, Confluence for the client, Jira for tracking
This is a role for someone who enjoys both sides – the analysis and the technical depth. You're as comfortable defining an API contract as you are running a client workshop.
2–4 years as a System or Business Analyst, with hands-on experience writing technical requirements
You write feature specs a developer can build from without guessing – structured and complete, with clear acceptance criteria, data dictionaries, and field-mapping tables
REST APIs and JSON are familiar ground – you read OpenAPI/Swagger and define contracts, not just consume them
You think about the unhappy paths too – error states, fallbacks, validation logic
You're confident with diagrams: BPMN, UML, sequence, flow
Systems thinking comes naturally – you spot edge cases and dependencies early
You're comfortable analyzing an existing system from the outside – reading its behavior, integrations, and data flows when documentation is thin
You're comfortable owning your requirements end to end
B2+ English for client conversations
Payment & billing logic – checkout, subscriptions, provider integrations
Subscription & wallet-style flows – recurring billing, shared or pooled balances
Posted August 6, 2026