Interesting challenges exist to apply technology to innovate in the "local" space. We're way more than a "daily deal" company. My colleagues at Groupon are smart, driven, and fun.
We're an "agile shop" organized into small feature teams, all doing focused work. We are expected to not just deliver software but design and innovate the product. We've just scratched the surface with the systems and products we'll build to achieve our goals. That means lots of opportunities to learn new things and work on different projects; new teams are forming all the time.
Things are getting better and better for engineers. From an employee-driven "open transfer" policy (if you want to move teams, find a fit, and go for it), a per-engineer conference/training budget, and regular hack-a-thons, everyone is putting effort into making Groupon a great place to be an engineer.
It's a young company that grew really fast. Lots of things to get better at, like making decisions and communicating throughout the organization. With lots of small teams working independently, it's tough if you need to coordinate things. It's been a rough year with poor public press and a CEO change out.
Keep listening to the front line and never stop working to make Groupon Engineering into the place we say we want it to be.
I was reached out to by a recruiter and interviewed by a member of the technical staff. The interview was a standard technical interview, nothing particularly unique, and was conducted one-on-one. The coding section involved whiteboard coding in my
Contacted by HR on LinkedIn. Phone conversation with HR. Received a programming exercise to complete in a week. It was pretty simple. Onsite interview with 5 developers/SDETs and HR. The first two SDETs had been with the company for less than six
Had an initial 30-minute phone interview that covered some basic questions. Then came into the office for two 30-minute interviews with managers, where it was a lot of role-playing scenarios with customers.
I was reached out to by a recruiter and interviewed by a member of the technical staff. The interview was a standard technical interview, nothing particularly unique, and was conducted one-on-one. The coding section involved whiteboard coding in my
Contacted by HR on LinkedIn. Phone conversation with HR. Received a programming exercise to complete in a week. It was pretty simple. Onsite interview with 5 developers/SDETs and HR. The first two SDETs had been with the company for less than six
Had an initial 30-minute phone interview that covered some basic questions. Then came into the office for two 30-minute interviews with managers, where it was a lot of role-playing scenarios with customers.