Your technical resume is a 1-2 page persuasive document that showcases your relevant technical and interpersonal skills, including what you have learned in Ada and any transferable prior experience or education. Your resume communicates your fit for a role to employers, and helps networking connections learn about your background.
Purpose of Your Resume
Your technical resume is a 1-2 page document that:
Curates your technical skills and what you have learned at Ada and your internship, as well as any transferable previous experiences.
Has similar content to resumes you may have made before, such as “Experience” (sometimes broken up into "Technical Experience" and "Additional Experience"), “Education,” and "Skills," and also the tech-specific section of “Projects” (for a curated selection of your Capstone and 1-2 Classroom or personal projects).
Is cleanly formatted and easy to skim in 7 seconds. If you were a stranger, would you be able to tell what job this resume is meant to apply for, just by looking for 7 seconds?
Aim For
Readability: Make choices that are predictable, legible, and help the reader. For example, it could be self-defeating to squeeze in all your information with a smaller text size, if it's hard to read.
Clear order of priority: The most important information about your relevant skills and experiences, should go up higher on the page. For example, instead of one "Experience" section with all of your work history, consider breaking this up into "Technical Experience" near the top of the page and "Additional Experience" lower on the page.
Qualitative and quantitative details: Descriptive or numbers-based details (even estimates) will help explain the scope and impact of what you did or made.
Own Your Resume
You are the final decision maker of your resume. You will always make the final choices about your resume and what you include. If you ask, "Should I include or remove X?", look for answers that explain the reasons and impacts to how your resume is received by a human recruiter or reviewer. You will get different or conflicting advice, which is why it is important for you to become comfortable making a personal choice and to know the reason why.
Ada Session Materials
C23 Resume Foundations (Career Retreat) - Slide Deck
C22 Building Your Tech Resume (Career Week) - Slide Deck
Resume Templates
Template 3 by The Pragmatic Engineer
Template 4 by Sourabh Bajaj
Sample Resumes
Self Review - Resume Review Rubrics
Prioritize Content and Readability
Use a standard document editor such as Google Docs or Word.
Avoid Powerpoint, Canva, Figma, InDesign, and other templates with complex tables and formatting. These editors usually don’t export ATS-friendly PDFs.
Employers read resumes from Top to Bottom, and only sometimes Left to Right, in an “E” shape. (Source)
Going down the left hand side from top to bottom, an employer tends to scan down your job titles and experiences on the left, then read over towards the right in sections that seem interesting or relevant to gaining a rapid sense of your skills and past achievements.
Include reasonably spacious margins and white space to make your content easier to scan.
Employers spend as little as 7 seconds (< a minute) reading a resume. (Source) Many factors affect this, such as the number of total applications (also known as the candidate pool) for a position, or if the resume was submitted via a referral.
On a multi-page resume, the most important content should be on the front of the first page. There is no guarantee 2nd+ pages will be read.
2 column resumes are not recommended due to ATS compatibility. (Source) However, you can still use a 2 column resume if you know it will be reviewed by a human and not an ATS first.
Intentionally Structure and Order Your Sections
Resume content is organized into sections/categories of different ways you’ve gained skills or experiences, such as “Education” or “Work Experience.”
Choose sections and a section order that puts your most relevant technical experiences and education first, followed by transferable experiences.
Section titles should be short and digestible. Aim for no more than 2-3 words per title that clearly summarize the content.
View sample resume sections and order, on Ada’s Resume Templates (Template 1, Template 2).
Make Clear Impact Statements
Resume bullet points (especially in the Experiences and Projects sections) should go beyond “general responsibilities” to describe real-world results of your work. In a position description, job responsibilities are hypothetical and subject to change. However, once you are in a role or project, you have more unique contextual details about your working style and how you executed.
Strong impact statements:
Start with active verbs.
Explain the scope and context of responsibilities, features, or tasks.
Describe the tools and technologies you used, and how you utilized them.
Include quantitative or qualitative metrics to measure your contribution/results.
An “impact statement framework” can help you evaluate and write out resume bullet points to ensure they include all of the above points. You will use it to:
Draft out your accomplishments, then select the 3-5 most relevant and ensure they contain Impact, Results, and Your Contribution.
Break down a project into digestible steps to better show the viewer your process.
More easily adapt position description bullets into impact statements, as most position description bullets are written as Action Verb-Context but lack Results.
Show when you went above and beyond on unique projects, even if they weren’t listed under your job duties.
Below are some example frameworks and impact statements. Choose the framework that makes the most sense to you.
Example Impact Statements
Framework #1: A-C-R or C-A-R
A = ACTION VERB that describes what you did
C = CONTEXT for the situation/problem or skills and tools you used
R = RESULTS in terms of how you created a positive impact or change for the employer/stakeholders
Sample ACR/CAR statement:
Action, Context, Results
“Led a team of 3 developers to build a dependency injection framework that was adopted by 15 teams and all 50+ developers at the company”
Framework #2: W-H-O
W = WHAT did you do (tasks/projects), starting with an action verb
H = HOW did you do the work (skills, strategies, methods, tools, including stakeholders you collaborated with)
O = OUTCOMES associated with the work (results, contribution, intention, scope)
Sample WHO statement:
What, How, Outcomes
“Created a mobile app using React Native, Firebase, and Javascript to enable outdoor enthusiasts to plan, share, and review hiking routes.”
Framework #3: S-T-A-R
Note the STAR framework is effective to answer behavioral interview questions, but not every interview STAR story is an achievement that is significant enough to also take up resume space.
SITUATION / TASK = A specific, challenging, work-related SITUATION that you resolved or TASK you were faced with
ACTION = The ACTION steps you took to resolve the issue or complete the task
RESULT = The positive RESULT of your actions, ideally with a quantifiable or qualitative measure
Sample STAR statement:
Situation/Task, Action, Result
“Spearheaded 20+ page website revision via cross-functional meetings, content prototyping in Miro, and tracking deliverables in Excel, expanding DEI-focused content and resulting in a 50% weekly visitor increase.”
Why Tailor Your Resume?
The resume is a living document and is not one-size-fits-all-jobs. Resumes should be tailored to each job, to increase chances of passing ATS and gain employer interest. Even 5 minutes spent tailoring will increase your chances of showing recruiters that you care about that specific role/team/company, and that your skills are a compelling fit.
Tailoring is the act of editing resume content to prioritize the most relevant experiences and skills related to a specific position description, and incorporating keywords in context. Examples of tailoring actions include rearranging bullet points or sections, curating experiences to remove or add the most relevant past jobs/projects, or changing bullet point language to match keywords.
Keywords are pieces of language (skills, qualifications, traits, themes) in a position description or employer content (website, company description, mission, values, etc). The more you integrate keywords that make sense in context, the more tailored your resume is to that role.
Steps for Tailoring
Review the position description:
Highlight, color code, or underline any key phrases, verbs, qualifications, repeating language that is related to actions, skills, or competencies the employer desires, and that you have.
Create a new version of your resume for the specific job description:
Assess the order of your sections and the specific Experiences/Projects you have chosen to include. Do the order and selected experiences match the priorities of the employer, such as showcasing projects that use a similar tech stack, or including prior career experiences that show transferable skills or aligned values?
Identify places within your content where you can use similar or the same phrases and verbs, such as adapting a job title to better explain what your responsibilities were (for example, Coordinator vs. Manager, or Coach vs. Advisor). Changes should not misrepresent your work. Your responsibilities, tools, and impact must still be clear.
Compare both documents:
Use a free resume scanning service (Teal, Resume Worded, ResyMatch.io, Jobscan, Skillroads) to get external feedback on your keyword matches and how an ATS may rate your resume.
Manually check the two documents, especially your highlights in the position description, to ensure all of the keywords and qualifications are addressed.
Ada Session Materials
Resources:
Who else can I ask for feedback?
Peers: Exchange constructive feedback with other Adies who know your work well and can help you better describe your achievements and skills.
Ada alumni: Gain the perspective and lessons learned of someone who has gone through the bootcamp experience and/or also changed careers. This can be seen as a favor/"homework," so try to establish a connection first by sending a thoughtful message or requesting an informational interview/short chat first.
Mentors: Resume review is a great topic for 1:1 chats or meetings. Mentors may have past hiring experience or a stronger idea of what skills/experiences are desirable at their particular company.
Recruiters, HR, and anyone else whose expertise you want to invite: This can range from non-mentor teammates at Internship, to resume review opportunities sometimes offered at career fairs, conferences, and other tech events and programs. In any case where you’re seeking feedback, think about why you would trust their advice and what perspective or background they bring.
Who shouldn’t I ask?
Friends or family, unless they have relevant industry or hiring experience.
We recommend avoiding paid resume review services due to the number of free resources available.
What kind of feedback should I accept?
No matter the reviewer or context, useful feedback should give you an idea of what is working, what you could change, and how those changes could make your resume more persuasive or easier to read. For example:
Can the resume be scanned for key points in under a minute? If yes, what are the key points the reviewer sees or would like to see, compared to the key points you are hoping to communicate?
Is an issue related to formatting, content, or both?
Can the reviewer give an example of a time that their suggestion(s) helped them or another person in a job search?
Give the reviewer direction on what feedback to provide, such as by asking how well your resume aligns with a certain company or role and why, or ask questions about specific sections/attributes of your resume such as whether you have explained gaps in job history coherently.
How do I ask?
Build a relationship first: Similar to job referrals, others are more likely to agree to review your materials, and to feel respected as colleagues/peers, if they get to know you briefly before you ask.
Request during networking chats: If you feel a networking conversation is going well, finding an appropriate time to ask (often closer to the end of the chat) can show you value the other person’s perspective. Use what you have learned about them throughout the conversation, to justify your interest in their feedback.
Sample resume review requests: Use these examples to help find your own words!
Email Script - Prior Connection: “Hi Ada! It was great to meet you at the Out in Tech networking mixer last week. I loved learning how you pivoted into tech to find a more inclusive workplace. Would you be willing to chat about your experience and briefly look over my resume sometime? I am also a career changer seeking a queer-friendly workplace. Please let me know - I would be happy to share my resume or grab coffee at a time that’s convenient for you.”
Conversation Script: “Thank you so much for chatting with me! I loved hearing about your career journey. I notice we have maybe 10 minutes left in our coffee chat time. I was wondering if you would be open to give your opinion about my resume? I’m excited by what you’ve shared about working on accessibility at Hulu and I have a position in mind I’m applying to this week. I would appreciate any advice you have about my materials.”
How do I respond when reviewers give me different or conflicting feedback?
It happens, all the time! Reviewers give subjective opinions based on their own experiences. For example, a senior engineer with 10+ years of experience may give feedback based on how they were hired into junior roles in the past, or what they look for when hiring now. A recruiter may give feedback based on labor market trends and company hiring practices. Two people who work at the same company may give different feedback because they have different teams or tech stacks.
Examine the “why” (reasoning for the feedback), and put their feedback in context of your relationship, such as if the reviewer works at a company you’re applying to, or if there is a power dynamic between you and the reviewer. Consider: Does this make their advice seem more or less relevant? Is it general feedback, or specific to this version of your resume? Then decide what changes you want to make.
Ada Resources
Create a “Principal copy”
A ‘Principal Resume’ or ‘Main Copy’ contains all of your past work experience, projects, volunteering, and education and may be several pages long.
A principal resume should be used as a starting place for a tailored resume. Tech hiring does not expect you to disclose your entire working history, and often, a 1-2 page resume is preferred.
When tailoring to a job description, your principal copy will help you edit, add, and remove content more quickly since nothing is ever permanently deleted.
Your LinkedIn profile can also double as a principal/main copy.
Gather a list of achievements/metrics during the project/role
It's hard to remember your accomplishments after you've left a job or finished a project, so gathering even a few quick notes while you are working helps your future self. This can look like a work log, 1:1 notes, a ‘wins list,’ manager/mentor explanations of why what you are building is helpful to the larger team, and more. Note successes, growth, and concrete numbers while you still have access to your work. This way, you can more easily add or edit these details on your resume later.
Create strong project documentation
Publish projects with good READMEs on your Github page.
Aim for the README to have a good summary, screenshots, details on how to run, and how to test.
Take inspiration from these curated projects with awesome READMEs.
Have Demos that can be viewed, and/or Tests for your project that can be run.
To learn more about this, see the Learn Test Driven Development resource.
If you have tests in your project, add a “Running tests” section on your README, to make it clear how anyone can run these.
For an example on how to document running tests, see how this is done in Leaflet.
The below outside resources have been curated by Ada Student Support in order to support Ada interns to create and update entry-level technical resumes.
Note: We don't recommend Canva for resumes because Canva PDFs can be challenging for screen readers and ATS software to read. Other tools with high design focus, like Figma, can have the same issue.
Resume scanning services use software to compare your resume against common resume mistakes or a position description you choose, for keywords and relevance. While manually tailoring your resume is an important skill, these services can help improve your ability to identify keywords and edit materials for clarity.
Jobscan - 2 free scans per month
Skillroads - Free scans require account registration
Your action verbs should aim for clarity, not uniqueness. They should be tailored to the verbs and keywords in each position description. Use these lists to identify clearer, not fancier, verbs to better describe your past experiences.
Action Verbs for Resumes (Includes lists of verbs to replace common phrases such as “Responsible for”)
Action Words for Engineering (Cornell University) (Sorted by Skill category)
These are standing resources that should be used in addition to networking chats and your Ada community. When using online resources, remove/anonymize personal information!
Reddit has regular resume advice threads on CS Career questions. This forum is meant for new grads.
Reddit has a general resume review sub where you can get resume feedback.
Search for resume review offers from fellow members of the tech community. Dev.to had a resume review thread and people occasionally offer to give feedback on Twitter and on LinkedIn.
General Advice
Sections and Content
How to Structure Your Software Engineering Resume (Interview Kickstart) (See section, “How to Create the Right Sections for a Software Engineer Resume”)
Resume Review Feedback
Research