Skip to content
ByteWave Technology

Role family · Technology & Digital · Software / Web / Mobile

Technology careers

Technology roles design, build, test and maintain the software people use every day, from websites and mobile apps to the services behind them. For students, graduates and career changers who want to build software, and for developers who want to move into a new kind of development work.

Roles covered

  • Software DeveloperGuide
  • Frontend DeveloperGuide not published yet
  • Backend DeveloperGuide not published yet
  • Full-Stack DeveloperGuide not published yet
  • Mobile App DeveloperGuide not published yet

Role names follow ByteWave's industry and roles directory. Titles vary between employers.

01

Technology roles

What each role does, what it produces and who it tends to suit.

  • Software Developer

    Designs, writes and tests code for products and internal systems.

    Typical outputs
    Features, bug fixes, code reviews, tests
    May suit
    People who enjoy logic and building things end to end
    Adjacent roles
    Full-Stack Developer, QA Engineer, DevOps Engineer
  • Frontend Developer

    Builds the parts of websites and apps that people see and click.

    Typical outputs
    Pages, components, accessible layouts
    May suit
    People who care about how things look and feel to use
    Adjacent roles
    Full-Stack Developer, UI Designer, Mobile App Developer
    Full guide not published yet
  • Backend Developer

    Builds the services, APIs and databases behind an application.

    Typical outputs
    APIs, data models, integrations
    May suit
    People who like data, logic and how systems fit together
    Adjacent roles
    Full-Stack Developer, Data Engineer, Cloud Engineer
    Full guide not published yet
  • Full-Stack Developer

    Works on both the user-facing and server sides of an application.

    Typical outputs
    Complete features from screen to database
    May suit
    People who like seeing the whole picture
    Adjacent roles
    Frontend Developer, Backend Developer, DevOps Engineer
    Full guide not published yet
  • Mobile App Developer

    Builds apps for phones and tablets.

    Typical outputs
    Mobile screens, app releases, store updates
    May suit
    People interested in how apps work on small screens
    Adjacent roles
    Frontend Developer, Software Developer
    Full guide not published yet
02

This path may suit you if…

These are common reasons people enjoy this work. They aren't requirements, and people arrive from many backgrounds.

  • You enjoy breaking a problem into small steps and checking each one works.
  • You like making something that other people use, and improving it from feedback.
  • You're comfortable learning new tools as they change.

Developers usually work in small teams with designers, testers and product managers, reviewing each other's code and planning work in short cycles. People arrive from computer science degrees, bootcamps, self-study and other technical jobs.

Check My Fit
03

Skills by level

Foundations are what most entry-level jobs expect. The other levels come with practice and experience. Individual employers ask for different combinations.

Foundations

Must-have to start

  • Programming basics in one language
  • How the web works (requests, browsers, servers)
  • Version control with Git
  • Writing simple tests

Working proficiency

Expected once you're in the role

  • Building and reading APIs
  • Working with a database
  • Debugging and reading other people's code
  • Code review and working in a team

Advanced / specialist

Nice to have; grows with experience

  • System design and performance
  • Security basics for applications
  • Automated testing and deployment pipelines
  • Mentoring and technical decisions
Check My Readiness
04

Tools and technologies

Good to start with

  • Git and GitHub
  • A code editor such as VS Code
  • Browser developer tools
  • One language (for example JavaScript or Python)

Often used later

  • React or another UI framework
  • Node.js, Java or similar for services
  • SQL databases such as PostgreSQL
  • Docker and cloud basics

You don't need every tool. Employers ask for different combinations, so learn the basics first and then the tools your target jobs mention most.

Explore Training Plans
05

Compare roles and ways in

