My background is in building backend automation systems on top of GoHighLevel, but my approach is platform-agnostic. I think in terms of events, state, and data flow — not features.

Every project starts with system architecture: mapping the lifecycle, defining the source of truth, and identifying where automation replaces manual work. Only then do I touch a workflow builder.

I work best with teams that need someone to own the backend — design it, integrate it, and make sure it keeps running.

{
  "role": "Backend Automation Engineer",
  "focus": ["system_architecture", "workflow_design", "integrations"],
  "stack": ["GoHighLevel", "Webhooks", "REST", "Twilio", "Zapier", "Make"],
  "thinks_in": ["events", "state", "lifecycle"],
  "available_for": ["contract", "full_time", "project"]
}