Good pay, benefits, stock options.
Get to work with new technologies. Friendly, knowledgeable co-workers. It really depends on your manager and your team. Some are good. Supposed IPO.
"No Vacation policy" means you can take whatever time you want as long as your manager approves. (Mostly managers take advantage; engineers rarely.)
A sweatshop for engineers. No free time. "Free lunch" is a perk to keep you in the office and work more.
Always under the gun. Too many managers to engineer ratio. Agile, but never "punting" in 2 years.
Legacy code is absolutely atrocious to work with.
Expect to build 3-4 versions of a feature for out-of-control "A-B" testing of product features. Product managers have no idea what works, so you build several versions of a feature just to test what "works" in the same amount of time it would take to build one. But since it's "agile," you end up changing direction a few weeks later and redesigning/building something else in its place.
Majority of code is discarded after "A-B" test concluded.
The "rush" period is insane, mismanaged, and never prepared for ahead of time. Expect to work long hours, late nights, and weekends for about 4 months out of the year.
Mostly lip service from upper management about "the student graph" and "LinkedIn for students." Product does not reflect this direction.
I only saw one engineer get promoted in 2 years.
"High priority" projects don't get the attention or resources they deserve. Everything is "high priority."
Slow down. Too much vaporware and A/B testing is out of control. Hire product managers who know what they are doing.
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
Applied online from their website, then email and phone screening from a recruiter. After that, a phone interview from an engineer of that team. After that, scheduled an onsite interview with seven people! Luckily, the long interview was interrupted
The hiring manager contacted me and set up an initial conversation. It looked interesting for the profile they were hiring for, so I went in for a full-day on-site. In my view, the on-site went fairly well – not outstanding, but certainly not terri
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
Applied online from their website, then email and phone screening from a recruiter. After that, a phone interview from an engineer of that team. After that, scheduled an onsite interview with seven people! Luckily, the long interview was interrupted
The hiring manager contacted me and set up an initial conversation. It looked interesting for the profile they were hiring for, so I went in for a full-day on-site. In my view, the on-site went fairly well – not outstanding, but certainly not terri