Job searching is a skill with almost no relationship to the skill of writing software, which is why excellent engineers sometimes struggle for months while weaker candidates get offers. This course treats the search as its own discipline and gives you a system to run, rather than advice to feel encouraged by.
It begins with positioning. What kind of role you are actually a strong candidate for today, which adjacent roles are reachable with two months of deliberate work, and how to describe yourself in a sentence that makes a hiring manager keep reading. Then the portfolio, built on a single unpopular principle: two finished, deployed, documented projects beat eleven abandoned repositories, and the course shows precisely what finished means, including the README that decides whether anyone clicks further.
The application material follows. A resume rewritten to lead with outcomes and numbers rather than responsibilities, formatted to survive automated screening. Cover notes that are three sentences long and get replies.
The second half is interviews. Technical screens and how to think out loud without falling silent. System design at a level a mid-level candidate is genuinely asked. Finally the negotiation conversation, with exact wording for the moment they ask your expectations and you should not answer first.