
Yokogawa Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 115 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 115 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Yokogawa.
Sales Engineer
I interviewed for a sales engineer position. The direct supervisor was young and the position involved working closely with just that one person. He seemed very egotistical and proud. Feel like I dodged a bullet by declining the 2nd interview. Wouldn't have been a good fit. My request for salary clarification was ignored, at the time I already had another offer, so before accepting I wanted to know the salary Yokogawa offered, but they didn't want to disclose. This isn't a good practice when you are already offering someone a follow up interview and you know they have another offer.
- Can you tell me about your experience in a similar role?
Data Analyst
The process had 3 stages. First, we talked about whether you're a good fit, your interest, mindset, qualifications, attitude, and communication style. Then, we went over the role details, checking your skills, alignment, strengths, motivation, and potential. Lastly, HR talked about culture, salary, your readiness, and made the final decision, extending an offer.
- Can you describe your experience with projects in this domain?
Graduate Engineer Trainee
It was a pool campus drive. The process included an online test followed by an in-person interview. There were 2 rounds in total, including an HR interview. The interview questions focused on computer networks, projects, and resume details. No coding questions were asked. The interview process was considered easy, but the results were announced late.
- Can you explain the difference between IPv4 and IPv6?
Technology Manager
It was a good experience where it started with asking my education and background and working experience. HR/hiring manager didn't give much intro about Yokogawa or the job scope. When I asked deeper questions about what they are looking for, they seemed unsure and mentioned they have many different openings. At the end, I was asked if I would consider a contract position. I think permanent and contract positions are different and should be stated upfront. The next day, the headhunter said they invited me back for a technical interview. I reflected on my concerns about contract positions and would like to reject if it's not permanent, but they said they have open options. I attended the second interview with two technical hiring managers. I thought it was for Technology Manager, but again after an hour, they told me they were hiring for Data Scientist. I was shocked because what I presented wasn't for a Data Scientist. Apparently, the hiring managers, HR, and headhunter were not aligned. It seemed quite messy internally. Thanks for the learning experience about Yokogawa.
- Would you consider a contract role?
Yokogawa Interview Questions
Quoted word for word from Yokogawa interview reports.
“What is the difference between an abstract class and an interface?”
Read reports →“What is the reason for using a 4-20 mA range over a 0-max range?”
Read reports →“Can you explain the difference between IPv4 and IPv6?”
Read reports →“What's the difference between a DTS and an ETS system?”
Read reports →“What is the BMS sequence, and what can cause a BURNER shutdown?”
Read report →“Can you explain the difference between 4-wire and 2-wire sensor types?”
Read report →“Can you explain what a barrier is and how it differs from an isolator?”
Read report →“Can you define what a set point is and explain if it's possible to have multiple set points?”
Read report →“Can you make two teams from the given array of ages?”
Read report →Formats, difficulty and experience
Across all 115 Yokogawa interview reports.