Chronosphere logo

Chronosphere Interview Questions
& Process

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

Based on 29 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
34.5% Positive experience

Which role are you interviewing for?

14 roles · 29 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Chronosphere.

Showing 4 of 29
Chronosphere logo
Chronosphere

Engineering Manager

Engineering · a year ago

Manager Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral System Design Presentation

The recruitment team calls you for a very brief 5-minute chat, speaking really fast. They then move you to the interview loop without really getting to know you or explaining the job or company. In one interview, the interviewer was yawning and seemed uninterested. The final round involved meeting very senior leadership who asked rapid-fire questions. I noticed they were distracted, checking emails and switching computer windows, even though it was behind a glass reflection. The senior leaders seem to have come from Uber. After all these rounds, I was ghosted.

Confirmed questions2 questions
  • The leadership interviews included many questions asking about past experiences, like 'Can you tell me about a time...?'
  • One question was about system design, asking me to explain the architecture of something I had worked on.
Chronosphere logo
Chronosphere

Software Engineer

Engineering · more than a year ago

Mid Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Coding Behavioral

Started with a recruiter call, which was cool. They were upfront about salary, which I liked. After that, things went downhill. I had a coding screen that lasted about an hour. The interviewers gave minimal feedback while I was coding, which felt like inexperience. Live coding feels awkward, and I think interviewers should offer some encouragement or guidance. I got barely any feedback. They also told me not to write unit tests, just to test within the main function, which was a bad move. The tests were slow and poorly designed, and unit tests would have made them better. It felt unprofessional. I had a chance to ask questions, but the interviewers seemed tired and their requirements seemed messy. The whole coding screen and follow-up discussion was so bad I almost withdrew. But I got a rejection a few days later, so I didn't have to.

Confirmed questions2 questions
  • You require an NDA for a screening question that's publicly accessible; how do you justify this?
  • For a live coding interview, how do you assess a candidate's skills with a question that, while "real world", might not effectively measure competency?
Chronosphere logo
Chronosphere

Product Manager

Product · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Presentation
Interview formats
Presentation Behavioral

The hiring process was pretty bad. After getting past the hiring manager interview, I was told the next set of interviews, which included a 45 minute presentation, would be scheduled right away. I started working on the presentation, but then days went by. I figured it was because of the holidays and reached out to the recruiter again. She told me a few times, after significant delays each time, that the hiring manager was on vacation and the interview would be scheduled soon. Then she said it would be scheduled within 48 hours. What a joke. I already spent a lot of time on the presentation. Then the recruiter emailed to say they had filled the position. If they knew they had a candidate who was late in the process, they shouldn't have made other candidates spend a lot of time on presentations. Honestly, I felt disrespected as a candidate, and I'm concerned about what this implies about their company culture.

Confirmed questions1 question
  • Create a 45-minute presentation.
Chronosphere logo
Chronosphere

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Background check
Interview formats
Behavioral Technical

We had an initial casual remote chat. I talked with the head of engineering about the company and its work, just to see if we were a good fit. It went well, the person was nice and answered my questions. Then there was a more formal chat with the same person, or maybe another engineer. This one was more about my background and expertise. The next steps were supposed to be a technical assignment, a technical interview, and a soft skills interview or two. But they mentioned they were really looking for more senior folks with experience in large distributed systems and high loads, which I didn't have. Still, they were upfront and nice about it, making it feel like a pleasant conversation.

Confirmed questions2 questions
  • Can you tell me about the toughest technical challenge you've faced?
  • What is one thing you would choose to teach someone?

Chronosphere Interview Questions

Quoted word for word from Chronosphere interview reports.

Can you design an alerting system that monitors values at regular intervals and sends notifications when the state changes?

Read reports

Given a design mockup of a proposed web app screen, describe how you would structure its frontend architecture.

Read reports

You require an NDA for a screening question that's publicly accessible; how do you justify this?

Read report

What does ownership mean to you in a professional context?

Read report

For a live coding interview, how do you assess a candidate's skills with a question that, while "real world", might not effectively measure competency?

Read report

Formats, difficulty and experience

Across all 29 Chronosphere interview reports.

Interview formats

Behavioral 36.7%
Technical 21.7%
Coding 15%
Presentation 13.3%
System Design 8.3%

Interview difficulty

Easy 10.3%
Average 65.5%
Difficult 24.1%

Candidate experience

Neutral 10.3%
Positive 34.5%
Negative 55.2%

Reports by job function

Engineering 13
Product 4
Sales 4
Operations 2
HR 2
Other 2