Pros
I joined FNZ in 2015 and stayed for almost six years. During that time, I grew across several roles and FNZ was the place where I learned some of the most formative professional and personal lessons of my life. In the early years, the culture was exceptional. We worked hard, but we worked together. The technology hubs were vibrant, the teams were deeply connected, and the sense of shared purpose was real. FNZ’s vision in those years was strong enough that many of us weren’t just “employees” — we were genuinely invested in the mission. Senior engineers, long-timers, and vision-driven colleagues carried the culture with pride and integrity. I am grateful for my years at FNZ. They shaped me professionally and personally. I carry deep respect for the mission, the early culture, and the extraordinary colleagues I worked with.
Cons
Where Things Became Challenging The challenges began as the company scaled aggressively. While the workforce grew, the gap between middle management and senior management widened significantly. By 2019–2021, the main issues were: Capacity planning became detached from delivery reality. Teams were pushed to deliver under increasing pressure without being part of resource decisions or roadmap planning. Middle management bore responsibility without authority. We were accountable for delivery quality but not present in the governance layers where decisions were actually made. A veil formed between C-level leadership and on-the-ground reality. I do not believe this was intentional. Rather, it was a consequence of internal politics and director-level filtering. C-level never saw the full truth of what teams were carrying. Delivery excellence was expected, but the structural support for it weakened. Teams continued to over-deliver out of pride and commitment, but burnout increased. Despite this, I want to be clear: I never believed the founders or C-level were indifferent. What I witnessed was more a symptom of information not flowing upward than a lack of care. FNZ became too large too quickly, and the internal communication structure did not evolve fast enough to match its scale. Why I Ultimately Left FNZ stopped feeling like the home it once was. Not because the work wasn’t meaningful, and not because the people weren’t extraordinary — but because the vision that once united us began to fade beneath layers of bureaucracy, politics, and structural opacity. I honored my contract, my teams, and the mission until my last day. But eventually, I recognized that the environment no longer aligned with the way I work: transparent, collaborative, vision-driven, and people-first. Leaving FNZ was not a rejection — it was an acknowledgment that the company was moving in a direction that no longer matched what I needed in a workplace.