Feedback on res, tryna break into Big Tech as a Junior

[umbral tusk]

your res is pretty good

[proper siren]

Ive got like 0 processes atm 😭, preciate u looking at it tho lol

[orchid stratus]

cmi

[fossil rain]

feels a bit squished, maybe try rewording some bullets so they fill up just 1 line, inconsistent bolding too but its wtv

[proper siren]

most of them already r like relatively close to 1 line should be able to cut it down a bit to make it less clustered. ya bolding is bad would u say just bolding only the "tech stack" is the move?

[small bay]

Cut đown on bolding yea tech stack + metrics

[proper siren]

🫡

[fossil rain]

well personally i'm not rly sure, it was just i saw "billing and document workflows" bolded in the 2nd exp and it just doesn't seem that important

just thought it was a bit peculiar

[proper siren]

ya fair enough that section does look pretty weak especially Ill work on it and post the updated one here tmrw. preciate the help so far

[proper siren]

reworked the bullet points, mind giving it a look

[odd osprey]

theres 100% metrics you can use for the kafka bullet point in schwab

the immediate one is scale, how many msgs per minute

this bullet point has the impact but no metric

this is misinformed, python only got true multithreading in 2025. I mean technicaally there's a multithreading moduel but it wouldnt really do anything at all if your code calls were async aalready

[odd osprey]

same for the schwhab one. improved incident respsonse by how much

these are mostly nitpicks, the only one id say you actually should fix is the kafka bullet point not having a metric. kafka is a very high signal keyword so you shoudl aim to nail your only bullet point on it

[proper siren]

Developed a real-time Kafka data pipeline, achieving sub-200ms end-to-end latency and a peak throughput of 15,000 messages/sec during simulated load tests.

[proper siren]

ya makes sense, most of my testing was done through integration tests with Springboot should list those

Identified and resolved 3 performance bottlenecks pre-production by building a Prometheus + Grafana stack to analyze API latency under simulated load.

this is an idea for impact, but honestly it was mainly just a proactive scaling strategy, my load tests were relatively limited I didn't get a chance to do much 😅

[proper siren]

good catch it wasn't multithreaded just asynced ur right must've just added that cuz it sounded right 😂

[proper siren]

thanks though preciate it

[fossil rain]

idt metrics are necessary, but if you have metrics you can add just add them