A great resume paints a comprehensive picture of an engineer without being overwhelming. If you have 20 years of experience, don’t share every detail of every role. Instead, describe the top accomplishments from your recent roles. On the other hand, if you’re new to programming and don’t have much professional experience, try not to leave this section too sparse. Sharing details about your educational background, personal projects, and relevant work or volunteering can help companies get to know you.
A great resume also answers the simple question “So what?” Let’s say you built a new mobile app... so what? What problem did it solve? How did you solve it? Who was impacted? In what way? Companies are generally most interested in what you did, not just the job title, degree, or project name. Engineers who take the time to describe their responsibilities and projects, along with any measurable results, often receive more interest from companies. And if you can add quantifiable data or metrics that support that impact, even better.
Finally, companies are particularly interested in what you've been doing most recently, whether that's a job, education, or side project, so be sure to include your most recent accomplishments. Similarly, if your resume doesn't reflect continuous work or study, you may want to include what you've been up to so that hiring managers aren't left guessing. One or two months here or there isn't a big deal, but more than that is usually worth a short explanation.
If you have additional questions, please contact Candidate Support.