Context: Searching for a new senior level software development job over a 9 week period in summer 2025.

  • Focused mostly on data engineering and backend roles that are in-person or hybrid in the SF Bay Area.
  • Leads from recruiters on LinkedIn were much more likely to lead to interviews+offers.
  • The winning offer came through my personal network.
  • I mostly used Hiring.cafe for prospecting. They’re a scraper with an interface I didn’t hate.
    • pixxelkick@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      4
      ·
      2 days ago

      Formatting is honestly a big part. Left align what matters.

      Too wordy, missing key details, too big, too small, etc

      Missing they key words the job posting covers. If the job posting talks about Node and angular and your resume doesn’t explicitly namedrop them, then it loses a tonne of points.

      Usually the majority of resumes that pass the sanity check then go to screening. You’d be surprised how many people just screw up basic stuff.

      Every single time I’ve had someone complain to me about job offers, I’ll grab a random job posting I find and ask em to send me the version of their resume + cover letter they would send to that specific posting.

      Quite often within a min or two I can find several reasons why their resume would’ve gotten bin’d