u/Bensutki

One slightly off reply at work and my head goes: theyre annoyed -> theyre documenting -> im getting pushed out -> i should preemptively quit.

The annoying part is it feels rational in the moment because i can usually explain the chain. But the chain starts with a guess.

What’s helped me is separating:

1. Observation (what happened, verbatim)
2. Inference (my best guess)
3. Conclusion (what i’m about to act on)

My rule now: i’m not allowed to act on a conclusion unless i have two independent observations that point the same way. “Tone felt cold” doesn’t count as one. “They removed me from the meeting i normally run” counts.

I also started writing the “alternative explanations i hate” (they were busy, they assumed id see the doc, they forgot). If i can list 3 plausible ones, i’m not allowed to treat my inference as truth yet.

For tracking, i dump the raw facts into Google Sheets, a notes app, and the Coached career assessment (mostly so i stop arguing with myself in circles).

The other thing i had to admit: my dataset is trash when i’m stressed. I sample from the last 3 negative interactions and call it a pattern. So i force myself to add counter-data on purpose: times they did trust me, times i was wrong about “tone,” times the scary story didn’t happen.

If you do this too, what’s your threshold before you act? One strong signal, two, more? And what counts as a real signal vs “vibes”?

Just started a new job and I’ve already made the same mistake: trying to be "easy to work with" by being way too available and open. By week three, a coworker pulled me into the breakroom to "check on me," and I was dumb enough to mention I was still interviewing elsewhere because the workload was already insane. Two days later, my manager is breathing down my neck asking why I’m "not committed," and suddenly I’m on a performance plan for stuff that was never even an issue before.

It’s such a gut punch. I realized the problem isn't having work friends. It’s thinking that being friendly means they need total access to my life. I’ve had to build this mental "trust ladder" just to survive.

I stay polite and talk about boring stuff like weekend plans or memes, but I’ve completely cut off the personal stuff. No talking about health, money, or definitely not my plans to quit. The trap is that spending 40 hours a week with people makes Level 2 feel like Level 4, so you overshare just to feel like a human being.

I’ve started keeping my entire "exit strategy" strictly to myself so I don’t end up trauma-dumping to random coworkers when I'm stressed. I actually spent a few nights running my updated CV through resumeworded, and it was a huge help for my sanity. It didn't just help me fix the document, it gave me a way to focus on my actual worth and accomplishments outside of this toxic office environment.

I realize that my value isn't tied to what my manager thinks of my "commitment," but to the actual impact I can prove on paper. It gave me the confidence to keep my head down and keep looking for the door.

I’m done with "can I be candid?" talks with peers. If I wouldn't want it forwarded to the CEO, I don't say it. No more complaining about personalities, just tracking dates and facts. I'm also done assuming HR is neutral. If it’s not illegal, they aren't going to help. I'm trying to figure out if it's even possible to have real friends here without it blowing back on me, or if I just need to keep my guard up until I finally get out.

About 2 months into this job search I realized my resume looked like I was trying to convince companies I could do literally every data job on earth.

ML, analytics, DE, GenAI, dashboards, pipelines, experimentation, forecasting. Just a giant pile of keywords with no actual identity. I think I kept adding stuff because getting ignored makes you panic and start thinking “maybe I just need MORE.”

The annoying part is I’m not even entry-level. I’ve got 3 years experience, real projects, production-ish work, actual business impact. But my resume somehow made it all feel vague and watered down.

This week I finally split everything into separate versions depending on the role. One more analytics-focused, one more applied ML-focused. Immediately felt less embarrassing to look at. I also cut down the giant tools section because half of it read like I touched something once in 2022 and wanted credit forever.

Biggest realization was that my bullets barely explained why anything mattered. They were all method-first. “Built model.” “Created pipeline.” Cool, who cares? I rewrote a bunch around outcomes/decisions instead.

At one point I ran the resume through Resumeworded and sent it to a friend who hires analysts because I genuinely couldn’t tell anymore whether my resume sounded competent or just overloaded. Helped me notice how scattered the story felt. Like I was applying emotionally to every possible DS posting instead of looking like someone who knew where they fit.

Still kinda torn on whether having multiple resumes is smart or if it just makes me look inconsistent if the same company sees both somehow.

I spent waaay too long thinking I had an “offer decision” problem when really I was applying to jobs I didn’t even want once you looked past the title.

