My Journey at Tezi 🚀

The interview was... unexpected.

I walked in expecting questions like:

“What's the difference between var, let, and const?”

Nope. 😂

Instead, Krishna Sir opened my Smart Link Intelligence project and started asking why I built things the way I did.

Every answer led to another cross-question.

• “Why this architecture?”
• “What happens if 10,000 users use it?”
• “Why did you choose this database?”

It felt less like an interview and more like someone trying to understand how I think.

At the end, instead of saying “You're selected”...

He handed me a GitHub repository.

“Contribute something. Raise a PR. Then come back.”

I was like...

“Bro, my right hand? Nope... only my right thumb works.” 👍😭

I genuinely thought he was treating me like a beginner with some tiny assignment.

I was very wrong.

9 PM. PG Room. Reality Check.

I opened the repository around 9 PM.

It was a Journal App.

Within five minutes... I was completely lost.

I couldn't understand 80% of the project.

I didn't even understand the README.

There were words everywhere:

I was reading English... but understanding absolutely nothing. 😂

I thought,

“Forget contributing... let's at least run the project.”

npm run dev

Boom. Error.

Three hours later... another error.

After a lot of Googling, AI conversations, documentation, and pure stubbornness...

Around 12 AM, the project finally started.

Seeing it run felt like I had deployed Google itself. 😭

My First PR (and my first embarrassment)

I somehow understood one small feature, made changes, and submitted my first Pull Request.

The next day I proudly showed it.

Krishna Sir looked at it and said:

“Cool. Now explain your PR.”

Line by line.

Or at least feature by feature.

My brain immediately left the meeting.

Because... AI had written most of it.

I started fumbling.

Trying to explain code I didn't actually understand was painfully obvious.

That day I got one of the most valuable lectures I've ever received.

He didn't tell me to stop using AI.

He taught me how to use AI effectively.

That conversation genuinely changed the way I code.

The 15-Day Challenge

Instead of giving production work immediately, we got homework.

One topic. Every day.

Learn it. Then implement it from scratch in your own Journal App.

...and many more.

For the next 15 days, that's exactly what I did.

Every day was learn → build → break → rebuild.

I also started using AI differently.

Instead of asking “Build this for me,” I started asking “Explain why this works.”

(You can still find that entire 15-day roadmap inside my GitHub plan folder.)

Welcome to Production Engineering

After those 15 days, things changed.

Our team was handed a real project:

Plot twist?

I had never written Flutter before.

Not even once.

New framework. New language. New codebase.

Surprisingly... it wasn't scary anymore.

I had learned how to learn.

Within a few days, Flutter started making sense.

For the next 2.5 months, we worked on HelioCoach as a team.

This was my first time seeing how production software is actually built.

GitHub finally became real.

We weren't sending ZIP files anymore. 😂

We worked with:

• Feature branches.
• Pull Requests.
• Reviews.
• Merge conflicts.
• Production code.

Everyone owned different features.

Everyone raised PRs.

Everyone explained their changes.

That's when GitHub stopped being a website and became part of my workflow.

The Scariest Chair in the Office 💀

There was one chair.

Right beside the CEO.

That chair had one purpose.

Explaining your Pull Request.

Initially, I hated sitting there.

I'd vibe code something, submit a PR, and then get asked,

• “Explain this function.”
• “Why did you do this?”
• “What's happening here?”

Silence.

Embarrassing silence. 😂

But something changed after repeating this enough times.

I stopped submitting code I couldn't explain.

Before opening a PR, I made sure I understood every major part of my implementation.

That chair slowly became less scary.

The Best Feeling Ever

About a month later...

I opened GitHub and saw something different.

My PR...

No discussion.

No “Explain this.”

Just merged.

It sounds like a tiny thing.

But for me, it genuinely felt like a celebration.

Because it meant someone trusted my code.

What Tezi Changed For Me

Tezi didn't just give me my first internship.

It completely changed how I approach software engineering.

I learned that:

• AI is a teammate, not an autopilot.
• Reading documentation is part of the job.
• Planning architecture saves hours later.
• Code isn't finished until you can explain it.

I walked in thinking I knew how to build projects.

I walked out understanding how engineering teams build products together. ❤️