Data work โ analyst, analytics engineer, data scientist, data engineer โ is one of the most consistently async-friendly categories in tech. The deliverables are queries, dashboards, models, and pipelines, all of which are inherently artifact-based and reviewable asynchronously. The teams that do this work well have moved most of their planning into written briefs and most of their reviews into pull requests on shared analytical infrastructure. The teams that don't have a recognizable failure mode: every analysis becomes an ad-hoc Slack request that has to be answered "right now."
The roles on this page are filtered for data teams that have moved past the ad-hoc-Slack-request pattern. We look for explicit references to a request-intake process, for analytics-engineering practices like dbt or similar (a strong signal of structured async workflows), and for managers whose published thinking acknowledges the difference between deep analytical work and reactive support work.
Three role shapes work especially well for working parents. Senior IC analytics engineer at a company with mature data infrastructure โ your work is shipping models and transformations through a structured PR process, almost entirely async. Embedded analyst at a non-data team (marketing, product, finance) where you own a defined surface area, build the recurring reporting once, and then spend most of your time on deeper investigations of your own choosing. Contractor analytics work for early-stage companies that need a data foundation built but aren't yet ready for a full-time hire โ typically 15 to 25 hours per week per client.
What doesn't work as well: data scientist roles at companies where the work is heavily ML-experimentation-driven and tightly coupled to product launches (these have unpredictable real-time demands), business-intelligence roles that are primarily reactive ("can you pull this number for the board meeting tomorrow?"), and any data role at a company where the executive team is data-curious but not data-mature (you'll spend most of your time educating rather than analyzing, and the work will feel synchronous regardless of the stated culture).
For transitioning into data work from another field โ surprisingly common among parents on a career second act โ the most efficient on-ramp is the analytics-engineering specialty. The toolset (SQL, dbt, a basic Python or R, one BI tool) is teachable in 6 to 9 months of focused study, the work is in high demand, and the role itself is naturally async-friendly from day one. The barrier to entry is lower than you'd expect, and the long-term career trajectory is strong.
Compensation expectations: senior IC data roles at async-first companies in 2025 pay $130,000 to $220,000 full-time, pro-rated for part-time arrangements. Contractor analytics work typically bills at $90 to $200 per hour depending on the depth of the work. The fractional market for senior data leadership is also growing rapidly โ fractional Heads of Data and fractional Heads of Analytics are common at companies in the $5M to $30M ARR range and pay $5,000 to $12,000 per month per client.
Current matching listings
No exact matches right now.
The feeds refresh regularly. Browse the broader pool: all jobs, all schedule types, or our guides.