Most "remote work" job-search advice was written for fully-remote, fully-time office refugees. It does not work well for parents trying to fit a job inside a 9-to-2:30 school window, because the keywords those parents need ("part-time," "school hours," "core hours") return mostly the wrong results. Here's the search strategy that actually works.
Step one: ignore the keyword "flexible." Every remote job lists itself as flexible. The word has been emptied out. Filter for it and you'll get tens of thousands of results, 95% of which require core hours. Search instead for phrases that imply structural async-ness: "no required meetings," "written-first," "fully asynchronous," "results-based culture," "no daily standups," "pacific time not required."
Step two: search for time-zone math, not for schedule words. If you live in the US Eastern time zone and want to work 9 to 2:30, you want jobs based in the UK or continental Europe. Their workday ends around the time your school day ends, and your morning lines up with their afternoon. Search for "remote, UK-based" or "remote, EMEA" and filter for companies open to North American hires. The reverse works in California β Asia-Pacific companies often have evening overlap with morning California time.
Step three: search by hours-per-week explicitly. Many job boards now let you filter by "part-time" or by hour count. The trustworthy listings will mention an explicit hour cap in the description: "20 hours per week," "25 hours per week," "fractional, approximately 12 hours per week." If the description avoids any number, the role is full-time even if it's tagged as part-time. Read the actual description, not the tags.
Step four: filter by company size. Small companies (10 to 50 employees) and very large companies (5,000+) tend to have the most flexibility around hours. Mid-size companies (200 to 1,500) are usually the most rigid because they've added enough process to enforce schedules but not enough scale to need true async culture. The math is empirical, not theoretical: if you're cold-applying, prioritize small startups and large enterprises, deprioritize the middle.
Step five: read the company's engineering blog or team handbook. Many async-first companies publish their internal handbook publicly (GitLab, Buffer, Doist, and many others). If you can find a company's handbook and it explicitly addresses meeting culture, async expectations, and time-zone overlap, you've found the rare thing β a company whose stated culture is actually their culture. Apply to those first. Their job listings are sometimes scarce, but the hit rate is dramatically higher.
Step six: when you interview, ask one specific question. "Walk me through what the person currently in this role does on a typical Tuesday between 2:30 PM and 5:30 PM their local time." If the answer involves meetings, the role is not school-hours-compatible. If the answer is "they're usually offline by mid-afternoon and we don't expect coverage" β you've found one.
Current matching listings
Staff Data Analyst, Product
Senior Staff Product Marketing Manager, AI
Head of Graphic Design
Intern - Marketing Design
Product Owner
Product Specialist
Senior Product Engineer
Senior Product Designer
Director of Conversion Rate Optimization
Entry Level Crypto Market Specialist
Senior Product Designer
Senior Product Marketing Manager
Product Counsel
Senior Product Manager
Product Designer
Manager, Customer Support
Senior DevOps Engineer
Founding Engineer
Sales Development Representative North America June Hiring Class
Senior DevOps Engineer
Full Stack Software Developer 80-100% (f/m/x)
Video Content Strategist / Storyboards