Get tailored insights about working at Distyl AI in one quick step.
Distyl AI interview questions
based on 4 ratings - Updated Jun 4, 2026
Averageinterview difficulty
Mixedinterview experience
How others got an interview
50%
Recruiter
Recruiter
50%
Applied online
Applied online
Interview search
4 interviews
Distyl AI interviews FAQs
Glassdoor users rated their interview experience at Distyl AI as 25% positive with a difficulty rating score of 3.25 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for SRE/DevOps Engineer and Engineer rated their interviews as the hardest, whereas interviews for ML/AI Engineer and Engineer roles were rated as the easiest.
The hiring process at Distyl AI takes an average of 14 days when considering 4 user submitted interviews across all job titles. To compare, the average duration of hiring at similar companies like BlackRock, Inc. is 14 days, Fabricated Software, Inc. is 2 days, and Apple Inc. is 21 days. Candidates applying for ML/AI Engineer had the quickest hiring process (on average 14 days), whereas ML/AI Engineer roles had the slowest hiring process (on average 14 days).
I applied through a recruiter. I interviewed at Distyl AI
Interview
recruiter -> takehome.
The interviewer was late and in a noisy background. Can't hear clearly.
Takehome exercise took 2-4 hours but only 20 minutes for presentation with not many detailed questions or discussions. and the rest of time is another assignment.
Interview questions [1]
Question 1
self-intro, previous work experience, takehome exercise functions
1. Behavioral Interview based on resume
2. Live Coding for an AI system
3. System Design (AI based)
4. System Design (Backend based)
5. Final Round with Technical Manager
Took approximately 4-5 weeks from start to finish
Interview questions [1]
Question 1
How would you debug an agentic system if users complain about vague outputs?
technical overview of python script and dockerfile. asked questions to correct junior engineer errors. then proof a dockerfile and talk about ci/cd and orchestration of service. then a discussion of past projects