Preface

At Strategic Data Systems, we review hundreds of developer resumes each year. Whether you’re looking for a consulting role with one of our Fortune 500 clients or hoping to grow your career in software development, your resume is your foot in the door. We’re always looking for developers who combine technical skills with clear communication, and a well-crafted resume demonstrates both.

This blog post summarizes insights shared by Conner Ardman, a former Facebook software engineer and popular YouTuber, in this video. Based on our experience reviewing developer resumes at Strategic Data Systems, we’ve added our own commentary and interpretation.

Essential Tips to Improve Your Tech Resume

When landing your dream software engineering job, your resume is often the first, and sometimes the only, chance you have to make a great impression. Conner Ardman, a former FAANG software engineer, offers invaluable advice on how to craft a resume that stands out to recruiters and hiring managers. Drawing from his extensive experience, Ardman meticulously critiques several real-world resumes, highlighting what works and what doesn’t and how to optimize every section for maximum impact.

In this article, I’ll distill Conner’s insights and provide a comprehensive guide to improving your software engineering resume. Whether you’re a new grad, an intern, or a seasoned developer, these tips will help you present your skills and experience clearly and professionally, increasing your chances of landing interviews at top tech companies.

Why Resume Format and Clarity Matter

One of the first things Ardman points out is the importance of a clean, simple resume layout. While creating a visually flashy design to showcase your frontend or design skills can be tempting, simplicity often wins the day. Recruiters typically spend less than a minute scanning each resume, so your resume must be easy to read and parse.

Additionally, many companies use Applicant Tracking Systems (ATS), which automatically scans and ranks resumes. Complex formatting can confuse these systems and cause your resume to be rejected before a human sees it. Ardman recommends testing your resume’s readability by copying all text from the PDF version and pasting it into a basic text editor. This simple step helps ensure the resume content remains intact and in the correct order, which is crucial for ATS compatibility.

Resume Header: What to Include and How to Brand Yourself

The resume header is your first impression, so it needs to be clear and professional. Ardman advises against overly specific job titles in the header, like “React/frontend developer.” While React is a valuable skill, labeling yourself strictly as a React developer can pigeonhole you. Instead, use broader terms like “Frontend Developer” or create multiple versions of your resume tailored to the job description.

Contact information should be straightforward, including your name, phone number, email, LinkedIn, GitHub, and location. Be mindful of the email address you use. Ardman shares a cautionary tale about using a university (.edu) email you might lose access to after graduation. Instead, a stable Gmail account is safer for maintaining long-term professional connections.

Work Experience: Prioritize Clarity, Chronology, and Impact

Work experience is the heart of your resume. Ardman stresses the importance of ordering your jobs in reverse chronological order, with the most recent position at the top. Chronological ordering helps recruiters quickly see your current role and relevant skills.

Each job should have bullet points that start with strong action verbs and quantify achievements where possible. For example, instead of saying “Optimized React components,” a better bullet might be “Reduced response time by 20% through optimizing REST API calls and React component rendering.” Specificity matters because generic statements like “Worked on React projects” don’t convey the scope or impact of your work.

Ardman also suggests avoiding mission statements or company “selling points” within your experience section. Describing what the company does is fine, but keep it concise and factual rather than promotional.

Project Descriptions: Separate Personal Projects from Work Projects. Many resumes include a projects section, but Ardman highlights a common confusion when work projects are listed alongside personal or academic projects. All work-related projects should be integrated into the respective work experience bullet points to keep your resume organized.

The projects section should be reserved for personal, hackathon, or coursework projects. This separation clarifies what you accomplished independently versus as part of a team or company.

Education: Highlight Relevant Coursework and GPA Wisely

Education is more than just your degree and graduation date. Ardman recommends listing relevant coursework to demonstrate your technical foundation, especially classes like “Data Structures and Algorithms,” which are crucial for coding interviews.

