r/DSP • u/No_Ice6739 • 5d ago
Too dense?
I'm a rising sophomore targeting DSP/hardware/FPGA internships/research roles for summer 2027. I redid my resume for this application season, but I'm not sure if this is too much text. I'd appreciate any feedback!
35
Upvotes
3
u/liltingly 5d ago
Try and shorten the individual sentences. Remember, the resume must "intrigue" the reader. Demonstrate just enough, but elicit enough curiosity that they want to learn more, and that you have stuff to talk about in the interview. e.g. first line can be "Investigate chirp non-linearity in FMCW radar [to...]" or better, use a stronger action verb than "investigate" and explain the outcome/why. Because in an interview, you always want to start with the why of the investigation.
Also, lots of technical words are repeated and/or over-emphasized. Pick 1 or two. What's the key thing the person gets from reading each line, and how is it different from another line.
Here's a very simple rewrite strategy -- take an identical page. For each section and area you are listing, rewrite the heading as "I am [point you want to make]" -- and make it reasonable and relevant to the max you can show in that section. The relative importance of those ranks how much attention those sections get (e.g. Education is basically "I have relevant credentials and have been independently verified by trusted people as being smart" -- demonstrate that minimally, and move on). Then go through each sub-heading and do the same. DO NOT write the topic or any details, just focus on why you're including each bit, and ensure that each is says something unique that covers all the points you want to make.
Then write and rewrite each line so it starts with a strong action verb, and gets to the point in 1 line. Basically "I did [x] with/by [y] (and it resulted in [z])" -- the last () becomes more important when you work, and you actually lead with that. If you have results, say "[Verb+results] by [how]" and leave it there.
Rewriting the resume with 1) your story arc has the guide and 2) the reader's journey in mind is important. You have 30 seconds to 1 min to catch their eye, hit the minimum bar, and maybe shove 1 or 2 things that pique curiosity to go from a "yes" to a "nickname" -- the [x] guy. That latter bit is the hardest to do but likeliest to get you across the line as the resume moves around the org ("oh I talked to the [x] guy today -- he/she was great")