📎 Webclip
My wild prediction for 2027: this is your last job.
The article argues that the job market for software engineers is shifting fast. Hiring as it exists now is expected to collapse, while fewer jobs will remain because AI will make software work cheaper and more accessible for smaller businesses. The author says the useful response is to build broad systems thinking, understand the real problem, and avoid fixating on a single solution.
Reading notes#
- Hiring is already showing strong signs of breaking down, with companies unable to find candidates and candidates unable to find jobs.
- Software engineers will be redistributed from large companies to smaller businesses as AI becomes more accessible.
- More engineers will become self-employed and solve specific problems for different businesses.
- Elizabeth Stone’s example is used to support hiring for systems thinkers and against narrow specialization.
- Systems thinking is described as stepping back to question broader assumptions and understand why a problem exists.
- The author warns that questioning can become unproductive when it turns into endless edge-case hunting.
- Good systems thinkers understand the outcome, focus on what actually needs to happen, and can adapt when conditions change.
- The article uses examples from legal opt-ins, app rebuilds, and pivots to show how systems thinkers remove assumptions and simplify work.
- The Einstellung effect is cited as the habit of sticking with a known solution even when a better one is available.
- The author says many engineers focus on getting a job by filling missing credentials, but that matching strengths matters more.
- The article contrasts people with strong fit, like Jonas, and people with weaker market position, like Peter, who still succeeded by targeting well and explaining their thought process.
- Building something cheaper or more generic is presented as a weak strategy compared with offering something focused and valuable.
- People who stay open to work for too long may turn bitter, fake activity, and hurt their chances.
- The author contrasts unemployment, being employed but exhausted, and having time and energy, and gives different advice for each case.
- If there is little runway left, the advice is to get a job quickly and avoid trying to automate the search.
- If there is some traction, the weak signal should be explored.
- If there is time and energy left after work, the author says to stop with hobby projects and build something for yourself and your family that outlasts jobs: value creation instead of trading time for money. He says software engineers may not have as much time as they think.
- Building is now cheap, so the open questions are whether it can be sold and whether it is specific enough. Starting from the building means losing to AI sooner or later.
- The cautionary case is an IT support worker, drained by a semi-toxic job, who builds an app on the side. He has energy for building but not for checking whether he is solving the right problem or whether anyone would pay. The author calls this self-handicapping and says it was his own pattern across four failed startups.
- The advice is to build on a domain where you have an advantage the models were not trained on, such as twenty years in health, and to prove it sells before building.
