- Comp & Benefits
- Work/Life Balance
- Senior Management
- Culture & Values
- Career Opportunities
I worked at On-Site.com full-time (more than 3 years)Pros
I worked closely with both Engineering and the CEO, and sometimes with the support team also. I liked everyone I worked with very much. It was fun, at least for me. It is true there are managers who are inexperienced. This is the flip side of promoting from within, which how these managers became managers.
The CEO can appear to be unapproachable, but I always found that if I jumped in the office with a problem, he listened, was receptive and helpful, and addressed it. I think several remarks made in other reviews are very unjust. I really liked the CEO and all of the management. I enjoyed working for them.
At the time I was working here, I was paid in the top range of my field at the time. My reviews were regular and helpful, and raises were generous.Cons
The business operates similarly to a start-up, though they are now established in their market. Everyone works hard. Comp time was frowned on, but when I asked for it, I always got it.
When I was there, Engineering development happened without anything I would now consider to be minimal QA.
Leadership didn't communicate well with each other or to the team as a whole. This really hurt the business, both in terms of morale, and in leading to decisions that were bad for the team, product and brand.
Most of the executive team became the executive team while they were at this company. They have not taken management classes, or worked in other companies where they would learn management norms or how good and bad management looks to an employee. However, they are good people who are interested in running a good business - ultimately are succeeding in running a good business. So if you're interested in being a part of that, this will be a good place for you.Advice to ManagementAdvice
(Thumbs up for the perks!)
Weekly or every-other-weekly meetings, even just a stand-up, with the entire team to let them know how the business is doing and whatever is going on week to week would really have helped during the time I was there. When people don't know why any decision has been made, the decision looks random. Decisions that seem random always seem bad. So when you don't communicate, it seems to your team that you are making random, bad decisions. That ultimately erodes trust and satisfaction for your team.
Don't focus exclusively on feature development, and start streamlining the product and code base. Some recent products out there that have fewer features work a lot better.
A real QA team that can set up and maintain automated testing is way overdue, if one hasn't been established.Approves of CEO
Getting an Interview
Getting an Interview
1 person found this helpfulApplication Details
I applied through a staffing agency. The process took a day – interviewed at On-Site.com in March 2013.Interview Details
The interview was arranged by an area staffing agency. They told me that they were highly confident I would get the position, due to my past experience.
I felt everything was going great while I was interviewed by HR personnel. I was asked questions about my past experience, my CS style, how I handle irate callers, previous employers' talk times and metrics, etc.; the second part was the CEO interview.
His first question was if I rented or owned my home. A renter, he seemed surprised at the name of my apartment complex and made a comment that residents needed to have "a lot of disposable income" to live there. Personally, this part of the interview process was awkward and irrelevant.
He asked me if I had interviewed for any other companies in Silicon Valley. Due to a non-disclosure agreement, I couldn't say who. Visibly annoyed and refusing to move on, he spent a good chunk of time asking probing questions about the company, instead of continuing the interview.
He asked what highways I took to get there from my apartment.; the ensuing conversation was not relevant to my interview.
A last-ditch effort to impress, I mentioned how 50% of the U.S.'s population lives within 500 miles of Akron, OH, to which he stated he was going to Google, ASAP. He then handed me a stack of papers to fill out and left, without describing who or what was next in the process. I sat in the room for about 30 minutes until a man came and said he was told to take me back to the receptionist's area.
I sat there for yet another 15 minutes, until the CEO happened to come and see me there. He actually stated, "You're still here? I told them to tell you to leave." He then personally signed me out, but not before mentioning that the population was 45%, not 50. And I left the premises.Interview Questions
No OfferNegative ExperienceDifficult Interview
- Almost all of the CEO's questions were unexpected. He never really asked me questions relevant to my work experience or the interview at hand, or why I wanted to work for his company--or any other typical interview questions. Answer Question
- Please try to be as detailed as possible regarding the technical question, business case, etc. Answer Question
Let us know if we're missing any workplace or industry recognition –