Skip to contentSkip to footer

Database Software Engineer Interview Questions

Salaries
Interviews

39 database software engineer interview questions shared by candidates

First Round: Coach Interview The initial 45-minute interview was a thorough exploration of my technical background and project experience. The coach fostered a friendly and relaxed atmosphere, encouraging an open discussion. His genuine interest in my potential contributions to the company, underlined by the emphasis on continuous learning opportunities at DataStax, made the interaction enjoyable. Following this positive exchange, we connected on LinkedIn. Second Round: Interview with Engineering Leader During the second round, the manager detailed his responsibilities and posed a few questions related to Kubernetes (k8s). Despite my explicit mention of not having worked with k8s recently, he suggested that I brush up on it for potential future rounds, a recommendation I appreciated. However, an undertone of negative power dynamics was detectable, creating a disconnect that raised doubts about long-term fit. Unfortunately, this round was a bit of a downer. Third Round: Values Interview with Second Coach This 30-minute discussion revolved around the company's core values: speed, execution, and ownership. The coach articulated their interpretation of these values, and I reciprocated, gaining insights into the company's commitment to its principles. The term "chaos" was notably mentioned, alluding to a potentially challenging work environment. The stress on self-reliance and thriving amidst "chaos" made me ponder the existence of issues like micromanagement within the organization. Fourth Round: Architecture/Design Interview Conducted by a lead and senior engineer, this round focused on a specific project from my resume. It delved into my knowledge of k8s, networking, and observability. The discussion showcased the diverse technological stack at DataStax and hinted at opportunities for professional growth. However, the mention of on-call responsibilities alongside development work pointed towards a potentially overwhelming workload. Codility Assessment: The Codility assessment posed a problem similar to a medium-level LeetCode question. Although I submitted my solution, I inadvertently overlooked a test case, which was addressed in the following round. Final Round: Code Review Assessment: The final round involved two software engineers, diving immediately into problem-solving and code reviewing. However, a communication gap between the HR department and the engineering team was evident when one engineer asked for a link to my solution, seemingly unaware of a change in the process. During this review, I clearly defined the problem, demonstrated various test cases, and walked them through my thought process. I acknowledged a missed test case and proposed an optimized approach to address it. The experience with the engineers was mixed; one seemed preoccupied, while the other, despite nearing the end of his day, was receptive and appreciated my clear explanation. This final round left me with a sense of ambiguity due to unclear expectations around problem-solving and coding skills. It was a mixed bag with both highs and lows, leading to a neutral assessment overall. Overall Review: Based on my interview experience, DataStax appears to foster a high-intensity, potentially chaotic environment. Personally, such settings appeal to me as they provide the right stimulus for mastering my field, particularly at this stage of my career. While DataStax's product is impressive, and their multi-cloud SaaS offering possesses significant potential (coupled with indications of an imminent IPO), the organization seems to be grappling with issues that contribute to a chaotic atmosphere within the engineering department. These issues appear to stem from pressure exerted by the upper leadership. In light of these observations, I would suggest that the senior management team revisit their stated values and reflect on their adherence across all levels and departments of the organization. This could potentially uncover gaps that need addressing for the company to meet its ambitious objectives. Despite the challenges noted, I genuinely wish DataStax the very best in their journey towards achieving their goals and objectives.
avatar

Software Engineer - Astra Cloud Database (Remote US)

Interviewed at DataStax

4★
Jun 23, 2023

First Round: Coach Interview The initial 45-minute interview was a thorough exploration of my technical background and project experience. The coach fostered a friendly and relaxed atmosphere, encouraging an open discussion. His genuine interest in my potential contributions to the company, underlined by the emphasis on continuous learning opportunities at DataStax, made the interaction enjoyable. Following this positive exchange, we connected on LinkedIn. Second Round: Interview with Engineering Leader During the second round, the manager detailed his responsibilities and posed a few questions related to Kubernetes (k8s). Despite my explicit mention of not having worked with k8s recently, he suggested that I brush up on it for potential future rounds, a recommendation I appreciated. However, an undertone of negative power dynamics was detectable, creating a disconnect that raised doubts about long-term fit. Unfortunately, this round was a bit of a downer. Third Round: Values Interview with Second Coach This 30-minute discussion revolved around the company's core values: speed, execution, and ownership. The coach articulated their interpretation of these values, and I reciprocated, gaining insights into the company's commitment to its principles. The term "chaos" was notably mentioned, alluding to a potentially challenging work environment. The stress on self-reliance and thriving amidst "chaos" made me ponder the existence of issues like micromanagement within the organization. Fourth Round: Architecture/Design Interview Conducted by a lead and senior engineer, this round focused on a specific project from my resume. It delved into my knowledge of k8s, networking, and observability. The discussion showcased the diverse technological stack at DataStax and hinted at opportunities for professional growth. However, the mention of on-call responsibilities alongside development work pointed towards a potentially overwhelming workload. Codility Assessment: The Codility assessment posed a problem similar to a medium-level LeetCode question. Although I submitted my solution, I inadvertently overlooked a test case, which was addressed in the following round. Final Round: Code Review Assessment: The final round involved two software engineers, diving immediately into problem-solving and code reviewing. However, a communication gap between the HR department and the engineering team was evident when one engineer asked for a link to my solution, seemingly unaware of a change in the process. During this review, I clearly defined the problem, demonstrated various test cases, and walked them through my thought process. I acknowledged a missed test case and proposed an optimized approach to address it. The experience with the engineers was mixed; one seemed preoccupied, while the other, despite nearing the end of his day, was receptive and appreciated my clear explanation. This final round left me with a sense of ambiguity due to unclear expectations around problem-solving and coding skills. It was a mixed bag with both highs and lows, leading to a neutral assessment overall. Overall Review: Based on my interview experience, DataStax appears to foster a high-intensity, potentially chaotic environment. Personally, such settings appeal to me as they provide the right stimulus for mastering my field, particularly at this stage of my career. While DataStax's product is impressive, and their multi-cloud SaaS offering possesses significant potential (coupled with indications of an imminent IPO), the organization seems to be grappling with issues that contribute to a chaotic atmosphere within the engineering department. These issues appear to stem from pressure exerted by the upper leadership. In light of these observations, I would suggest that the senior management team revisit their stated values and reflect on their adherence across all levels and departments of the organization. This could potentially uncover gaps that need addressing for the company to meet its ambitious objectives. Despite the challenges noted, I genuinely wish DataStax the very best in their journey towards achieving their goals and objectives.

Viewing 21 - 30 interview questions

Glassdoor has 39 interview questions and reports from Database software engineer interviews. Prepare for your interview. Get hired. Love your job.