Skip to content

Software Engineering · Career guide

Frontend Developer

Build the interfaces people see and use — fast, accessible and delightful on every device.

Role overview

Frontend developers build the part of a product that users interact with. The job blends engineering with design sense: component architecture, state management, performance, accessibility and responsive layouts across phones, tablets and desktops.

Typical responsibilities

  • Translate designs into components
  • Manage client state and data fetching
  • Ensure accessibility and responsiveness
  • Optimise load performance
  • Write UI tests

Beginner roadmap

  1. 1

    HTML & accessibility

    Semantic elements, forms, ARIA only when needed, keyboard navigation.

  2. 2

    CSS & responsive layout

    Box model, flexbox, grid, media queries, design tokens.

  3. 3

    JavaScript

    DOM, events, async/await, fetch, modules.

  4. 4

    TypeScript

    Types, generics, narrowing, typing components.

  5. 5

    A UI framework

    Components, props, state, effects, routing.

  6. 6

    Data fetching & state

    Server vs client state, caching, forms and validation.

  7. 7

    Performance

    Core Web Vitals, code splitting, image optimisation.

  8. 8

    Testing

    Component tests and end-to-end tests.

  9. 9

    Portfolio

    Three polished, deployed projects with case-study write-ups.

Advanced directions

Design systemsMicro-frontendsAnimation & motion designRendering strategies (SSR, SSG, streaming)PWA & offline

Project ideas

  • beginner

    Responsive portfolio site

    Accessible, fast, works beautifully on mobile.

  • intermediate

    Recipe finder

    Search, filters, favourites, API integration, loading and empty states.

  • advanced

    Component library

    Documented, themed, accessible components published as a package.

Interview topics

  • Event loop
  • Closures
  • CSS layout
  • React rendering & hooks
  • Accessibility
  • Web performance
  • Build a UI component live

Resume guidance

  • Show before/after performance or accessibility improvements you actually measured.
  • Link live demos — reviewers will click them.