You know the ad. Entry level. Three years of experience required. It reads like a joke, and it is one, but the people who post it are not stupid. They are asking a real question in a clumsy way. If you understand the question, you can answer it without the three years.
What the ad is actually asking
Nobody hiring a junior expects three years of anything. What they are trying to avoid is the candidate who has only ever worked alone, on their own machine, with no deadline and no one reading their code. Companies hire to reduce risk. A candidate with a shipped project, a codebase other people depend on, and a senior who can say how they handled feedback carries far less risk than one with a portfolio of tutorial clones, however polished.
So the real question is: have you done the job, even once, under real conditions? Real conditions means a client who cares about the outcome, a scope that was agreed before you started, code review from someone senior, and a deadline that moved when reality did. Most junior candidates cannot answer yes. That, not the number of years, is the gap.
Why personal projects do not close it
Personal projects prove you can write code. They do not prove you can work. The difference sounds small and is the whole interview. A to-do app you built alone never had a stakeholder change their mind halfway through. It never had a pull request rejected with a paragraph explaining why. It never ran in production for someone who would notice if it broke. Interviewers know this, which is why “tell me about a project” goes quiet so quickly when the project only ever had one user.
The four things that move an interviewer
- A deploy you can talk about. Not a repository, a running thing that a real organisation uses, with a name you are allowed to say out loud.
- The reviews it went through. Being able to describe a change you were asked to make, why it was asked, and what you learned from it is worth more than any framework on your CV.
- A senior who will vouch for you. Not a lecturer, a working engineer who saw you handle a real deadline and real feedback and is willing to say so.
- Something concrete to negotiate with. When the offer comes, you point at evidence instead of describing potential. What they offer is still their call, but the conversation is a different one.
How to get all four in one project
This is what Blacksmith.Works is for, so we will say plainly how it works. A company brings us an internal tool or a scoped feature they keep not building. Our senior engineers turn the brief into a solution architecture and a Jira board with sprints and tickets. You apply for a slot, take a scoped part of the build, and ship it over four to sixteen weeks depending on the project size, working roughly eight to fifteen hours a week on a schedule agreed up front.
Every pull request you open is reviewed by a senior engineer with at least five years of production work, with a written rationale, not a thumbs-up. You get weekly check-ins with your mentor and mentoring hours for the moments you are stuck. When your part ships, you earn the right to list the client as a reference on your CV, and your public Anvil Stamp page records what you shipped.
It is not free for you. A Starter project costs €399, a Professional one €749 and an Enterprise one €1,299, with a full refund within 14 days if the project has not started. We charge because the seniors reviewing your code are paid for every review and every hour, and because a real client is paying attention to your work. That is the price of it counting.
What to do this week
- Read the apprentice page and decide whether eight to fifteen hours a week is honest for you right now. A real project needs a real schedule.
- Look at the three project sizes and pick the one that matches your level, not your ambition. Starter is a real product with real auth and a real database; nobody is bored on it.
- Create your profile and apply. Applications are reviewed by our admins, and if it is a fit you will be on a Jira board with a mentor before the month is out.
Nobody hands you experience. But you do not have to wait three years for it either. You can forge it in one project, and walk into the next interview with something to point at.