Be prepared to explaing following terms/rules/principles etc.
- MVC 🔹
- Idempotency 🔹 🐩
- REST 🔹
- Single responsibility principle 🔸 🔖
- Open/Closed principle 🔺 🔖
- Liskov substitution principle 🔸 🔖
- Interface segregation principle 🔺 🔖
- Dependency inversion principle, link 2
- Tell, don't ask principle 🔸 🔖
- Law of Demeter 🔹
- Duck-typing 🔹 🔖 🐩
- Inversion of control
- Dependecy injection 🔺 🔖
- Explaining Variable 🔸 🔖
- DRY 🔹 🐩
- Eventual Consistency 🔺 🔖 🐩
- Composition over inheritance 🔺 🔖
- Loose coupling / High Cohesion
- Microservices 🔸 🔖 🐩
Be prepared to talk about following topics. Answers can be scoped to given framework.
- What do you think about custom controller actions (outside CRUD)?
- What do you consider clean code?
- How about testing? Are there any principles you identify with regarding TDD?
- How would you ensure that tests are easy to understand by other developers?
- Does writing tests after implementation affects process & quality in positive or negative way? Please explain.
- What do you like about [framework] the most?
- What is your preferred way in working with repository? (i.e. GitFlow) 🐩
- What options can you see in terms of static code analysis? 🐩
- What is your list of top things/techniques to ensure high code quality and why?
- What do you think about metaprogramming?
- What patterns do you consider useful when writing backend MVC apps?
- What full-text search solution are you familiar with? In what cases would you use those solutions?
- What do you miss in [framework]? Where do you think [framework] is not the good fit?
- What do you think about project documentation?
- What are the anti-patterns when writing [framework] apps in your opinion?
- How would you deal with complex, legacy project that you need to work with, if it does not have adequate tests coverage?
- Are you familiar with concept of Test Induced Design Damage? What is your opinion on that? 🐩
- How do you often deal with long running requests (i.e. generating documents)
- How would you describe “maintainable code”?
- If I was to write API only application in [language], what would be your recommendations / hints in relation to this task?
- What kinds of caching do you feel are the most useful when developing [framework] applications?
- If there is an information you need deep inside your code, but it is only accessible on top level (i.e. in controller), how would you approach propagating it (think “current_user”, but it can be anything else)
- What do you think about / where do you find application for JWT 🐩
- What do you think about / where do you find application for Pub / Sub 🐩
- What do you think about / where do you find application for UUIDs 🐩
- What do you think about / where do you find application for WebSockets 🐩
- Where do you find use for so-called "monorepo"s 🐩
- What is your opinion about monolithic vs microservice based architecture? 🐩
- How would you ensure reliability of microservice architecture?
- How do you deal with database related performance issues (when processing tens of millions of records)?
- If you are asked to implement an interface that should work with live (realtime) data feed, how would you approach implementing it?
- How would you handle very intense traffic (i.e. from IoT) in [framework] application?
- How would you ensure stability of public API in application that is under active and rapid development?
- What do you think about / where do you find application for SOA 🐩
- What do you think about / where do you find application for CQRS 🐩
- What do you think about / where do you find application for DDD 🐩
- What do you think about / where do you find application for Event Sourcing 🐩
- What do you think about / where do you find application for Reporting Databases