Luann Francisco

My career began in full-cycle software engineering and grew into technical leadership, engineering management, and CTO work. Across about 18 years in technology, I have moved between writing software, shaping systems, helping teams find their footing, and making technical decisions alongside product and business needs.

That path shaped a practical view of engineering leadership: stay close enough to the work to understand its constraints, make trade-offs in context, and build teams that can move without depending on one person to unblock every decision. The goal is useful progress that lasts, not change for its own sake.

AI-native, with evidence

I am exploring how AI can take on more of the operational work of engineering. That does not mean maximizing generated code. People still set direction, exercise judgment, and own the result; evidence helps us decide whether a system's output is ready to trust.

Here I write about hands-on engineering leadership, product-minded architecture, team autonomy, and the systems and checks behind AI-native work. I care about what is useful, what can be verified, and where automation should stop.

If you are building an engineering team or rethinking how product work gets done with AI, I would be glad to compare notes.