Priority Software Reviews 2

I worked as a QA Engineer at Priority Software from October 2024 to January 2026. This review reflects my direct experience on one team.

From the start, expectations and onboarding were unclear. I was assigned responsibility for building REST API test automation infrastructure without documentation, ownership guidance, or access details such as API endpoints. I independently contacted multiple teams to obtain the required information and delivered the requested work, but expectations were not clearly communicated or aligned during this phase.

I was the only QA engineer on the team and was responsible for test design, manual testing, automation, and bug reporting. A consistent blocker throughout the role was the low quality of Jira tickets: many lacked acceptance criteria, steps to reproduce, or sufficient technical context. When I raised this issue repeatedly, it was dismissed rather than addressed.

Weekly one-on-one meetings with my direct manager focused primarily on criticism, with little discussion of support, prioritization, or how to succeed in the role. Requests for clearer standards or examples of expected test cases were declined.

In July 2025, test cases I authored for a major email service were formally reviewed by senior stakeholders (R&D leadership, product, automation, and development). Feedback was provided and fully implemented. In September 2025, the same test cases were rejected by my manager due to the length of their titles—an issue not raised during the earlier review. I updated approximately 300 test cases within one day to meet this feedback, yet the work was still escalated to HR.

During this period, a junior manual QA engineer joined the team and reported directly to the same manager. My scope and workload remained unchanged.

In October 2025, a planned salary increase was denied. I met with HR, presented my work, and requested reassignment to another QA role within the company due to ongoing management issues. No alternative role was offered.

In late November 2025, I was invited to a meeting initially labeled as a formal hearing, which was later described as a regular alignment discussion. During the meeting, I addressed each point raised and again proposed concrete solutions to align expectations, including standardized test case templates. Shortly afterward, my employment was terminated.

My experience was defined by inconsistent expectations, delayed and shifting feedback, lack of managerial support, and limited avenues for resolution. Candidates considering this role should proactively clarify documentation standards, feedback processes, and support structures before joining.

We've been on this new ERP system for less than 2 years. The implementation was not done well - a lot of things seemed to be missing even this far down the road. We're a small business - only about 30 employees, and this ERP software is way too convoluted for us. We haven't been able to rely on the system's data for anything from financials to inventory. We're trying to make it work, but we've had to hire extra people to do the same thing we did before on a different system.