Skip to contentSkip to footer

Senior Backend Engineer Interview Questions

Salaries
Interviews

2,034 senior backend engineer interview questions shared by candidates

They'll create a private repo with a task (just a README, a few dockerfiles, docker-compose.yml, and some .php files inside), share it with you and expect you'd implement it (in PHP, Python, or Go) in no more than 7 days and then open a single Pull Request on Github with all the changes to submit the result. The task is: 1. Implement Recipes API with the specified endpoints (6 in total) for List, Create, Get, Update, Delete, Rate. 1.1 Implement authentication for the Create, Update, and Delete (according to the task, the method is up to you, but at the end you'll learn that not really). 1.2 Implement search functionality. 1.3 Optional requirements (at the end they may be not that optional): implement pagination, content negotiation, add other types of testing (though, nobody cares), have good git history (even though, nobody would read it). 2. Do not use any frameworks or microframeworks. Code generation of any kind is forbidden. 3. Use Postgres, MongoDB, or Redis for data persistence. 4. Overengineer your solution so they can see what you can do (that's just a beautiful lie they copy pasted from somewhere). 5. Make sure your project works with the specified docker-compose or they will ignore your result right away.
avatar

Senior Backend Engineer

Interviewed at HelloFresh

3.3★
Feb 26, 2018

They'll create a private repo with a task (just a README, a few dockerfiles, docker-compose.yml, and some .php files inside), share it with you and expect you'd implement it (in PHP, Python, or Go) in no more than 7 days and then open a single Pull Request on Github with all the changes to submit the result. The task is: 1. Implement Recipes API with the specified endpoints (6 in total) for List, Create, Get, Update, Delete, Rate. 1.1 Implement authentication for the Create, Update, and Delete (according to the task, the method is up to you, but at the end you'll learn that not really). 1.2 Implement search functionality. 1.3 Optional requirements (at the end they may be not that optional): implement pagination, content negotiation, add other types of testing (though, nobody cares), have good git history (even though, nobody would read it). 2. Do not use any frameworks or microframeworks. Code generation of any kind is forbidden. 3. Use Postgres, MongoDB, or Redis for data persistence. 4. Overengineer your solution so they can see what you can do (that's just a beautiful lie they copy pasted from somewhere). 5. Make sure your project works with the specified docker-compose or they will ignore your result right away.

1. Initial call 2. 3 to 4hr long take home 3. 45min review call with CTO 4. 2hr long culture fit (? I didn't get to this stage). The take home is to build a concurrent FastAPI app, which integrates with 2 clients. They're looking for concurrency.
avatar

Senior Backend Engineer

Interviewed at Photoroom

4.6★
Mar 28, 2025

1. Initial call 2. 3 to 4hr long take home 3. 45min review call with CTO 4. 2hr long culture fit (? I didn't get to this stage). The take home is to build a concurrent FastAPI app, which integrates with 2 clients. They're looking for concurrency.

Viewing 2001 - 2010 interview questions

Glassdoor has 2,034 interview questions and reports from Senior backend engineer interviews. Prepare for your interview. Get hired. Love your job.