#Soon to be grad (spring 2024) looking for resume saviors (be harsh please!)

64 messages · Page 1 of 1 (latest)

azure ridge
#

Just be ready to answer questions about those numbers 😉

#

I think everything is fine but as a hiring manager I would dig deeply into those numbers. I know a lot of resume builders suggest throwing in the effects of your work, but having concrete numbers like that from a Jr/Intern is impressive (which makes it questionable).

#

NDA generally don't get violated via interviews. I wouldn't even mention it. Generally NDA are brought up by people who are faking their resume to avoid ansewring complicated questions. NDA cover what you worked on and technologies used (sometimes), and definitely algorithms and business practices. During interviews you discuss your skills you gained/used and avoid going deeply into business details.

storm patio
#

Here we go

#

So let's take this from top to bottom

#

In the skills section:

Do you primarily consider yourself a C developer?

#

So as a general rule, I'd list my languages from left to right in the order that you want to be considered for them.

#

This may seem minor, but if I see someone start by listing C, my expectation is that this guy considers C his first language

#

As far as your jobs...

#

Just to recap, you worked full-time as a developer from 2017 to 2019, then you went to school for mechanical engineering?

#

I would also spell out "TypeScript"

#

But that's maybe something to get a 2nd opinion on

#

So wr/t your jobs section. It isn't working for me but I'm trying to put into words why not.

#

My guess, would be that you got some advice somewhere that you should start bullet points by talking about impact first

#

The problem is twofold

#

First, most of your bullets aren't entirely clear as to what the project was. You kind of go <financial impact> with <technologies> but it's unclear to me what you built or what your personal role was in building it.

#

Second, there's a bit of a credulity issue. You're a new grad aiming for new grad roles, and some of the huge financial claims in here have a real "damn, dude built the whole company himself" energy.

#

These may in fact be true.

#

You may have solo-dev'd a project that resulted in 2 million dollars of realized cost savings

#

For new grads where it is not expected that you have changed the world yet I think a format of

<role> in <project> using <technologies> resulted in <impact>

is a little bit better of a format

#

Were these solo projects you were assigned? Or were these projects where you were part of a team?

#

The number itself isn't so much the problem.

#

It's that if I look at your job history from top to bottom the story I get is that

  1. This is an intern that left literally millions of dollars of value in the wake of everything he touched
  2. It is totally unclear to me how he did any of this
  3. This guy didn't get a return offer for either of these literally unbelievable resume stints
#

Because they're interviewing you

#

So okay, this is a great story

#

And the moral of it is that you save money

#

But you need to open with the context here I think

#

Well, most of then

#

But specifically top job top bullet

#
  1. what was your role in this project?

Sounds like you were paired with a Chemical engineer?

tacit sphinx
#

So that's an improvement to a process of ~2/3% right?

I've had a similar concern where the effects of my work seemed outsized on my resume because of the total amount of revenue the business actually does. I forewent the $ value because it does make readers question credulity, and only provide that in the context of an interview where I can explain

storm patio
#

So my first question in interviewing basically anyone who is talking about a really impressive successful project is

"What specifically was your role?"

#

So I'd start the bullet with

"Lead developer for software which <whatever your software does> using <technologies> resulting in <impact>

#

Now question 2

#

What the fuck does your software do?

#

I've specifically worked in O&G and have no idea what you mean by blend trading

#

I assume it's something to do with formulations, but you should assume software interviewers will know less

#

You're not downplaying anything

#

You're going from explaining a good project poorly to explaining it well

#

Because, also, HMs dont necessarily care about business impact they care about what you did.

#

Unless the way you impacted business is directly translatable to their needs.

#

I.e. if you're in marketing and you designed a campaign that made XX million sales and I'm hiring for a marketing campaign manager.

That's a situation where business value may be apples to apples

tacit sphinx
#

I agree with ruckus

#

It is more clear the impact you had when it's in % than in $

#

If it seems like it's less impressive, that's because it is.

storm patio
#

That sounds like a great project

#

It sounds

#

Like a "purchasing tool"

#

Which "dynamically optimizes reagent sourcing"

tacit sphinx
#

Maybe others disagree but I think it might be worthwhile to only really focus on one project

#

As in, give multiple bullets to this project to explain more what you did and why, like you did here

storm patio
#

To me the issue isnt 1.8MM vs 3%

#

It's that as a hypothetical hiring manager I'm unclear what the project was and what your contribution was.

tacit sphinx
#

You could just post the bullets here

storm patio
#

Honestly you may be better off having a few resume variants

#

Which like, I know this sucks

#

But if it makes you feel any better, this is probably more work than having an actual job

tacit sphinx
#

I mean, you have a ton of theoretical room

#

The "Software Developer" position isn't what most people would consider "Experience"

#

I would personally

#

It's not intuitive

#

Yes, especially since you were in them so long.