Teen Meets
Corporate

The strange thing about meeting the corporate world as a teenager is how quickly a conversation about your work can become a conversation about your birthday.

You can explain what you built, how it works and where its limits are. You can answer questions about security, responsibility and delivery. Then someone notices your age, and suddenly the evidence feels optional.

That is the attitude I have a problem with. It is backwards. It is outdated. And dressing it up in professional language does not make it smart.

A policy can look tidy on a spreadsheet and still be a poor way to judge the person in front of you. If the process cannot distinguish between an actual risk and an unfamiliar situation, the process needs work.

Fifteen is not a permanent condition

The fifteen-year-old you dismiss today will, in the normal course of life, become eighteen. Then twenty-one. Then twenty-five. Then twenty-eight.

They do not spend the years in between frozen in place. They learn, build, make mistakes, take advice and get better. A person with useful skills at fifteen can have years of practical experience by the time your usual recruitment process decides they exist.

If your response to that person is “come back later”, think about what you are asking them to remember. You could be the organisation that gave them a careful first opportunity. Instead, you might become the organisation that made them feel stupid for trying.

There is a long-term business decision in that. People remember who took their work seriously. They also remember who would not even look at it.

You are meeting someone at the start of their working life. Act like there might be a future in it.

Looking corporate is easy. Using judgement is harder.

I do not think an adult is automatically incapable because they work for a large company. I do think a company becomes less intelligent when its people stop using judgement and start treating every existing rule as evidence that someone else already did the thinking.

“That is our policy” tells me what the decision is. It does not tell me whether the policy is good, whether it applies to this situation or whether there is an appropriate route for review.

If a rule comes from a real legal requirement, say that clearly. If it comes from a provider’s terms, explain the restriction. If it is an internal choice, own the choice. Those are different things, and a capable organisation should be able to explain the difference.

The intelligent response is to understand the work, identify the risk and decide what can responsibly happen next. Sometimes that decision will be no. It should still be a decision someone can explain.

Safeguards are good. Dead ends are not.

Young people need protection from pressure, exploitation and commitments they do not understand. They need room for education, rest and a life outside work. Having a skill does not make any of that disappear.

What I want is a process that can protect someone while allowing them to develop. A safeguard should address a particular risk. When every safeguard ends at the same blanket refusal, I think it is fair to ask whether anybody has tried to design a workable alternative.

Where the law and the activity allow it, that alternative might be a small paid project with a clear scope. It might be an adult representative for the contractual part, an independent adviser, limits on access or a review before a serious commitment. It should include a clear way to stop if the arrangement becomes unsafe or unsuitable.

None of those ideas should be used to get around a legal age restriction. They are ways to make a permitted opportunity more responsible. The details need proper review for the person, the work and the jurisdiction involved.

Protection should also mean fair treatment. “You are young, so be grateful for exposure” is not an opportunity. Neither is letting someone do the work while refusing to credit or compensate them appropriately.

Ask questions that tell you something

Show me the work. Ask me to explain it. Ask what I would do if it failed. Ask where I need help. Check references where appropriate. Set a realistic task with clear expectations.

Those questions give you evidence. They work for adults too.

A young person should not have to pretend to know everything to get a chance. Being able to say “I need someone qualified to review that” is part of good judgement. A company should value it instead of rewarding the person who confidently guesses.

Assess the actual skill for the actual task. Someone can be a capable developer and still need support with a contract. An experienced executive can understand a contract and still need a developer to explain a system. That is why teams exist.

Give people somewhere to go

You do not owe every teenager a job, a contract or access to your systems. You can have standards. You can turn down work that is not good enough. You can refuse arrangements that would be unsafe or unlawful.

But if the work is good and an appropriate opportunity is possible, do not put someone off just because their age makes the paperwork less familiar. Give them a clear route. Tell them what evidence you need, what support is required and what they could do next.

If they are not ready, useful feedback is better than a patronising brush-off. A specific gap can be worked on. “You are too young to understand” usually just closes the conversation.

I want the corporate world to be ambitious enough to recognise ability early and responsible enough to support it properly. That takes more thought than an automatic rejection. It is also a much better use of the intelligence these companies claim to value.

The teenager grows up. The skill develops. The question is whether your organisation grows with them, or keeps congratulating itself for a process that cannot.