Me postulé a través de una agencia de empleos. El proceso tomó 3 semanas. Acudí a una entrevista en Shippo en sep 2021
Entrevista
It was the worst interview I've already made.
The interviews looked to not be very prepared to apply it. They made a lot of strange questions, and the feedback they gave it was I'm middle level. I'm right about my seniority, but I learned plenty of things doing this interview. For example, the whiteboard, isn't a whiteboard, talking about technology or other things, it's a tech "challenge" to reorder some data in 3 CSVs files.
All tech interviews looked unhappy doing this job, so I started to think about the position.
A piece of advice, don't apply to a tech position. You'll lose your time too.
Preguntas de entrevista [1]
Pregunta 1
First, it was to order some data and about data structure
Second, it was with a guy a little weird and looked unprepared, but it was about how to handle many requests at the same time in an API
Third, it was the worst, the guys gave some CSV's to parse and make some process. But the guy didn't seem to be interested in the interview. He was doing another task during this time.
Fourth it was about database structure. This guy was great... Maybe the only interview that makes sense.
There were more two interviews, one about culture, other with the manager.
Me postulé a través de una recomendación de un empleado. El proceso tomó 1 semana. Acudí a una entrevista en Shippo (Oklahoma City, OK) en ene 2022
Entrevista
Phone Screen followed by online tech assessment. I was unable to make it past this part but the next step is a virtual onsite and then after that it is an offer.
Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en Shippo en sep 2021
Entrevista
I was emailed by their senior technical recruiter for an introductory call to fill a senior software engineer role. I then scheduled the initial technical round.
1st technical round:
I met with a senior software engineer and was given a fairly simple coding problem to implement. He then followed up with system design questions that were fairly straightforward for an engineer with a few years of experience.
virtual onsite:
A 4 hour virtual onsite interview was then scheduled. -1st interviewer was a senior engineer who tested my knowledge of system design. This was the most in depth of all the other technical rounds.
- 2nd interview was a basic react coding test. Nothing too difficult, just to make an API request and display the info on the page.
- 3rd interview was another system design problem. This focused more on database knowledge and how to structure tables relating to a situation.
- 4th interview was with a product manager to determine day-to-day team preferences and behaviors. Some situational questions were thrown in.
-5th interview was with an engineering manager to discuss culture fit. This was a fairly casual conversation and moment to ask questions about the company.
- finished with a summary conversation with the recruiter
Post virtual onsite:
Was informed that I would be a better fit for another team. What I wasn't told was this was going to be a down-level to a software engineer II position.
Final interview with another engineering manager:
A casual conversation about team culture, a couple situational questions about handling conflict and adversity, then some moments to ask questions about the team.
Reference check - required to give 3 references with one being a manager.
Offer conversation - had to give a verbal YES to see an actual letter. I wasn't completely informed on the details, particularly the stock options portion. I gave them an initial yes to see a letter but I didn't feel the stock options were worth it because the base pay was lower than my requirement. In the end, it would have been a lateral movement from a team I enjoy. Attempted to negotiate a bit higher on the base pay but was denied.
Preguntas de entrevista [1]
Pregunta 1
Anagrams, system design, api design, database design