There is a familiar story about technical founders: brilliant at building, uncomfortable with selling, and forced to unlearn the habits of engineering before they can lead a company. It is a story with some truth in it. But it misses something important. The disciplines that make a good software developer — breaking problems into parts, testing assumptions, respecting evidence over enthusiasm — are not obstacles to entrepreneurship. Properly extended, they are among its most reliable foundations.
Ahmad Athamneh's career offers a useful case through which to examine that idea. It begins with a degree in information technology, passes through years of development and technical consulting, includes a business education at Oxford and a period in digital marketing at a global platform, and arrives at a portfolio of ventures spanning live streaming, an exhibition venue, artificial intelligence and digital assets. The path is not unusual in its individual steps. What is instructive is the way each step changes the meaning of the ones before it.
The engineer's inheritance
Software development teaches a particular kind of honesty. Code either runs or it does not; a system either handles the load or it fails in front of its users. The developer learns early that confidence is not evidence, and that the gap between a plausible design and a working product is where most of the real work happens.
Three habits from this discipline travel especially well into business. The first is decomposition: the instinct to break a large, ambiguous goal into smaller problems that can be understood and solved. A venture is, in this sense, a system — of customers, incentives, operations, technology and capital — and its problems yield to the same patient analysis.
The second is iteration. Engineers rarely expect to get things right the first time. They build, test, observe and refine. Founders who carry this habit into strategy are less likely to fall in love with a plan and more likely to notice when the market is telling them something different.
The third is a respect for failure modes. A good engineer asks not only how a system works but how it breaks. In business, this translates into a sober view of risk — regulatory, operational, reputational — that is often absent from more optimistic forms of entrepreneurship.
What engineering does not teach
If the engineer's habits are an inheritance, they are not a complete education. Technical training tends to treat requirements as given. Entrepreneurship requires discovering them — understanding what people actually need, what they will pay for, and what will make them return.
This is where experience outside engineering becomes formative. Work in digital marketing, for example, is fundamentally work in understanding audiences: how they discover content, what earns their attention, how culture and language shape what resonates. For someone trained in systems, it is a lesson in the variables that do not appear in a specification.
Formal business education adds another layer: the language of capital, organisational design and strategy. An MBA does not make anyone an entrepreneur, but it can supply frameworks for questions engineers are rarely asked — how to value an opportunity, how to structure an organisation, how to think about competition over a horizon of years rather than release cycles.
The consultant's apprenticeship
Between pure engineering and founding a company lies an underrated stage: consulting. Technical consultants are invited into organisations at moments of consequence — when a system must scale, a service must be modernised or a platform must be built under scrutiny. They see many organisations from the inside, often in a short time, and they learn to read institutional context as carefully as technical architecture.
Contributing to large-scale digital service platforms, in particular, offers lessons that are difficult to acquire any other way. Reliability becomes a moral obligation rather than a metric. Coordination across many teams becomes the central challenge. And the consultant learns that the best technical answer is not always the one an institution can adopt — a lesson every founder eventually meets when negotiating with partners, regulators or large customers.
The founder's turn
At some point, many people with this kind of background face a choice: continue to build and advise on systems owned by others, or start something of their own. The decision is rarely about technical ability. It is about appetite for a different kind of responsibility — for payroll, for strategy, for the consequences of decisions that cannot be escalated to someone else.
Founding a live-streaming platform, as Ahmad did with YouLive in 2019, illustrates how the earlier stages combine. A live platform is technically demanding, culturally sensitive and economically delicate. It needs engineering that performs in real time, an understanding of how audiences and creators behave, and a business model that rewards participants fairly. None of the earlier experiences would be sufficient on its own; together, they form a plausible foundation.
From one company to a portfolio
The later stages of such a career often widen rather than deepen. Ownership of an exhibition business, active ventures in healthcare and education technology, and an exchange platform in development may look like scattered interests. Viewed through the engineering lens, they share a structure: each is a system connecting participants who need to find, trust and transact with one another.
This continuity matters because it shapes how ventures are evaluated. The questions are consistent: Is the underlying problem real? Can the system be built to the necessary standard? Who carries the risk, and is that fair? Are we being precise about what exists today and what remains a plan?
Five habits worth carrying across
For engineers considering a similar path, these habits tend to matter most:
- Treat your technical habits as assets, not liabilities. Decomposition, iteration and respect for evidence are rare in markets that reward storytelling. Use them.
- Seek deliberate exposure to what engineering omits. Roles in marketing, sales, operations or consulting teach the human and institutional variables that determine whether technology matters.
- Value the apprenticeship of consulting. Seeing many organisations from the inside is an accelerated education in how decisions are actually made.
- Be precise about status. A founder's credibility rests on clear distinctions between what is operating, what is in development and what is still an idea.
- Choose problems where your combination of skills is unusual. The most defensible position for a technical founder is often at the intersection of disciplines that rarely meet.
Engineering, extended
The journey from software development to entrepreneurship is sometimes described as leaving engineering behind. A better description is that engineering expands — from systems of code to systems of people, incentives and institutions. The founder who makes that transition well does not abandon the developer's discipline. They apply it to larger and more consequential problems, and they combine it with the understanding of markets and people that the code alone could never supply.
Editorial analysis and commentary. This essay does not quote interviews or report announcements.