How Much Does Company Alignment REALLY Matter For Developers?

Dev Leader Weekly 131

Mar 15, 2026

TL; DR:

Mission alignment shapes how engaged you are daily
Understanding why your work matters is underrated
Reflect on what engages you, then align your search
Join me for the live stream (or watch the recording) on Monday, March 16 at 7:00 PM Pacific!

Does It Matter If You Believe in What Your Company Does?

I came across a post on the ExperiencedDevs subreddit that I found genuinely interesting -- and if I’m being honest, it hit pretty close to home because I was already thinking about this exact topic.

The Redditor described how they used to work at a company in the music industry. They were engaged. The work felt meaningful. They cared about what they were building and why. Then, over time, structural issues at the company led them to move on. Now they’re working in some legacy tech space, and they realize -- almost with some shock -- how much that previous alignment had been fueling them. Without it, they’re just... not feeling it. They don’t care about what the company does. And it’s making it hard to be enthusiastic about the work.

That’s a real thing. And it’s worth talking about.

You can check out my full thoughts on this in the video below:

Not Everyone Is In The Same Place -- And That’s Okay

Before I get into the substance of this, I want to be clear about something: I’m not here to tell you what you should value in your career. That’s shaped by your life experiences, your stage in life, your financial reality, and a hundred other things. It’s not my place to say you’re doing it wrong.

If you’re early in your career and your only goal is to get your foot in the door -- I get it. Completely. Your focus is survival, not fulfillment optimization. That’s entirely reasonable. The stuff I’m going to talk about may not be relevant to you right now, and that’s fine.

My point in wanting to explore this is that over the course of a career -- which is most of your adult life -- this stuff starts to matter more. The things that engage and disengage you will shift over time. What you value at 22 is probably not what you’ll value at 42. But if you’re going to spend a massive chunk of your life working, it’s worth at least thinking about whether you’re spending that chunk somewhere that feels meaningful to you.

The “Fulfillment Across a Career” Framing

Here’s the framing I keep coming back to: most of our adult lives are spent working. If you don’t have a shortcut out of that equation -- and for most of us, that shortcut isn’t on the table -- then optimizing for fulfillment over the long arc of your career just makes sense.

Now, I know what some of you are thinking: “Cool, sounds nice on paper.” And I hear you. If you’ve never worked somewhere that felt engaging, you have no evidence that it can be otherwise. Your lived experience says it’s just work, and work is fine, and the fulfillment comes from what you do outside of it. I don’t disagree with that framing either -- if you can minimize time at work and maximize everything else, great. Fulfillment is the goal. How you get there is up to you.

But for me personally, I do want to optimize my career around fulfillment. I like being productive. I like making progress toward things. So I want to make sure that, for a large chunk of my life, I’m doing work that feels worth doing.

What Alignment Actually Looks Like

Here’s something I’ll be honest about: I don’t know that I would have predicted what would feel aligned for me until I was in it.

Early in my career, I got into digital forensics. I was very fortunate that things lined up the way they did -- there was too much serendipity for me to take much credit for it. But that work was deeply fulfilling in a way I don’t think I’ll easily replicate. There was a sense of impact that felt very real and very direct.

Now I’m at Microsoft, working on the routing plane for Office 365. The scale is completely different. Orders of magnitude more scale. And because of that scale, even small things can have massive impact. We were talking recently on one of my teams about a C# optimization -- something on the order of 1% reduction in memory allocations for a particular path. On its own, that sounds like nothing. But at the scale this service runs, that 1% ripples out to millions of users. The numeric impact is way larger, even if the perceived impact feels different.

Neither of those experiences is objectively better. They’re just different ways fulfillment can show up. The question is whether you take the time to notice.

The Manager Angle: Always Explain the Why

I haven’t talked about this in a while, but as an engineering manager, this concept of alignment plays out in a really concrete way for me. And I want to share it because I think it applies whether you’re a manager or an IC.

In most engineering conversations, we focus on the what and the how. What’s the feature? What’s the architecture? How are we going to implement it? What are the constraints? Those conversations are totally valid and necessary. But there’s a gap.

The gap is why.

Why does this work matter? “It moves this metric from point A to point B” is not why -- that’s a measure. The why is what the metric actually represents for users, for the team, for the broader mission.

I’ve told engineers on my team explicitly: if at any point you don’t understand why we’re doing what we’re doing, tell me. It’s not a confrontational thing. It doesn’t have to be “I think this is dumb.” It can just be “I know what we’re building and how, but I’m missing the bigger picture of why it matters.” I want that conversation to happen. Because if people don’t get why, they stop seeing how they’re contributing to something meaningful -- and over time, that erodes engagement.

Actionable Tip: If you’re a manager or lead, don’t just share the what and how with your team. Zoom out regularly and explain why the work matters -- how it connects to users, to the mission, to something real. It’s not about making every task feel earth-shattering. It’s about helping people see the bigger picture.

What Should You Do If You’re Not Feeling Aligned?

Back to that Redditor. They’re not aligned with what their company does, they’re not engaged, and they’re wondering if they should brush up on their resume.

My take: yeah, look around. But that doesn’t mean you have to rush out the door. If the current situation isn’t actively negative -- you’re being treated fairly, the pay is reasonable, it’s not toxic -- then you don’t need to panic. But I’d absolutely encourage shopping around. The only cost is your time, and that’s yours to decide how to spend.

Actionable Tip: Do an honest reflection on what engages you and what doesn’t. Think about the industry, the tech, the team culture, the problem space. Think about what you do outside of work that you genuinely love. You don’t have to go find a job in exactly that space -- but you might notice patterns about what kinds of problems and environments light you up versus drain you. Use that as a filter when evaluating opportunities.

For that Redditor -- and for anyone in a similar spot -- the reality is that if you fundamentally don’t care about what your company does, you’re probably not doing your best work. Not because you’re lazy or uncommitted, but because that underlying engagement isn’t there. The only motivation left is the paycheck, and that sustains you for a while, but it’s not enough to fuel your best output over the long haul.

Wrapping Up

None of this is me telling you your career needs to be your entire source of meaning. It doesn’t. But if you’re going to spend a huge chunk of your life working, it’s worth asking whether the work you’re doing is pointing you toward something you actually give a damn about.

The things that engage you will shift over time. That’s fine -- that’s expected. The goal is to stay aware of what those things are and make deliberate choices, rather than just drifting from one unaligned role to the next.

If you’ve got questions about this stuff -- career decisions, engineering management, whatever -- you can always head over to codecommute.com and submit anonymously.

Dev Leader Weekly

Discussion about this post

Ready for more?