InfluxData logo

InfluxData Interview Questions
& Process

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

Based on 71 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
71.8% Positive experience

Which role are you interviewing for?

27 roles · 71 reports

Candidate interview experiences

First-hand accounts from people who interviewed at InfluxData.

Showing 4 of 71
InfluxData logo
InfluxData

Account Manager

Sales · more than a year ago

Mid Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The internal organization was terrible. They changed interviewers without telling me, there was internal criticism, they changed the interview's direction, and the interviewer was narrow-minded and incapable of thinking outside the box. This is about a specific interviewer, not the whole company.

Confirmed questions4 questions
  • Which MEDDIC letter is most critical?
  • Let's try this again: sell yourself.
  • You acquired all necessary information, but not in the manner anticipated.
InfluxData logo
InfluxData

Technical Support Engineer

Engineering · more than a year ago

Entry Easy Neutral experience No offer 1 round
Interview process
Recruiter call Technical screen Offer
Interview formats
Behavioral Technical

It was a remote interview. I wasn't going to accept anyway due to layoffs, but I did it for practice. The first question was the usual 'how did you find us?' Then they asked about a core technology that wasn't on my resume. I admitted I hadn't worked with it, and the interviewer immediately said that disqualified me. I thanked them, and they weirdly said 'Speak to you soon.' I thought that was it, but two days later, HR sent a standard rejection letter saying the hiring manager made a tough decision. It's just another example of how sketchy employers are with potential hires these days, so impersonal.

Confirmed questions2 questions
  • How did you learn about our company?
  • Can you tell me about your experience with [specific core technology not on CV]?
InfluxData logo
InfluxData

UX Engineer

Design · more than a year ago

Mid Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Technical Presentation

Applied in early December and got a response two weeks later, right before the holidays. A week after that, I had a 20-minute screening call with a Product Designer. About a week passed before I heard back to proceed to the next stage: a take-home assessment where I had to make some changes to their design system. Another week later, I interviewed with the Design Manager to discuss the assignment and other things. A few days after that, I was informed they selected another candidate. The entire process lasted a bit over a month. The recruiter was very pleasant and addressed all my inquiries about the company. I'd consider reapplying in the future.

Confirmed questions2 questions
  • Can you explain the design choices made for the assessment?
  • What are your suggestions for enhancing the current design system?
InfluxData logo
InfluxData

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding

The interview process was super efficient and straightforward. I first met with the hiring manager, then spoke with two team members, a cross-team interviewer, the VP of my division, and finally the HR manager. This all happened within one week, which was awesome because most companies take way longer. The hiring coordinator was really flexible with scheduling. Since it was for a software engineer role, the peer interviews were very technical, featuring real-world live-coding challenges and discussions, not typical leetcode style problems, but more focused on engineering realities. My only minor complaint is that the company culture part felt a bit standard – like every company says they value employees, want to get things done, and are humble. It was hard to tell if they truly lived those values or just said them. I don't have a great idea on how they could better show their commitment, maybe with examples, but I can say that since I've been hired, it's clear they genuinely mean it. All in all, it was one of the best interview experiences I've had regarding speed, fairness, and practical approach.

Confirmed questions6 questions
  • How does your previous experience align with the requirements of this role?
  • Do you fit with the company's values?
  • Could you tackle this programming problem relevant to the job?

InfluxData Interview Questions

Quoted word for word from InfluxData interview reports.

Could you implement a function that checks if a given string has balanced parentheses?

Read reports

Can you filter data using the Grafana API based on collector type and datasource type, given that the data is in JSON format? Any programming language is fine for the solution.

Read reports

Can you explain the difference between open source and paid products?

Read reports

What are some difficulties that come with building or using distributed systems?

Read report

What frameworks are related to the tools and languages the teams use?

Read report

How would you design a system for batch processing items?

Read report

What are the typical steps involved in onboarding a new customer?

Read report

Formats, difficulty and experience

Across all 71 InfluxData interview reports.

Interview formats

Behavioral 45.5%
Technical 36.6%
Coding 7.6%
Presentation 6.2%
System Design 2.8%

Interview difficulty

Easy 12.7%
Average 83.1%
Difficult 4.2%

Candidate experience

Negative 15.5%
Positive 71.8%
Neutral 12.7%

Reports by job function

Engineering 37
Sales 14
Marketing 5
Design 4
HR 3
Analytics 2