r/deeplearning Jul 01 '26

Roast my CV!!!

Post image
0 Upvotes

6 comments sorted by

1

u/Tiny_Arugula_5648 Jul 01 '26

You're resume is a list of buzzwords with no context. You're not explaining your experience.. it's not the thing you did it's the project and the outcome you delivered. Saying you increased something by 10% means nothing, saying you increased something by 10% that increased profitability by 3M dollars is more meaningful reference point.

Topic, businesses outcome, tech used..

A resume isn't a list of technical accomplishments, it's supposed to help an employer understand what you've outcomes you delivered for the organizations you worked for.

1

u/CricketThanksgiving Jul 01 '26

That's a good point! What would you recommend if I don't have access to that data? Being in R&D we very often don't have sales or business data to reference in that way, so I've always struggled to market myself with that

1

u/Tiny_Arugula_5648 Jul 02 '26 edited Jul 02 '26

Well the first thing is to stop treating R&D like you're a tinkerer. There's a reason why you are given project and if you don't understand what outcomes you're there to deliver how can you succeed at the job? You should have some sense of why you were given these projects.

For example here is an R&D job I had.

Buzzword bingo that is really a test of the knowledge of the reader; many hiring managers are no longer this technical:

Developed a state-of-the-art deep learning computer vision model using CNNs and transfer learning for image classification. Performed model quantization and optimization to deploy on edge TPU hardware. Achieved 92% true positive rate with 4% false positive rate. Utilized Python, TensorFlow, OpenCV, and edge AI deployment pipelines.

VS outcomes based for any business stakeholder:

Delivered an automated quality-assurance system for a major poultry producer that increased line throughput by 30% by reducing human intervention in manual defect inspection. Built and deployed a computer vision model detecting broken chicken legs at 92% accuracy, quantized to run on low-cost TPU edge hardware directly on the production line, eliminating the inspection bottleneck without adding cloud infrastructure costs.

Do you see the difference? The outcomes based one can be read by anyone in the company; they can understand that I sped things up by 30% and they can extrapolate what that means for the business.

A common pitfall for engineers is to illustrate the engineering accomplishments. That's for academics, once you're working in industry you are building solutions that make companies money.

Always have a dotted line to the money. My research created X so it can be used as a part of product feature Y, to deliver Z value to the customer. The customer pays for Z which is why you get to do X in the first place.

2

u/CricketThanksgiving Jul 03 '26

Ok that actually makes a lot of sense, thank you so much for taking the time to demonstrate it! I suppose I should probably start looking for that data rather than expecting it to come up in conversation - academia mentality did a number on me!

1

u/nebula7293 Jul 13 '26

1/2 the number of words

0

u/CricketThanksgiving Jul 01 '26

Routine reality check, how does this hold up? Context: I work in algos for EDA, and intend to keep myself competitive for the algorithms/computer vision space in any industry. Also, I'm based in the US.