Solutions Engineer // AI Practitioner
I bring enterprise sales instincts and hands-on engineering depth to the same problem. I stay in customer-facing roles on purpose: good software starts with getting close to customers and their problems, then carrying what you learn back to the people who build it.
I started in enterprise SaaS sales and moved into Solutions Engineering by choice. I wanted to stay customer-facing and go deeper technically. I translate what customers need into what engineering builds, and I stay close to the problem to do it.
I'm an advanced user of Claude Code, Cursor, and n8n, and I build workflow automations that save real time. I completed a full-stack bootcamp at Northwestern and am currently studying LLM Engineering, RAG, and Agentic AI systems. I write code because understanding the craft makes me a better engineer for customers.
The SE job keeps changing, and at Codility I've leaned into that. I train our GTM teams on generative and agentic AI, build Claude Agent Skills that automate onboarding, meeting prep, and account research, and built the agentic harness that cut RFP turnaround from 14 to 5 business days. With Product and Engineering, I helped design new skill evaluations for Forward Deployed Engineers.
Bilingual in English and Spanish. Trivia enthusiast, always learning something new. The curiosity that helps at pub trivia also keeps me digging until I understand a customer's problem and the system behind it.
Advocate
INFJ-A
A quiet idealist who thinks in causes and long time horizons. Assertive rather than Turbulent, which mostly means I commit and don't second-guess.
Assessed by 16PersonalitiesMind51% Introverted
Roughly even, and the work is roughly even too: discovery calls and demos one hour, heads-down building or a written proposal the next. Neither one costs me anything.
Energy62% Intuitive
I reach for the pattern first, then go and get the details to check it. That is most useful in discovery, where the stated problem is rarely the actual one.
Nature76% Feeling
A technical recommendation only matters if people adopt it, so I plan for how a change affects the people who have to live with it.
Tactics61% Judging
I commit to a date and renegotiate if I have to, instead of leaving the question open. Open loops are where projects stall.
Identity60% Assertive
Escalations and live demo failures do not rattle me much. My instinct is to fix the problem in the room.
I plan in commitments, and a date beats an open loop. Mind sits at a coin flip, which fits work that alternates between deep focus and customer rooms. And I count who a decision affects as part of whether it is the right decision.
I read for causes: what made a thing happen, or kept it from happening. That instinct is what took me to a History degree, and a second degree in Spanish language and linguistics gave it a structure to work inside. In software it shows up as seeing where the ball is going, then doing the legwork now so the product is already there when it arrives.
I'm a disciple of Clay Christensen's Jobs Theory. Nobody buys a product, they hire one, under a particular set of circumstances, to make progress they care about. Understanding that progress, and the conditions around it, is what customer obsession means to me when it isn't a buzzword.
9 years of enterprise sales across new business and account management. 3 years of sales leadership mentoring high-performing teams. 6x Awards Trip Winner for top sales performance.
2019 - 2020
Northwestern University
JavaScript, React, Node.js, SQL, HTML/CSS
2004 - 2010
Michigan State University
Bilingual English/Spanish
Codility 2025
Codility 2023
Codility 2022
2010-2019
Developer Portfolio
A developer portfolio is in progress, covering product engineering projects, architecture decisions, and AI implementation case studies. This section grows as new work is published.