Full-Stack Engineer, Platform and Automations

About us

AbuvThePar runs an Amazon wholesale education program. Our students learn how to open accounts with real brands, buy inventory at wholesale, and sell it on Amazon. Behind the program are teams for purchasing, brand outreach, and student coaching, plus the software that ties all of it together.

About the role

We run the business on our own apps and automations: a platform for our students, an ops platform for our team, and scheduled jobs that move data between them and the tools we use every day. Most of it was built with AI coding tools, and it has grown past what our current team can keep up with. This role keeps all of it running, fixes what breaks, and ships what's next.

If AI-built code makes you nervous, this isn't the role. If it makes you curious, keep reading.

What's already builtAcre: the student platform

The app our students use to run their wholesale business day to day.

• Find brands to work with and build lead lists
• Look up the right contacts at each brand (email and phone), from our own brand database and outside data providers
• Research a brand before a call: prep notes, talking points, and the brand's products on Amazon
• Track every brand from first contact to closed deal, with tasks, notes, and files
• Write emails that land as drafts in the student's own Gmail, and pull in the replies
• Listing tools: copy checks for Amazon listings and product image generation
• A background job system for long-running work, with usage limits for each student

Next up on the roadmap: more Amazon data sources, usage credits, and speed work as more students join.

Ivy: the ops platform

The internal app our team uses to run purchasing, offers, and fulfillment. It is several apps in one codebase.

• Purchasing: upload purchase orders, check the profit on each product, approve or decline
• Student offers: turn approved orders into offers for students, with a Google Sheet and a Gmail draft for each student
• Offer tracking: see which offers were sent, accepted, or declined, with weekly reports
• PO flow: follow each order from close through supplier payment, warehouse receiving, and invoicing (Xero)
• Account management: track which products each student is approved to sell
• Brand outreach: a database of 20,000+ brands and their contacts, with contact lookup and call queues
• Coach workspace: student profiles and rosters for our coaching team

Automations

• Offer texts: when an offer email goes out, the student gets a text (through GoHighLevel) and one reminder 48 hours later
• Gmail sync that tracks offer emails and replies
• Scheduled jobs (GitHub Actions and cron) that keep Ivy, Google Sheets, and our CRM in sync
• Email sequences to students and brands (Hunter)
• Brand research and contact lookup pipelines in Python and Node, using Hunter, Apollo, SerpAPI, and LLMs

Tech stack

• Apps: Next.js and React. Acre is TypeScript, Ivy is JavaScript (pnpm + Turborepo monorepo)
• Database: Supabase (Postgres, row-level security, storage)
• Hosting: Vercel (Acre), Railway (Ivy)
• Code and CI: GitHub, GitHub Actions
• Testing: Vitest, Playwright
• Scripts: Node and Python
• Outside services: Google Workspace APIs (Gmail, Sheets, Drive), GoHighLevel, Hunter, Apollo, SerpAPI, OpenRouter for LLM calls, Xero
• AI coding tools: Claude Code, Codex

What you'll doEvery week

• Fix bugs across Acre, Ivy, and the automations. When someone says "it's broken," find which step broke, fix it, ship it, and check it on the live app. Same day when you can.
• Run deploys on Vercel and Railway, watch the logs, and roll back fast when something goes wrong.
• Change the database safely: write and apply migrations, keep row-level security tight, and keep backups current.
• Keep the automations healthy: notice when a scheduled job or sync stops, find out why, and get it running again.
• Watch usage and limits on outside APIs (contact lookup, AI, texting) so nothing runs out without warning.

Projects

• Ship Acre roadmap features end to end
• Clean up screens that confuse students or staff, in both apps
• Speed up slow pages as more students and data come in
• Add tests for the parts that break most often
• Keep a short doc for each system, so nobody has to guess how it works

The bug work matters most. Done means you saw it working live, not "it should work now."

Your first 90 days

• First 30 days: Get access to everything. Map how Acre, Ivy, and the automations fit together: what calls what, where the data lives, and what runs on a schedule. Fix your first live bugs.
• By day 60: You own the bug queue and deploys for both apps.
• By day 90: You ship Acre roadmap features end to end, from the idea to checking it live.

What you're good at

• Reading a system you didn't write and mapping it: what calls what, where the data lives, what runs in the background
• Deploys and keeping apps up: GitHub, Vercel, Railway, env vars, logs, rollbacks
• Postgres and Supabase: migrations, row-level security, and never deleting what you can't get back
• Next.js, React, and TypeScript, enough to fix it and ship it
• A good eye for UX/UI. You can tell when a screen is confusing and make it simpler.
• Working with AI coding tools and checking their work instead of trusting it
• Clear written updates: what broke, what you changed, and how you checked it

Nice to have

• Experience with Amazon selling, ecommerce, or wholesale
• Python for scripts and data jobs
• Connecting tools through their APIs: Gmail, Google Sheets, Slack, GoHighLevel, or other CRMs
• Background jobs, queues, and scheduled tasks

How we work

• Find out why something broke before you fix it.
• Small changes shipped often beat big risky ones.
• Back up before you change data. Never delete what you can't get back.
• AI writes a lot of the code. You check all of it.

This isn't for you if

• You need a full spec before you start anything
• "It works on my machine" feels like done to you
• You'd rather rebuild a system from scratch than learn the one that's already running

How to apply

Skip the long cover letter. When you apply, send us three things:

• One thing you built or fixed, with a link if you can share it
• What broke along the way, and how you found it
• Your available hours and time zone

A resume is fine too, but we read those three answers first.

Pay: Up to $100,000.00 per year

Benefits:

• Work from home

Work Location: Remote