The reality of the work
The company presents itself as an AI-first organisation where engineers work on cutting-edge projects. In practice, the majority of the work is legacy software delivery for large US corporate clients. It was widely discussed, including in public forums before I joined, that a single client accounts for the substantial majority of revenue. This is not a secret, but it is also not reflected in how the company markets itself to prospective hires.
If you are joining because of the AI positioning, understand that this is primarily a traditional consulting model. For engineers who want to work on genuinely innovative projects, the gap between expectation and reality is significant.
What I experienced directly
My offboarding process was one of the most disorganised and professionally difficult experiences of my career. I want to be specific because specificity is what makes reviews useful, but I will keep this to what I personally experienced:
Leadership moved to terminate my contract, reversed the decision under internal pressure, then re-initiated termination three days later, on Christmas Eve.
During my notice period, I was informed that my notice pay would be conditional on meeting newly defined KPIs. I pushed back on this and the position was dropped, but only because I was familiar enough with employment norms to know it was not a reasonable or enforceable condition.
I was initially offered payment for one month of a two-month contractual notice period, framed as a fair resolution. Recovering what I was contractually owed required sustained and repeated challenge.
After my notice period had ended, I was still being asked to personally coordinate the return of company equipment: sourcing quotes, arranging insurance, liaising with local providers, with no acknowledgement that this fell outside any reasonable obligation on my part.
The impression I was left with was that raising contractual requirements was seen as obstructive rather than reasonable. The frustration expressed was not with the substance of what I was saying, but with the fact that I kept saying it at all.
I was able to navigate this because of my professional background in HR. Most people would not know what to push back on, or how. I am aware of colleagues who found themselves in similar positions during their departures and were not in a position to advocate for themselves in the same way. The pattern does not appear to be accidental.
Broader patterns I observed
What I experienced directly was consistent with patterns I observed more broadly during my time at the company:
People appeared to be let go without documented cause or a transparent performance process.
Employees who took leave for serious personal reasons, including family illness, sometimes found their position had changed on return.
People who inherited responsibilities from departed colleagues, without any handover, were in some cases held accountable for early mistakes without that context being considered.
Former employees were sometimes spoken about negatively after leaving, rather than with basic professional respect.
Large amounts of accrued untaken leave, in some cases well over a month, reflected an environment where people did not feel safe fully disconnecting, even while officially on holiday.
I want to be clear: I am describing what I observed and experienced. I am not in a position to speak to intentions. But patterns, repeated across multiple people and situations, are worth naming.
Leadership and culture
Feedback is actively solicited and, in my experience, consistently treated with suspicion when it challenges the prevailing direction. Over time, people learn to agree outwardly and disengage inwardly. Structural concerns around capacity, resourcing, and unclear priorities tend to be reframed as individual attitude or commitment problems rather than addressed as what they are.
Responsibility is pushed downward without the authority or resources to match it. This is a reliable recipe for burnout and the quiet departure of your most capable people.
I also observed a heavy reliance on AI-generated responses to handle sensitive correspondence. The outputs were often technically coherent but missed the human and contextual substance of what was actually being communicated.
On the interview process
The hiring process felt disorganised and unclear about what the role actually required. There was no coherent picture of the skills being assessed or what success would look like. In hindsight, that experience was consistent with how the organisation operated more broadly. If your interview feels similarly vague, I would treat that as useful signal.
On flexibility and working hours
The flexibility is genuine, and for people with limited access to fully remote, well-paying technical roles, it is hard to walk away from. But flexibility in this context is not the same as respect for your time. Extra hours are frequently expected without acknowledgement or adjustment in return. Out-of-hours training participation is framed as optional but treated as a measure of commitment: those who do not engage are noticed. I am also aware of people who were hired into roles spanning time zones they were not clearly informed about in advance. If you are considering joining, get clarity on working hour expectations before you sign, and set boundaries early. Without them, the flexibility that attracted you can quietly become the thing that consumes you.
On payment terms
A pattern I observed across multiple departures was that final payments were delayed significantly beyond when they were due. For people who had already stopped working and were relying on that income, the delay created real financial pressure, and in some cases appeared to influence whether they felt able to pursue what they were owed.
The practical advice I would give anyone considering contracting here: check your payment terms carefully. If you are relying on this income, negotiate a short payment cycle, seven to ten days, before you sign. Do not assume a thirty-day cycle is acceptable if cash flow matters to you. And if your departure becomes difficult, document everything in writing from the first conversation. Verbal assurances, in my experience, do not hold.
A note on contracts
Read your contract carefully before signing. Make sure notice requirements are explicitly documented and unambiguous. If any dispute arises around termination or payment, seek independent advice early and do not assume goodwill will be sufficient. Several people I am aware of found themselves in genuinely difficult financial positions because they trusted the process rather than the paperwork.