What to say when you have no commercial experience

The main rule

Don't apologise. "Unfortunately I have no experience, but I really want to learn" is a sentence after which people talk down to you.

Employment isn't the only experience. If you've built things with your hands, you have something to talk about — and it should be said calmly and factually.

What counts as experience

• Your own finished projects. Especially ones that at least you use.
• Team work on a shared project. Highly valued, because it's the hardest to get on your own.
• Contributions to open projects. A merged change is public proof you can work to someone else's rules.
• Volunteer work. A real client with real requirements and deadlines.
• Automation at a previous job. Even if you weren't a programmer: formulas, scripts, assembling reports — that's problem-solving experience.

How to answer

Bad:

I have no commercial experience, only study projects. But I learn quickly.

Good:

I haven't been employed in the field. For the last six months I've been building an expense tracker: the full cycle from database to deployment, and I use it myself. There was also a team project with three of us, where I owned the data and went through having my code reviewed for the first time. I'm happy to show the code and talk through the decisions.

The second answer is the same length but has substance. The only difference is that the person isn't apologising, they're describing.

On honesty

Don't dress up study projects as commercial ones. It surfaces within two questions and ruins the whole impression at once.

The right move is to name things accurately and show you understand the difference: "I know real work is different — someone else's code, deadlines, requirements that shift. The closest I've come was a project for a dance studio, where there was a live client and revisions."

That answer shows maturity, which is valued no less than knowledge.

What you lack without a job

Say it plainly if asked: working with old code you didn't write, requirements that change, responsibility for outages. Knowing your gaps makes a good impression.

And immediately say what compensates: team work, contributions to other people's projects, the fact that you've written code for someone other than yourself.

What closes the question best

The ability to check your claims. A working link. A change history showing how you worked.

And a confirmation from the person you built something with: when the description of your part wasn't written by you, "no commercial experience" stops meaning "did nothing". It means exactly what it says — nobody paid you for it.