Wrapbook logo

Wrapbook Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 36 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
91.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Wrapbook.

Showing 3 of 36
Wrapbook logo
Wrapbook

Software Engineer

Engineering · a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical

It started with a short screening call, then a nontechnical interview about work experience with two people. After that, there was a technical interview with two people, and finally an exec interview about high-level career goals and experience with two people. Everyone was super nice and professional, but also made it feel comfortable. They really seemed to care about the hiring process and did it thoughtfully. They had standard questions they'd ask but would follow up. They didn't waste time on irrelevant stuff. They mentioned they review notes individually before meeting to discuss, to avoid bias. The questions felt pretty reasonable and well-thought-out. In a few interviews, they'd rephrase what they heard, like 'So, what I'm hearing is x, y, and z. Does that sound right?' This summary step was great because it showed they were processing my answers, gave me a heads-up on what they were noting, and let me correct any misunderstandings. I really liked that. The technical interview was actually related to the job, which is awesome. It was pretty chill and casual, with lots of chances to chat, ask questions, or even Google stuff. I can't really say how hard it was because that depends on your level and I'm not sure how I did, or how much it varies based on your specific strengths.

Confirmed questions3 questions
  • Can you share some examples of different work experiences, like how you handled challenges (technical or people-related) or a project you're proud of?
  • Tell me about a project that you're proud of.
  • Can you give an example of dealing with different challenges, whether technical or more people-based?
Wrapbook logo
Wrapbook

Software Engineer

Engineering

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel Offer
Interview formats
Behavioral Technical Presentation

So the interview process was pretty standard. I met with a bunch of team members, different experience levels, to just get a feel for culture and if we'd vibe, you know? Then there was this technical thing, done in person with the engineering leads. They also chatted with management to get a sense of my career goals and how I could grow here at Wrapbook. For mid-level engineering, they really wanted to figure out the best spot for me to add value, both in terms of level and team. They gave me a good amount of time to ask my own questions too, about Wrapbook, the job, and just to get to know the people interviewing, who were from different teams and had varying levels of experience.

Confirmed questions3 questions
  • Are you looking to grow as an individual contributor or move into people management?
  • What are your career aspirations and growth expectations?
  • How do you see your career path fitting in with Wrapbook's structure?
Wrapbook logo
Wrapbook

Software Engineer

Engineering

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Background check Offer
Interview formats
Behavioral Technical

I went through the entire interview process which lasted for weeks. After all the interviews, I was asked to provide three references, which I did. I also had a good conversation with the person I would be reporting to. I was really looking forward to joining Wrapbook. However, they unexpectedly rejected my application the next day with a standard email saying they weren't moving forward with my application. It's strange because the position is still open even after a month, making me wonder about the purpose of opening these roles and if I was just part of some quota.

Confirmed questions2 questions
  • Behavioral questions were asked.
  • A technical interview focused on a Rails app and common tasks was conducted.

Wrapbook Software Engineer Interview Questions

Quoted word for word from Wrapbook interview reports.

Could you explain what a database is in simple terms, like for a child of 8?

Read reports

Could you explain the concept of databases in a way that a child could understand?

Read reports

How would you go about renaming a database column in a way that's safe for production?

Read reports

Build a mini Rails app for managing related entities, a semi-interactive test.

Read reports

How can we promote equity in STEM for women, minorities, and marginalized groups?

Read report

Given some code, how would you approach fixing a bug within it?

Read report

What are your thoughts on the underrepresentation of women in programming?

Read report

What are your thoughts on why women and minorities are not as common in tech?

Read report

What suggestions do you have for enhancing diversity within the Software Engineering field?

Read report

Formats, difficulty and experience

Across all 36 Wrapbook interview reports.

Interview formats

Behavioral 37.9%
Technical 33.7%
Coding 20%
Presentation 5.3%
System Design 3.2%

Interview difficulty

Easy 5.6%
Average 83.3%
Difficult 11.1%

Candidate experience

Positive 91.7%
Negative 5.6%
Neutral 2.8%