Omgeo Interview Questions & Reviews
Getting an Interview
Very Difficult Interview
Scrum Master Interview (Negative Experience; Very Difficult Interview)
I applied through an employee referral and the process took 2+ weeks - interviewed at Omgeo in August 2013.
Interview Details – Amoazing long and drawn out interview process for a consultant (contract) position, all things considered, but the communication was extremely unprofessional and highly pejorative. I was profoundly disturbed to find that the position was open due to the prior hire being canned a month into the job due to "inconsistencies on their application". What was disturbing is not that it happened, but that they felt compelled unconsciously to repeat that ad nauseum throughout the interview. Indeed all five of the panel interviewers mentioned this continually during the interview, which I found odd and incongruous, as I wasn't sure why this was necessary information to provide during an interview. Omgeo is very clearly hiding something. There is much more to that story I am certain. Left a bad taste in the mouth. When I left the interview, I felt like I had dodged a silver bullet.
Not one person that interviewed me had any experience or background in professional project management. Their questions and reactions to the answers to my questions belied this. I reviewed the background of every interviewer prior to the interview, and among all seven interviews for a Scrum master position nobody had even one technical or project management certification. I don't think any of them had spent any time working with Agile or Scrum framework at all. The entire world is moving to certified Scrum Masters from the Scrum Alliance, or the PMI institute's ACP, Agile Certified Practitioner certifications. I personally don't believe you need a piece of paper in order to succeed at anything in life, certainly not something so practical as Scrum framework or Agile PM methodology, however, the presence of such certifications on one's resume are becoming table stakes for working on the kinds of projects Omgeo undertakes on a regular basis for their many enterprise clients. One of the reasons for that is the requirement for documented realworld Agile / Scrum experience, along the lines of 2,000 - 5,000 hours at a minimum for many SM certs. Long story short, I don't think they have anyone working at Omgeo currently who was qualified to pass judgement on Scrum Master candidates. At least, that's how it seemed to me.
This interview process, for a consultant position, had all of the weight, stress and time consuming nature of an interview for a fulltime position. At one point, the hiring manager told me he didn't like working with contracts, because they were always looking for a permanent job or to leave soon. My thoughts were: put on your big boy pants and make a hire then. Or stop complaining during interviews, one or the other.
At every opportunity throughout this interview, whenever a question was asked, or I was not talking, each interviewer let it be known that their team is so young and inexperienced that they have no experience with, or even desire, to use Agile or Scrum framework. They mentioned that Omgeo is a "Revolving door", with guest foreign H1B visa workers and very headstrong (their word was 'Obstinate') programmers and development managers. Gosh, just what I was looking for...not.
I was continuously told that my predecessors had both become frustrated with working with the Omgeo team and had left for other contracts after a month (two in the case of my immediate predecessor). I was thought to myself: "Life is too short to waste, even in this nightmare economy". Decided to pass. i can get a better contract and work with people who won't make my miserable. I am a professional project manager, and I know now to avoid bad working situations. They are kryptonite to your career. Caveat emptor.
Interview Question – How would you handle altercations both between developers and your team and yourself regarding their obstinate reluctance to work with Scrum framework? View Answer
Reason for Declining – I could tell it was a working environment that would be too challenging, and I doubted their intentions to honor the term of the contract in question. They seemed to be hiding the true nature of the team's working environment and the frequent departures they seemed compelled to repeatedly mention during the interview.
Systems Engineer Interview (Positive Experience; Average Interview)
I applied online and the process took 2 weeks - interviewed at Omgeo.
Interview Details – Phone screening, then face-to-face interview with multiple people.
Negotiation Details – Back and forth between HR
Business Analyst Interview (Negative Experience; Average Interview)
I applied through a recruiter and the process took 2 weeks - interviewed at Omgeo in October 2012.
Interview Details – I was contacted through LinkedIn about scheduling a phone interview., and I replied with my number and a time that worked for me. The recruiter from the company replied saying he would give me a call at the prescribed time. Being at work, I had to find an empty office to hide in for a bit, and waited for the call. 45 minutes later, I emailed him back stating I could not wait any longer, and I would need to reschedule. He replied that was fine (without any explanation about the no-call), and we were back on for the following Monday.
After the phone interview, later that same day he scheduled an in-person interview for the following week. I met with him, and then three people from the group. The next morning I sent a thank you email and he replied that the hiring manager would be out until the end of the next week, and he would contact me then regarding the "next steps in the process". He never contacted me back, and that was that.
Pretty straight-forward interview process, all things considered, but the communication was pretty dreadful. The only unsettling thing I found was the position was opened due to the prior hire being relieved of their duties a month into the job due to inconsistencies on their application. Two people mentioned this during the interviews, which I found a bit strange, as I wasn't sure why this was necessary to share with a candidate.
That said, it seems like an interesting role and some good things are going on at the company.
Interview Question – Nothing really difficult or out of the ordinary. All three people asked most of the same generic questions, so by the third person I had serious deja-vu. Answer Question
Performance Engineer - Silk Performer Interview (Positive Experience; Easy Interview)
I applied through a staffing agency and the process took 3 days - interviewed at Omgeo in April 2010.
Interview Details – 1. Contacted by Staffing Agency for the position.
2. Initial screening by staffing Agency in Silk Performer - very basic questions on Silk Performer scripts
3. 1st Round with Performance Test Team Manager - Basic Silk Performer Scripting Questions
4. Round 2 - Performance Lead - basic Silk performer Scripting and Workbench Questions
5. Round 3, 4, 5 - Discussion with 3 individuals from the Performance team.
6. Some questions from SilkTest and Functional Testing encountered. Although irrelevant for this position, it was fun to answer them.
7. After 5 rounds Omgeo decided to go with a local candidate.
8. Not a full fledged performance engineering interview. No questions on performance tuning, Result analysis.
Interview Question – Difference between thinktime, wait, waitfor and halt Answer Question
Software Engineer Interview (Neutral Experience; Difficult Interview)
The process took 2 days - interviewed at Omgeo in November 2007.
Interview Details – The interview process was interesting. It consisted of several phone screens, and an all day interview with about 7 people, from engineers to the director of technology. I was tested in design, implementation, debugging, and communication. They also bought me lunch.
Interview Question – They asked me to describe the most complicated system I have ever build. Answer Question
Technology Manager Interview (Positive Experience; Average Interview)
I applied through a recruiter and the process took 1+ week - interviewed at Omgeo in May 2009.
Interview Details – Typical interview process with an initial phone screen followed by an in-person interview with a few different team members. The questions ranged from technical experience to behavioral situations.
People seemed to be very positive but realistic about expectations.
Interview Question – Talk about a project you have led. Answer Question