About Living in a Bubble Living in a Bubble (LIAB) is a premium, fast-growing DTC brand building thoughtfully designed campervan and RV accessories for a global community of van-lifers and adventurers.
We sell through our own Shopify store and Amazon across Australia, the United States, Canada, and Germany.
We’re a small, senior, fully distributed team with a builder culture: we value judgment over hours and ownership over supervision.
Our customers make considered, high-intent purchases — so our store rewards rigour and sharp thinking, not experimentation for its own sake.
The Role We’re hiring a senior CRO specialist to own our experimentation program end to end — audit, roadmap, test design, execution oversight, and reporting — working hand in hand with our Shopify developer.
This is a hands-on-strategy role for an autonomous operator .
You’ll set the roadmap, make the sequencing calls, and run the program without day-to-day management.
We want the person who brings the discipline — not one who waits to be told what to test next.
One honest framing before you apply: we sell premium, high-consideration products, so our conversion rates run structurally lower than the general-ecommerce average — and that’s expected, not a problem to be embarrassed about.
We measure success against our own trailing baseline, and we value correct, well-powered test calls (including honest “inconclusive” results) over a high count of shipped tests.
What You’ll Do • Run full-funnel data, UX, and conversion audits using GA4, Shopify Analytics, session recordings/heatmaps, and Core Web Vitals reporting.
• Build and continuously refresh a prioritised, 90-day experimentation and A/B testing roadmap as results land.
• Write clear, unambiguous technical briefs and wireframes for our Shopify developer — specific enough to build from with zero strategic interpretation required.
• Own the test cadence end to end: brief the developer, QA the build against your brief, and call each test won, lost, or inconclusive with statistical discipline.
• Report monthly on conversion rate, AOV, and ROI impact of implemented changes, with clear recommendations.
• Make the sequencing judgment calls — which leak (product page, cart-add, or checkout) is the higher-leverage target — without needing day-to-day direction.
What Success Looks Like • Week 1: establish our true trailing-90-day baseline across the funnel — this is your first deliverable and the yardstick everything else is measured against.
• By Month 6: a measured, statistically validated relative lift in conversion rate over that agreed baseline, reported on a trailing basis so no single month decides it.
• Cart-add and checkout: measurable improvement toward benchmark on priority product and collection pages, and on checkout completion, each validated before rollout.
• A working testing engine: a documented pipeline running one purchase-level CVR test at a time (typically 4–8 weeks each, given our traffic) plus one to two faster upper-funnel tests per month — each with a pre-registered hypothesis, a sample-size/MDE calculation, and a significance-stated call.
Hours & Work Arrangement The work is front-loaded.
Early on we need more hours to diagnose what’s underperforming and capture quick wins; as the program matures it moves to a lighter, consultancy cadence.
• Month 1 — Audit & Quick Wins: 15–20 hrs/week.
Full data and GA4 review, funnel and checkout drop-off diagnosis, quick-win briefs to the developer, 90-day roadmap build, baseline locked.
• Months 2–4 — Ramp-up: 10–15 hrs/week.
Test design and QA, weekly developer briefings, results analysis, monthly CVR/AOV/ROI reporting, roadmap refresh.
• Month 5 onward — Ongoing consultancy: 8–12 hrs/week.
Maintain the test backlog, protect statistical rigour, periodic re-audits, and knowledge transfer.
Remote and async-first.
Some overlap with Asia-Pacific business hours for reviews and briefings is helpful, but you won’t need to be online all day.
This is a non-exclusive contract — we assume a senior operator brings other work, and we respect it, provided LIAB gets your full focus during agreed hours.
Working Arrangement Contract, remote • ~5 years in ecommerce conversion optimisation or growth strategy, with direct, verifiable experience scaling Shopify or Shopify Plus stores.
• A proven, quantified track record — you can point to specific before/after CVR and AOV numbers from past engagements, not just activity descriptions.
• Fluency in GA4, Shopify Analytics, a heatmap/session-replay tool (Hotjar, Microsoft Clarity, or similar), and a Shopify-compatible experimentation platform (Intelligems, VWO, Convert, or similar).
• Working command of statistical testing fundamentals — sample sizing, minimum detectable effect, and run-time discipline.
• Comfortable directing a developer with strong technical literacy.
• Excellent written English — your briefs go straight to a non-CRO developer and must be actionable with zero ambiguity.
• Able to operate autonomously against KPIs and set your own roadmap; this role is not closely managed day to day.
Nice to Have • Direct DTC physical-goods experience.
• Automotive, vehicle-accessory, or fitment-driven catalogue experience — a strong plus given our product range.
What We’re Not Looking For • Agencies who’d hand this to a junior while a senior name sits on the invoice — we’re hiring the person who does the work, not an account manager.
• Anyone whose answer to every problem is “run more tests.
” At our traffic, one well-powered test beats five sloppy ones.
• Strategy-only specialists who won’t write the actual developer briefs.
You own the brief, end to end.
• SEO or general-marketing generalists relabelling themselves as CRO.
• Anyone who needs day-to-day direction, or who comes undone when priorities shift.
Why This Role • Full ownership of the experimentation program — you set the roadmap and make the calls.
• Direct access to the founders: short lines, fast decisions, no layers to push through.
• A premium, high-intent store and a developer ready to build what you brief.
• A team that values honest calls over vanity metrics and won’t punish a well-run test for coming back inconclusive.
