I Got Hired Remotely — Then Fired 90 Days Later. Here's What I Completely Missed.

The Call I Didn't See Coming

Three months into my first fully remote role, I got a call from HR on a Thursday afternoon. By Friday I was clearing out my digital desk.

The official reason: "Performance not meeting expectations in the probation period." The real reason — which I only understood six months later — was that I had never actually onboarded. I had completed the paperwork onboarding. The Slack introductions. The first-week calls. But I had never onboarded into the culture, the unwritten rules, or the political landscape of that team.

The Warning Signs I Walked Past

My manager only communicated via async Slack. I took that as "he's busy and trusts me." It was actually: "he has checked out and is not invested in your success."

Team meetings went quiet whenever I offered ideas. I assumed this was their communication style. It was actually: "you are not reading the room."

I was producing work but not asking for feedback. In an office, someone eventually pulls you aside. Remote, they just note it in a file. By week 6 I had a pattern of "misses" on my record that I didn't know existed. By week 10 the decision had been made. I just hadn't been told yet.

What I Now Do in the First 30 Days of Any Remote Role

• Request an explicit 30/60/90 day plan with measurable expectations — in writing
• Schedule a bi-weekly 1:1 and ask directly: "What would make this a clear success?"
• Over-communicate deliverables: send a weekly update nobody asked for
• Watch for the absence of feedback — that is itself feedback

In a remote role, the first 90 days require twice the communication you think is normal. Not because you're less capable — because you're invisible by default. Remote work punishes silence. In an office, people see you working. Remote, they only see your outputs and your communication.