From a First Class Honours graduate working in London's tech scene: practical insights that university doesn't teach you.
When I walked across the stage to receive my First Class Honours degree in Software Engineering from the University of Greenwich, I felt a mix of pride and uncertainty. I'd spent years learning algorithms, data structures, and programming languages, but the reality of entering the tech industry in London hit differently than I'd expected.
Now, working as an IT Service Desk Analyst whilst actively pursuing software engineering roles, I've gained insights that would have made my transition smoother. If you're a computer science or software engineering student preparing to graduate, here are five truths I wish someone had told me earlier.
What I thought:
My First Class Honours and solid academic record would open doors.
The reality:
Recruiters spend an average of 6 seconds scanning your CV. What catches their eye isn't your grade — it's what you've built.
During my final year, I developed a CI/CD automation project using TeamCity and GitHub that was nominated for the Best Project Award. That project has been mentioned in almost every interview I've had. Meanwhile, my excellent grades in theoretical modules? Rarely discussed.
What I did about it:
I built Skill Maps, a full-stack e-learning platform using React, Node.js, Express, and PostgreSQL. This project demonstrates:
Actionable advice:
Start building now. Don't wait until after graduation. Pick a problem you care about and build a solution. Make it live. Put it on your CV. It matters more than your dissertation grade.
What I thought:
Graduate schemes and internships are the primary entry points.
The reality:
These programmes are incredibly competitive and often have lengthy application processes involving multiple video interviews, assessment centres, and technical tests that can take months.
As someone whose first language isn't English, I found video interviews particularly challenging. The time investment for graduate schemes felt like a gamble when I needed to start earning.
What I discovered instead:
Actionable advice:
Don't put all your eggs in the graduate scheme basket. Apply broadly. The path into tech isn't one-size-fits-all, and that's absolutely fine.
What I thought:
My customer service experience was irrelevant to software engineering.
The reality:
It makes me a well-rounded candidate who understands both technology and people.
My experience in customer service taught me skills that many developers lack — and employers value these highly.
What I gained from customer service:
These aren't "soft skills" — they're essential professional capabilities that bridge the gap between code and real-world business problems.
Actionable advice:
Stop apologising for your "non-traditional" background. Reframe it as your unique value proposition. The tech industry needs people who can bridge different domains.
What I thought:
Speaking Romanian, Russian, German, and English was just... normal for me.
The reality:
In London's global tech market, this is a massive advantage.
Many companies operate across Europe, have international teams, or serve multilingual users. Being able to:
...is genuinely valuable. I've seen job postings specifically seeking developers with European language skills.
Actionable advice:
List your languages prominently on your CV and LinkedIn. Don't hide this skill at the bottom — it differentiates you from monolingual candidates.
What I thought:
I needed to land the perfect software engineering role immediately after graduation.
The reality:
My IT Service Desk Analyst role has been incredibly valuable and taught me so much:
This experience makes me a better developer because I understand the full picture — not just how to write code, but how it gets used in real organisations.
Working whilst job searching also means:
Actionable advice:
Don't turn down "not-quite-right" tech roles whilst waiting for the perfect position. Every role in the tech ecosystem teaches you something valuable. You can always move later.
One decision I made that's already paying dividends: building Skill Maps as a public portfolio project.
Instead of just having projects on GitHub that nobody sees, I:
Recruiters can see that I can ship production code. That's powerful.
If I could go back and give my final-year self advice, it would be this:
Your degree is the foundation, not the destination.
The real learning happens when you build things, navigate the job market, and adapt to the reality of the industry.
The path isn't always linear. It's fine if your first role isn't your dream job. It's fine if you take longer than expected to land your ideal position. It's fine if your journey looks different from your classmates'.
What matters is that you keep building, keep learning, and keep moving forward.
I'm currently seeking junior developer, full-stack engineer, or data analyst roles in London. My combination of software engineering expertise, multilingual capabilities, and experience bridging technical and business needs makes me a strong candidate for diverse tech roles.
What do you wish you'd known before graduating?
Share your experiences on LinkedIn — I'd love to hear from you.