Privacy

Accept optional first-party analytics or decline. Functional journey and sound preferences stay on this device.

Read the privacy notice

About

I'm Alexandra — a senior full-stack developer working in applied AI. I build retrieval systems and assistants that sit inside workflows people already use, and I own them end to end: the data model, the retrieval layer, the evaluation, and the interface. I care most about the parts a lot of people skip.

What I like to build

The work I enjoy most is the hard kind — a problem that genuinely resists you, where getting to the answer means real debugging: reproducing it, tracing it, and staying with it until you've found the actual cause and fixed it. I like the challenge, and I like the moment it finally gives.

What I think most people underrate

A lot of developers treat the frontend, speed, and UI/UX as things you bolt on at the end. I don't. How fast it feels, how it's laid out, and whether the code underneath is clean and well-structured aren't finishing touches — they're the product. Good structure is what lets a system keep growing without falling apart.

How I build now

The biggest shift in how I work: in the age of AI, you can reach the same result far faster, and I lean into that on purpose. The systems on this site — Alex OS, Alex CMS, the Theme DNA layer — were built with AI assistance, working with Claude Code as a pair rather than a code generator. I set the architecture, make the calls, reject what doesn't meet the bar, and own what ships. It changes what one person can realistically build, and I'd rather say that plainly than let anyone assume otherwise.

How I work

I'm comfortable either way — inside a team or owning something end-to-end on my own. Both produce good work; what matters is the standard, not the setup. And when an approach turns out to be the wrong one, I treat that as information — I don't repeat it. The mistakes are part of how the next version gets better.

What I won't do

One thing I won't do is ship something I already know isn't good. If a system doesn't meet the bar, it doesn't go out — I'd rather fix it, or say so plainly, than pretend it's finished.

Where I've worked

See the evidence

None of this is just claims — the work is here to inspect: projects with the problem, the decisions, and the outcome, and a proof section with before-and-after results.

See the proof

Get in touch

I'm interested in conversations about applied-AI systems, web platforms, custom tools, and field experiments. If you're building something — or want to — I'd like to hear from you.

Contact me