HuaRenCa
Back to Forum
Community

Got a job a month after being laid off, but it's really tough for new grads right now

Craig
Craig

2 weeks ago

My industry has been in a slump lately. I went on a trip in August, and on my first day back in September, my entire team got laid off. I was even checking emails and replying on Slack during my vacation—worked like a dog and still got axed anyway. If I'd known, I would've just slacked off; it would've made no difference either way.

On day one after being laid off, I sent out a dozen applications; over three weeks, forty or fifty. None of that AI mass-apply stuff—I tweaked every resume myself, and even had Claude and GPT grill each other about the companies. Found a new job in just over a month, used the severance for a vacation—tremendous deal, believe me.

But I interviewed at a dozen or so places, and only one had a coding test; the rest were all architecture discussions. Where would a new grad get business knowledge? Can't out-code AI, and haven't seen much architecture either—this setup is really very unfair. Small company teams are all people with five-plus years of experience; what's a new grad supposed to do in there, clap for the seniors?

I also bumped my previous job title up two levels—called screwing in bolts "building rockets"—and it actually worked better. Being too honest on your resume gets you ignored; exaggerate a bit and people believe you. Is this job market hiring people or hiring storytellers?

Fools who know nothing will still say new grads just need to grind more LeetCode. Do you forum folks think new grads are truly screwed, or is it just that the companies I interviewed at suck?

3
349

Comments (3)

Your avatar
Sign in to comment
霍城薰衣草
霍城薰衣草2 weeks ago

It's true that interviews that focus entirely on architecture are tough for new grads, but bumping your level up by two is a big risk—if it comes out in a background check or during probation, you'll be in trouble. Next time, it'd be better to jot down the architecture questions from your interviews and turn them into your own project case studies.

爱就一个字
爱就一个字2 weeks ago

Going from being laid off to landing a new job in just one month—that speed has already saved quite a bit of the cost of being out of work.

茄熊
茄熊2 weeks ago

Out of a dozen or so interviews, only one involved actual coding—that ratio says a lot. Are the companies you're interviewing with all on the small side, eager for someone who can jump straight into leading projects? If you applied to more mid-to-large companies with formal new-grad training programs, the interview structure would probably look completely different. Also, the fact that you could inflate your resume to "rocket scientist" levels and still pass the screen actually shows the people screening resumes can't tell the difference—which explains why the architecture discussion in the interview went the way it did.