About the role
You will own the entire requirements process on our client projects, and you will be the bridge between the client, the product and the engineering team.
This is not a BA role whose main job is documentation. We expect you to run the client communication yourself, lead discovery, shape and challenge requirements, and help design the solution together with the technical team — especially on our AI and fintech projects. You need to be technical enough to speak the same language as developers and architects, and to turn the client’s business need into something the team can actually build.
We enter projects two different ways. Often from scratch: no written product definition exists yet, and we author it with the client. Just as often by joining something already in flight: an existing backlog, someone else’s conventions, a deadline already running. Both ask the same thing of you — build the structure where there is none, and take the requirements to the point where a developer can build without guessing.
What you will do:
Drive the client communication — you don’t just take part in the meetings, you drive the discussion.
Lead discovery and refinement sessions with clients in English — you run them, you don’t take notes at them.
Shape and challenge requirements, and help design the solution together with the technical team.
Join running projects, map what already exists, and bring the documentation to a consistent, testable state.
Write specifications developers can build from: concise, testable acceptance criteria, no duplication, no invented facts.
Turn unknowns into open questions with named owners, and chase them down the cheapest route that can answer them.
Support scope and ROM estimation with explicit assumptions, dependencies and confidence levels.
Use AI as a full working instrument in your analysis, and take part in building AI-enabled solutions — verifying everything it produces before it reaches a client or a developer.
What we are looking for:
Strong client-facing experience — you have been the person the client talks to, not the person briefed afterwards.
Strong fintech / banking expertise — a deep understanding of financial products and processes, integrations and data flows: enough to ask the right questions, spot the risks and challenge what the client asks for.
An AI background — experience on projects where AI is part of the product, plus daily use of AI tools in your own analysis work, including a concrete example of catching a wrong AI output.
Technical enough to speak the same language as developers and architects.
5+ years as a Business Analyst / Systems Analyst in custom software development, including at least 2 years as the only analyst on a project.
Experience of both entries: starting a product from scratch, where the requirements had to be created rather than collected, and joining a project already in flight with documentation you did not write.
English B2+ (C1 preferred) — enough to facilitate a workshop with a client, not only to attend one.
Discipline in written specifications: testable acceptance criteria, and the judgement to cut what does not belong.
Confident daily use of Jira and Confluence; able to read designs in Figma.
The habit of asking the uncomfortable question a second time when the first one was brushed off.
Nice to have:
Pre-sale experience: scope shaping, assumptions, ROM estimates, proposal input.
Domains beyond fintech: healthcare, logistics, renewable energy.
BPMN / UML / ERD used as a means of agreement, not as a deliverable for its own sake.
Experience mentoring analysts or reviewing other people’s specifications.
How we work:
One department standard and one quality rubric — your work is measured against the same instrument as everyone else’s, and so is everyone else’s.
Decisions have named gates: AI drafts, a human decides, and it is written down who decided.
We fight documentation overload as a matter of policy. Shorter and test
