Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Instructure (Salt Lake City, UT) en may 2016
Entrevista
I applied online and within a day got an email from a recruiter. The first call was a quick 20 minute conversation with a recruiter to discuss my experience and describe the role. We also discussed salary requirements, benefits, etc. I really appreciated the openness early in the conversation.
Next, the recruiter scheduled a 1-hour video interview with Senior / Lead engineers. This was a tough interview where you had to identify an algorithm for looking through a binary tree and determine the path with the largest sum. You have to understand Depth-First Search to figure this one out. You then have to code the answer in a shared online editor (collabedit.com)
A day later, I got an email from the recruiter letting me know that I did well on the video interview, and was given a coding exercise to complete: write a library (in any language) for importing student and course information from a CSV, handling cases where the CSV headers were malformed. I ended up writing a full web-app that used the library and wrote unit tests and integration tests for both the library and web app. The exercise took a few hours to complete - about 4 hours in total.
The next step was a series of in-person interviews with SET Leads, Test Manager and SVP of Engineering. I flew in to Salt Lake City and had a full day of interviews (including lunch with the team). Their recruiting coordinator setup all the flight details. The main office is located about 20 minutes from Salt Lake City Airport.
The interviews were technical requiring you to write code on whiteboard. Overall, the questions were moderately difficult - requiring you to understand data structures and algorithms.
Preguntas de entrevista [5]
Pregunta 1
How would you test a black box system that takes an apple as it's input and outputs an orange?
Given an array of numbers 1 to n, stored in an array of length n-1, where all numbers are unique, write a function that to determine which number is missing.
El proceso tomó más de 1 semana. Acudí a una entrevista en Instructure (Salt Lake City, UT)
Entrevista
Recruiter is super friendly and screens you. Next is hackerrank test and problem. Not to difficult. Then you meet with a Techincal interviewer when really they say your meeting with the hiring manager. The interviewer is cold, rude, and even swears at you. I did a brute force 0(n2) approach and was mocked. This interview was the worst i have ever experienced. Stay far away from instructure.
Me postulé en línea. El proceso tomó 2 días. Acudí a una entrevista en Instructure (Salt Lake City, UT) en abr 2018
Entrevista
I had a phone interview with Jared Salisbury and was asked to complete a coding assessment. After accusing me of plagiarism on one of the answers, Jared then informed me another recruiter had already filled the position I was applying for.
Preguntas de entrevista [1]
Pregunta 1
Did you look up the answer for your assessment question online, or were you already familiar with the problem?
Me postulé a través de una recomendación de un empleado. El proceso tomó más de 1 semana. Acudí a una entrevista en Instructure (Salt Lake City, UT) en feb 2018
Entrevista
I was contacted through e-mail and given a link to take a HackerRank test that involved 15 questions and three programming challenges. I was given 90 minutes to complete. Even though my solutions failed most of the tests, I submitted my code and passed the online portion. The challenges were difficult, but inline with what I understand to be part of a Software Engineer in Test position. This would be out of scope for a QA engineer position.
The next day I had a video interview with a team lead that lasted 30 minutes.
Two days later I had an onsite interview. I met with QA team leads, who each gave me a whiteboard coding challenge and followed up with questions on how I would test the function I had just written. Then I met with the product owner who asked similar question, in a more practical format.
I was told I would receive an answer the next day, but this was a holiday weekend and the response was delayed until the next week.
