let polopan style you          ✦        complete outfits, personalised to your taste          ✦          download the free app now

Shopify App Engineer

Job Category: Engineering
Job Type: Full Time
Job Location: Remote

team: product (commerce, attribution, partnerships)

why this role exists

polopan sits before checkout.

if attribution is wrong, billing is wrong.
if billing is wrong, trust breaks.
if trust breaks, the product doesn’t exist.

this role exists to ensure that our shopify app – the surface area between polopan and merchant revenue – is:

  • correct
  • auditable
  • resilient to edge cases
  • boring in the best possible way

we care less about adding features, and more about never having to question whether a sale actually happened, who it should be attributed to, and whether we charged correctly.


what you’ll be responsible for

1. owning the shopify app end-to-end

  • maintain and evolve polopan’s shopify app in production
  • own app install, OAuth, permissions, and lifecycle
  • handle shopify api upgrades, deprecations, and policy changes
  • ensure the app behaves predictably across thousands of merchant configurations

this is not a “feature factory” role. this is platform ownership.


2. referral & attribution correctness

  • maintain referral link generation and tracking
  • ensure accurate order attribution across:
    • sessions
    • devices
    • delayed conversions
  • handle refunds, partial refunds, cancellations, and edge cases without ambiguity
  • make attribution explainable — not just “it works most of the time”

if attribution is ever questioned, the system has already failed.


3. billing & commission reliability

  • own commission calculation and billing logic
  • ensure shopify billing apis are used correctly and conservatively
  • make every charge defensible to a merchant
  • build systems where:
    • under-charging is visible
    • over-charging is impossible

4. webhook hygiene & failure handling

  • design and maintain webhook systems that:
    • don’t silently fail
    • are idempotent
    • are easy to replay and debug
  • handle uninstall, reinstall, and permission changes cleanly
  • make failures obvious early, not months later in revenue reconciliation

5. setting standards early

  • define how shopify-facing code should be written, logged, and tested
  • document why decisions exist, not just what they do
  • push back on:
    • over-engineering
    • “we’ll fix it later” thinking
  • leave the shopify surface area cleaner than you found it

what we care about (more than speed)

we don’t measure this role by:

  • features shipped
  • PRs merged
  • velocity charts

we measure it by:

  • how rarely attribution or billing needs explanation
  • how confidently finance, product, and partners trust the system
  • how boring revenue operations become over time

deadlines will exist — not to rush you, but to force clear decisions.


what we’re looking for

you’ll likely resonate if you:

  • have built and shipped shopify apps in production
  • understand shopify’s apis, webhooks, and billing model deeply
  • are allergic to silent failures
  • care about correctness more than clever abstractions
  • think in edge cases before they show up in production
  • prefer owning a surface area fully rather than touching many lightly

experience that helps (not all required)

  • building and maintaining Shopify apps at scale
  • consuming shopify webhooks appropriately
  • working with referral tracking, attribution, or affiliate systems
  • handling payment, billing, or revenue-adjacent logic
  • debugging issues that only show up weeks later
  • comfort with understanding backend systems (Node / Python / similar)

tech stack matters less than judgment. shopify app development fluency matters a lot.


what this role is not

  • not a generic full-stack role
  • not frontend-heavy
  • not growth engineering
  • not “ship fast, fix later”

this is foundational commerce infrastructure.
what you build here determines whether polopan can scale partnerships at all.


how success looks (first 90 days)

  • shopify app runs without surprises
  • attribution logic is explainable and trusted
  • billing feels boring and defensible
  • edge cases are documented, not feared
  • parts of the system become confidently “done”

final note

we’re building polopan deliberately.

if you care more about trust than speed, about doing things once instead of often,
and about owning revenue-adjacent systems properly, you’ll feel at home here.

Apply for this position

Allowed Type(s): .pdf