Mod 2 Week 1 Creating a Technically Focused Resume

Learning Goals

  • Understand how to tell your professional story through your resume
  • Build a working draft of your resume that is both technically focused ATS Friendly

After you complete this lesson, you’ll synthesize your learning in this Exit Ticket.

Overview

This PD lesson will focus on creating a technically focused resume that represents your unique professional brand as a career changer and experienced turned software developer. Your resume draft will include most of the following resume sections:

  • Customized header with contact details, title, and optional headline
  • Optional Resume summary to connect the dots as a career changer
  • Skills and Keywords that are industry-specific
  • Technical Projects that have consistent formats and show accomplishments
  • Education section that includes Turing’s Certificate of Completion

  • Directions
    • As you follow along, we recommend taking notes.
    • Allow yourself about 30 mins (each video is between one and three minutes) to complete the video portion of the following lesson.
    • We recommend scheduling time on your calendar and using dedicated PD work time to complete the entire lesson.

Intro to Creating a Techically Focused Resume

As a new software developer, what kind of story do you want your resume to tell about you?

Section 1: Contents of a Technical Resume include:

  1. Contact information, title, and headline (optional)
  2. Resume Summary (optional)
  3. Skils and Keywords
  4. Technical Projects
  5. Work Experience
  6. Education and Training

Section 1: Contact Information,Title and Headline

Your desired job title is one of the most essential keywords applicant tracking system’s when screening resumes.

Section 2: Resume Summary (optional)

The Summary section is optional; however, it can be strategically used as a career changer to connect the dots for an employer to explain career change and the value you will bring to the Company and role.

If you’re considering a summary statement:

  • Think about what relevant and novel information you can provide the employer.
  • Which transferable skills matter to this role?
  • What’s your zone of genius? Where do you gain energy in your work? What impact do you want to have in this role/company?

Section 3: Skills and Keywords

A good rule of thumb is only include the technical skills you’re comfortable talking about in an interview.

Section 4: Technical Projects

Since you are a software developer now, your software projects are essential – arguably, the most vital – part of your new resume.

Projects overviews should also include accomplishments, outcomes and results:

  • What was your role in the project?
  • What specific goals did you meet?
  • What was the result/impact of your project/work?

Section 5: Work Experience

  • Think of your bullets points as Storytelling -Short, accomplishment stories.
  • Quantify impact with a #, % or $ amount whenever possible. I did X and the result was Y; state the result or outcome.

Section 6: Education and Training

Creating an “Education and Training” section will help showcase your developer training and highlight your transferable qualifications.

Section 7: Complying with the Applicant Tracking System (ATS)

Next Steps:

  • Complete this exit ticket. Completion of this exit ticket is required for your professional development this module.

  • Create a resume first draft with these steps to get started:

  • First, plan the framework of your resume based on the lesson:
    • Will you use a resume summary?
    • What relevant work experience will be used?
    • Which prior education and training will be added?
    • Which industry specifc skills are most important right now to add?
  • Next, choose a resume template:
    • Pick an ATS-friendly template with Job Scan Template.These templates will download as Word docs. You can either cut and paste it or upload it to google doc.
    • We recommend that you review this ATS Friendly Template
  • Then, develop a rough draft of your resume:
    • Use this resume checklist to guide your draft development.
    • Include technical projects on your resume. Consider some of the projects you’ve completed so far in the program to help you construct your bulleted descriptions (you can switch them out later for other projects, but you should become comfortable with describing them concisely).
  • When describing projects, consider the following:
    • Name of the project (group/solo/pair)- URL (hyperlinked)
    • Time spent on the project (hours, days, or weeks)
    • Describe the project briefly. What does it do?
    • Bullet points should include action verbs, tasks, and results:
      • Describe one aspect of how the project was built.
      • Share another example of how the project was created.
      • Describe the method, process, or workflow.
      • In groups, how did you contribute?
      • Describe the technology stack you used.
  • Resources

Check for Understanding and Due Dates

  • Complete the exit ticket for today’s lesson by EOD Friday of Week 1.
  • During your Homeroom Group you’ll discuss more in-depth how to create an effective resume. You should have an ATS-ready (read: plain, straightforward information), 1-page version of a resume that includes at least 2 software projects and a list of technical skills to submit by EOD Friday of Week 2.

  • Professional Coaching:
    • What is professional coaching? Sometimes referred to as “career therapy,” coaching provides you with the opportunity for thought partnership on goals that you have for your career. What topics could be covered? Whatever you want! Some popular topics are:
      • Stress management
      • Organization and time management
      • Career transition guidance
      • Using your Pairin data for growth
    • You can sign up for small group coaching sessions with Emma here.
    • If you’d like to get additional reports on your Pairin strengths, reach out to Allison on Slack (@allison_reu_singer).