What we test for
Typical work
- Moving a JavaScript code base to TypeScript, one boundary at a time
- Shared types and client libraries several teams build on
- Making an API contract impossible to break in silence
- Build and editor performance in a monorepo that got slow
The coding test
Take a module typed loosely enough to hide a bug, fix the bug, and tighten the types so the same bug cannot come back. Then design the types for a small API client so that calling it wrongly does not compile. Scored on how little they change, and on whether the types now carry the rules.
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 does TypeScript stop protecting you?
A strong answer covers: At every boundary. Anything parsed, fetched or cast is a claim rather than a check, so the edge needs validation at runtime with the type derived from the validator, otherwise the two drift. An as cast is a promise with nobody checking it.
How do you move a large JavaScript project across?
A strong answer covers: With the compiler still accepting JavaScript, strictness raised one flag at a time, and the shared types written first so the rest has something to lean on. An any amnesty that nobody ever revisits is TypeScript in name only.
When is a generic the right tool, and when is it showing off?
A strong answer covers: When the relationship between what goes in and what comes out is real. Otherwise an overload or a union says it more plainly. Conditional types earn their keep in a library; in product code a signature that needs a paragraph to read will be fought by the next person.
unknown, any and never: when do you reach for each?
A strong answer covers: unknown at the boundary, because it forces narrowing. any only as a deliberate escape, commented and fenced in. never for exhaustiveness: assigning the default case to never means adding a variant breaks the build instead of slipping through.
The build and the editor got slow in a monorepo. What now?
A strong answer covers: Measure it with the compiler diagnostics rather than guessing. The usual causes are enormous union or conditional types, inferred return types crossing package lines, and no project references or incremental build. Explicit types at package boundaries buy most of it back.
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 TypeScript developers?
6+ years of professional TypeScript work, with recent production experience.
Can I see the coding test results?
Yes. Every profile card includes the score and the reviewer's 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.