Pros
* pay – pay is slightly above market rate. Based on my conversations with other developers, you can expect 100K or so if you're mid level (3-5 years experience). Big bonus at the end of the year as well. * vacation - 15 days your first year. Another great thing about the engineering dept is that if necessary, you're allowed to take a month or two off and go travel or learn a new skill. Management is very flexible and understanding. * employee discount – wholesale price on pretty much anything on the site. Revolve has very fashionable clothing/accessories, so if that's your thing, you're really gonna like it. I didn't really see many developers take advantage of it though. * flexible hours - you can start work anytime you want. * high employee caliber - my coworkers here have been knowledgeable, always willing to discuss designs/algorithms/strategies, and ready to help out if you're stuck. There are some quirky characters, but that's nothing new in an engineering dept. * work/life balance - you work 40 hours a week. It's rare that anyone does overtime, so if you have a family, Revolve will be perfect for you. Also, if you finish your work before the end of your sprint, which happens here and there, you're free to do whatever you want. Some developers choose to just browse the web, chat, go to the coffee shop, or just call in sick. * huge growth - Revolve is growing at a phenomenal rate. Their revenue is 7 figures each day and the number of employees continue to grow. If you simply do your job, the chance of growth within the company is very high.
Cons
* workplace – you will be working in a warehouse. Although the artifical walls do help, noise is a concern. Most developers put on earplugs/headphones. * work - Revolve uses Model 1 JEE architecture, which is as simple as it gets. The design is intentionally simple, and as a byproduct you won't work with the latest MVC framework, but you'll always have free time to explore them if you want to. On the positive side, you can be productive rather quickly, since you'll have an easy time understanding the code base (a few months usually). * no formal QA process – this was the first company I worked for where the code was being pushed to live without any formal testing process. The philosophy is that developers are then forced to write better code, and indeed I do see very high quality code with little errors. It forces developers to think about the requirements and produce the best algorithms for the task at hand.