PRODUCT ENGINEER,DESIGN-MINDED BUILDER,EXPLORING AI-NATIVE EXPERIENCES.
Four years of production experience — and a year spent learning everything shipping code can't teach you. Now focused on AI-native experiences and iOS development.
Lume
I designed and built an AI meeting intelligence system focused on reducing information loss in collaborative teams. The project explored how transcription pipelines, semantic retrieval, and AI summarization could transform conversations into searchable organizational context rather than disposable meeting notes.
SVJ Outdoor
Working closely with a local outdoor retail business, I adapted and operationalized a POS system around their existing workflows — from inventory management to transaction reporting. The system is now actively used in daily operations, helping reduce manual overhead and improving operational visibility across the business.
Work beyond the flagship projects
Smaller explorations across AI systems, interaction design, motion, and product thinking — often built to investigate ideas, workflows, or emerging technologies.
Engineer. Designer. Builder.
For the first four years of my career, I focused mostly on shipping software — primarily mobile applications in production environments. Later, I stepped away from full-time engineering for a while to explore the broader layers around product building: UX design, motion, business, branding, and AI systems. That period ended up reshaping how I think about technology entirely. What interests me now isn't just building functional products, but understanding how systems, interfaces, and human behavior influence each other — particularly as AI becomes part of everyday interaction. Lately I've been exploring that through conversational interfaces, operational tools, and AI-native experiences on the web and iOS.
The Arc
The foundation
2018 — 2022Studied Informatics Engineering while starting to take on real development work. Built the habit of shipping things — not perfectly, but actually. Learned that software is a craft that improves through contact with real problems, not theory.
Four years in production
2021 — 2024Worked as a mobile engineer across two companies, shipping across fintech, civic tech, IoT, enterprise monitoring, and government infrastructure. Eight products shipped professionally. Learned what production software actually requires: client alignment, maintenance realities, the gap between what you build and what people experience. Grew into a UI design role alongside the engineering work.
Filling the gaps deliberately
2025 — 2026I noticed I could build things that worked. I wasn't sure they were good. That gap — between technically correct and actually worth using — required tools my engineering background hadn't given me. So I spent a year developing them: formal UX training, motion design for real clients, a market-facing business, AI systems that had to survive contact with operational reality. Every discipline taught me something the others couldn't.
Converging on Apple
2026 — NowWhen I returned to engineering, I knew I wanted to go native. Apple's ecosystem felt different — opinionated in a way that produces better interfaces, with design resources integrated rather than adjacent. I started learning SwiftUI and immediately noticed the coherence between the frameworks, the documentation, and the Human Interface Guidelines. That coherence is what I want to build inside. The Apple Developer Academy is the next deliberate step.
Disciplines
Product Engineering
End-to-end ownership from architecture to deployment. Comfortable across mobile, web, and AI backend systems. Not just writing features — thinking about what's worth building.
AI Systems
Building AI as infrastructure: pipeline design, microservice orchestration, embeddings, transcription, summarization. AI that has to work in production, not just in demos.
iOS Development
Currently: SwiftUI, Xcode, Apple frameworks, on-device inference. Building toward deep native expertise within the Apple ecosystem — CoreML, voice interfaces, and privacy-preserving AI.
UX Design
User research frameworks, usability thinking, interaction design, accessibility. Enough fluency to make engineering decisions that are grounded in how people actually use things.
Motion Design
SaaS explainer videos, brand animation, visual storytelling. Trained the eye for temporal UX — how things feel as they move, not just how they look at rest. Directly applicable to interaction design.
Product Thinking
Market validation, business mechanics, user psychology. The Etsy business was a compressed course in what makes people actually pay for something. Now applied to every independent product decision.
"The obstacle is the way."
Outside of technology, I'm interested in Stoic philosophy, neuroscience, human behavior, and the science of learning. These aren't separate from how I work—they shape how I approach growth, problem-solving, and building. Stoicism teaches that obstacles are information, not setbacks. Neuroscience and learning research reinforce a similar idea: improvement is less about innate talent or motivation and more about deliberate practice, feedback, and consistency over time. That perspective influences how I build. I value systems over willpower, experimentation over certainty, and long-term compounding over short-term optimization. Progress comes from staying curious, embracing challenges, and treating every outcome as an opportunity to learn.
Systems over motivation
Sustainable progress comes from reliable systems, not bursts of inspiration. Design the environment and process before relying on discipline.
Growth through challenge
The fastest learning often happens just beyond the edge of current competence. Seek opportunities that stretch existing assumptions and skills.
Long-term compounding
Knowledge, skills, relationships, and experience compound over time. Consistent investment creates outcomes that rarely appear linear in the moment.
Learning by building
The best way to understand something is to create with it. Build, test, iterate, and let real-world feedback guide improvement.
Obstacles as feedback
When something resists a solution, there's usually something left to learn. Resistance is often a signal pointing toward deeper understanding.
Currently reading
Literal.club
Critical Thinking
Richard L. Epstein, Michael Rooney
The Diary of a CEO
Steven BartlettCurrently listening
Spotify
October
Adrián Berenguer