Clarity over cleverness
If a system needs explaining before it can be used, the design is unfinished.
Senior Full-Stack & Applied AI Developer
Alexandra Nac. — Senior Full-Stack Developer | Applied AI Developer | AI Workflows · RAG Systems · Agentic Applications
I build AI systems people can trust.
Built with AI as a pair, from the reasoning behind them to the interfaces people use.
01 / IntroductionScroll to explore↓
02Who I am
I'm a senior full-stack developer who builds with AI, and builds AI into the products I ship.
What I've built moved with the stack: web platforms first, then assistants, retrieval and recommendation work inside real workflows. I use AI the way I'd use any strong tool. I set the architecture, I make the calls, and I keep only what meets the bar.
Alex OS, the assistant on this page, is how I'd rather introduce myself. It answers about me from my own published work, with sources. Ask it anything.
CurrentlySenior full-stack developer — applied AI and web platforms · IWConnect
More about me03What I've shipped
Built with purpose.
See every project
01
Alex OS
A FastAPI reasoning and retrieval layer that sits between the CMS and the public site — grounded answers, journey-aware recommendations, and a relationship-graph reasoning pass, not an open-ended chatbot.
One caching pass took Alex OS's heaviest data loads from 10.5s to 1.8s.
↗02
Alex CMS
A Next.js CMS with a fully dynamic content-type registry — no hardcoded post models — plus a journey-based homepage, an orchestrator workflow, and per-item content scoring.
Fully dynamic content model with zero hardcoded types.
↗
03
Theme DNA Design System
A database-driven design token system ("Theme DNA") that every public template consumes — change the brand once, and 23 templates restyle themselves. No hardcoded colors anywhere.
One place to change the brand; 23 templates follow instantly, including AI-generated content.
↗04Where I've worked
The jobs behind the work.
See the full record- 2018Current role
IWConnect
Senior full-stack developer — applied AI and web platforms
One company since 2018, and the work moved with the stack. Web platforms and email infrastructure first; applied AI now: workflow assistants built as prototypes with a human sign-off, recommendation systems, and the evaluation that tells you whether either actually works.
- Email helpdesk responder (prototype) — triages incoming support mail and drafts replies for human approval
- Insurance policy renewal assistant (prototype) — AI-assisted handling of the renewal workflow with sign-off kept where the risk is
- Product recommendation engine and an SDK for measuring recommendation quality repeatably (both prototypes)
- AI-assisted delivery — written scope, model-drafted implementation, line-by-line review, tests and evaluation as the gate
TypeScriptJavaScriptReactNext.jsNode.jsREST APIsMySQLWordPress
05How I think
Notes on working with AI, and the systems it helped build.
All notesEvidence over performance
I don't want AI features that only look intelligent. I want traceable sources, visible limitations and measurable outcomes.
AI as a pair, not a substitute
I use AI to reach the result faster. The architecture, the standard and the decision to ship stay with me.
ai-assisted-development · 1 min
How I work with AI→Three bugs that shipped in AI-assisted code, and the gates that catch them now
A hook after an early return, a silent embedding wipe, a reranker that vanished with a dead key. None of them were caught by reading the code.
Read↗ux · 1 minTwenty-two buttons is the same as no guidance
The first in-editor AI panel had 22 equally weighted actions. Generating features is cheap now; deciding which one to lead with is the work.
Read↗ai-assisted-development · 1 minWhat I let Claude Code do, and what I don't
AI as a pair changes what one person can build. It doesn't change who owns the architecture, the review, or the decision to ship.
Read↗06Why any of this matters
The systems I build are technical. The goal is always human.
Less confusion, better decisions, and more control.
Alex OSYour AI guide
I'll lead with what Alexandra has shipped, and what each system changed.
Every answer comes from Alexandra's own published content, with sources.