J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 1 semaine. J'ai passé un entretien chez Pattern (Provo, UT) en sept. 2021
Entretien
I found Pattern at a BYU career fair, and scheduled an in-person interview for the following day. Everyone I interacted with was very nice and friendly. The interview itself wasn't very long, maybe 15 minutes. I was given a very simple coding challenge which I didn't complete because of how easy it was (FizzBuzz). The interviewer was ok with that, and instead asked me a few technical questions.
We appreciate the feedback! We would like to know what we can do to improve our interview process. Will you please send specific feedback to carly.selander@pattern.com since Glassdoor doesn't allow you to respond here? That way we can help others have positive experiences in the future. We're excited to have you at Pattern!
Autres retours d’entretien d’embauche pour un poste comme Software Engineer(Internship) chez Pattern
They took my interview on-campus and asked mostly about backend development. Networking theory, APIs, etc. Also they asked about SQL and OOP basic concepts. The interviewer was friendly. I didn't get selected but it was a good experience.
met at the career fair, then an in-person technical interview, with questions about your previous projects, writing a recursive function, and optimizing SQL calls. The interviewer is really nice and patient.
Questions d'entretien [3]
Question 1
What are some previous projects you have worked on?
J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Pattern (Provo, UT) en oct. 2024
Entretien
It was a quick, thirty minute interview. It was a combination of behavioral and technical questions. It was professional, but I also felt welcomed by the interviewer. The technical questions related to recursion as well as databases.
Questions d'entretien [3]
Question 1
What experience at your last work place are you most proud of?
If the data was in a database, how would you do it more efficiently to not have to create a call to the database every time you want to get a child's value?
