
January Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at January.
Software Engineer
The interview process was quite unconventional and showed a unique approach. The recruiter wasn't very clear about what to expect. Some interviewers were professional and knew their stuff, but others were unfocused and kept cutting out due to bad audio. One interviewer seemed unprepared for the scale challenge. When I asked for more details on different use cases, they didn't really get it and couldn't provide specifics, only mentioning GET and POST APIs. While I was explaining my solutions, they got distracted, did something else, and then asked me to repeat myself because they hadn't heard. The whole experience felt disrespectful and like a waste of time.
- Discussed cultural fit.
- Presented a scale challenge.
- Coding exercise.
Software Engineer
Did OA first. Passed that and moved to onsite interviews. One hour coding interview, solved a Leetcode question in 20 mins. Then a 1-hour relational DB design question, where I had to set up tables and API routes for a food app similar to Uber Eats. After that, there were 2 hours of culture and behavioral rounds.
- Can you design Uber Eats, specifically focusing on the database tables?
- Could you tackle a relational database design problem?
- How would you set up tables and API routes for a food delivery app like Uber Eats?
Software Engineer
The interview process started with a recruiter phone screen and then a code exercise with members on the engineering team. I really liked the interview process because everyone I talked to was professional and helpful in helping me learn more about the organization. The employees I spoke with were very communicative and kind. One thing I thought could be better is that I thought I was interviewing for a general full-stack role based on the job description, but the rejection email said I was interviewing for a position on the platform team. This was a surprise and wasn't mentioned during the process. The platform team is a specific placement for ICs, and this should have been communicated in the first conversation.
- Can you create a function and some variations for a board game?
January Software Engineer Interview Questions
Quoted word for word from January interview reports.
“Can you implement a function to check if a piece on a board can be moved to a new location?”
Read reports →“How would you implement a move function for a piece that can move diagonally any number of steps, but cannot move past another piece?”
Read reports →“How would you implement a move function for a piece that can move two steps in any direction, but must move over another piece?”
Read reports →“How would you implement a move function for a piece that can move one step in any direction (up, down, left, right, diagonal)?”
Read reports →“Can you implement three different types of pieces for a board game framework?”
Read report →“Design the data model for online order and customizations of coffee.”
Read report →“How would you calculate an invoice?”
Read report →“Can you create a function and some variations for a board game?”
Read report →“Could you design a chess or checkers game using basic object-oriented programming concepts?”
Read report →Formats, difficulty and experience
Across all 12 January interview reports.