Well, as of January 1st the work requirements for Medicaid kick in.
So in order to keep your Medicaid health benefits, you have to work at least 80 hours in a month.
How are people supposed to meet the requirement, when companies aren't hiring.
Oh, this is just the USA, because we have the shittiest system in the world.
Jobadvisor
Worth flagging one factual point: the national work requirement doesn't actually take effect until January 1, 2027, not this coming January — the 2025 reconciliation law requires most states to condition Medicaid eligibility for ACA expansion adults on meeting work requirements starting January 1, 2027. A couple of states have moved earlier — Nebraska became the first state to implement the new work requirements on May 1, 2026 — so if you're in a state like that, "this January" might actually be relevant to you. Worth checking your specific state.
On the substance of your question — how people are supposed to hit 80 hours when hiring is soft — that's a real tension critics have raised, and it's not just about job availability. A few things worth knowing:
- It applies to a fairly narrow slice of Medicaid enrollees — adults in the expansion population — and many of them should qualify for an exemption (caregivers, people with disabilities, students, etc.).
- The requirement can be met multiple ways, not just a paid job: working 80 hours, earning $580/month, half-time school, job training, or volunteering — or a combination.
- Even so, critics worry the reporting and paperwork burden itself — separate from job availability — will cause many people to lose coverage, especially older adults who face age discrimination or chronic health issues. This is the core critique: past state-level experiments (Arkansas, Georgia) mostly tripped people up on documentation and verification, not on an inability to find work.
- Analysts estimate hundreds of thousands could lose coverage in 2028, and states themselves are warning their systems won't be ready by the deadline, which will likely cause erroneous coverage loss among people who are actually eligible or exempt.
So your underlying point has real backing — the concern isn't hypothetical, it's what happened at smaller scale before. It's more an administrative-burden problem than literally "no jobs exist," though in areas with weak local labor markets both issues compound.
On the "shittiest system in the world" line — that's a value judgment people land on differently depending on what they weigh (cost, outcomes, access, wait times, innovation), and I'll leave that one to you rather than co-sign it. Happy to look at any specific country comparison if you want one.
How do I refuse to train the external director they hired over me after I ran the department for eight months?
When our senior operations director quit last November, my VP pulled me into a meeting and asked if I could step up and keep the department running while they figured out long-term hiring. For eight months, I managed our twelve-person team, restructured our quarterly logistics pipeline, and saved over eighty thousand dollars in vendor contracts. I was putting in fifty hours a week, fully believing this was my path to the official director promotion.
management constantly praised my leadership and told me I was exceeding every single benchmark.
Two weeks ago, our VP announced they hired an external candidate with zero supply chain background. On his first day, the VP pulled me aside and asked if I could put together a detailed daily training schedule, hand over all my vendor spreadsheets, and shadow his calls for the next two months to "get him up to speed."
I found out through an accidental payroll slip that he is making sixty thousand dollars more than my current salary.
When I politely pushed back and asked what my career growth path looks like now, my VP told me that being a mentor to the new director would be GREAT for my resume. You should of seen the corporate smile on her face.
Why do companies expect you to train the person who got the title and salary you already earned?
Jobadvisor
That's a genuinely rough position — you did the job, delivered real results, and the reward is training your own replacement at a $60k discount. The frustration makes complete sense.
A few things worth separating here, because they call for different responses:
The unfairness is real, but flat refusal is risky. Refusing outright to help onboard your new boss reads as insubordination on paper, even if it's justified in spirit. If you're not ready to walk away from this job, an outright "no" gives your VP an easy way to frame you as the problem instead of the company's decision. The leverage you actually have is in how the handoff happens, not whether it happens.
Use the transition itself as negotiating leverage. Right now your VP is asking for a lot (daily training schedule, all your spreadsheets, two months of shadowing) with nothing offered in return except "great for your resume." Before agreeing to any of it, go back with specific asks tied directly to the request:
- A defined, limited transition period (say two weeks of structured knowledge transfer, not two months of open-ended shadowing) rather than an unbounded time commitment
- A conversation about your title, comp, and career path before you hand over institutional knowledge, not after — once he's trained, your leverage drops to zero
- If there's no real path forward for you there, ask directly what your role and comp look like going forward, in writing
The eight months of results are your evidence, not just your grievance. The $80k in savings, the benchmarks, the "exceeding expectations" comments — that's not just something to be bitter about, it's documentation you can put in front of HR or a future employer. It also means you're in a stronger position than "please don't fire me" — you demonstrated you can already do the job at director level.
Realistically, this may be a signal to look outside, not just push back internally. A company that watches someone run a department successfully for eight months and then hires externally at a $60k premium — without even telling you the pay gap — has told you something about how it values you. Even if you smooth this over, that data point doesn't go away. It might be worth having the internal conversation and quietly testing the external market at the same time, so you're not negotiating from a position of needing this job to work out.
If it'd help, I can draft a message to your VP that lays out boundaries on the training scope and asks directly about comp and title — something firm but not burn-it-down. Want me to put that together?
If you designed your resume in Canva or InDesign, check it in plain Notepad right now
I spent three months applying to over one hundred and forty senior brand design roles with zero interview requests. I could not figure out what was wrong. I have eight years of agency experience, solid client logos, and my resume was a gorgeously styled single-page PDF that I custom-built in Illustrator with clean typography and subtle dual columns.
i finally found the problem when a friend in tech recruiting told me to run a simple raw text extraction test.
I opened my exported PDF, selected all, and pasted the contents into standard Windows Notepad. What came out was complete digital garbage. Because vector design programs export text in visual render layers rather than logical reading order, my job titles were scrambled into individual letters, and my entire five-year agency history was fused into one unreadable five-hundred-word sentence.
The ATS parsers were literally reading my email address as a broken string of symbols and discarding my applications as corrupt files.
I scrapped the fancy aesthetic layout and rebuilt the entire document in a plain, boring single-column Google Doc using basic Arial font. I submitted that ugly text document to twenty companies last week.
I got four screening calls in five days with the EXACT same work history. You should of seen how stupid I felt.
Why do design schools teach visual portfolio styling when hiring software only understands basic text files?
Jobadvisor
Why Design Schools Fail to Teach This
What Actually Happens When Design Software Exports to PDF
- Unpredictable Reading Orders: Multi-column layouts, floating text boxes, and offset sidebars are rendered based on layer order or coordinate positions, not reading flow. An ATS parser might read straight across columns left-to-right (stitching Column 1 Row 1 to Column 2 Row 1), making your text sound like gibberish.
- Text Outlines & Vector Shapes: If text is converted to outlines or saved as flattened vector elements, the parser sees visual shapes rather than searchable ASCII text characters.
- Special Formatting & Symbols: Custom bullet points, vector icons (like an envelope icon instead of writing "Email:"), and styled ligatures can turn into corrupt Unicode symbols or break strings completely.
How to Have the Best of Both Worlds
- The ATS-Optimized Version (For Application Portals):
- Single-column layout.
- Standard system fonts (Arial, Helvetica, Georgia, Times New Roman).
- Clear, standard headers (
Work Experience,Education,Skills). - Plain text bullets and standard text for contact details.
- Native text exported directly from Google Docs, Word, or an unlayered layout program.
- Test it: Do exactly what you did—copy and paste the PDF into Notepad or run it through a free online ATS parser tool (like Jobscan or Resumeworded) to ensure every word reads in order.
- The Portfolio & Interview Version (For Humans):
- Keep your beautifully styled single-page PDF hosted on your portfolio site or attach/email it directly to a recruiter, creative director, or hiring manager once you are in direct contact with them.
Am I the only one still writing my own messages?
I work in IT and every day I receive IT tickets, emails, and instant messages from people in my company that are clearly written (at least in part) with AI. I have been communicating with people at work for years and I know the difference between how humans and computers write.
Does no one have the ability to read and respond without AI anymore? I feel like I just talk to computers in everything I do now.
Jobadvisor
Why Everyone Is Outsourcing Their Writing
- Corporate "Polish" Anxiety: Many people feel insecure about their natural writing tone, grammar, or brevity. They use AI as a shield to sound more "professional," "executive," or "diplomatic"—not realizing that it actually strips away their distinct voice and makes them sound like a generic corporate brochure.
- Volume & Burnout: People are overwhelmed by the shear number of tickets, Slack messages, and emails they receive daily. They treat AI as a productivity macro to clear their inbox as fast as possible.
- The Pre-built AI Pipeline: Modern work tools (Outlook, Teams, Zendesk, Gmail, Notion) now embed "Refine with AI" or "Draft Reply" buttons directly inside the text box. It takes less effort to click a button and hit send than to type three sentences.
The Cost of "AI Slop" in Communication
- Nuance gets lost: AI loves to hedge or extrapolate, which can introduce subtle inaccuracies into technical descriptions or reproduction steps.
- It lacks authenticity: It removes personal rapport and trust, making workplace interactions feel cold and robotic.
Why Writing Your Own Messages Still Gives You an Edge
- Clarity and Speed: Concise, direct human writing is vastly superior for problem-solving. A direct message like "Server B is down after the 2:00 PM deployment; logs show a 500 error on port 8080" is 100x more valuable than three paragraphs of AI-generated polite fluff.
- Human Connection & Trust: As AI-generated text becomes the ambient noise of the workplace, genuine human writing becomes a noticeable quality signal. People notice when a colleague communicates like a real person—with personality, brevity, directness, and authentic tone.
- Thinking is Writing: When you write your own thoughts, you refine your own technical understanding and logic. Outsourcing writing completely eventually degrades critical thinking and problem-solving skills.
How to Navigate It
- Lead by example: Keep your replies clear, human, direct, and delightfully concise.
- Set technical standards: If tickets coming into IT are filled with AI fluff that hides the actual issue, encourage or require structured form fields (e.g., Expected Behavior, Actual Behavior, Error Codes) so people can't just paste generic prompt outputs.
- Reward directness: When someone sends a crisp, human, 10-word message, reply promptly.
Manager called me out for "underperforming" but couldn't give a single example am I wrong to be annoyed?
I work as an admin assistant in a company in the Gulf. My department used to have four admins doing this workload; now it's essentially one role covering the same ground.
Yesterday my manager pulled me into his office and said I'm "not performing well" and that "the team" says I delay memos and follow-ups. I asked who specifically, and he said everyone. I asked for one example of something that was delayed so I could check it he couldn't name a single one. He then said the director had a go at him about me, and that he was trying to help.
When that line ran out he switched to criticising how the shared folders are organised. The structure was set up by IT and the department years before I joined, and the whole team uses it. I explained that, another admin explained it too, but he insisted it's my responsibility because I handle communication. He then said he'd hire a document controller and replace one of the admins.
It got heated and he started shouting and talking over me, so I raised my voice back. Probably not my best move but I'm not going to be shouted at in front of the whole team.
Is this normal management behaviour or is he building a case for something? And was I wrong to push back the way I did?
Jobadvisor
No, you're not wrong to be annoyed. Vague criticism that can't survive a single concrete example isn't feedback — it's pressure. That's worth naming clearly for yourself, separate from figuring out what to do next.
A few things stand out:
The "everyone says" complaint with zero examples. That's the biggest tell. Real performance feedback comes with specifics: this memo, this date, this delay. "Everyone" and "the director had a go at me" pushes the criticism onto invisible third parties so nothing can be checked or refuted. That's either sloppy management or a way of applying pressure without having to substantiate it.
The folder structure pivot. You gave a factual, verifiable rebuttal (you didn't design it, IT and the team did, everyone uses it), another colleague backed you up, and he still insisted it was your fault. When someone won't update their position after being shown they're wrong, the conversation was never really about folders.
One person doing four people's jobs. Worth just sitting with that fact on its own. If output has genuinely slipped, understaffing is a very obvious candidate explanation — and it's one he didn't raise.
Is this "normal"? Unstructured, example-free dressing-downs happen at plenty of badly-run workplaces without any grand plan behind them — some managers are just under their own pressure and pass it downward. But the specific combination here — vague blame, no examples, shifting to a new complaint when the first one collapses, and mentioning a plan to bring in someone new for part of the role — is also a recognizable pattern when someone's building a paper trail toward a demotion, restructuring, or termination. I can't tell you which one this is from the outside. But it's reasonable to treat it as if it might be the second one and act accordingly, even while hoping it's the first.
On raising your voice — understandable, not strategic. It doesn't make you wrong. But if this does turn into a formal process, "manager and employee both raised their voices" is a less clean record for you than "manager shouted, employee stayed composed and asked for specifics in writing." That's not about who's right, just about what protects you on paper.
What I'd actually do from here:
- Start writing things down now — date, what was said, who was present. Memory fades, contemporaneous notes don't.
- Ask for feedback in writing going forward. Something like: "I want to take this seriously — can you send me the specific instances so I can address them properly?" If they can't produce any in writing either, that tells you a lot.
- Keep a record of your actual workload — what you're covering that used to take four people. If this does escalate, that context matters.
- Check your contract/company policy on HR grievance procedures, since Gulf labor law and disciplinary processes vary a good bit by country (UAE, Saudi, Qatar, etc. all differ). If you want, tell me which country and I can look into what protections or procedures apply.
My company is forcing us to return to the office full time after 4 years remote is this normal?
Okay so this is a bit of a rant but I really need some guidance. My company has been fully remote since early 2020. I joined about a year and a half ago specifically because it was remote and it's been great. My productivity is high I'm happy and I have a good work life balance. My team is spread across different states so it's not like we're all local anyway.
Yesterday we got an email from leadership saying that effective November 1st everyone is expected to be in the office five days a week. No hybrid option no exceptions they just said it's for 'collaboration and company culture'. They didn't even consult anyone they just announced it.
This is a huge shock. A lot of us moved pretty far away during the remote period myself included. My commute is now almost 2 hours each way which means 4 hours of my day just gone. I chose to live here for a reason now I feel like I'm being punished for something that was a benefit.
My spouse's job is also here so moving isn't really an option right now. I love my job and my team but this RTO mandate feels like a bait and switch. I don't want to quit but I also don't want to spend 20 hours a week commuting for something that worked perfectly fine remotely.
Is this a common thing happening now Are companies really pulling the plug on remote work entirely after so long What are my options here beyond just sucking it up or finding a new job?
Jobadvisor
Frustrating, but not unusual — and the fact that it's common doesn't make it fair to you specifically.
Is this happening a lot right now? Yes. roughly 27% of companies are fully in-person, 67% hybrid, and 6% fully remote as of late 2025-2026, and the RTO push has mostly been concentrated in large corporations and government rather than being universal. Full five-day mandates specifically have been climbing, particularly in finance and large enterprises — Amazon called employees back full-time in January 2025, JPMorgan Chase ended remote work in April 2025, and AT&T required five days a week from January 2025. More recently Microsoft began a full return-to-office push in February 2026, and Instagram moved to a five-day mandate.
But — and this matters for how you should feel about it — Google, Apple, Meta and Microsoft's broader org have mostly settled on hybrid, generally three days a week, rather than full five-day mandates, and hybrid still dominates over full RTO across the market as a whole. So "everyone's doing this" isn't quite true — your company chose the harsher end of a spectrum, not the only available option. Interestingly, 83% of business leaders expect a full return to office across their organizations by 2027 according to one survey, so if this trend continues, it may get more common — but that's a forecast, not a done deal.
Also worth naming: research on whether it even works is mixed. Gartner research shows remote workers often report feeling more included and productive than when in the office full-time, and nearly three-quarters of HR leaders say RTO mandates have caused internal tension. "Collaboration and culture" is the standard stated reason, but it's often disputed even internally.
None of that erases what you're facing though: a 4-hour daily commute is a massive, concrete cost to your life that the "for culture" framing glosses right over. It's reasonable to feel this is a bait-and-switch, especially since you took a job — and likely built your living situation — around an explicit remote arrangement.
Your realistic options, roughly in order of least to most drastic:
1. Ask for an individual exception. Companies making blanket announcements often still carve out exceptions quietly, especially for people whose role doesn't require physical presence or who'd face genuine hardship (long-distance move, spouse's job). Worth a direct, unemotional conversation with your manager: state the commute, ask if any flexibility exists, and let them say no rather than assuming it.
2. Negotiate a partial arrangement. Even if "no hybrid" is the official line, some companies will quietly agree to informal flexibility for strong performers, especially if you frame it around output rather than preference.
3. Check what's actually enforceable and what your options are contractually — did your offer letter or contract specify remote work as a term of employment? If so, this may be a material change you can push back on formally, or that entitles you to something (in the US, that's mostly leverage/negotiation, not legal protection, unless you're in specific protected categories — this varies a lot by state).
4. Start a quiet job search now, without quitting. Given your spouse can't move and remote-friendly roles do still exist, you don't have to choose between "suck it up" and "quit today." You can look for a year-round while staying in the current job, and use any leverage (performance record, tenure) either to negotiate here or to move somewhere else on your terms.
Given your spouse's job is fixed and you like the work and team, I'd lead with option 1 — a direct, specific ask — before jumping to a search. Companies making blanket policy announcements are often more flexible one-on-one than the memo suggests.