The first step to software engineering recruitment is to have a solid resume. As you definitely know, make sure to emphasize impact in any of your experiences on your resume, and get many people to read it over.
is a great way to start. There is no need to make it pretty (unless you are applying to design roles).
Try to keep it to 1 page. Recruiters won’t spend much time looking at your resume, so list the important stuff that makes you stand out from other applicants.
You should list ~3 bullet points to describe each experience.
Make sure to include your up-to-date contact information at the top so the recruiters can contact you (email, phone number, etc.).
Don’t forget to spell check!
Submit it as a PDF to prevent weird formatting from occurring.
Structure
The way you structure your resume will depend on the amount of experience you have and how many projects you have worked on. Here is a possible resume structure from Google to help give you an idea of what tech companies are looking for:
Projects
Projects are super important for software engineering roles. These projects can include personal projects, previous coding internships, or projects you worked on in a hackathon. If you don’t have many of these other projects, class projects are also okay, but are not as well regarded. See
GPA is not everything. While GPA can be a good indication of whether you are smart, it is important to note that a bad GPA can harm you but a good GPA will not get you the job. In other words, a 3.9 GPA does not mean that you have a higher chance of getting a job than a 3.7 GPA. A decent GPA is merely a prerequisite, and after that, all that matters are your experiences and your technical expertise. Someone with a 3.7 GPA and many significant projects / internship experiences would be a stronger candidate than someone who has a 3.9 GPA and nothing else on their portfolio!