It's really comfortable in NYT; don't have to put too much effort.
Good for new grads, but not so much for mid-levels or higher.
It's a product company – not many technical challenges.
Limited tech stack, hard to onboard new tech products.
DevOps culture is non-existent (it's the engineers' problem along with QA).
Everything has to be Golang; nothing else can be justified.
Tech debt can be substantial.
Meetings, a lot of meetings.
The interview consisted of a practical (open book) test where I was allowed to browse the internet to find examples, documentation, and/or solutions to the presented problem. This is key to remember, as what they are testing is primarily how you rese
30-minute recruiter screening, followed by a 30-minute hiring manager screening the next week. Then, a 30-minute technical assessment the week after that, using Coderpad. Everything was going great. I did well on the assessment, and then the recruit
Had a conversation with the recruiter. 30-minute tech screen with a Manager. A homework assignment. A week later, 30-minute homework assignment review. Two weeks later, 4 hours onsite with various people, including architect, SSD, PM, SPM, and Dire
The interview consisted of a practical (open book) test where I was allowed to browse the internet to find examples, documentation, and/or solutions to the presented problem. This is key to remember, as what they are testing is primarily how you rese
30-minute recruiter screening, followed by a 30-minute hiring manager screening the next week. Then, a 30-minute technical assessment the week after that, using Coderpad. Everything was going great. I did well on the assessment, and then the recruit
Had a conversation with the recruiter. 30-minute tech screen with a Manager. A homework assignment. A week later, 30-minute homework assignment review. Two weeks later, 4 hours onsite with various people, including architect, SSD, PM, SPM, and Dire