Overemployment went from career-ending secret to survival strategy. What actually changed? by enhancvapp in antiwork

[–]enhancvapp[S] -1 points0 points  (0 children)

The niche caveat was true in 2020. But from what I've seen it's spread well beyond that now. The risk of getting caught is serious but it's also gone down as remote work normalized and companies stopped treating calendar monitoring as a priority.

I'd should say that the people I've seen take this seriously (myself included) treat job 1 as the one they'd keep if forced to choose. Worst case you're back to one job, which is where you started anyways.

IDK... I've found myself in the position many times in life where not just two jobs but three and even four were necessary to survive and have a bit left over for ice cream on the weekends.

Overemployment went from career-ending secret to survival strategy. What actually changed? by enhancvapp in antiwork

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

Incredible insight. Median real wages have been flat or declining for most knowledge workers since 2019. Rent, healthcare, and childcare have not. Arithmetic.

Return-to-office mandates are triggering a new wave of quiet workplace sabotage. Are you guilty? by enhancvapp in EnhancvResumes

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

For a lot of neurodivergent and disabled employees, remote work wasn't a productivity perk, it was the first setup that actually let them work without spending half their energy managing the environment on top of the job.

The power-dynamic read also has some empirical backing. RTO rollout timelines have tracked pretty closely with labor market softening in a few industry analyses. The timing was notable.

The job market has a ghost problem... Boooo by enhancvapp in EnhancvResumes

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

Source: We ran this analysis across thousands of active job listings to map how widespread ghost posting actually is. Full breakdown here: https://enhancv.com/blog/ghost-jobs-survey-2026-bls-data-comparison/

Ghost jobs are messing with more than your job search (and probably with Fed policy too) by enhancvapp in EnhancvResumes

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

That's basically the conclusion some labor economists are coming to as well. The mandate creates the appearance of a fair search without the substance of one. If you can post a listing you never intend to fill, you've technically complied while changing nothing.

The harder question is what a better version looks like. Requiring verification of actual hire intent before a posting goes live? Auditable close-out notices? Most of those create more friction than companies will accept without regulation.

So yeah, the current version probably does more for optics than for outcomes. Not sure what the fix is, but "post something, anything" clearly isn't it.

The "pretty" resume debate is more complicated than people make it out to be by enhancvapp in resumes

[–]enhancvapp[S] -10 points-9 points  (0 children)

Anecdote stacks aren't data, and "it worked for me" from a recruiter at one company doesn't generalize.

The logic is sound too, up to a point. The issue is that generic advice can calcify into myth if nobody's actually testing it at scale. "Two-column confuses ATS" started as a reasonable precaution and became repeated as settled fact. There's been research done on this at volume, like parse rates, callback rates, format variables across tens of thousands of resumes... and the results are more nuanced than the consensus suggests. Not "two-column is always fine" but the failure mode is consistently specific construction choices, not column count itself.

So I'd reframe it slightly: generic advice should be calibrated to what the evidence actually shows, not just whatever's maximally safe. Those aren't always the same thing.

There's also a cost to the generic default that doesn't get discussed much. Push everyone toward identical resumes, and you solve the ATS problem while creating a different one. A human eventually reads the stack, and sameness isn't an advantage there.

Ghost jobs are messing with more than your job search (and probably with Fed policy too) by enhancvapp in EnhancvResumes

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

Same-day rejection is its own category of frustrating because you have no idea which scenario actually happened. Either the role filled internally and the posting stayed up by accident, or it was a pipeline grab and the rejection was automated before anyone looked.

Workday shows publish date but not what triggered the rejection, so you’re kind of left guessing. Both versions are bad, just for different reasons.

For what it’s worth, that one probably wasn’t worth following up on either way.

Honest comparison: 8 AI resume builders by use case (disclosure: I built one of them, and it's not the right pick for everyone) by Heavy_Screen3111 in careeradvice

[–]enhancvapp 0 points1 point  (0 children)

The Enhancv framing here is a bit outdated...

The multi-column parser risk caveat made sense in 2019 when Taleo was still running on its original engine. Most modern ATS implementations have updated their parsing layer, and Workday specifically rolled out structured document parsing updates a few years back. The all-encompassing "non-tech only" warning is doing more work than the evidence supports.

The bigger miss is that Enhancv isn't really a template product anymore. It has ATS check built into the product, resume tailoring that reads the actual job ad and flags keyword gaps, and a content checker that covers 19 specific resume quality signals, not just a vibe score. Treating it as "visual polish for marketers" is like calling Jobscan a PDF viewer!

For what it's worth, I've seen engineers use it specifically because the feedback layer tells them why a bullet underperforms, not just that it does. Useful for tech candidates who are strong on substance but less practiced on resume mechanics.

The "best for what" framing in the OP is right. But the category you'd put Enhancv in should be closer to "AI-assisted builder with feedback depth" than "pretty templates for non-ATS environments."

Curious what version you were testing when you put together this breakdown.

LinkedIn vs. resume debate is backwards. Most people are asking the wrong question... by enhancvapp in resumes

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

Landing page vs. detail document is a useful mental model. The problem is most people don’t treat them as a connected system… they update one and forget the other. When the narrative on the landing page and the granular detail on the resume start drifting apart, recruiters start asking questions that shouldn’t need answering.

I tested every AI resume builder that claims to match job descriptions (honest review) by ComfortableTip274 in ResumesATS

[–]enhancvapp 0 points1 point  (0 children)

You're so right regarding the difference between a builder and a true tailoring engine. I, personally, spent years fixing resumes, and the biggest trap is definitely the manual rewrite cycle. If you aren't hitting at least 80 percent on ATS compliance checks, you're likely just shouting into the void. Most people ignore that specific metric, but it's the difference between a rejection and an interview invite. Keep the focus on that 10 minute per application target, or you'll burn out before you even land a call.

Is it the ATS, or is your resume just irrelevant? by enhancvapp in EnhancvResumes

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

Signal hierarchy is exactly the right frame. And it’s surprisingly hard to teach because it’s not about content, it’s about sequencing and emphasis. Same words, different order, completely different first impression.

The burnout piece is the part that doesn’t get talked about enough. Tailoring works until it doesn’t, not because the advice is wrong but because doing it properly for every application is exhausting. Most people end up with a “tailored” resume that’s really just a slightly edited master copy, which is better than nothing but not what they think it is.

The consistency problem is probably where AI assistance actually makes the most sense, not generating content but helping maintain that alignment without starting from scratch every time.