Skip to main content
In this lesson, we explore how to answer the interview question: “What kind of databases have you used or supported?” Though the question may seem basic, your response can reveal deep insights into your technical experience and impact the interview outcome. Before reading further, take a moment to reflect on your personal experience. Consider which types of databases you are most familiar with and how you have supported them in past roles. This self-reflection will prime you to deliver a concise, yet effective answer during your interview. Databases are essential components of nearly all applications. As a DevOps engineer, you will commonly work with various database technologies while supporting development teams and application infrastructures. Although you are not expected to be a full-fledged database expert, having a clear understanding of the different database types and their use cases is critical.
The image lists different types of databases used in application development, including Key-Value DB (Redis), Column DB, NoSQL Document DB (MongoDB), and Relational DB (MySQL). It emphasizes the importance of understanding database use cases for DevOps engineers.
Avoid stating that you have worked with “all types of databases” unless you can discuss specific use cases for each one. It’s often more effective to focus on the database technology you know best and explain its functionality and benefits in detail.

​
Common Database Types

Below are the typical categories of databases encountered in modern application development:
  1. Key-Value Databases:
    Examples include Redis. In a Kubernetes context, the control plane utilizes etcd—a key-value store—to manage critical cluster data.
  2. Column-Oriented Databases:
    Cassandra is a prime example of a column-oriented database. Unlike row-based databases, column stores focus on efficient data storage and quick retrieval by organizing data in columns.
  3. NoSQL or Document Databases (Schemaless Databases):
    These databases store data in a JSON-like format, eliminating the need for a predefined schema. MongoDB is one of the most recognized document databases, with AWS providing DynamoDB as a managed alternative.
  4. Relational Databases (SQL Databases):
    Systems such as MySQL, Aurora, PostgreSQL, and Oracle are classic examples of relational databases. They are widely adopted in cloud environments and enterprise applications.
When mentioning specific technologies like AWS RDS, MongoDB, or Cassandra, consider linking to their official documentation for enhanced SEO value and credibility.
For professionals with hands-on experience in any of these database types, focus your interview response on that expertise. For example, if you have significant exposure to MongoDB, you might say, “I’ve worked extensively with MongoDB,” and then be ready to discuss its features in more depth should follow-up questions arise.
The image is a diagram categorizing different types of databases, including Key-Value DB (Redis), Column DB, NoSQL Document DB (MongoDB), and Relational DB (MySQL), with annotations and logos.

​
Leveraging Relational Databases in Cloud Environments

For those targeting roles in IT or DevOps, showcasing experience with relational databases can be particularly effective. You might highlight the use of AWS RDS to manage relational databases—such as MariaDB, AWS Aurora, or MySQL—within cloud environments. Sharing such specific examples demonstrates not only your knowledge of database technologies but also your familiarity with cloud infrastructure.

​
Sample Interview Answer

Below is a sample response you might consider during your interview:

​
“I have significant experience working with relational databases in a cloud environment. In my current team, we use AWS RDS to manage multiple relational databases like MySQL and MariaDB, which play a crucial role in our application architecture. This exposure has equipped me with an understanding of database management essentials, including scalability, reliability, and performance optimization in a cloud context.”

Be prepared for follow-up questions that may ask you to elaborate on the specific technologies mentioned. If you have worked with additional database types beyond relational ones, feel free to incorporate those experiences into your response.

​
Final Thoughts

Approach your answer with confidence and ensure your explanation is structured and specific. Emphasizing your hands-on experience with at least one database type—and understanding its real-world application—will leave a lasting impression on your interviewer. Good luck, and see you in the next article!
For further reading on database technologies and DevOps best practices, consider checking out these resources:

Watch Video