Looking for work with a US company? Apply to the Rolemote talent roster — free →

At a glance

Highest score first. Scores within 2 points are level: when we had the screener read the same two applications again, the gap between them moved by up to 2. A must-have in the brief (below the list) costs 5 points when the application does not show it and 2 when it only partly does.

  1. Ximena O.Mexico · asking $1,300Goes on to the interviewLevel with Dominic T. (86 vs 85 is too close to call): stronger on the work sample (87 vs 84), Dominic T. on the scenario answer (88 vs 85).86/100
  2. Dominic T.Philippines · asking $1,150Goes on to the interviewAhead of Mylene C. mainly on the scenario answer (88 vs 66).85/100
  3. Mylene C.Philippines · asking $850Stops here69/100

2 of 3 clear 70, the score an applicant needs to go on to the written interview. A real shortlist only holds people who clear it and then the interview; the one below it is shown so you can see what the screener turns down.

The brief they were screened against

Role: Shopify Developer · Band: $800–1,350/mo

Must-haves: Liquid and Online Store 2.0 sections, customises a theme without breaking its updates, diagnoses before rebuilding, mobile performance on product pages

Nice to have: metafields and app integrations, reading Shopify and GA4 analytics, checkout extensibility

Scored on 2026-09-23 by the AI screener that grades real applicants: the shopify-developer rubric, run on claude-sonnet-4-6. Nothing below was edited afterwards — including where it went against a candidate. The rubric and weights are published.

Ximena O. · 1 of 3

SCREEN 86/100

Mexico · asking $1,300

How the 86 adds up · Top ~10%

A bar is as long as its part's weight; the filled share is the score out of 100.

  1. Graded work sample 35%87

    Block-in-/blocks, metaobject with per-SKU override, graceful empty state, VoiceOver, and a real A/B result with session count and lift figures.

  2. Scenario judgment 25%85

    Defines the metric first, segments by device/channel/product, checks tracking integrity, uses Clarity recordings, and proposes split-test over blind revert.

  3. Experience specificity 20%84

    Four years CRO-side agency, ~40 A/B tests, named tools across measurement and Shopify stack, two checkout UI extension builds on a Plus store.

  4. Written & spoken English 15%82

    Consistently clear and direct; 'Recordings usually show in an hour what the numbers take a week to say' is precise and client-ready.

  5. Salary-band fit 5%100

    Asks $1,300 a month, inside the $800–1,350 band.

Must-haves in the brief: 4 of 4 shown

  • Liquid and Online Store 2.0 sections — shownLiquid, Online Store 2.0 sections, blocks and theme blocks
  • customises a theme without breaking its updates — shownNo existing theme file was edited, so there is nothing for a vendor update to clash with.
  • diagnoses before rebuilding — shownI'd tell the client I understand wanting the old version back, and that they'll have a yes or no within two working days, with the numbers behind it.
  • mobile performance on product pages — shownwatch 30 to 40 recorded mobile sessions in Microsoft Clarity on the new version

The parts, weighted as above, come to 86.

Screening notes

Strongest: Work sample is fully realised — architecture, content-management design, edge-case handling, accessibility, and a live A/B result with hard numbers.

Concern: JavaScript described as "comfortable, not my strongest"; depth there is untested.

Worth asking: How they handle theme-update conflicts when a vendor does change a section they've extended, and what their JS limit looks like in practice.

Verdict: A well-evidenced, conversion-focused Shopify developer whose ask sits near the top of the band but within it.

Experience

4 years as a Shopify developer at a Mexico City e-commerce agency, on the CRO side: US and Mexican DTC brands in beauty, pet food and coffee subscriptions. I build the product-page changes and I also set up the measurement — GA4, Shopify's customer events, and the tests. I've run about 40 A/B tests on product pages. The one I'm proudest of moved delivery and returns information from a tab to under the add-to-cart button for a US pet-food brand: add-to-cart rate up 11% over three weeks and about 48,000 sessions.

Tools

