Smart people.
Decent pay, almost on par with other companies in the Bay Area.
Flexible hours. Work from home. Friendly colleagues.
Older technology. Mostly outdated. Custom-built in-house. Work experience and knowledge gained by Devs and QA are not as useful once you leave the company.
Update the technology stack. This will give Devs and QA something to look forward to. Using the same technologies for the past 10 years adds very little to an employee's resume, as the market is moving very fast. QA testing is limited and mostly manual, which slows down release cycles. Encourage all employees in product development to write code so that productivity increases.
The interview process began with a quick 30-minute phone screen consisting of basic data structures and OOP design questions. I was then invited for a 4-hour onsite interview. I spoke briefly with the recruiter. The onsite interview included: *
The process began with an initial phone screen with a recruiter. Next, I was invited for an online coding test lasting two hours. It was pretty simple, really, emphasizing correctness over performance. The task work was a little repetitive but over
• Wordy puzzle game • Went over the solution with the interviewer. • On-site interview, coding about a coffee-vendor machine.
The interview process began with a quick 30-minute phone screen consisting of basic data structures and OOP design questions. I was then invited for a 4-hour onsite interview. I spoke briefly with the recruiter. The onsite interview included: *
The process began with an initial phone screen with a recruiter. Next, I was invited for an online coding test lasting two hours. It was pretty simple, really, emphasizing correctness over performance. The task work was a little repetitive but over
• Wordy puzzle game • Went over the solution with the interviewer. • On-site interview, coding about a coffee-vendor machine.