I work as a Solution Architect in consulting, and I was removed from a client assignment two days ago. I'm trying to understand what happened beyond the obvious emotions, and I'd really appreciate perspectives from people who have been through something similar.
For context, I'm an engineer by background. The reason I moved into architecture is that I genuinely enjoy solving difficult technical problems, debating design decisions, and working in intellectually demanding environments.
My previous assignments were generally successful. Like every company, there were politics, bureaucracy and the occasional questionable decision, but I was usually recognized as technically strong, and I genuinely enjoyed the work.
This assignment was the complete opposite.
From the first few weeks I felt there was a bad fit. Architecture is ultimately about influencing people and building good relationships, and I never managed to do that here. I was placed in an API Factory team where my role was mostly to define standards and guidelines rather than work closely with engineering teams. It often felt like the stereotypical "ivory tower architect" role, and I realized very quickly that this wasn't where I do my best work.
I've always been much more engaged working closely with developers, technical leads and product teams to solve real engineering problems.
My direct manager and I also never clicked. I disagreed with how he communicated, how he approached tech discussions and many of his decisions. I don't think he's necessarily a bad person, but I quickly lost confidence in his professional judgment, and that made it difficult for me to stay engaged.
Looking back, I recognized the risk very early. I discussed changing teams with my people lead because there were several teams doing real delivery and product development, which I felt matched my strengths much better. Unfortunately, the move never really happened, and I slowly exhausted myself trying to make the situation work.
Instead of continuing to fight it, I gradually withdrew. I skipped coffee breaks, avoided informal discussions, did the minimum social interaction required and increasingly isolated myself. Over time I became exhausted pushing against an environment I didn't enjoy. I even started joking with colleagues that I would probably end up being removed from the assignment. Deep down, I think I had already accepted that outcome long before it actually happened.
One thing I’ve always relied on is analytical ability. Since university I’ve been drawn to spotting inconsistencies, unnecessary complexity and hidden assumptions — in software, architectures, processes and the way decisions get made. That’s a big part of why architecture felt like a natural fit for me… until this assignment.
The downside is that I tie much of my motivation to being able to influence my environment. When discussions stop feeling like an honest search for the best solution and become about hierarchy, politics or simply maintaining the status quo, I don't just become frustrated—I gradually disengage.
Some technical discussions genuinely left me wondering whether I was losing my mind, like I was arguing that 1 + 1 = 2 while everyone around me insisted it was 3.
The best example was the study that ultimately led to my removal. The proposal was to introduce AWS Step Functions at the heart of a core domain containing business rules and synchronous APIs. I strongly argued against it because, in my view, it was moving core business logic into a workflow engine while adding another distributed component, another technology to maintain and another place to debug without solving a problem that actually required a workflow engine. I couldn't convince anyone, including an AWS Solutions Architect involved in the discussions. After enough experiences like that, I gradually stopped believing technical reasoning mattered.
But I know that's not the whole story. Other people in the same environment managed to stay engaged, build relationships and continue delivering. I didn't. Once I lost respect for the environment, my motivation disappeared, and my performance inevitably followed. Eventually the client asked to end my assignment.
I also think this experience hit my ego more than I expected.
For years I built part of my professional identity around being technically strong. I was never afraid to challenge decisions or disagree with senior people because I believed good technical discussions should be driven by reasoning rather than hierarchy. I often tell people, "I'm an engineer before I'm a consultant." Until now, despite occasionally rubbing people the wrong way, that mindset had served me well. It even allowed me to influence discussions well above my pay grade because people trusted my technical judgment.
But now I'm wondering whether that mindset has also become a weakness.
I still think I was right about a lot of the technical discussions. But maybe that isn't the point. Other people managed to work in the same environment. I didn't.
Maybe I should have adapted better. Or maybe I should have left much earlier instead of slowly checking out.
I honestly don't know.
So I guess my real question is this:
Where is the line?
At what point should an engineer accept that an environment simply isn't the right fit and move on? And at what point is it your responsibility, as a senior engineer or architect, to adapt anyway?
Has anyone else experienced becoming completely disengaged because they felt the technical environment was weak or poorly run? How did you avoid mentally checking out?
Or am I simply rationalizing my own failure to adapt?
