Software engineer resume for freshers, with a sample

What engineering recruiters read first

Whether it is a campus drive or an off-campus application, a recruiter spends a short time on each resume. For freshers, the eye goes to the college and CGPA, then to any internship, then to projects and the tech stack. Make those easy to find and easy to believe.

Believable means specific. "Built a full-stack web app" could mean anything. "Built an expense-splitting app in React and Node.js with PostgreSQL; 150 users from my hostel" tells the reader what you built, with what, and that people used it.

Projects: your most important section

• Pick two to four projects. One you built well beats five tutorials you followed.
• For each, write the name, the stack and a link to the code, then one to three lines on what it does and what you did.
• Show engineering decisions: why you chose a queue, how you made a query faster, how you tested it.
• Mention real users or real data if there were any. A college club using your app counts.
• Make sure the GitHub link works and the README explains how to run it. Interviewers do click.

Skills: group them, and be ready to defend each one

Group your skills into languages, frameworks and tools. List only what you could answer questions on in an interview. If you put "Docker" on your resume, expect to be asked what a container is and how you used one.

Leave out skill bars, ratings and soft skills like "team player". Show teamwork in your project and internship lines instead.

Coding profiles and achievements

If you have a LeetCode, Codeforces or CodeChef profile with real activity, link it in your contact line and add your rating or problem count under achievements. Hackathon results and ranks also go here. Use exact figures, because interviewers sometimes check.

If you don't have a strong profile, don't add a link to an empty one. Your projects can carry the resume.

Internships and experience

Write internship lines the same way as project lines: what you changed, in which system, with which tools, and the result. "Worked on backend" says nothing. "Added webhook retries to the payments service in Go" gives the interviewer something to ask about, which is what you want.

If you have no internship, that is common for freshers. Open-source contributions, freelance work for a local business or a teaching assistant role can fill the space honestly.

Format and length

• One page, single column. The Jake's Resume layout (our Ledger template) is popular for a reason: it fits a lot without looking cramped.
• Education at the top while you are a fresher, with CGPA. Add Class 10 and 12 if the company's drive asks for them.
• No photo, no date of birth, no objective statement.
• Export a text-based PDF and name the file with your name, for example Neha-Reddy-Resume.pdf.

After the resume: the coding round

A good resume gets you to the interview, where you will be asked to write code and explain the projects on your resume. Practise both out loud. Octrahire's practice interview includes a coding round where you write code, then explain and defend your solution, and your first interview is free.