AboutRuben John Mendoza

I work on the part of the business that runs after the form is submitted.

Backend Automation Engineer and Sales Support Operations Specialist. I build the event flows, integrations and exception paths that keep operations moving without someone chasing every record.

Ruben Mendoza
Pasig, Philippines · remote

I came into automation through operations. Reconciling accounts, chasing mismatches and rebuilding the same spreadsheet every week made the problem obvious: the work was not the report, it was the manual step before the report.

Since then I have built lead-response and booking systems in GoHighLevel, a reputation workflow that intercepts negative feedback privately, an order-to-invoice pipeline across Shopify, Make, Zoho and Xero, and a multi-source reconciliation pipeline in Python and SQL.

My approach is platform-agnostic. The tools change; the questions do not. What is the source of truth? What event starts the next step? What happens when the payload is wrong, the customer already exists, or nobody replies?

I work best with teams that need someone to own the backend: design it, integrate it, test the ugly cases, and leave the evidence behind.

Read the casebook

How I got here

Jun 2026 — present
Commercial Account Operations Specialist (Automation Support), United Petroleum

Reconcile commercial account data across XGen, Rosette and internal records; maintain the reporting workflows behind daily and weekly activity figures.

Project work
Automation systems for service businesses

Lead response, booking, review management, order-to-invoice and reconciliation systems built across GoHighLevel, Make, Python and SQL.

Jan 2019 — Jan 2024
Marikina Polytechnic College

Bachelor of Engineering, Heating, Air Conditioning, Ventilation and Refrigeration Maintenance Technology / Technician.

Principles

01

Start with the handoff

A process breaks where ownership changes. I map the handoff before choosing a tool, so the automation has one clear source of truth.

02

Make exceptions visible

A system is only as good as its failure path. Unmatched records, malformed payloads and no-shows get their own route instead of disappearing.

03

Leave evidence

Screenshots, logs and execution history are part of the deliverable. If the system cannot show what happened, it is not finished.

Tools

Automation
GoHighLevel, Make.com, Zapier, webhooks
Data
Python, SQL, Excel, Google Sheets
Business systems
Xero, Zoho Inventory, CRM pipelines
Channels
Twilio, Gmail, SMTP, Slack / Discord

Start with the process

Send the process that is still running by hand.

You get a written read on what can be automated, what it would take, and what it removes from the week. No pitch deck required.