[Recruiting]
Senior Full Stack Engineer hired across time zones
A company under NDA needed a senior full stack engineer for its core team. We recommended the candidate who was slightly weaker in hard skills and a much better fit for the team, and that was exactly what the company needed.
The brief
A company under NDA needed one senior full stack engineer to join its core team early and build the platform end to end. The role called for strong TypeScript, Node.js and React, production experience with cloud services and message queues, and the ability to take part in architecture decisions.
The team was fully remote. The client worked in a different time zone from the candidates and from us, and the team itself was spread across several countries.
Where we looked
We searched on LinkedIn, one profile at a time, and kept a written note on every profile we reviewed, so the reason behind each decision stayed clear. We passed on profiles with too little experience for a senior role and on those without the background the team needed.
For profiles that looked promising but unclear, we wrote to the candidate to learn more. One of the candidates who later joined the shortlist came to us through a personal recommendation.
The funnel in numbers
66 candidates found and added to the search
43 marked for outreach
30 received the job description and follow-ups
18 went through screening and a video interview with us
13 made the shortlist
11 were presented to the client
7 had an interview with the client
4 did a test task
3 reached the offer stage
1 engineer started work
Of the 36 candidates whose search ended with a recorded outcome, 34 were declined after a review, 1 was not suitable and 1 was put on hold.
How we worked
Every candidate reached the client as one package: our written review with a professional assessment, a video interview, and the candidate's answers to five technical questions the client had asked us to cover in every interview.
The client lives in a different time zone from our team and from the candidates, so we built the process around that. Nobody had to line up calendars. The client opened the review and the video when it suited him and saw the answers to his own questions right away.
The finalist who chose another company
One of the finalists liked the offer and then accepted a counter-offer from another company. The candidate was weighing a young startup against a larger company with established processes, and the second suited him better. We liked him as much as the other finalists and respected his choice, because a good fit works in both directions.
The candidate who joined
The offer went to a candidate who was slightly weaker in hard skills than some of the others. He had a strong theoretical background and less experience in commercial projects, and our review said so openly.
What set him apart was how he worked with people. Our notes pointed to effective communication, creative problem solving, adaptability and a strong drive to grow. He was comfortable with processes that are still taking shape, which is exactly what a growing team needs.
We told the client plainly where he was weaker and why we still recommended him. The client chose him after the interview and the test task, and the choice proved right: his fit with the company mattered more than a few extra points in hard skills.
What to take from it
A test task checks hard skills. Soft skills decide how a person fits a small team, so we weigh both.
Tell the client openly where a candidate is weaker. An honest review builds trust in the rest of the package.
Build the process around time zones: one package with the review, the video and the answers, and no calendars to match.
Keep several strong finalists in play. A good candidate can accept a counter-offer at the last step.
[Result]
A senior full stack engineer joined the core team.
Is your situation similar?
Start with a consultation: 60 minutes, your questions, a written action plan.