Apps Script + Sheets Systems Engineer & WordPress Funnel Dev

SALARY: $1,000–$3,000/month (₱57,000–₱171,000) at the full seat · project-based ladder to start · the top of the band is earned by mastery across BOTH sides

HOURS: Project rounds first → ongoing seat for the one who delivers SPLIT: ~70% Google Sheets / Apps Script systems · ~30% WordPress / tracking / funnel tech

This is a detailed listing because the work is real. If you're the right person, reading it will feel like recognition.

What this is -

I run a live online operation on two connected layers, and I'm hiring one technical person who understands both:

Layer 1 — the operating system: a multi-workbook Google Sheets structure (tasks, content production, scheduling, payroll, testing) driven by a standalone Apps Script engine on live triggers, with remote workers editing daily while the engine writes.

Layer 2 — the web side: WordPress on shared hosting — fast landing pages, tracking parameters passed cleanly through multi-page flows, pixels placed, tested, and verified.

The two layers feed each other, and most failures live at the handoffs between them. I want one person who understands the whole pipe.

The architecture is already built, documented, and working. I don't need it rebuilt — I need it hardened, connected, and made to run itself, surgically, without breaking a live system.

If your toolkit stops at VLOOKUP, this seat isn't the fit. If you write real .gs, build multi-sheet systems that feed dashboards, and are comfortable opening a WordPress page in code view — keep reading.

The hard parts, up front -

I share these because I want someone who has beaten them before. I already hold a full diagnosis of this system — so your answers don't need to be long, they need to be specific. Specific beats general every time.

Automated writes collide with live human edits. The engine writes on time-based and onEdit triggers while workers edit the same sheets. Runs collide, and things silently un-fix. If you know why this happens and the discipline that prevents it, you're ahead of the pool.

Position-bound logic breaks when rows move. New blocks of rows are inserted daily — and jobs that generate records on those rows silently stop firing. This currently needs daily manual patching. I want it anchored so it never needs a human again.

Roughly 1 in 5 runs of the core trigger fails — silently. No error, no alert. Early work drives that toward zero.
Failures need to get loud. Reconciliation comparing expected vs. actual state — every complete row has its generated links, every date its formatted header — flagged on-sheet within the hour, not discovered days later.

On the web side: pages load fast, tracking fires with the right data and carries parameters page-to-page, and a change to one flow never quietly breaks another.

Why this seat is worth having -

A real production system, already documented. You inherit a mapped architecture with a written operating manual — not an undocumented sloppy system.

Direct with the owner. No agency layers, no committees. Decisions in hours, not weeks.

Paid at every step, on acceptance, fast. Clear written criteria, quick payment when work verifies.

Room to become the technical lead of the entire stack as trust builds — the system, the automation, and the web layer.

The work -

Side 1 — Sheets / Apps Script (the core):

Maintain and harden a standalone Apps Script engine across a multi-workbook system

Triggers — onEdit, time-based, onChange — with safe handling of concurrent writes vs. live human edits

Root-cause fixes that hold, not band-aids that break next week

Replace position-bound logic with key-anchored logic that survives daily row growth

Validation, flagging, alerting, reconciliation, scheduled summary reports

QUERY / IMPORTRANGE / ARRAYFORMULA / INDEX-MATCH / FILTER at a systems level — input sheets rolling up into live master dashboards

Sheets ↔ external APIs with auth + error handling

Side 2 — WordPress / web tech (the delivery layer):

Build and edit pages on WordPress — comfortable in code/HTML view, not just page builders

Clean HTML/CSS, enough JavaScript to place scripts correctly and troubleshoot

Place and TEST tracking pixels and scripts — header vs. body vs. page, parameters passed through multi-page flows

Page speed basics: minify, image optimization, caching

Replicate a working page flow to new versions and languages without breaking the original

Always: build on a copy, test, then deploy. Document everything.

What's required -

Real Apps Script experience — actual .gs code, not just formulas

Concurrency discipline — you've handled automated writes vs. live human edits under real load

Key-based, not position-based — logic that survives rows, tabs, and values being added daily

Advanced formula fluency — the QUERY/IMPORTRANGE stack at a systems level

WordPress in code view — you read and clean markup, not just drag blocks

Tracking you can prove — you've placed pixels AND verified them firing with the right data

Root-cause over patch · surgical over destructive · documented over clever

Clear written English, reliable availability, stable setup

You stand out if -

clasp + a real editor for Apps Script development

Apps Script + external API integration (REST, OAuth)

Master-dashboard rollups from many input sheets, in production

Google Tag Manager · Cloudflare/DNS basics · A/B or split-test setups

You've built for performance-marketing funnels or paid social flows

You've automated real operational systems — payroll, tracking, reporting — not demos

How this stays clean -

Everything runs under my accounts — sheets, scripts, triggers, hosting, domains, and credentials stay owned by me. You work from an access-limited account I issue.

Paid fix rounds: real issues, scoped per round — honest estimated hours × up to $13/hr (₱~750/hr), fixed total, paid on acceptance against written criteria. Estimates are scoped against the work line-by-line, so quote what it truly takes.
The seat: deliver well across rounds on BOTH sides and we scope the ongoing role at the salary above, with bonuses for clean implementation, speed, and reliability.

I move quickly for people who deliver.

How to apply -

The steps below are part of the evaluation — complete applications get read in full; incomplete ones can't be considered.

Put ACE at the very top of your application.
Share 2–3 projects you personally built — together they should show real .gs work, a multi-sheet/dashboard system, AND a WordPress site you built or heavily modified. Links: code (GitHub/Gist), working sheet copies, live URLs.
In 3–4 sentences — the question that matters most: every day a new block of rows is inserted into a sheet, and a scheduled job that generates records on those rows silently stops firing. What's your first hypothesis for why, and how would you rebuild it so it never breaks on inserted rows again?
In 2–3 sentences: one thing you automated with Apps Script that a formula couldn't do — name the trigger and the logic.
In 2–3 sentences (high-level steps): how you'd implement a two-page flow on one WordPress domain — Page 1 passes a tracking parameter from the ad click through to Page 2 — so the parameter survives the full journey.
In one line each: how you catch a script that fails silently — and how you tell a real fix from a patch that will break again.

Plus — a screen recording (3–5 minutes, required): walk through, with your voice: (a) a Sheets/Apps Script system you built — show the code; (b) a WordPress site you worked on — open the editor, show code you modified; (c) where you placed tracking and what it does. The recording is the heart of the application — it's how I see real work instead of words.

Complete this well → paid test task on a copy of my real system. Deliver that → the rounds. Deliver those → the seat.

I'm hiring ONE person — someone who can hold the whole pipe: the sheets, the scripts, the pages, and the tracking that ties them together. If that's you, I'm looking forward to your application.