Canonical Senior Software Engineer interview questions

Education How did you fare in high school mathematics, physical sciences and computing? Which were strengths and which were most enjoyable? How did you rank, competitively, in them? Which degree and university did you choose, and why? What did you enjoy most about your time at university? Outside of class, what were your interests and where did you spend your time? What did you achieve at university that you consider exceptional? Context Describe your experience with Data Platform technology (e.g. PostgreSQL, MySQL, MongoDB, Kafka, Elasticsearch, Redis, etc.) Give details of your practical experience with Kubernetes, and with container-based operations in general Have you had any involvement in the Cloud Native community, or contributed to any related projects? Outline your thoughts on the challenges of operating a well integrated and robust data platform What is your understanding of the core functionality for a software operator that drives, for example, a database? Why do you most want to work for Canonical? Engineering Experience What kinds of software projects have you worked on before? Which operating systems, development environments, languages, databases? Give details of your Python software development experience to date, how would you rate your competency with Python? Which project or piece of software are you most proud of, and why? Give details of any experience you have with automated provisioning tools, configuration management and infrastructure-as-code tools How comprehensive is your knowledge of Linux, from the kernel up? How familiar are you with low-level system architecture, runtimes, packaging and command line tooling? Describe your experience with public cloud based operations - how well do you understand large-scale public cloud estate management and developer experience? Outline your thoughts on quality in software development. What practices are most effective to drive improvements in quality? Outline your thoughts on documentation in software projects. What practices should teams follow? What are great examples of open source docs?