Cribl Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 23 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Cribl.
Cribl
Software Engineer
Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Take home
Interview formats
Technical Coding
I went through a recruiter screen, then a hiring manager screen, and then a take-home assignment. After talking to the HM, they said the next step was a take-home challenge. They asked for my GitHub username and sent the challenge the next day. I worked on it over the weekend and sent it in Monday. I messaged the recruiter Tuesday and got a rejection email right away. I asked for feedback but they ghosted me. The HM mentioned in a Slack group recently that they're still hiring for the role.
Confirmed questions1 question
- Can you describe the most technically challenging project you've undertaken?
Cribl
Software Engineer
Staff Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Presentation
Interview formats
Coding Technical Presentation
It was a 4-stage process: first an HR screen, then a chat with the Hiring Manager, followed by an online coding test, and finally a tech talk round. I had a really good experience overall; everything was well organized. The recruiter was helpful and always got back to me with feedback in a timely manner.
Confirmed questions5 questions
- Complete coding tasks and develop minor features in the online coding assessment.
- Address a range of questions with varying difficulty levels during the 60-minute tech talk.
- Demonstrate your understanding of real-world software development challenges through your answers.
Cribl
Software Engineer
Senior Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding
I interviewed for the search team and spoke with the recruiter, then the hiring manager. I also completed a take-home assignment which I later discussed with some engineers who seemed senior. They didn't seem to know how Node.js streams work, which was surprising. Discussing the take-home was amusing and discouraging due to their bad attitude, lack of smiles, brief introductions, long silences, and unclear questions. It felt like they wanted me to just agree with their solution. The team's culture felt misleading compared to their Glassdoor profile. The engineers barely knew basic info about each other, showing how siloed the team is.
Confirmed questions1 question
- Could you design a REST API that allows users to get logs from various Unix servers without needing to log in to each one individually, with customization options?
Cribl Software Engineer Interview Questions
Quoted word for word from Cribl interview reports.
“What are TCP/UDP protocols?”
Read reports →“Could you explain the difference between TCP and UDP?”
Read reports →“design a log collection server api”
Read reports →“Can you explain the difference between soft and eventual consistency?”
Read reports →“design a bonus ui”
Read report →“Design a log searching service”
Read report →“design a multi-server system for the second bonus”
Read report →“Can you build an endpoint that reads a file over 1GB and returns lines containing certain keywords, based on parameters like file path, keywords, and number of rows?”
Read report →“Can you describe how to design a system for reading a 100GB file?”
Read report →Formats, difficulty and experience
Across all 23 Cribl interview reports.