Wanted: Developer

Start date: As soon as possible
Job type: Contractor, full-time, project-based 
Location: 100% remote, Europe/US timezones preferred
Compensation: Competitive, in alignment with your experience

Paul Davids is one of the world’s most-loved online guitar content creators. His YouTube channel has nearly 4 million subscribers and over half a billion views, and his five courses have helped over 100,000 students get better at the guitar. Paul is now working on something new, and we are looking for a few brilliant new members to join our team.

The role:

We are looking for a second developer to join the team to work specifically under the marketing technologist and alongside the performance marketing team to build all funnel pages, and support the marketing technologist with tracking and reporting. 

This is going to be a fast-paced role. We’ll be testing lots of ads from the word go, so you need to be comfortable with fast turnarounds and multiple iterations. 

We’re still having conversations about the best tech stack, so you can also have an input there.

We have a lot of momentum, and you should also bring the energy. We have a lot to achieve, in a short amount of time. If you’re the right person for this role, that will excite you greatly.

About you:

  • You’ve shipped tracking for a real digital product launch at $1M+ scale. (SaaS-only or static-site-only backgrounds aren’t going to cut it here.)
  • You’ve rebuilt an attribution stack. You understand client vs server-side firing and why both matter post-iOS 14.5.
  • You’ve worked under a marketing technologist or growth lead. You can take a spec and ship; you don’t need hand-holding on the architecture side.

Your skills:

  • Server-side tracking implementation. Meta CAPI, Adtribute, GA4. Wiring server-side conversion events with proper event_id deduplication against client-side pixels.
  • Webhook orchestration. Building integration chains across SaaS platforms (Stripe → Skool → Kit → Adtribute). This is the spine of the launch.
  • Cloudflare Workers, or equivalent edge functions. Where the abandoned-cart, account-provisioning, and SMS-trigger logic lives.
  • Stripe API + webhooks. Payment flows, idempotency, failure modes.
  • WordPress collaboration. We have a main developer who owns the core WP work; you need to ship tracking without breaking it. 

You should be familiar with:

  • Meta Pixel + Conversions API
  • Adtribute (or you’ve used Hyros, Triple Whale, or Wicked Reports and can switch)
  • GA4 + GTM
  • Stripe (API, dashboard, webhooks)
  • Cloudflare Workers
  • WordPress (you should have enough PHP to read and patch existing themes)
  • Git and deployment workflows
  • Bonus: Skool API, SamCart, Kit (ConvertKit), Postscript or other SMS APIs, Node.js / TypeScript

To apply:

Send a short note to developer@pauldavidsguitar.com with a brief note about yourself, your experience, and why you’re right for the role. Please answer these questions in your email:

  • Webhook chain reliability. After a paid purchase on our external checkout (Stripe-backed), we need to: (a) create the user’s account on our community platform with their paid entitlement, (b) tag them in our email tool, (c) fire a Purchase event to Meta CAPI. Walk us through how you’d architect this. What happens if step (a) succeeds but (b) or (c) fails? How do you recover?
  • Cross-domain attribution. Our audience starts on YouTube, clicks a Meta ad, lands on our main site, goes through an embedded SamCart iframe (on samcart.com, a different root domain, potentially as a fail safe), then post-purchase lands on a third-party community platform (also a different domain). How do you make sure the full event chain fires to Meta with proper deduplication, and that the same user is tracked across all three domains?
  • Diagnostic. We’re seeing a 15% gap between purchases reported by our payment processor and Purchase events showing up in Meta. Where do you start investigating, and in what order?

Please don’t send a CV. Your work and your words will tell us everything we need to know.

There’s no fixed deadline, but we’re moving quickly. Once the position is filled, this advert comes down. We’ll aim to reply to all applicants within four weeks.

We’re looking forward to hearing from you.