Write the CV That Scares You — and Sets You Free


Introduction: Why This Matters
There was an FNB opportunity recently, and it made me pause. I saw brilliant individuals around me struggling with one basic thing — writing a CV. Not because they lacked skills, but because they believed they had nothing worth putting down. That hit me. It made me realize: we're not lacking qualifications — we're afraid of expressing our uniqueness.
We have so much within us — languages, small projects, creative quirks, untold resilience — yet we hide behind bland templates and generic buzzwords. We try to fit into templates, mold ourselves into blueprints that don’t belong to us, and strip away the most valuable thing we have — our authenticity.
The Biggest Mistake: Writing What You Think They Want to Hear
Let’s get one thing straight:
A CV is not a template — it’s a mirror.
Most people think writing a CV means following a set formula:
List education
Add “team player” and “good communicator”
Pray someone notices
But that’s not how it works — especially not in tech. In this space, we’re not just filling roles. We’re building things that touch lives. And lives aren’t built with templates. They're built with truth.
Your CV should be the boldest, clearest reflection of who you are when you’re not in the room.
“What impression do I leave when I’m not in the room?”
“What do I believe in?”
“What sets me apart?”
Those are the questions your CV should answer.
Own Your Uniqueness — Especially the Weird Bits
People often underestimate the value of what they consider "non-technical."
Someone told me not to include Japanese or Russian on a CV — “Why does that even matter?” they said.
But here’s the truth: language bridges cultures. In tech, we’re building across dimensions and borders. Every unique trait is a piece of the puzzle.
Whether it’s a foreign language, writing blogs, running a campus club, or mentoring friends — put it in. Don’t hide behind what you think is expected. Show up as who you are.
Language skills?
Beginner-level coding?
Fixing typos in someone’s README on GitHub?
All of that counts.
Don’t say you have “nothing.”
Even if you're just getting started — you still count. What matters is:
Can you hold a conversation about what you’re learning?
Can you talk about what excites you in tech?
Your CV should show that you're on a path — not perfect, not finished — just committed.
3. There’s No Perfect CV — But There’s an Authentic One
There’s no such thing as the “perfect CV.”
But there is such a thing as the true CV.
Yours.
You’re not expected to be an expert — especially not for internships or junior roles. The idea is to reflect growth, effort, and curiosity. If you’ve started learning Java, say it. If you’ve built a simple portfolio, include it. If you fixed a bug or added a README
section on GitHub, talk about it.
Skills are like blades — they don’t come sharp. You sharpen them over time. Show that journey.
Structure: Simplicity is Sophistication
People reviewing CVs? They don’t read — they scan.
Write your CV like you’re explaining it to someone who knows nothing about what you do. Clear, bold headings. Divided sections. Straightforward language.
“Simplicity is the ultimate sophistication.”
Here’s what to include:
Profile: Your essence in 3–4 lines
Skills: Even the “weird” ones — they’re often your strongest
Education: Straightforward and honest
Projects: Real or personal — just show initiative
Experience: Paid or volunteer, it all counts
Interests & Awards: Let your curiosity show
Avoid long paragraphs and jargon. Your story is enough — just say it plainly.
5. No Experience? Then Prepare — One Tiny Step at a Time
Don’t wait for opportunities. Prepare for them.
One of the most common things I hear is:
“But I have nothing to include.”
You do.
You just haven’t listed it yet.
Before applying, invest in yourself. Not in big frameworks, but in tiny steps:
Learn what GitHub is
Contribute to a repo (even fixing typos helps!)
Watch a course
Write a LinkedIn post
Help your classmate with code
Volunteer to digitize something for your school
Document your growth
Help others on X, or any other coding platform.
These are only a few, there is so much more than what i have just listed.
Each one is a seed. Put it on your CV.
Your Small Wins Are the Real Wins
These aren’t “tiny” things — they’re foundational.
They show initiative, consistency, curiosity. They show you care.
And that’s exactly what recruiters are looking for.
Don’t underestimate these small things:
Wrote a blog? You’re a technical writer.
Fixed a README? You’re a GitHub contributor.
Tutored a friend? You’re a peer educator.
Stop chasing perfection.
Start honoring your journey.
If you can excel in the small things, you can be trusted with the big ones.
Bravery Is the Real Skill in 2025
In the age of AI, anyone can fake it.
You can use ChatGPT to generate the “perfect CV.”
But is it you?
This is the time to be brave enough to be yourself.
Put down the words that scare you. Share what you think isn’t enough. Show the world what you truly care about.
Authenticity isn't fluff — it’s a filter.
It attracts the right opportunities, the right teams, the right mentors.
The more honest your CV is, the more aligned your future becomes.
🧭 Final Thoughts
Your CV isn’t just a document. It’s your fingerprint in a world of clones.
Be clear. Be bold. Be simple.
Most importantly — be you.
When opportunities come (and they will), may your CV be ready — not as a list of buzzwords, but as a celebration of the path you’ve walked and the one you’re building.
Because the CV that scares you to write?
That’s the one that will set you free.
Subscribe to my newsletter
Read articles from Ray Mcmillan Gumbo directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by

Ray Mcmillan Gumbo
Ray Mcmillan Gumbo
A deep thinker, builder, and learner sharing my journey through tech and thought. This blog is my space to reflect, explore hard questions, and document growth — not just in skills, but in purpose. It’s for anyone who feels lost, curious, or stuck — a reminder that your voice, ideas, and path still matter. Here, I write before ideas become products and code becomes real — the foundation behind Ryom and the questions that drive it.