Hire me as an apprentice? Why not.
Why this article?
A résumé gives facts. A cover letter gives intentions. But what's often missing is the context: why this field, how I actually work, and what I can concretely bring to a team. So rather than sticking to a classic format, I wanted to write this article the way I would write about any other topic: with clarity, and a bit of authenticity. In 2026, finding an apprenticeship is tough: many schools offer work-study programs, and a lot of them even make it mandatory (which isn't my case), especially in tech, a field that's constantly evolving, particularly with the rise of AI.
Who I am, concretely
After my first year, I realized that the Coding Factory format had gotten me used to an intense pace, with lots of hands-on projects, real deadlines, and a production mindset rather than purely theoretical learning. That's exactly the environment that suits me: learning by building, not just by watching. Although we were taught a wide range of technologies in first year, I built my projects mainly around Next.js/TSX. It's the ecosystem I'm most comfortable and most productive in: reusable components, strict typing, fast and consistent styling with Tailwind. I like understanding why an architecture works, why a technical choice makes sense in the long run, and how to deliver something clean rather than something that just works "for now"... that's my way of doing things.
Why an apprenticeship, and why now
For me, an apprenticeship isn't a box to check in a curriculum: it's not strictly mandatory, since my program can also be completed full-time. But I think it's the format that makes the most sense for progressing quickly in this field. Theory has its limits: it's through contact with a real codebase, real constraints, and a real product used by real users that you learn the most. What I'm looking for today is an environment that will push me, a team that will help me grow, and in exchange, I commit to giving everything I've got: rigor, curiosity, and a genuine drive to do things well.
What this means for you
Taking on an apprentice is an investment, I know that. But it's also an opportunity to train someone according to your methods, your tools, your product culture, rather than having to "undo" bad habits. And in my case, you're starting with someone who already has a solid technical foundation in a modern, in-demand stack (Next.js/Tailwind/TypeScript), combined with a product sensibility that goes beyond just code. I'm available right now to talk, discuss a project, or simply answer your questions. If you're looking for someone motivated, curious, able to adapt quickly, and who cares as much about the final result as about clean code, we should talk.