Hire developers · Front-end

Front-end

Hire TypeScript engineers

Hired as a discipline rather than a framework — for teams whose problem is type safety and shared contracts across a codebase, not any one UI library.

Category
Front-end
Roles
3
Screening
By an engineer, with written evidence
Terms
Quoted per role, in writing

What they are hired to build

The work, before the CV.

A role written against the work gets a better shortlist than a role written against a stack. These are what TypeScript engineers are usually brought in to do.

Roles we recruit: TypeScript engineer · Full-stack TypeScript developer · Platform or tooling engineer.

  • Shared types between a front-end and its API
  • Migrating a JavaScript codebase to TypeScript without a rewrite
  • Internal libraries, SDKs and tooling
  • Full-stack work across a single-language codebase

The technical screen

What the conversation actually covers.

Every candidate has a real technical conversation with an engineer who has done the job, and you get written evidence per competency. In TypeScript, that conversation covers the following.

Usually assessed alongside: Node.js, React or Vue, Zod or similar validation, Monorepo tooling.

  • Whether types describe the domain or merely silence the compiler
  • Generics and inference — used where they earn their complexity
  • Handling of `any`, `unknown` and the boundaries where data enters
  • Build and module configuration, which is where most teams lose days