What we test for
Typical work
- Async APIs and internal services, documented by their own schemas
- Python services fronting a model, a queue or a third-party API
- Moving a Flask or Django API across without rewriting the domain
- Latency work: connection pools, timeouts and backpressure
The coding test
Build a service with Pydantic models, database access through a dependency, and tests driven by httpx. Then work out why one route is far slower under load than it is on its own. Scored on the schemas, on where the dependency sits, and on whether they find the blocking call.
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 is declared async and the service still blocks. What is happening?
A strong answer covers: A synchronous library inside the coroutine is holding the event loop, and the keyword did not make it async. Either run it in a thread pool, or let the route be an ordinary def so the framework does that for you, or swap in a driver that is genuinely async.
What do dependencies buy you beyond tidier code?
A strong answer covers: One place for auth, sessions and pagination, a lifetime you control, teardown through yield, and an override in tests so a suite never touches the real thing. A service that builds its own session inside each handler cannot be tested without one.
How far do you let Pydantic carry validation?
A strong answer covers: To the boundary: shape, types, ranges, and a response model so a field cannot leak out. A rule that needs the database is not validation, it belongs in the service. Strictness and coercion settings are a decision to take once, not per model.
The OpenAPI schema is generated for you. What still goes wrong with it?
A strong answer covers: Response models left off, so every route documents itself as anything at all. Errors undocumented, because only the happy path has a model. And breaking changes nobody notices, which is why the schema is worth diffing in the pipeline.
How do you keep an async service healthy under load?
A strong answer covers: A timeout on every outbound call, bounded pools, a cap on concurrency, and readiness that fails before the pool is exhausted rather than after. Retries get jitter and a budget; without one, a slow dependency becomes an outage you built yourself.
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 FastAPI developers?
6+ years of professional Python, with recent production FastAPI work. We count Python years on purpose: the framework is young enough that six years of it would mean adopting it the month it appeared.
Is this the same pool as your Python developers?
Yes, scored on a different test. The FastAPI test is async-first, which is where the mistakes live.
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.