
Peek Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 131 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 131 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Peek.
Strategy & Business Operations
There were two interviews. The first was with the recruiter where they asked standard questions like why I was interested in the company, my salary expectations, etc. The second interview was with the hiring manager, and it was a deeper dive into situational questions related to the job responsibilities. The people were nice, but unfortunately, I was ghosted afterwards.
- What are your salary expectations?
Software Engineer
First, a recruiter calls you. Then, you'll interview with an engineering lead. This is more of a personal/behavioral interview, but they'll ask about projects you've worked on, things you've done that you're proud of, and how you handle criticism about your work. Next, there's about a 4-hour practical take-home coding assessment. It's not tricky algorithm stuff, just implement some business logic and consider production impact. They'll review your assessment, usually within about 2 days. After that, you'll interview with engineers to go over your assessment, explain your logic, and they'll ask about your thought process. They'll also present situations and ask how you'd accommodate those in your code. Finally, you'll interview with the director of engineering. It's very similar to the interview with the engineering lead, covering your background, what you're looking for career-wise, challenges you've faced, mistakes you've made and learned from, and other similar topics. They're really looking for cultural fits and care a lot about maintaining their culture. Everyone there loves their coworkers and the management-fostered environment. They encourage professional growth, cross-pollination, and knowledge sharing. If you're passionate about this and can show it, you'll do well. Be sure to have good questions prepared to ask them.
- Can you share an example of a project you're proud of?
- Describe a mistake you made and how you dealt with it.
- Tell me about your past projects.
Front End Engineer
The interview process had 3 rounds, followed by a coding challenge and references. First, a recruiter screening to discuss salary expectations and role fit. Then, an interview with the engineering hiring manager to discuss the role and my resume. After that, I had a take-home coding challenge to build a booking app with CRUD features (create and read for this junior role). The challenge was front-end specific and requirements varied by level. The readme had good info and the hiring manager answered questions quickly. The third round was a code review of my submission with two senior devs, which was a good way to meet potential teammates and understand the company's engineers. They were friendly and provided great feedback. Finally, I submitted 3 references (1 coworker, 2 past managers). The whole process was about 3 weeks and I had a good experience.
- Could you walk me through your code and explain it?
- Can you explain your code in detail.
Onboarding Specialist
The interview process was amazing! It spanned for a period of 3 weeks with a total of 4 interviews. The first interview was an introduction with the recruiter, seeing if I matched the qualifications for the position. Second interview was with who will be my immediate manager where they asked questions about my experience and some behavioral questions as well. The third interview was with the department manager, they mainly asked questions about how I handle certain situations and what my preferred supervision style was. The last interview was a presentation to 2 people who would be my coworkers, I had to teach them how to use a website/product of my choosing. After that last interview, in about a week I got asked to email them references and then a week and a half later I received an offer. Although I wished it would’ve been a bit quicker, I do think they took the necessary steps to ensure the right person was chosen for the role, which made me happy and it increased my trust in the company.
- What kind of supervision style do you prefer from your manager?
- How do you deal with a situation where everyone is picking up a new skill except for one individual?
Peek Interview Questions
Quoted word for word from Peek interview reports.
“Can you explain the distinction between 400 and 500 HTTP status codes, and what's the purpose of a 304 status code?”
Read reports →“Could you build an app using the Twitter API to pull all mentions of Peek?”
Read reports →“Regarding view creation in iOS development, what are the advantages and disadvantages of building them programmatically compared to using storyboards?”
Read reports →“Could you explain the differences between 'weak', 'unowned', and 'strong' references in Swift, and in which situations each would be appropriate?”
Read reports →“Could you tell me about unit testing, and what's the difference between Post and Put requests? Also, what about Put versus Patch?”
Read report →“What are the advantages and disadvantages of the various methods used in the coding challenge submission?”
Read report →“How do you deal with a situation where everyone is picking up a new skill except for one individual?”
Read report →“What's your approach when a customer is disrespecting an employee without reason?”
Read report →“Do you know what Rack is? What about CSRF attacks, and how does caching work?”
Read report →Formats, difficulty and experience
Across all 131 Peek interview reports.