Liquid, Online Store 2.0 sections, blocks and theme blocks, Shopify CLI, metafields and metaobjects, GA4 and Google Tag Manager, Shopify customer events (custom pixels), Shopify Analytics, Looker Studio, Microsoft Clarity, Shoplift, checkout UI extensions (two builds on a Plus store), JavaScript (comfortable, not my strongest)

Scenario answer

Asked: A Shopify store's product-page conversion rate dropped 25% after a theme update last week. The client wants to revert to the old version. Before you do anything, walk through how you'd diagnose what actually changed — and what you'd recommend after your investigation.

I'd tell the client I understand wanting the old version back, and that they'll have a yes or no within two working days, with the numbers behind it. First I make sure we're measuring the same thing. 'Product-page conversion' can mean three different numbers, so I define it as sessions that viewed a product and added to cart, and pull it from both Shopify and GA4 for the 14 days before and after the update. If Shopify shows the drop and GA4 doesn't, or the other way round, I look at tracking first: if the store's add_to_cart event is pushed from theme code, an update can drop it. Then I segment, because a real theme problem rarely hits everyone equally: - mobile vs desktop - paid social vs email vs organic - new vs returning visitors - the top 10 products one by one. If the drop sits on products with many variants, I look at the variant picker; if it sits on products with lots of reviews, I check the reviews block survived the update. In parallel I compare the two versions: the vendor's release notes first, then the product template and main product section side by side, in the theme editor and in code. And I watch 30 to 40 recorded mobile sessions in Microsoft Clarity on the new version, looking for dead clicks and rage clicks around the picker and the button. Recordings usually show in an hour what the numbers take a week to say. On speed, I'd run PageSpeed Insights on both versions, but in my experience a few hundred milliseconds rarely explains a 25% drop by itself. A missing or moved element usually does. Then my recommendation. If I find a specific cause, fix it in the new version and keep the update. If the drop is real and I can't find a cause, I'd split-test old against new for two weeks instead of reverting on one week of data that might be noise — Shopify's Rollouts can run an experiment between two themes if the store has access to it; otherwise Shoplift. Reverting for good also means the next update becomes a bigger jump.

Work sample

Asked: Describe a Liquid template change or custom section you've built: what did the brief ask for, what approach did you take, and what did you test before calling it done?

BRIEF A US pet-food brand, subscription-first. Customers kept emailing to ask when an order would arrive and whether they could return an opened bag. The answers existed — in a 'Shipping' tab under the description, which on mobile sat three screens below the add-to-cart button. The ask: put delivery and returns information where people decide, and let the team change it without a developer. APPROACH - One block, 'Delivery and returns', directly under the add-to-cart button. Their theme's product section accepts theme blocks, so it lives in its own file in /blocks. No existing theme file was edited, so there is nothing for a vendor update to clash with. - The content comes from a metaobject, 'Delivery promise', with three fields: the dispatch cut-off ('Orders placed by 2pm ET ship the same business day'), the delivery range in days, and a one-line returns promise. The team edits it once and it changes on every product. - A product metafield can override it, for the two heavy SKUs that ship by freight. - Plain text, no accordion. The whole point was that people see it without tapping anything. WHAT I TESTED - A normal product, a freight product with the override, and a product with nothing assigned: the block hides itself instead of showing empty labels. - The theme editor: the team can move, hide and restyle the block without code. - VoiceOver on iPhone reads it in order, straight after the button. - Then a real A/B test before I called it done: three weeks, about 48,000 product-page sessions split 50/50. Add-to-cart rate went from 7.1% to 7.9%, and 'where is my order' emails dropped by about a third. The client kept it.

Availability

Full-time, 8am–5pm Mexico City time — the whole US Central working day and most of Eastern's. Three weeks' notice.

↑ All 3 at a glanceNext: Dominic T. ↓

Dominic T. · 2 of 3

SCREEN 85/100

Philippines · asking $1,150

How the 85 adds up · Top ~10%

