I applied through a recruiter. I interviewed at Elsevier (New York, NY) in July 2017
Interview
Recruiter wanted to setup an onsite meeting without gathering basic facts like salary expectation, role and culture fit. Found out they pay way less than market rate and tried to talk me to take a pay cut. I am glad I found out early in the process, so I did not have to invest anymore time. Train your recruiter to be pleasant, forthcoming and honest about what your company can and cannot offer to potential employees.
I applied through a recruiter. I interviewed at Elsevier (Bangalore Rural) in June 2021
Interview
I have given interview as Python Automation Tester and the Interview consist of 4 parts :
1. Technical Interview - 4 Technical members joined over Skype Video conference
2. Technical Interview - 3 Technical memebrs joined over skype Video conference
3. SHL Exam
4. Thomas PPA Exam
Interviewer were super understanding and discussion over Technical aspects will be based on Present and Previous experience.
Interview questions [2]
Question 1
Explain different between generators and iterators and how do you implement generators in your current automation framework.
1. Perform sorting without using inbuit function of a list and find second highest
2. Identify the numeric values in a string
3. Convert the Capital letters in a statement without using inbuit function.
I applied through a recruiter. The process took 6 days. I interviewed at Elsevier in Apr 2016
Interview
A recruiter sent my resume in and a couple days later I had a phone interview setup. Phone interview consisted of 3 people, a project manager and 2 devs. During the interview went over some basic stuff like the job description. Not much asked about my background with the exception about agile environments and if I have worked in them.
Turn offs:
- They have leads/managers working on the agile team as a core contributor while managing. Managing your team mates goes against agile. So while they may claim to be agile please be aware they are not
- Their code review process sounds weak and only consists of a buddy test
- I didn't hear them mention testing (unit, integration, functional)
Interview questions [1]
Question 1
How do you talk to the back-end from the front-end?