Good compensation.
Stock shares upon signing with the company and additional yearly shares thereafter.
401k matching at a standard 3% cap.
Commuter / parking company contributions.
Frequently received company swag.
Extremely poor work/life balance. Although management preached better balance and communication, you often worked nights and weekends to push out tickets to meet goals.
"No Meeting Tuesdays" for personal growth and development were not a thing, and we often had many meetings on Tuesdays.
Very loose application of Agile. Had standups, grooming, and monthly retros. No definition of ready, no quarterly planning, no definition of done, and scope creep on tickets was very common.
Meetings were set aside for employee growth, but they were frequently skipped. Never received a formal plan or regular communication for my growth, as I was told to catch up on the team’s backlog. After a year of backlog catch-up, there still wasn’t any discussion of my career growth.
Onboarding was largely directionless and lasted maybe a day. After that, I was thrust into completing tickets.
Code reviews existed, but most of the time PRs were approved without any discussion. Basically, ship it to prod as fast as possible without any time set aside for future development or improvements to the code.
Dogs are allowed in the Boston office, but only 5 per floor (though this seems to be loosely enforced), per building lease agreement. The Florida office does not have a limit, I believe. The Boston office has a sign-up sheet for bringing dogs in.
On-call was not good. Frequently alerted for issues where the resolution ended up not requiring any work to fix, and instead involved waiting for the job to run again in a few hours. Many jobs would alert in this manner, and no time was given to either fix the process or change the alerting priority on the failed job.
1) Hiring Manager: Past experience 2) Virtual Loop: * System Design Round: No actual sys design, just verbal questions. * Behavioural (x2): Focused on operating principles. Candidates are not data engineers, and questions may extend beyond d
Phone call with a recruiter that led to a technical interview, then a behavioral interview, 45 minutes each. Typical LeetCode questions were asked, along with questions about how to handle suggestions from managers and take constructive criticism.
You will meet with many different leaders across the company in 1-hour meetings. You may be asked technical questions and could be required to do a coding exercise, but the bulk of the interview focuses on the Chewy Operating Principles PDF provided
1) Hiring Manager: Past experience 2) Virtual Loop: * System Design Round: No actual sys design, just verbal questions. * Behavioural (x2): Focused on operating principles. Candidates are not data engineers, and questions may extend beyond d
Phone call with a recruiter that led to a technical interview, then a behavioral interview, 45 minutes each. Typical LeetCode questions were asked, along with questions about how to handle suggestions from managers and take constructive criticism.
You will meet with many different leaders across the company in 1-hour meetings. You may be asked technical questions and could be required to do a coding exercise, but the bulk of the interview focuses on the Chewy Operating Principles PDF provided