The Coders Guild offered clear and practical insights into generative AI, which we’ve started applying in our business. The course was well-structured and relevant to our needs, making the learning process straightforward and effective.
The Coders Guild led the research and development that produced the UK’s first Level 4 AI and Automation apprenticeship standard — built with Skills England and the Alan Turing Institute after a year of research into what SMEs actually need from AI training. We’re not reselling someone else’s framework. We designed it, and we’re running the first cohorts now.
Our trainers work in the field. Every programme is delivered by industry practitioners — people using these tools in real businesses, not academics teaching from a curriculum. That means what gets taught reflects how AI and automation work in practice, not how they looked two years ago.
Built for smaller businesses. Most AI training is designed with enterprise budgets and infrastructure in mind. Ours isn’t. Everything we do is built around the constraints and opportunities of SMEs — businesses where one capable person can genuinely change how the whole organisation works.
Pick the one that matches where you are. If it’s not obvious, tell us what you’re working with and we’ll point you right.
Spend, policy, risk, who on the team needs what. AI for Leaders is six weeks that take you from using the tools to leading the doing.
Grow your own AI capability with fully funded, hands-on training. Your people learn on real work in your business, on the UK’s Level 4 AI and Automation apprenticeship, the standard we created with Skills England.
Closed cohorts on your dates, up to twelve people, built around how your business actually works. One conversation tells you what fits.
Want to go deep yourself? Our courses run from Foundations through Intermediate to Advanced. See them all below.
“Businesses need outputs, not certifications. That’s why our training returns value fast: people do the work on your business, instead of watching videos and hoping some of it sticks.”
Crispin Read – who led the R&D on the UK’s new Level 4 AI and Automation standard with Skills England
Every business is different. If you’re unsure which option works best, or you need something more tailored to your specific challenges, fill in the form and we’ll send you some options and arrange a call.
"*" indicates required fields
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Product work is about understanding what users need, designing solutions that work for them, and ensuring teams build the right things. Whether you’re managing digital products, designing user experiences, improving customer journeys, or analysing business requirements, these roles bridge the gap between users, business goals, and technical delivery.
Every business is different. If you’re unsure which option works best, or you need something more tailored to your specific challenges, fill in the form and we’ll send you some options and arrange a call.
"*" indicates required fields
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
No, though technical understanding helps. Many successful product managers came from non-technical backgrounds – business, design, marketing, operations.
What matters more than technical background is ability to:
That said, technical literacy helps you:
You don’t need to code. But understanding basic technical concepts, learning engineering terminology, and showing genuine interest in how things work builds credibility with technical teams.
Some product areas benefit more from technical background – developer tools, infrastructure products, highly technical B2B products. Consumer products often value business and user understanding over technical depth.
These roles overlap but have different emphases:
Product Manager: Focuses on product strategy, vision, market understanding, and business outcomes. Works across multiple teams and stakeholders. Strategic and outward-facing role. Decides what should be built and why.
Product Owner: Focuses on backlog management, sprint planning, and working closely with development team. Tactical role within Agile framework. Ensures development team understands what to build and accepts completed work.
In practice:
Product Owner is often easier entry point into product work because it’s more defined within Agile framework and requires less strategic responsibility initially. Many people start as Product Owner and progress to Product Manager.
No. While design degrees help, many successful UX designers don’t have formal design education.
UX design is relatively new field – formal education programs are still developing. Many working UX designers are self-taught or transitioned from other fields like graphic design, psychology, human-computer interaction, or even completely unrelated backgrounds.
What matters more than degrees:
Many successful UX designers built portfolios through:
That said, for some employers, particularly larger corporates, degrees help get past initial screening. But smaller companies and startups focus more on portfolio and capability.
Coding skills are helpful but not essential for most product management roles:
You don’t need to code if you:
Coding helps if you want to:
More valuable than coding:
Some technical product managers have engineering backgrounds and code. But many successful product managers never wrote production code. What matters is technical literacy and ability to work effectively with technical teams, not coding ability.
If you want to develop technical skills, learning SQL and understanding how web applications work matters more than learning to build full applications.
Yes, this is common career transition. Business Analysts have many transferable skills relevant to product management:
Skills BAs bring:
Skills to develop:
Making the transition:
Many organisations have both BAs and PMs. Demonstrating product thinking in your BA work can lead to opportunities to transition internally.
UX (User Experience) and UI (User Interface) design are related but distinct:
UX Design focuses on:
UI Design focuses on:
Analogy: UX is the blueprint and structural design of a house (does it flow well, are rooms in right places?). UI is the interior design and decoration (does it look good, feel inviting?).
In practice:
Both matter. Products need to work well (UX) and look good (UI). Best designers understand both but may specialise in one area.
Building portfolio without product role is challenging but achievable:
For Product Management portfolios:
For UX portfolios:
What makes portfolios strong:
Yes, though success varies by organisation and seniority:
Remote works well for:
Remote is harder for:
Hybrid often works best: Remote for focused work like roadmapping, documentation, analysis. In-person for workshops, key stakeholder meetings, team building, discovery work.
Product management is collaboration-heavy. Digital tools enable remote collaboration, but some organisations believe product work benefits from in-person interaction. This varies significantly by company culture.
Many product managers now work fully remote successfully. But it requires deliberate effort to build relationships, influence stakeholders, and maintain connection to users and teams.
This is false choice – good product work balances both:
User needs matter because:
Business goals matter because:
The art of product work is finding intersection:
Pure user advocacy without business reality leads to products that delight users but don’t make money. Pure business focus without user needs creates products nobody wants. Great product managers navigate tension between both, finding solutions that work for users and business.
When user needs and business goals conflict, best product managers are honest about trade-offs rather than pretending conflict doesn’t exist. Sometimes you serve business goals first. Sometimes user needs take priority. Good product thinking acknowledges both rather than defaulting to one.
This is classic catch-22 of product work. Here’s how to demonstrate product capability without product title:
Show product thinking in current role:
Build portfolio showing capability:
Contribute to product discussions:
Leverage transferable experience:
Start with adjacent roles:
Nobody starts with product experience. Everyone’s first product role requires someone taking chance on them. Make that easier by demonstrating product thinking through whatever opportunities you have.
Product work encompasses several related disciplines that all focus on creating digital products and services that solve real problems for users while meeting business objectives.
Product managers own the vision and strategy for products. They decide what gets built, prioritise features, work with stakeholders to define requirements, and coordinate teams to deliver products that users want and businesses need. Product owners do similar work in Agile environments, managing backlogs, writing user stories, and working closely with development teams.
UX designers focus on how products work – the flows, interactions, and interfaces that make products usable and effective. They research user needs, design solutions, create prototypes, and test designs with users. The goal is products that people can actually use without frustration or confusion.
Customer experience (CX) professionals look at the entire journey customers have with an organisation – not just individual products but the full experience across touchpoints. They map customer journeys, identify pain points, and design improvements that make the overall experience better.
Business analysts bridge business stakeholders and technical teams. They gather requirements, document processes, analyse business problems, and help ensure what gets built actually solves the problems organisations face. BAs translate business needs into specifications that development teams can work with.
Service designers take a holistic view of services – both digital and physical touchpoints. They design end-to-end service experiences, considering not just user interfaces but also operational processes, staff interactions, and organisational capabilities needed to deliver services effectively.
These roles overlap significantly. Product managers need to understand UX. UX designers need to understand business requirements. BAs need to understand user needs. In smaller organisations, one person might do multiple roles. In larger organisations, roles are more specialised with clear boundaries.
What connects these disciplines is focus on users and outcomes rather than just features and technical implementation. They all involve understanding problems deeply, designing solutions thoughtfully, and working collaboratively with diverse stakeholders to deliver value.
Product work exists across every sector now. Technology companies pioneered these roles, but healthcare, financial services, retail, government, education, and manufacturing all need people who can design and manage digital products and services. Digital transformation means nearly every organisation needs product capabilities.
Product work requires combining user research, strategic thinking, design skills, and stakeholder management:
User research methods: Conducting interviews, usability testing, surveys, observations. Understanding how to gather qualitative and quantitative insights about user needs and behaviour.
Creating research plans: Defining research questions, choosing appropriate methods, recruiting participants, structuring research to get useful insights.
Synthesising research: Taking raw research data and finding patterns, themes, and insights. Creating personas, journey maps, and other artifacts that communicate user understanding.
Continuous discovery: Ongoing conversation with users rather than one-off research projects. Building habits of regularly talking to users and learning from data.
Product vision: Defining what the product should become. Creating compelling vision that aligns stakeholders and guides decisions.
Strategy development: Setting product direction, identifying market opportunities, defining competitive positioning, making build vs buy decisions.
Roadmapping: Planning what to build when, balancing short-term needs with long-term vision, communicating plans to stakeholders.
Prioritisation: Deciding what features to build next. Using frameworks like RICE, value vs effort, or weighted scoring. Making trade-offs between competing priorities.
Business case development: Articulating why something should be built, expected benefits, costs, and risks. Building compelling cases for investment.
Requirements gathering: Discovering what stakeholders need through interviews, workshops, observation. Going beyond what people say they want to understand underlying needs.
User stories: Writing effective user stories that describe value from user perspective. Understanding acceptance criteria and definition of done.
Specification writing: Documenting requirements clearly enough for development teams to build. Balancing detail with flexibility.
Business process mapping: Understanding and documenting current state processes. Identifying improvement opportunities and designing future state processes.
Information architecture: Organising information and functionality logically. Creating structures that make sense to users.
User flows: Mapping how users move through products to accomplish tasks. Identifying friction points and optimising flows.
Wireframing and prototyping: Creating low and high-fidelity mockups of designs. Building interactive prototypes to test concepts with users.
Interaction design: Designing how interfaces respond to user actions. Creating intuitive interactions that feel natural.
Visual design basics: Understanding typography, colour, layout, hierarchy. You don’t need to be graphic designer, but understanding design principles helps.
Design systems: Understanding component libraries, design patterns, and consistency across products. Working within or contributing to design systems.
Usability testing: Testing designs with real users. Observing where people struggle, what confuses them, what works well.
A/B testing: Testing different versions of designs to see which performs better. Understanding statistical significance and interpreting results.
Analytics interpretation: Using quantitative data to understand how people use products. Identifying drop-off points, popular features, user behaviour patterns.
Accessibility: Designing for users with disabilities. Understanding WCAG standards, testing with assistive technologies, inclusive design principles.
Journey mapping: Mapping customer experiences across touchpoints over time. Identifying moments that matter and pain points.
Service blueprinting: Documenting entire service delivery including frontstage, backstage, and support processes.
Touchpoint design: Designing consistent experiences across channels – digital, physical, human interaction.
Omnichannel thinking: Understanding how experiences flow between channels. Designing for channel switching and continuity.
Stakeholder identification and analysis: Understanding who has interest or influence in product. Managing different stakeholder needs and expectations.
Building consensus: Getting diverse stakeholders to agree on direction. Navigating politics and competing interests.
Executive communication: Presenting to senior leadership. Distilling complex topics into clear narratives that support decision-making.
Managing expectations: Setting realistic expectations about what can be delivered when. Saying no diplomatically when necessary.
Agile product ownership: Working with Agile teams, managing backlogs, participating in ceremonies, adapting to sprint-based delivery.
Lean startup principles: Build-measure-learn cycles. MVP thinking. Validated learning rather than building everything upfront.
Hypothesis-driven development: Framing work as experiments with clear hypotheses. Learning from what works and doesn’t.
Design tools: Figma is most common now for UX work. Sketch, Adobe XD for design. Miro or Mural for workshops and collaboration.
Prototyping tools: Figma for interactive prototypes, Axure or Framer for more complex prototyping.
Product management tools: Jira for backlog management, Productboard or Aha! for roadmapping, Confluence for documentation.
Research tools: UserTesting, Lookback, or Maze for remote usability testing. Optimal Workshop for card sorting and tree testing. Survey tools like Typeform or Google Forms.
Analytics: Google Analytics, Mixpanel, Amplitude, or Heap for product analytics. Hotjar for heatmaps and session recordings.
Collaboration tools: Miro and Mural for virtual workshops. Slack or Teams for communication. Loom for async video updates.
Empathy: Understanding users deeply – their frustrations, contexts, goals. Advocating for users in discussions where they’re not represented.
Communication: Explaining complex ideas clearly. Adapting communication style for different audiences. Writing clear specifications and documentation.
Facilitation: Running workshops, design sprints, stakeholder sessions. Creating environments where diverse perspectives contribute.
Influence without authority: Product people rarely have direct authority over developers, designers, or stakeholders. You succeed through influence, persuasion, and building trust.
Strategic thinking: Seeing beyond immediate features to understand bigger picture. Connecting product decisions to business strategy.
Comfort with ambiguity: Product problems are messy. Requirements evolve. You need to be comfortable making decisions with incomplete information.
Analytical thinking: Using data to inform decisions. Balancing quantitative metrics with qualitative insights.
Product careers offer multiple specialisation paths with opportunities to focus on strategy, design, or analysis:
Junior Product Manager / Associate Product Manager: Supporting product managers, gathering requirements, writing user stories, coordinating with development teams, maintaining product documentation. Learning product management fundamentals. Salary: £25,000 – £35,000.
Entry roles involve lots of coordination work, requirement gathering, and learning how products are built. You’ll support more senior product people while building skills.
Junior UX Designer: Creating wireframes and mockups, conducting basic usability testing, supporting senior designers, learning design tools and methods. Salary: £24,000 – £32,000.
Junior Business Analyst: Gathering requirements, documenting processes, supporting senior analysts, creating specifications for smaller features. Salary: £22,000 – £30,000.
Product Manager: Owning product or feature area, defining roadmap, prioritising work, working with cross-functional teams to deliver products. Making strategic decisions about what to build. Salary: £40,000 – £60,000.
At this level you’re trusted to own product areas independently, make prioritisation decisions, and balance stakeholder needs with user needs and technical constraints.
Product Owner (Agile): Managing product backlog in Agile environment, writing user stories, accepting completed work, working closely with development teams. Salary: £35,000 – £55,000.
Product Owners are more tactical than strategic Product Managers, focused on sprint-level planning and working with development teams rather than long-term strategy.
UX Designer: Independently designing user experiences, conducting research, creating prototypes, testing with users, working with developers on implementation. Salary: £32,000 – £50,000.
Business Analyst: Analysing business problems, gathering and documenting requirements, facilitating workshops, creating business cases, supporting project delivery. Salary: £30,000 – £45,000.
CX Designer / Customer Experience Manager: Mapping customer journeys, identifying pain points, designing improvements across touchpoints, measuring customer satisfaction. Salary: £32,000 – £48,000.
Senior Product Manager: Leading product strategy for major product areas, managing other product managers, influencing company direction, working closely with executives. Salary: £55,000 – £80,000.
Lead Product Manager / Principal Product Manager: Setting product vision and strategy across multiple products, defining product standards, mentoring product managers. Salary: £65,000 – £90,000+.
Senior UX Designer / Lead UX Designer: Leading design for complex products, mentoring junior designers, influencing design strategy, establishing design standards. Salary: £45,000 – £70,000.
UX Research Lead: Leading research function, defining research strategy, conducting complex research studies, building research practice. Salary: £50,000 – £75,000.
Senior Business Analyst: Leading requirements for complex projects, mentoring junior analysts, defining BA standards and methods. Salary: £45,000 – £65,000.
Service Designer: Designing end-to-end services across digital and physical touchpoints, working across organisational boundaries, strategic service design. Salary: £40,000 – £65,000.
Head of Product / VP Product: Leading product function, setting product strategy, building and managing product teams, reporting to executives. Salary: £75,000 – £120,000+.
Chief Product Officer (CPO): Executive responsibility for all products, product strategy aligned to business strategy, board-level reporting. Salary: £100,000 – £180,000+.
Head of Design / Design Director: Leading design function, defining design vision, building design teams, influencing company direction through design. Salary: £70,000 – £110,000+.
Head of Customer Experience: Leading CX strategy across organisation, measuring and improving customer satisfaction, building CX capability. Salary: £65,000 – £95,000+.
Technical Product Manager: Product management for highly technical products, working closely with engineering on architecture and technical decisions. Requires stronger technical background.
Growth Product Manager: Focus on user acquisition, activation, retention, monetisation. Data-driven product work optimising growth metrics.
Platform Product Manager: Managing internal platforms and tools used by other teams. Focus on developer experience and internal users.
UX Researcher: Specialising in user research rather than design. Planning and conducting research studies, synthesising insights, building research practice.
Content Designer / UX Writer: Focusing on words in products – microcopy, error messages, onboarding, help content. Making products clearer through better writing.
Product skills open doors to consulting (advising organisations on product strategy), startups (founding or joining early-stage companies), venture capital (evaluating investment opportunities), or executive leadership beyond product function.
Product roles suit people who enjoy understanding users, solving problems strategically, and coordinating diverse stakeholders to create valuable outcomes.
Genuine curiosity about users: Product work starts with understanding people – what they need, how they work, what frustrates them. If you’re naturally curious about why people do what they do, product work is engaging.
Strategic thinking: Seeing beyond immediate features to understand bigger picture. Connecting product decisions to business goals and user needs.
Comfort with ambiguity: Product problems are messy. You rarely have perfect information. You need to be comfortable making decisions with uncertainty and adapting as you learn.
Collaborative nature: Product work is inherently collaborative – working with designers, developers, stakeholders, users. If you enjoy bringing diverse perspectives together, you’ll find this rewarding.
Communication skills: Much of product work involves communication – gathering requirements, presenting strategy, writing specifications, facilitating workshops. Clear communication is essential.
Analytical and creative: Good product work balances data with intuition, analysis with creativity. You need both quantitative thinking and creative problem-solving.
Software developers: Technical people moving into product roles bring understanding of what’s technically feasible and credibility with engineering teams. They add user focus and strategic thinking.
Designers: UX designers moving into product management bring deep user understanding and design thinking. They add business strategy and stakeholder management.
Business analysts: BAs moving into product roles bring requirements skills and stakeholder management. They add more strategic focus and product ownership.
Project managers: PMs transitioning to product roles bring coordination skills and ability to get things done. They shift from delivery focus to outcome focus.
Domain experts: People with deep expertise in particular industries (healthcare, finance, education) moving into product roles for that domain. They bring invaluable context and credibility.
Complete career changers: People from teaching, psychology, research, customer service, or other fields who bring fresh perspectives, empathy skills, and transferable capabilities.
People who genuinely care about users and solving their problems. Those who can balance competing interests – user needs, business goals, technical constraints. Individuals comfortable influencing without authority. People who communicate clearly and build trust across diverse stakeholders.
Age and background don’t matter. Product work values maturity, business context, and life experience. Many successful product people came to the field mid-career and bring valuable perspective from other domains.
You don’t need technical background for most product roles. Understanding technology helps, but product work is fundamentally about understanding problems and designing solutions – technical implementation comes from engineering teams.
Influence without authority: Product people rarely have direct authority over teams building products. You succeed through influence, which can be frustrating when people don’t follow your direction.
Saying no constantly: Most product work involves saying no – to stakeholder requests, feature ideas, scope creep. Disappointing people diplomatically is emotionally draining.
Ambiguous problems: Product problems are rarely clear-cut. You make decisions with incomplete information and deal with constantly changing contexts.
Competing priorities: Stakeholders want different things. Users want different things. Engineering has constraints. Business has pressures. Navigating competing priorities is constant.
Slow feedback loops: Unlike coding where you see results immediately, product decisions take time to validate. You might wait months to know if strategy was right.
Creating impact: Seeing products you shaped being used by real people solving real problems. The impact is tangible and meaningful.
Intellectual challenge: Product work is intellectually engaging – understanding complex problems, designing solutions, making strategic trade-offs.
Variety: Product work touches everything – strategy, design, data, technology, business, users. Most days involve diverse activities.
Learning continuously: Understanding users, industries, technologies, business models. Product work provides constant learning.
Seeing whole picture: Unlike specialists who focus on one area, product people see how everything connects – strategy to execution, user needs to business goals.
Product work is accessible without technical background, though the path depends on which area interests you most:
For Product Management:
Start learning product fundamentals:
Take free courses:
For UX Design:
Learn design fundamentals:
Practice design:
For Business Analysis:
Develop analytical skills:
Product employers want to see how you think and work:
Case studies: Document your thinking about products:
For UX portfolios:
For BA portfolios:
Product experience is challenging to get without product role, but there are ways:
Internal opportunities: If your current organisation has product teams:
Side projects:
Transition from adjacent roles:
Learn some technical basics: You don’t need to code, but understanding:
Data and analytics:
Business fundamentals:
Apprenticeships: Product management, UX, and business analysis apprenticeships provide structured learning while working in real product roles. Duration: 15-18 months. Government-funded for qualifying employers.
Apprenticeships suit people transitioning from other roles or entering the field. You’ll work with experienced product professionals while building skills systematically.
Bootcamps: UX bootcamps and product management courses teach practical skills intensively. Some are government-funded. Duration: 8-16 weeks.
University degrees: Degrees in UX, design, or business analysis provide theoretical foundation. Not essential – many successful product people don’t have specific degrees.
Certifications: Product Management certifications (Pragmatic Marketing, Product School), PSPO (Professional Scrum Product Owner), or BA certifications (BCS, IIBA) provide credibility but aren’t essential.
Entry-level product roles are competitive:
Target smaller organisations: Startups and scale-ups hire junior product people more readily than large corporates. You’ll learn quickly through broad exposure.
Consider adjacent roles: Product Coordinator, Product Operations, UX Researcher, Junior BA – these provide exposure to product work and pathways to core product roles.
Leverage domain expertise: If you have healthcare, finance, retail, or other domain experience, target product roles in that sector. Domain knowledge is valuable.
Transition from current role: Project Managers, BAs, Customer Service – emphasise transferable skills and show product thinking.
Network: Join product communities – Product Tank, Mind the Product, local UX groups. Engage with product professionals. Many roles are filled through connections.
Show product thinking: In interviews, demonstrate how you think about products – prioritisation, user needs, trade-offs. Your thinking matters more than experience for junior roles.
The Coders Guild offers product management, UX, and business analysis apprenticeships covering user research, product strategy, design methods, and stakeholder management. Training is practical, includes real product work, and is taught by experienced product professionals.
Government funding is available for apprenticeships and qualifying programmes. Browse our product courses below or get in touch to discuss which route might work for you.
Junior Product Manager / Associate PM: £25,000 – £35,000 for entry-level product roles supporting more senior product managers.
Product Manager: £40,000 – £60,000 for mid-level product managers owning product areas independently.
Senior Product Manager: £55,000 – £80,000 for experienced PMs leading product strategy and mentoring others.
Lead/Principal Product Manager: £65,000 – £90,000+ for product leaders setting strategy across multiple products.
Product Owner (Agile): £35,000 – £55,000 for POs working with Agile teams. Generally slightly less than equivalent Product Manager roles.
Junior UX Designer: £24,000 – £32,000 for entry-level design roles.
UX Designer: £32,000 – £50,000 for mid-level designers independently creating user experiences.
Senior/Lead UX Designer: £45,000 – £70,000 for experienced designers leading complex projects and mentoring others.
UX Researcher: £35,000 – £60,000 depending on experience. Research specialists often paid similarly to designers.
Junior Business Analyst: £22,000 – £30,000 for entry-level BA roles.
Business Analyst: £30,000 – £45,000 for mid-level BAs independently managing requirements.
Senior Business Analyst: £45,000 – £65,000 for experienced BAs leading complex projects.
Head of Product / VP Product: £75,000 – £120,000+ for product leadership roles.
Head of Design: £70,000 – £110,000+ for design leadership.
Salaries vary significantly by sector and company type. Technology companies and startups often pay more than traditional industries. London pays 20-30% more than other regions. Scale-ups and tech companies often include equity alongside salary.
Product roles continue experiencing strong demand as organisations recognise importance of product thinking:
Product Managers: High demand, particularly for people with combination of technical understanding and business acumen. Competition for junior roles but strong demand for experienced PMs.
UX Designers: Steady demand across organisations of all sizes. Entry-level roles competitive but experienced designers remain sought after.
Product Owners: Consistent demand in Agile organisations. Often easier entry point than Product Manager roles.
Business Analysts: Strong demand, especially in financial services, consulting, and government. BA skills transfer well across sectors.
UX Researchers: Growing demand as organisations invest more in research. Research specialists less common than designers so less competition.
Product work adapted well to remote during COVID and many roles remain remote or hybrid:
Remote-friendly aspects: Much product work – research synthesis, roadmapping, specification writing, design work – can be done remotely. Digital collaboration tools work well.
Challenges of remote: Collaborative workshops, user research, stakeholder relationship building can be harder remotely. Some organisations prefer product people in-person for better collaboration.
Hybrid common: Many organisations now offer hybrid – remote most days with occasional in-person for workshops, planning, or stakeholder meetings.
Junior roles sometimes benefit from more in-person time for mentoring and learning. Experienced product people work effectively remotely.
Product contracting and consulting is common at senior levels:
Contract Product Managers: £400-£700 per day depending on experience and specialisation.
Contract UX Designers: £300-£550 per day for design work on specific projects.
Product consultants: £500-£900+ per day for experienced consultants advising on product strategy and transformation.
Interim product leadership: £600-£1000+ per day for interim Head of Product or similar leadership roles.
Contracting typically requires several years of permanent experience first. Clients want proven track record and often specific domain expertise.
Product careers offer strong progression for people who develop both strategic thinking and execution skills:
Depth in domain: Becoming expert in particular industry (fintech, healthcare, B2B SaaS) increases value and compensation.
Technical product management: Product managers with technical background or who develop strong technical skills often earn more.
Leadership progression: Moving into management – leading product teams, setting product strategy – significantly increases compensation.
Startup equity: Joining early-stage startups as product leader can provide significant upside through equity if company succeeds.
Senior product leaders with combination of strategic thinking, delivery track record, and leadership skills can reach six-figure salaries. CPO roles at scale-ups and larger companies offer £150,000+ plus equity.
If you’ve got an event, collaboration or success story we should know about – get in touch.
FREE AI WEBINARS
Two short, practical AI sessions a month. Free. Drop your email and we’ll send you the link, plus the recordings of the ones you’ve missed.
"*" indicates required fields
