Profitable company. Things move fast. You can see your code changes in production in no time. Looks good on a resume. Cubes have a nice view if you get a lucky seat. Some, but not all, of the technology is cool.
Obsessively driven co-workers with no lives.
You will be expected to work 45-50 hrs a week just to keep up.
October to Dec 25 is treated as crunch time because of the holidays.
Mandatory on-call from 1 of every 4 weeks to 1 of every 8 if you are lucky.
Developers are 30% tech support for their service, 40% business analyst, and 30% developer.
You will spend far more time learning the intricacies of shipping boxes through UPS than working on "cool" things, and you will be expected to feel passionately about those boxes.
Standard "lean" process speeches from senior management over and over.
Priorities change at the last minute.
Chaotic undirected environment with everyone competing for air time.
You have to learn a thousand buggy in-house made tools.
You will be a cog in the machine. Squeak, and you will be replaced by a new college grad.
There is a reason nearly everyone there is under 30, think about it.
Treat employees like people, not code.
Give better benefits (medical/dental premiums).
Why can't we all have Kindles?
Stop reading all the stupid Lean Manufacturing/Six Sigma crap and think for yourselves.
It was good, but they didn't respond to me for a long time after 14 days. I asked them why, but they didn't respond back.
Initial phone call with a recruiter, followed by a 90-minute coding assignment. This consisted of standard LeetCode-style algorithm and data structures problems, loosely related to the specific role and easy to prepare for by using normal resources.
Only one round for the intern position. The first part of the interview was technical questions. I got one "out of the box" question and one LeetCode question created by the interviewer, not on the list. The second part of the interview was behaviora
It was good, but they didn't respond to me for a long time after 14 days. I asked them why, but they didn't respond back.
Initial phone call with a recruiter, followed by a 90-minute coding assignment. This consisted of standard LeetCode-style algorithm and data structures problems, loosely related to the specific role and easy to prepare for by using normal resources.
Only one round for the intern position. The first part of the interview was technical questions. I got one "out of the box" question and one LeetCode question created by the interviewer, not on the list. The second part of the interview was behaviora