
IHS Markit Qa Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 20 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at IHS Markit.
Quality Assurance Engineer
I applied online for a Senior Quality Assurance Engineer position and got a call from HR the next morning to schedule on-site interviews. I was concerned about the salary so I emailed HR about the pay range, but she said they usually don't discuss comp until after the first interview. She made a scheduling mistake and then corrected it. I went for the on-site interview with the QA Director, but HR didn't show up. HR then scheduled a second and third on-site interview with two QA Leads. After those interviews, one of the QA Leads was surprised I hadn't met with HR and mentioned there was 'a lot of churn' in HR. The next day, HR called to discuss salary for a job offer and asked my target salary. She said she'd call back after a 'salary committee' meeting but didn't. I called her, left a message, and called again. She finally answered and icily said they decided to move forward with another candidate after hearing my target salary, rescinding the job offer. I questioned why she refused to discuss salary earlier, but she denied everything and claimed she misspoke.
- What salary are you targeting?
SQA Engineer
The interview process started with a Pymetrics assessment for behavioral analysis. Then, there was an HR phone screen, followed by a 45-minute interview with the hiring manager. After that, a 45-minute team fit verification with the team, and finally, a 30-minute technical round. The people in the interviews were nice and the discussions felt informal. A downside was the pay discussion, as the salary range in the job description was unclear. My expected salary was mentioned as higher than their budget during the HR screen, but I was still asked to interview and discuss it with the hiring manager, who seemed unaware of why HR directed me to him. The HR later contacted me again and confirmed my expected salary, acknowledging the budget constraints. Despite knowing my pay expectations didn't align with their budget, they proceeded with the interviews. The candidate felt IHS Markit could be more transparent about salary ranges to save everyone time.
- When writing Protractor test cases, how would you implement Explicit Waits?
SQA Engineer
The interview process involved three rounds. The first was a technical interview with a Senior SQL engineer. The second round was technical and managerial, conducted by the Director of Technology. The third round was technical, led by the Test Lead. After these rounds, I received an email from HR requesting necessary documents, and a few days later, they extended an offer.
- Could you discuss your experience with Selenium and Protractor?
- Can you demonstrate your basic programming skills and a Selenium demo?
- Tell me about scenarios based on your past experience.
IHS Markit Qa Engineer Interview Questions
Quoted word for word from IHS Markit interview reports.
“There are 30 peoples in the party. If everyone is to shake hands with one another, how many handshakes are possible?”
Read reports →“Difference between Ref and Out in C#.”
Read reports →“A box contains 12 marbles of three different colors green, yellow and blue-4 each, If you were to close your eyes and pick them at random, how many marbles must you take out to be sure that there are at least two of one colour among the marbles picked out?”
Read reports →“Reverse Each word in string "Protractor Automation Testing" and find complexity.”
Read reports →“Can you explain what the 'final' keyword is?”
Read report →“Write code on Rest Sharp / Or Rest Assured on Post Request on below Urls a. Url: https://reqres/api/course b. Post { "id" : "123", "Name" : "Protractor" }”
Read report →“Can you explain the difference between GROUP BY and HAVING, and how to copy one table to another?”
Read report →“Describe what should be included in a test plan.”
Read report →“When writing Protractor test cases, how would you implement Explicit Waits?”
Read report →Formats, difficulty and experience
Across all 20 IHS Markit interview reports.