please cook my resume

[olive geyser]

Your first experience is hard to follow, make it more concise. Also if you want to put ML research you should prob include what ur model is doing .

[sudden ravine]

my ML research points were more detailed but i felt like it was way too technical and would just appear as a word salad to recruiters esp bc im mostly just applying to SWE roles

[olive geyser]

Yea I have the same issue on my resume so i know what u mean. I think it is still good to explain why ur work is novel especially if its AI

[olive geyser]

looks good, but are you sure you cut internal tickets by 30% thats kind of ambitious. But if you did that rly impressive.

[sudden ravine]

oh the wording is pretty misleading im not referring to dev tickets (making actual code changes), im referring to tickets that have to do with changing config or resetting a user state for instance because a client requested it

what do you think i should call those instead bc now that you mention it "internal" tickets don't really mean anything lol

[sudden ravine]

this request would go to tech support or smth typically, not an engineering team but if it's complex enough then they would raise it to us

[olive geyser]

tbh i would make it sound more software forward. Like "developed application-level retries using (language used) to speed incoming ticket requests by 6% ( or some bs number)

cuz although you have a lot of tech related content in the first experience it doesnt sound super swe focused upon lightly skimming. I think you can reword them to adress this

[sudden ravine]

hmm yeah i get what you mean thanks

[olive geyser]

yer

[sudden ravine]

the backend was all in typescript as well though so i didnt want to keep repeating "typescript"

[olive geyser]

then add it on first point

also maybe slight nitpick but you keep using percentages, is it possible you have a count of them

ig for ur current setup it doesn't make sense

but perhaps you can change point to be like developed # endpoints in ts reducing ticked proc by %

[sudden ravine]

i also handwaved a lot of these metrics they are by no means rigorous or super accurate 😂

[olive geyser]

Yea tbh everyone does

[sudden ravine]

i had something like this before (it was just 4 CRUD endpoints) but i shifted away from it to more easily understood business-impact

[olive geyser]

even if embellishing you should move it to be more SWE focused. But yea ur right having understandable impact is more important

you can try to baance both

you can format it (swe coding) + (impact) or the reverse

[sudden ravine]

also how do you even combine language + library in a bullet point is it fine to say TypeScript (AWS Lambda) or AWS Lambda (TypeScript)

other ppl seem to just omit one

[olive geyser]

Since you did mostly typescript you can split them into two lines. Tbh the key words are just for a quick scan or ATS so i think it’s ok to have it only once

[sudden ravine]

also right now it is (impact) + (swe coding) though is it not? (swe coding) + (impact) would just put most of the metrics at the end (except when the swe coding itself has metrics, like # of endpoints as you said)

[olive geyser]

it is ur right

Developed Python FastAPI services enabling 22+ (clients) to ingest and visualize device signals in real time

Reduced data transmission pipeline latency, from 45 to 8 seconds over TCP enabling instant feedback that allowed (clients) to continue testing without interruption

Deployed services on AWS Elastic Beanstalk, integrating InfluxDB for signal data and RDS user metadata

this is how i have the points on my resume, i try to make it very clear and concise

idk if this will help much but its how i did it

[sudden ravine]

hmm yeah i see what you mean you do switch it up so it's more natural. maybe i should stop trying to force XYZ order

like in your first point it's "by doing Z, accomplished X (includes Y)"

[olive geyser]

ya thats a good way to think of it

[sudden ravine]

and then in your seocnd point you're only attaching the metric for the Z instead of X "By doing Z (includes metric Y), accomplished X"

so yeah youre reframing the focus in your points to be the code implementation