An AI Automation Engineer.
Most automation work I see is shallow. Connect this API to that spreadsheet, trigger an email when a form submits, done. That's not what I build. My work is end-to-end: a problem comes in one end, something useful comes out the other, and as little human touching happens in between as possible. I've built systems for invoice processing, AI-powered lead generation, and content pipelines that non-technical teams actually use daily without needing to call me. The stack varies by problem. OpenAI, Claude, n8n, Make.com, Airtable, Google Workspace, custom frontends — whatever the job requires. What doesn't vary is the thinking: treat every workflow as an architecture problem, not a configuration task.
<aside> <img src="/icons/briefcase_gray.svg" alt="/icons/briefcase_gray.svg" width="40px" /> View Projects
</aside>
<aside> <img src="/icons/user-circle-filled_gray.svg" alt="/icons/user-circle-filled_gray.svg" width="40px" /> About Me
</aside>
<aside> <img src="/icons/branch-create_gray.svg" alt="/icons/branch-create_gray.svg" width="40px" /> Github
</aside>
<aside> <img src="/icons/document_gray.svg" alt="/icons/document_gray.svg" width="40px" /> LinkedIn
</aside>
<aside> <img src="/icons/mail_gray.svg" alt="/icons/mail_gray.svg" width="40px" /> Email
</aside>