Sourcing by role
How to find engineers, data and AI talent.
Sourcing guides for technology roles: the title inflation and drift that makes job titles nearly meaningless, where engineers leave public evidence of their work, and search strings built around what someone has actually built.
AI / Machine Learning Engineer
Research versus production as the costliest mis-hire, and how to tell genuine LLM depth from API-level work.
46 title variantsSoftware Engineer
Why job titles carry so little signal here, how the Staff and Principal ladder actually reads, and how to search the public work trail instead.
64 title variantsCybersecurity Analyst
Why blue team, red team and GRC need different people, which certifications actually prove capability, and how clearance gates the market.
54 title variantsData Scientist
Why one title covers three different jobs, how company size inverts its meaning, and the published work trail that reveals what a CV cannot.
47 title variantsData Engineer
Why the title is a decade old and hides its most experienced practitioners, and why batch and streaming are different skills.
43 title variantsCloud Engineer / Architect
Why certifications predict little, how much provider depth actually transfers, and what published infrastructure code reveals.
42 title variantsDevOps / Platform Engineer
Why one title covers four different jobs, how SRE and platform engineering differ, and the sysadmin pool nobody searches.
40 title variantsMLOps Engineer
Why every candidate arrived from a different discipline, how ML systems fail differently from software, and what LLMOps changed.
40 title variantsPrompt Engineer / AI Specialist
Why the title is dissolving into broader roles, how evaluation skill separates practitioners, and the domain-expert pool nobody searches.
47 title variantsData / BI Analyst
Why most analyst roles are actually reporting roles, how to test SQL depth properly, and the domain career-changer pool.
45 title variantsSolutions Architect
Why pre-sales and delivery architects are different hires, how to tell whether an architect still builds, and when TOGAF matters.
47 title variantsProduct Manager
Why titles do not indicate level, how consumer and enterprise PM differ, and how to evaluate impact claims that are hard to attribute.
43 title variantsForward-Deployed Engineer
Why orientation matters more than capability, how it differs from pre-sales, and the startup engineer pool that fits naturally.
46 title variantsData Annotator
How annotation moved from volume labelling to expert judgement, why guideline design determines quality, and the labour ethics dimension.
46 title variantsFull Stack Developer
Why the term means different things by company size, why equal depth on both sides is unrealistic, and how GitHub verifies the claim.
49 title variantsQA Engineer
Why SDET is a software engineering job, why automation is a code quality problem, and when manual testing still matters.
48 title variantsUX / UI Designer
Why the portfolio is the only reliable screen and process beats visuals in it, and why UX and UI are different disciplines.
48 title variantsNetwork Administrator / Systems Engineer
Why traditional networking fundamentals still decide troubleshooting in cloud environments, and which certifications genuinely track capability.
45 title variantsIT Support Specialist
Why this is where IT careers start and what that means for retention, the tier structure, and the MSP pool nobody approaches.
48 title variantsIT Manager
How company size completely redefines this role, and the vendor and budget skills adverts never mention but the job requires.
47 title variants