I have honestly loved my time at RQ so far. Here's why it's been a great place to work:
Autonomy: The company has appropriately high expectations and gives engineers the autonomy to meet those given each engineer's individual skillset. Engineers are expected to come up with solutions to issues and not just rely on someone telling them what the solution is.
Change: In the few years I have been here, I have been able to make quite a few major changes to both processes and code, with the goal of doing things in a more efficient way, or a more future-proof way. Just because RQ has done something one way in the past, at least on the engineering side, has not prevented my ability to look at new things and do things differently.
Zero blame culture: I have the ability to break things quickly, but I also have the ability to fix things quickly. And fixing things is a team sport instead of just blaming individuals who contributed to the break.
Tech stack: Without going into details, we have a cutting edge tech stack here at RQ, using all the latest CI/CD and IOC keywords. We are also always looking to do things better, and engineers are encouraged to bring ideas to the table.
My cons are mostly focused on internal tools and culture. I would love to see more purposeful internal diversity efforts, especially around LGBTQ. For example, an internal LGBTQ club etc would be a welcome addition.
I would also love to see more internal clubs that may not be focused on just RQ. We had a motorcycle group that was fairly active as an example, and it just disappeared one day.
We should bring back the kombucha machine.
We should also allow more interest groups to be created through teams etc.
2 Cultural interviews with the recruiter followed by a technical interview. I was turned down for the role, which happens. And they gave feedback, which I appreciated. But the feedback was strange. They said they wanted someone better at coding.
Take home project. I spent time and tried using React in Java which I'm not very familiar with, so my mistake there, but whoever reviewed it claimed I didn't do things that I did do and rejected me because of it.
A recruiter reached out online, followed by a 30-minute HR screening call. The next step is a take-home assignment. After that, there is an onsite interview with the hiring manager, followed by a technical interview with two senior engineers. The fi
2 Cultural interviews with the recruiter followed by a technical interview. I was turned down for the role, which happens. And they gave feedback, which I appreciated. But the feedback was strange. They said they wanted someone better at coding.
Take home project. I spent time and tried using React in Java which I'm not very familiar with, so my mistake there, but whoever reviewed it claimed I didn't do things that I did do and rejected me because of it.
A recruiter reached out online, followed by a 30-minute HR screening call. The next step is a take-home assignment. After that, there is an onsite interview with the hiring manager, followed by a technical interview with two senior engineers. The fi