Exciting working for a company that is growing. Seems like there are a lot of exciting initiatives happening.
Most people say positive things about Chewy. Whenever I see consumers say great things about Chewy, that makes me very happy.
People can be very helpful when you have questions about anything. There's a lot of support for a collaborative environment.
There's a strong platform and design team that sets standards.
Promotions seem to be a combination of merit and seniority. People that get promoted seem to deserve it.
Pay is good.
You can have your fair share of mediocre software engineers or managers. However, I'd say this is the average amount. There are also very great developers and managers here.
Loss of former members makes it harder to deal with legacy code. While we are moving away from legacy code, it still exists.
There can sometimes be time pressure for deadlines. However, management is usually reasonable with listening to developers about the timeline based on story estimations and the number of tickets for an epic.
Using contract-to-hire practices could give us a better feel of job candidates before they work full-time. Also, a job candidate should at least be interviewed by a manager or trusted teammate of the team they will be working on.
Have a plan for maintaining legacy code. Even if nobody is actively contributing to it, until there are no clients, it's still a codebase that needs to be maintained.
A recruiter reached out to me via email, stating I might be a good fit for a backend SWE position they had. I completed the first round of interviews, which was essentially a call with an engineer. We worked on a HackerRank problem involving 2D array
First, a multiple-choice Java assessment was sent, mostly on algorithms and data structures. Then, a recruiter phone call with basic behavioral questions like eligibility to work and simple questions about your interest. The final round is technica
1. Phone screen 2. 1-Hour technical interview 3. 4-Hour final panel interview (coding/algorithm, behavioral, debugging/problem-solving, system design) The interviews themselves were fine, and study material was provided. Interviewers were kind and h
A recruiter reached out to me via email, stating I might be a good fit for a backend SWE position they had. I completed the first round of interviews, which was essentially a call with an engineer. We worked on a HackerRank problem involving 2D array
First, a multiple-choice Java assessment was sent, mostly on algorithms and data structures. Then, a recruiter phone call with basic behavioral questions like eligibility to work and simple questions about your interest. The final round is technica
1. Phone screen 2. 1-Hour technical interview 3. 4-Hour final panel interview (coding/algorithm, behavioral, debugging/problem-solving, system design) The interviews themselves were fine, and study material was provided. Interviewers were kind and h