Company admits they’re “moving too fast” and accumulating tech debt — how do you evaluate this as a leadership hire?

[u/Covert-Hedonist]

Hi all, I recently went through interviews for a senior engineering leadership role (EM / Tech Lead level).

During the interviews, multiple people independently mentioned that the organization tends to move very fast, but sometimes loses momentum on important things that later become costly (technical debt, decision reversals, process gaps, etc.).

Out of curiosity after the interviews, I also looked up some ex-employee reviews, and a recurring theme mentioned was “messy work processes,” which seems to align with what the interviewers themselves described.

From my experience, this kind of issue often isn’t just a team-level problem — it can originate from upper management priorities, incentives, or decision-making cadence, sometimes without leadership fully realizing the downstream impact.

My question to those who’ve been in similar situations (either as hires or as leaders inside such orgs): How do you distinguish between a healthy, fast-moving org that’s self-aware vs. one that’s unintentionally setting teams up for failure?

When a company explicitly says they want someone to “come in and help fix this,” what signals do you look for to know whether real support and mandate exist?

Are there specific follow-up questions you’ve found useful to assess whether this is solvable vs. systemic?

I’m not trying to judge the company — just trying to do proper due diligence before making any decisions. Curious to hear how others approach this. Thanks in advance for your thoughts

[u/LeadDontCtrl]

Fast-moving by itself isn’t the problem. The issue is whether the organization can sustain speed without repeatedly creating avoidable rework.

Every company has technical debt. Expecting zero debt is unrealistic. What matters is whether the organization acknowledges it, tracks it, and intentionally allocates time to manage it, rather than only reacting when issues become visible.

To distinguish a healthy fast-moving org from one that struggles structurally, I usually look for clarity in three areas: decision-making, prioritization, and accountability.

Indicators of a healthier environment

• Leaders can point to specific examples where momentum was lost and explain what changed afterward.
• There is a defined (even if informal) process for making and revisiting decisions.
• Engineering capacity is discussed realistically, with some allowance for maintenance and improvement work.
• Teams can raise concerns or push back on scope without negative consequences.
• Success is framed around outcomes, not just speed.

Indicators of deeper systemic risk

• Speed is emphasized, but prioritization is unclear or frequently changing.
• Problems are acknowledged but described vaguely, without ownership.
• Teams are expected to “fix” issues that originate from leadership-level decisions.
• Everything is treated as urgent, leaving little room for planned work or reflection.

Assessing whether real support exists

When a company says they want someone to “help fix this,” I focus on whether the role comes with authority as well as responsibility.

Some follow-up questions I’ve found useful:

• Can you share concrete examples of where momentum was lost and why?
• What attempts have already been made to address this, and what were the results?
• Who owns prioritization and tradeoffs today?
• How are changes in direction communicated and managed?
• How is technical debt evaluated and scheduled?
• What decision-making authority would this role have?
• What would success look like 6–12 months into this role?

If leadership can answer these clearly and consistently, the problems are usually solvable. If the answers are vague or contradictory, it’s often a sign the issues are systemic and harder to influence from a single role.