Careers · HeyGM · Dublin, Ireland and the UK, with time in New York
HeyGM builds operating hubs for hospitality groups: one place where an owner sees last night's sales beside the labour that earned them, the bookings on the books, the events coming in, the reviews, the books from the accountant, and a morning brief that says what matters.
Flexible: part time on an hourly rate to start, moving to a full-time role as the work grows.
We are building a team of high-quality developers who use AI and the latest tools to build high-performance, high-value systems for some of New York's leading hospitality groups, and beyond, with more in the pipeline in construction and real estate. We are also building systems in the UK and Ireland. The first live hub, for a sixteen-venue group across Manhattan and Dublin, went from nothing to read-every-morning in four weeks, and there is a good pipeline of work already lined up to build out.
We deploy at the leading edge of what AI can do: agentic, self-serve systems that go after the value sitting in companies who cannot build this themselves, and whose alternative is a large established consultancy that charges far more and delivers less. The gap between what those firms ship and what a small team with the right tools can ship is the opportunity, and it is the job.
You will work in a Python codebase that pulls from Toast, QuickBooks, Tripleseat, OpenTable, Resy, Google and Meta, turns the raw data into reports and alerts, and ships a dashboard every morning from an always-on machine. You will also help turn the same engine into the demos HeyGM sells with: hospitality today, crèche, padel and property next.
This is an early place on a small team. You will see every part of the system, own things early, and be judged on whether what you ship is right and whether the people who read it every morning trust it. The bigger projects will mean time spent in New York and in the other US cities we are targeting, so you should be able and willing to travel.
A Python package with a command-line interface, about 2,500 commits in its first month, 27 docs and 430 tests. Raw data from each system lands unchanged, per-day summaries are recomputed from it, and one build makes the whole dashboard. Next: new report pages, the week-ahead roster, the group view for the owner.
Toast, QuickBooks, Tripleseat, OpenTable, Resy, Google and Meta today. Next: Sling and SpotOn Teamwork for scheduling, Paychex and ADP for payroll, the reservation platforms' APIs when they are granted, and more venues on each.
A refresh at 5:30am New York, a second pull for the late-closing venues, briefs by email at 6:45am, an hourly events pull and a weekly partner report. Keeping it reliable, catching what it misses, and moving it to a server when the group outgrows the box.
The hospitality demo is the real hub with every name swapped and every number scaled, refused if a real name survives. Next: crèche, padel and property demos on the same engine, and the tenant model so a demo becomes a customer without a rebuild.
Not needed: a degree, a particular stack, or years of experience. Needed: evidence you can finish things and say plainly what you did not finish.
The rules the codebase already runs on. Each was learned the hard way and is written at the top of the repo.
Run the hub locally, read the docs and the systems register, fix three small things from the request box, and ship one of them through the proper route.
Own one connector end to end, so the week-ahead roster can sit beside the bookings and fixtures the hub already forecasts.
Build one report page from a manager's question to a live page with its line in the morning brief, the calculation written beside the number.
Take the nightly. You know what runs when, what it does when a platform is down, and you have fixed at least one morning before anyone noticed.
By the end of it you should be able to say which venue's data you would trust, which you would not, and why.
| Employer | HeyGM. Reports to Richie Carroll, Founder. |
| Location | Flexible. Dublin or remote in Ireland or the UK; the venues are in Manhattan, so some afternoons run on New York time. For the bigger builds there will be time spent on site in New York and in the other US cities we are targeting. |
| Hours | Flexible: part time on an hourly rate to start, with a transition to a full-time role. The nightly runs before 7am New York; you are not on call for it, but you own what it did when you sit down. |
| Equipment | A Windows laptop and access to the always-on build machine; Claude Code on both. |
| Start | As soon as found. |
Send three things to richie@heygm.io: a short note on something you built and what went wrong with it, a link to code you wrote (any language, any size), and which of our platforms you have used, if any. No cover letter.
Apply here