Logz.io logo

Logz.io Interview Questions
& Process

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

Based on 27 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
51.9% Positive experience

Which role are you interviewing for?

16 roles · 27 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Logz.io.

Showing 4 of 27
Logz.io logo
Logz.io

Customer Success Engineer

Engineering · more than a year ago

Mid Easy Neutral experience No offer 6 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Panel
Interview formats
Behavioral Technical Other

The interview process involved about 5-6 rounds. It started with a recruiter call, then a call with the hiring manager. After that, there was a take-home assignment and an in-office assignment. Finally, there were two more calls. I'm marking my experience as neutral/negative because they reached out to me for a Customer Success Engineer role, but then in round 3, they decided I didn't have enough experience, which was strange given they initiated the process after reviewing my resume. Additionally, they weren't willing to offer more money than I was currently making. I was primarily interviewing to gauge the company's environment, and based on speaking with the hiring manager, it seems like they are still an early-stage company with some potential volatility, aligning with other reviews.

Confirmed questions1 question
  • Can you share an instance where you exceeded expectations in your role?
Logz.io logo
Logz.io

Technical Support Engineer

Engineering · more than a year ago

Entry Difficult Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Presentation Onsite Background check
Interview formats
Behavioral Technical Coding Presentation

It started with a recruiter call. Then, I had an interview with the team lead to assess my knowledge, background, and personality. After that, I spoke with HR. Then, the team lead interviewed me again for a technical assessment. They gave me a live assignment to demonstrate my understanding of the platform's behavior and how to work with it. This included technical aspects like filebeat, kibana, logs files, configuring log files, uploading them, creating new visualizations, or identifying error occurrences, specific HTTP methods, or responses like 200. Finally, I interviewed with the manager above the team lead. The process also included a background check.

Confirmed questions4 questions
  • What's your approach to troubleshooting issues?
  • How do you handle pressure during a critical situation?
  • Could you elaborate on your professional background?
Logz.io logo
Logz.io

Senior Software Engineer

Engineering

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen
Interview formats
Behavioral Technical Coding

It started with a recruiter call, as expected. Then there was a 30-minute questionnaire with 3 real-life scenarios to solve. I thought the next part was a 1-hour technical interview, but it turned out to be more of a product and company promotion discussion, where they also answered my questions, with just a few tech questions at the end. The final round was a 2-hour coding session on a Sunday to build a pipeline, followed by a 1-hour Q&A. The pipeline task description had errors and wasn't clear that a library, not an app, was needed. I built an app and got stuck. The interviewer seemed uninterested, constantly checking his phone. It felt like a 'guessing game' where you had to read their mind to find the one 'correct' solution, as other ideas were rejected.

Confirmed questions3 questions
  • Regarding the pipeline, how would you approach its configuration?
  • Could you discuss caching mechanisms for the pipeline?
  • What are your thoughts on implementing time limit throttling for the pipeline?
Logz.io logo
Logz.io

Customer Care Engineer

Engineering

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Onsite Take home
Interview formats
Technical Behavioral

After my referral resume was submitted, I was contacted via email by an admin within 1-2 weeks to set up an interview. I was expecting some delays given it's a fast-paced startup. I was interviewed during a staff lunch, which gave me a good informal feel for the office culture. I spoke with the department manager about my personal approach and career goals, and then with a current team member about my skills. The interview concluded with a 7-day take-home assignment. This assignment was a genuine test of my skills and understanding of business needs, not unpaid work. The team seemed very motivated and focused, working in a fascinating field. It's a small group of dedicated and intelligent individuals. If your skills align, be prepared for mentorship and guidance. I identified areas where I could improve but was glad for the opportunity to meet everyone.

Confirmed questions1 question
  • How would you approach and resolve unfamiliar networking or coding problems?

Logz.io Interview Questions

Quoted word for word from Logz.io interview reports.

Build a Kubernetes cluster with multiple nodes, integrating it with Logz.io's telemetry tracking to show data transmission between nodes.

Read reports

Could you write a component (a Class) that writes log messages (Strings) to the file system? It needs to be non-blocking and write to a single active file. It also needs to be thread-safe so multiple threads can write to it at the same time. The configuration parameter should be directoryPath – the directory where log files are saved. Your class needs to implement this interface: public interface FileSink { void write(String logMessage); }. For testing, use JUnit or a main method to validate these scenarios: writing one line, writing multiple lines, and writing multiple lines from multiple threads. Make sure your test checks that all messages written to the FileSink are actually present. Each thread should write 10,000 unique messages. Each test must validate that the scenario actually worked (not by manually checking the output). Important Note: Have working software by the end of the time limit. Time limit: 2 hours. Good luck!

Read reports

What are your thoughts on implementing time limit throttling for the pipeline?

Read reports

Could you outline a solution for building a processing pipeline?

Read report

Regarding the pipeline, how would you approach its configuration?

Read report

Formats, difficulty and experience

Across all 27 Logz.io interview reports.

Interview formats

Behavioral 36.8%
Technical 29.8%
Coding 12.3%
Presentation 12.3%
Other 5.3%

Interview difficulty

Easy 22.2%
Average 66.7%
Difficult 11.1%

Candidate experience

Negative 25.9%
Positive 51.9%
Neutral 22.2%

Reports by job function

Engineering 15
Sales 6
Operations 2
Marketing 2
Other 1
Design 1