#Junior passing barely any screens

1 messages · Page 1 of 1 (latest)

tardy barn
#

cfaang

stiff remnant
#

Are you applying early? that's been the biggest factor in callback rates this cycle

Besides that, I see 3 major issues with your resume in terms of content:

  1. Poor digestability. I'm having a really hard time understanding what you did in your various internships/projects. You should aim to communicate this a lot more clearly even if it means going over 1 line per bullet

  2. Lacking demonstrable impact. I don't understand what your work was for or what outcomes were actually resultant of this. It feels like you're emphasizing more keywords and implementation details than actual impact (and you have a lot of weird/BS points too e.g., "Led code reviews" or "Designed/developed algorithms to...")

  3. No differentiation. What sets you apart from other similar candidates? You have a lot of generic points conveying tech implementation so far but I don't see any real distinguishable characteristics on your end. This is especially true when I look at your first startup and your projects. Your first startup in particular reads more like a project and I have a really hard time trusting your credibility here from it

Other nits:

  • missing roles in leadership
  • coursework is unnecessary with experience
  • ordering of skills is weird relative to your resume (why is nodejs in languages, why are c/c++/java before ts/js?)
  • you should really aim to leverage your experience with capital one - if you can't come up with something good for your first startup then I lowkey feel like you might get better results dropping it down to a project ngl. More experience means higher expectations it looks like