A bar is as long as its part's weight; the filled share is the score out of 100.

  1. Graded work sample 35%84

    Metaobject-driven size chart, native dialog, 20-line JS, accessibility tested, LCP unchanged, returns dropped from 14% to 9% — specific and client-ready.

  2. Scenario judgment 25%88

    Checks whether orders confirm the drop before touching anything, splits by device, diffs both theme copies in Git — precise sequencing with real tradeoffs.

  3. Experience specificity 20%82

    25 stores, 3 years agency DTC, LCP 4.6s to 2.2s, add-to-cart 5.8% to 6.9%, named tools throughout — numbers and decisions are specific.

  4. Written & spoken English 15%81

    Phrases like 'the number that can't lie — orders' and 'a week of data is a signal, not a verdict' show confident, client-appropriate register throughout.

  5. Salary-band fit 5%100

    Asks $1,150 a month, inside the $800–1,350 band.

Must-haves in the brief: 4 of 4 shown

  • Liquid and Online Store 2.0 sections — shownOnline Store 2.0: custom sections, metafield-driven product pages
  • customises a theme without breaking its updates — shownIt's listed in the repo README, so if a future theme update can't carry it over, putting it back is one block, not a rebuild
  • diagnoses before rebuilding — shownLet's not revert yet
  • mobile performance on product pages — showna US apparel brand's mobile product-page LCP went from 4.6s to 2.2s

The parts, weighted as above, come to 85.

Screening notes

Strongest: Scenario answer — orders-first logic, device split, Git diff of both theme copies — shows genuine diagnostic discipline.

Concern: Checkout extensibility is self-described as "one project, still learning"; depth there is thin.

Worth asking: How they handle a client who overrules the diagnosis and insists on reverting anyway.

Verdict: A well-evidenced, conversion-minded Shopify developer whose ask sits comfortably inside the band and whose work shows real production judgment.

Experience

5 years on Shopify, the last 3 at a Manila development agency building for US DTC brands — apparel, supplements and home goods, about 25 stores. Most of my work is Online Store 2.0: custom sections, metafield-driven product pages, and moving old vintage themes to JSON templates. Best result: a US apparel brand's mobile product-page LCP went from 4.6s to 2.2s after I replaced an autoplay hero video and removed two apps nobody used, and mobile add-to-cart rate went from 5.8% to 6.9% the following month.

Tools

Liquid, Shopify CLI and Theme Check, Shopify's GitHub integration for themes, Online Store 2.0 sections, blocks and app blocks, metafields and metaobjects, Shopify Analytics and the web performance reports, GA4, PageSpeed Insights, Chrome DevTools, Microsoft Clarity, Search & Discovery, Klaviyo and Judge.me (theming their app blocks), checkout UI extensions (one project, still learning)

Scenario answer

Asked: A Shopify store's product-page conversion rate dropped 25% after a theme update last week. The client wants to revert to the old version. Before you do anything, walk through how you'd diagnose what actually changed — and what you'd recommend after your investigation.

First, my reply to the client: 'Let's not revert yet. The old version is still in your themes list, unpublished, so going back is one click whenever we decide. Give me until tomorrow to find what changed — reverting blind throws away the update's fixes and teaches us nothing.' Then, in this order: 1. Is the drop real? Shopify's conversion rate breakdown for the 7 days after the update against the 7 before and the same week last month: sessions with cart additions, reached checkout, completed checkout. Then the number that can't lie — orders. If orders held and only the reported rate fell, tracking broke, not the store. A GA4 snippet pasted into theme.liquid years ago is exactly the kind of code edit that goes missing in an update. 2. Which step dropped? If add-to-cart held and checkout completion fell, the theme probably isn't the cause, because checkout doesn't run on the theme. I'd look at shipping rates, payment methods, an expired discount. 3. Split by device and traffic source. A theme problem usually shows on one device. A drop spread evenly across everything, starting the day a sale ended, isn't a theme problem. 4. Diff the two versions. shopify theme pull --theme <id> for both copies into one Git repo, then diff: templates/product.json, the main product section, the variant picker, the product JavaScript. I also check whether Shopify said 'code edits could not be included' when the update was added. If it did, anything a developer or an app had written into those files is gone. 5. Use the page like a customer, on a real phone. Is add-to-cart still above the fold? Did the picker change from buttons to a dropdown, or stop preselecting a variant? Are the review stars, size guide and payment messaging still there? 6. Speed. Shopify's web performance report for product pages on mobile — theme changes are marked on the chart — and PageSpeed Insights on both versions. What I'd recommend depends on what I find, but it's usually a fix, not a revert: put the missing snippet back as its own section, restore the picker behavior, repair the tracking. I'd only republish the old version as a stopgap if orders are really down and I can't find the cause within a day, and then port the fix into the new version rather than live on the old one. One caveat I'd say out loud: with a few hundred product-page sessions a week, 25% can be a dozen add-to-carts. A week of data is a signal, not a verdict.

