Day 4 — Your Portfolio in the AI Era

Something changed in 2024 and most freshers have not noticed yet.

The average resume now looks significantly better than it did two years ago. AI tools help students write polished bullet points, clear project descriptions, and professional summaries. Every resume sounds confident and structured.

The problem: when everyone's resume sounds good, the resume stops being the differentiator.

What differentiates you now is proof.

Not claims. Proof. A URL that opens. Code that runs. A project that does something real.

Why This Matters More Than Before

Two years ago, a resume that said "Built a web application using React and Node.js" was enough to get a callback. The recruiter assumed it was true.

Now, recruiters — especially at product companies and good startups — assume the description was written with AI help. They want to see the thing itself.

This is not a disadvantage if you act on it. Most of your competitors have not built anything real. They have descriptions of projects that barely work or were built by copying tutorials. If you have working projects with live URLs and clean GitHub repos, you stand out immediately.

What Recruiters Actually Check in 2025

Based on what hiring managers at Indian tech companies have shared publicly:

Service companies (TCS, Infosys, Wipro): Still mainly resume-driven. But having a portfolio URL adds credibility. They may not visit it during the first screen, but it matters in the technical interview when they ask "tell me about your project."

Mid-tier product companies (Zoho, Freshworks, Persistent, Mphasis): Actively look at GitHub. They check if the repos are real — do they have commits over time or was it one big push? Is there a README? Does the code look like you wrote it or copied it?

Startups and early-stage companies: Portfolio is often more important than the resume. They want to see what you can build, not what grades you got.

MNCs with structured campus programs (Amazon, Microsoft, Deloitte): The resume gets you the interview. The portfolio strengthens the technical interview. They will ask you to walk through a project in detail — having a live URL makes this easier and more convincing.

The Three Types of Projects — Ranked by Impact

Tier 1 — Projects you built because you had a real problem to solve

These are the best. You needed something, you built it, it works, you use it.

Examples:

• A tool that sends you WhatsApp alerts when your college timetable changes
• A script that tracks the prices of textbooks on Amazon and notifies you
• A bot that fills your attendance portal automatically

These are compelling because they are real. You can explain every decision because you made every decision.

Tier 2 — Projects that demonstrate a specific technical concept

The RAG bot, job search agent, and MCP server from this course fall here. They show you understand the technology, even if you do not use them daily.

These are good for demonstrating AI knowledge which is in high demand right now.

Tier 3 — Tutorial projects you customised

Following a YouTube tutorial and then adding features is better than nothing. But be honest about this in interviews. "I followed a tutorial for the base structure and added authentication and the dashboard myself" is a legitimate answer.

What is not legitimate: claiming a tutorial project is fully original.

Exactly What to Include in Your Portfolio

For each project, have these four things:

1. A live URL — The project should be deployed and accessible. Vercel and Railway offer free hosting. If it requires a backend that costs money, deploy a demo version.

2. A clean GitHub repository — With a README that explains: what the project does, what tech stack it uses, how to run it locally. Commit history should show work over time, not one dump of code.

3. A 30-second explanation — Practice saying what the project does, what problem it solves, and what was technically interesting about building it. This is what you say in the interview.

4. One thing that was hard — Every real project has one part that was harder than expected. Know what that was and how you solved it. This is what interviewers ask about.

Do NOT include:

• Hello World programs
• Calculator apps (unless genuinely unusual)
• Projects where you cannot explain the code
• Projects with no commit history
• Projects where the live URL is broken

The Portfolio URL You Should Have

Your portfolio itself should be a project. Not a PDF. Not a LinkedIn profile. A website with your own domain or at minimum your name as the URL.

lakshmi-bandari.vercel.app is better than nothing.
lakshmi.dev (₹800/year) is better than a Vercel URL.
resumeportfolio.in/lakshmi shows you know and use your own tools.

Day 8 of this course walks you through building and deploying a portfolio site in 90 minutes using AI tools. If you have not done that yet, do it before applying anywhere.

The AI Impact on Portfolio Building

Here is the opportunity most students are missing:

AI tools can help you build projects that used to require months of learning. The three technical projects in this course — a RAG bot, an AI agent, and an MCP server — each took a few hours to build with AI assistance.

Two years ago, those projects would take a dedicated student 3-4 months of learning to build.

If you build them, add them to your portfolio, and can explain them in an interview, you are showing technical depth that was previously only accessible to students with strong mentors or expensive bootcamps.

The playing field has leveled. Use the tools.

Your Action Item

Look at your current projects. Apply this filter:

1. Does it have a live URL?
2. Does it have a clean README on GitHub?
3. Can you explain it in 30 seconds without notes?
4. Can you explain what was hard about building it?

Any project that fails more than one of these criteria needs either improvement or removal.

Pick one project and spend 30 minutes today making it pass all four criteria.

Day 4 of 15 — AI Survival Kit for Engineers