Skip to contentSkip to footer

Senior Backend Engineer Interview Questions

Salaries
Interviews

2,798 senior backend engineer interview questions shared by candidates

Caller Id Service: The goal of this exercise is for you to implement a standalone service that will respond to requests seeking caller id information. Api Requirements/Notes Api should return json Phone numbers should be in E.164 format. Appropriate http codes should be returned on error. API Endpoints GET /query Fetches caller id information. Params: number - the number we want caller id information for. Example query: GET http://localhost/query?number=%2B15556789090 Response: {results: [{ “name”: “Bob Barker”, “number”: “+15556789090”, “context”: “personal”}]} POST /number Adds caller id data to the service. Body: name - contact name number - the number in E.164 format context - the context for the phone number. Note: A phone number may be present multiple times, but can only appear once per context. In other words you can think of a <number,context> pair as unique. Seed Data Normally a service like this would call other services in turn, but to keep things simple we are going to provide seed data for the service as a csv file. Your service will need to read in that initial data and use it to serve requests. Line format: <phone number>,<context>,<caller id> Example: 5556780909,work,John Doe The seed data can be downloaded via this link - https://www.dropbox.com/s/0hmkx242o42g924/interview-callerid-data.csv.gz?dl%3D0&sa=D&ust=1504897125902000&usg=AFQjCNGnxbihbQtE2FV_ZUghuhLkh41Prw Service Requirements We prefer if your service is standalone, this means that it shouldn’t require additional server software (tomcat/apache/etc) to run. If it does require such software you will need to provide setup instructions. The port on which the service listens should be configurable without editing code. Your code should include a README file with instructions on how to run your service. Shell scripts are also appreciated but not required. Misc/Other Notes Once again to keep things simple data submitted to your service does not need to be persisted. While our main goal is to look at your code, we will run your code and test it. There is no timeline, please take as long as you want. However if you take especially long we may check in. If you have any questions please ask.
avatar

Senior Backend Engineer

Interviewed at Truly

4.3★
Sep 8, 2017

Caller Id Service: The goal of this exercise is for you to implement a standalone service that will respond to requests seeking caller id information. Api Requirements/Notes Api should return json Phone numbers should be in E.164 format. Appropriate http codes should be returned on error. API Endpoints GET /query Fetches caller id information. Params: number - the number we want caller id information for. Example query: GET http://localhost/query?number=%2B15556789090 Response: {results: [{ “name”: “Bob Barker”, “number”: “+15556789090”, “context”: “personal”}]} POST /number Adds caller id data to the service. Body: name - contact name number - the number in E.164 format context - the context for the phone number. Note: A phone number may be present multiple times, but can only appear once per context. In other words you can think of a <number,context> pair as unique. Seed Data Normally a service like this would call other services in turn, but to keep things simple we are going to provide seed data for the service as a csv file. Your service will need to read in that initial data and use it to serve requests. Line format: <phone number>,<context>,<caller id> Example: 5556780909,work,John Doe The seed data can be downloaded via this link - https://www.dropbox.com/s/0hmkx242o42g924/interview-callerid-data.csv.gz?dl%3D0&sa=D&ust=1504897125902000&usg=AFQjCNGnxbihbQtE2FV_ZUghuhLkh41Prw Service Requirements We prefer if your service is standalone, this means that it shouldn’t require additional server software (tomcat/apache/etc) to run. If it does require such software you will need to provide setup instructions. The port on which the service listens should be configurable without editing code. Your code should include a README file with instructions on how to run your service. Shell scripts are also appreciated but not required. Misc/Other Notes Once again to keep things simple data submitted to your service does not need to be persisted. While our main goal is to look at your code, we will run your code and test it. There is no timeline, please take as long as you want. However if you take especially long we may check in. If you have any questions please ask.

I got the interview through a headhunter, and this headhunter lead me to believe that they were preparing an offer after my second interview - the truth was that they had not made any decision. This lead to growing frustration which manifested itself by my contacting one of the interviewers in order to offer additional "justification" for hiring me. Anyone with a lot of interviewing experience knows that doing that is instant death - I knew that and got careless and both Banjo and I lost out.
avatar

Senior Backend Developer

Interviewed at safeXai

3.2★
Sep 24, 2019

I got the interview through a headhunter, and this headhunter lead me to believe that they were preparing an offer after my second interview - the truth was that they had not made any decision. This lead to growing frustration which manifested itself by my contacting one of the interviewers in order to offer additional "justification" for hiring me. Anyone with a lot of interviewing experience knows that doing that is instant death - I knew that and got careless and both Banjo and I lost out.

Viewing 1371 - 1380 interview questions

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