#I have never passed a resume screen, but 2+ YOE from 4 internships. What am I doing wrong.

1 messages · Page 1 of 1 (latest)

still zodiac
#

LGTM

gritty crescent
#

Yea, your resume is actually quite solid overall. You're hitting all the major points I'd look for in a resume (organizing bullets by impact, business metrics, details with tech, even soft skills with documentation and customer-oriented collaboration).

You may be getting screened out due to your graduation date, but you'll probably find a lot more success in the upcoming application cycles. Make sure to network on LinkedIn, reach out to recruiters, etc. to get yourself a leg up.

Most of the feedback is minor:

General

  • I'm impartial towards the tech being listed next to the role (since it's mostly small roles and internships, it works out), but you should list out the most relevant tech if possible. You're excluding React and Express from role 2, TS from role 3, and React/D3, Express and WebSockets from role 4. I can see it coming off as odd, and it might put into question your actual work/contribution with the tech you describe in the bullets
  • Bolding/emphasis is inconsistent across the roles, which you should fix. The typical approach is either to bold tech (most common) or metrics (less common) - in your case, either works. Another approach that you could consider is bolding the relevant parts related to the role you're applying to (though this is least common, it'll help recruiters eyeball what value you bring and whether you fit in the company need)
  • Metrics formatting for numbers is inconsistent. I don't recommend filling up space for the sake of filling it - each word should be there for a reason. It's fine if it's different between money and other countables, but if it's different between the same type of countable (users), it raises eyebrows
gritty crescent
#

Role 1

  • Try to be more straightforward e.g., "Delievered and owned" -> "Launched", "Led creation" -> "Created"
  • Consider being more specific about business context (what game?)
  • Try to avoid subjective measures ("robust", "solely"), especially in place of an action verb (role 2 bullet 1) - "Configured robust rate limiting" is fine if you leave it as is, but it can be better. "Architected a multi-factor authentication (MFA) system to..." if you really need to fill up that space
  • WS for audio streaming? Not WebRTC? Can you explain/defend this? I would be digging at it if I were interviewing you, and test your understanding of WebSockets

Role 2

  • Second bullet can be reworded to be clearer, and not just seem like buzzword vomit. If this is a microservice to handle MFA, you don't need to tell me you developed REST APIs - in fact, if this is the case, I would also be digging into your understanding of microservices architecture, because if this is a project under your ownership, you should be able to explain the design decision behind making this REST-based and how it fits in with the rest of your system architecture
  • A user interface to incorporate JWT auth using Redux? Why is the JWT not in an HTTP-only cookie? If sessions are JWT based, that also introduces security issues related to MFA - you should be able to explain this
    • What I think you're trying to say is "Built an MFA user interface to incorporate incorporating JWT-based auth..."
  • Don't quantify the number of tests - quality and coverage matter far more. What kinds of tests? There are a couple other buzzwords you can supplant here (e.g., behavior-driven development) that you can use without bloating your point with fluff

Role 3

  • Automate customer docs? Saving 15+ hours monthly? Can you clarify?
  • 5+ Angular screens? 10+ production issues? Why are the numbers not exact? Why screens and not pages?
  • Imo the last bullet could be rephrased a lot better -- 10 bugfixes isn't a lot
#

Role 4

  • This is a startup right? Consider using the term MVP, and instead of "Spearheaded", use something like "Launched"
  • Nit: Switch D3 and Websockets to match the order of the feature description "real-time" <=> WS, "data viz" <=> D3
  • I think bullets 1 and 2 can be combined to give more context to the product itself. Something like

Launched a web-based healthcare management system with real-time data visualizations using React, WebSockets, and D3.js to improve medical decision making, securing $500K+ in investment

  • Also needs more specifics on the problem space/value proposition
  • Third bullet can be reworded to not keep "RESTful API" - too much emphasis on the API itself and not the structure. Also no Node?
  • What does "improved analytics capabilities" mean, and how does your metric relate?

Community

  • Don't say backend developer here
  • Give context to the problem/product before going into technical detail - especially if you label it under community, I want to see what you're doing for social good, and I want to see more teamwork/passion outside of tech (which you have enough of)
  • Is Apollo migration that impressive? The scope and impact is not clear (it conveys the impression of just npm upgrading the package). You have far more impressive feats elsewhere, you should use this space to address non-technical points as well where possible
fleet radish
#

hey man, really appreciate your help and the time you invested into this