Any
$15/hr
20
Apr 21, 2026
The Role:
Each dental practice we sign triggers the same 30-day deployment. You will own steps 2 through 8 of that sequence:
• AI voice agents in Bland AI for after-hours answering, missed-call recovery, and patient reactivation campaigns — including pathway design, prompt engineering, and edge-case handling.
• n8n automation workflows connecting Bland AI, Twilio, GoHighLevel,
• Per-client provisioning: Twilio subaccounts and A2P 10DLC registration, GoHighLevel sub-accounts with pipelines and SMS workflows,
• QA and go-live testing — every deployment gets at least 15 scripted call scenarios before a client ever uses it.
• Ongoing monitoring and optimization of live workflows — catching failures before the client does, tuning prompts and sequences based on real performance data.
• Internal tooling on our own n8n and Supabase stack to support our growing client base.
• Clean, handoff-ready documentation of every build — so the system you ship is maintainable by the next engineer, not just by you.
Required Skills (Non-Negotiable):
• Strong n8n experience. You have built real workflows end-to-end — not tutorials. You can diagram a process, reverse-engineer an SOP, and build it in n8n without hand-holding. Portfolio or screenshots required.
• AI voice agent experience. You have built working voice pathways in Bland AI, Vapi, Synthflow, or Retell. You understand prompt design for voice, conditional routing, variable injection, and how to debug a call that went sideways.
• Solid API and webhook fundamentals. REST, webhooks, authentication (OAuth, API keys, bearer tokens), JSON manipulation. You can read API docs and build an integration from scratch.
• Development background. You are not just a no-code operator. You can read and write basic JavaScript or Python for custom n8n nodes, data transformation, and edge-case logic. Git familiarity expected.
• Troubleshooting under pressure. When a client's phone system stops routing calls at 5 PM on Friday, you know how to diagnose it, fix it, and document what happened.
• Clean documentation discipline. Every build you ship must be maintainable by a second engineer. You name things clearly, document credential storage, and draw data flow diagrams.
• Strong written English. All our internal communication is written. Async, clear, and concise.
Bonus (Not Required, But Valued)
• GoHighLevel build experience — sub-accounts, pipelines, SMS workflows, A2P 10DLC.
• Twilio experience — subaccounts, BYOT, 10DLC registration, Messaging Services.
•
• Supabase experience — schema, auth, row-level security.
• Lovable, Bolt, or similar AI-assisted frontend builders.