Entry routes vary. Some roles are common first jobs; others usually follow experience in a related role.

  • Software Developer

    Core skills
    Programming fundamentals, version control, testing
    Entry-level route
    Degree, bootcamp or self-taught portfolio of small apps
    Experienced route
    Move from another developer role or from QA or support
    Adjacent roles
    Full-Stack Developer, QA Engineer, DevOps Engineer
  • Frontend Developer

    Core skills
    HTML, CSS, JavaScript, accessibility
    Entry-level route
    Portfolio of responsive pages and small interactive apps
    Experienced route
    Move from design, content or web support roles
    Adjacent roles
    Full-Stack Developer, UI Designer, Mobile App Developer
  • Backend Developer

    Core skills
    A server language, SQL, API design
    Entry-level route
    Portfolio with a small API and database
    Experienced route
    Move from data, support or systems roles
    Adjacent roles
    Full-Stack Developer, Data Engineer, Cloud Engineer
  • Full-Stack Developer

    Core skills
    Frontend and backend basics, databases, deployment
    Entry-level route
    Usually after some frontend or backend experience
    Experienced route
    Grow from a frontend or backend role
    Adjacent roles
    Frontend Developer, Backend Developer, DevOps Engineer
  • Mobile App Developer

    Core skills
    A mobile framework, APIs, testing on devices
    Entry-level route
    Portfolio with one or two published or demo apps
    Experienced route
    Move from web development
    Adjacent roles
    Frontend Developer, Software Developer

No salary or hiring-demand figures are shown: those need a dated, sourced reference.

Get My Plan for a Technology Role
06

Practice projects

Practice examples to build evidence, not client work. A project helps you show a skill; on its own it doesn't qualify you for a job. Use dummy or public data only, and practise in your own sandbox or lab.

  1. Practice project 1

    Build a small application

    Brief
    Build a to-do, booking or budget app that saves data and has at least one form.
    Deliverable
    Working app, code on GitHub and a short README explaining your choices.
    Skills shown
    Programming, Version control, Testing
    Reflect on
    What would you change if a hundred people used it every day?
  2. Practice project 2

    Write a test plan

    Brief
    Pick an open-source app or your own project and plan how you'd test one feature.
    Deliverable
    A one-page test plan with test cases and the bugs you found.
    Skills shown
    Testing, Attention to detail, Writing
    Reflect on
    Which test found the most useful problem, and why?
  3. Practice project 3

    Document a setup

    Brief
    Write clear setup and troubleshooting notes for a project someone else could follow.
    Deliverable
    A step-by-step guide tested by a friend.
    Skills shown
    Documentation, Systems basics, Communication
    Reflect on
    Where did your tester get stuck, and how did you fix the guide?
Build a Portfolio Project
07

Learning roadmap

A suggested order, from fundamentals to evidence you can show. Go at your own pace.

  1. 1Learn the foundationsOne programming language, Git and how the web works.
  2. 2Build small thingsTwo or three small apps that each teach one new skill.
  3. 3Work like a teamTests, code review and an open-source contribution or group project.
  4. 4Show your evidenceA tidy portfolio, a focused resume and a GitHub profile you can talk through.
  5. 5Prepare for interviewsPractise coding questions and explain your projects out loud.
Build My Career Plan
08

Career progression and adjacent roles

Developers often move between frontend, backend and full-stack work, or towards testing, DevOps or product roles. How and when you move depends on your experience, performance and the employer. There's no fixed ladder and no guaranteed promotion.

Related role families

Explore Related Roles

Your next career move should be intentional.

Choose how you'd like to start. Every route ends in the same place: a clear, honest next step built around you.

How would you like to start?

What happens next

3 short steps

Answer short questions about where you are and where you want to go.

  1. 01Tell us where you areYour goal, target role and what is in the way.
  2. 02See your next stepA recommendation straight away.
  3. Get a plan built around youWe follow up by your preferred channel.

Or start in one tap — which best describes you?

Get My Placement Plan

No job, interview or visa guarantees, just a clear plan.

Talk to an advisor · 1 of 2

What would you like help with?

What would you like help with?