What we test for
Typical work
- REST and messaging services on Spring Boot 3
- Upgrades from Spring Boot 2 and Java 8 or 11
- Splitting a Spring monolith into services that deploy on their own
- Performance work: connection pools, caching, query and JVM tuning
The coding test
Build a service with one REST resource, Spring Data JPA persistence, bean validation and an integration test on a real database through Testcontainers. Then make a @Transactional method that silently does nothing actually commit. Scored on layering, which test slice they reach for, and how they explain the proxy that broke it.
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 @Transactional method does nothing when another method of the same class calls it. Why?
A strong answer covers: Spring advises the bean through a proxy, and a self-invocation never crosses it. Move the method to another bean, inject the proxy, or weave with AspectJ; private and final methods are never advised either.
How do you find out why auto-configuration handed you a bean you did not want?
A strong answer covers: The condition evaluation report, from --debug or the actuator conditions endpoint; then read the @ConditionalOnMissingBean ordering and exclude the auto-configuration class, rather than fighting it with a later @Bean.
How do you lay configuration out across environments?
A strong answer covers: Profiles over externalised config, typed @ConfigurationProperties with validation instead of @Value scattered through the code, secrets from the environment or a vault, and no production password in application.yml.
What do you test with @SpringBootTest, and what do you not?
A strong answer covers: Slices by default with @WebMvcTest or @DataJpaTest, the whole context only for the few wiring paths that need it, a real database through Testcontainers rather than H2, and never booting the app to check a mapper.
How do you secure an internal API on Spring Security 6?
A strong answer covers: A SecurityFilterChain bean, since WebSecurityConfigurerAdapter is gone; JWT validated as a resource server with issuer and audience checked; method security for the fine-grained rules; and CSRF left on for anything cookie-based.
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 Spring Boot developers?
6+ years of professional Spring Boot 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.