APEX Operations Engineer — Internal Systems & DevOps (Sheets/Apps Script, HubSpot, Git)

Read this first: This is an ENTRY-level seat with a real ceiling — not a senior role. Most operations jobs are dead-end. This one isn't. You start running part of our internal systems, and as you prove yourself, you grow into owning the entire internal operating system across all our businesses — and taking DevOps work off our lead engineer. Scope, trust, and pay grow with performance. Our lead engineer walked this exact path here. If you want a finished senior title handed to you on day one, this isn't it. If you want to EARN one, keep reading.

ABOUT THE WORK
We run our business on internal operating systems — the same repeatable pattern (data masters, dashboards, review queues, health checks, logs, automations) running across several ventures. The core is built in Google Sheets + Apps Script, and it connects out to the tools we run the business on: HubSpot (CRM/pipeline), QuickMail (cold email ), Quo (voice/SMS), Slack (team + alerts), and Stripe (payments). Our engineering lives in GitHub. It all works and it's good — but it was built piece by piece, it's not standardized, and it's not in version control (Git/clasp). Right now the founder is the only person who fully knows how it all runs. Your job is to change that.

Important boundary: This is our INTERNAL operations layer. It is NOT the customer-facing product — that's engineering's world. You won't write product features. You WILL own how the internal machine runs, connects, and ships.

WHAT YOU'LL DO

• Standardize our systems: take the best version of each pattern (queues, logs, health checks, automations) and make everything match it. Solve it once, not five times.
• Own the connections between tools: data flows out to HubSpot / QuickMail / Quo, and signals (opens, replies, deal outcomes, payments) flow back to our systems, all keyed to one identity. Keep those adapters clean and swappable.
• Get our Apps Script into clasp + Git and own the versioning/release (DevOps) process.
• Run the daily rhythm: work the review queues, watch the health-check alerts, keep everything clean and current so the founder is out of daily operation.
• Read across systems to catch duplication and broken handoffs before they cause problems. You're the person who notices "wait, we already built this."

WHO YOU ARE (this matters more than your résumé)

• You SURFACE PROBLEMS. You hit something broken, confusing, or duplicated and you raise it — WITH a recommendation, not just a complaint. You can't walk past a mess. This is the #1 trait we're hiring for.
• You're CURIOUS FIRST, then honest. You understand WHY something exists before proposing to change it, then you say the true thing directly.
• You're PROACTIVE. You fill your own queue. Nobody should have to tell you what to work on.
• You TEACH YOURSELF. If you don't know a tool yet but you'll have it down in two weeks, that counts.

WHAT YOU NEED TO START

• Advanced Google Sheets.
• Can read and write Apps Script (JavaScript) — enough to fix a function, edit a config, set up a trigger, connect an API, and run a change carefully.
• Comfortable working with tools like HubSpot and connecting APIs between systems.
• Familiar with Git, OR a fast learner who will pick up Git + clasp quickly.
• The character above — especially the instinct to catch problems and bring a fix.

BONUS (not required — these move you toward the senior end of the pay range faster)

• MySQL / SQL databases.
• Laravel / PHP.
• Experience connecting or automating between SaaS tools (HubSpot, Stripe, email /SMS APIs, Zapier/Make/n8n, etc.).
• Any DevOps / CI / deployment experience.

We're heading toward an owned platform (MySQL + Laravel) over time — if you can grow into that, this seat grows a lot.

HOW TO APPLY
Reply with:
1. The word "APEX" at the top of your application (so I know you read this).
2. A short description of an internal system, tool, or automation you built — in Google Sheets/Apps Script, or connecting tools like HubSpot/Stripe/APIs — what problem it solved and how you built it.
3. One time you noticed something was broken or being done inefficiently, and what you did about it.

Applications without these three things won't be reviewed. There is a short test as part of hiring.