The most common résumé we see simply lists past duties in chronological order. But a reader does not want to know what you did — they want to know what you can do.
For each project, briefly set out the scale, the team structure, your role, the technologies used and the results. Your place in the team structure in particular is the first thing an interviewer checks.
Two to three pages is about right. Taking the time to change which experience you highlight for each application is, in the end, the fastest route.
Related Articles
1 Oct
About Skillhouse University
The training available to registered staff, and the support we offer for earning certifications.
1 Oct
What People Overlook in Their First Job Change
Not just salary, but the evaluation system, real overtime and where you'll be placed. The points to confirm before you join.
1 Oct
Why Demand for IT Security Talent Keeps Growing
Regulation, the move to the cloud and the structure of talent supply. An analysis of why security openings aren't shrinking.