It's an energetic place, with lots of good people, interesting work, and interesting challenges. As a programmer, it's got a very interesting problem set to work on, and an interesting set of requirements to design to. This allows us to make a product that is so customizable by our customers, open where we want them to modify it, and closed where we don't.
They live up to the Agile/SCRUM methodology – a sustainable work pace that doesn't have me killing myself every release or abandoning my family, nor does it leave me bored. It's a very cool, collaborative type of environment. I'd worked in offices before, and being able to talk to and listen to my coworkers more easily is a nice change.
I've been a programmer for 20 years, and this is my favorite work environment. I get to get things done, build cool stuff, have a life, and work with interesting people. When I hit a trouble point, people here help. I can ask my coworkers or my boss at any moment and get pointed in the right direction.
If you want an office, it's cubicles. Personally, now that I've done it, I like it (I never thought I would – too many negative stereotypes of cubicles). The interaction, the ability to just toss a question to a coworker, is well worth it. No walls, so you can easily talk.
No food in walking distance. There are food trucks and a sandwich place that brings food in – that I do miss; I used to work in an office with more choices. We've got a free Friday lunch that is often good, and it's something, but I miss walking to my local Chinese or Mexican in the area.
The interview process consisted of two phone interviews, a take-home project, and in-person interviews. The first phone interview with the hiring manager was a "get to know you" call and was easy. The second phone interview was with an engineer who
Check your horoscope before going for an interview. There is no defined process for taking the interview. My interview went like this: 1. Technical round 2. Followed by manager and HR round 3. After 3 weeks, the consultancy guy called me and sched
Two technical rounds followed by a discussion with the IDC head. All are technical in nature. The first round comprises one coding and design question. The second round features a Java discussion. The last round is a design question followed by ge
The interview process consisted of two phone interviews, a take-home project, and in-person interviews. The first phone interview with the hiring manager was a "get to know you" call and was easy. The second phone interview was with an engineer who
Check your horoscope before going for an interview. There is no defined process for taking the interview. My interview went like this: 1. Technical round 2. Followed by manager and HR round 3. After 3 weeks, the consultancy guy called me and sched
Two technical rounds followed by a discussion with the IDC head. All are technical in nature. The first round comprises one coding and design question. The second round features a Java discussion. The last round is a design question followed by ge