I've reviewed 100,000+ Software Engineering resumes for Google and Unity over my career. I can tell you this. One big thing I've learned is to pretty much rebuild your resume at certain points in your career.
When Engineers are moving from full stack engineering to a niche like Cloud Services or ML, I want to see how the work you've done in your past 5 jobs is relevant to the position we are filling.
Depending on your experience, I want to see the highlights of the work you are most proud of and then I want to see where you've been exposed or developed skills in the technologies/architecture we are implementing.
If you lack industry experience, but believe you could excel at the role, it's even more critical to communicate your experience with the skills and requirements for that specific role.
Even if you've only worked on the backend api for 4 months, doesn't mean you won't land that Software Engineering role at your dream company. If you HIGHLIGHT the work that you're MOST PROUD OF and EMPHASIZE how you've used our SPECIFIC STACK or ARCHITECTURE.
We want you to sell us a bit in your resume. It's like an executive summary for a business, but typically way more interesting as it encapsulates a career of multiple ventures and opportunities. Rare is the person who works on one project or at one company for their entire professional career.
I'm currently asking to make the transition from Software Engineering Recruiter to Business Development Manager, working in the field with studios building on top of Unity.
If/when I get the job, I will begin a chat for Engineers building in Unity, I'll be able to provide resources from our end to help devs in many situations.
'till then, steemon...
