
Stem Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 24 interview experiences · FREE TO READ
Which role are you interviewing for?
14 roles · 24 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Stem.
DevOps Architect
I did a take-home assessment where I had to work with EKS, GitOps, Terraform, and ArgoCD. Basically, I created a GitHub project and then deployed an application using Helm charts to an EKS cluster. I also set up everything using Terraform and GitHub Actions.
- How do you handle EKS cluster upgrades?
All-round Employee
The interview, an adventure that starts even before the meeting. The interview and its fundamental rules. The interview from the candidate's and recruiter's perspective. 3 tips to de-stress before the interview. Manage your body language. Salary negotiation. Closing the interview. Types of interviews and how to conduct them. How to prepare for the second interview? Different tests during the job interview. The essential things to remember.
No confirmed questions were included in this interview report.
Software Engineer
The interview process was pretty straightforward. I was actually approached by a recruiting agency, not through a direct application. It started with an initial call to introduce me to what Stem does. Then, I submitted my CV and was given a coding exercise. The exercise was quite fun, and it seems they weren't too strict on it, as I later reviewed it for other candidates. Following that, I had an interview panel with some engineers, the chief architect, and directors from related dev teams (like QA and DevOps). The questions they asked were realistic and not overly complicated.
- Can you explain how you'd optimize the response time of an API?
- What caching strategies and implementation methods would you use for an endpoint?
UX Designer
The interview process was pretty standard. It started with HR, then the Hiring Manager, and finally the Team Members. The whole thing spanned about 2-3 weeks and involved 4 interviews with 5 people. They were all really nice and we had some great discussions, but ultimately I didn't get an offer, which is fine. What was frustrating, though, was the lack of consistency. I was repeatedly told how much they liked me and my background, but then in the final interview, they suddenly said my design skills weren't up to par. It was strange because we didn't even review my portfolio or my design decision process during that last interview, which you'd expect when meeting potential co-workers. Even the HR person seemed confused when she delivered the news that they chose another candidate. Usually, I'm okay with that, but the role was posted again the same day, which makes me feel misled and lied to, especially since I thought everyone was so friendly.
- What are your career aspirations for your next position?
Stem Interview Questions
Quoted word for word from Stem interview reports.
“Can you explain the distinction between tuples and lists in Python?”
Read reports →“What ratio is used for debt to equity?”
Read reports →“Regarding ERCOT's recent regulatory changes for battery operators, how do you anticipate these will impact the revenue stack for asset owners?”
Read reports →“Could you write a Java class that handles reading from and writing to a file at a specified path?”
Read reports →“Can you explain the value streams that behind the meter battery storage offers?”
Read report →“How do you handle EKS cluster upgrades?”
Read report →“What do I know about the solar developer and EPC base in the northeast?”
Read report →“What caching strategies and implementation methods would you use for an endpoint?”
Read report →“Can you explain how you'd optimize the response time of an API?”
Read report →Formats, difficulty and experience
Across all 24 Stem interview reports.