Applying as a New Developer at 30 Is Giving Me a Reality Check
Everywhere I submit my resume, only younger people get picked, and the places that do reach out don't meet my conditions. Every time I write down my job-seeking preparation period on my resume, reality hits me and I turn off my computer. Just venting.
10 answers
Yeah, I also started in my mid-30s, and now I go regularly.
That's right lol, once you're over 30 you have to lower your standards.
Well, I'm not so sure about that. There are plenty of people around me who started as new hires at 30. Rather than the career gap being the problem, I'd say coding test or portfolio skills matter more.
I get the burnout. But instead of just venting, if you're from a bootcamp, organize a few solid projects and put GitHub links on your resume. There are definitely places that look at skill over age.
Do you have a source? Which job posting did you see the age restriction in?
I also started as a new hire at 32. I sent out 100 applications and heard back from fewer than 5 places. But once you're actually in, they don't care much about age. Don't give up.
Disagree. The junior job market itself is tough these days; it's not just about age. Even people in their 20s get filtered out at the resume screening stage.
You can do it! Hang in there.
It's not that I'm turning off the computer because of a sudden hollow feeling—it's more like the computer is turning itself off lol. Just kidding, hang in there.
Rather than writing it as a 'job-seeking preparation period,' wouldn't it be better to write it as a 'personal project period'? It seems like packaging matters more than age.