vikash.v
RETURN TO LOGS
July 20, 2026

Points We Can't Write — The Real Resume

#Personal

Every few months, I update my resume.

I rewrite a few bullet points.

Change the order of projects.

Add a new role.

Remove an old one.

Maybe tweak a sentence until it sounds a little more impressive.

Eventually, I export it as a PDF and think, "Yeah... this looks good."

Then I close it.

Because the moment I do, I remember how little of the story actually made it onto those pages.

Resumes are strange things.

They capture outcomes.

Never the journey.

They'll tell you I worked as a research scientist.

They won't tell you about the nights I sat staring at research papers that felt impossible to understand. The ones I read over and over until a single paragraph finally started to make sense.

They'll tell you I built projects.

They won't tell you how many never made it past the prototype stage. Or how often I deleted weeks of work because I realized I had solved the wrong problem.

They'll tell you I studied engineering.

They won't tell you what it felt like to sit through classes while the technology I cared about was changing faster than the syllabus ever could.

That's the strange thing about resumes.

The most important parts never fit inside them.


A few years ago, I was a diploma student in Coimbatore.

I didn't have a grand plan.

I just liked building things.

One project led to another.

Curiosity turned into habit.

Habit slowly became obsession.

Somewhere along the way, I found myself working on AI research while I was still trying to finish college.

Looking back, I don't think there was one big turning point.

It was thousands of small decisions.

Opening one more paper.

Trying one more experiment.

Breaking one more project.

Starting over.

Again.

And again.


People often imagine learning as a straight line.

Mine never looked like that.

It looked like confusion.

Like reading the same paper five times and understanding a different sentence each time.

Like realizing that learning AI wasn't just about Python.

It was mathematics.

Statistics.

Computer architecture.

Distributed systems.

Optimization.

And, more than anything else, learning how to be comfortable saying,

"I don't know yet."

That word yet turned out to matter more than I expected.


College, meanwhile, kept moving at its own pace.

Attendance.

Assignments.

Exams.

Marks.

Outside the classroom, everything moved differently.

Research didn't care about attendance.

Production systems didn't care about semester breaks.

Users didn't wait because it was exam week.

Living in both worlds at once often felt like switching between two different realities.

One rewarded having the right answers.

The other rewarded asking better questions.


There are projects nobody will ever see.

Ideas that lasted a weekend.

Experiments that failed before they even began.

Entire weeks spent chasing problems that turned out not to be worth solving.

For a long time, I thought those were wasted efforts.

I don't anymore.

Every failed experiment quietly changed the way I approached the next one.

Not every project has to survive to be valuable.

Sometimes its only job is to teach you why the next version should exist.


The biggest things I've learned never came with certificates.

They came from frustration.

From rebuilding something after breaking it.

From admitting I didn't understand.

From asking for help.

From trying again anyway.

Those lessons don't belong on a resume.

They're difficult to measure.

But they're the reason the bullet points exist in the first place.


There's another part we rarely talk about.

The cost.

Somewhere between projects, research, classes, and deadlines, I stopped noticing weekends.

Friends slowly stopped asking because I was usually busy.

The laptop became a permanent fixture beside me.

I don't think anyone consciously chooses that life.

It just happens one late night at a time.

One deadline.

One idea.

One more thing you tell yourself you'll finish before going to bed.


I still update my resume.

I probably always will.

It's useful.

Necessary, even.

But I've stopped believing it's the best summary of who someone is.

The real resume is written in the things no recruiter will ever read.

The questions you kept asking when nobody expected you to.

The failures that quietly changed the way you think.

The curiosity that refused to leave you alone.

Those things don't fit into bullet points.

Maybe they were never supposed to.