Really strange process. Hacker rank 10 minute test consisting of java trivia questions. Then a phone screen with more java trivia. On-site consisted of even more trivia questions or vague situational questions without enough details although the interviewers seemed to be looking for a very specific answer and would blurt it out prematurely while I was still ruling out possibilities. No coding, no design, nothing. One of the interviewers had a thick Indian accent and asked a trivia question about a spring boot specific annotation. Seriously? Spring boot specific trivia?? He then asked this odd question: βWhat is the difference between synchronization and concurrencyβ. Confused, I responded by giving him the dictionary definition of these two terms to show the difference. After the fact, I realized what he actually meant was βwhat is the difference between synchronized collections and lock-free thread safe collections many of which are in the java.util.concurrent package" but he wasn't wording the question correctly or maybe he misunderstood what concurrency actually means. Overall really terrible interview with untrained interviewers. Team seemed relatively weak. Half of the team moved into development recently from QA including the manager. Seems like itβs a really chaotic environment. No structure and plenty of people in positions of power that have no business being there. Seems like a real disconnect between the skill of the engineers and the management perceptions. Got rejected a few days later citing the BS reason of not being able to hit the ground running.
I like the name of this company. If employees of Google are called Googlers, If employees of Amazon are called Amazonians, If employees of Microsoft are called Microsofties, Are employees of Chewy called Chewtiyas?
Best thing I read for today. Good job again JohnMcPee
They called them Chewtopians for the curious.
I had an phone interview, was asked what would I use for a phone book / contacts app, and the interviewer wanted me to choose between linked list and arrays. When I explained the time complexity for both approaches, they told me I was making it too complex and I should just choose one. And then the recruiter ghosted me. ππ
Eh, it's chewy, who gives a shit lol
Damn you inferred all of that from the interview π
Can you elaborate? Curious to hear your take since you are currently working there.
Where to begin? Management doesn't seem to know what they're doing or what their engineers are doing half of the time. They're mostly yesmen who promise their superiors everything and then urgently dump it all on the devs. So chaos and fighting fires is the norm. We're losing a lot of good people π
how do you know?
I can also confirm that the engineering culture at Chewy is non existent. At one point in time there was a group of engineers that just wanted to do the right thing and ship software. Unfortunately things changed drastically after the departure of the CTO. It's a shame too because their tech stack wasn't all too bad, just mismanaged. Nearly all of the engineering talent parted ways with the company, and have been replaced by contractors. The remaining few must have gotten paid.
Tell them your ground is too weak to start running on it π