An insulting place to work - Software Engineer Riskhub Employee Review

- Office looks nice - Decent food market nearby

- You will have software on your laptop that takes 900,000 screenshots a month of your machine while working & be flagged for HR intervention if they suspect you aren’t working as hard as they want - Temporary adjustments for additional remote scheduling require gruelling process of interrogation by management and HR while watching favoured employees do whatever they please - Employees will take covert photos of eachother to report to HR - Long standing reputation of mistreating workers on VISA, as the company knows that workers on VISAs are effectively trapped unless they find a new role - CEO actively detests both customers and employees

The technical work has interesting moments and there are capable people within the engineering team. Some colleagues are genuinely good to work with and the office location is convenient.

My experience was marked by inconsistent leadership, poor communication, lack of trust, excessive micromanagement and monitoring, and coworkers disappearing without any clear communicated reasons. There is a culture where raising concerns feels risky rather than encouraged. Decisions are often implemented with little explanation, meeting times change without notice, and policy shifts are not acknowledged even when contradictory, such as increasing in-office requirements for collaboration while simultaneously cancelling meetings. Processes are unstable and frequently overhauled without clear rationale. Jira workflows and delivery structures change every few months. While the development lifecycle in theory is sound, QA is consistently overloaded, creating delays that ultimately result in developers being blamed for missed timelines rather than systemic bottlenecks being addressed. There are visible double standards in how rules and policies are applied. Sick leave, working from home when unwell have been handled inconsistently across employees. Policies are often reactive and selectively enforced rather than principled and transparent. Role boundaries are unclear. Individuals outside engineering contribute to code and architectural decisions despite formal leadership roles existing. Senior leadership directly edits Jira tickets and adjusts deadlines without communication, undermining accountability and planning. There is no structured progression framework or meaningful investment in professional growth. The culture is delivery focused with little mentorship or support for advancement. Social cliques and favoritism go unaddressed, contributing to an exclusionary environment. The overall atmosphere is one of micromanagement, heavy monitoring, and low trust. Combined with inconsistent communication and at times misleading messaging from management, it creates disengagement rather than motivation. This may suit those comfortable in a highly controlled and politically driven environment, but those seeking transparency, fairness, and professional growth should evaluate carefully.