We’re hiring a Technical Automation Developer to help us build, run, and steadily improve the systems our clients rely on every day.

This is not a role where you disappear into abstract architecture or spend months designing theoretical systems. You’ll work directly on production workflows that support billing, CRM pipelines, dialers, and revenue operations.

The work is practical. The impact is real. The expectations are clear.

If you like ownership and turning messy sales processes into dependable systems, keep reading.

How We Work (This Matters)

Before tools or titles, this is what we care about.

People First

Relationships over transactions. We assume good intent. We communicate clearly. We care about doing serious work without making work miserable.

Excellence as a Standard

Quality isn’t optional. Our clients run real businesses. Their billing, data, and pipelines have to work on an ordinary Tuesday, not just during a launch.

Constant Innovation

We improve continuously. That means questioning defaults, cleaning up duct-taped automations, and replacing fragile workflows with something sturdier.

Infectious Energy

We enjoy solving problems. Curiosity, momentum, and humor go a long way here.

If those values don’t resonate, this won’t be a good fit.

What You’ll Be Responsible For

Owning operational systems
You’ll build and maintain automations and backend logic that support CRM workflows, billing flows, and sales operations. When something goes live, you stick around to make sure it keeps working.

Working across integrated tools
You’ll connect systems like HubSpot, Close, Pipedrive, dialers, payment processors, and internal services. Real-world integrations are messy. You’ll design for that.

Translating business into systems
Clients describe outcomes. You break those down into steps, map the flow, and implement reliable automation.

Protecting revenue-critical paths
Billing, lifecycle stages, lead routing, and attribution matter. You’ll ship changes carefully using staging, logging, and rollback planning so mistakes are manageable.

Making systems more reliable over time
You’ll fix brittle Zaps, reduce unnecessary complexity, and replace “it works for now” with something that actually holds up.

Leaving things better than you found them
Clear documentation. Cleaner workflows. Fewer silent failures. Better naming. Fewer mysteries.

Working async, on purpose
Clear written updates. Thoughtful documentation. Fewer meetings. We value communication that respects people’s time.

As you grow, you’ll take on larger systems and help shape how we standardize and improve our automation approach across clients.

What “Good” Looks Like Here

• Automations run without constant babysitting
• CRM pipelines behave the way they’re supposed to
• Billing and data flows are stable
• Integrations survive upstream API changes
• Documentation helps the next person move faster
• You don’t need micromanagement to do solid work

What We’re Looking For

You must have:

• 2–5 years of professional experience in backend development, automation, or Sales/Revenue Operations systems

• Strong working knowledge of Node.js / JavaScript

• Hands-on experience with CRM platforms (HubSpot, Close, Pipedrive, or similar)

• Real experience building or maintaining Zapier / Make automations

• Comfort working with third-party APIs and webhooks

• Experience operating inside live, revenue-impacting systems

• Clear written communication skills

• Authorization to work in the United States

Nice to have:

• Billing or subscription system experience

• Dialer / telephony integrations

• AWS familiarity

• MongoDB or Postgres experience

• Experience supporting high-ticket coaching or consulting businesses

• Practical use of AI tools to accelerate debugging or documentation

Why This Role Exists

Our client systems are becoming more important and more interconnected. We need someone who enjoys building dependable automation inside real business environments and steadily improving what already exists.

This role is best suited for an early-to-mid career builder who enjoys practical execution more than large-scale architecture debates.

If you want meaningful work with people who care about quality, relationships, and making systems better without unnecessary stress, this role is worth your attention.