Let’s face it, I’m not an expert in information technology. I don’t write code, I can’t architect a cloud-based software application or administer an Oracle Database. Although I would love to add all of these skills to my knowledge toolbox, my frontal lobes are wired for recruiting. Recruiters wear many hats, and at first glance, I cannot decipher much past job titles, especially if a resume is not written well. It is my responsibility to delve past traditional job titles by bringing to the surface your proudest and most important contributions to your employers.
As a recruiter, my goal is to paint a picture for the client that is more in depth than your resume. Your resume may indicate you’ve held numerous positions, but does not highlight your leadership qualities. Without digging deeper into conversation, I may never know that you actually “led a team of 5 developers on a data migration project”, something to highlight in seeking out your next endeavor. When crafting your resume, don’t list the mundane aspects of your job duties. Believe me, my eyes are tired of reading “Gathered the functional requirements for the project,” for IT Business Analysts. Tell me a time you went above and beyond to abstract critical information for a deadline, or crafted a detailed project outline for all parties involved in the process.
Job titles and even basic job functionalities are all smoke and mirrors. As my colleague mentions to candidates, you have between 8 and 10 seconds for someone to make up their mind about whether or not you can solve their problem. Think intuitively about the role you played at each within each and every one of your positions held. If you could change your “dubbed” job title, what would you call yourself? That is what a recruiter wants to know.