Work sample

Asked: Describe a Liquid template change or custom section you've built: what did the brief ask for, what approach did you take, and what did you test before calling it done?

BRIEF A US swimwear brand, about 300 products, wanted a size chart on every product page — different for tops, bottoms and one-pieces — that their own team could edit. They had already picked a size-chart app. I tested it on a duplicate theme first: it added about 110KB of JavaScript to every page of the store, not just product pages, and their mobile product-page LCP was already 3.4s. So I proposed building it into the theme instead, with no monthly fee, and they agreed. APPROACH 1. Data first. A metaobject definition, 'Size chart': a name, a list of rows (each row its own small metaobject: size, bust, waist, hip, in inches and cm) and a fit note. Three entries — tops, bottoms, one-piece. Each product gets one metafield pointing at its chart. The team assigned all 300 products in an afternoon. 2. Markup in its own snippet, size-chart.liquid: a 'Size guide' link next to the size picker that opens a native <dialog> with a real HTML table. Not an image of a table, so it's readable on a phone and by a screen reader. 3. One small edit to a vendor file: a new block type in the main product section's schema that renders the snippet. It's listed in the repo README, so if a future theme update can't carry it over, putting it back is one block, not a rebuild. 4. No JavaScript library. The dialog needs about 20 lines to open and close, loaded on product pages only. WHAT I TESTED - A product of each chart type, a product with no chart (the link doesn't render) and a chart with an empty row. - A real iPhone and a mid-range Android, not just DevTools: the table scrolls sideways inside the dialog instead of widening the page. - Keyboard and VoiceOver: focus moves into the dialog, Escape closes it, focus returns to the link. - The theme editor: the block can be moved or hidden without code. - Theme Check clean, and PageSpeed Insights on mobile before and after: no change to LCP, because nothing loads until someone taps. - Then I asked the client to watch the number that mattered. Over the next two months, 'wrong size' exchanges went from about 14% of returns to 9%.

Availability

Full-time on US Eastern hours: 9pm–6am PHT, moving an hour later when the US goes back to standard time. Two weeks' notice.

↑ All 3 at a glanceNext: Mylene C. ↓

Mylene C. · 3 of 3

SCREEN 69/100

Philippines · asking $850

How the 69 adds up · Competent but generic

A bar is as long as its part's weight; the filled share is the score out of 100.

  1. Graded work sample 35%72

    Schema settings, CSS grid, JS slider, and cross-device testing described with real specifics; deployed on 5 product pages.

  2. Scenario judgment 25%66

    Sensible sequence: compare themes, check app blocks, test on device, ask about other changes; time-box before reverting is practical.

  3. Experience specificity 20%63

    60+ projects, 98% JSS, named tools and themes, but decisions and outcomes beyond client satisfaction are thin.

  4. Written & spoken English 15%78

    Consistently clear, correct, and professional; phrasing like 'protect the sales' is natural and client-ready throughout.

  5. Salary-band fit 5%100

    Asks $850 a month, inside the $800–1,350 band.

Must-haves in the brief: 3 of 4 shown, 1 partly

  • Liquid and Online Store 2.0 sections — shownI created a new section file, before-after.liquid, in the Sections folder. In the schema I added settings for the heading, two image pickers, a text box and the background color, plus a preset so the client can find it under 'Add section' in the theme editor
  • customises a theme without breaking its updates — partly shown (−2)If I find the problem, I would fix it in the new theme
  • diagnoses before rebuilding — shownbefore reverting I would try to find out what changed
  • mobile performance on product pages — shownI checked it on desktop, tablet and mobile in Chrome, and on my own iPhone

The parts, weighted as above, come to 71; must-haves not fully shown cost 2, so 69.

Screening notes

Strongest: Work sample shows real Liquid section construction — schema settings, CSS grid, JS slider, and multi-device testing with a concrete deployment outcome.

Concern: No evidence of update-safe customisation practices (e.g. avoiding direct theme file edits, using app blocks or overrides); must-have 2 is only partly covered.

Worth asking: How do they keep theme customisations intact across Shopify theme updates in practice?

Verdict: A capable junior-to-mid Shopify developer with solid fundamentals and clean English, sitting near the bottom of the pay band, but with a gap around update-safe workflow discipline.

Experience

3 years as a freelance Shopify developer, working through Upwork and with a small Cebu agency, mostly for small US and Australian stores. I set up and customize themes, edit Liquid and CSS, create custom sections, install and configure apps, and fix layout problems on mobile. I have completed more than 60 projects with a 98% Job Success Score. I am hardworking, a fast learner and I always make sure my clients are satisfied.

Tools

Shopify, Liquid, HTML, CSS, JavaScript (basic), Shopify theme editor, Dawn and other free themes, PageFly, GemPages, Klaviyo, Judge.me, Canva

Scenario answer

Asked: A Shopify store's product-page conversion rate dropped 25% after a theme update last week. The client wants to revert to the old version. Before you do anything, walk through how you'd diagnose what actually changed — and what you'd recommend after your investigation.

I understand the client is worried about losing sales, so I would act quickly. But before reverting I would try to find out what changed, because the new version may have important fixes and improvements. First, I would open the old theme and the new theme side by side in the theme editor and compare the product page: the layout, the sections and the blocks. I would check if any sections or app blocks are missing, like the reviews or the size chart, because sometimes apps need to be added again after a theme update. Then I would test the product page on my phone and on desktop to see if something is broken, like the variant selector, the add to cart button or the product images. I would also check the browser console for errors. I would also ask the client if they changed anything else last week, like prices, shipping rates or apps, because the drop might not be caused by the theme. If I find the problem, I would fix it in the new theme. If I cannot find it in one or two days, I would recommend going back to the old theme to protect the sales, and keep working on the new version in the background before publishing it again.

Work sample

Asked: Describe a Liquid template change or custom section you've built: what did the brief ask for, what approach did you take, and what did you test before calling it done?

BRIEF: A skincare client wanted a 'Before and after' section for the homepage and product pages, where they can upload two photos and a short text and change it themselves without a developer. APPROACH: I created a new section file, before-after.liquid, in the Sections folder. In the schema I added settings for the heading, two image pickers, a text box and the background color, plus a preset so the client can find it under 'Add section' in the theme editor. For the layout I used CSS grid: two columns on desktop and one column on mobile. I also added a small JavaScript slider so customers can drag to compare the two photos. WHAT I TESTED: I tested the section in the theme editor to make sure all the settings work and it can be added to any page. I checked it on desktop, tablet and mobile in Chrome, and on my own iPhone. I also tried it with different image sizes to make sure the layout does not break. The client was happy with the result and now uses it on 5 product pages.

Availability

Full-time, 9pm–6am PHT to cover US Eastern hours. Available immediately.

↑ All 3 at a glance

This is the artifact every search delivers

Post the role and the same screener runs on your real applicants — the questions arrive already written, and you read every finalist in full before any fee is due.

Post a role free Or have us run the search

The same screener, other roles

Sample shortlist: Shopify Developer | Rolemote