Fantastic company to work for! - Software Developer iCabbi Employee Review

5.0
Mar 21, 2023
Recommend
CEO approval
Business outlook

Pros

Great office environment and the staff are very friendly. Feels like a second family. Management does its best at making sure everyone is aware of what and where the company is heading with up-to-date meetings. Ideas and opinions are considered when planning is taking place.

Cons

A task may be given to the wrong person with little to no skill in the area the task is required, thus making the finished product for the task either incorrect or can take a long time to complete.

Explore other reviews about iCabbi

2.0
Dec 19, 2025
Recommend
CEO approval
Business outlook

Pros

- Really interning product - Talented and professional engineers who care about their work and take full responsibility for what they do

Cons

- Unprofessional top-level managers who don’t fully understand what they are doing, consider themselves senior experts, refuse (or are afraid) to take responsibility for anything. - Strange priorities: You may spend months developing a feature that brings no real value to the company, while requirements change daily. In the end, missed deadlines are blamed on engineers. - Lack of communication: Departments do not communicate between each other. - Lack of transparency: If you are a contractor, beware: today you may be treated as the best person on the team, and tomorrow you can be laid off through a third party, not even face to face.

1.0
Jul 8, 2025
Anonymous employee
Recommend
CEO approval
Business outlook

Pros

Members of my team were very helpful and nice.

Cons

Token QA Hires, No Onboarding – Three QA contractors were brought on board a week before my redundancy, without interviews or proper team introductions, signaling process dysfunction. Sudden, Unjustified Layoff – Despite consistently positive performance reviews, I was laid off under a vague “cost-cutting” banner with zero transparency - not even an apology or any empathy shown. Broken Release Processes – Frequent production releases shipped critical bugs, leading to repeated customer escalations. Endless Firefighting – Day-to-day work devolved into triaging live incidents rather than stable feature development. Massive Manual Regression – Every sprint for 2 weeks the entire QA team was bogged down in an exhaustive, manual regression cycle due to a lack of automation and clear test plans. When bugs were found and fixed regression wouldn't restart and they would be testing on an outdated codebase. Outdated Technology Stack – Legacy tools and frameworks with no investment in automation made routine testing slow and error-prone. Toxic “Watch Your Back” Culture – Despite talk of collaboration, there were no formal processes; on day one I was privately warned to “watch out” for certain colleagues.

2
See reviews by: Helpful|Rating|Date|All