Taro Logo

Working on the BestBuy.com team: a bad experience that felt like it had potential

Software Engineer
Former Employee
Worked at Best Buy for 1 year
November 7, 2019
Richfield, Minnesota
1.0
Doesn't RecommendNeutral OutlookNo CEO Opinion
Pros

A few bright spots that have potential to help turn things around:

  • Team managers seem well-intentioned (unfortunately bogged down by larger structural inefficiencies, though)
  • Working on a current tech stack (once again, this manifests itself less optimally due to organizational weaknesses)
Cons
  • Very much has the vibe of "clock in, clock out" culture. People don't seem passionate about the work they're doing and its quality. This probably has certain roots in how heavily the workforce is skewed towards contractors.

  • Teams are split by site functions rather than as full stack teams. This makes it hard to build functionality/solve problems independently and leads to cross-team blockers that stagnate. Certain teams bear more of the load here, which only compounds the issue.

  • Designers focus on pixel-perfect wireframes when there are more systemic design issues in engineering and the actual website final product.

  • Documentation is very poor. It's hard to feel like you can hit the ground running, especially combined with the fact that on-boarding is non-existent.

Advice to Management
  • Too many contractors leads to weird team dynamics and heavy churn. Value employees and they'll value you.

  • Structure teams so they have autonomy. Siloing teams in a way that fractures responsibility leads to ownership problems and breeds resentment.

  • Build a user experience that is meaningful instead of the default comparisons to Amazon and Target.

Was this helpful?

Best Buy Interview Experiences