Great work-life balance.
Real, revenue-impacting problems to solve and things to build, and the freedom to choose my own ways of tackling the problems.
Great team – my coworkers are hilarious and brilliant.
My division is very start-up-esque, in that we can think of a feature, rapidly gain buy-in, and start building within a sprint or two.
Great lunches and snacks every day. Unlimited vacation and work-from-home. Loose hours, as long as I'm working hard.
Great pay, great benefits, great stock compensation, and the stock is doing great.
We have fun.
So much data, it can be daunting. We AB test everything, which increases the complexity and time to production. We're still feeling out a balance for this, but extreme diligence and data-saturation are good problems to have, if you're going to have some.
Unlimited vacation always strikes me as a bit of a trap. I'm far less inclined to take it when there isn't a timer on it.
The start-up feel can mean there's a lot of forging ahead and seeing what works. I personally love this, but if you need a lot of structure and direction, be aware.
Keep doing your thing.
They don’t respect your time when you try to schedule an interview. Their representation of the position and the company during the phone interview was very unprofessional. Simple questions about the technical stack weren’t answered.
The first step was a HackerRank online test. The second step was a 1-hour Zoom interview. The interviewer shared a HackerRank code pad and asked me to write the code. It was a simple question about the longest common substring without repeating char
1 phone screening and 1 onsite. The phone screen question was relatively easy – an n-ary tree. The manager was kind enough to guide me. The onsite interview was not that hard either. Perhaps because on the same day I had received an offer from anot
They don’t respect your time when you try to schedule an interview. Their representation of the position and the company during the phone interview was very unprofessional. Simple questions about the technical stack weren’t answered.
The first step was a HackerRank online test. The second step was a 1-hour Zoom interview. The interviewer shared a HackerRank code pad and asked me to write the code. It was a simple question about the longest common substring without repeating char
1 phone screening and 1 onsite. The phone screen question was relatively easy – an n-ary tree. The manager was kind enough to guide me. The onsite interview was not that hard either. Perhaps because on the same day I had received an offer from anot