次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 14,171

← 検索結果に戻る

CRO & UX Analyst

HireGummy

リモート勤務

勤務地
Remote (Pakistan)
勤務時間
Full Time
掲載日
2026年10月15日

応募する前に、企業のウェブサイトで現在も募集中かどうかと詳しい条件を確認してください。

仕事内容

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

CRO & UX Analyst Location: Remote Employment Type: Full-Time Experience: 5+ Years Schedule: Must be available for overlap with Sydney hours, including availability from 2:00 PM AESTWhy this role matters We're hiring someone to help take our client to the next level. This is not a freelance or contract role. You'll be all in with our team and our clients from day one. We want a motivated person who lifts the team and inspires our clients. You have a can-do attitude. You believe every data problem can be solved, and you keep going until it is. The role You'll find out what users do once they land on a client's site, and why they don't convert. You'll spend most of your day in GA4 and behavioural tools like Hotjar, Contentsquare, FullStory or Microsoft Clarity. You'll also step back to spot trends and patterns, and explain what they mean for the client's business. You'll work closely with our senior CRO and CRO team. Here's a typical task. A client's conversion rate dropped 15% last month. You work out which channel, device and landing page drove the drop. You check the ratios behind it, such as add-to-cart and checkout completion rates. Then you watch session recordings and heatmaps to see what users did. Then you write up the likely cause, what it's costing the client, and what to test. If the numbers look wrong, you check for a tracking issue first. This role is not We've had many applicants from adjacent fields. They're good backgrounds, but they're not this job. This role is not: A tracking or tag setup role. Our developers handle implementation. An A/B test build or development role. You'll analyse test results, but you won't build the tests. A UX or UI design role. A campaign, SEO, PPC or media reporting role. We care about what users do on the site, not how they got there. A data science role. Python, SQL and BigQuery aren't required. If you have them, tell us how they'd add to the skills below, not replace them What you'll do GA4 analysis (the core of the role) Build custom reports and explorations in GA4 to answer specific client questions. Build funnel and path explorations to find where users drop off. Create segments and comparisons, such as new vs returning, device, channel or landing page. Find which pages, sources or user groups explain a change in conversion rate. Business-level analysis Spot trends and patterns over time, such as week-on-week, year-on-year and seasonal shifts. Work with ratios, not just totals. For example: conversion rate, average order value, revenue per user, add-to-cart rate, and cart-to-checkout and checkout completion rates. Tell a real change apart from noise or a shift in traffic mix. Link site metrics to business outcomes like revenue, leads and lead quality. Size opportunities. For example, what a 1% lift in checkout completion is worth to the client per year. A/B test results and post-test analysis This is critical to our business. We need to know why a test won or lost, not just that it did. Analyse A/B test results and report them clearly, including confidence and sample size. Break results down by segment, such as device, new vs returning, channel and landing page. Dig into secondary metrics and funnel steps to explain what changed in user behaviour. Use recordings and heatmaps of each variant to show why it won or lost. Turn the findings into clear next steps and new test ideas. Behavioural and UX analysis Review session recordings, heatmaps and scroll maps to see what users actually do. Run heuristic reviews of client sites and funnels to spot likely conversion blockers. Check findings across GA4, behavioural tools and heuristics. Don't rely on one source. Data quality Spot when data looks wrong, such as missing events, duplicates, thresholding or sampling. Work out whether it's a tracking issue. Brief our developers clearly so they can fix it. You won't do the fix yourself. AI and automation Use AI tools to automate repeat work, such as reporting, data pulls and write-up drafts. Use AI for basic data analysis, such as summarising exports, spotting outliers and first-pass trend checks. Check every AI output before it's used. You own the accuracy, not the tool. Look for new ways AI can speed up how we work. Communication Explain findings in plain English to the team and to clients. Present and defend your own ideas live, on calls and in meetings. Say so, politely, when you disagree. Say "I'm not sure yet" when that's the truth. Then go and find the answer. Double-check your findings before you share them. Produce clear, well-structured write-ups. What we're looking for Skills 5+ years working in the GA4 interface (or Universal Analytics before it) to answer conversion questions. Strong skills building custom reports, explorations and segments in GA4. Proven experience analysing A/B test results and explaining why tests won or lost. Strong business sense. You're comfortable with trends, ratios and commercial metrics, and can explain what they mean for revenue. Regular hands-on use of at least one behavioural tool: Hotjar, Contentsquare, FullStory or Microsoft Clarity. Advanced use of AI tools for automation, reporting and basic data analysis, with a habit of checking the output. Enough tracking knowledge to tell when data is wrong and explain the problem to a developer. Strong written and spoken English. Attitude A curious mindset. You keep digging until you find the real answer, not the first plausible one. A can-do attitude. No data problem is too hard for you. You want to be part of a team long term and help it grow. Confidence to share your own ideas, disagree politely, and admit when you don't know yet. A habit of double-checking your work before you share it. Nice-to-haves A tracking or tagging background, such as Google Tag Manager. Useful for debugging, but not what the role is about. Python, SQL or BigQuery skills, if you can show how they'd strengthen the GA4 and behavioural work above. Certifications in Contentsquare, Hotjar, FullStory or similar tools. CRO agency experience great to have but not necessary. Logistics Full time, permanent. Not a freelance or contract role. Based locally or remote. If remote, you must be online by 2pm AEST/AEDT to overlap with our Sydney team. How to apply Please answer these seven questions in a loom video or something similar. Short, specific answers are best. A client's checkout conversion rate fell 20% in two weeks. List the first five things you'd check in GA4 and your behavioural tools, in order, and why. A client's sessions are up 30% year on year, but revenue is flat. Which ratios would you look at first, and what would each tell you? An A/B test on a product page finished flat overall. How would you work out what actually happened, and what would you recommend next? Describe a time something didn't look right in the data. How did you find the cause, and how did it get fixed? Describe a custom report or exploration you built in GA4. What question did it answer, and what did you find? Describe a time you found something unexpected by combining GA4 with a behavioural tool. How did you investigate it, and what did you recommend? Describe one way you use AI in your analysis or reporting work. How do you check its output? Originally posted on Himalayas

