The Internship That Taught Me to Read Between the Lines of a Job Offer

I didn't read the job description.

I didn't check Glassdoor.

I didn't ask a single senior what the company was actually like on the inside.

I just sat for the drive, cleared the rounds, and found out three months later — the hard way — that "placed" and "safe" are not the same word.

Back with issue #4 of The DEV Guide I Wish Existed — this time: the framework I built to screen a company before I ever sit for its drive, because once you're selected at most colleges, you can't say no. The offer letter isn't where you catch a bad fit. The 30 minutes before you apply is.

If you read Issue #1, you know the short version: a paid, three-month, work-from-home internship at a small Bangalore startup. The first two months were fine. Then I became the only person in the IT department — blamed for things I hadn't built, watching a non-technical founder change UI flows every few days, carrying 6+ hours of solo dev work most nights after a full day of college. No new hires. No real learning. Just "use Cursor" as the answer to everything. I left five days before my sem 6 finals. (That's the short version — Issue #1 has the rest.)

That post was about the path after the damage. This one is about making sure there's no damage to write about next time.

Because the internship wasn't the real mistake. The real mistake was sitting for that drive without checking a single thing about the company first.

How Campus Drives Actually Work (And Why That's a Problem)

Here's the thing nobody tells freshers until it's too late:

Company shows up on campus. HR gives a PPT. You submit your resume. You clear the rounds. You're in.

And once you're in — at most colleges — you can't say no. Your placement cell marks you "placed." You're locked out of every future drive. Done. Game over. Thanks for playing.

That 30-minute window between the PPT ending and the application deadline closing? That is the single most important decision point of your entire placement season. And almost nobody treats it like one.

Everyone around me was applying to everything. Package looks good? Apply. Company name sounds big? Apply. Free pizza at the PPT? Apply.

I did that too — once. You already know how that turned out.

So when placement season came around for real, I made one rule: not every company that shows up on campus gets my resume. I sat for drives before Simform — but only the ones where the role actually matched what a fresher SDE should be doing. Not what a mid-level developer should be doing at fresher pay.

Here's the framework I used to decide.

The Framework: Screen Before You Apply

1. The JD Reality Check

Read the job description like a contract, not a movie poster.

If a company is hiring for "SDE Fresher" but the JD asks for Kubernetes, microservices architecture, CI/CD pipelines, and "2+ years of production experience" — that is not a fresher role. That's a senior role wearing a fresher's salary.

Here's what I actually look at:

Does the tech stack match what a final-year student could reasonably know? React, Node, basic SQL — fair game. Terraform, Kafka, distributed systems — you're not hiring a campus graduate, you're writing creative fiction dressed as a PDF.

Is the role description specific? "You'll work on exciting, cutting-edge projects" is a sentence that means absolutely nothing. "You'll build internal tools for our ops team using Node and PostgreSQL" — that means something. If they can't tell you what you'll actually be building, it's because they don't know either. Or worse — they know, and they don't want to say it out loud.

Does "SDE" actually mean SDE? I came across one listing — fresher title, legit-looking JD on paper. Dug a little deeper. The actual work? AI data labeling. Not software development. Not engineering. Labeling. If I hadn't checked, I'd have walked in thinking I was getting an engineering role and walked out tagging training data for someone else's model.

That last one is why I check every JD now. The title on the campus poster and the work on the ground can be two completely different stories.

2. HR and Support Signals (Visible Before the Drive)

You can learn a lot about a company during the pre-placement talk — if you know what to listen for. Most students zone out during the PPT. I get it. The slides are boring. The HR is reading from a script. But this is your recon window.

The PPT is not a TED Talk. It's an interrogation — and you're the one asking the questions.

A few that are worth asking out loud, or at least listening for answers to:

"How is the onboarding structured for freshers?" — If they fumble this, they don't have one. And if they don't have one, you're going to spend your first month figuring out where the codebase even lives while your Slack messages go unanswered.

"What does the team look like? Will I have a mentor or a lead?" — If the answer is vague, there's a nonzero chance you end up as the entire IT department. Ask me how I know.

"How does escalation work if there's a conflict with a manager?" — This one scares most HRs. Good. If they have a real answer, the company has a real structure. If they dodge it, you're on your own when things go sideways.

"How long has the HR team been with the company?" — Not because tenure automatically means quality. But if everyone in the room joined in the last six months, something is pushing people out — and that something will eventually come for you too.

3. The LinkedIn Audit

This is the check that catches exactly the kind of mismatch from Section 1.

Before you apply for any campus drive, spend 20 minutes — just 20 — doing this:

LinkedIn: Search for people with the exact same job title at that company. Open three or four profiles. What does their "About" section actually describe? What skills are they listing? Does any of it match the JD you were handed — or does it tell a completely different story?

Glassdoor: Filter by "Intern" or "Fresher." Ignore the star ratings — those are about as reliable as Yelp reviews for a restaurant that pays for placement. Read the actual text. Look for patterns. If three separate reviews all mention "no learning" or "assigned work outside the role," that's not a coincidence. That's a signal.

Ask seniors. Not the ones who got placed there three years ago and have already moved on. The ones who are currently there, or left recently. Ask exactly one question: "Would you sit for this drive again knowing what you know now?"

Their pause before answering tells you more than the answer itself.

If the LinkedIn profiles don't match the JD, if Glassdoor contradicts the PPT, if the seniors hesitate — skip the drive. Another one is coming. A bad placement is worse than waiting for the next one.

4. Read the Bond Terms Before the Drive, Not After

Bond. Job bond.

This one is personal.

If you read the FinePrint post, you know the story — a friend nearly signed a 3-year service agreement with a ₹2,00,000 penalty clause buried in clause 3 of his offer letter. He had no idea it was there. First real offer. He was excited. He almost signed it without reading past page one.

That's why @yug_vasava and I built FinePrint for the Gemma 4 Dev Challenge — an AI contract analyzer, powered by Gemma 4, that reads offer letters, finds every buried clause, and tells you exactly what's dangerous and what to push back on. My first DEV Challenge entry. My first post on this platform. Built to catch someone else's near-miss — I just didn't know yet it'd end up catching mine too.

FinePrint — An AI Pocket Lawyer That Decodes Predatory Contracts Using Gemma 4

Gemma 4 Challenge: Build With Gemma 4 Submission

Dhruv Jani

Dhruv Jani

Dhruv Jani

Follow

May 24

FinePrint — An AI Pocket Lawyer That Decodes Predatory Contracts Using Gemma 4

#devchallenge #gemmachallenge #gemma #ai

10 reactions

Add Comment

6 min read

And yes — I ran my own Simform offer letter through it too.

But here's the part most students get wrong: they read the bond terms after they've been selected. By then, at most colleges, it's too late to walk away.

The fix is simple. Before the drive, ask your placement cell or the company's HR directly: "Can you share the service agreement and bond terms before the selection process begins?" Most companies share them in JD itself and it's not an unreasonable ask. If a company refuses to share terms before you commit? That tells you everything you need to know about what's in those terms.

Why I Sat for Simform (And Not Everywhere Else)

I didn't spray-and-pray. After the internship, I made a rule: only sit for drives that pass the filter. That meant skipping companies where the package looked great but the JD was vague. Where the PPT felt like a sales pitch instead of an actual information session. Where seniors told me the work on the ground didn't match the title on the poster.

Some of those companies offered more money than Simform. I skipped them anyway. Because after what I'd been through, I knew the package isn't the product — the work environment is.

Here's what Simform looked like when I ran it through the framework:

Glassdoor — Fresher reviews were consistent. Not glowing five-stars across the board — no real company is. But the patterns described actual engineering work. Not relabeled support tickets. Not data tagging. Actual development.

Seniors — The ones who'd joined recently described real projects, real mentorship, actual team structures. Nobody hesitated when I asked if they'd sit for the drive again.

The PPT — I've sat through pre-placement talks where the HR spends 40 minutes saying nothing useful. Simform's presentation answered every question I cared about before I had to ask. Nobody in the room had a single doubt afterward. That almost never happens.

The interviewers themselves — This is the part that stuck with me. The HR told me she'd been with Simform for 6 years — and this was her 4th firm overall. She didn't just work there. She chose to stay. The developer who ran my technical round had been there for 10 years. Ten years. In this industry. That is not an accident. That's a verdict.

The process — Placement portal with round-by-round updates. Clear timelines. Offer letter delivered through a proper system — not a WhatsApp forward at 11 PM with "congrats bro" as the subject line.

None of this is a guarantee. I haven't started yet — I'm joining as a Trainee Engineer and I'll form my own opinions once I'm on the inside. But the difference between this and the internship? This time, I checked. This time, I knew what I was walking into before I walked in.

The Part I Didn't Plan

FinePrint started because a friend almost signed a predatory contract. It became my first DEV Challenge entry. My first post on this platform. Months later, I ran my own offer letter through it — the one from the company I actually chose to join. And now I'm writing about the decision framework behind that choice, in Issue #4 of the series that FinePrint kicked off.

Every issue of this series loops back to something I built, broke, or learned the hard way. This one loops back to where the whole thing started.

If you're in final year right now, placement season is either approaching or already running. And the pressure to just get placed — anywhere, at any company, just get it done — is suffocating. I know. I felt it too.

But "placed" doesn't mean "safe." A bad first job can burn you out before your career even starts. The 20 minutes you spend checking Glassdoor, reading the bond terms, and asking one honest senior one honest question before the drive — that's the highest-ROI twenty minutes of your entire semester.

Screen before you apply. Not after you're selected.

Read between the lines — before you sign on one.

To the freshers: What's the sketchiest company that showed up at your campus this season? What red flags did you catch — or miss?

To the working devs: What do you wish someone had told you before you accepted your first offer?

Drop your stories. 👇

🎓 Follow for the next drop — nobody hands you this playbook in college, so I'm writing it as I go.

Dhruv JaniFollow

Upcoming Trainee Engineer @ Simform 🚀 Building, experimenting, and writing my way through tech. AI • Web • Open Source • Challenges If I find something interesting, I'll probably write about it. 😄