employer cover photo
employer logo
employer logo

Westpoint Software Solutions

Is this your company?

Good experience for someone starting in the area - Software QA Tester Westpoint Software Solutions Employee Review

4.0
10 Jun 2025
Recommend
CEO approval
Business outlook

Pros

The team was super collaborative and open to feedback. I had the chance to work on different kinds of testing, including manual and a bit of automation, which really helped build my growth. They also had a good structure in terms of documentation and processes, so I always knew where things stood.

Cons

Things moved fast sometimes, and priorities could shift during the week — you had to stay flexible and keep up.

Explore other reviews about Westpoint Software Solutions

5.0
20 Aug 2025
Recommend
CEO approval
Business outlook

Pros

Workload is balanced most of the time, so you can focus on building solid features without constant rush. The team is easy to talk to and there’s a lot of sharing knowledge during standups. Documentation has improved a lot since I joined, which makes picking up new tasks much easier. Office has a relaxed feel and management doesn’t hover over you, as long as you deliver.

Cons

Testing processes can be a bit slow when multiple teams are involved, so some fixes take longer than expected to get through. Not much variety in project types lately, so things can feel repetitive after a while. Cross-team communication outside of scheduled meetings could be better, since a lot of updates only come up during formal calls.

3.0
9 Sept 2025
Recommend
CEO approval
Business outlook

Pros

The code review culture was good, with feedback that was clear and helpful. The component library was in decent shape, which meant I could move quickly without having to rebuild basics. Design and QA were easy to work with, and handoffs were usually clear. I also had the chance to lead a couple of rollouts end to end, which gave me solid experience. The office in San Jose was comfortable, and quick desk chats often solved things faster than long threads.

Cons

Impact was hard to see at times, since metrics lived in a few tools and took time to pull together. Late design tweaks or microcopy changes created rework near the finish line more than once. Context switching between small features in parallel made it harder to go deep, which was very different from my last team where we only worked within singular contexts. The release train was strict, so if a feature slipped I had to wait for the next cut.

See reviews by: Helpful|Rating|Date|All