Your responsibilities tell an employer what your job was.
Your impact tells them how good you were at it.
We asked the team:
How can you demonstrate impact rather than just listing responsibilities?
👉 Swipe through for the team’s advice.
#iFindTech #ConsultantTopTips #SoftwareEngineering #TechRecruitment
Not bad for a Monday! 👏
Two deals over the line within five minutes of each other.
Massive effort, Charlie Dell. What a start to the week!
🔐 We’re Hiring – Lead Information Security Engineer
📍 Oslo
Looking for a role where you can take real ownership of information security?
We’re partnering with an established Norwegian technology company looking for a hands-on security professional with a strong technical background.
You’ll combine security governance, risk management and technical security while working closely with engineering teams.
✅ 6+ years’ relevant experience
✅ Strong technical background
✅ Security governance & risk management
✅ Fluent Norwegian
📩 Interested? Contact Charlie Dell at charlie.dell@ifindtech.com
#CyberSecurity #OsloJobs #InformationSecurity #Hiring
A great hire isn’t just about finding the right person. It’s about what happens next.
Months of searching, technical meetings and conversations can go into finding the right software engineer.
But the first 90 days in a new role are just as important.
Even the most experienced engineers need time to understand a new codebase, get to know their colleagues and learn how the business operates.
And the companies that recognise this can give their new hires a much stronger start.
We’ve always believed that a successful placement isn’t simply someone accepting an offer.
It’s seeing that person settle in, contribute and become a valued part of the team.
Because the real success of a hire is measured long after their first day.
Would you hire a software engineer who uses AI to write 70% of their code?
They use tools like Claude Code, Cursor and GitHub Copilot every day.
They deliver features faster, automate repetitive tasks and spend more time solving problems than writing code from scratch.
But here’s the question.
If they’re not writing most of the code themselves, does that make them a less capable engineer?
Or are they simply making better use of the tools available to them?
Of course, there’s a difference between generating code and actually understanding it.
An engineer still needs to make architectural decisions, identify mistakes, understand security implications and take responsibility for what goes into production.
At iFindTech, we think the interesting question isn’t how much code an engineer writes themselves.
It’s how well they understand what they’re building.
Would heavy reliance on AI coding tools concern you when hiring an engineer?
🚀 SENIOR FULLSTACK DEVELOPER | POLAND
We’re working with a fast-growing global AI start-up building an innovative AI-powered platform for the legal industry.
They’re looking for an experienced Fullstack Developer to help build and scale their product.
💻 Tech stack: Python, FastAPI, React, TypeScript, PostgreSQL, Redis and LLM technologies (RAG, AI agents).
✅ 5+ years’ software development experience
✅ Strong frontend and backend skills
✅ Fluent Polish and English
✅ Experience or a strong interest in AI/LLM development
Interested in finding out more?
📩 Get in touch with Charlie Dell for a confidential conversation about the opportunity.
Imagine you’re a fintech company hiring a Senior Software Engineer.
You have two candidates.
One has spent eight years working in financial services.
The other has spent eight years building complex, high-traffic platforms in gaming.
Both are technically strong.
One understands your industry, its regulations and its challenges.
The other brings fresh perspectives, different approaches and experience solving problems your team might never have encountered.
Who would you hire?
At iFindTech, we regularly see how industry experience can influence hiring decisions.
And sometimes, it’s absolutely essential.
But other times, companies could be overlooking exceptional engineers simply because they’ve built great technology in a different sector.
Is industry experience a genuine requirement, or just a preference?
AI can match your CV to a job description in seconds.
But should you actually take the job?
That’s a very different question.
AI can identify that you know React, TypeScript, AWS and Kubernetes.
It doesn’t necessarily know that you’re leaving because you want more technical ownership.
Or that you never want to work in consultancy again.
Or that becoming an Engineering Manager would actually take you further away from what you enjoy.
Or that you’d accept an office-based role for an exceptional company, despite telling everyone you want remote.
These are the conversations we have every day.
We absolutely use AI to help identify opportunities and make better matches.
But careers aren’t keyword searches.
The better we understand the person behind the profile, the better companies and opportunities we can put in front of them.
AI can help find the opportunity.
We help work out whether it’s actually worth taking.