Junior Frontend Engineer

About the role

We are looking for a junior frontend engineer to join an established product engineering team. You will work mainly on the frontend, in a strict TypeScript Next.js codebase built on a mature design system, and you will grow into owning full features within your first few sprints. This is a delivery role with real mentoring attached. You will pick up scoped frontend stories, take them from Figma to a reviewed and merged pull request, and integrate them against live backend APIs. You are not expected to be an expert on day one. You are expected to be curious, careful, and quick to absorb feedback. One thing matters to us specifically: we do not want a frontend engineer who stops at the API boundary. In our experience most defects live at the seam between frontend and backend. You should be able to read a Spring Boot controller, understand what a REST contract actually returns, and debug an integration problem instead of handing it over and waiting.

Key responsibilities

• Build responsive, accessible interfaces from Figma designs using the team's design system, component library and design tokens.
• Implement screens and components in React and Next.js App Router with strict TypeScript.
• Wire the frontend to backend REST APIs, handle loading, empty, error and permission states properly, and validate payloads at the boundary.
• Debug across the stack. When a screen breaks, trace it through to the API response and identify whether the defect is frontend or backend before escalating.
• Write and maintain unit and component tests for what you ship, and support the team's end to end test suite.
• Take part in pull request reviews as an author, respond to every comment, and verify your own fixes before marking them done.
• Keep your work visible and current on the team's board, branches and pull requests in Azure DevOps.
• Raise questions, risks and blockers early in standup and in writing.

About you

• React and Next.js: Working knowledge of React and Next.js, including the App Router. You have built and shipped real screens, not only tutorials.
• TypeScript: Comfortable writing typed code and reading a strict, typed production codebase.
• CSS and Tailwind: Solid CSS fundamentals and component driven styling with Tailwind CSS.
• Design to code: Able to turn a Figma design into a faithful, responsive interface with attention to spacing, hierarchy and consistency.
• Accessibility basics: Understands semantic HTML, keyboard navigation, focus handling and WCAG AA colour contrast, and is willing to go deeper.
• Data and state: Basic experience with client side data fetching and server state, for example TanStack Query or an equivalent, plus form handling and schema validation.
• Able to open a Java or Spring Boot service and follow a request from the controller to the response body. You do not need to be a backend engineer, but you must not be blocked by backend code.
• Understands HTTP methods, status codes, request and response payloads, pagination, and what a breaking contract change means for the UI.
• Basic understanding of token based authentication and role or permission driven access, and how it changes what a screen is allowed to show.
• Can read simple SQL and understands the difference between a data model problem and a UI problem.
• Confident with Git: branching, commits, pull requests and responding to code review feedback.
• Comfortable working in two week sprints with an issue tracker such as Azure DevOps, Jira or similar.
• Writes unit tests for the code you ship and is willing to learn the team's integration and end to end testing practice.
• Takes review comments as normal engineering practice, responds to every point, and re-checks the code before saying it is fixed.
• Clear written English. Flags blockers early instead of going quiet.
• Hands on use of an AI coding assistant such as Claude Code, Cursor or GitHub Copilot in real work, not just experiments.
• Able to give clear, structured instructions to scaffold, refactor, debug and document code.
• Reviews and verifies AI generated output instead of accepting it blindly. You own the quality of everything you ship.
• Uses AI to read unfamiliar parts of the codebase and get productive faster, and shares what works with the team.