OpenSpace (CA) logo

OpenSpace (CA) Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 34 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
50% Positive experience

Which role are you interviewing for?

16 roles · 34 reports

Candidate interview experiences

First-hand accounts from people who interviewed at OpenSpace (CA).

Showing 4 of 34
OpenSpace (CA) logo
OpenSpace (CA)

DevOps Engineer

Engineering · a year ago

Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

The application process was standard, but required more than just the usual info like name, email, and resume, also asking for voluntary self-identification and LinkedIn/phone number, which is a bit much. After a few weeks, I got an email for a phone screening. During the call, the interviewer asked some basic personality and legitimacy questions and talked a lot about needing a k8s expert, which felt like a red flag. After passing that, I had an interview with the hiring manager. He also focused heavily on k8s, mentioning the need for someone responsive to handle unplanned work. When I asked about the team's k8s experience, he was vague. I got a rejection email the next day. It seems like they jumped on the k8s trend without a clear plan and now need an expert to fix it, but they're looking for an unobtainable ideal.

Confirmed questions1 question
  • Have you worked with k8s in a production setting? How would you describe your expertise level with it?
OpenSpace (CA) logo
OpenSpace (CA)

IT Operations Manager

Operations · more than a year ago

Manager Easy Negative experience No offer 7 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The interview process was quite disorganized. It spanned two months and involved seven interviews, each lasting at least 45 minutes, which was inconvenient. Communication was poor, with a month-long delay in response after applying. During the initial interview, the recruiter repeated the job description despite being informed I had read it. Scheduling was difficult, sometimes with less than 12 hours' notice, and updates were only provided upon request, often using templated messages. I had to proactively schedule my own interviews. The role had been open for a while, suggesting uncertainty about the hiring needs. Despite positive feedback after all interviews, no candidate was selected, indicating a flawed hiring process that didn't effectively fill the role. While the team and company seem decent, the hiring experience can be a significant time investment with an uncertain outcome, even with positive feedback.

Confirmed questions1 question
  • Tell me about a mistake you made and what you learned from it.
OpenSpace (CA) logo
OpenSpace (CA)

Inside Sales Representative

Sales · more than a year ago

Entry Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Onsite
Interview formats
Behavioral

I applied on LinkedIn, and setting up interviews was straightforward. The process was smooth, and they didn't require any pre-work like prospecting, drafting emails, or mock calls. This was different from other roles I applied for that had a lot of homework. I had a couple of interviews, and everyone I met was likable and interesting. I noticed that they really focus on hiring people who fit the company culture.

Confirmed questions2 questions
  • They asked me a lot of questions about myself to really get to know me.
  • He asked me about the gap in my work history and seemed impressed that I took the leap to find the right opportunity.
OpenSpace (CA) logo
OpenSpace (CA)

Front End Developer

Engineering · more than a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Coding

So I started with a recruiter call, then I talked to a co-founder which was pretty cool, then I had a great chat with a front-end engineer. After that, it was all downhill. They gave me a take-home coding challenge and I finished it in two days. But then, I couldn't figure out how to submit it and the front-end engineer didn't give me their email. I tried reaching out to the recruiter three times with no luck. I even tried guessing the engineer's email, but no response. I feel like they ghosted me and I'm super disappointed because I put time into that code challenge and it wasn't even looked at. They should at least have the decency to email back and say they're not moving forward.

Confirmed questions1 question
  • Could you code a tooltip component using React?

OpenSpace (CA) Interview Questions

Quoted word for word from OpenSpace (CA) interview reports.

Could you fork a provided GitHub repository and implement Cypress tests for the included React date-picker web app?

Read reports

Could you build a React site based on the provided example API?

Read reports

How would you facilitate customer access to field notes?

Read report

What's your morning routine for setting yourself up for success?

Read report

What do you do to set yourself up for success day-to-day?

Read report

Formats, difficulty and experience

Across all 34 OpenSpace (CA) interview reports.

Interview formats

Behavioral 50.8%
Technical 28.6%
Presentation 7.9%
Coding 7.9%
Group 3.2%

Interview difficulty

Easy 20.6%
Average 64.7%
Difficult 14.7%

Candidate experience

Negative 44.1%
Positive 50%
Neutral 5.9%

Reports by job function

Engineering 10
Sales 8
Operations 7
Marketing 2
Analytics 2
HR 2