Resume and Portfolio
Write resume bullets that show impact, structure a one-page resume, and build a small portfolio and online presence that a hiring manager can evaluate in minutes.
beginner35 min#resume#portfolio#github#projects#job-search
Prerequisites: How the Software Interview Process Works
Why it matters
A resume is read quickly, often in well under a minute at first pass, by someone who may not be an engineer. Its job is not to tell your life story; it is to earn a conversation. A portfolio (projects you can link to) backs your claims with evidence, which matters most when you lack professional experience. Both are documents you fully control, so small improvements pay off across every application.
Intuition
Treat your resume as a product page and the hiring manager as a busy shopper. They scan for a few signals: relevant skills, things you built, and results. Each line should answer "so what?". "Used Python" is a feature; "Cut report generation from 20 minutes to 2 by caching intermediate results in Python" is a benefit. Show outcomes and scope, not duties.
How it works
Structure of a one-page resume
For students and early-career engineers, one page is the norm. A common order:
- Header: name, email, location (city is enough), links to GitHub, LinkedIn, and portfolio. Skip photo, birth date, and full street address.
- Education: school, degree, graduation date. Add coursework or honors only if relevant. Early on, place it near the top.
- Experience: internships, jobs, research, or substantial volunteer work, newest first, 2 to 4 bullets each.
- Projects: two to four best ones with a one-line description, tech used, and a link.
- Skills: languages, tools, and technologies you can discuss with confidence. Only list what you would be comfortable being asked about.
Use a clean single-column layout with standard headings and a plain font. Automated screening tools and humans both read simple structure better than complex columns, icons, or graphics. Export to PDF unless asked otherwise.
The bullet formula
A strong bullet follows: action verb + what you did + how/with what + result or scale.
Before: "Worked on the backend for the school scheduling app."
After: "Built a REST API in Python and PostgreSQL for a course-scheduling app used by about 300 students, replacing a spreadsheet process and cutting schedule conflicts reported per term."
What changed: a specific verb (built), concrete technology, a real scale, and an outcome. If you do not have an exact figure, describe the effect honestly ("removed manual copying between three spreadsheets") rather than inventing a number. Never invent or inflate; interviewers will ask about every line.
More examples:
- Weak: "Responsible for testing." Stronger: "Added 40 automated unit tests to the billing module, catching two regressions before release."
- Weak: "Helped improve website speed." Stronger: "Reduced page load time by compressing images and lazy loading, measured with the browser's performance tools."
- Weak: "Participated in a hackathon." Stronger: "Built a working prototype in 24 hours with a team of three, handling the data pipeline and the demo."
Only use numbers that are true and that you can explain. Real details beat impressive vague ones.
Tailoring and keywords
Read the job description and mirror its relevant terms where they honestly apply (languages, frameworks, practices). Reorder bullets so the most relevant come first. A few minutes of tailoring per application beats sending one generic version everywhere. Do not stuff in skills you do not have.
Building a portfolio
A portfolio is a small set of projects a reader can open and understand quickly.
- Pick a few, polish them. Two or three finished projects beat ten abandoned ones.
- Solve a real problem, even a small one: a tool you use, a service for a club, a dataset you analyzed. Real use gives you stories and numbers.
- Write a good README. What it does, a screenshot or short demo, how to run it, key design decisions and trade-offs, and what you would improve. The README is often all a reviewer reads.
- Show engineering habits: tests, a clear commit history, small readable commits, and a working setup instructions that someone else can follow. See the Git lesson.
- Deploy it if you can, so a visitor can try it without installing anything.
- Keep the code clean. Remove secrets and credentials from the repository and its history, and delete dead experiments.
- Contribute to open source in small ways, such as documentation fixes or a bug fix. Merged contributions show you can work in someone else's codebase.
project README checklist
[ ] one-sentence purpose [ ] how to run (copy-paste commands)
[ ] screenshot / demo [ ] design decisions and trade-offs
[ ] tests and how to run them [ ] known limitations, next steps
Online presence
Keep your public profiles consistent with your resume: the same dates, titles, and project names. Pin your best repositories, write a short professional bio, and make your email easy to find. Review privacy settings and what appears when someone searches your name.
Cover letters and outreach
If a cover letter is optional, a short, specific one can help: why this team, one relevant accomplishment, and a clear sign-off. When reaching out to someone, be brief, specific, and respectful of their time, and make a small, easy ask.
Common pitfalls
- Duty lists instead of impact. "Responsible for" says what the job was, not what you achieved.
- Inflated or invented claims. They collapse in the interview and damage trust.
- Skills you cannot discuss. If it is on your resume, expect questions about it.
- A wall of text. Dense paragraphs get skipped. Use short bullets with white space.
- Typos and inconsistent formatting. They suggest carelessness. Proofread and have someone else read it.
- Dead links and empty repos. Check every link, and make sure repositories have a README.
- Secrets in public code. API keys committed to a repository can be harvested. Rotate any key that ever appeared.
- Tutorial projects presented as original work. If you followed a tutorial, say so and extend it with your own feature.
Practice
Rewrite this bullet easy
Hint
Use action verb, what, how, and result. Keep it honest.
Show solution
Original: "Did data stuff for a class project." Rewrite using what you actually did, for example: "Cleaned and analyzed a 50,000-row public transit dataset with Python and pandas, identifying the three routes with the longest average delays and presenting findings to the class." Replace the details with your own true ones; the structure is what matters.
Turn duties into outcomes medium
Hint
Ask 'so what changed because of my work?' for each duty.
Show solution
Duty: "Maintained the club website." Questions: how many people used it, what did you improve, what broke before? Result: "Rebuilt the club website with a static site generator, reducing monthly hosting cost to zero and letting officers update event pages without developer help." If you cannot find an outcome, you may have found a project not worth a bullet.
Audit a project README medium
Hint
Pretend you are a stranger with two minutes.
Show solution
Open one of your repositories as a stranger. Can you tell what it does in one sentence, run it with copy-paste commands, and see what it looks like? Add what is missing: a purpose line, a screenshot, setup steps, a short "design decisions" section, and a limitations list.
Tailor for a job posting medium
Hint
Highlight overlap, do not fabricate.
Show solution
Take one job posting and underline its main requirements. Mark which of your projects or experiences honestly match each. Move those bullets to the top and mirror the posting's terminology where it is accurate. Where you have a gap, plan to address it in a project or mention that you are actively learning it.
Interview questions
- Walk me through your resume. Give a short narrative linking education, experiences, and projects to this role, highlighting the most relevant two or three items.
- Tell me about this project. Explain the problem, your role, one or two technical decisions and their trade-offs, and what you would do differently.
- What was the hardest bug you hit in it? Describe symptoms, how you investigated, root cause, and the fix.
- Why did you choose that technology? Give the real reasons and alternatives you considered, including constraints.
- What would you change if you rebuilt it? Show honest reflection and awareness of scaling or design limits.
Interviewers look for: depth behind every line, honest scope of your own contribution, and the ability to explain decisions rather than recite technologies.
Quick check
Which resume bullet is strongest?
Finished this lesson?
Further resources
- Résumé (Wikipedia) (article)
- Applicant tracking system (Wikipedia) (article)
- Cover letter (Wikipedia) (article)