The 4 weeks
One real problem, carried all the way through.
The problem you pick in Week 1 is the one you design for, build, and prove. By the end you have a working piece of your own recruiting system and the story to sell it.
Week 1
Notice It, Diagnose It
Map your hiring pipeline like an engineer: stages, conversion, cycle time, and where it breaks. Lay your friction log over it and choose your best first problem: recurring, meaningful, in your control, and small enough to test.
You leave withYour pipeline map and one problem, backed by evidence.
Week 2
Design It
Learn what LLMs actually do, then work through the design questions for your problem. What's causing it? What should stay human? What's the smallest thing worth testing? Build and bias-check one prompt or fix.
You leave withA written design and one tested intervention.
Week 3
Build It
Automation for non-engineers: triggers, actions, and APIs in plain English. Turn your fix into a working MVP using ready-made templates and practice data, and learn why clean data matters more than flashy tools.
You leave withA working MVP you can share with your team.
Week 4
Prove It
Measure what changed, build a before/after scorecard, and plan who has to change what for it to stick. Then write a three-sentence pitch for your VP and defend it to your partner: why this problem, what tradeoffs, who has to adopt it, how you know it worked.
You leave withA leadership-ready case for what you built.