#T_T PLS HELP junior 150+ apps 0 procs

1 messages · Page 1 of 1 (latest)

fleet sleet
#

Looking for 2026 SWE internships

specifically C++ dev

for context of my strategy thus far:
only applying for roles with C++ in the job description
also not applying to anything in defense👎👎

#

T_T junior 130+ apps 0 procs for swe internships plz roast :3

upbeat walrus
#

Damn esri nice

slender grove
#

esri orz

fleet sleet
#

@wooden osprey hallloooo fellow drainer...
sorry but would love your eyes on this ><

fleet sleet
#

T_T PLS HELP junior 150+ apps 0 procs

wooden osprey
fleet sleet
frosty forge
#

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:

  1. “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.

  2. “Improved efficiency of ad-hoc testing…”. Yeah how much did it improved? did it reduce test cycles, debugging time, or manual steps?

  3. “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*."

  4. 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?

  5. 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.
fleet sleet
fleet sleet
fleet sleet
frosty forge
frosty forge
#

its just a bunch of meaningless buzzword

fleet sleet
fleet sleet
#

i can see how they’re buzzwords perhaps but i don’t feel that they’re meaningless

frosty forge
fleet sleet
#

I’ll remove it! just surprised it comes off as meaningless

frosty forge
#

well i didnt know the team used that term directly haha

#

i thought it was just buzzwords for your resume

fleet sleet
#

thanks for the thorough advice will implement!!

fleet sleet
scarlet plaza
#

C++ merchant orz

fleet sleet
#

the only language ever

wooden osprey
#

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

fleet sleet
#

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

wooden osprey
#

ok imma dm u