Designing for Hiring

How engineering and HPC/AI organisations make better hiring decisions

Series: Sustainable Reality Reflections — Decisions in Emerging Technologies

Technical organisations often discuss hiring as though it sits outside the core work.

Products, systems, infrastructure, and strategy receive sustained attention. Recruitment is sometimes treated as a support function that begins only when a vacancy appears.  That distinction rarely holds in practice.

Hiring decisions shape delivery speed, team cohesion, technical direction, and the ability to grow over time. Few choices influence an organisation more consistently than deciding who joins it.

At Sustainable Reality, John Fergusson approached hiring from the perspective of a career investigator. His session focused less on recruitment mechanics and more on decision quality: how organisations define roles, assess fit, and avoid mistakes that create long-term drag.  Here is what we learned.

Define the role before starting the search

Many hiring problems begin before candidates ever enter the process.

Teams often start with urgency. Someone has left. Work is piling up. A manager wants to move quickly. In that environment, organisations can default to replacing a person rather than rethinking the role itself.

A stronger starting point asks different questions.

• • What does the organisation need now? 

• • What should this role achieve over the next few years? 

• • How might the work evolve as the business changes?

Clear answers improve every later decision. Without them, hiring teams often search for a person before they understand the job.

Outcomes matter more than skill wish lists

Job descriptions frequently become long inventories of tools, qualifications, and desirable traits.  These lists can create the appearance of precision while obscuring the real question: what does success look like in practice?

Strong hiring processes define outcomes first. They identify the problems the role should solve, the responsibilities it should carry, and the results expected over time.  That approach helps candidates assess fit honestly. It also gives interviewers something more useful than intuition when comparing applicants.

Hire technical specialists, not generic talent

Technical work rarely benefits from vague categorisation.  A software engineer may have deep experience in one environment and limited exposure to another. A data specialist may excel in modelling but not platform engineering. Broad labels often hide meaningful differences.

Treating talent as interchangeable creates avoidable friction after someone joins.

Better hiring decisions recognise specificity. Teams perform more effectively when organisations understand the actual expertise required and recruit accordingly.

Hire for growth, not perfection

The search for a perfect candidate often delays progress.  Few people meet every requirement, and insisting on complete alignment can unnecessarily narrow the field. It can also lead organisations to overlook people who would grow strongly in the role.

A better balance weighs present readiness against future development.  Candidates do not need to arrive finished. They need enough foundation to succeed, enough adaptability to grow, and enough alignment with the environment to contribute well.

Structured interview processes improve decisions

Hiring quality depends partly on how decisions are made.

Unstructured interviews often reward confidence, familiarity, or personal chemistry more than evidence. Different interviewers may assess different things without realising it. Candidates leave uncertain about the role, while teams leave uncertain about the candidate.

Structured processes reduce that noise.

When each stage has a clear purpose, interviewers know what to test, and assessments connect to the actual role, decisions become more reliable and easier to defend.

Real evidence matters more than polished answers

Interviews often ask people what they would do.  That can produce polished answers with limited predictive value.

A stronger approach asks what candidates have done. Real examples reveal how someone approaches problems, works with others, handles trade-offs, and learns from mistakes.

Past behaviour is not a perfect forecast, but it usually offers better evidence than hypothetical performance.

Hiring is strategic work

The wider lesson is simple.  Hiring is not separate from organisational performance. It is one of the ways organisations create it.

Strong hiring in technology often depends on clear role design, structured interviews, evidence-based assessment, and realistic expectations around growth. These principles apply whether organisations are hiring software engineers, AI specialists, infrastructure teams, or technical leaders.

In that sense, hiring is not merely an operational task.  It is a design discipline.

You can gain all the insights from John’s talk by visiting the speaker’s page, or if you want a taste of his talk, you can watch the short clip below: