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
Procurement Systems Analyst (L2)
2-3 yearsSkills to master
- Independently resolving L1/L2 support issues, managing basic system configurations (e.g., updating approval chains), delivering user training, and taking ownership of routine system processes.
You're ready to move on when
- You're consistently resolving complex support tickets without needing escalation.
- You've successfully managed several small configuration changes from start to finish.
- Colleagues and managers frequently ask for your input on system-related questions.
- You've proactively identified and proposed solutions for minor system inefficiencies.
- 2
Experienced Procurement Analyst / Category Analyst with System Focus
3-5 yearsSkills to master
- Deep understanding of procurement processes from a user perspective, strong analytical skills (especially with spend data), experience with system reporting, and a keen interest in how technology can solve procurement problems.
You're ready to move on when
- You're the 'go-to' person in your category team for system-related questions or issues.
- You've actively participated in system implementation or enhancement projects from a business user's side.
- You've built complex reports using system data and identified areas for process improvement through that analysis.
- You're constantly thinking about how to automate manual procurement tasks.
- 3
IT Business Analyst (with Procurement Domain Experience)
3-4 yearsSkills to master
- Strong requirements gathering, process mapping, and stakeholder management skills from an IT perspective. Experience in translating business needs into technical specifications and working with development teams.
You're ready to move on when
- You've successfully delivered IT projects for procurement or finance functions.
- You're comfortable with technical documentation and system integration concepts.
- You have a solid understanding of the software development lifecycle.
- You can effectively bridge the gap between business users and technical teams.