Automation Automation Engineer — Client-Focused, No-Code First (10-15hrs/week)

"FieldHQ eliminates the administrative work stealing revenue-generating time from solicitors, accountants, and estate agents across the UK.

We're looking for someone who builds automations the way good developers write code—modular, documented, maintainable. Because our clients shouldn't be dependent on us to keep their systems running.

This is fractional to start (10-15hrs/week). If we work well together and client demand grows, so does your involvement."

What You'll Do:

- Build and maintain Make/Zapier automations for 3-5 active UK clients
- Document workflows so clients can understand (and maybe eventually manage) them
- Conduct technical discovery calls when the team needs backup
- Advise on scope: when to simplify, when to build, when to say no
- Light custom code when no-code hits its limits (webhooks, API integrations, data transforms)

What You Won't Do:

- Sell or do account management (FieldHQ handles that)
- Build complex custom software (we're no-code first for a reason)
- Work alone in a silo (you'll collaborate with the team on client strategy)

You're a Fit If:

- You've built 20+ Make or Zapier automations that are still running 6+ months later
- You can explain technical trade-offs to non-technical clients without condescension
- You care more about "client saved 12 hours/week" than "I used the latest AI model"
- You've been burned by unmaintainable automation before and learned from it
- You can work with UK timezone overlap (at least 2-3 hours for calls with our team)
- Strong written and spoken English

You're Not a Fit If:

- You need daily direction or struggle with ambiguity
- You think no-code tools are beneath you
- You optimize for technical elegance over client outcomes
- You want to build your own thing (we support that, but not in this role)

Logistics:

- 10-20 hours/week to start, flex schedule
- Fully remote, async-first (some UK timezone overlap required)
- Project-based compensation + retainer for maintenance work
- Potential to grow hours as we scale

To Apply:
Send a 2-minute Loom (or video) answering these:

1. Walk us through an automation you built that's still running 12+ months later. What did you do to make it maintainable?
2. A client asks for something complex. You realize a simpler solution solves 80% of their pain. How do you handle it?
3. What's one automation you regret building, and why?

Include link + GitHub/portfolio if you have one.