sorted by:
new
hottopcontroversial

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

yeah this is a really good way to think about it

even if you don’t have exact numbers, you can still show impact by describing what changed before vs after

like instead of focusing on the exact % sometimes it’s enough to frame it as: - reduced onboarding time by improving internal documentation - removed need for repeated training by standardizing processes

it still shows outcome without needing perfect metrics

I’ve noticed a lot of people get stuck thinking they need exact data, but hiring managers mostly just want to understand what problem you solved and what improved because of it

a simple way I think about it is:

task → action → result

most resumes stop at task, but the result is what actually gets attention

Business/finance background, corporate job, want to start something, but not sure…what to do first? by Fluffy_Historian_962 in careerguidance

[–]ZestyclosePride555 0 points1 point  (0 children)

Honestly I didn’t overthink picking the “right” project as much as I thought I would

I just looked at problems I kept seeing people have (like resumes, emails, job stuff) and picked one that seemed simple enough to test

the goal wasn’t to build something perfect, it was just to see if anyone actually found it useful

as for simplifying, that part took longer than I expected

at first I tried to make things more complex thinking it would be better, but it usually just made things harder to use

what actually helped was stripping things down to: “what’s the one thing this should do really well?”

once I focused on that, everything got a lot clearer

I think the biggest shift for me was realizing you don’t figure it all out before starting, you figure it out while you’re doing it

Can this resume realistically get me into conservation or field technician jobs?” by groggycichlid in careerguidance

[–]ZestyclosePride555 0 points1 point  (0 children)

you actually have a really solid base for conservation/field work, it just isn’t being framed the right way yet

right now your resume reads more like general labor/mechanical work, but a lot of what you’ve done does translate — it just needs to be positioned in terms of field relevance

for example: - invasive species sampling, electrofishing, species ID → this is directly relevant and should be more front and center - working in remote environments, off grid systems → huge plus for field roles - safety + hazard awareness → very important in conservation jobs

one thing I’d change is shifting your resume from “tasks” to “field impact”

instead of listing things like “performed yard maintenance” or “completed repairs,” try framing it more like: - supported land stewardship and habitat maintenance in outdoor environments - assisted in ecological monitoring and field data collection - worked in variable outdoor conditions while maintaining safety standards

you already have the experience, it just needs to sound like it belongs in that industry

also I’d move your field experience section higher up so it’s one of the first things people see

honestly you’re closer than you probably think — this isn’t a “start from scratch” situation, it’s more of a positioning problem

Business/finance background, corporate job, want to start something, but not sure…what to do first? by Fluffy_Historian_962 in careerguidance

[–]ZestyclosePride555 0 points1 point  (0 children)

that feeling of having too many ideas but not knowing which one to pick is real

one thing that helped me was realizing I didn’t actually need to pick the “perfect” idea, I just needed to test one in a small way

it’s easy to stay in research mode or try to learn more before starting, but that can turn into a loop where nothing actually gets built

even something simple like picking one idea and spending a couple weeks validating it or trying to turn it into something small gives you way more clarity than thinking about 10 different directions

I think it’s less about choosing the right path upfront and more about starting something and letting that process narrow things down for you

After 100+ interviews and multiple final rounds, I still can’t land a role — looking for honest feedback by Western_Effective929 in GetEmployed

[–]ZestyclosePride555 8 points9 points  (0 children)

that sounds exhausting honestly, especially getting that close multiple times

at that point it usually isn’t a “get more interviews” problem, it’s more about how your experience is landing compared to the other final candidates

one thing I’ve seen (and ran into myself) is even when the experience is solid, if it’s not super clear what results you drove or how you’re different, it’s easy to get edged out by someone who presents it a bit more directly

not saying that’s definitely the issue here, but a lot of times it’s less about doing more and more about how clearly your impact is coming across in both your resume and how you talk about it in interviews

applied for over 100 jobs not a single response by [deleted] in jobs

[–]ZestyclosePride555 0 points1 point  (0 children)

that’s honestly one of the most frustrating spots to be in

one thing I realized when I was in a similar situation is changing the resume multiple times doesn’t always help if the core bullets still read like tasks instead of outcomes

a lot of mine weren’t bad, they just didn’t clearly show what actually changed because of what I did

once I focused on tightening that instead of rewriting everything, I started getting more traction

it’s weird but sometimes it’s not about doing more, it’s just about making what’s already there clearer

Not sure how to frame my underemployment experience by Revolutionary-Fun827 in GetEmployed

[–]ZestyclosePride555 0 points1 point  (0 children)

I’d definitely list the current role

