#No process, really need some help
1 messages · Page 1 of 1 (latest)
ok off rip i'd say maybe focus on 1-2 projects and expand a bit more? network file server seems rlly interesting
ok 1st internship, bp1 'boosting user satisfaction' seems like kinda a weird metric? might just be me but i feel like the cutting response time is the more impactful/relevant metric anyways so maybe just keep that?
bp2 kinda same with the 'improving overall chatbot performance' part seems kinda vague, i'd say either elaborate on how u improved performance or just omit that part
ahh yeah then its up to u, prob worth cutting down on projects either way then
hmm i feel like metrics are best when they aren't vague and there's a clear correlation between what u did -> metric
so for like the 2 points i brought up, i think the 'cutting repsonse times by x' and 'enhancing response accuracy' are valid but maybe not the stuff after for both points
bp1 maybe remove use of sophisticated, seems like unnecessary waffle
bp2 i'd say convert 20 to 8 minutes eto a percentage of time reduced and for boosted engineer productivity this seems kinda vague? are u referring to like saving manual work done by engineers? if so maybe mention time/week or something like that instead of 30%
i think u kinda get the gist tho, just nitpicks on the bulletpoints but overall structure and exp seems solid ngl
wtf
pretty much yeah, 1 quality metric > buncha mid ones
u need sponsor right, thats honestly prob the biggest factor
but yeah very early dont get discouraged
lowkey maybe remove the points ab testing aswell w pytest, feel like it doesn't add much at least imo
jesus christ
alright hot take
id remove remove projects entirely
and space out your work exp points into single lines
that individually have way more impact
you're at a point in your career where i dont think anyone really cares about those projects a lot more than 5 other internships
okay this might also be a hot take
but since most roles are fullstack, a majority of roles (if not required), like to see some amount of javascript / typescript experience
because thats pretty transferrable
for bolding: it might be more imapctful to bold metrics/quant outcomes over technologies
but yeah as others have said, this is a sick resume, just needs to be tweaked a bit to make the recruiters want to hire u more
gl
i meant try to condense work exp points into one liners (each bullet point fits into one line)
it makes it much easier to read it
would mean you might end up having an extra bullet point in some cases
its purely a style choice, but i've seen it makes it easier to read the resume 10 fold
yeah that could work too
i'll dm u an example
but yeah shorter, while keeping all the what/why/how intact, is really powerful