Proton.ai logo

Proton.ai Interview Questions
& Process

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

Based on 22 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
40.9% Positive experience

Which role are you interviewing for?

12 roles · 22 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Proton.ai.

Showing 4 of 22
Proton.ai logo
Proton.ai

Product Marketing Manager

Marketing · nearly a year ago

Mid Average Negative experience No offer 1 round
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

Applied for the PMM role and connected with someone on LinkedIn who was keen to schedule a direct call. The call the following week was unusual; it started with casual questions then immediately became an interrogation without any company or role context. I didn't learn anything new about the company. They asked odd questions like criticizing my current manager and gave vague answers to my questions about company growth, fundraising, and daily responsibilities. I was told I'd get an email back. I sent a thank you email the next morning but received no response. It felt like an organization run by young people who prioritize hiring friends over professionals. The lack of a response suggests my time wasn't valued, and the pressing questions during the initial call were strange. I probably would have declined an offer anyway.

Confirmed questions3 questions
  • Could you rate your current manager on a scale from 1 to 10?
  • What's your personal superpower?
  • What prompted your departure from X company?
Proton.ai logo
Proton.ai

Data Engineer

Engineering · nearly a year ago

Senior Difficult Negative experience No offer 3 rounds
Interview process
Technical screen Technical screen Onsite
Interview formats
Technical Technical Behavioral

The interview process had three rounds. First was a technical screening covering SQL, Python, PySpark, and Airflow, which was clear and relevant. Then, a technical deep dive focused on architecture, pipelines, scaling, and APIs; it was challenging but fair. The final round was with senior leadership and was unexpected, as it focused heavily on personal life, schooling, and past manager feedback, rather than technical skills or professional fit. This felt more like a background check than an evaluation, and the interviewers seemed disengaged, making it feel like a waste of time after three weeks. The technical rounds were good and related to the job, but the final round was disappointing due to its overly personal nature, which wasn't related to data engineering or professional cultural fit.

Confirmed questions8 questions
  • Regarding Python and data handling, how would you read and process an 8 GB text file without running out of memory?
  • For pipeline design and reliability, suppose your pipeline ingests hundreds of CSVs daily from multiple sources, and some arrive late or incomplete – how would you design it to handle these issues?
  • In terms of pipeline reliability, why would you opt for Redis checkpointing over solely relying on Airflow states?
Proton.ai logo
Proton.ai

Software Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Behavioral Technical

The interview process was quite drawn out, lasting about a month. It began with an initial call, followed by two technical interviews. The final stage was a "vibe check" with the CEO and Head of Engineering. They claimed there were no right or wrong answers, but the main question was about my journey from high school. While I shared my story, the questions were basic, like my student type. I asked some unique questions that impressed them. Despite a positive feeling and good initial feedback, I received a generic rejection email two days later. The company also failed to inform the referrer why I was rejected, which was very unprofessional given their supposed culture.

Confirmed questions2 questions
  • Can you walk us through your journey from high school up to the present?
  • What kind of student did you used to be?
Proton.ai logo
Proton.ai

Head of Product

Product

Executive Average Positive experience No offer 2 rounds
Interview process
Recruiter call Phone screen Background check Offer
Interview formats
Behavioral Technical

I applied for this job and had a phone chat with the recruiter. The plan was a 30-minute call, but we ended up talking for almost an hour because I had a bunch of questions. The recruiter was great she knew a ton about the job. It was honestly the most detailed HR convo I've had about a role. She really got into the nitty-gritty of the job, the challenges, and what they needed. She even gave me some straight-up on my gaps compared to others in the process. After that, I had a 30-minute interview with the CEO. It went pretty well - he seemed a little distracted but asked a ton of questions about my background and dove into my work experience. I got a deeper look into the company and the role, which was cool. Left that call feeling like I wish I had more time with him to learn more. The next day, the recruiter hit me up to say they weren't moving forward with my application. Bummer...but hey, at least she was speedy with the news. I shot her a follow-up asking for some feedback, and she got back to me fast with some helpful insights. All in all, I appreciated how fast things moved, even if the outcome wasn't what I hoped for.

Confirmed questions2 questions
  • The recruiter asked a bunch of questions about my current product role, like our customer type/size, the average contract size, how I collaborated with engineering to push features, and how much time I split between individual contributor work and management tasks.
  • Less question and more of discussion in the call with the CEO

Proton.ai Interview Questions

Quoted word for word from Proton.ai interview reports.

Regarding Python and data handling, how would you read and process an 8 GB text file without running out of memory?

Read reports

In terms of pipeline reliability, why would you opt for Redis checkpointing over solely relying on Airflow states?

Read reports

If a late file arrives and the source team requests a reprocess, how would you execute a DAG rerun?

Read reports

Regarding API usage, would you call APIs on every page load? If not, where would you store and serve the data from?

Read reports

If you had to store data in SQL or Elasticsearch instead of Parquet files, how would you optimize the writes?

Read report

You mentioned indexing; how does indexing impact database writes?

Read report

If the processing itself is optimized but storage writes are still slow, what aspects would you investigate and optimize?

Read report

Regarding file pickup reliability, are you using Airflow sensors or schedules, and how do you select which to use?

Read report

For APIs and real-time data, if an API experiences downtime, timeouts, or rate limits, how would you design your pipeline to handle it gracefully?

Read report

Formats, difficulty and experience

Across all 22 Proton.ai interview reports.

Interview formats

Behavioral 40%
Technical 32%
Presentation 18%
Group 4%
Coding 4%

Interview difficulty

Easy 13.6%
Average 72.7%
Difficult 13.6%

Candidate experience

Negative 36.4%
Positive 40.9%
Neutral 22.7%

Reports by job function

Engineering 8
Marketing 4
Sales 3
Product 2
HR 2
Design 2