Platform & Integrations Engineer (operations)

Platform & Integrations Engineer

Romea.AI · Philippines-based team, remote · Full-time · You work directly with the founder

What we are building

AI front-office staff for plastic surgery and aesthetic practices in the US and Australia. Our AI talks to patients over SMS, web chat, iMessage and voice, qualifies them, books them into the practice's EMR and calendar, follows up, takes payments, and hands the practice an analytics portal that shows the whole funnel from ad to surgery. Around fifteen practices run on it today and they talk to it more than they talk to their own front desk. Nobody has done this properly for this industry yet. We are small, fast and profitable enough to be picky.

Who we are looking for

An engineer who gets a kick out of two things at once: watching an AI agent book a real surgery consult at 3 am for a clinic in Texas, and knowing exactly why it worked, because you run the system it ran on.

You are an AI fanatic in the practical sense. You use coding agents every day, you have opinions about which models are worth their price for which job, and you have learned the hard way where they lie. You also like servers. Backups you have actually restored, a Caddyfile you wrote by hand, a Postgres you tuned, a Cloudflare worker you fixed at midnight. If one of those two halves bores you, this is not your job.

What you will do

Run production. Two droplets, a Cloudflare account, a handful of Python services, Postgres with pgvector, the databases, the backups, the secrets, the deploys. It is yours. You d ---------- how it is monitored and what "healthy" means.

Build with AI, ship as a human. Code gets written with Claude Code and our own agent setup on the build server. You are the gate: you review it, test it, deploy it from a git tag and you own what is live.

Onboard practices and build integrations. New clients go live as configuration on one shared engine, not as forks. When a practice needs its EMR (4D, Symplast, Nextech, PatientNow), its CRM (GoHighLevel), a payment provider or a new channel wired in, you write the adapter, with tests.

Talk to clients. Practice owners and coordinators know you by name. You join the onboarding call, you explain what the AI will and will not do, you fix what they report and you tell them when it is fixed. Customer success handles the day to day; the technical conversations are yours.

D ---------- with us. Four people, no layers. Model choice, what to build next, which client request becomes a product feature, how we handle an i ---------- : you are in the room and your vote counts. The founder designs the system plans and directs the AI builders; you make sure what comes out is real, safe and running, and you push back when a plan is wrong.

Keep it clean. Patient data, HIPAA, consent, money. No shortcuts, no PHI in repos or chat, least privilege, audit trails where it matters.

What you bring

Five or more years of running systems you were on call for, including at least one migration you finished and one i ---------- you traced across several services.

Python at a professional level (FastAPI, async, pytest). TypeScript well enough to read and patch a Cloudflare worker.

Postgres beyond the basics (partitions, roles, pooling, pgvector, backups and restores), Linux, Docker, Caddy or nginx, systemd, Cloudflare Workers, D1 and Queues.

Real-world API work: OAuth2, webhooks, idempotency, retries, rate limits. GoHighLevel, EMR or healthcare APIs are a plus.

Daily use of AI coding agents, and the judgement to know when their output is wrong.

Comfortable on a call with a surgeon's office manager. Clear written English.

What this is not

We have an architecture and we are not rewriting it. If your instinct on day one is a new framework, a new language or a platform v2, we will disagree. The interesting problems here are in making a live AI system reliable, extending it one integration at a time, and shipping every week.

How we hire

A conversation with the founder, then three practical exercises of about an hour each, with whatever tools you normally use, AI agents included. We look at the result and how you explain it.

A Cloudflare worker, a tenant row in the database, and a patient message that never got a reply. Find out why.

A Python CRM adapter that double-books an appointment on retry. Fix it and add the test that would have caught it.

A Postgres database on a droplet you have never seen. Add a backup, prove a restore, add the alert for when it stops running.

The exercises run on our real gateway code, our real adapter test harness and a throwaway server we give you. Then a last call where you tell us what you would change in the first month.

Terms

Freelance contract, 40 hours per week. I ---------- work outside your hours is paid.

Start ASAP

How to apply

Write to ---------- with three things: an i ---------- you resolved and what you changed afterwards, a migration you finished and how long it took, and something you built with AI that you are proud of. CV optional.