Leadership is disconnected from the day-to-day realities of engineering and consistently ignores feedback, even when delivered through formal channels or exit interviews. Concerns about technical debt, product instability, unscalable processes, and unrealistic timelines are raised repeatedly—only to be ignored until they escalate into critical issues that impact revenue or delivery. The operating model is reactive, not strategic. The cycle repeats.
The absence of strong technical leadership creates a leadership vacuum, with overuse of management frameworks that don't fit the needs of the team. For example, weekly “Traction” meetings—intended to enforce cross-functional alignment in much larger organizations—feel unnecessarily rigid and out of sync with the needs of a lean software team. These meetings often reduce engineering time to box-checking rather than driving meaningful progress.
Leadership frequently speaks about “quality” and “trust” as values, but these words are rarely supported by meaningful investment. The QA function is under-resourced, leading to major gaps in coverage. Testing is often manual, inconsistent, or skipped altogether. As a result, quality assurance falls disproportionately on engineers—who are already stretched thin—and many product issues that could have been avoided with better testing practices end up in production. Leadership continues to say “quality is our top priority,” while failing to staff or empower teams to deliver on it.
Instead of removing friction, leadership adds more layers of process. Planning cycles are bloated, status updates frequent, and tracking systems like Monday.com are used obsessively. Engineers are pulled into a never-ending loop of check-ins, retros, planning sessions, and alignment meetings that do little to drive outcomes. The obsession with frameworks and optics creates an illusion of control, while engineering velocity suffers.
Some employees embrace this system fully, often referring to time spent with the Executive Team as a marker of status. This creates a culture where proximity to leadership is equated with competence, and where asking difficult questions is seen as disloyal rather than constructive. Engineers who push back against inefficiency are often labeled as “not a cultural fit” instead of being recognized for their insights. Conformity is rewarded; critical thinking is not.
The engineering team skews junior, with a heavy reliance on offshore contractors who face communication and collaboration barriers. Compensation is below industry standards, making it difficult to hire or retain experienced talent. The result is an overburdened and under-supported engineering organization where those who stay are often spread thin, siloed, or disengaged.
Culturally, the organization is fractured. Teams outside of leadership’s inner circle are marginalized, and cross-team collaboration is rare. There is no unified technical vision or coherent architectural strategy. Excessive emphasis is placed on alignment—engineers are pulled into meeting after meeting to ensure everyone is “on the same page,” yet actual collaboration and execution suffer. New teams and hires are brought in with minimal onboarding or trust-building, and expected to conform to a slow, rigid system. The result is disengagement, fatigue, and a growing sense that time spent talking about the work has replaced doing the work. Morale is low.
There is an overwhelming focus on short-term wins, investor optics, and surface-level metrics—often at the expense of long-term product quality and team stability. Feedback loops are weak, accountability is uneven, and engineers are left to navigate an environment where leadership’s promises rarely translate into action.
