Hard work deserves to be rewarded! 🥂
Which means another well-earned Lunch Club!
A big shoutout to Andy MacKay, Owen Butler and Ellis Sullivan for their fantastic performances 👏
Recruitment isn’t always easy. It takes consistency, resilience and plenty of determination to succeed.
Another great month in the books and a perfect excuse to get away from the desks, enjoy some good food and a few drinks! 🍻💪
#iFindTech #LunchClub #TechRecruitment
One of the easiest ways to lose a good engineer is to benchmark salary too simplistically.
“What’s the average Senior Developer salary in Stockholm?”
It’s a useful question.
But it’s not enough.
A Senior Developer at a 40-person product company can be a completely different profile from a Senior Developer at a large enterprise.
Then you’ve got Staff and Principal titles, which vary even more between companies.
Add specialist experience in areas like AI, security, platform engineering, mobile or distributed systems and the range gets wider again.
Norway adds another layer because compensation expectations don’t map perfectly against Sweden.
Then candidates compare pension, bonus, equity, holiday, flexibility and sometimes contracting income too.
We spend a lot of time talking to engineers about compensation before they’re actively interviewing.
That’s often where the useful salary data comes from.
Not what someone accepted two years ago.
What it would actually take for them to move today.
Happy Birthday to our CEO, Robert Collins! 🥳
From building iFindTech from the ground up to helping shape the team, culture and business we have today, it certainly wouldn’t be the same without him.
A brilliant CEO, leader and someone who continues to play a huge part in everything we do.
We hope you have a great birthday and enjoy the celebrations! 🍻❤️
Myth:
The best Senior Backend Engineer CV will have every technology in your stack.
Java. Kotlin. Kafka. Kubernetes. PostgreSQL. AWS. Terraform. Redis.
Reality:
We’d much rather see evidence that someone understands why and when those technologies should be used.
There’s a big difference between:
“Used Kafka”
and
“Designed an event-driven architecture and had to think about ordering, retries, idempotency and what happens when consumers fail.”
The same applies to Kubernetes.
Having deployed something to Kubernetes doesn’t automatically make someone strong in cloud-native engineering.
The engineers we rate highly tend to talk about trade-offs.
– Why did you choose that architecture?
– What broke?
– What happened at scale?
– What would you design differently now?
– How did you make the system observable?
That conversation tells you considerably more than counting keywords on a CV.
When we’re screening senior engineers, depth nearly always beats the number of technologies listed.
2 Years of Charlie Dell! 💙
Over the past two years, Charlie has become a huge part of the team, building some brilliant relationships across the Nordic market and making a great impact along the way. 🚀
It’s been amazing watching his journey so far, and we’re looking forward to seeing what year three brings!👏
#WorkAnniversary #TeamIFindTech #iFindTech #NordicTech
September Rundown 🍂
September has been a busy one at iFindTech and a great month for the team.
🏆 Owen took Consultant of the Month, alongside celebrating 5 years with iFindTech.
🎉 Lucy hit an incredible 6 years with us, while Ellis celebrated 2 years with the team.
🍻 Our incentive winners enjoyed a well earned afternoon out, and the Friday pub trips have continued to make an appearance.
💻 Programmers’ Day landed in September, giving us a chance to recognise the developers and engineers at the heart of the tech industry we work with every day.
📈 Most importantly, the financial year has started strongly. Plenty of new roles, conversations, interviews and placements already moving in the right direction.
And you know summer is officially over when the office aircon finally starts being left OFF.
Plenty happening. Plenty more to come.
On to October. 🚀
#iFindTech #SeptemberRundown #TechRecruitment #TeamCulture #Recruitment #Technology
Something we’ve seen happen more than once.
We start a search with a very specific technical brief.
The client knows exactly what they want.
Specific language.
Specific framework.
Specific cloud.
Specific background.
Then we introduce someone who doesn’t tick every box.
But they understand the engineering problem better than almost anyone else we’ve spoken to.
The interview happens.
An hour later, the conversation has completely changed.
Instead of:
“Do they have enough experience with X?”
it becomes:
“How quickly can we get them back in?”
Those placements are always a good reminder that a job description is a starting point.
Particularly at senior level, you’re rarely hiring a collection of technologies.
You’re hiring someone’s judgement, experience and ability to solve problems the company probably hasn’t encountered yet.
Sometimes the right candidate doesn’t match the brief.
They improve it.
Happy Birthday, Ellis Sullivan! 🎂
What better way to spend your day than off work on a Friday! 🍻
Wishing you a very Happy Birthday from everyone at iFind. Hope you have a brilliant day and make the most of the long weekend! 🥳💙
#HappyBirthday #TeamiFindTech #iFindTech
Stack: Kotlin · Kafka · Kubernetes · AWS · Terraform
Domain: Fintech · High-scale systems
Profile: Native Swedish · Stockholm-based
Then perhaps a very specific salary range on top.
Individually, none of those requirements sounds unreasonable.
Combine them and you’ve reduced the market dramatically.
This is where good hiring managers do something important.
They separate:
“Must already know”
from
“Can learn quickly”.
If someone is an exceptional Java engineer who understands distributed systems deeply, does Kotlin really need to be mandatory?
If they’ve operated Kubernetes on GCP, is AWS genuinely a blocker?
Sometimes it is.
Often it isn’t.
The strongest hiring processes we work on tend to identify the two or three things that genuinely predict success and stay flexible around the rest.
We’d take an exceptional 90% candidate over an average 100% keyword match every time.