Hire developers · Back-end
Back-end
Hire Java engineers
The stack most likely to be running something that cannot be switched off, which makes the screen as much about operational judgement as language.
What they are hired to build
The work, before the CV.
A role written against the work gets a better shortlist than a role written against a stack. These are what Java engineers are usually brought in to do.
Roles we recruit: Java backend engineer · Senior Java / Spring Boot engineer · Backend lead or principal engineer.
- Spring Boot services and microservice estates
- Systems with hard throughput or latency requirements
- Banking, insurance and other long-lived regulated platforms
- Modernising a monolith without a full rewrite
The technical screen
What the conversation actually covers.
Every candidate has a real technical conversation with an engineer who has done the job, and you get written evidence per competency. In Java, that conversation covers the following.
Usually assessed alongside: Spring Boot, JPA / Hibernate, PostgreSQL or Oracle, Kafka.
- Concurrency: threads, pools, and what they have actually debugged
- JVM behaviour under load — memory, GC pauses, and how they diagnosed one
- Spring's dependency injection and transaction boundaries
- Persistence and the N+1 problems that follow careless JPA
Three ways to bring one on
The route changes; the screening does not.
The same three routes apply whichever stack you are hiring for. Which one fits depends on how long you need the person and whether the headcount is approved.
Permanent placement
Companies hiring engineering and data roles
One fee on joining, with a 90-day replacement guarantee.
- Typical timeline
- 3–8 weeks to offer
Contract staffing & staff augmentation
Companies with budget but no headcount
We employ them, you direct them. Monthly, for when the need is real but headcount is not approved.
- Typical timeline
- Monthly, 3-month minimum
Contract to hire
Companies hiring into a new or unclear role
Three to six months as a contractor, then convert. The honest option when neither side is sure.
- Typical timeline
- 3–6 months to conversion
Or have us build it instead
If the need is the work, not the headcount.
Software Engineering
API & integration engineering
Making systems talk to each other, reliably and observably.
Software Engineering
Legacy modernisation & re-platforming
Incremental re-platforming, sequenced so the business keeps running throughout.
Advisory & Architecture
Architecture review
A second opinion mid-build, when something feels wrong but nobody can name it.