Resume Building for Tech Roles

Icebreaker: "What's the worst resume advice you've ever heard?"

• "Make it creative with lots of colors and graphics"
• "Include your high school achievements"
• "List every skill you've ever touched"
• "Use fancy fonts to stand out"

Reality Check: Most resumes get 6 seconds of attention. What matters most?

Discussion: "What do you think recruiters look for first?"

The 6-Second Scan:

• Name and contact info (obviously)
• Current role/status (Student at JMU)
• Relevant experience or projects
• Technical skills that match the job

ATS (Applicant Tracking System) Friendly:

• Simple, clean formatting
• Standard section headers
• Keywords from job descriptions
• No images, graphics, or fancy formatting

One Page Rule:

• Students and new grads: Always one page
• Forces you to prioritize most important info
• Easier for recruiters to scan quickly
• Exception: Academic CVs (but that's different)

Activity: "Let's build a resume structure together"

Must-Have Sections:

• Header: Name, phone, email, LinkedIn, GitHub (if relevant)
• Education: School, degree, graduation date, GPA (if 3.5+)
• Experience: Jobs, internships, relevant work
• Projects: Personal, class, or team projects
• Skills: Technical skills, tools, languages

Optional Sections (if space allows):

• Leadership: Officer positions, team captain, etc.
• Awards: Scholarships, competitions, recognition
• Certifications: Relevant professional certifications
• Activities: Only if directly relevant to the role

What NOT to include: Objective statements, references, personal info, hobbies (unless relevant)

The Magic Formula: Action Verb + What You Did + Result/Impact

Strong Action Verbs:

• Leadership: Led, managed, coordinated, supervised
• Achievement: Achieved, improved, increased, reduced
• Creation: Developed, designed, built, created
• Analysis: Analyzed, researched, evaluated, assessed

Quantify Everything:

• Numbers: "Managed team of 5 people"
• Percentages: "Improved efficiency by 30%"
• Time: "Completed project 2 weeks ahead of schedule"
• Money: "Reduced costs by $10,000"

Before and After Examples:

Weak: "Worked on a website for a class project"

Strong: "Developed responsive e-commerce website using HTML, CSS, and JavaScript, serving 100+ users with 95% uptime"

Weak: "Helped customers at retail job"

Strong: "Provided customer service to 50+ daily customers, maintaining 4.8/5 satisfaction rating and resolving 95% of issues on first contact"

Question: "Should you list every programming language you've ever touched?"

Organize by Category:

• Programming Languages: Java, Python, JavaScript, C++
• Web Technologies: HTML, CSS, React, Node.js
• Databases: MySQL, PostgreSQL, MongoDB
• Tools & Platforms: Git, AWS, Docker, Linux

Proficiency Levels (Optional):

• Proficient: Can work independently
• Familiar: Have used but need guidance
• Experienced: Multiple projects, can teach others

Pro Tip: Only list skills you can talk about in an interview!

Why Projects Matter: They show you can actually build things!

What to Include:

• Personal projects you built for fun
• Class projects (if substantial)
• Hackathon projects
• Open source contributions

How to Describe Projects:

• Project Name: Give it a clear, descriptive name
• Technologies: What did you use to build it?
• Description: What does it do? What problem does it solve?
• Impact: Users, performance metrics, learning outcomes

Example Project Description:

"Personal Finance Tracker" - Built web application using React and Node.js to help students track expenses and budgets, featuring user authentication, data visualization, and automated categorization of transactions

Question: "What tools do you currently use to create documents?"

Recommended Tools:

• Google Docs: Easy collaboration, auto-save, accessible anywhere
• Microsoft Word: Professional templates, advanced formatting
• Canva: Beautiful templates, easy to use
• Overleaf (LaTeX): Perfect formatting, but steeper learning curve

Formatting Best Practices:

• Use standard fonts: Arial, Calibri, Times New Roman
• Font size: 10-12pt for body, 14-16pt for name
• Consistent spacing and alignment
• Plenty of white space - don't cram everything
• Save as PDF to preserve formatting

Let's Review Some Real Examples (Anonymized)

Formatting Mistakes:

• Using tables or columns (ATS can't read them)
• Fancy fonts or colors
• Including photos or graphics
• Inconsistent formatting

Content Mistakes:

• Listing responsibilities instead of achievements
• Using weak action verbs ("Helped with...")
• No quantification or specific details
• Including irrelevant information

Technical Mistakes:

• Listing skills you can't discuss
• No GitHub or portfolio links
• Outdated or broken contact information
• Typos and grammatical errors

Hands-On Activity: Let's improve real resumes together

Peer Review Process:

1. Partner up with someone
2. Exchange resumes (or drafts)
3. Use our checklist to review
4. Provide specific, actionable feedback
5. Discuss improvements together

Review Checklist:

• Is it easy to scan in 6 seconds?
• Are bullet points action-oriented and quantified?
• Is the formatting clean and consistent?
• Are technical skills relevant and accurate?
• Do projects show real impact?

Going Beyond the Basics

ATS Keyword Optimization:

• Job Description Analysis: Identify 10-15 key terms from each job posting
• Natural Integration: Weave keywords into bullet points naturally
• Skill Matching: Use exact terminology from job requirements
• Industry Buzzwords: Include relevant technical terms and methodologies
• Acronym Strategy: Use both full terms and acronyms (e.g., "Machine Learning (ML)")

Example Keyword Integration:

Job Requirement: "Experience with React, Node.js, and RESTful APIs"

Resume Bullet: "Developed full-stack web application using React frontend and Node.js backend, integrating RESTful APIs to serve 500+ daily users"

Tailoring for Different Roles:

• Software Engineering: Emphasize coding projects, algorithms, system design
• Data Science: Highlight statistical analysis, machine learning, data visualization
• Product Management: Focus on user research, project coordination, business impact
• UX Design: Showcase design process, user testing, prototyping tools

Industry-Specific Resume Templates:

Software Engineering Resume Structure:

1. Header with GitHub and portfolio links
2. Technical Skills (programming languages, frameworks, tools)
3. Projects (3-4 detailed technical projects)
4. Experience (internships, relevant work)
5. Education (degree, relevant coursework, GPA if 3.5+)

Data Science Resume Structure:

1. Header with GitHub and portfolio/blog links
2. Technical Skills (languages, libraries, statistical methods)
3. Projects (data analysis, ML models, visualizations)
4. Experience (research, internships, relevant work)
5. Education (degree, relevant coursework, certifications)

Making Your Achievements Measurable

Types of Metrics to Track:

• Performance Metrics: Speed improvements, efficiency gains, error reduction
• Scale Metrics: Number of users, data processed, transactions handled
• Business Metrics: Cost savings, revenue impact, time saved
• Quality Metrics: Test coverage, uptime, user satisfaction scores
• Team Metrics: People managed, projects coordinated, stakeholders engaged

Before & After Quantification Examples:

Weak: "Built a mobile app for a class project"

Strong: "Developed iOS mobile app using Swift and Core Data, achieving 4.8/5 App Store rating with 200+ downloads and 95% crash-free sessions"

Weak: "Worked as a teaching assistant"

Strong: "Mentored 25 students in Data Structures course, improving average exam scores by 15% and maintaining 4.9/5 student evaluation rating"

Weak: "Participated in hackathon"

Strong: "Led 4-person team to 2nd place finish at 48-hour hackathon, developing machine learning solution that processed 10,000+ data points with 87% accuracy"

Weak: "Improved website performance"

Strong: "Optimized website performance by implementing lazy loading and code splitting, reducing page load time by 40% and increasing user engagement by 25%"

When You Don't Have Numbers:

• Estimate Reasonably: "Approximately 50 users" is better than no number
• Use Relative Terms: "Significantly improved," "substantially reduced"
• Focus on Scope: "Enterprise-level application," "production environment"
• Highlight Complexity: "Multi-threaded application," "real-time data processing"

Understanding the Recruiter's Perspective

What Recruiters Look For (In Order):

1. Relevant Experience: Do they have the background we need?
2. Technical Skills: Can they do the technical work?
3. Education: Do they have the foundational knowledge?
4. Cultural Fit Indicators: Will they work well with our team?
5. Growth Potential: Can they learn and advance?

Insider Recruiter Insights:

What Recruiters Really Think:

• "Red Flags": Typos, inconsistent dates, job hopping without explanation
• "Green Flags": Clear progression, relevant projects, quantified achievements
• "Neutral Factors": GPA (unless very high/low), school prestige (less important than you think)
• "Attention Grabbers": Unique projects, impressive metrics, relevant side projects

Common Recruiter Questions:

• "Can this person actually do the job?"
• "Will they fit with our team culture?"
• "Are they genuinely interested in this role/company?"
• "Do they have the potential to grow?"

Standing Out in the Stack:

• Lead with Impact: Start bullet points with results, not tasks
• Show Progression: Demonstrate growth over time
• Be Specific: Avoid generic statements that could apply to anyone
• Tell a Story: Create a narrative of your professional development

Adapting Your Resume for Different Contexts

Online Applications (ATS-Optimized):

• Simple Formatting: No tables, columns, or graphics
• Standard Fonts: Arial, Calibri, Times New Roman
• Keyword Rich: Include exact terms from job description
• Standard Headings: "Experience," "Education," "Skills"
• PDF Format: Preserves formatting across systems

Networking/Referral Submissions:

• Personal Touch: Can include brief personal note
• Storytelling: More narrative elements allowed
• Relationship Context: Mention mutual connections
• Conversation Starters: Include interesting projects or experiences

Career Fair/In-Person:

• Visual Appeal: Clean, professional appearance
• Conversation Guide: Easy to discuss key points
• Contact Emphasis: Make it easy to follow up
• Multiple Copies: Bring extras for multiple conversations

Strategic Application Approach:

The 3-Resume Strategy:

1. Master Resume: Comprehensive 2-page version with everything
2. ATS Resume: Optimized 1-page version for online applications
3. Networking Resume: Conversation-friendly version for in-person meetings

Customization Levels:

• Level 1 (5 minutes): Adjust skills section and summary
• Level 2 (15 minutes): Reorder sections and modify bullet points
• Level 3 (30 minutes): Rewrite key sections for specific role

Creating a Sustainable Resume Management Process

Documentation Strategy:

• Achievement Bank: Ongoing list of accomplishments with metrics
• Project Library: Detailed descriptions of all projects
• Skill Inventory: Comprehensive list of technical and soft skills
• Experience Archive: Full descriptions of all work experiences

Version Control for Resumes:

• Master Template: Base version with all possible content
• Role-Specific Versions: Customized for different job types
• Company-Specific Versions: Tailored for specific applications
• Date Tracking: Keep track of when and where you applied

Continuous Improvement Process:

• Monthly Reviews: Update with new experiences and skills
• Feedback Integration: Incorporate suggestions from mentors and peers
• Performance Tracking: Monitor application success rates
• Industry Updates: Stay current with resume trends and best practices

Update your resume using what we covered today. If you don't have one yet, build one from scratch. Once it's done, send it to one person — a friend, a mentor, anyone — and ask for honest feedback before the next meeting.

Not mandatory, but a polished resume is the thing standing between you and your first interview. Don't wait until application season to build it.

Submit through the Homework tab when done.