From trainee to first job: what our graduates did differently
We asked graduates who landed a role within three months what made the difference. The answers were surprisingly practical.

Every intake ends with the same question: what now? Some graduates find a role within weeks; others take much longer. We wanted to know what the quick ones did differently, so we asked them.
Talent helped, of course. But the answers had much more to do with habits than with brilliance, and every one of those habits can be learned.
They shipped one project they could explain
Not five half-finished tutorials, but one complete project, online, that they understood end to end. In interviews, they could explain why it was built the way it was, what went wrong and what they would change.
Nobody hired the person with the most certificates. They hired the one who could walk through their own project.
They kept their profiles tidy
- A GitHub profile with pinned projects and a short README for each.
- A LinkedIn profile with a clear headline and the project linked.
- A CV of one page, with the project near the top.
They practised explaining out loud
Several graduates recorded themselves explaining their code, then watched it back. It felt awkward, they said, but it made interviews feel familiar. In class, we now run mock interviews where trainees present their project to a trainer they haven't worked with.
They applied steadily
The graduates who found work fastest applied every week, a few roles at a time, and adjusted their CV based on what came back. Applying to fifty places in one burst and then waiting rarely worked.
What we changed because of this
That is why every path at Tamkeen now ends with a project you build with a team and present, why we review CVs and profiles in the last weeks, and why our partner companies join demo days. The skills matter; being able to show them matters just as much.





