Search for the work someone performs, not just the title on their profile. A person called an operations specialist, implementation consultant, or business analyst may write scripts, maintain integrations, or build data pipelines without holding an engineering title.
That makes title a useful starting signal, not a complete definition of capability. The sourcing task is to identify relevant evidence and then confirm the scope with the candidate.
Translate the vacancy into technical activities
Write down the work you need done: automate a recurring process, debug an integration, query a database, maintain a deployment pipeline, or analyze production data. For each activity, list tools and vocabulary a person doing that work would plausibly use.
For example, a data-operations search might include SQL, Python, ETL, data quality, API integration, and workflow automation. Those terms are search hypotheses. Finding one does not establish proficiency.
Expand the title families
Search adjacent functions where the same work appears. Implementation, analytics, revenue operations, technical support, solutions consulting, and research can contain technical responsibilities.
Keep title expansion separate from changing the seniority requirement. An operations analyst who scripts reports is not automatically a senior platform engineer. Match the scope, complexity, ownership, and recency of their work to the role.
The job-title normalization guide explains why original titles and standardized classifications should both remain visible.
Read responsibility statements closely
Look for descriptions of actions and outcomes: “built,” “integrated,” “debugged,” or “maintained” followed by a specific system or result. Distinguish using a tool from developing with it, and participation from ownership.
Record the evidence behind the match. A useful sourcing note might say, “Maintained Python scripts that reconciled billing data between two systems; depth of testing and ownership still to confirm.” That is more defensible than assigning an engineer label from a keyword.
Public work can add context. Our guide to sourcing engineers through GitHub contributions shows how to inspect contributions without treating activity counts as a skills verdict.
Ask a scope-confirming question
In outreach, describe the responsibility that caught your attention and ask whether it reflects their current work. In screening, ask what they built, how they tested it, what they owned, and which decisions they made themselves.
Give candidates room to clarify. Internal titles may reflect an employer's structure, and a candidate may have broader or narrower responsibilities than a title suggests.
Make the search repeatable
Maintain a record of adjacent titles, technical activities, and the evidence you want to see. Change one search dimension at a time so you can tell which expansion produced useful candidates.
Skills- and experience-led talent sourcing supports the broader discovery and outreach workflow. Confirm specific integration and search capabilities before assuming any platform automatically validates a candidate's technical work.
Bottom line
Technical capability can sit behind a nontechnical title. Find it by searching responsibilities and tools, inspecting specific work, and confirming ownership. Preserve the original title and separate a plausible sourcing match from a verified skills assessment.