
Electric AI Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Electric AI.
Software Engineer
The interview process was smooth and straightforward. The recruiter was super friendly and helpful. It started with a 30-minute recruiter call, then a technical call with an engineering director. After that, I had a code challenge which included both a design doc and an implementation part. They were flexible with my schedule for the "on-site" rounds, which were all remote, and spread them out over a few days. I did a technical system design interview, a behavioral interview asking about past experiences, and an interview with my potential manager. Everyone I met was nice, asked good questions, and answered mine thoroughly. The recruiter kept in touch between rounds, and I got an offer call a few days later.
- Can you share an instance where you had to work with different teams to successfully complete a project?
Software Engineer
The interview process was pretty standard for a software engineering role. Communication from the recruiting team was good, and they were happy to answer any questions I had. Overall, it was a positive experience and I'd recommend it. The process involved: 1. A screening interview. 2. A coding interview. 3. Panel interviews focusing on system design. 4. A final interview with senior management.
- Can you solve a LeetCode easy/medium string manipulation problem?
- How would you design a messenger system?
Software Engineer
Had a 30-minute call with the hiring manager. After that, there was a 90-minute test on HackerRank.com. I thought the test was kind of silly and not a good way to measure a developer's skills. The third question was especially confusing and silly. Honestly, the best things about a senior engineer are maturity, business sense, communication, getting along with others, being punctual, and staying positive. Most problems involve research and analysis first, not immediate coding. I'm not sure why these kinds of tests are standard now, but they seem pointless to me.
- Can you write a program to convert decimal numbers up to 1000 into Roman numerals?
- Could you convert a prefix expression into its postfix equivalent?
- Write a program to calculate the cost of fused nuclear rods, where rods are grouped, and the cost is the sum of the square roots of the number of rods in each fused group.
Electric AI Software Engineer Interview Questions
Quoted word for word from Electric AI interview reports.
“Write a program to calculate the cost of fused nuclear rods, where rods are grouped, and the cost is the sum of the square roots of the number of rods in each fused group.”
Read reports →“Could you convert a prefix expression into its postfix equivalent?”
Read reports →“Can you write a program to convert decimal numbers up to 1000 into Roman numerals?”
Read reports →“What about the Nuclear rods problem?”
Read reports →“Can you explain Postfix/prefix notation?”
Read report →“How would you handle Roman Numerals?”
Read report →“How would you design a messenger system?”
Read report →“Can you solve a LeetCode easy/medium string manipulation problem?”
Read report →“How would you design a system that takes in Slack requests from outside and routes them to our internal system?”
Read report →Formats, difficulty and experience
Across all 5 Electric AI interview reports.