El proceso tomó 4 semanas. Acudí a una entrevista en O'Reilly Auto Parts (New York, NY)
Entrevista
Applied on LinkedIn. Recruiter screen followed where I was given a brief description of the work and gave an overview of my experience. Next was a hackerrank challenge. Very easy.
Finally came the virtual interviews. Three total at an hour each, although I interviewed with two teams. Focus on design philosophies, work experience, and familiarity with the tech stack.
Total process was about a month. Everything was smooth, laid back, and a good experience.
Acudí a una entrevista en O'Reilly Auto Parts (Guadalajara, Jalisco)
Entrevista
Entrevista sencilla, el proceso fue rapido y se tuvo comunicacion todo el tiempo, fue una entrevista tecnica, platicas con los lideres y con recursos humanos. Las prestaciones son competitivas aunque al NO ser una empresa de TI sino de refacciones se maneja otro ambiente.
Me postulé a través de otra fuente. Acudí a una entrevista en O'Reilly Auto Parts en jul 2023
Entrevista
Tried interviewing for Sr. Software Engineer but was told they see a senior role for someone with 10+ years. This is obviously myopic and ageist. So knowledge and expertise is nothing to them. I took the interview anyway to brush up for other interviews in the pipeline.
Preguntas de entrevista [1]
Pregunta 1
usual questions like what does it mean to be a part of the team and so on. tech interview was easy with 2-3 hacker rank questions. they will ask you your current compensation and visa status.
Me postulé en línea. Acudí a una entrevista en O'Reilly Auto Parts en jun 2023
Entrevista
There are 4 rounds - 1. Initial round with recruiter 2. Two online hacker rank assignments 3. 1 technical interview 4. 1 hiring manager interview I made it through 3 but did not hear back from hiring managers for whatever reason.
Preguntas de entrevista [4]
Pregunta 1
easy hackerrank question related to counting vowels
hackerrank question similar to merge intervals on leetcode. this one was a little tricky to complete in 20 minutes but doable if not under interview stress
technical questions on java like virtual vs synchronized. name uses of static. what is a db index when do you use one or when do you not use one etc. review basic sql syntax for ddl and dml. review a pr with their "sr" developer who got angry when I pointed out a basic exception it was throwing that he had missed. Their tech stack looks old-ish, possibly 2015ish with no mention of microservices, event streaming, or even any container management or control plane of any kind so no need to review any of those.