A Web Team in Decay — Technically Functional, Strategically Dangerous
Pros
• If you’re looking for a zero-stress job where deadlines are vague and performance is barely tracked, this team offers exactly that. • There’s no pressure to grow, no fire drills, no tension — just ambient work at a slow, manageable pace. • Psychological safety is strong, though it’s used more to preserve comfort than to enable creativity or high-trust collaboration. • There is still some merit to joining a company like this. If your priority is to coast, avoid stress, and preserve work-life balance above all else, this team technically delivers that. But be fully aware: this isn’t just coasting — it’s bottom-of-the-bucket territory. The technical skill, effort, and standards here are shockingly low. You will encounter things that are incredibly dysfunctional, to the point where even basic honesty and accountability feel optional. It’s below even the slowest defense contractor environments — at least those have structure and discipline. Here, you’ll see things that make you question how the place even functions. • The CTO is intelligent, energetic, and genuinely believes in EverCharge’s mission. His passion is real — even if the team under him doesn’t reflect it. • There are a few individuals on the web team with real technical skill and professional integrity — people who could succeed in a high-performing environment. But they are the exception, not the norm. The majority of the team is clearly here to coast, doing the bare minimum under leadership that rewards inertia.
Cons
• This review focuses on the web software team, which is responsible for both end-user interfaces and B2B operational tools like charger provisioning, fleet management, and backend access. These systems are especially brittle, outdated, and neglected. • The team is technically functional — but just barely. What should take a week routinely takes months, due not to complexity but to sheer lack of urgency, feedback loops, or accountability. • The B2B software is mission-critical, but it’s treated like a secondary concern. Work is done slowly, sloppily, and never questioned. • EverCharge is a portfolio company of SK Group, a massive multinational conglomerate with a wide investment footprint. SK knows that EverCharge is underperforming overall, but they have no visibility into how dysfunctional and ineffective the software team is specifically — especially the web team. The core engineering engine is not just underwhelming — it’s quietly hollow. That should be a major red flag for any parent company betting on long-term upside. • The company is not profitable. Its continued survival depends on future growth and investor confidence — which makes it all the more alarming that a core engineering team is this inert. • A company in this position cannot afford to operate like this. It doesn’t have the margins, prestige, or product-market fit to support a low-performing engineering group. SK Group, the parent company, has a giant portfolio and can absorb many things — but it is also under pressure. It needs winners. EverCharge’s dysfunction doesn’t just hurt itself — it reflects poorly on the entire portfolio. If cuts come, this team is an easy candidate. • Web team leadership is permanently remote — not because of company policy, but because of personal exception. They work from Hawaii and have been known to take time off during workdays to play golf, not once or twice, but as a recurring pattern. This isn’t flexibility — it’s disengagement. Their physical and mental distance from the team reflects a complete absence of leadership. They are entirely disconnected from the product, the process, and the team’s actual output. • The rest of the team is hybrid or onsite. This double standard reflects the deeper issue: web team leadership does not care about the mission or the product. • Ask yourself plainly: Does managing a web team from Hawaii while golfing reflect strong engineering leadership? Of course not. It reflects prioritizing personal comfort, not product impact. • They’re not here to build something great. They’re here to protect their jobs by removing stakes, avoiding confrontation, and hiring engineers who won’t rock the boat. • The reason the team hasn’t fallen apart is because they’ve lowered the bar to the floor. Everyone is safe — but nothing gets better. • One engineer regularly lied about task completion and shipped broken code. A colleague raised the issue through proper channels — but instead of addressing the dysfunction, leadership removed the whistleblower. That’s how fragile and self-protective this structure is. • There’s no mentorship, no design reviews, no push for quality, no technical standards. Just stale Jira tickets and layers of process pretending to be structure. • If you care about growing as an engineer, you will stagnate here completely. This is where technical skills go to rust. • Promotions don’t go to the sharpest minds — they go to the people with the right relationships. The most valuable engineers, the ones keeping the company from falling apart, don’t occupy the most senior ranks. The lead staff engineer can barely write Python, the team’s primary language, and spends most of their time jumping between greenfield TypeScript projects to avoid working on the main codebase. It’s avoidance dressed up as innovation. • The CTO has worked on cutting-edge, meaningful projects in the past — yet he’s now surrounded by a team that does just enough to avoid attention. • He’s not complicit — he’s disconnected. Web team leadership has worked hard to maintain a surface-level calm, masking the decay underneath. They ensure the team appears stable, even as its output weakens and talent erodes. • And because SK Group doesn’t see the day-to-day, the team continues to exist on borrowed time and blind trust. That’s not stability — that’s strategic debt.