I’d get excited about a posting, go through interviews, maybe even get an offer, then feel this weird dread when they described the actual day-to-day. That was a pretty bad sign.

The biggest thing that helped was making a literal “NO” list before applying anywhere. Stuff like heavy on-call, endless ticket cleanup, being the only person holding together some ancient system, calendars packed with meetings pretending to be engineering work, all that.

I also stopped using one generic resume for everything. I made two versions: one leaned more backend/reliability, the other more product-facing. Same experience, just different emphasis depending on the role.

At some point I threw the bullets into ChatGPT and Resumeworded because after staring at the same resume for weeks I genuinely couldn’t tell anymore which lines sounded clear and which sounded like vague tech filler. It actually helped me trim a lot of bloated wording.

Another thing I started doing: reading the first part of the job description like it’s a personality test for the company. Sometimes you can immediately tell the role is going to turn into “please save our dumpster fire.”

Now I apply to fewer jobs, but the interviews feel way less fake because I’m not trying to force myself into roles I already know I’ll hate six months later.

At this point my biggest red flag is when recruiters can’t explain what engineers actually spend most of their week doing without defaulting to buzzwords.

Anyway, I'm still unemployed (lol), but I feel like I'm getting closer. I hope this helps those in the same boat and I'm also open to advice from ya'll!

PM skills transfer. PM resumes usually don’t.

I didn’t really get this until I started sitting on hiring panels. You can feel it within seconds. If your resume doesn’t sound like the world we’re hiring for, it’s over.

When we posted a construction PM role, we got buried in resumes from IT PMs who clearly had never stepped on a job site. For SaaS roles, we’d see long writeups from plant PMs with zero mention of customers, integrations, anything like that. Same pattern every time.

It’s not that those people were bad. It just felt like reading something in the wrong language. And honestly, no one has the patience to sit there and translate it for you.

I made the same mistake when I tried moving from internal ops into SaaS. I kept thinking “PM is PM,” so I sent out my resume as-is and got absolutely nothing back. Not even rejections. Just silence.

What finally clicked for me was realizing I had to rewrite my experience so it actually sounded like SaaS work.

I pulled a bunch of job posts and looked for repeated words and phrases. Stuff like go-lives, vendors, integrations, customer teams. I even ran some of it through and Resumeworded just to see patterns and tighten the wording. Then I went back to my own projects and pulled out anything that even slightly overlapped.

So instead of saying I improved warehouse processes, I talked about rolling out a cloud system across multiple sites, working with a vendor, coordinating with IT, hitting a cutover date. Same project, just told in a way that made sense to them.

Also had to stop hiding behind vague terms like “stakeholders.” I started naming who I actually dealt with. Ops managers, IT, vendors, whatever. It reads very different.

Once I did that, I finally started getting replies.

It’s kind of frustrating, because nothing about my actual ability changed. Just the way I described it. But yeah, that was the difference.

After getting burned by three jobs in a row that looked great on paper, I realized I didn't actually have a working definition of fit. I just knew it when I felt it, which is useless when you're trying to evaluate an offer.

So I made a list. Not values or mission stuff (that's all marketing anyway), but actual day-to-day conditions:

1. Manager style - do they micromanage or disappear? I need someone who sets clear expectations and then gets out of the way.

2. Pace - some companies take three weeks to approve a simple decision. I lose my mind in that environment.

3. Flexibility - can I shift my hours if something comes up or is it rigid 9-5 in-office?

4. Scope creep - is the role actually what they described or will I end up doing three jobs?

5. Team energy - are people collaborative or is it every person for themselves?

I keep a running doc in Google Sheets and also used resumeworded to make sure my actual resume reflected the environments I was targeting, not just job titles.

The thing is, companies weaponize 'fit' to reject you for vague reasons. But candidates need it MORE than companies do. You're the one who has to show up every day. You're the one who'll burn out if the environment is wrong.

Now when an interviewer asks why I'm interested, I don't perform excitement. I say something like 'based on what I've learned so far, it seems like the kind of environment where I do my best work - clear priorities, autonomy on execution, and a team that actually talks to each other. Does that match how you'd describe it?'

Turns the question around. Makes them prove fit to YOU.

Fit isn't vibes. It's whether the day-to-day conditions match how you actually work.

I know this might sound like common sense to a lot, but it's crazy how many people don't understand this. Anyway, I hope this helps. Good luck fellow jobseekers!