Pramati Technologies logo

Pramati Technologies Principal Software Engineer Interview Questions
& Process

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

Based on 8 interview experiences · FREE TO READ

2.6 Rounds average
Easy Typical difficulty
87.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Pramati Technologies.

Showing 3 of 8
Pramati Technologies logo
Pramati Technologies

Principal Engineer

Engineering · more than a year ago

Staff Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Coding

They had a simple interview and I answered all the questions correctly. However, I received negative feedback via email within 20 minutes. My friend had the same experience. I don't understand why they waste job seekers' time with useless interviews. This job has been open for about 4 months, and I keep getting emails about it.

Confirmed questions1 question
  • Can you write a query to retrieve names that begin with a vowel?
Pramati Technologies logo
Pramati Technologies

Principal Engineer

Engineering · more than a year ago

Staff Easy Positive experience Accept offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical Coding System Design

I had a phone call with the hiring manager first. We talked about my past work, different data warehousing situations I'd dealt with, technologies I've used, and any management tasks I'd handled. Then, they threw a data warehouse design question at me related to a scenario, plus some data engineering challenges within that situation. It was about an hour long, and I got good feedback from HR afterwards. The next day, I had a second round where the interviewer presented a straightforward DW design problem based on a report requirement and asked me to write a SQL query.

Confirmed questions3 questions
  • Can you tell me about the migration of a 100MM USD business's DW from Oracle to RedShift that you worked on?
  • What led to your decision to choose RedShift for this migration?
  • What difficulties did you encounter during the migration process?
Pramati Technologies logo
Pramati Technologies

Principal Engineer

Engineering

Staff Average Positive experience Accept offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical Technical Behavioral

The interview process included two technical rounds and then a discussion with HR. The first technical round was about assessing your practical experience with technologies and concepts. You'll pass if you've actually worked on things and understand the 'how.' The second round was more about how you approach certain tech use-cases. As a full stack JavaScript dev, I could connect it to JavaScript's nature. At times, it felt like a regular discussion where information is shared from both sides. Overall, it was a smooth, quick, and not too stressful process.

Confirmed questions3 questions
  • What is the difference between variable and function hoisting?
  • Can you explain how the context API works in ReactJS?
  • In ReactJS, how does the browser DOM differ from the Virtual DOM, specifically regarding events?

Pramati Technologies Principal Software Engineer Interview Questions

Quoted word for word from Pramati Technologies interview reports.

What is the difference between variable and function hoisting?

Read reports

In ReactJS, how does the browser DOM differ from the Virtual DOM, specifically regarding events?

Read reports

Can you write a query to retrieve names that begin with a vowel?

Read reports

What led to your decision to choose RedShift for this migration?

Read report

Can you describe how you would design an online bookstore?

Read report

Describe your understanding of client and server interactions.

Read report

What difficulties did you encounter during the migration process?

Read report

Formats, difficulty and experience

Across all 8 Pramati Technologies interview reports.

Interview formats

Technical 36.4%
Coding 27.3%
Behavioral 27.3%
System Design 9.1%

Interview difficulty

Easy 37.5%
Average 25%
Difficult 37.5%

Candidate experience

Positive 87.5%
Negative 12.5%