Yokogawa logo

Yokogawa Software Engineer Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Yokogawa.

Showing 3 of 12
Yokogawa logo
Yokogawa

Software Engineer

Engineering

Intern Average Negative experience No offer 3 rounds
Interview process
Technical screen Recruiter call Background check Offer
Interview formats
Coding Technical Behavioral

The process began with an online aptitude and coding round on Hackerrarth, featuring two coding questions. If you passed that test, you were then invited for interviews. Typically, there were two interviews: one technical and one HR. Interestingly, the technical interviewer seemed unfamiliar with Data Structure and Algorithm concepts like Hash maps, Heaps, or Hash tables, as they didn't grasp my DSA-based coding solution. A peculiar question asked was to retrieve table data from a database without using SQL queries.

Confirmed questions5 questions
  • Tell me about your resume and explain all oops concepts in one program?
  • Do you know DBMS questions?
  • Can you make two teams from the given array of ages?
Yokogawa logo
Yokogawa

Software Engineer

Engineering

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

I went for the interview as a fresh graduate. For me, there were a total of 2 interviews. The first was a technical interview, as the company developed software mainly in C# or C++, the programming questions were asked to answer either in one of the languages or if you know both, you can write in both languages. The programming questions were to test the understanding of Object Oriented Concept and certain programming proficiency. For me, I was tasked to write a class to implement a real-world object and its associated behaviors. (Heard from my colleague who entered later than me say the programming questions are now done on laptop, previously we had to write it on paper). After completion of the programming questions, an architect will be present to review the codes and ask questions pertaining to what you have written. If you are applying for Senior Software Developer, I think you are required to model the problem with UML diagram as well. The second interview was done with a HR and 1 management to know more about you and see how you can fit into the company. They will ask you how much you know about the company and what it does (Industry Automation) and at the same time, explain the culture of the company and also the job description. This is also the time where you can ask them about the company as well.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Yokogawa logo
Yokogawa

Software Engineer

Engineering

Mid Average Neutral experience Accept offer 2 rounds
Interview process
Recruiter call Background check
Interview formats
Behavioral Technical

The first interview was an HR phone screening and then a Hiring Manager interview. The Hiring Manager asked behavioral questions, technical questions, and assessed my skills and abilities. Most of the questions were related to object-oriented programming. After that, the company conducted reference checks and/or background checks to verify my employment history, education, criminal record, etc.

Confirmed questions1 question
  • What is the difference between an abstract class and an interface?

Yokogawa Software Engineer Interview Questions

Quoted word for word from Yokogawa interview reports.

What is the difference between an abstract class and an interface?

Read reports

How would you bring the content of a table in the database without using any SQL queries?

Read reports

What did you find out about our company from its website?

Read report

Tell me about your resume and explain all oops concepts in one program?

Read report

Formats, difficulty and experience

Across all 12 Yokogawa interview reports.

Interview formats

Behavioral 40.7%
Technical 37%
Coding 18.5%
System Design 3.7%

Interview difficulty

Easy 25%
Average 66.7%
Difficult 8.3%

Candidate experience

Neutral 33.3%
Negative 16.7%
Positive 50%