Everyone in my office put in at least 60+ hours each and every week almost without fail. The higher you're promoted, the worse it gets.
Nobody uses proper bug tracking software, release software, and documentation is poor and scattered everywhere, so everyone e-mails everyone with everything. You end up with hundreds of e-mails a day, maybe 1% of which you actually care about. It wears you down after a while.
This is not a software company; they're a hardware company that writes driver software. So expect poorly written and poorly designed code written with a "just make it work" mentality.
Too many products and little-to-no code reuse, so instead of focusing on having one good codebase, you'll end up with 50 crappy ones.
Everyone is really stressed and tense, so the culture around the office is not the most pleasant.
If you work in the Markham office, it's a satellite office and San Diego HQ makes sure you know it at every turn. Expect super slow VPN access, 4-6 hours to sync using P4/Git, no on-site gym except for the hole-in-the-ground in the basement that they'll reimburse you for.
Management is actually doing a good job driving the company with a clear message and goals, all the way down from CEO to low-level managers. Your review system is awesome.
BUT I would really consider how hard you drive your employees. I hear management say, "we want you to have good work-life balance," but I don't feel like they mean it. Everyone I talk to always seems exhausted, and I can't help but think to myself what quality of work you're getting from someone who can't remember what outside looks like.
If you want good quality software, you have to invest in improving the codebase you already have or you'll scare away talented developers. Get some courses on software design and get your employees trained up. It's scary that almost no developers knew what Dependency Injection is, or Factory Pattern, etc.
Computer science is important, whether you work at Google or you're developing drivers for a SoC.
The hiring process takes a very long time, which can be frustrating. The interview process was challenging but a lot of fun. About a month after submitting my resume, I received an email to schedule a phone interview. This initial call was to determ
3 rounds 1. The first few rounds will cover Data Structures and Algorithms (DSA) questions. They will include topics like arrays, linked lists, trees, and other data structures. 2. They will ask a few puzzles. 3. Your previous experience and the cha
The process took two weeks, starting with a telephone interview followed by an on-site visit. I was interviewed by the hiring manager and the software director. I was called on-site after the phone interview. I received the offer the next day. My
The hiring process takes a very long time, which can be frustrating. The interview process was challenging but a lot of fun. About a month after submitting my resume, I received an email to schedule a phone interview. This initial call was to determ
3 rounds 1. The first few rounds will cover Data Structures and Algorithms (DSA) questions. They will include topics like arrays, linked lists, trees, and other data structures. 2. They will ask a few puzzles. 3. Your previous experience and the cha
The process took two weeks, starting with a telephone interview followed by an on-site visit. I was interviewed by the hiring manager and the software director. I was called on-site after the phone interview. I received the offer the next day. My