Getting hired

The realistic junior-AI-engineer pipeline. Resume, GitHub, DSA realism, take-homes, behavioural, light system design. The application sprint that gets you offers.

• 30.0Orientation: the chapter that turns shipping into hired
• 30.1The pipeline at small companies
• 30.2The pipeline at large companies
• 30.3The resume that survives 30 seconds
• 30.4The GitHub profile that signals competence
• 30.5The LinkedIn presence without cringe
• 30.6Cover letters: when they help, mostly when they don't
• 30.7The online assessment and the take-home
• 30.8DSA realism for AI-leaning roles
• 30.9The seven coding-question shapes
• 30.10Behavioural interviews: STAR without sounding rehearsed
• 30.11The "tell me about yourself" answer
• 30.12The "why this company" answer
• 30.13Light system design for junior roles
• 30.14Mock interviews: how to find partners, how to use them
• 30.15Negotiation 101
• 30.16Tracking applications, follow-ups, the funnel as data
• 30.assignAssignment: 50-application sprint with tracked metrics

What 'junior' actually means in a team. Onboarding fast. The non-technical mistakes that get juniors fired. The six-month review you set up for yourself.

• 31.0Orientation: the chapter that decides whether the job sticks
• 31.1What 'junior' means in a real team
• 31.2The first week: what to do, what to skip
• 31.3The onboarding S-curve and where most people stall
• 31.4Asking for feedback that gets you better, not nicer
• 31.5The first PR you ship at work
• 31.6The first incident you are part of
• 31.7The first time you are wrong in a meeting
• 31.8The non-technical mistakes that get juniors fired
• 31.9Working with senior engineers
• 31.10Working with non-technical stakeholders
• 31.11Salary negotiation after the offer
• 31.12Setting up your six-month review for yourself
• 31.13When to ask for a promotion vs when to leave
• 31.14Burnout: how to recognise it before it costs you
• 31.15The send-off
• 31.assignAssignment: your 30/60/90 plan