What we test for
Typical work
- Features built from a design, with the states the design forgot: loading, empty, error
- A component library the whole product uses, so a button looks the same everywhere
- Performance work on a slow page: what loads, when, and how much of it
- Accessibility fixes that pass an audit and still work for the people using them
The coding test
Build a filterable list from a design and a real API: loading, empty and error states included, and usable with only a keyboard. Then we slow the network down and ask what the user sees. Scored on state handling, accessibility and what they chose not to re-render, not on pixel polish.
Inside Front-End
The ones people search for by name get a page of their own, with their own coding test and interview questions.
JavaScript
The language rather than one framework: TypeScript, performance and shared tooling.
See the page →React
Frontend engineers who ship the UI your roadmap promised.
See the page →Next.js
App Router, server components and rendering decisions you can explain per route.
See the page →Angular
Large typed front ends, RxJS, and upgrades from old Angular versions.
See the page →Vue.js
Vue 3 and Nuxt product UI, Pinia, and migrations off the Options API.
See the page →TypeScript
Types that make a refactor safe, migrations off JavaScript, and contracts that hold.
See the page →CSS and UI
Design systems, responsive layouts, and accessibility that passes an audit.
See the page →Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
Where should this piece of state live?
A strong answer covers: As close to where it is used as it can be, and in the URL when someone would want to share or bookmark it. Server data belongs in a cache built for it, not copied into a global store. The answer to worry about is one store for everything, because then every change re-renders everything.
A page feels slow on a cheap phone and fine on a laptop. What do you look at?
A strong answer covers: The JavaScript: how much ships, how much runs before the first interaction, and what blocks the main thread. A trace on a throttled device settles it faster than any guess. The usual causes are a heavy library for one feature, and work done on every render that should be done once.
How do you make a custom dropdown accessible?
A strong answer covers: First ask whether a native select would do, because it already works. If not: the right roles, focus that moves with the arrow keys and returns when it closes, and a label a screen reader announces. A senior tests it with a keyboard and a screen reader, not only with the linter.
What do you test in a front end, and what do you leave alone?
A strong answer covers: Behaviour the user sees: a form that submits, an error that shows, a list that filters. Not implementation details that change with every refactor. A few end-to-end tests on the paths that make money, and component tests for the logic around them.
When is server rendering worth it?
A strong answer covers: When the first view has to be fast or indexable: marketing pages, product listings, anything found through search. Behind a login it often adds a server to run and little a user notices. Being able to say when not to use it is part of being senior.
One invoice a month.
The shortlist is free. Pick the contract that suits you: monthly, six months or twelve.
What every seat includes
- Contracts, payroll and compliance handled
- Vetting: coding test, soft skills, English and a level check
- Free replacements: unlimited on 12+ months, 2 on 6 months, 1 on monthly
- A direct line to our CEO
Terms in plain words
- Monthly, six months or twelve, your choice
- Your rate is locked for the whole contract on 6 and 12+ months
- Monthly ends with 30 days’ notice
- Want to hire the developer full-time? The buyout is set in the contract from day one
Questions tech leads ask us
How senior are your front-end developers?
6+ years of professional front-end work, with recent production experience in the framework you hire for. We test that framework, not a general one.
Can I see the coding test results?
Yes. Every profile card includes the score and the reviewer's notes.
Skip the sales rep. Talk to the CEO.
Tell us what you're building, your stack and when you need people. Three vetted profiles per role within 48 hours of the call, and a straight answer on whether we're the right fit.