Remote Work’s Next Big Problems Aren’t About Location

The first time I stumbled on Remote OK, it felt like a revelation. A single feed aggregating every remote job from dozens of boards. No more hunting through “remote” keyword searches on generic sites. Pieter Levels had built a simple aggregator that hit #1 on Product Hunt and racked up nearly 100,000 visitors in a month. His post about the build is a classic indie hacker case study: rapid MVP, clever engineering, and a splashy launch.

But that was 2015. Nearly a decade later, the remote work landscape has shifted. Job discovery—the problem Levels tackled—is largely solved. Indeed, We Work Remotely, and a dozen niche boards make it easy to find remote roles. Yet our platform tracks a surge of new problems: 47 in remote job discovery alone (avg severity 3.8/5), but also 63% of remote work problems are now about communication, productivity, and work-life balance—not location. The next wave of opportunities lies in the messy middle after the job is landed.

Levels correctly identified that “major job boards are not embracing remote work” and that consolidation was needed. Our data reinforces his point: the top industries for remote job discovery problems are still Tech (21 problems), Marketing (9), and Customer Support (7). But the has shifted. In the last six months, we’ve seen a 22% increase in app ideas around remote work tools, with 14 new problem entries solely in the last quarter. And these aren’t about finding jobs—they’re about what happens next.

Take onboarding. A new remote hire gets a laptop shipped to them, a Slack invite, and a week of Zoom calls. But how do they really integrate into a team they’ve never met? Our platform shows 12 problems specifically about remote hiring and onboarding, with an average severity of 4.2/5. Employers struggle with time zone coordination, cultural fit, and building trust without in-person interaction. That’s a market gap Levels didn’t address because, in 2015, remote work was still a niche of nomads. Now it’s mainstream, and companies need tools to make it sustainable.

Then there’s the industry expansion. Levels focused on tech roles, which dominated remote work then. But our data reveals remote work problems across 74 industries. Healthcare (18 problems, avg severity 3.6/5), Education (9 problems, avg severity 3.7/5), and Manufacturing (7 problems, avg severity 3.9/5) are all underserved. A nurse looking for a telehealth job or a factory manager overseeing remote teams faces different hurdles than a software developer. Builders who ignore these verticals are leaving money on the table.

Levels championed the nomadic lifestyle—the idea that remote work lets you move around the world. But our data challenges that narrative: only 12% of remote work problems are about “finding places to work.” The vast majority—63%—are about staying productive, communicating effectively, and maintaining boundaries. The romantic image of working from a beach fades when you’re struggling with Zoom fatigue or overlapping time zones. The real pain is operational, not geographical.

For indie hackers and vibe coders looking at this space, the lesson is clear: don’t build another job board. The low-hanging fruit is gone. Instead, look at the tools that support remote teams after the hire. Think automated onboarding checklists, async communication platforms, or culture-building games. Or go deep into a non-tech industry: a remote work platform for healthcare compliance or a productivity tracker for distributed manufacturing teams. Our data shows these areas are ripe for innovation.

Levels’ story remains inspiring—he built something people wanted, launched fast, and rode the wave. But the wave has moved. The builders who win next will address the problems Levels didn’t see, because they hadn’t emerged yet. They’re emerging now.