Read a function, explain what it does, declare tests for it and find bugs.
Senior Backend Engineer Interview Questions
2,786 senior backend engineer interview questions shared by candidates
Qué me motivaba a cambiar de trabajo y mi experiencia reciente y relevante.
Check if string contains the exact same number of repetitions of every character. I.e. "aabb" - true, "aabbc" - false. Then check if removing a single character from the string can make it valid, i.e. "aabbc" - true, "aaabbbcc" - false
Code base to modify. It had tests
What is the name of main Spring web servlet? Algorithm related problems and general technology related questions. Some questions related to frontend development.
coding problem trie-based autocomplete system
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.
Apart from the project demo, they asked a number of very specific questions of how I would deal with very particular scenarios when developing and deploying a new API. It seems like they were just looking for ideas on how to solve existing problems, without paying someone to do it.
Theory questions about DNS, TLS, HTTPS, Reverse Proxy, everything related security.
- Rest Python PR review - URL shortener for system design
Viewing 2761 - 2770 interview questions