SWE #JobSearchTips #ResumeHelp #FAANG #TechCareer
Hey fellow techies! 👋 Have you ever experienced the frustration of applying to countless SWE positions, only to receive immediate auto rejections? 🤯 Let’s help out a fellow community member who’s facing this issue with 4 years of experience under their belt. Here’s a few things to consider:
-
Resume Review:
- Check for any formatting issues
- Highlight key achievements and skills
- Tailor it to each job application
- Use action verbs and quantify results
- FAANG Focus:
- Research the company culture and values
- Showcase relevant experience and projects
- Leverage referrals and networking opportunities
- Practice for technical interviews
As for the concern of constant auto rejections, have you tried reaching out to recruiters for feedback? It may shed light on areas for improvement. Keep refining your resume, honing your skills, and staying persistent! ✨ Good luck on your job search journey! 🚀
What’s your work authorization status? If you’re getting *immediate auto rejections* it’s most likely to be a visa issue.
Looks like lack of buzzwords
I don’t know your stack since I do Android
My experience points look like this:
Job at x company: senior Android developer
Projects:
– project A: app that does x developed in kotlin and java using jetpack compose, flows, live Data, fragments, retrofit, view binding, ConstrainLayout, linearlayout, glide, room, multithtrading, coroutines, graphql and mockito and mokk for unit testing
If you’re getting auto-rejected literally immediately, it’s obviously an ATS doing it, so I can only assume that you aren’t matching up to the job posting closely enough. Are you making sure that you’re tailoring your resume to the specific posting and the language it uses?
Also, this wouldn’t be the cause of immediate auto-rejects, but find a synonym for “built” and/or a different way of writing those bullets – 5 out of 8 start with the same verb as is.
I bet it’s the degree
Have you applied to any Data Engineering jobs?
Are you on linkedin?
If not, get on linkedin, set up profile and get active, check linkedin everyday, share likes on trendy tech posts, etc. That way you’ll surface more on recruiter search lists.
See how many recruiter spam you get.
The scope of your work and tech stack may be too limited and niche, you list protobuf but no json? You list typescript, but no javascript? You list java, but no spring, no springboot?
You’re likely being autofiltered by ATS scans, that can’t see relevant hits based on your listed tech stacks. It seems random mishmash of tech words throwin in, instead of solid progression of tech stack foundation build up.
!Remindme 1 day
I was going through your resume and it’s pretty good, then I got to the education portion. Sadly it’s probably the degree holding you back. ATS is probably seeing no CS degree and is tossing it.
Random resume feedback:
* “Built and helped designed” –> “Architected and built”. I don’t care if you helped. Everyone exaggerates, you can explain the nuance in person if anyone actually cares (they don’t)
* “50 millisecond 95-percentile” –> “50ms p95”
* Maybe just mention technologies used at each job once (inline with the role/company possible), no one cares which specific technology you used for each line item (unless you’re targeting some specific role that needs some kind of specialist on day 1
* Almost every bullet point is “Built thing” — reframe some of them to mention what you enabled or business impact it had where possible
* IMO remove the months from all the dates. HR will do a background check if anyone gives a shit anyways, for interviewers just let them eyeball roughly how many years you were at each place. Months just adds more noise and math required
* “Build and maintained microservice backend for facilitating real time payment processing” –> “Built real time payment payment processing microservice used in 180+ countries”. Not sure what the “switching” part even means
* “Built service to generate PDF reports” –> “Built PDF generation service”. Many of your points are “Built service to ____”. Building a service is fairly meaningless – it might as well say “Built an API”. You can call anything a service. Tell me *what* you built, and what impact it had. If you want to say it was encapsulated into a service, that can come later in the sentence
Just my 2 cents
Just to add on to what the other commenter said about ATS, we hear a lot about how tables prevent ATS from parsing your resume properly. This looks like a table format resume, I use a similar style that is a table. I would recommend doing away with the tables and see how that goes. I know I’ll be refactoring my resume next time I start job searching