Observe (CA) logo

Observe (CA) Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
42.9% Positive experience

Which role are you interviewing for?

2 roles · 7 reports

Candidate interview experiences

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

Showing 4 of 7
Observe (CA) logo
Observe (CA)

Software Engineer

Engineering · half a year ago

Senior Average Neutral experience No offer 2 rounds
Interview process
Technical screen Phone screen
Interview formats
Technical Behavioral

The first part was a technical test, and it seemed to go well. The person interviewing me was either a staff or senior engineer. The next step was a behavioral interview with a different engineer, which I also felt went well, and the interviewer agreed. Unfortunately, after that, I never heard back from them.

Confirmed questions2 questions
  • How do you center a div and text using only HTML, CSS, and JS? Also, how can you adjust styling like text color and size?
  • Can you write code to check if a string is a palindrome?
Observe (CA) logo
Observe (CA)

Sales Development Representative

Sales

Entry Difficult Positive experience Accept offer 2 rounds
Interview process
Onsite Presentation Background check Offer
Interview formats
Behavioral Presentation

They were clear about the job and gave honest feedback. The process involves an onsite interview and a final chat with an executive. Showing you're motivated and keen on sales is key.

Confirmed questions1 question
  • What makes you want to pursue a career in sales?
Observe (CA) logo
Observe (CA)

Software Engineer

Engineering

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen
Interview formats
Technical Coding Technical

The recruiter reached out and things moved really fast, they scheduled everything quickly and in a way that worked for me. I had 4 interviews, each lasting an hour, spread over two days. I think I answered most of the questions correctly, and all the interviewers seemed friendly and knew their stuff. The part I didn't really like was getting mixed signals; it wasn't clear at all how I performed until I got the email saying no offer.

Confirmed questions4 questions
  • Could you explain how to implement topological sort?
  • How would you implement common subexpression elimination?
  • Tell me about OS memory management.
Observe (CA) logo
Observe (CA)

Software Engineer

Engineering

Mid Average Positive experience Decline offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Technical Coding

I was contacted by a recruiter via email, and then connected with their interview coordinator. The interview process was pretty standard for Silicon Valley, starting with a technical phone screen and moving to a virtual on-site. I was a bit surprised by the interview questions, as they frequently had a concurrency component, like a twist. I guess Observe has a lot of critical code that uses channels, so they're looking for engineers who are comfortable with CSP.

Confirmed questions1 question
  • Could you implement a cache that handles concurrent reads?

Observe (CA) Interview Questions

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

How do you center a div and text using only HTML, CSS, and JS? Also, how can you adjust styling like text color and size?

Read reports

Could you implement a cache that handles concurrent reads?

Read reports

How would you design a system to track modifications in a structured map over time and query these changes? What is the time complexity of your design?

Read report

Could you set up your preferred monitoring tool to observe a CI/CD pipeline and then walk me through how you accomplished that?

Read report

Formats, difficulty and experience

Across all 7 Observe (CA) interview reports.

Interview formats

Technical 35.7%
Coding 28.6%
Behavioral 21.4%
Presentation 7.1%
System Design 7.1%

Interview difficulty

Easy 0%
Average 71.4%
Difficult 28.6%

Candidate experience

Neutral 28.6%
Positive 42.9%
Negative 28.6%

Reports by job function

Engineering 6
Sales 1