Dysfunctional Environment - Software Engineer Retail Success Employee Review

1.0
Jun 15, 2020
Recommend
CEO approval
Business outlook

Pros

The building itself is a very nice place to work. The benefits are average.

Cons

There is too much tension and dysfunction between the front-end and back-end development teams. This is mostly due to poor engineering management and leadership. The product team is weak and not innovative. They appear to have a singular idea that they continue try to dress up as if it were a different product.

avatar
Retail Success Response
3y
We appreciate your feedback - things like this are immediately addressed by our leadership team.

Explore other reviews about Retail Success

5.0
Apr 21, 2026
Recommend
CEO approval
Business outlook

Pros

Retail Success is an exceptional organization with a stellar team, starting with our leadership. I thoroughly enjoy being part of this team and find that collaborating across departments is seamless. The company fosters an open, communicative culture, where everyone is deeply committed to quality and growth.

Cons

Would like to have more in-person, company get-togethers

3.0
Jun 10, 2026
Recommend
CEO approval
Business outlook

Pros

the pros included the speed at which I was allowed to bring my myself up to speed for the job. What were my responsibilities, expectations, how to do the work and what the preferred methods were. I was not thrown directly into it but allowed to learn first, quickly, but I had the time necessary. the optional hybrid work options also is very attractive and helpful. helps save money on commute and take care of any personal tasks at home and of others I need to more easily. My coworkers being cooperative and friendly as well is a plus. Being able to speak with a dev directly about issues discovered is very helpful. clear direction on priorities is also an improvement I enjoy here.

Cons

The documentation for tools, resources to use, instructions and onboarding is out of date. some tools have been replaced without new instructions. software changed so much since its guide or instructions were written they provides no benefit. decisions on tickets and general direction are also not as clearly/consistently communicated as they could be. An example would be that some issues are discovered, tickets made, and they are sent to the backlog if they are lesser issues at the time. the con comes in when a decision is made on how to proceed with the change needed, but this is not communicated to anyone besides those who discussed the change and the ticket sits in backlog until its seen again.

See reviews by: Helpful|Rating|Date|All