What Core Values Mean for Engineers
Your core values are the standards you use when no one is watching and the stakes are real. For engineers, this might mean choosing to refactor legacy code that slows down the whole team, even though it's not on the sprint. It might mean pushing back on a deadline you know is impossible, or speaking up when a design decision will cause problems downstream. These aren't abstract ideals. They're the reasons you make the choices you make.
Most engineers inherit their values without examining them. You picked a company because the salary was good or the office was close. You stay in a role because it pays the bills. You accept the technical debt someone else created and move on. But when your work stops matching what you actually believe in, everything gets heavier. The code doesn't feel like yours anymore. The team frustrates you in ways you can't quite articulate. You start wondering if you're in the wrong job or the wrong industry.
The Gap Between What You Say and What You Do
Engineers often claim to value quality, but work in systems where shipping speed matters more. You say you want to learn, but your team treats you like a specialist you can't escape. You believe in collaboration, but you spend most days writing code alone in a quiet room. These aren't failures of character. They're signals that what you're doing doesn't actually reflect what matters to you.
The problem is that values aren't discovered in a conference talk or a career coaching session. They emerge from paying attention to when you feel energized and when you feel drained. When did you last feel genuinely satisfied with your work? It probably wasn't when you shipped something fast. It was when you solved something hard. Or when you helped someone else understand a complex system. Or when you built something that lasted. That moment tells you something about what you actually value, not what you think you should value.
Why This Matters Right Now
You're probably reading this because something feels off. Maybe you're burned out and can't explain why a job that looked perfect on paper feels hollow. Maybe you're considering a move and want to make sure the next place is different. Maybe you're early in your career and want to avoid building a life around the wrong things.
The engineers who stay sane and satisfied tend to have done this work. They know whether they're driven by mastery, autonomy, impact, stability, mentorship, or something else entirely. When they make a decision about a job, a project, or how to spend their technical energy, they can answer a simple question: Does this align with what I actually care about? If the answer is no, they either change what they're doing or they understand the cost of the compromise.
This doesn't mean you need to find a perfect job where everything aligns. That job doesn't exist. But it means you stop being surprised by your own discontent. You know why you're frustrated. You know what trade-offs you're making. You can decide whether it's worth it.
Starting the Conversation with Yourself
Identifying your core values requires some friction. Not the painful kind. The useful kind. You need to think about the times you felt proud of your work and the times you felt like you were wasting your time. When a senior engineer took you under their wing, was that what made the role matter? Or did it matter because you were building something that solved a real problem for real people? When you left a job, what were you actually running from?
These questions don't have right answers. Your values are not better or worse than someone else's. An engineer who values financial security and chooses a stable job at a large company is not less idealistic than one who values autonomy and joins a startup. They're just different. The problem comes when you pretend to have one set of values while you're actually operating from another.
The My Values assessment can help you cut through the noise and name what actually matters to you in your career. That clarity changes everything. It doesn't solve the real structural problems in your industry or your workplace. But it gives you the ground to stand on when you're making decisions. And it's the first step toward building a career that feels like yours, not something you fell into.
How do core values differ from skills in engineering?
Skills are what you can do. Values are what you believe should matter when you're doing it. You might be skilled at writing code fast, but if you value quality, that skill creates tension every day. Skills can be learned and forgotten. Values tend to be consistent across your entire life.
Can your core values change over time?
Yes, they often do. Junior engineers frequently discover that what mattered to them early in their career shifts as they gain experience. Someone might prioritize learning above all else at 25, then shift toward stability and mentorship at 35. The key is noticing when your values have changed and adjusting your career accordingly.
What if your company's values don't match yours?
You have three options: change what you do within your current role, change your role or team within the company, or change companies. The first option works when the misalignment is local. The second works when the problem is cultural but not company-wide. The third is necessary when the mismatch is fundamental and not negotiable.
How do I know if I'm compromising too much?
Pay attention to whether you're making a conscious trade-off or whether you've stopped noticing the compromise at all. If you can articulate why you're staying in a job that doesn't fully align with your values, that's fine. If you can't remember what your values were anymore, that's a warning sign.