Procurement Technology Specialist

Role Purpose & Context

Role Summary

The Procurement Technology Specialist is here to make sure our buying systems actually do what they're supposed to. Day-to-day, you'll be fixing little glitches, setting up new users, and tweaking the system so it fits how we work. Honestly, you're the person who stops people from pulling their hair out when Coupa or Ariba throws a wobbly. This role sits right at the heart of our procurement operations, bridging the gap between our buying teams and the tech that makes it all happen. You're translating what the business needs into system configurations. When you do this well, our teams can buy things quickly and compliantly, which means less hassle for everyone and better deals for us. If things go wrong, well, invoices get stuck, suppliers don't get paid, and people get really frustrated. That's why your work is so important. The real challenge here is dealing with those unexpected system quirks and making sure everyone, from the tech-savvy to the 'just make it work' crowd, can use our platforms. The reward? You get to see your work directly improve how people do their jobs, making a tangible difference to our efficiency and, frankly, our sanity.

Reporting Structure

• Reports to: Senior Procurement Technology Specialist
• Direct reports:
• Matrix relationships: Procurement Systems Analyst, P2P Specialist, S2P Specialist, Procurement Application Support,

Key Stakeholders

Internal:

• Procurement Operations team (they're your primary users)
• Accounts Payable (they need the invoices to flow smoothly)
• Finance team (they care about the numbers and compliance)
• Internal business users (anyone who needs to buy something)
• IT Support (you'll work closely with them on integrations)

External:

• S2P/P2P software vendors (like Coupa or SAP Ariba support)
• Other technology partners (for integration issues)

Organisational Impact

Scope: Your work directly impacts how smoothly our entire buying process runs. If you keep the systems humming, we save time, reduce errors, and keep our suppliers happy. Mess it up, and things grind to a halt, costing us money and goodwill. It's a pretty central role, even if you're not always in the spotlight.

Performance Metrics

Quantitative Metrics

1. Metric: Tier 1 Ticket Resolution Time
2. Desc: How quickly you close out those initial user support requests, like 'I can't log in' or 'My PO is stuck'.
3. Target: <8 business hours
4. Freq: Weekly review, monthly aggregate
5. Example: If a user raises a ticket at 10 AM on Monday, you'll aim to have it sorted by 6 PM that day, or at least have a clear plan of action communicated.
6. Metric: User Provisioning SLA
7. Desc: Making sure new users get access to the right procurement systems on time, with the correct permissions.
8. Target: 99% of requests completed within 24 hours
9. Freq: Monthly audit
10. Example: Someone new starts in Procurement on Monday; you'll have them set up in Coupa with their correct roles by Tuesday morning, ready to go.
11. Metric: Report Accuracy
12. Desc: The precision of the standard reports you pull or generate from our systems for internal teams.
13. Target: <1% error rate on standard monthly reports
14. Freq: Quarterly spot checks by your manager
15. Example: You pull a report on spend by category for Finance. We'll check a few lines to make sure the numbers match the source system and there aren't any weird data glitches.
16. Metric: System Uptime & Availability
17. Desc: The percentage of time our core procurement systems (Coupa, Ariba, CLM) are fully operational and accessible to users.
18. Target: 99.5% (excluding planned maintenance)
19. Freq: Monitored continuously by IT, reviewed monthly
20. Example: If Coupa goes down for 2 hours unexpectedly in a month, that's a problem. Your job is to help troubleshoot and get it back online quickly, working with IT and vendors.

Qualitative Metrics

1. Metric: User Satisfaction & Feedback
2. Desc: How happy our internal users are with the support you provide and the usability of our procurement systems.
3. Evidence: Positive feedback in ticket comments; users proactively coming to you for advice; fewer repeat issues from the same users; informal check-ins with key users.
4. Metric: Documentation Quality & Completeness
5. Desc: Keeping our user guides, FAQs, and internal process documents clear, up-to-date, and easy to understand.
6. Evidence: Users finding answers themselves in your documentation; new joiners getting up to speed quickly using your guides; your manager finding your process notes clear and concise during reviews.
7. Metric: Proactive Issue Identification
8. Desc: Spotting potential problems in the system or with user behaviour before they become big, hairy issues.
9. Evidence: You flag a recurring error pattern to your manager; you notice a user workaround that suggests a process flaw and propose a fix; you suggest a small system tweak that prevents future tickets.
10. Metric: Adherence to System Governance
11. Desc: Following our established rules and processes for system changes, master data updates, and user permissions.
12. Evidence: No unauthorised system changes; master data updates follow the correct approval flows; user access reviews are completed on time and accurately; audit trails show correct procedures were followed.

Primary Traits

• Trait: Process-Minded Problem Solver
• Manifestation: You're the kind of person who, when faced with a system error, immediately thinks, 'Okay, what's the sequence of events here?' You'll probably draw a little flowchart in your head (or on paper) to figure out where things went wrong. You don't just fix the symptom; you keep asking 'why' until you've found the actual root cause, making sure it doesn't happen again. You love translating messy human requests into logical, step-by-step system configurations.
• Benefit: Our procurement systems are all about structured processes. If you configure something illogically, or only fix the surface problem, it'll just break again next week. That means more user frustration, more tickets, and potentially invoices getting stuck. We need someone who can think like the system, ensuring our workflows are robust and reliable.
• Trait: Patient Translator
• Manifestation: You can calmly talk someone through a complicated technical issue, even when they're clearly stressed or not very tech-savvy. When a user calls in a panic because 'Coupa won't let me buy my thing!', you listen first, understand their actual problem, and then guide them step-by-step to a solution without making them feel silly. You're happy to write out clear, simple instructions for people who need them.
• Benefit: You're the bridge between the tech and the people. If you get impatient or use too much jargon, users will give up, bypass the system, or just stop asking for help. That leads to poor system adoption, rogue spending, and a perception that our tech is a blocker. Your ability to explain things clearly and empathetically is crucial for getting people to actually use the systems correctly.
• Trait: Detail-Oriented Guardian
• Manifestation: You're the one who spots the single incorrect GL code in a list of a hundred before it messes up the integration. You'd notice if a new permission setting accidentally gave someone approval authority they shouldn't have. Before we roll out any new workflow, you'll insist on testing every single possible scenario, just to make sure there are no hidden surprises. You're meticulous, and you pride yourself on catching those tiny things that others miss.
• Benefit: In procurement tech, tiny mistakes can have huge consequences. A misplaced decimal, a wrong approval threshold, or a misconfigured tax code can lead to thousands of pounds in misallocated spend, compliance breaches, or delayed payments. You're the last line of defence against these costly system errors. Your attention to detail directly protects the business from financial and operational headaches.

Supporting Traits

• Trait: Inquisitive
• Desc: You're naturally curious about why things work the way they do and always looking for ways to make them better with technology. You don't just accept 'that's how we've always done it'.
• Trait: Collaborative
• Desc: You'll work with all sorts of people—Finance, Accounts Payable, IT, and various business teams. You're good at listening to different perspectives and finding common ground, even when priorities clash.
• Trait: Resilient
• Desc: Sometimes systems go down, users get frustrated, and you'll face a bit of pressure. You're able to keep a cool head, troubleshoot effectively, and bounce back from criticism, understanding it's usually about the system, not you.

Primary Motivators

1. Motivator: Solving Puzzles
2. Daily: Every system error or user query is a puzzle to you. You love digging into the root cause, tracing workflows, and finding that 'aha!' moment when you figure out the solution. It's satisfying to untangle a complex problem.
3. Motivator: Helping People
4. Daily: You genuinely enjoy making things easier for others. When a user thanks you for quickly resolving their issue or for patiently explaining a process, that's a real win for you. You like being the person who can unblock someone's day.
5. Motivator: Seeing Systems Work Smoothly
6. Daily: There's a deep satisfaction in knowing the systems you manage are running efficiently, that data is flowing correctly, and that processes are being followed. You like order and predictability in the tech world.

Potential Demotivators

Honestly, this job isn't always glamorous. If you need every day to be perfectly smooth and predictable, you might struggle. There's a fair bit of grunt work, and sometimes you'll feel like a firefighter.

Common Frustrations

1. **Garbage In, Garbage Out:** You'll spend a fair chunk of your time cleaning up messy supplier master data—think duplicates, outdated info, missing details—because frankly, no one else has properly owned it. It's tedious, but essential.
2. **The Rogue Spender:** Dealing with the fallout when a senior leader bypasses the system entirely for a big purchase, then expects you to 'just make it work' for the invoice. It's a political minefield, and you'll often be caught in the middle.
3. **Integration Nightmares:** That sinking feeling on a Monday morning when you discover the ERP integration failed silently over the weekend, leaving you with a backlog of hundreds of un-synced invoices. It's a race against time to fix it.
4. **'Can you just...':** Stakeholders will constantly ask for 'one small change' to a global workflow that, in reality, would mean weeks of re-testing and could unravel all our standardised processes. Saying no, or explaining why, can be exhausting.
5. **The Scapegoat:** Sometimes, you'll be blamed for a late payment to a critical supplier, even when the real reason was a business approver sitting on the Purchase Order for two weeks. It's frustrating when you know the truth.
6. **License Police:** You'll probably end up chasing people to justify their expensive software licenses, knowing full well that half of them aren't even being used. It's a constant battle to reduce 'shelfware' and save money.

What Role Doesn't Offer

1. A completely predictable, routine day – expect curveballs.
2. The chance to build complex new systems from scratch (that's more for the Lead/Architect level).
3. A role where you're always making the strategic decisions (you'll be executing and proposing, mostly).
4. A job where you never have to deal with frustrated users or messy data.

ADHD Positives

1. The varied nature of support tickets and troubleshooting can keep things fresh and engaging, as you're constantly tackling new problems.
2. The need for quick, on-the-spot problem-solving can be a great fit for rapid ideation and hyperfocus on urgent issues.
3. The satisfaction of quickly resolving a user's problem can provide immediate positive feedback.

ADHD Challenges and Accommodations

1. Repetitive data cleaning or documentation tasks might be challenging. We can help by breaking these into smaller chunks or pairing you with someone for accountability.
2. Prioritising multiple 'urgent' user requests can be tough. We'll work with you on clear prioritisation frameworks and tools like Jira to manage your queue.
3. Attention to detail is critical, so we'll provide checklists and templates to ensure important steps aren't missed, especially during configurations.

Dyslexia Positives

1. Strong problem-solving and visual thinking skills are highly valued, especially when mapping out complex system workflows or data flows.
2. Excellent verbal communication for explaining technical concepts to non-technical users can be a real strength.
3. The ability to see the 'big picture' of how different system components fit together can be very helpful in troubleshooting.

Dyslexia Challenges and Accommodations

1. Reading and writing extensive technical documentation or configuration guides might be slower. We can offer tools like text-to-speech software and provide templates with clear formatting.
2. Proofreading configurations or data entries for tiny errors can be difficult. We encourage using spell-checkers, grammar tools, and peer reviews for critical tasks.
3. We're happy to provide coloured overlays or specific fonts if that helps with readability on screen.

Autism Positives

1. A strong preference for logical, structured systems and processes aligns perfectly with configuring procurement technology.
2. Exceptional attention to detail, especially for spotting inconsistencies or errors in data and configurations, is a huge asset.
3. The ability to focus deeply on specific tasks, like troubleshooting a complex integration, can lead to highly effective problem-solving.

Autism Challenges and Accommodations

1. Unexpected changes to plans or urgent, disruptive requests can be challenging. We aim for clear communication about changes and provide as much notice as possible.
2. Navigating social dynamics with frustrated users or conflicting stakeholder priorities might be stressful. We can provide scripts for common interactions and offer quiet spaces for focused work.
3. Sensory overload from open-plan offices can be an issue. We offer noise-cancelling headphones and flexibility to work in quieter areas or from home when possible.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Procurement Technology Specialist (Mid-Level)
2. Responsibilities: Take ownership of a specific procurement module (like Invoicing or Supplier Onboarding) within our S2P suite (Coupa, Ariba, etc.). This means you're the first point of contact for issues and basic configurations.
3. Independently troubleshoot and resolve Tier 1 and 2 user support tickets. Think 'My PO is stuck' or 'How do I find this report?' You'll be the hero unblocking people's days.
4. Configure basic system workflows and settings. This could be setting up a new approval path for a specific type of spend or tweaking a user's permissions. You'll work within established guidelines.
5. Create and maintain clear, easy-to-understand user documentation, FAQs, and training materials. You'll make sure people can help themselves, reducing the number of basic questions.
6. Run standard system reports and dashboards, usually in Power BI or Tableau, to help our Procurement and Finance teams understand spend patterns or system usage. You'll make sure the data is accurate.
7. Help onboard new suppliers into our system, ensuring all their details are correct and that they're set up for compliant purchasing. This means making sure their master data is clean.
8. Work with the IT team to test system integrations (e.g., between Coupa and SAP S/4HANA) after updates or changes, making sure data flows correctly and nothing breaks.
9. Supervision: You'll have weekly check-ins with your Senior Procurement Technology Specialist. For routine tasks, you'll work independently, but you'll always have someone to bounce ideas off or escalate novel problems to. We trust you to get on with it, but we're here if you get stuck.
10. Decision: You can make routine decisions within established guidelines, like how to best resolve a common user error or which template to use for a new report. Anything outside of standard operating procedure, or that impacts system-wide settings, you'll need to discuss with your Senior Specialist or Manager. Think of it as: you fix the small fires, they help you with the big ones.
11. Success: You'll be doing well if users are happy with your support, tickets are resolved quickly, and your documentation means fewer repeat questions. Basically, if you're making the system feel less like a headache and more like a help.

Decision-Making Authority

• Type: User Access & Permissions
• Entry: Escalate all requests for new user roles or changes to existing permissions to a senior team member for review and approval.
• Mid: Independently provision standard user roles based on approved templates. Escalate requests for custom roles or high-level access.
• Senior: Design and approve new standard user roles. Authorise changes to complex permission sets and troubleshoot access issues.
• Type: System Configuration Changes (e.g., workflow updates)
• Entry: Do not make any configuration changes. Document proposed changes and submit for review.
• Mid: Implement minor configuration changes (e.g., updating approval thresholds within defined limits, adding a new field to a form) after manager approval. Escalate all major changes.
• Senior: Design and implement complex workflow changes. Propose and lead major system configuration projects, with final approval from leadership.
• Type: Troubleshooting & Problem Resolution
• Entry: Follow documented troubleshooting steps for common issues. Escalate anything not covered by existing guides.
• Mid: Independently diagnose and resolve most Tier 1 and 2 system issues using your knowledge and available resources. Escalate complex or critical issues.
• Senior: Lead the diagnosis and resolution of critical system incidents. Act as the primary technical liaison with vendor support for major outages or bugs.
• Type: Master Data Management (Supplier/Item)
• Entry: Perform data entry for new suppliers/items following strict guidelines. Flag any data quality issues.
• Mid: Independently manage the creation and updates of master data, ensuring data quality and adherence to governance rules. Identify and propose solutions for data inconsistencies.
• Senior: Define and enforce master data governance policies. Lead initiatives to improve data quality and standardisation across the organisation.

Competency Requirements

Foundation Skills (Transferable)

These are the fundamental skills that underpin everything you'll do. They're about how you think, how you talk to people, and how you approach challenges. We're looking for someone who can communicate clearly, solve problems logically, and isn't afraid to adapt when things change.

• Category: Communication & Collaboration
• Skills: Active Listening: You'll need to really hear what users are saying, not just what they think they're saying, to get to the root of their problem.
• Clear Explanations: Translating complex technical jargon into plain English for non-techy colleagues is crucial. Think 'explaining it to your nan'.
• Written Communication: Writing clear, concise emails, documentation, and ticket updates so everyone knows what's going on.
• Cross-functional Teamwork: Working effectively with Finance, AP, IT, and other business teams, even when they have different priorities.
• Category: Problem-Solving & Analytical Thinking
• Skills: Root Cause Analysis: Not just fixing the symptom, but digging deeper to find out *why* something broke in the first place.
• Logical Reasoning: Being able to follow a process step-by-step, identifying where the logic might be failing in a system workflow.
• Data Interpretation: Looking at system reports or error logs and understanding what the numbers or messages are actually telling you.
• Troubleshooting Methodologies: Having a structured approach to figuring out what's wrong when a system isn't behaving.
• Category: Adaptability & Initiative
• Skills: Managing Changing Priorities: You'll often have multiple 'urgent' requests. Being able to re-prioritise and communicate changes is key.
• Learning Agility: Our tech stack evolves, so you'll need to pick up new tools and features quickly.
• Proactive Issue Resolution: Not waiting for problems to blow up, but spotting potential issues and tackling them before they become critical.
• Self-Organisation: Keeping track of your tasks, tickets, and projects without constant oversight.

Functional Skills (Role-Specific Technical)

These are the specific skills and knowledge you'll need to do the job well, from understanding procurement processes to using our key software.

Technical Competencies

• Skill: Source-to-Pay (S2P) Process Optimisation
• Desc: You'll need a solid grasp of the entire procurement lifecycle, from how we source suppliers and sign contracts, right through to buying things and paying invoices. You should be able to spot inefficiencies and suggest how technology could make it smoother.
• Level: Intermediate
• Skill: Supplier & Item Master Data Management (MDM)
• Desc: Understanding why clean, accurate supplier and item data is so important. You'll know how to create and maintain these records, making sure we don't end up with duplicates or outdated information. It's the foundation for everything else.
• Level: Intermediate
• Skill: Category Management Enablement
• Desc: You'll learn how different types of spend (like IT software vs. office supplies) have different buying processes. You'll help configure our systems to support these specific needs, like setting up different catalogues or approval forms.
• Level: Basic
• Skill: Change Management & User Adoption
• Desc: While not leading big projects, you'll play a part in helping users get on board with new system features. This means helping with training, answering questions, and generally being a friendly face for new tech.
• Level: Basic
• Skill: Agile Methodology for System Enhancement
• Desc: We use Agile principles (sprints, backlogs) for our system improvements. You'll need to understand how this works, helping to track tasks, contribute to user stories, and participate in sprint reviews.
• Level: Basic

Digital Tools

• Tool: Coupa or SAP Ariba (S2P/P2P Suites)
• Level: Intermediate
• Usage: You'll be doing user administration, configuring basic workflows (like approval paths), generating standard reports, and troubleshooting common user errors. You're the daily expert on how these systems work for our users.
• Tool: SAP S/4HANA or Oracle NetSuite (ERP Systems)
• Level: Basic
• Usage: You'll need to understand how procurement data (like Purchase Orders and invoices) flows into our core financial system. This means pulling basic reports and validating that data has replicated correctly, especially for troubleshooting.
• Tool: Power BI or Tableau (Data Analytics)
• Level: Intermediate
• Usage: You'll build and maintain dashboards and reports using data from our procurement systems. You'll use pre-defined data sources to give our teams insights into spend and system usage.
• Tool: Microsoft Excel
• Level: Intermediate
• Usage: You'll use Excel for data manipulation, quick analysis, and cleaning up master data. Think VLOOKUPs, PivotTables, and general data organisation.
• Tool: DocuSign CLM or Icertis (Contract Lifecycle Management)
• Level: Basic
• Usage: You'll manage user permissions and templates within our CLM system. This means tracking contract status, running renewal reports, and helping users find the right contract documents.
• Tool: EcoVadis or Dun & Bradstreet (Supplier Intelligence)
• Level: Basic
• Usage: You'll use these platforms to pull basic supplier risk reports during the onboarding process or when a team needs to understand a supplier's background.
• Tool: Jira or ServiceNow (Collaboration/PM)
• Level: Intermediate
• Usage: You'll manage your support tickets and tasks in these systems, updating their status and documenting resolutions. You'll also use them to track progress on smaller system enhancement projects.
• Tool: Confluence (Documentation)
• Level: Intermediate
• Usage: You'll create and update our internal knowledge base, writing clear process guides and FAQs for our procurement systems. You'll make sure everyone can find the answers they need.

Industry Knowledge

• Area: Source-to-Pay (S2P) and Procure-to-Pay (P2P) Cycle
• Desc: A solid understanding of the full lifecycle: from sourcing, contracting, requisitioning, ordering, receiving, invoicing, and payment. You'll know what a '3-Way Match' is and why it matters.
• Area: Supplier Relationship Management (SRM) Basics
• Desc: Understanding the importance of managing supplier information, performance, and risk within our systems.
• Area: Basic Financial Concepts in Procurement
• Desc: Knowing what a General Ledger (GL) code is, cost centres, and how procurement activities impact the company's finances.

Regulatory Compliance Regulations

• Reg: GDPR (General Data Protection Regulation)
• Usage: Understanding how to handle supplier and user data responsibly within our systems, especially when setting up new accounts or managing personal information.
• Reg: Internal Audit & Compliance Policies
• Usage: Knowing our company's specific rules around procurement processes, approval limits, and data security. You'll ensure system configurations support these policies, like 'No PO, No Pay'.

Essential Prerequisites

• Roughly 2-3 years of hands-on experience working with procurement systems (like Coupa, Ariba, or similar) in a support or configuration role.
• A good grasp of core procurement processes – you know your Purchase Orders from your invoices.
• Demonstrable experience in troubleshooting system issues and helping users, even if it was just for one specific platform.
• The ability to clearly explain technical steps to non-technical people, usually in a calm and patient way.
• Experience creating simple reports or dashboards, ideally using tools like Power BI or Tableau, or at least being very comfortable with Excel for data analysis.

Career Pathway Context

Think of these as the building blocks. You don't need to be an expert in everything, but having a solid foundation here means you're ready to jump in and start making a difference pretty quickly. If you've been an Associate Procurement Systems Analyst or an AP Specialist with a strong tech bent, you're probably in a good spot.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: Prompt Engineering & LLM Integration
• Why: Honestly, competitors are already using tools like ChatGPT and Claude to draft reports in minutes that used to take hours. Analysts who figure this out will simply outproduce their peers. It's not future-state; it's happening now.
• Concepts: [{'concept_name': 'Context Windows & Token Limits', 'description': "Understanding how much information an AI can 'remember' at once and how that impacts what you can ask it to do."}, {'concept_name': 'Temperature Settings', 'description': 'Knowing when to ask an AI for creative ideas (high temperature) versus factual summaries (low temperature) for different tasks.'}, {'concept_name': 'RAG (Retrieval Augmented Generation)', 'description': 'Learning how to get AI to use our own internal documents and data, not just its general knowledge, for more accurate answers.'}, {'concept_name': 'Output Validation & Hallucination Detection', 'description': "Crucially, knowing how to check if the AI's answer is actually correct and spotting when it's just making things up."}]
• Prepare: This week: Start using tools like ChatGPT or Claude for drafting emails, summarising long documents, or even brainstorming solutions to system problems. Just get comfortable with it.
• This month: Experiment with using AI to generate first drafts of user documentation or FAQs for a new system feature. See how much time it saves.
• Month 2: Explore how to connect AI to a simple data source (like an Excel sheet) to ask questions about the data, even if it's just a basic experiment.
• Month 3: Share your findings and any productivity hacks with your team. Show them what's possible.
• QuickWin: Start using AI to draft your daily emails or summarise meeting notes today. It's low-risk, high-reward, and you don't need anyone's permission to try it out.

Advancing Technical Skills

• Skill: Advanced S2P/P2P Configuration
• Why: As our business grows, our procurement processes become more complex. You'll need to move beyond basic workflows to designing more sophisticated approval matrices, conditional routing, and advanced form customisations.
• Concepts: [{'concept_name': 'Conditional Logic', 'description': 'Building workflows where approvals change based on spend amount, category, or user role.'}, {'concept_name': 'Integration Touchpoints', 'description': 'Understanding how system configurations impact data flow to and from other systems (e.g., ERP).'}, {'concept_name': 'Master Data Governance Rules', 'description': 'Designing system rules that enforce data quality and consistency for suppliers and items.'}]
• Prepare: This quarter: Volunteer to shadow your Senior Specialist on a complex configuration project, even if it's just for observation.
• Next quarter: Take an advanced configuration course offered by Coupa or Ariba (we'll support this).
• Month 6: Propose and lead a small, complex workflow optimisation project under supervision.
• Ongoing: Regularly review vendor release notes for new configuration capabilities and experiment in a sandbox environment.
• QuickWin: Ask your Senior Specialist if you can take on configuring a slightly more complex approval workflow for a new department or spend category.
• Skill: Data Cleansing & Transformation (Power Query/SQL)
• Why: You're already building reports, but the data rarely comes in perfectly clean. To create truly reliable insights, you'll need to get better at preparing the data yourself, rather than relying on others.
• Concepts: [{'concept_name': 'ETL Principles', 'description': 'Understanding Extract, Transform, Load processes for data pipelines.'}, {'concept_name': 'Power Query M Language', 'description': 'Learning the language behind Power Query for advanced data transformations in Excel and Power BI.'}, {'concept_name': 'Basic SQL for Data Extraction', 'description': 'Being able to write simple SQL queries to pull data directly from system databases when needed.'}]
• Prepare: This month: Start using Power Query for all your Excel data cleaning tasks, even simple ones.
• Next quarter: Take an online course on Power Query or basic SQL for data analysts.
• Month 6: Work with our Data team to understand how they clean and prepare data, and see if you can apply those methods.
• Ongoing: Look for opportunities to automate data cleansing steps in your reporting processes.
• QuickWin: For your next report, try to do all the data cleaning and shaping directly in Power Query within Excel or Power BI, rather than manual steps.

Education Requirements

• Level: Minimum
• Req: A Bachelor's degree in Business, Information Technology, Supply Chain Management, or a related field.
• Alts: We're flexible here. If you've got 4+ years of direct, relevant experience in a procurement systems role, especially with a strong track record, that's absolutely fine as an equivalent. We care more about what you can do than where you went to uni.
• Level: Preferred
• Req: A degree with a focus on business analytics, systems administration, or process improvement.
• Alts: Relevant professional certifications (see below) can also make up for a less specialised degree.

Experience Requirements

You'll need roughly 2-5 years of hands-on experience working directly with procurement technology platforms. This isn't about just being a user; it's about having configured, supported, or troubleshooted these systems. Experience in a P2P or S2P focused role, or as a systems administrator for a relevant platform, would be ideal. We're looking for someone who's seen a few different scenarios and knows their way around the backend a bit.

Preferred Certifications

• Cert: Coupa Certified Administrator
• Prod: Coupa
• Usage: Shows you've got a solid understanding of how to manage and configure our primary S2P platform, which is a huge plus for us.
• Cert: SAP Ariba Associate Certification (e.g., Procurement or Sourcing)
• Prod: SAP
• Usage: If you've worked with Ariba, this demonstrates a good foundational knowledge of another major procurement suite, which is valuable for future projects or if we use multiple systems.
• Cert: Lean Six Sigma Yellow Belt
• Prod: Various
• Usage: This shows you understand process improvement methodologies, which is really helpful for optimising our procurement workflows and system configurations.
• Cert: Microsoft Certified: Data Analyst Associate (Power BI)
• Prod: Microsoft
• Usage: Proves your ability to build effective dashboards and reports, which is a key part of how we measure system performance and procurement insights.

Recommended Activities

• Regularly engage with online forums and communities for procurement technology (e.g., Coupa Community, Ariba Network) to learn from peers and stay updated.
• Attend webinars and virtual conferences hosted by our software vendors to learn about new features and best practices.
• Take online courses (e.g., on LinkedIn Learning, Udemy, Coursera) in areas like advanced Excel, Power BI, or basic SQL to deepen your data skills.
• Seek out opportunities to shadow senior team members on more complex configuration or integration projects to learn by doing.

Career Progression Pathways

Entry Paths to This Role

• Path: Associate Procurement Systems Analyst (L1)
• Time: 1-2 years
• Path: Accounts Payable (AP) Specialist with Tech Focus
• Time: 2-3 years
• Path: Procurement Coordinator / Operations Support
• Time: 2-4 years

Career Progression From This Role

• Pathway: Senior Procurement Technology Specialist (L3)
• Time: 3-5 years in this role

Long Term Vision Potential Roles

• Title: Lead Procurement Systems Architect (L4)
• Time: 5-8 years from this role
• Title: Manager, Procurement Technology & Operations (L5)
• Time: 8-12 years from this role
• Title: Director, Source-to-Pay Transformation (L6)
• Time: 12-16 years from this role

How Zavmo Delivers This Role's Development

DISCOVER Phase: Skills Gap Analysis

Zavmo maps your current competencies against all requirements in this job description through conversational assessment. We evaluate your foundation skills (communication, strategic thinking), functional skills (CRM expertise, negotiation), and readiness for career progression.

Output: Personalised skills gap heat map showing strengths and priorities, estimated time to competency, neurodiversity accommodations.

DISCUSS Phase: Personalised Learning Pathway

Based on your DISCOVER results, Zavmo creates a personalised learning plan prioritised by impact: foundation skills first, then functional skills. We adapt to your learning style, pace, and neurodiversity needs (ADHD, dyslexia, autism).

Output: Week-by-week schedule, each module linked to specific job responsibilities, checkpoints and milestones.

DELIVER Phase: Conversational Learning

Learn through conversation, not boring modules. Zavmo uses 10 conversation types (Socratic dialogue, role-play, coaching, case studies) to build competence. Practice difficult QBR presentations, negotiate tough renewals, and handle churn conversations in a safe AI environment before facing real clients.

Example: "For 'Stakeholder Mapping', Zavmo will guide you through analysing a complex enterprise account, identifying key decision-makers, and building an engagement strategy."

DEMONSTRATE Phase: Competency Assessment

Zavmo automatically builds your evidence portfolio as you learn. Every conversation, practice scenario, and application example is captured and mapped to NOS performance criteria. When ready, your portfolio supports OFQUAL qualification claims and demonstrates competence to employers.

Output: Competency matrix, evidence portfolio (downloadable), qualification readiness, career progression score.