Journey

Why this path, and not a straight line

None of this happened as a single decision. Each stage answered a question the previous one raised — a chain of reasoning, not a list of job titles and dates.

  1. Education

    Learning what a system actually is

    Mechanical engineering education is full of diagrams of systems that behave exactly as described. The gap I noticed early was between that and how systems actually behave once they're real — worn, imperfect, and interacting with things the diagram never accounted for. I didn't have a decision to make yet, but I came out of that education with a bias: I trust what a system does more than what it's supposed to do. That bias is the thread running through everything that follows.

  2. Maintenance engineering

    Working where mistakes are expensive

    Maintenance work put real consequences behind that bias. When equipment fails, guessing at the cause is expensive — in downtime, in cost, sometimes in safety. The challenge wasn't fixing individual failures; it was making sure the same failure didn't happen again. I made a deliberate decision to document root causes and procedures rather than just resolve issues as they came up, which is where authoring SOPs came from. The lesson was that a good process outlives any single fix — and that lesson is what I later applied to something that had nothing to do with machinery.

  3. Outside the job

    Getting curious about Generative AI

    Alongside that work, I got curious about Generative AI — first AI image generation, then AI video generation as the tools matured. It had nothing to do with mechanical engineering, and there wasn't an obvious course or program that fit how I wanted to learn it, so the decision was simple: apply the same method I already trusted — test it directly, read documentation, iterate on prompts, notice what actually works, adjust. The lesson here mattered more than the subject itself — it confirmed that the way I learn isn't specific to mechanical systems. It transfers.

  4. 2025 — Present · Independent Freelance Business

    Turning experimentation into a real business

    At some point the experimentation got good enough that I asked whether it could be built into a real business, which led me to Fiverr. That created a new challenge I hadn't faced before: I'd never run anything like this or managed a client relationship. I decided to treat it as a proper independent freelance business rather than a one-off gig — sourcing clients, pricing the work, gathering requirements, developing and iterating prompts, managing revisions, and being responsible for delivery, with international clients I never met in person. Reviews and delivered work are visible on my Fiverr profile. The lesson was about responsibility more than technique: once someone is paying you, "good enough" has to mean something concrete and repeatable, not just "it worked this time."

  5. Noticing the pattern

    Noticing what actually mattered

    As the practice became consistent — clients coming back, deliveries landing on time, the same people trusting me with more work rather than looking elsewhere — I started asking a different question: was the actual skill the specific craft, or the process behind delivering it reliably? The answer is what redirected my interest toward business operations and systems rather than staying focused on the original work itself — more than any single tool or technology, that question was the real turning point.

What these share

A few things every stage had in common

Where this leads

Current direction

My experiences have gradually moved my interests toward business operations, project execution, systems thinking, and long-term business leadership. None of that happened by planning it in advance — it's the direction that each of the stages above kept pointing toward.

For the detailed experience behind this journey, see the roles, dates, and responsibilities — or start a conversation if you'd rather skip ahead.