I design automation architectures that solve business problems
An AI Automation Engineer specializing in designing and building intelligent automation systems. I work on projects spanning AI Agents, Python, n8n, RAG, RPA, and custom business integrations.
My value is not in any single tool — it is in understanding the business problem first, then designing the right technical architecture. I choose the right technology for each component, whether that means n8n, Python, AI Agents, or a hybrid approach.
Technical expertise
AI & Machine Learning
Automation Platforms
Software Engineering
Infrastructure & Deployment
My story
My engineering background started with embedded systems, IoT, and low-level programming — which gave me a deep understanding of how systems and machines communicate with each other. I moved into web application development and backend services with Python and APIs before finding my true focus in business automation.
I noticed that most of the problems businesses face are not fundamentally technical — they are process problems. Disconnected systems that do not talk to each other, repetitive tasks consuming employee time, and information scattered across multiple tools. That realization led me to automation.
As large language models became accessible through APIs, a new door opened: intelligent systems capable of reasoning and decision-making, not just executing if-then rules. I built AI Agents using LangGraph and CrewAI that handle complex customer support scenarios, RAG systems that make company documentation queryable in natural language, and orchestrated integrations across dozens of services using n8n.
I believe the value of an automation engineer is not in how many tools they know — but in their ability to diagnose the right problem, design the right architecture, and build something that keeps working long after the project is done.
How I work
Understand the problem first
Before any code or workflow design, I spend time understanding your current processes and their pain points. The technical solution follows from understanding the problem, not the other way around.
Design the right architecture
I choose technology based on business requirements. Some projects need n8n, some need Python, and some need a hybrid approach. I do not force a tool onto a problem it does not fit.
Build incrementally
I build in stages with regular check-ins. You see real progress at every milestone rather than waiting until the end of the project.
Document and transfer knowledge
Everything I build is fully documented. Your team can maintain and extend what I deliver without needing to depend permanently on an outside consultant.
Tools I use
What I believe
Business outcomes over technology
Every business problem deserves the right technical solution. I do not force one technology where another is more appropriate. The technology choice always follows the business requirement.
Architecture before implementation
Before writing any code or building any workflow, I design the architecture. This means understanding the data flow, the components, and the technology choices — and documenting them for review.
Simplicity is a feature
The best automation is the one that is easy to understand, maintain, and modify. I avoid over-engineering and prefer solutions that are as simple as possible — but no simpler.
Knowledge transfer matters
I document everything and train your team so they can maintain and extend what I build. I do not believe in creating dependency on consultants.
Want to work together?
I'm currently available for new projects. If you have a process that needs automating or a system that needs building, let's talk.