Observe (CA) Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Observe (CA).
Observe (CA)
Software Engineer
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)
Software Engineer
Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral
The recruiter reached out to me. They didn't seem very friendly or interested in discussing the company, despite initially expressing excitement about my background. This lack of engagement was disappointing, especially considering the company's reputation for diversity issues, which seemed evident in their hiring approach.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Observe (CA)
Software Engineer
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) Software Engineer Interview Questions
Quoted word for word from Observe (CA) interview reports.
“Can you write code to check if a string is a palindrome?”
Read 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 →“How would you implement common subexpression elimination?”
Read reports →“Could you implement a cache that handles concurrent reads?”
Read reports →“Could you explain how to implement topological sort?”
Read report →“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 →“Tell me about OS memory management.”
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 6 Observe (CA) interview reports.