Thrashy. Things change frequently. We go in circles with some decisions. I think this is the standard startup situation, but Opendoor certainly has its fair share of thrash.
Product is stretched thin. This means that engineers on some teams will work more directly with stakeholders than at other companies. Personally, I like this, but it's not for everyone.
Compensation is slightly above market, but if you can get hired at Opendoor you could probably make more (at least in cash) at some other companies. This is probably more true the more senior you are.
We are not profitable (yet). As a result, Opendoor is not as cushy as a high-margin business might be (many of the 'lavish' perks, like the headphone stipend, have gone away over the years).
We laid off a bunch of people in March to be very careful/conservative with COVID's impact on the economy. However, we managed to perform quite well during this period, and business is doing great now. If anything, we showed that our business model can react quickly to macro swings.
Pay engineers better and get Opendoor profitable
Firstly is an OA test. Then, you'll receive a call from HR to discuss the test and the next steps of the interviews. Following that is a general technology interview with a LeetCode-type question.
The onsite interview was pretty basic: two coding and two "design architecture" questions. The funny thing was, the first design question wasn't a design question at all. They had me confused with sending a "data engineer" to interview me. The guy l
Huge disconnect between companies' recruiting team and the actual position. I spoke with the recruiter first about an SE position. They set up a call with an SSE later. When I got to that interview, I was told that they were looking for someone almo
Firstly is an OA test. Then, you'll receive a call from HR to discuss the test and the next steps of the interviews. Following that is a general technology interview with a LeetCode-type question.
The onsite interview was pretty basic: two coding and two "design architecture" questions. The funny thing was, the first design question wasn't a design question at all. They had me confused with sending a "data engineer" to interview me. The guy l
Huge disconnect between companies' recruiting team and the actual position. I spoke with the recruiter first about an SE position. They set up a call with an SSE later. When I got to that interview, I was told that they were looking for someone almo