Engineering to MBA
I am a software engineer and incoming MBA candidate at the University of Nottingham.
My work so far has focused on backend systems, SaaS platforms, integrations, technical documentation, testing, and developer-facing workflows. I enjoy the craft of building reliable systems: understanding ambiguous requirements, breaking them down, designing sensible abstractions, and turning them into something teams can use.
Over time, I have become increasingly interested in the questions that sit around the code.
Why are we building this?
Who does it help?
What tradeoffs are we making?
How does a technical decision affect the product, the customer, the team, and the business?
How do good systems become valuable products?
That curiosity is what led me toward an MBA.
Why the MBA
Engineering has taught me how to think in systems. It has trained me to debug, decompose problems, reason through constraints, and build with precision.
But I want to pair that technical judgment with stronger business, product, and strategic thinking. I want to understand how companies make decisions, how markets shape products, how teams allocate resources, and how technology creates measurable value.
The MBA is a way for me to step back from implementation alone and develop a broader view of business, leadership, strategy, and execution.
What I am building toward
I am especially interested in roles where technical complexity needs to be translated into product decisions, operational priorities, and business outcomes.
Areas I am exploring include:
- Product management
- Technical product management
- SaaS strategy
- Platform and internal tools
- Technology strategy
- AI-enabled workflows
- Business-facing technical leadership
I am drawn to work that requires both technical depth and commercial awareness: understanding what is possible, what is useful, what is valuable, and what is worth building.
What I bring from engineering
My technical background gives me a practical understanding of what it takes to build and maintain software systems.
I have worked with backend services, APIs, GraphQL, databases, integrations, testing, observability, and reliability concerns. I have also worked on documentation and team enablement: making systems easier for others to understand, use, maintain, and explain.
That combination matters to me. Good products are not only built through code. They are built through shared understanding, clear tradeoffs, reliable execution, and communication across teams.
What I am preparing for
Before beginning the MBA, I am using this period to prepare deliberately.
I am reading around product management, strategy, business models, finance, operations, and technology-led transformation. I am also studying companies, annual reports, competitive positioning, risks, financial performance, and the ways technology businesses create and defend value.
This page is a record of that transition: what I am learning, what I am thinking through, and how I am connecting my engineering background to the next stage of my career.
Areas I am exploring
- How SaaS businesses grow and retain customers
- How product teams prioritize under uncertainty
- How technical debt becomes a business problem
- How internal tools improve operational leverage
- How AI changes workflows, teams, and product strategy
- How technology companies build durable competitive advantage
- How engineers can become better business and product thinkers
Open to conversations
Part of this transition is learning from people who have already walked parts of the path I am trying to understand.
I would be glad to connect with Nottingham alumni, MBA candidates, product managers, technical product leaders, founders, consultants, and UK-based technology teams.
I am especially interested in conversations about product management, SaaS, platform products, internal tools, AI-enabled workflows, and the move from engineering into broader business leadership.