Do not use 2 page resumes as entry level
#CS Junior 0 interviews, looking for new GRAD position, any help is appreciated
obsidian needle
obsidian needle
The rest seems fine
sterile lava
IG u can prob work on making it more "presentable", concise, and easy to follow
Like by presentable I mean bolding stuff so its a bit easier on the eyes
by concise u can prob cut out some fluff words or add context so they are not "fluff" anymore:
"scalable" query processing for 40000 "concurrent" users
like scalable query processing sounds like fluff since its hard for me to connect the fact that the "multithreaded" earlier on in the bullet is what u are prob referring to. So u can prob drop the "scalable" and "concurrent" sort of words here.
That's cuz the multithreaded authentication bullet has the same vibe (ohh we dealt w the challenges of parallelizing in some aspect...) so u don't need to really "repeat" ideas in the resume (aka what u did in the first bullet of the first experience by referencing mutithreading)
And by easy to follow i mean presenting ideas in a "logical" manner, like instead of saying u implemented an "allocator and RAII factoring" to cut down on allocations, you can say u implemented an allocator and integrated it into class-level RAII (or whatever), that makes it a bit more clear what u exactly did and gives me a better understanding of the "reduction in allocations metric" that follows
(how I got here: i dont see how this RAII pattern cuts down on the # of allocations, but IG the arena allocator does, which makes it a bit confusing to read since I cant immediately get the vibe of how they are related)
fading plume
this is a great resume