The pathway
How you actually get there, here
How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.
- 1
Requirements Analyst (L2) to Senior Requirements Management Advisor (L3)
2-3 years as an L2Skills to master
- Independent project ownership, advanced elicitation, conflict resolution, initial mentorship of juniors, proactive problem framing.
You're ready to move on when
- Consistently delivering high-quality requirements for complex single projects without close supervision.
- Demonstrating initiative in identifying and solving problems beyond your immediate scope.
- Successfully facilitating small workshops or leading specific sections of larger projects.
- Receiving positive feedback from stakeholders on your clarity and ability to build consensus.
- 2
Experienced Business Analyst from another Industry to Senior Requirements Management Advisor (L3)
5-8 years in a similar BA roleSkills to master
- Adaptation to internal consulting context, rapid domain learning, navigating internal politics, understanding our tech stack and methodologies.
You're ready to move on when
- A strong portfolio of requirements work from a previous role, demonstrating similar complexity and impact.
- Proven ability to quickly learn new business domains and technical environments.
- Excellent communication and stakeholder management skills, transferable to an internal context.
- A clear desire to work in a consulting-style role, driving change and solving diverse problems.
- 3
Project Manager (Junior/Mid-level) to Senior Requirements Management Advisor (L3)
3-5 years as a PMSkills to master
- Deep dive into requirements elicitation and documentation, shifting from 'how' to 'what' and 'why', structured analysis techniques, process modelling.
You're ready to move on when
- A strong interest and aptitude for the 'discovery' and 'definition' phases of projects.
- Experience managing project scope and dealing with change requests, understanding the impact of poor requirements.
- Demonstrated ability to communicate with both business and technical teams.
- A desire to specialise in the upstream phases of project delivery.