My Boss Uses WFH Weekly But Blocks The Staff From Doing It
I have worked in my office several years and we have the option to work from home 1x week with managers approval. My boss has used multiple excuses to block the staff from using the option but then proceeds to use it every week herself. The common argument is "departmental needs" prevent us from using it while the rest of the other departments use it no problem.
She emailed our department this week again saying unilaterally we are not allowed the option. I got fed up and asked her via "reply all" why she gets to use it but we aren't (which of course we received no reply). I took it a step further and asked the department head via email why there are different standards for employees and managers, and I was told that they would "caution me againts using generalizations like that when I don't know all the details". I don't understand how I am the bad guy for calling out the hypocrisy!
Jobadvisor
I hear your frustration, and honestly, it’s completely valid. There is nothing quite as demoralizing as "rules for thee, but not for me," especially when the "departmental needs" excuse feels like a transparent shield for a double standard.
The reason you feel like the "bad guy" right now isn't because you're wrong—it’s because of how the message was delivered. In corporate environments, logic often takes a backseat to hierarchy and "professional optics."
Here is a breakdown of why the leadership is pushing back and how to navigate this without further damaging your standing.
Why You’re Getting This Response
The "Reply All" Factor: In the eyes of management, a "reply all" that challenges a boss is seen as a public act of insubordination rather than a genuine question. It puts your boss on the defensive in front of her entire team, which usually leads to a shutdown rather than a dialogue.
The Department Head's Deflection: When the Department Head warned you about "generalizations," they were using corporate-speak to protect the management layer. They likely know exactly what’s happening, but they see your direct call-out as a threat to the "chain of command."
Managerial Discretion: Most companies write policies that give managers "sole discretion." This is the loophole she’s using. Even if it’s unfair, it’s technically "within policy," which makes it a hard wall to kick down with emotion alone.
How to Pivot
Since the direct confrontation has already happened, the goal now is de-escalation and documentation.
| Instead of... | Try... |
| Publicly questioning her integrity. | Privately requesting a meeting to define "departmental needs." |
| Comparing yourself to her. | Comparing your department to the rest of the company. |
| Using "Why" questions (which feel accusatory). | Using "How" questions (which feel collaborative). |
Recommended Action Plan
Cool the Engines: Avoid sending any more "reply all" emails or further escalations to the Department Head for a few days. Let the dust settle so you aren't labeled as "the emotional employee."
Request Specificity: In a 1-on-1 setting, ask: "I want to ensure I’m meeting all departmental needs. Could we define what specific metrics or coverage requirements need to be met so that WFH becomes a viable option for the staff again?" This forces her to put concrete requirements on paper.
The Paper Trail: If she continues to block it while using it herself, keep a private log. Don't share it yet, but have a record of dates she worked from home versus dates staff requests were denied. This is for HR, should you ever need to file a formal grievance regarding a toxic work environment.
It’s a tough spot to be in, but the goal is to make it impossible for them to call you "unprofessional" while you're highlighting their lack of fairness.
Should I stay with company after they offered me fully remote?
I was giving 2 week notice to my boss, due to my long commute (1 hour each way), and to my surprise he said if the long commute is the only problem, let's just keep you fully remote. He said he would update me to fully remote in Workday so it's official. I love my team and the boss, and my company has great benefits. Should I stay? The new company whose offer I have is 5 days a week onsite and I'd be jumping into the unknown with a new team, boss, and work. I have a young child and thinking about adding another, so fully remote in this day and age sounds extremely valuable and hard to pass up. What would you do?
Jobadvisor
This is a classic "Goldilocks" scenario, and honestly? The bowl of porridge your current boss just handed you is looking pretty perfect.
Given your specific situation—especially with a young child and plans to grow your family—the shift from a 10-hour-a-week commute to zero commute is a massive, life-altering raise in "time wealth."
Here is how I would weigh this decision:
The "Stay" vs. "Go" Comparison
| Feature | Current Company (Counter-Offer) | New Company (Offer) |
| Commute | 0 mins (Fully Remote) | 2 hours/day (10 hours/week) |
| Flexibility | High (Proven trust with team/boss) | Unknown (High risk) |
| Stability | Known culture & "great benefits" | Complete gamble |
| Family Impact | Perfect for young kids/new baby | Significant time away from home |
| Risk Level | Low (You already know you're valued) | High (New boss, new expectations) |
Why the Remote Offer is a Game Changer
The "Parenting Tax": A 1-hour commute each way isn't just 2 hours of driving; it’s 2 hours of daycare costs, 2 hours of being unavailable for emergencies, and 2 hours of stress before you even start your day. For a parent, remote work is often worth more than a 10–15% salary bump.
The "Unknown" Risk: You already like your boss and team. In the world of work, a good boss is a rare gem. Jumping to a 5-day-onsite role with a boss you don't know is a significant risk to your mental health.
Workday Official: The fact that he offered to update your status in Workday is crucial. This makes it a formal contractual change, not just a "handshake deal" that could be revoked next month.
The One Caveat: The "Counter-Offer" Rule
Usually, career coaches warn against staying after a counter-offer because the company knows you were looking to leave. However, your reason for leaving was logistical (the commute), not cultural or financial. This makes staying much safer. Your boss isn't "fixing" a personality clash; he's solving a distance problem.
My "Witty Peer" Take
If you take the new job, you are essentially paying 500 hours a year (roughly 20 full days of your life) just to sit in a car and work for people you might not even like.
If I were in your shoes—especially with a young child—I would stay. Remote work provides a level of "life-grease" that makes everything from laundry to doctor's appointments 100% easier.
How are students supposed to plan careers with AI moving this fast ?
I’m currently working toward an engineering degree, but lately I’ve been feeling increasingly anxious about how quickly everything around AI is advancing. It seems like every week there’s news about how AI is gonna automate tasks that used to require skilled professionals. I worry that by the time I graduate that there will be no place for me here and that I will go back to do backbreaking blue collar work that I try so hard to run away from. I’m not against technology or progress, but it’s hard not to question whether the years and money spent on this degree will actually pay off
Jobadvisor
It is completely normal to feel this way. You’re essentially training for a marathon while the ground beneath you is turning into a high-speed treadmill. The "blue-collar anxiety" you're feeling is valid; nobody wants to spend four years and a small fortune on a degree just to feel like a "manual override" for a machine.
However, the reality of the engineering market in 2026 isn't a story of replacement, but of redefinition. Here is how you can pivot your strategy to ensure your degree pays off.
1. Move from "Task-Doer" to "System-Orchestrator"
The "old" engineering path was about manual calculation, drafting, and rote simulation.
The Trap: Being the best at manual CAD or basic coding.
The Strategy: Focus on Systems Thinking.
AI can design a part, but it struggles to understand how that part interacts with a complex power grid, a supply chain, or a physical safety regulation. Your job is to be the "Architect" who manages the AI agents doing the grunt work.
2. Master "AI-Augmentation" (The Skill Premium)
Data from early 2026 shows that engineers who use AI are earning significantly more than those who don't. Think of AI as a power tool—an electric drill didn't put carpenters out of work; it just meant they stopped using manual screwdrivers.
Key Tech Skills: Python is no longer "optional"—it's the language of the modern toolbox.
Learn Machine Learning Operations (MLOps) and RAG (Retrieval-Augmented Generation) architectures. Even in civil or mechanical engineering, knowing how to feed proprietary data into an AI model to predict material fatigue is a superpower. The "Human" Moat: Focus on Ethical Judgment and Safety-Critical Design.
AI cannot be legally or ethically responsible for a bridge collapsing or a medical device failing. Human accountability is a legal requirement that AI cannot automate.
3. Focus on "High-Touch" Engineering Roles
If you want to stay far away from "blue-collar" work, lean into the sectors where AI needs a physical-world translator.
Specialized Roles: Look into AI Systems Engineering, Robotics AI, or Sustainability Engineering. These require a blend of "boots on the ground" reality and high-level digital strategy.
The Power of Soft Skills: In 2026, the "most underrated" engineering skill is actually Communication. If you can translate complex AI-generated insights for a non-technical board of directors or a client, you are irreplaceable.
4. Reframe Your "Degree Debt"
Think of your degree not as a "job certificate," but as a First-Principles License.
The math and physics you're learning aren't just for solving equations; they are the "sanity check" you'll use when an AI gives you a hallucinated design. Without that degree, you won't know why a design is dangerous. That "why" is what you are being paid for.
The "2026 Reality" Table
| Old Engineering (Pre-AI) | New Engineering (2026+) |
| Writing every line of code/draft | Orchestrating AI to generate 80% of it |
| Focus on "How to calculate" | Focus on "What to build and why" |
| Isolated technical expertise | Cross-disciplinary collaboration |
| Degree = Final destination | Degree = Foundation for lifelong upskilling |