Navigate this article
My journey did not start with a fixed stack. It started with real problems in small companies and expanded into products, teams, infrastructure, and AI systems.
2020: first freelance projects
I started by building websites, landing pages, and blogs for local businesses. The work soon extended beyond visuals into tracking, WhatsApp automation, email, CRM, and better ways to connect digital presence with daily operations.
That stage taught me to look at technology through the expected outcome. A useful website needed to connect with support, sales, content, and the people running it.
2021 to 2022: platforms, e-commerce, and management
I moved into more complete web solutions, online stores, integrations, and SaaS products. I also coordinated freelancers and projects where technology, operations, and marketing had to work as one system.
The responsibility was no longer limited to delivering a feature. Scope, priorities, communication, and continuity had to be organized so other people could contribute.
2023 to 2025: Frontmidie
I created a technology and marketing agency with a multidisciplinary team. The experience combined development, management, client relationships, and hundreds of website and online store deliveries.
It was an important period for understanding team capacity, standards, perceived quality, and how technical decisions affect deadlines and maintenance.
Technical leadership experience at Cilic
I worked on the architecture and evolution of SaaS platforms, intelligent agents, automations, and integrations across AI models, APIs, CRMs, ERPs, and digital channels.
This experience deepened my work with architecture decisions, code review, agent context, infrastructure, and systems that must remain understandable while evolving.
Today: Will Engineer
I now work independently across software engineering, backend, Platform Engineering, and AI infrastructure. I look for partnerships where I can understand the business, organize decisions, and help build a sustainable solution.
Will Engineer brings together what I learned in different settings: proximity to clients, product thinking, technical depth, and responsibility for operations after software reaches production.
Principles this journey consolidated
Different experiences created criteria I now use to assess products, projects, and partnerships.
- Understand operations before proposing technology.
- Translate technical decisions for the people accountable for the business.
- Build the smallest system that can create value and grow with evidence.
- Document enough so work does not depend on one person.
- Treat deployment, support, and maintenance as part of the product.
- Use artificial intelligence with context, evaluation, and responsibility.
How this experience reaches each project
I do not assume every company needs to rebuild everything or adopt the newest tool. I first understand the product stage, team constraints, and the outcome that needs to improve.
From there, I can support a focused assessment, review an existing foundation, implement infrastructure, connect platforms, or follow technical evolution over time.
This material presents my working approach and is educational. The right solution depends on the context, risks, and responsibilities of each project.
Share

