1. A two-line summary that names the stack and the target

"Computer science graduate (2026) with two shipped Django projects and a summer internship in QA automation, looking for a backend role." Concrete nouns, no adjectives about passion.

2. Projects as if they were jobs

Title, dates, one line on what it does, two or three bullets on what you did: the decision you made, the bug you found, the thing you measured. "Built a REST API" is a task. "Cut the median response time of the search endpoint from 900 ms to 120 ms by adding an index and a cache" is an outcome. Include a link to the repository and to the deployed app if it is live.

3. Internships, part-time and volunteer work, including non-technical ones

A cashier job proves reliability; put it in one line at the bottom, not in the middle.

4. Education with the courses that matter for the role

Operating Systems, Databases, Distributed Systems; not Intro to Psychology. GPA only if it is above 3.5.

5. Skills, grouped and honest

Languages, frameworks, tools. Do not list something you could not answer a basic question about in an interview.

What to leave out

An objective paragraph, a photo, "References available on request", a skills bar chart, and any technology you used once in a tutorial.

Format

One page, one column, standard headings. Entry-level resumes are read by tracking systems first, and columns and icons are exactly what breaks them.

If you want to see fourteen versions of this structure filled in, OwlApply has entry-level software engineer resume examples (entry-level, junior, intern, junior full-stack, iOS, Android, junior ML, entry-level data engineer). Each opens in the editor free of charge; exporting the finished PDF is on the paid plan. I am the founder, so treat the link as a founder's suggestion and the advice above as the part you can use without it.