
Dev.Pro Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 36 interview experiences · FREE TO READ
Which role are you interviewing for?
17 roles · 36 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Dev.Pro.
Infrastructure Specialist
It started with an HR interview, which was fine. The person was nice. But then the technical interview was terrible. The interviewer seemed unprepared and asked questions that weren't relevant to the job. She was unprofessional, laughing and talking to others during the call. I think the company needs to be more careful about who they assign to technical interviews because I've seen other reviews about similar behavior, and it could cause them to lose good candidates.
- Could you explain the difference between latency and response time?
- How would a user go about generating a 404 error?
Senior QA Automation Engineer
I went through a hiring process for a QA role in July 2025. They said it'd be quick, but I waited over 3 weeks after my technical challenge and interview before hearing anything. The challenge used tools like Selenium, which weren't even mentioned in the job description, so it felt like I was tested on stuff I didn't prepare for. I nudged them a few times, and finally got a basic rejection, no mention of the wait or my work. It was a bummer and really tiring. If you want good communication and a decent experience, maybe skip this one.
- There was a Selenium task not listed in the Job Description.
- The interviewer didn't have an IDE set up for the task.
QA Automation Engineer
I went through a hiring process for a QA role back in July 2025. They said it would be quick, but then I waited over three weeks after my technical challenge and interview with no updates. The challenge used tools like Selenium that weren't even in the job ad, so it felt like they tested me on stuff we didn't discuss beforehand. I had to chase them multiple times before finally getting a standard rejection email, which didn't even mention the wait or my effort. It was pretty frustrating and tiring. Honestly, I wouldn't suggest applying if you expect good communication or a good experience.
- A Selenium exercise was given, which was not mentioned as a requirement in the Job Description.
IOS Engineer
The interview process had 3 steps. First, a chat with HR, super smooth and fast, the interviewer was really nice. They asked about me, my background, and 3 specific tech questions for the role. Then, a 30-minute behavior interview with just behavior questions. The interviewer was friendly, but you gotta know yourself well for this one. Finally, a 1-hour technical interview. They said it would be just about my tech stack, but it included Computer Science stuff like Algorithms and more too. Overall, it went smoothly, and the Dev.Pro team is awesome. Waiting to hear back.
- Can you write a sorting algorithm?
- Could you explain what Linked Lists are?
- What has been your biggest challenge?
Dev.Pro Interview Questions
Quoted word for word from Dev.Pro interview reports.
“Regarding C#, why is a string a class, but it acts like a value type?”
Read reports →“Is it considered a microservice if two microservices consume the same database?”
Read reports →“What's the distinction between using a List and an IEnumerable?”
Read reports →“What HTML method request is used to create a new entity?”
Read reports →“When is it appropriate to use a List, and when an IEnumerable?”
Read report →“What are the API response codes?”
Read report →“How would a user go about generating a 404 error?”
Read report →“Could you explain the difference between latency and response time?”
Read report →“Can you tell me the difference between 400 and 500 errors?”
Read report →Formats, difficulty and experience
Across all 36 Dev.Pro interview reports.