It's all relative. If you compare jobless to working at Q, then of course it's better to have a job. So the pro is: at least you have a job.
If you don't want a long-term career, don't want to be properly rewarded for your time and effort, and don't want an interesting job, then it is good for you.
Too many. First of all, they have many of their people leave good feedback here to cover up their terrible business practices. So, I would go to other websites and/or get hold of real people working at Q for more accurate info.
Overall, don't expect a long-term career since the good spots are already occupied by Chinese and Indian people who are horrible at mid to senior management.
Don't expect to get rewarded properly for your time (a lot of your time) and effort, and when it's time to let people go, you are most likely the first since they protect the people in their small circles.
They also hire many H1B to replace Americans and/or older people. It's still a bargain to hire young, fresh H1B at even the American workers' price since they work extremely long hours, so the company gets a huge investment return out of them at the same price. American workers simply won't work 60+ hours weekly regardless of pay.
The reason why H1B work extremely long hours is because Q threatens to not petition for their green card unless they work extremely long hours so Q can get a much greater investment return. Therefore, there is no reason why they want to hire American workers even at the same price.
So, a Green Card IS the ultimate leverage Q has against H1B and highly qualified American tech workers who can't find jobs taken by H1B.
None as they are SIMPLY DESPICABLE
1. HR will contact you for basic information. 2. Your manager will ask about your skills and interview you with Linux questions. 3. You will interview with the team and with some basic Python questions. 4. Interview by the director or even VP.
The interview covered SystemVerilog and UVM questions. I was tested on design logic such as flip-flops and multiplexers (MUX), including the implementation of gates using MUX. A couple of behavioral questions were also asked.
A phone interview with the hiring manager was followed by an onsite interview. I received an invitation for the onsite interview the day after the phone interview. The onsite interview was scheduled 10 days later. I was interviewed by all the team
1. HR will contact you for basic information. 2. Your manager will ask about your skills and interview you with Linux questions. 3. You will interview with the team and with some basic Python questions. 4. Interview by the director or even VP.
The interview covered SystemVerilog and UVM questions. I was tested on design logic such as flip-flops and multiplexers (MUX), including the implementation of gates using MUX. A couple of behavioral questions were also asked.
A phone interview with the hiring manager was followed by an onsite interview. I received an invitation for the onsite interview the day after the phone interview. The onsite interview was scheduled 10 days later. I was interviewed by all the team