検索して比較し、応募を準備しましょう

次の仕事で活かしたい職種やスキルから検索を始めましょう。勤務地と職種の条件を調整し、求人を開いて担当業務を比較してください。結果がない場合は、短い検索語を試すか、条件を一つずつ外してみましょう。

必須条件と歓迎条件を分けて確認し、勤務時間、報酬、勤務地が掲載されている場合は目を通しましょう。リモート勤務でも、居住国、就労資格、勤務時間帯が指定されることがあります。現在の募集状況と詳しい条件は企業に確認してください。

募集要件に関連する実際の経験を選び、自分の役割と貢献を説明しましょう。数値は根拠がある場合にのみ使ってください。企業の応募方法に従い、送信前に連絡先、内容、PDFの表示を確認しましょう。

応募前の確認リスト

仕事探しに関するよくある質問

英語の求人が表示されるのはなぜですか?

職種名や説明文は企業が作成したものです。条件や要件を変えないように原文を掲載しています。操作画面とこのガイドは日本語です。日本語の検索で見つからない場合は、「software engineer」のように、掲載言語の職種名やスキル名でも検索してみてください。検索語が自動翻訳されるわけではありません。

リモート求人なら、どの国からでも働けますか?

必ずしもそうではありません。居住国、就労資格、勤務時間帯が指定されている場合があります。元の求人ページで条件を確認してください。記載がない場合は、自分の居住地から応募できると判断する前に企業へ確認しましょう。リモートという表示だけでは、勤務地の制限がないことは分かりません。

検索結果が出ない場合はどうすればよいですか?

より一般的な職種名や一つのスキルで検索し、条件を一つずつ外してみてください。同じような仕事でも企業によって呼び方が異なります。特定の求人が見つからなくなった場合は、企業の採用ページで求人番号を探しましょう。検索条件を広げても、終了した募集が再開するわけではありません。

ResumizeAIから応募が送信されますか?

応募ボタンは外部サイトを開きます。企業または採用サービスの案内に従い、そのサイトで送信を完了してください。ResumizeAIで応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。