Enjoing my time in Testlio - Software Engineer Testlio Employee Review

5.0
May 30, 2019
Recommend
CEO approval
Business Outlook

Pros

After being software engineer for more than 10 years these are the things which matter to me: * Cool, smart and motivated people * Challenging and interesting work * Really enjoyable work environment (this does not mean loose) * Engineering team focused on solving actual business problems * You, as a developer, can have a real impact in business, what you do matters * You can voice your opinion and thoughts without a worry or concern - more different opinions will form a better end result * People are trusted to do their work without micromanaging * Management is transparent and important information is shared and reasons are given if needed * Great benefits and enough team events (at least for me)

Cons

There are always things which could be improved but i can not point out anythings which i would consider as actual con.

Explore other reviews about Testlio

5.0
Feb 3, 2026
Anonymous employee
Recommend
CEO approval
Business Outlook

Pros

The renewed company focus allows teams to prioritize effectively and maintain alignment. The leadership team is grounded, motivated, and highly collaborative. The product strategy successfully embraces AI, positioning the company to define the future of AI testing.

Cons

The volume of organizational change over the past year was a bit high. While these pivots were clearly made to ensure both near and long-term success, so much change can lead to change fatigue. I believe that leadership maintaining the current level of transparency will be key as the org continues to stabilize under the new focus.

1.0
Jul 13, 2026
Recommend
CEO approval
Business Outlook

Pros

There is no growth and learning.

Cons

- Management lacked consistency and long-term direction. Priorities often changed without clear communication. - Processes were not well defined and varied significantly from one project to another, creating confusion and inefficiencies. - Knowledge sharing was limited, making it difficult for new team members to get up to speed quickly. - Quality of leadership and technical expertise varied across projects and teams. - Heavy dependence on contractors resulted in frequent team changes and loss of project knowledge. - Documentation was often incomplete or outdated, requiring testers to spend extra time gathering information. - Career growth opportunities and promotion paths were not clearly defined. - Feedback and performance expectations were sometimes unclear. Project assignments could end abruptly with little notice, creating uncertainty for contractors. - Communication across multiple time zones could delay decisions and issue resolution. - Test environments and access management occasionally caused unnecessary delays. - Lack of standard QA practices across projects made it difficult to establish consistent quality standards. - Limited opportunities to influence product decisions since QA teams generally worked as external contributors rather than part of the client's core team. - Resource planning was sometimes reactive rather than proactive, leading to workload fluctuations.

See reviews by: Helpful|Rating|Date|All