
Digit Fullstack Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Digit.
Full Stack Engineer
The interview process involved an initial call with the CTO, followed by a technical screen, and then an on-site interview. I found the on-site structure to be misleading based on the email received. Expect white-boarding questions, with each interviewer asking at least two questions: one algorithm and one main problem. The questions were focused on product-related fin-tech, leaning more towards backend than full-stack. A significant challenge was working with their data set and solving problems with limited context. The order of asking algorithm questions before the main problem felt inefficient.
- Could you build a website that changes color to red or blue upon the user's first visit and maintains that color?
- How would you approach a recursive algorithm problem to flatten an array?
- Can you design a system for scaling to a large number of users?
Full Stack Engineer
The technical phone interview involved implementing an app. I fully met all requirements and successfully completed four test cases. However, during the fifth test case, the interviewer stopped me a few minutes early. They said I failed due to insufficient experience with the chosen testing library, as I was taking too long on the last test case.
- Could you write code for a web app that randomly sets the background color to either red or blue upon the first visit, and ensures the background color remains consistent on subsequent page loads?
- Additionally, please write tests to verify that the app functions correctly.
Full Stack Web Developer
I had a phone interview, which was pretty standard. Then, there were two pair programming sessions where we had to code and test a web app within an hour. It wasn't super hard, but it took time. Two interviewers watched me code via screen share. I got about halfway through a solution when one interviewer stopped me 45 minutes in. They said my solution didn't scale, missed edge cases, and wasn't what they were looking for. I've done a lot of interviews and I'm a decent web developer, so it felt like a waste of time. Not going to write a lot about the assessment, but there were clear judgmental issues, and my time with Digit wasn't productive.
- Can you build a web app where users see a landing page with either a red or blue background, and this color stays the same on all subsequent visits?
- Please write tests to make sure all the code you've written functions correctly.
Digit Fullstack Engineer Interview Questions
Quoted word for word from Digit interview reports.
“How would you approach a recursive algorithm problem to flatten an array?”
Read reports →“How would you flatten an array?”
Read reports →“Could you build a website that changes color to red or blue upon the user's first visit and maintains that color?”
Read reports →“Can you build a web app where users see a landing page with either a red or blue background, and this color stays the same on all subsequent visits?”
Read reports →“Could you build a page that randomly selects a color and also write tests for it?”
Read report →“Could you write code for a web app that randomly sets the background color to either red or blue upon the first visit, and ensures the background color remains consistent on subsequent page loads?”
Read report →“How would you set up an A/B test for a new layout, allocating 30% of users to one version (a specific HTML page with a certain background color) and 70% to another, and ensure thorough testing?”
Read report →“Can you design a system for scaling to a large number of users?”
Read report →“What are your thoughts on an algorithm question before tackling the main problem?”
Read report →Formats, difficulty and experience
Across all 6 Digit interview reports.