Frontend Engineer

Frontend Engineer

UI components | Grant application forms | Accessibility standards

Stack tags: TypeScript · Remix / Next.js · React · WCAG 2.1 AA · Tailwind CSS

Role overview

This role owns the user-facing layer of the platform — UI components, complex multi-step grant application forms, and accessibility compliance. The platform is used by public sector grant applicants, which means accessibility is a legal and contractual obligation, not an aspiration. You will work in a TypeScript/React environment using Remix or Next.js, and you need to understand server-side rendering beyond surface-level React knowledge. This is a mid-level position with clear scope to grow under the technical direction of the Senior Full Stack Engineer.

Mandatory skills

• TypeScript (solid) — the frontend is TypeScript throughout. You must be comfortable with typed React components, interface design, and TypeScript-specific patterns.
• Remix or Next.js (beyond basic React) — genuine framework-level knowledge is required. You must understand server-side rendering, data loading patterns (loaders/actions in Remix, or the app router in Next.js), and how they affect form handling and state. React ability alone is not sufficient.
• Complex multi-step forms — demonstrable ability to build multi-step forms with heavy conditional logic, field-level validation, error handling, and state persistence across steps. Grant applications are long and branching; this is central to the role.
• WCAG 2.1 AA — explicit, hands-on experience building to this standard. Non-negotiable. The platform serves public sector users and accessibility compliance is a contractual requirement.

Important but not mandatory

• GDS / Welcome to GOV.UK Frontend — experience with the Government Design System or Welcome to GOV.UK frontend components. The platform follows public sector design conventions and prior exposure significantly reduces ramp-up time.
• Tailwind CSS (specifically Tailwind Catalyst) — the project uses Tailwind for styling with Catalyst as the component system. General Tailwind experience is useful; Catalyst-specific knowledge is a bonus.
• Plotly — familiarity with Plotly for dashboard and data visualisation components, used in grant reporting views within the platform.
• ArcGIS / mapping components — experience integrating ArcGIS or equivalent mapping libraries, relevant to geographical visualisation features.
• Accessibility testing tools — practical experience with Axe, NVDA, VoiceOver, or Lighthouse for verifying and debugging accessibility compliance.