In the ever changing tech scene, changing careers is pretty standard these days,right? But let's be honest, it's rarely a smooth ride. My name's Gikunju, and I made the leap from being a dev to a design engineer. It's been a crazy mix of exhilarating highs and, frankly, a huge learning curve. After spending the last few years navigating this path, I've really started to grasp the unique complexities of design. I honestly believe it's far more intricate than anything I dealt with in pure development. So, here's my story: what that transition was like, everything from the hurdles I faced, and why design has revealed itself to be such a deeply complex craft.
From Code to Creativity
For years, I was right there in the thick of it as a dev. My world was pretty straightforward: code either worked or it didn't. Success felt simple. If a program compiled and met its requirements, that was a win in my book. Bugs were annoying, sure, but they were tangible problems with logical solutions, often stuff you could even Google for a quick fix, lol. When I decided to pivot into design engineering, I was really drawn by the promise of more direct creative input and the chance to shape user experiences from concept to execution. I honestly thought my solid technical background would give me a significant head start, and boy was I in for a rude shock.
The transition, I won't lie, was a shock to my system. In development, my metrics for success were concrete: did the feature work as intended? In design, though, I found myself navigating this much murkier landscape. My very first big project involved redesigning a mobile app's onboarding flow. I dedicated hours into coming up with what I thought was this really intuitive, visually appealing experience. Only to get feedback like "it doesn't quite feel right" or "can you make it more engaging?" These vague responses left me totally struggling to interpret what they needed. It was such a sharp contrast to the precise error messages and clear requirements I was used to as a dev which I could at times Google and 70% of the time Stackoverflow would have my back- convenient, right?.
The Demands of Design
One of the biggest challenges I've hit is the sheer emotional investment that design work demands. As a dev, I cared about my code, absolutely, but I could maintain a certain professional distance. A failed build wasn't necessarily a reflection of my identity or worth. Design, however, feels really personal. Each wireframe, palette and layout choice I make feels like an extension of my creative vision. So, when a stakeholder critiques a design, it kinda feels like a critique of me- it's a sentiment I've heard echoed by countless other designers in my network and even across social media.
This emotional aspect gets even tougher with the constant pressure to deliver, often under tight deadlines. In development, I could follow a ticket, write code, and move on. But as a design engineer, I'm often tasked with advocating for the user's needs, even when leadership provides close to nothing in terms of direction. I can just be told, "We need this feature designed and built," and it'll be entirely up to me to not only figure out what the user truly needs but also how to translate that into a feasible, functional product. It's a responsibility that feels both incredibly empowering and, at times, daunting.
Another major hurdle has been dealing with subjective feedback. In development, feedback was pretty straightforward: "This function is broken, fix it," or "The API response time is too slow, let's aim to make it faster by at least this much" In design, I'm often met with ambiguous comments like "it's missing something" or "it doesn't pop." Learning to interpret and act on such nebulous feedback while still having confidence in my own work has been a constant mental balancing act. It can definitely leave you feeling drained.
Why Design Holds More Depth Than Development
Through this whole transition, I've come to believe that design is inherently more complex than development. Development operates within a defined framework. You have clear rules, syntax, and measurable outcomes. Design, on the other hand, requires balancing multiple, often conflicting, dimensions: aesthetics, usability, business objectives, and deeply understanding user psychology. It's not just about creating something visually appealing, it's about considering the user journey, listening to feedback, and balancing human psychology against what the data actually says. That multidisciplinary nature makes design a far broader challenge than simply writing code.
What's more, design fundamentally lacks the binary clarity of development. Code either works or it doesn't, easy. But design exists on a spectrum from "good enough" to "exceptional," with the difference often hinging on subjective interpretation and taste. I've had to learn how to justify my design choices and advocate for them, while also being open to iteration. This is a skill I rarely needed as a pure dev. This ambiguity can be exhilarating(especially since it at times comes with carte blanche), pushing creative boundaries, but it's also mentally exhausting, because you're constantly navigating uncertainty.
This becomes even more apparent in my daily work as a design engineer. My role specifically involves translating creative mockups into functional products, making sure the artistic vision aligns with technical constraints, navigating both the artistic and technical sides of a project at once. I'm not just handing off designs, I'm deeply involved in their implementation, seeing firsthand how much work it takes to bridge that gap. It's only deepened my appreciation for how complex the entire design process is, from that initial concept to the pixel-perfect code.
The Burnout Factor
The intense emotional and intellectual demands of design have also made me keenly aware of burnout. As a dev, I could step away when I hit a wall. There was always another day to debug a problem or write a new function. But as a designer(and particularly as a design engineer who has to balance both the creative and technical demands) I feel a constant pressure to be "on." I'm always delivering creative solutions on demand and figuring out their technical feasibility. The constant need to juggle between subjective feedback, and tight deadlines has taken a significant toll. More often than I'd like to admit, there've been moments where I've genuinely questioned whether the career shift was the right move, especially on days when I feel like I'm giving it my all only to have it picked apart by vague critiques with zero direction.
Would I do it again?
YES- honestly, there's a unique reward in design that just keeps me going, a certain level of satisfaction. Seeing a user interact with a feature I've designed, and witnessing their genuine delight, is a feeling I rarely experienced as a dev. Design may be more complex, but it's also far more human, more directly connected to the people I'm creating for.
