Four Offers, One Playbook: A Meta Engineer's Grad-School Job Hunt

Adwait Sathe graduated from Northeastern University in 2021 with four job offers in hand — from McKinsey, Walmart, Amazon and Meta. He chose Meta, where he now works as a 32-year-old senior data privacy engineer at Meta Superintelligence Labs after five years at the company, first at Messenger and the last three in data privacy engineering.

For recruiters and talent leaders, his account is a rare first-person record of how a candidate actually navigated a competitive entry-level search. Sathe moved to the US from India in 2019 to pursue a master's degree in information systems. He began his job search roughly a year and a half before graduation, scanning job postings in his second semester to map what the industry would demand a year later.

"I was very clear from the start: I want to work in data engineering privacy," Sathe said. He took classes in the field and built a portfolio through internships and side projects before applying anywhere.

What did his outreach tactic look like?

Sathe's first strategy was disciplined cold messaging on LinkedIn. He targeted a specific slice of the workforce: engineers and senior engineers at Big Tech firms working in data engineering, active on the platform, and deliberately not managers. No vice presidents. No directors.

"I was looking for mentorship," he said. "I approached them to understand the industry's requirements, so that when I applied, my application would stand out among the masses."

His message template was deliberately plain: "Hey, I am Adwait, I'm studying this, and I want to pursue my career in this. I have this tech stack and résumé; what should I improve?"

The volume was high at first. Many recipients never replied. Once he had secured three or four solid mentors, he eased off. One of those connections delivered a correction that changed his results: his résumé made him look inexperienced. Sathe had three years of work experience in India after his bachelor's degree, but he had front-loaded his education over that experience, making the document read like a new-graduate résumé. Interviews increased once he fixed the ordering.

He now pays the advice forward, replying to nearly every LinkedIn message he receives asking for career guidance — a data point worth noting for employers wondering how cold candidate outreach actually flows through their own engineering teams.

How did he structure the applications themselves?

Sathe split his search into two buckets. The first held the companies he genuinely wanted to join. He visited their career sites a couple of times each week, watching for new-grad postings, which typically open well before graduation season, and applied early.

The second bucket was pure volume, using one generic résumé across as many postings as possible. Tailored applications were reserved for the shortlist.

The pivot point came with his first offer, a data engineering role at Walmart. He stopped applying in volume immediately. From then on, he applied only to roles he truly wanted that could match or exceed the Walmart package. That sequence — volume first, selectivity once leverage arrived — produced the four offers.

What would he change in an AI-era search?

Asked how he would apply for the same roles today, Sathe flagged two additions. First, portfolio depth: "A working product, which is live and has real users, is way better than bringing a prototype into the interview," he said, describing the weak version as telling an interviewer a project "worked when I built it, but it's not working now."

Second, AI fluency — not just tool familiarity, but understanding how AI works in the background and exercising judgment about which tool fits which task.

The fundamentals, in his view, remain untouched. Strong coding and well-structured code still matter, and while AI can handle implementation, system design and architecture remain distinctively human work — a signal hiring teams can expect candidates to increasingly bring live, user-tested projects as proof.