#T_T PLS HELP junior 150+ apps 0 procs
1 messages · Page 1 of 1 (latest)
Damn esri nice
esri orz
@wooden osprey hallloooo fellow drainer...
sorry but would love your eyes on this ><
T_T PLS HELP junior 150+ apps 0 procs
pretty solid do some research at ur uni to get more to put on
thanku goatt ok will work on that zzzzz
General Advice:
- Use STAR/CAR/XYZ method when writing your bullet points. Most of your bullet points are not.
- Focus on impact rather than tasks, 99% of your bullet points are the tasks you did, not the impact of the task.
- Use strong action verb at the start of your bullet points
Here are examples of your weak bullet points:
-
“Collaborated with team to rearchitect high-performant C++ core providing geospatial and mapping functionality…”. Too long and buzzwordy. “High-performant” and “rearchitect” are overused. Instead you can write it like : "Rebuilt core geospatial engine in modern C++ to improve SDK performance and developer experience across multiple platforms.”, you can even mention the metrics of the improvement by 5%, etc.
-
“Improved efficiency of ad-hoc testing…”. Yeah how much did it improved? did it reduce test cycles, debugging time, or manual steps?
-
“Accessed coordinates, geodata…”. reads like a class assignment, instead you can write it like this : "Optimized geospatial route planning for 20,000+ streets, cutting average query time by 50% using custom hashmaps and A*."
-
Mahjong Detector. In this project, why not tell the results of your project, whats the detection accuracy of your project? why just tell the implementation?
-
Empathetic Chatbot. Again in this project, what did u achieve? whats the accuracy, f1, recall, precision? model type?
In Summary :
- Remove the weak bullet points, you dont need to tell everything you did, but enough so that the recruiter is interested, the rest can be talked in the interview. Thats why you need metrics to interest the reader/recruiter. Right now, when im reading your resume, it sounds like a lab assignment.
thank you this is great feedback! I feel that my bullet points generally follow the Accomplished X by doing Y using Z technologies
but I can see how some of my bullets lead with a task rather than the impact especially in my projects
When you say rearchitect and high-performant are overused, is this a general statement or in reference to my resume?
Just to clarify, do you recommend removing the weaker bullet points or rewriting them in accordance with your other suggestions?
rewrite them, and if you cant, you can just remove them
i meant it as like in general
its just a bunch of meaningless buzzword
gotcha sounds good!
really? i mean those were the terms used on the team because the main effort was a rearchitecture of their “high-performance C++ core” like that was the description on their github repo
i can see how they’re buzzwords perhaps but i don’t feel that they’re meaningless
i mean if you want to keep it that's okay
I’ll remove it! just surprised it comes off as meaningless
well i didnt know the team used that term directly haha
i thought it was just buzzwords for your resume
thanks for the thorough advice will implement!!
ahh gotcha
C++ merchant orz
the only language ever
show ur most updated version
@fleet sleet
sorry when i looked at ur ping i probably wasnt that available so i gave a mid response
also fwiw i disagree with some fo the stuff said above so just wanna see ur current version
specifically idt STAR / all these other frameworks are that valuable
i dont use any of those and ime its just brittle and redundant across multiple lines
wait nw sorry for pinging i appreciate your feedback
this is it so far, idk the new stats r definitely made up but tried following the advice of showing impact in projects and "removing the weak bullet points"
definitely not finished though something feels off
ur old first line mogs ur current hm
ok imma dm u