Lead with technical hiring scope
Put your current title, years of recruiting experience, and technical hiring areas near the top. Name the functions and seniority levels you have recruited for, such as backend engineering, data, or product leadership. If you have managed full-cycle searches, say so clearly; candidates who only sourced or coordinated should describe that scope accurately rather than implying ownership of the entire process.
Show the recruiting funnel
Use a few defensible measures to show how your work affected hiring: requisitions managed, hires made, qualified screens, time to fill, or interview scheduling turnaround. Add the period and the type of roles so the figures have context. Avoid crediting yourself for every team outcome; explain the recruiting action, such as intake calibration or outbound sourcing, that contributed to the result.
Name tools and sourcing methods
List the ATS and sourcing platforms you have actually used, such as Greenhouse, Lever, LinkedIn Recruiter, or SeekOut. Mention Boolean search, referral campaigns, or talent mapping when they are part of your work. Keep the tools section scannable and do not imply certification in a platform unless you hold a real credential; employers generally care more about what you did with the tools.
Describe fair hiring practices
If you have improved access or consistency in hiring, describe the process: structured interview plans, calibrated scorecards, accessible job postings, or broader sourcing channels. Include a concrete example and outcome when you can support it. Avoid broad claims about diversity without describing your contribution, and leave out confidential candidate details, internal compensation data, and unsupported conversion statistics.