What Is a Career in Tech (And How Do You Get One)?
Lesson 1 — Wednesday, September 16, 2026 • King 150, 5:45–6:45 PM
Lesson Overview
This foundational lesson introduces students to the diverse landscape of technology careers and provides a roadmap for achieving their professional goals. We'll explore various career paths, understand different types of work experiences, and learn how to strategically plan your journey into tech.
Discussion Topics & Talking Points
Opening Question: What Does "Tech Career" Mean to You?
Discussion Starter: "When you hear 'tech career,' what's the first thing that comes to mind?"
- Many students think only of software engineering/coding
- Tech industry is much broader than just programming
- Every company is becoming a tech company
- Non-technical roles in tech companies often pay just as well
Key Point: Tech careers aren't just for computer science majors!
Major Career Paths in Technology
Question: "Who can name a tech job that doesn't involve coding?"
Technical Roles:
- Software Engineering: Building applications, websites, systems
- Data Science/Analytics: Making sense of data to drive decisions
- Cybersecurity: Protecting companies from digital threats
- DevOps/Cloud Engineering: Managing how software gets deployed
- Quality Assurance: Testing software to ensure it works
Non-Technical Roles:
- Product Management: Deciding what features to build and why
- UX/UI Design: Making technology easy and enjoyable to use
- Technical Sales: Helping companies buy the right technology
- Customer Success: Helping clients get value from tech products
- Technical Writing: Explaining complex technology clearly
- Business Analysis: Understanding business needs and tech solutions
Discussion: "Which of these sounds most interesting to you and why?"
Types of Work Experiences
Question: "What's the difference between an internship and a co-op?"
Internships (Most Common):
- Usually 10-12 weeks during summer
- Can be paid or unpaid (tech internships are usually paid well)
- Great for exploring different companies/roles
- Often lead to full-time job offers
Co-ops (Cooperative Education):
- Longer commitment (6 months to a year)
- Usually alternate semesters (work, school, work, school)
- Deeper experience, more responsibility
- Common in engineering programs
Research Opportunities:
- Work with professors on research projects
- Great for students considering graduate school
- Can lead to publications and conference presentations
- Often unpaid but valuable for academic careers
Key Point: "Any experience is better than no experience!"
Reverse-Engineering Your Career Goals
Activity: "Let's walk through this process together."
Step 1: Pick a Dream Job
- What role do you want in 5 years?
- What company would you love to work for?
- Don't worry if it seems impossible right now
Step 2: Research the Requirements
- Look at job postings for that role
- What skills do they ask for?
- What experience level?
- What education background?
Step 3: Find People in Those Roles
- Search LinkedIn for people with that job title
- Look at their backgrounds and career paths
- How did they get there?
- What companies did they work for before?
Step 4: Create Your Action Plan
- What skills do you need to develop?
- What experiences should you seek out?
- Who could you connect with for advice?
- What's your next concrete step?
Discussion: "Who wants to share their dream job and what they learned?"
Success Stories: From Student to Intern
Share Examples: Real stories of JMU students who landed great internships
Example 1: The Networker
- Started with no connections in tech
- Attended every career fair and info session
- Connected with alumni on LinkedIn
- Got referral that led to internship at major tech company
Example 2: The Project Builder
- Built impressive portfolio of personal projects
- Contributed to open source projects
- Showcased work on GitHub and personal website
- Projects spoke louder than GPA
Example 3: The Persistent One
- Applied to 100+ internships
- Got rejected many times but kept improving
- Used each rejection as learning opportunity
- Finally landed dream internship in junior year
Key Takeaway: "There's no single path to success, but there are common patterns."
Common Myths About Tech Careers
Let's Bust Some Myths:
Myth: "You need to be a CS major"
- Many successful tech workers studied other fields
- Business, psychology, design, and other majors are valuable
- Companies need diverse perspectives
Myth: "You need to know how to code"
- Many high-paying tech roles don't require coding
- Product managers, designers, sales engineers, etc.
- Understanding technology ≠ writing code
Myth: "Tech is only for young people"
- Career changers are common and successful
- Experience in other fields is often valuable
- Many companies value diverse age groups
Myth: "You need to work 80-hour weeks"
- Work-life balance varies by company and role
- Many tech companies prioritize employee wellbeing
- Startups vs. established companies have different cultures
Interactive Exercise: Career Path Exploration
Activity: "Let's do some real-time career exploration together!"
Major Tech Industry Sectors:
- Big Tech (FAANG+): Google, Apple, Facebook, Amazon, Netflix, Microsoft
- Enterprise Software: Salesforce, Oracle, SAP, ServiceNow
- Fintech: PayPal, Square, Stripe, Robinhood, Coinbase
- E-commerce: Shopify, eBay, Etsy, Wayfair
- Gaming: Epic Games, Riot Games, Blizzard, Unity
- Cybersecurity: CrowdStrike, Palo Alto Networks, Okta
- Cloud/Infrastructure: AWS, Azure, Snowflake, Databricks
Entry-Level Tech Salaries (2024):
- Software Engineer: $85,000 - $150,000
- Data Scientist: $90,000 - $140,000
- Product Manager: $95,000 - $160,000
- UX Designer: $70,000 - $120,000
- Cybersecurity Analyst: $75,000 - $130,000
- DevOps Engineer: $80,000 - $145,000
- Technical Sales: $60,000 - $120,000 + commission
Note: Salaries vary significantly by location, company size, and experience
Self-Assessment Questions:
- Do you enjoy solving complex problems step-by-step?
- Are you comfortable with ambiguity and changing requirements?
- Do you prefer working independently or in teams?
- Are you interested in understanding how businesses work?
- Do you enjoy explaining technical concepts to others?
- Are you motivated by helping users solve their problems?
- Do you like staying up-to-date with the latest trends?
The Reality of Tech Work Culture
Question: "What do you think a typical day looks like for a software engineer?"
Daily Realities:
- Meetings: 30-50% of time in meetings (standups, planning, reviews)
- Coding: 40-60% of time actually writing code
- Debugging: Significant time fixing existing code
- Learning: Constant learning of new tools and technologies
- Documentation: Writing and reading technical documentation
Work Environment Factors:
- Remote vs. In-Person: Many companies offer flexible arrangements
- Startup vs. Big Company: Different pace, resources, and stability
- Team Dynamics: Collaboration is key to success
- Continuous Learning: Technology changes rapidly
- Work-Life Balance: Varies significantly by company and role
What They Don't Tell You:
- Imposter Syndrome: Almost everyone feels like they don't belong sometimes
- Constant Change: Technologies and priorities shift frequently
- Not Always Glamorous: Lots of maintenance and bug fixes
- Communication Skills: Often more important than technical skills
- Burnout Risk: Fast pace can be overwhelming
Building Your Tech Career Foundation
The Four Pillars of Career Success
Pillar 1: Technical Skills
- Core Competencies: Master the fundamentals of your chosen field
- Continuous Learning: Stay current with industry trends
- Hands-On Practice: Build projects that demonstrate your abilities
- Depth vs. Breadth: Go deep in one area, broad in others
Pillar 2: Professional Network
- Industry Connections: Build relationships with professionals
- Peer Network: Connect with fellow students and early-career professionals
- Mentorship: Find mentors and eventually become one
- Online Presence: Maintain professional social media profiles
Pillar 3: Real-World Experience
- Internships: Gain practical work experience
- Personal Projects: Demonstrate initiative and creativity
- Open Source: Contribute to community projects
- Freelancing: Work with real clients on real problems
Pillar 4: Professional Skills
- Communication: Explain complex ideas clearly
- Problem-Solving: Break down complex challenges
- Teamwork: Collaborate effectively with others
- Leadership: Take initiative and guide others
Creating Your Personal Career Roadmap
Interactive Planning Session
Your 4-Year Career Plan:
Freshman/Sophomore Year:
- Explore different tech roles through research and informational interviews
- Build foundational skills through coursework and online learning
- Start building your professional network
- Create your first personal projects
Junior Year:
- Secure your first internship or co-op
- Develop specialized skills in your area of interest
- Build a strong portfolio of projects
- Expand your professional network
Senior Year:
- Complete additional internships or advanced projects
- Begin full-time job search process
- Leverage network for job opportunities
- Prepare for technical and behavioral interviews
Post-Graduation:
- Start your first full-time role
- Continue learning and skill development
- Build reputation within your company and industry
- Begin mentoring others and giving back
Homework
Research 3 roles you're genuinely interested in. For each, find a real job posting and write down the top 5 skills it requires. Come to the next meeting ready to share what you found — and which role excited you most.
Not mandatory, but this is exactly what we'd do if we were sitting where you're sitting. The sooner you know what you're aiming for, the faster everything else clicks into place.
Submit through the Homework tab when done.
🔍 Week 1, Days 4-5: Professional Network Analysis
What to do: Find 15 professionals on LinkedIn in your target roles
How to do it:
- Search LinkedIn for "Software Engineer at Microsoft" or similar
- Look at their education, previous jobs, and career progression
- Note common patterns in their backgrounds
Example submission:
"John Smith, Senior Software Engineer at Amazon: BS Computer Science from Virginia Tech → Junior Developer at startup (2 years) → Software Engineer at Amazon (3 years) → Senior role. Skills: AWS, Python, React. Pattern: Most successful engineers have 1-2 internships and start at smaller companies before big tech."
📊 Week 1, Days 6-7: Skills Gap Analysis
What to do: Compare your current skills to job requirements
How to do it:
- List all skills mentioned in job postings
- Rate yourself: Beginner (0-1 year), Intermediate (1-3 years), Advanced (3+ years)
- Identify the biggest gaps
Example submission:
"Required: Python (Advanced), React (Intermediate), AWS (Beginner), System Design (Beginner). My current level: Python (Intermediate), React (Beginner), AWS (None), System Design (None). Biggest gaps: Need to learn AWS and system design concepts. Plan: Complete AWS certification course and practice system design problems."
🎯 Week 2, Days 8-10: Career Roadmap Development
What to do: Create a detailed 4-year career plan
How to do it:
- Set specific, measurable goals for each semester
- Include internships, projects, and skill development
- Research specific companies and application timelines
Example submission:
"Sophomore Spring 2025: Complete Python course, build 2 web projects, apply to 15 summer internships. Junior Fall 2025: Secure internship at mid-size tech company, learn React and databases. Junior Spring 2026: Complete advanced algorithms course, contribute to open source project. Senior Year: Apply to Google, Microsoft, Amazon for full-time roles."
🤝 Week 2, Days 11-12: Network Building Strategy
What to do: Plan how to build professional relationships
How to do it:
- Identify specific people to connect with
- Draft personalized LinkedIn messages
- Research networking events and career fairs
Example submission:
"Target connections: 5 JMU CS alumni at Google, 3 software engineers at local companies, 2 product managers at startups. LinkedIn message template: 'Hi [Name], I'm a CS student at JMU interested in [their field]. Would love to learn about your career journey. Could we chat for 15 minutes?' Events to attend: JMU Career Fair (March), Richmond Tech Meetup (monthly), Grace Hopper Conference (virtual)."
📝 Submission Format
How to organize your submission:
- Use clear headings for each deliverable
- Include specific examples and data
- Show your research process and sources
- Be detailed - aim for 2-3 pages total
Example structure:
"## Career Research Report
### Software Engineer Role Analysis
- Job Requirements: [list]
- Salary Range: $X - $Y
- Career Progression: [path]
### Data Scientist Role Analysis
[continue for all 10 roles]
## Professional Network Analysis
### Person 1: [Name, Company, Background]
[continue for all 15 people]"
Homework
Research 3 roles you're genuinely interested in. For each, find a real job posting and write down the top 5 skills it requires. Come to the next meeting ready to share what you found — and which role excited you most.
Not mandatory, but this is exactly what we'd do if we were sitting where you're sitting. The sooner you know what you're aiming for, the faster everything else clicks into place.
Submit through the Homework tab when done.