#Junior not having any luck :(

1 messages · Page 1 of 1 (latest)

median crest
#

I'd love some suggestions on what to add/change on my resume. I'm going for SWE internships, but not really having much luck. Would greatly appreciate any advice or suggestions :D

image.png
neon notch
#

honestly looks good. im surprised you're not finding much luck. the only thing i might change is adding a brief description to each project/experience. as cool as the detailed accomplishments are i dont actually know what each of the projects do. other than that maybe bold some key words so its easier to skim

opal cedar
#

I would recommend removing Data Science and Organization of Programming Languages from your Relevant Coursework section. I am not familiar with Discrete Structure - perhaps Discrete Math would be more relevant here.

VS Code should be a given developer tool (you can omit this).

Projects look great. For dates, I suggest 3 letter acronyms (so use Sep. over Sept.)

vapid kayak
#

your projects look rlly cool

vestal eagle
tight crypt
#

Biggest advice is to be applying early. That's been the biggest factor in callbacks this cycle.

Immediately tho, I don't see a lot of compelling experience beyond some of your projects. There's been a massive influx of new entrepreneur/startup student devs so a lot of people view it with more scrutiny. You also don't have any outside experience in extracurriculars, which hurts you more in university pipelines unless you have compelling experience otherwise (projects are only supplementary).

Firstly, as a founding engineer, you should be responsible for your baseline metrics. Having relative metrics ("increasing user engagement by 300%", "boot user collaboration by 70%") immediately come off as a red flag if you don't have associated baselines and major initiatives with it (and with a startup, you should be doing a lot more than "customizable user profiles" in the 2 years you worked there - it's something you can hack together in a day or two).

Second, you waste a lot of space by not talking about the business or its success metrics. You already say you're a founding engineer - why do you need to restate that you're a "key member"? Tell me what you built, how you launched, how much success you can measure (users, revenue, funding). What exactly did you do?

Third, if you feel that your startup was not strong enough to have compelling points to talk on, or that you don't feel like there was much you did, I would avoid saying you're a founding engineer altogether to avoid the negative bias and risk associated with it.