I rarely write reviews for a former employer, but I feel a responsibility to share my experience for anyone considering a technical role here, especially if relocation is involved.
There are capable individuals in the organization, but the broader environment made it extremely difficult to be effective.
Key concerns:
*Significant technical debt and stagnation - Core systems and platforms are aging, with limited forward movement. Necessary upgrades and modernization efforts are delayed or deprioritized, increasing operational risk over time and making it difficult to attract or retain skilled technical talent. Lack of regular maintenance opportunities limit the ability to patch or upgrade systems. This effectively translates into an IT strategy that is “stagnation by design”.
*Leadership communication and transparency: Strategic modernization messaging was often ambitious and compelling, but it did not translate into actual execution.
*Risk adverse culture and lack of alignment throughout leadership: While strategic messaging is modernization, leadership throughout the company does not align regarding these initiatives. The company is "risk adverse" which results in lack of forward movement to reduce technical debt in core systems, cements the technical stagnation and prevents modernization.
*Misalignment between role expectations and operating model-The role was presented as involving direct contribution to modernization initiatives; however, the routine delivery model assigns project work primarily to external consulting partners (often offshore), with internal roles focused on coordination and oversight and routine production support. This represents a materially different scope than communicated during hiring.
*Incentives that discourage initiative- The environment tends to favor compliance over initiative, discouraging proactive problem-solving and limiting continuous improvement. Strong performers are relied upon to carry critical work, while underperformance is often tolerated and, at times, reinforced. This results in inconsistent accountability.
*Resistance to technical expertise-Clear, evidence-based analysis was frequently overlooked in favor of less informed input, slowing resolution and increasing risk.
*Centralized decision-making limiting effectiveness: Decision-making authority is highly concentrated, often with limited openness to alternative perspectives or technical input. This creates bottlenecks, reduces effectiveness and limits autonomy of experienced team members.
*Compensation and performance alignment concerns: Compensation and performance outcomes appear standardized to mid-range ratings, low pay increases, and lack of promotions even in cases of significant contribution, which may not align with expectations for high-impact roles.
*Operational friction and unclear ownership: Frequent management changes contributed to unclear ownership, inconsistent decision-making, and avoidable friction in day-to-day work.
*Work-life balance expectations: Despite HR statements that there is a planned week off between Christmas and New Year’s - it does not apply to IT. This was later reinforced by the CIO as a standard expectation for IT roles. They scheduled work over holiday breaks without validating that personnel is available - it is expected that you are. Work expectations routinely extend into all holidays.
*High turnover: Multiple core team members exited within a short period, which should be considered carefully when evaluating long-term stability.
Advice to candidates:
*Clarify how work is divided between internal teams and external partners
*Ask direct questions about modernization plans and technical ownership
*Get role expectations, project scope, and roadmap commitments in writing, especially if relocation is involved
*Pay close attention to how technical input is received during interviews
*Validate alignment between leadership priorities and actual execution
