ProcDNA logo

ProcDNA Software Engineer Interview Questions
& Process

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

Based on 11 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
81.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at ProcDNA.

Showing 3 of 11
ProcDNA logo
ProcDNA

Programmer Analyst

Engineering · nearly a year ago

Entry Average Positive experience Accept offer 2 rounds
Interview process
Technical screen Recruiter call Background check Offer
Interview formats
Technical Coding Behavioral Case Presentation

So there were 2 rounds. The first was a technical round where I got some SQL queries (basic and medium) and some basic Python questions. The interviewer also looked at my resume and projects, asking for detailed explanations about their tech stack, implementation, and architecture. This round lasted about 30-40 minutes. After that, I had an HR round. In this round, they were mainly checking my critical thinking and how I approach problems. They asked me one puzzle, which I eventually solved, but it took me a bit. They also asked about my future aspirations and dream company. This round was about half an hour.

Confirmed questions3 questions
  • They really focused on the technical aspects of SQL and Python programming.
  • They also assessed critical thinking and problem-solving skills.
  • Regarding soft skills, they evaluated my communication abilities and how I would handle clients in the future.
ProcDNA logo
ProcDNA

Software Developer Intern

Engineering

Intern Average Positive experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Coding

So the interview was pretty much a mix of like, technical stuff and just, you know, testing if I get the concepts. They hit me with a bunch of SQL questions, and some of them were pretty tricky, like really digging into how databases work and how to write queries. Plus, they wanted to see if I knew my OOP stuff, like inheritance, polymorphism, and abstraction. Basically, they wanted to see if I could code and if I actually understood the underlying principles.

Confirmed questions1 question
  • Can you solve the LeetCode Two Sum problem and answer some SQL questions?
ProcDNA logo
ProcDNA

Software Developer

Engineering

Entry Average Neutral experience No offer 3 rounds
Interview process
Group Take home Technical screen
Interview formats
Group Case Behavioral

They mainly conducted a group discussion (GD), then a case study, followed by an interview. The GD was pretty easy. The case study was confusing for me and I got eliminated in that round. For the GD, you can expect questions from your resume.

Confirmed questions1 question
  • Tell me about a project you've worked on.

ProcDNA Software Engineer Interview Questions

Quoted word for word from ProcDNA interview reports.

Can you solve the LeetCode Two Sum problem and answer some SQL questions?

Read reports

Can you give an overall description of your experience?

Read report

Formats, difficulty and experience

Across all 11 ProcDNA interview reports.

Interview formats

Behavioral 27.3%
Technical 24.2%
Coding 18.2%
Case 15.2%
Presentation 6.1%

Interview difficulty

Easy 9.1%
Average 81.8%
Difficult 9.1%

Candidate experience

Positive 81.8%
Neutral 9.1%
Negative 9.1%