Pros
Salary (they will give your asking) Over Time Pay 6am - 9am flexible time-in Pre-employment Bonus and referral multiple technologies used for testing automation team is moving forward with Cypress
Kontras
One of the worst HR team, there is a 1-2 days turnaround time for employee inquiry, most of the time, they will not answer your query at all. HR time is based on the US even though the team is following PST, which is a weird explanation as to why most of them are in graveyard shift. So where is the HR for the PH office? Payroll is 1-3 days delayed after cut off, pay slip is 3-5 days delayed after cut off. Kanban release style (weekly releases), which was not given a straight forward answer during the interview. Management basically just fills the empty positions, not really putting any thought if the applicant is the right fit for that team. Thus skill set was not properly used by the employee No available B.A. thus user stories are empty, developers are now controlling what the testing of the QA will be. Business requirements keeps getting add in-between sprint thus development is never really done for anything. Since there is no BA, no formal discussions area available thus feature or User stories has always a gap, development is always adding up, so basically features are not properly developed No ticket responsibility, no one is really responsible on any tickets (especially User Story, Feature) QA’s are the one making the User Stories, it’s difficult to say know where the QA will asked the Acceptance Criteria since they are the ones that created the ticket in the first place. Developers give little to half baked information about anything, unless you include a lead on a call, they basically give you information one at a time, making testing difficult and time management low. Developers are so sure if they are performing Unit testing on their items To many testing environment, (3 testing environments), thus it is no longer sure if the developers, are actually performing any unit testing since they can just release the updates on the next testing environment There are User Stories that have no information at all, thus you are only provided a notepad, when asking for assistance or help, even the one who created the User Story ticket do not know what it is for and what is the issue is, Outdated QA test plan especially for new hires, yet they are deliberately pronouncing that it is up to date, yet changes are done every time there is KT session Have a “If it is not broken why fix it” mentality Bug have testcase on them, when asked no definite answer provided, they can’t say (it is being used for formality by the automation team.) Weekly releases, since release happens every week, and Acceptance Criteria is always added on the User Story within the sprint, the point of pushing or rushing the item to be released makes no sense, the item is incomplete, does not work properly sometimes at all, so why rush it? User’s can’t use it, management have no ide what’s it’s for even on the demo’s they are pushing it but at the end of it, it is still incomplete? Why rush in the first place? It has been 2 years of the pandemic, still no definite solutions for the Work From Home, if it’s going to be permanent or hybrid