When it comes to GPA, use discretion. If your GPA is below 3.0 on a 4.0 scale, it’s better to omit it. For GPAs between 3.0 and 3.5, including your GPA won’t harm but probably won’t significantly help. If your GPA is above 3.5, include it to highlight your academic excellence.

For candidates with multiple degrees, consider whether to list GPA based on consistency. If one GPA is high and the other is low, it might be better to omit both to avoid raising questions.

Skills Section: Organize for Quick Scanning

A well-organized skills section can quickly communicate your technical competencies. Ardman suggests grouping skills into categories such as:

• Programming Languages (e.g., JavaScript, TypeScript)
• Frameworks and Libraries (e.g., React, Node.js)
• Developer Tools (e.g., Docker, VS Code)
• Databases and APIs (e.g., MongoDB, RESTful APIs)

This structure helps recruiters quickly identify your core strengths. Avoid listing overly generic tools like text editors (e.g., VS Code, PyCharm) as “skills” since most developers use these by default.

Also, be precise with categories. For example, REST APIs are not frameworks but a type of interface; Agile methodologies are processes, not tools or frameworks. Clarity here demonstrates attention to detail.

Additional Sections: Open Source, Certifications, and Leadership

Including open-source contributions can set you apart, but formatting matters. Ardman notes that lumping multiple contributions under one date or section can be confusing. Instead, list each contribution separately with clear dates and descriptions.

Certifications like AWS Certified Developer add value but should include context so recruiters understand their significance. For instance, briefly explain what the certification entails or why it’s relevant to your role.

Leadership sections should represent actual leadership experiences, such as managing teams or organizing events. Winning a hackathon is impressive, but it fits better under projects rather than leadership unless you had a formal leadership role.

Common Mistakes to Avoid

• Summary Statements: These often take up valuable space and add little value since recruiters spend minimal time per resume. Instead, let your experience and skills speak for themselves.
• Inconsistent Formatting: Job titles, dates, and bullet points should be uniformly styled. Decide whether to capitalize job titles fully and stick with it.
• Wordy Paragraphs: Avoid long paragraphs, especially in work experience. Bullet points are easier to scan and more impactful.
• Unclear Project Descriptions: Always specify what technologies you used, what problems you solved, and the impact of your work.
• Unprofessional Email Addresses: Use a professional email, preferably Gmail, rather than outdated or university-specific emails to which you might lose access.
• Overloading Skills Sections: Avoid listing too many minor tools or text editors that do not differentiate you from other candidates.

Final Tips for Crafting a Winning Software Engineering Resume

Ultimately, your resume should be a clear, concise, and compelling document that tells the story of your skills and achievements. Here are some final takeaways inspired by Ardman’s critique:

• Keep it Simple: Use a clean, ATS-friendly layout that is easy for recruiters to skim.
• Be Specific: Quantify your accomplishments and explain the technologies and methodologies you used.
• Tailor Your Resume: Customize your title and skills for each application to match the job description.
• Proofread and Consistency: Ensure consistent formatting, spelling, and capitalization throughout.
• Prioritize Important Sections: Put your most recent and relevant experience at the top and highlight key coursework if you’re a recent graduate.
• Remove Fluff: Avoid generic statements, unnecessary paragraphs, and vague “core competencies” that don’t add measurable value.

By following these guidelines, you’ll create a resume that not only passes automated scans but also captures the attention of recruiters and hiring managers, increasing your chances of landing interviews and ultimately securing your next software engineering role.

 “Recruiters only spend about 30 seconds to a minute on your resume, so make every word count.” – Conner Ardman

Remember, your resume is a living document. Keep refining it based on feedback and evolving job requirements. And while a great resume is essential, it’s just one part of the journey. Building your skills, practicing coding interviews, and networking are equally important steps toward your career goals.

How does your resume look?

Strategic Data Systems works with a professional tech resume writer. Do you need help with your technical resume?  If so, send it to [email protected] with the subject “Review my resume,” and we will reformat it and suggest improvements to help you land that next great job!