Explain Springboot Actuator. N+1 Select Problem How to manage threads efficiently, etc
Back End Engineer Interview Questions
Back End Engineer Interview Questions
If you're applying for a job position as a back-end engineer, interviewers want to know if you have the knowledge to design, build, and maintain the server-side of a website. Be prepared to answer questions about the latest in web design and technology, as well as questions about your problem-solving skills, time management abilities, and communication skills.
Top Back End Engineer Interview Questions & How to Answer
Question 1
Question #1: Can you talk about the most modern advancements in website building and servers?
How to answer
How to answer: Employers don't just want someone who is up to date with the latest technology, they want someone who is innovative and on the cutting edge. When discussing the most modern advancements in web design and web building, talk about how you would incorporate these modern enhancements into the company's website.
Question 2
Question #2: How do you feel about working as a member of a team?
How to answer
How to answer: Back-end engineers often have to work as a member of a team to develop and run a website. Interviewers want to know if you're a team player who can work well with the staff that already exists at the company. Highlight your abilities to communicate effectively and collaborate with others.
Question 3
Question #3: Can you tell me about a time you had to meet a tight deadline?
How to answer
How to answer: When asked this question, highlight your time management skills and ability to stay organized and on task, even in high-stress situations. Employers want to know that you can work well under pressure.
1,560 back end engineer interview questions shared by candidates
Leetcode string and array manipulation
Nothing Just they asked whatever framework i had created. At least they should ask few technical question for rejection. I had great experience but still they rejected.
Por que utilizar anotações em Java?
Por que, em uma requisição x na API, usa-se parâmetros ao invés de passar as informações através do corpo da requisição?
They asked me what I would add to my implementation of the assignment, and why I made some of the technical choices I have. The technical questions were the kind you can find in any coding interview website. I recognized one of the questions, but not the other 2.
Como não causar um overflow com os dados da resposta em algum eventual frontend que consuma essa API?
Java Garbage Collection, Z Garbage Collector (ZGC)
Create two microservices for calculating people's social rating. First microservice (data collector) should: 1. consume http requests with JSON in a body: { "first_name": <text>, "last_name": <text>, "age": <number> } 2. read calculation seed from application properties file (it can be just a random number 0-1) 3. send all information to the queue Second microservice (social rating calculator) should: 1. read message from the queue 2. calculate social rating score (score = base seed * user’s age) 3. print similar to the following message to the application console "<firstName> <lastName> has <socialRatingScore> score" Bonus points: - use docker to run dependent services - the second microservice should save calculated scores for each user in the Redis - It should be possible to specify properties file on the application start phase Desirable to use Java, Spring Boot, Apache Kafka (or AWS SQS).
implement a Search by relevance function
Viewing 1181 - 1190 interview questions