Joveo Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Joveo.
Joveo
Software Engineer Intern
Intern Average Positive experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Coding
Overall process is simple and fine, the interviewer is so nice and well talented and also overall process is so well and its online.
Confirmed questions1 question
- The interviewer asked me a medium-difficulty dynamic programming question.
Joveo
Software Engineer
Mid Average Negative experience No offer 3 rounds
Interview process
Technical screen Take home Technical screen
Interview formats
Technical Coding
The interview process was strange because there was only one person conducting all rounds. The first round involved a medium difficulty problem that needed to be solved in 20 minutes. The second round was a HackerEarth assessment with 5 programming questions to be completed in 90 minutes. The problem descriptions were extremely long and confusing, and matching the output with numerous system outputs and strings was required. I passed this round, but I couldn't run test cases for individual questions, suggesting poor question setup. The third round consisted of 2 hours of programming questions, focusing on scenarios. I finished 2 questions in 1 hour and 45 minutes, but the VP ended it early due to perceived time constraints. The first question was complex, involving external sorting on tapes, but I handled it well. The second question was about Python indentation, which I found tricky as I don't use Python, and the VP expected it to be solved in 20 minutes, asking basic questions without understanding the logic. There were 8 long questions focused on data structures and algorithms. The interviewers lacked basic courtesy, not even replying after the interviews. I strongly advise against this company; they act like Google but waste your time with numerous questions and don't even have the decency to send a rejection email to a qualified candidate. Not recommended.
Confirmed questions6 questions
- I was asked a medium problem in 20 minutes.
- There were 5 programming questions in 90 minutes on HackerEarth with confusing descriptions and strict output matching.
- I was asked scenario based questions.
Joveo
Software Engineer
Senior Difficult Neutral experience No offer 3 rounds
Interview process
Technical screen Onsite Recruiter call
Interview formats
Coding System Design
There was this HackerRank test first, lasted 90 mins, with 4 questions, two of which were pretty tough. Honestly felt like too many questions for the time given. After that, there were two more rounds. Mostly system design questions came up. The HR called me after those two rounds, saying there'd be one more round on DS and Algo. But that never happened. When I followed up, they said it was postponed and then I never heard back from them. The interviewers were cool, though. The HR could've been more professional with scheduling and letting me know the outcome.
Confirmed questions2 questions
- Can you describe a project you've worked on?
- What architectural choices and design patterns did you employ in that project?
Joveo Software Engineer Interview Questions
Quoted word for word from Joveo interview reports.
“Implement GET /job/<id> for the JOB API. If the job ID is recognized, respond with status 200 and the job's ID and status. If the ID is unknown, respond with status 404.”
Read reports →“Implement DELETE /job/<id> for the JOB API. Respond with status 200 if the ID is known and the job isn't in a terminal state (except DELETED). Specifically, if the job is DELETED, return its ID and DELETED status. If it's RUNNING, pause it, mark as DELETED, and return ID/DELETED. If PAUSED, mark as DELETED and return ID/DELETED. If QUEUED, remove it and return ID/DELETED. For SUCCESSFUL/FAILED states, return 403, and for unknown IDs, return 404.”
Read reports →“Implement POST /job/<id>/<resume> for the JOB API. Respond with status 200 if the job ID is valid and the job isn't in a terminal state. If the job is RUNNING, return ID/RUNNING. If it's PAUSED, resume it and return ID/RUNNING. For QUEUED/SUCCESSFUL/FAILED/DELETED states, return 403, and for unknown IDs, return 404.”
Read reports →“What is the git diff between two strings?”
Read reports →“Given an array, find two elements that sum up to a specific value.”
Read report →“What is the Edit Distance problem?”
Read report →“How would you transmit a Binary tree via HTTP?”
Read report →“Can you implement merge sort?”
Read report →“Could you implement the HTTP protocol with specific methods (GET, PUT, POST, DELETE) and URL parsing using a TCP network library? Your implementation should handle request bodies for POST/PUT and return specific status codes (200, 404, 500, 403) with a string payload, without using any existing HTTP server libraries.”
Read report →Formats, difficulty and experience
Across all 13 Joveo interview reports.