Chewy spent a lot of time in human-driven sessions (not just online training) around its operating principles, its culture, and diversity, equity, and inclusion.
About 4-6 hours for a cohort of 30ish new employees in the first week, and there are future sessions planned. To me, that shows that the company understands the importance of these things for hiring and retaining staff.
The work-life balance seems good so far, as does the support I receive from my team and the company.
Every company has its own pathology driven by its history. I've been in the industry since 1995, and I've seen a lot. Chewy staff keep on apologizing for the mess, but it's really not that bad. Yes, there's some unnecessary chaos. Yes, folks are trying to pay down that tech debt or org debt as best they can. Are there jerks here? I guess there must be, but I haven't seen it yet.
I'm a release engineer, so my focus is on the road and infrastructure to facilitate continuous delivery. Acceleration does seem a very important goal, and spending cycles on improving the road for that acceleration seems important too.
Better guardrails, better management of the "traffic" or work cutting across teams seems important.
Technical Interview: Python + SQL Questions - 1 hour 0-5 min: Interview started with normal introductions. It was like any other interview. 5-20 min: Questions based on the resume. I went deeper into my projects, but the interviewer couldn't unders
The role was for a React developer. The interview enforced coding in vanilla JavaScript, HTML, and CSS. After a while coding in React, your vanilla JavaScript coding skills fade, making you panic as if you don't know anything.
Step 1: Apply to the role. Step 2: If selected, a recruiter will contact you. Step 3: Recruiter call. Step 4: 1-hour interview with one of their engineers (30 minutes of technical questions and a 30-minute coding round on HackerRank). Step 5: 4-h
Technical Interview: Python + SQL Questions - 1 hour 0-5 min: Interview started with normal introductions. It was like any other interview. 5-20 min: Questions based on the resume. I went deeper into my projects, but the interviewer couldn't unders
The role was for a React developer. The interview enforced coding in vanilla JavaScript, HTML, and CSS. After a while coding in React, your vanilla JavaScript coding skills fade, making you panic as if you don't know anything.
Step 1: Apply to the role. Step 2: If selected, a recruiter will contact you. Step 3: Recruiter call. Step 4: 1-hour interview with one of their engineers (30 minutes of technical questions and a 30-minute coding round on HackerRank). Step 5: 4-h