Own Your EvidenceCareer NavigatorMy dashboard
  1. 1 Discover
  2. 2 Explore
  3. 3 Compare
  4. 4 Skills
  5. 5 My Evidence
  6. 6 Roadmap
Technology

Software Engineer

Builds the apps, websites and systems people use every day.

Why it may fit you

  • Included to widen the options you have seen

Your evidence for this career

Based only on the experiences and strengths you have entered. Add more in My Evidence.

Strong evidence

Nothing here yet — two experiences showing the same skill will move it here.

Some evidence

Nothing here yet.

Evidence to build

  • Teamwork
  • Communication
  • Listening
  • Technology
  • Problem solving
  • Digital skills
  • Working with data
  • Attention to detail
  • Planning
  • Working independently

What you may need to develop

Teamwork

Why it matters: Employers want a specific example, not the word itself.

Your current evidence: Limited evidence identified so far.

Ways to build this

  • • Write up one team experience: your role, a disagreement, what you did
  • • Join a team activity outside your course

Communication

Why it matters: Named in almost every job advert, and usually tested at interview.

Your current evidence: Limited evidence identified so far.

Ways to build this

  • • Ask for written feedback after a presentation or piece of writing
  • • Write a short summary of something technical for a general reader

Listening

Why it matters: Underrated, and central to advisory, care and client roles.

Your current evidence: Limited evidence identified so far.

Ways to build this

  • • Volunteer in a support, buddy or peer-mentoring scheme
  • • Interview someone about their career and write three notes from it

Technology

Why it matters: You do not need to be a specialist — just comfortable and willing to learn.

Your current evidence: Limited evidence identified so far.

Ways to build this

  • • Complete a free introductory course in a tool used in the sector
  • • Build something small and keep it as a portfolio item

What they do

Software engineers design, write and improve code. Work ranges from mobile apps and websites to the systems behind banking, healthcare and games.

What your day could involve

  • Picking up a task and understanding what a user needs
  • Writing and testing code
  • Reviewing a teammate's work and giving feedback
  • Fixing a bug reported by users
  • A short team stand-up to plan the day

Skills employers often look for

People skills

  • • Teamwork
  • • Communication
  • • Listening

Technical skills

  • • Technology
  • • Problem solving
  • • Digital skills
  • • Working with data

Professional skills

  • • Attention to detail
  • • Planning
  • • Working independently

Qualifications

There is usually more than one way in. A degree is one route — not the only one.

Typical degree routes

  • • Computer science
  • • Software engineering
  • • Maths
  • • Physics
  • • Any degree plus a portfolio

Apprenticeships

  • • Level 4 software developer apprenticeship
  • • Level 6 digital and technology solutions degree apprenticeship

Other routes in

  • • Self-taught with a public portfolio
  • • Coding bootcamps
  • • Moving across from IT support or testing

Certifications worth exploring

Only worth doing if it helps you. Experience and evidence usually matter more than collecting certificates.

Useful now

  • A free beginner course (Python or JavaScript)
    Lets you build something small quickly — that project is your evidence.
  • Git and GitHub basics
    Employers look for a place they can see your work.

Useful later

  • Cloud fundamentals (AWS, Azure or Google Cloud)
    Most teams now deploy to the cloud.

Optional specialist

  • Security or mobile platform certifications
    Only once you know which area you enjoy most.

Organisations to Put on Your Radar

Examples to explore — illustrative, not job adverts or endorsements

Large employers

A global technology company

Technology

Roles to look for: Graduate engineer, intern, apprentice

Why explore it: Strong training and mentoring.

Specialist organisations

A software house or digital agency

Software services

Roles to look for: Junior developer

Why explore it: Varied projects for many clients.

Public sector

A government digital service

Public sector

Roles to look for: Junior developer, apprentice

Why explore it: Work used by millions of people.

Charities and NGOs

A charity with a digital team

Third sector

Roles to look for: Digital assistant

Why explore it: Technology with social purpose.

Start-ups and growing companies

An early-stage start-up

Technology

Roles to look for: Junior full-stack developer

Why explore it: Wide responsibility, fast learning.

Organisations in my region

A local employer with an IT team

Varies by region

Roles to look for: Apprenticeships, junior roles

Why explore it: Many mid-size local firms hire apprentices.

What should I look for on an employer's website?

  • Graduate programmes — Structured schemes with training, usually opening a year before they start.
  • Apprenticeships — Earn while you learn. Look for the level — Level 2 or 3 up to degree level.
  • Internships — Paid experience over summer or a placement year. Often the main route into graduate roles.
  • Insight days — One-day or one-week introductions, often for Year 12, 13 or first-year students.
  • Volunteering — Many employers run volunteering days or support local projects you could join.
  • Work experience — Short placements or shadowing. Ask directly — many are never advertised.
  • Entry-level roles — Assistant, coordinator or support job titles are real doors into a career.