Area	Teamwork, Communication,Business processes,FeedbackOwnership and Drive
Phase 1 (junior, mid)	• Did you have any conflicts at work in the past? ◦ over technology, misunderstanding of context, PR reviews, different views on arch solution? ▪ How did you resolve them? • What work processes are you used to? ◦ What code style do you use? ◦ What is the difference between waterfall, scrum and kanban? ◦ What are the benefits and the drawbacks of working in an Agile environment? • How does perfect PR look like?
Phase 2 (mid, senior)	• How requirements and documentation can be expressed and held up-to-date? ◦ Tests, readme, api docs, DB diagrams, state • Tell us an incident that you caused • What is the perfect task description for you? Who should write it? ◦ Acceptance criteria / steps to reproduce • As company and team grows from 1+ developer to 200+, how should teams grow? ◦ Should engineers have narrow specialisation? ◦ Should engineers have access to live DB? ◦ Should services have internal credentials? • At what you should pay attention with PR reviews? ◦ bugs, size, complexity, improvements
Phase 3 (senior+)	• What should happen if service goes down in the middle of the night? ◦ on-call & alerts • How do you make sure that critical bugs in production at night don't keep growing within organization? ◦ incident management. lessons learned. CI. • What non-functional requirements can you list? ◦ Security, Scalability, Consistency, Fault tolerance • You need to partially migrate data to another datacenter, but its owned by 5+ teams. How do you do that? • Any opensource contributions / maintenance experience?