f FlexCareers
Home › Q&A › How do I find async-first companies specifically?

How do I find async-first companies specifically?

Async-first companies advertise themselves with specific words and behaviors that are easy to spot once you know what to look for. The combined signal is reliable enough that you can build a shortlist of 30-40 employers in an evening, then watch their careers pages for openings.

Three search strategies that work. First, search for company-name combinations with the phrase "async-first" or "asynchronous communication" plus your target role. Companies that mean it tend to use the phrase repeatedly across their handbook, blog, and listings. Second, look at lists of companies known for remote engineering or remote product work — GitLab, Doist, Automattic, Buffer, Zapier, Basecamp, Help Scout, Tuple, Levels, and the broader "remote-OK" reading lists. Many have published their internal handbooks publicly, which lets you read exactly how decisions get made before you even apply. Third, search for "company-name handbook" — companies that publish their handbook are almost always serious about async, because writing things down is the foundational async behavior.

The handbook signal is the most reliable. A public handbook means the company has invested in writing decisions down, has standardized how teams communicate, and has made the implicit explicit. All three are necessary for async-first to be real. Companies without a public handbook can still be async-first, but you have less to verify against.

Beyond the handbook, watch for these patterns on the careers page: explicit mention of working hours flexibility, no required overlap windows or only narrow ones (one to three hours of overlap), parental leave policies described in writing with specific durations, location-flexibility ("hire from anywhere we can legally employ"), and an emphasis on outcome-based rather than hour-based work measurement. Companies that mention all of these tend to mean them; companies that mention one in passing usually don't.

Read the team blog if there is one. Long, multi-author technical and product blogs are a strong async signal — they require writing as a habit, which means writing is woven into how the team actually works. A team blog with one author posting once a quarter signals the opposite.

One specific tactic: find people who currently work at a candidate company and ask them how decisions get made. Twitter, LinkedIn, and remote-work Slack communities are full of employees willing to answer. Ask: "How does your team document decisions?" and "What's a typical Wednesday like?" The honest answers from current employees are far more reliable than the careers page.

Finally, beware of the asymmetric signal. Many companies adopted async language during the 2020-2022 remote wave and have since drifted back to sync defaults without updating their public materials. The careers page may say "async-first" while the actual culture has 35 hours a week of meetings. The way to catch this is to look at the company's public presence in the last 12 months — recent blog posts, recent open positions, recent commentary from employees. If the public material is older than the cultural drift, you'll be misled. Recent signals are the only reliable ones.

More questions