From finance to computer science

I started with a finance degree, then built a career in B2B sales, working with companies from small operators to large enterprises. People sometimes frame my move into software as a reset. It has not felt like one. It has felt like two things finally meeting.

Why I'm making the move

I've spent years close to software without building it. The longer I've sold and supported it, the more I've wanted to be on the other side of the table. I kept seeing systems I wished existed and had no way to make them, and closing that gap became the thing I cared about most.

A finance degree was good training

A finance degree teaches a way of thinking that transfers cleanly: leverage, risk, and the cost of being wrong. You learn to ask what happens in the bad case, not just the expected one, and to respect downside that is not symmetric. That is the same instinct behind designing an AI system to propose instead of act, or treating tenant isolation as an invariant. I added a Mathematics minor for the quantitative depth, and a lot of it rhymed with how I already thought.

What the transition taught me

• Learning fast under real constraints is its own skill. Coming in without a traditional CS background pushed me to build things in order to understand them.
• A perfect record in CS coursework matters less to me than the projects it freed me to attempt. The grades are a byproduct of taking the work seriously.
• Being early in a degree and early in seriousness are different things. I am early in one and not the other.

The convergence

My background is not a detour I am trying to explain away. It is the reason my engineering has a point of view. My years in sales tell me which problems are worth solving and what trustworthy software has to feel like. The CS, math, and systems work give me the means to build it. Agentic CRM is the clearest example: it solves a workflow I've watched break for years, built with architecture I had to learn from scratch. Neither half does that alone.