You already know how to recruit. This course gives you the one thing you're missing: enough understanding of how tech teams work that you can talk to engineers, designers and product managers as a peer, read their CVs properly, and push back on hiring managers with confidence.
You do not need to learn to code or design. You need to understand what each role does, why it exists, how to tell good from average, and what words mean. That is what this course teaches.
The one idea that holds everything together: every tech product is built by three groups answering three questions.
| Role | The question they answer | In one line |
|---|---|---|
| Product Manager | Why are we building this, and what should we build? | Decides what's worth doing |
| Product Designer | How should it look, feel and work for the person using it? | Makes it usable and desirable |
| Software Engineer | How do we actually build it so it works, reliably, at scale? | Makes it real |
Keep this table in your head. Almost every confusing job spec, title or interview question becomes clear once you ask: which of these three questions is this person mainly answering?
How the course is structured
- Module 1 – How tech companies work. The big picture: products, teams, company stages.
- Module 2 – Software engineering decoded. Every engineering specialism, explained simply, plus languages, stacks and levels.
- Module 3 – Product design decoded. UX, UI, research, portfolios and tools.
- Module 4 – Product management decoded. What PMs actually do all day and how to spot a strong one.
- Module 5 – How the three work together. A feature's journey from idea to launch.
- Module 6 – Sourcing, screening and interviewing. Practical playbooks, questions and red flags for each role.
- Module 7 – Levels, pay and the market. Career ladders, what drives salary, and closing candidates.
- Module 8 – Glossary. Every core term in plain English.
- Final assessment. Practice scenarios with model answers.
How to study it
- Go in order the first time. Each module builds on the last.
- Do the "Recruiter takeaway" at the end of each module. It turns the theory into something you can use on a call tomorrow.
- Use real job specs as homework. After each module, take a live job spec and try to translate every line into plain English.
- Ask candidates to teach you. Saying "Walk me through how that works, in simple terms" is a great screening question and a free lesson. Strong candidates explain clearly; weak ones hide behind jargon.
Golden rule: you are not assessing whether someone can code or design. You are assessing fit, scope, impact and communication, and making sure the right people reach the technical interview.