What we test for
Typical work
- Product and marketing apps where the first paint is the business case
- Migrations off the Pages Router, route by route
- Rendering decisions: static, streamed, revalidated or per request
- Getting an app off platform-only assumptions and onto your own infrastructure
The coding test
Build a route that streams, revalidates on a webhook, and shows something useful while the slow part loads. Then take a page that should be static and find what made it render per request. Scored on the rendering choices and on whether they can name the line that opted the route in.
Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
A route you expected to be static is rendering per request. What made it dynamic?
A strong answer covers: Something read cookies, headers or search params, or opted out of the cache, and that decision applies to the whole route. The build output says which routes are which. The fix is to push the dynamic read down to a smaller boundary, not to cache harder around it.
What actually belongs in a client component?
A strong answer covers: Interactivity, browser APIs and local state. Everything else stays on the server and never ships. The common mistake is use client at the top of a page, which drags the whole tree into the bundle; it belongs on the leaf that needs it.
How do you choose between static, revalidated and per-request rendering?
A strong answer covers: By how stale the data may be and who pays for the wait. Content goes static and revalidates, on demand when there is an editor or a webhook to trigger it; per request is for things that differ per user. Then tag the cache so one change invalidates its own page and not the site.
A Server Action is about to write to your database. What do you check?
A strong answer covers: That it is treated as the public endpoint it is: authenticated and authorised inside the action, input validated, hidden fields not trusted, and a rate limit. The revalidation or redirect afterwards is part of the contract, not an afterthought.
What breaks when you take a Next.js app off its hosting platform?
A strong answer covers: Image optimisation, incremental regeneration across several instances with no shared cache, middleware running on a different runtime, and streaming behind a proxy that buffers it. Worth deciding early how much of the platform you intend to depend on.
One monthly price per developer. Everything in it.
No deposit, no minimum term, no placement fee. You pay one invoice a month for each developer on your team.
Per developer, all-in. Your quote arrives by email with your exact number after you send the brief.
- Developer pay, local payroll and taxes
- Vetting: coding test, soft skills, English
- Free replacement within 90 days
- A direct line to our CEO
What changes the price
- Seniority and role. Senior engineer, tech lead or architect.
- Stack. Some stacks and niche tools cost more to staff.
- Team size. Larger teams get a better monthly rate per seat.
- White-label. Agencies reselling under their brand get partner pricing.
Terms in plain words
- First 2 weeks risk-free: if it isn't working, you don't pay for them
- Month to month, 30 days' notice to end
- No deposit and no minimum number of seats
- Want to hire the developer full-time? Buyout of 3 months' fee in year one, 2 months' after
Questions tech leads ask us
How senior are your Next.js developers?
6+ years in React, with recent production work on the App Router. The router split in 2023, so we ask what they have shipped since, not only how long they have used the name.
Do they only work on Vercel?
No. We ask in the interview what breaks when a Next.js app is self-hosted, because the answer separates people who built an app from people who filled in a template.
Can I see the coding test results?
Yes. Every profile card carries the score and the reviewer notes.
What does it cost?
$6,900 per developer per month, all-in, and flat: the same rate whatever the stack. Your exact quote arrives by email after you send the brief.
Skip the sales rep. Talk to the CEO.
Tell us what you're building, your stack and when you need people. Three matched profiles within 48 hours, and a straight answer on whether we're the right fit.