📎 Webclip
Pimp Up Your Resume
The page says a strong software resume should fit on one page and present you as a serious marketable candidate. It recommends being truthful, using a photo, skipping vague titles and objectives, keeping skills short and specific, and adding public signals such as Stack Overflow, GitHub, certifications, talks, a blog, and selective career details.
Reading notes#
- Keep the resume to one page, because longer versions look unprofessional and bury the most important information.
- Never lie on the resume, and be ready to explain every word you use.
- Put a photo at the top, make it artistic, casual, and confident.
- Skip objective and title fields, since your name is enough and generic titles do not help.
- Keep the skills list under 12 items, and make the skills specific and at the same level of abstraction.
- Build a visible Stack Overflow profile and link it in the resume.
- Use GitHub activity and open source contributions as proof that other people have seen your code.
- Add certifications, but avoid low-value certificates from sites like BrainBench.
- Mention big names and big numbers from your past work when they are true and you can explain them.
- Create a blog and write about your code, work, plans, and reading.
- If you are early in your career, add ambitions such as learning Go, writing a book, or earning a certification.
- Keep education short, unless you have a PhD or studied at Stanford or MIT.
- Speak at conferences when possible and make yourself visible in the market.
- Keep career history short and focus on achievements rather than duties.
- Add memberships in groups such as ACM, IEEE, or JUG to show community participation.
- Mention hobbies to create a personal connection with the reader.
- Design the resume carefully so it feels like a product you made with care.