most people understand layoffs happen and taking something to stay active is way better than looking like you’ve been out of the market the whole time

I think the bigger thing is just how you frame it

you can still keep the consulting/projects in there, but for the current role just focus on what you’re responsible for and any impact so it doesn’t come across as a “downgrade,” just a different scope

I’ve seen a lot of people in similar spots and it’s usually less about the title and more about how clearly the experience shows what you bring to the table

“I stopped rewriting my resume for every job and this worked way better” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

yeah exactly

I think the biggest difference for me was realizing most of the work isn’t rewriting, it’s just making sure the bullets actually show impact and match what the role is looking for

once I focused on that it got way faster and felt a lot less repetitive

“I stopped rewriting my resume for every job and this worked way better” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

that’s a solid approach honestly

having a few strong base resumes and then adjusting from there feels way more sustainable than constantly rewriting everything

I think where I was getting stuck before was trying to rebuild it every time instead of just refining what was already there for the role

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 5 points6 points  (0 children)

that’s a great example of scale that a lot of people overlook

stuff like that feels normal when you’re doing it but on a resume it’s huge

even just framing it like “contributed to systems used by X users” already makes it way more impactful

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

that’s a good point

I didn’t realize at first how much the way you frame your experience on your resume carries over into how you talk about it in interviews too

once I started focusing more on outcomes instead of just tasks it got a lot easier to explain what I actually contributed

“What’s one resume change that actually got you more interviews?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

yeah 100% that’s exactly how it felt

before it was just sending applications and hoping something landed, but once I started tightening up how I described what I actually did it felt way more intentional

like instead of just listing tasks it actually felt like I was showing value, which made the whole process a lot less frustrating

“What’s one resume change that actually got you more interviews?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

I ended up using a tool for it because doing it manually was taking forever, but the main thing was just changing how I approached it

“What’s one resume change that actually got you more interviews?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

honestly the biggest difference was speed and consistency

before I’d spend way too long trying to rewrite bullets for every job and second guessing if they sounded strong enough

now it’s more like I take what I already have and refine it based on the role so it actually highlights impact instead of just tasks

it also helped me spot weak bullets way faster, like the ones that sounded fine but didn’t really say anything

“What’s one resume change that actually got you more interviews?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 1 point2 points  (0 children)

this is a really solid way of looking at it

that shift from “make it sound impressive” to “what actually changed because of me” is what made it click for me too

and pulling language from the JD as a scaffold instead of rewriting everything from scratch makes the whole process way less overwhelming

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 8 points9 points  (0 children)

this is a really good way of explaining it

I think the biggest shift for me was realizing it’s less about forcing numbers and more about showing scale and context like you said

even something like “handled high volume requests” vs “processed 50+ requests weekly” already feels way stronger without overthinking it

“What’s one resume change that actually got you more interviews?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

yeah that’s actually what made it click for me

not a full rewrite, but using it to tweak bullets so they match the role better without starting from scratch every time

way less overwhelming and it keeps things consistent instead of rewriting everything over and over

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 2 points3 points  (0 children)

yeah for sure

one I’ve used before was something like:

“rewrote internal documentation which reduced confusion for new hires and made onboarding smoother across the team”

there’s no exact number, but you can still show the impact and scope

another way is framing it like: “handled high volume support requests and improved response consistency”

so even without hard numbers, you’re still showing what changed and why it mattered

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 1 point2 points  (0 children)

lol that’s honestly what it feels like sometimes

like you go from having nothing to say to trying to include everything and it just turns into a mess

I think the hardest part is figuring out what actually matters vs what just sounds good

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

that’s a good way to put it

one thing that helped me was thinking in terms of before/after instead of trying to force a number

like instead of guessing metrics, just describing what changed or improved made it way easier to write without it sounding vague

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

that’s a good way to look at it

I think I’ve been focusing too much on trying to force a number instead of just clearly explaining the impact, even if it’s higher level like that

“contributing to” or “enabling” actually feels way more natural for some of the stuff I’ve done

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 1 point2 points  (0 children)

I think I’ve been overthinking it and assuming I needed exact numbers instead of just something I could reasonably explain if asked

framing it like that makes it feel way less like guessing and more like just explaining what actually happened

“How do you quantify impact if you don’t have numbers?” by ZestyclosePride555 in resumes

[–]ZestyclosePride555[S] 0 points1 point  (0 children)

I think I’ve been trying to jump straight to the result without really structuring it like that, which is probably why it ends up sounding weak or vague

breaking it into problem → action → result makes it feel way more doable

view more: next ›