We build a lot of our own internal tools. Sales dashboards, finance and accounting views, customer insight databases, reporting that pulls from Shopify, Recharge, Klaviyo and a handful of other platforms. A lot of the first version gets built with AI, and it usually gets us 80 percent of the way there.

The problem is the last 20 percent. Something breaks, an API call fails, the data doesn't reconcile, and we lose hours poking at code we don't really want to be maintaining. We want someone who can open the project, find the actual problem, fix it properly, and then own it going forward.

Over time we also want this person building new data projects from scratch rather than us prototyping them first.

What you'll do

- Debug and fix internal dashboards and scripts when they break, including code that was generated with AI tools
- Build new internal tools from a plain-English brief: sales reporting, finance and accounting views, subscription and cohort reporting, customer insight databases
- Set up and maintain data pipelines between the platforms we already use so numbers land in one place instead of five
- Clean up and structure messy data so it can actually be reported on
- Write documentation positive enough that a non-technical person on our team can use what you built without asking you

Our stack

You do not need every one of these, but the more you've touched the better:
- Shopify (Admin API, Flow, metafields), Recharge, Klaviyo
- Google Sheets and Google Cloud, Apps Script, BigQuery or similar




- Python or JavaScript/Node for scripts and APIs
- Some kind of dashboard or BI layer (Looker Studio, Metabase, Retool, or a custom frontend)
- Automation tools like Make, n8n or Zapier
- Claude, and building data projects with it rather than around it

Who this is for

- You already build data projects with Claude or similar AI tools. This one matters. We want someone who works this way now, not someone learning it on our time.
- You've connected and reconciled data across multiple sources and APIs before
- You can read code you didn't write and figure out what it's doing without a lot of hand-holding
- You're comfortable being handed a half-working project and told to make it work
- You can talk to non-technical people about what's possible and what isn't, in plain language
- You'd rather ship something useful this week than architect something perfect over two months
- You like the part-time, project-based setup and aren't looking for this to turn into a full-time job

Not a fit if

- You need detailed specs before you can start
- You only want greenfield work and don't want to touch anyone else's code
- You need a lot of process and structure around you

How to applySend us

1. A short note on a data tool or dashboard you've built or rescued, what broke, and how you fixed it
2. Links to anything you can show us. GitHub, a dashboard screenshot, a Loom walkthrough, whatever you have
3. Your hourly rate and how many hours a week you can commit to

📌 Data & Automation Engineer (Canada)
🏢 Ape Born
📍 Canada