Little Parrot Logo

    For non-technical software Product Managers

    Become a Technical Product Manager Without Becoming an Engineer

    In our research into product management discussions, the same sentence kept coming up: “sometimes it does feel like I’m the least knowledgeable person in the room.”

    You know what your product does, but not yet how it works. So when a stakeholder suggests a new feature, you can’t yet say roughly how big a change it would be. This learning path teaches how the parts of a software product work together, and takes you a layer deeper into each one, so you can recognise them in your own and make decisions.

    We'll email you when the learning path opens.

    Follow a request through the frontend, the backend, the database and the infrastructure underneath
    Work out which parts of your product a proposed feature would change, before you commit
    Give engineering the steps that trigger a bug and what you’ve already ruled out
    Answer a straightforward product data question yourself
    A Little Parrot course open on a phone, showing one step of a walkthrough
    Built by Kinga, a lead product manager, and Tamas, a principal software engineer, previously at
    DatadogCitrixVolkswagenCloudera

    The learning path

    Seven steps, each one built around a question product managers search for, and each one leaves you able to do something new. The path is still being built, so the order may change.

    1. 1

      How a web application works: frontend, backend, database and infrastructure

      You’ll go a layer deeper into each part, so you know why a backend is usually several services, and what the terms your team uses about the infrastructure actually refer to; AWS, Google Cloud and Azure included.

    2. 2

      How an API works: data flow, webhooks and integrations

      You’ll inspect an API request and response and follow the data between systems, so you can ask specific questions about ownership, access and failure when a feature depends on an integration.

    3. 3

      How software deployment works: staging vs production

      You’ll follow one change through review, testing, staging and release, so you know how a change reaches users and when to expect it there.

    4. 4

      Bug triage: reproduce a bug, read the status code, find the failed request

      You’ll reproduce a failure, read the status code it returns and find the failed request in the browser’s network tab, so you can involve engineers with a useful starting point.

    5. 5

      SQL and product analytics for product managers

      You’ll write a simple SQL query and understand what's behind the numbers on a product analytics dashboard, so you don’t have to wait for someone else to answer a data question.

    6. 6

      Technical debt, technical feasibility and build vs buy

      You’ll understand what technical debt is costing you, when to prioritise tackling it above a new feature and make a build-versus-buy case.

    7. 7

      AI prototyping for product managers

      Use an AI agent to build a small working prototype and work out what engineering would still need to address before real users could use it, including security, reliability, monitoring.

    How the learning path works

    It's made up of hands-on challenges. Every step is self-paced, in short cards you can work through on your phone, so you can fit it around the job you’re already doing.

    You finish each challenge with something you made rather than a set of notes: a system map, a release walkthrough, a bug investigation, a technical decision review and a working prototype.

    Who writes them

    We write all of it ourselves. Kinga spent over a decade in the tech industry, learned to code, moved into product management and worked as a lead product manager. Tamas spent 15 years as a software engineer and engineering leader, and co-founded a coding school that graduated over 3,000 people into tech careers.

    Is this learning path for you?

    Yes, if

    • You manage a software product with no engineering background.
    • You can describe what your product does, but not how it works.
    • You want to represent the business and the customer in technical discussions, and follow the trade-offs the team is making.
    • You want to answer with confidence when a stakeholder calls something a quick feature, because you can see the work behind it.

    Not really, if

    • You want to move into an engineering role. This path teaches product judgement, not production engineering.
    • You already read your team’s code and follow architecture discussions.
    • You’re preparing for a technical product manager interview. This one is about the job you already have.

    Frequently asked questions

    Do product managers need to be technical?

    Not in the sense of writing production code. In the discussions we researched, product managers kept coming back to the same outcomes: explaining how their own product works, asking better questions and spotting complexity early. They also said again and again that getting good at a programming language was not the shortest route there.

    How technical should a product manager be?

    Technical enough to follow an explanation, restate it accurately, ask what breaks and judge whether a proposed change is riskier than it sounds. You don’t need to design the architecture or choose the implementation. You do need to follow the trade-offs well enough to speak for the business and the customer while the team decides.

    What technical skills do product managers need?

    There’s no single list, but seven skills came up again and again in our research. Each one is a step in the learning path above.

    Will I learn to code?

    You’ll read some code, and you’ll write some with an AI agent when you build a prototype in the last step. You won’t be learning a programming language, and nothing you build there reaches real users unless engineering takes it on.

    How much does it cost?

    We’re still setting the price. Join the list and you’ll see the current one straight after you sign up, along with one question about whether that price works for you. Your answer helps us decide what to charge.

    How long does it take?

    Each step in the path is self-paced and takes under an hour, in short cards you can work through on your phone. You finish each one with something you made, like a system map or a bug investigation, rather than a set of notes.

    Be first to know when it opens

    We'll email you when the learning path opens.