E Source logo

E Source Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 18 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
38.9% Positive experience

Which role are you interviewing for?

13 roles · 18 reports

Candidate interview experiences

First-hand accounts from people who interviewed at E Source.

Showing 4 of 18
E Source logo
E Source

Data Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Take home Presentation Background check
Interview formats
Technical Presentation

After some initial interviews, E Source asked me to complete a take-home project which I would then present to an interview panel. I spent a week on this project and proudly turned it in, knowing that I had done a good job on it. They came back and said "After careful review, we’ve decided to move forward with other candidates for this role," without giving me the chance to present my work. This was a shocking about-face on their part and highly unsatisfying. They never told me what about my work was insufficient for their needs.

Confirmed questions1 question
  • Could you design an ELT pipeline that would run in a Data Lake for several tables of electrical utility data?
E Source logo
E Source

Remote Sensing Analyst

Engineering · more than a year ago

Mid Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Presentation

The interview has 3 sections. First part is talking to HR, second part is talking to the manager, and the third part is talking to the manager's team. The interview went well in my opinion and I answered all their questions. The third section was very detailed, almost felt like they were picking my brain as if they don't know the answer. They claimed it's a brainstorm section for the last interview, but honestly, the whole time they were asking me to talk and asking very specific questions about small details as if they didn't know how to solve it.

Confirmed questions1 question
  • What motivates you to join our company
E Source logo
E Source

Director of Product Management

Product

Director Easy Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Panel Onsite Background check
Interview formats
Behavioral Technical Presentation

The interview process involved a phone screen, followed by a panel interview with the research team, an interview with one of the company owners, and then meeting with the HR VP. This was considered the first visit. The second visit included meeting with the VP of Software Development. They asked a lot of questions about research, which seemed odd for an agile company. I think if you're hiring for an agile director of software development, the interview should reflect that. Questions about agile roadmaps, agile culture, and understanding MoSCow ratings and Kano scores would be more appropriate.

Confirmed questions2 questions
  • What are your thoughts on our weighted product vetting excel spreadsheet?
  • How do you approach using our weighted product vetting excel spreadsheet?
E Source logo
E Source

Data Scientist

Analytics

Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Panel
Interview formats
Behavioral Technical

I went through 3 rounds for the role. It started with a 30 min phone screening with the recruiter, then a 45 min video interview with a Sr. Data Scientist. After that, there was a 90 mins technical interview with a panel of scientists and a manager. The team seemed great, really smart and capable people. The technical part involved brainstorming a past project. Unfortunately, the position was cancelled, which aligns with some negative feedback I've seen about upper management.

Confirmed questions3 questions
  • Can you discuss your past projects, focusing on behavioral aspects?
  • Can you discuss your past projects, focusing on technical aspects?
  • Let's brainstorm through one of your past projects.

E Source Interview Questions

Quoted word for word from E Source interview reports.

Could you explain the distinction between an abstract class and an interface?

Read reports

Could you design an ELT pipeline that would run in a Data Lake for several tables of electrical utility data?

Read report

How do you approach using our weighted product vetting excel spreadsheet?

Read report

What are your thoughts on our weighted product vetting excel spreadsheet?

Read report

Formats, difficulty and experience

Across all 18 E Source interview reports.

Interview formats

Technical 35%
Behavioral 30%
Presentation 17.5%
Case 7.5%
Coding 5%

Interview difficulty

Easy 22.2%
Average 72.2%
Difficult 5.6%

Candidate experience

Negative 33.3%
Neutral 27.8%
Positive 38.9%

Reports by job function

Engineering 5
Research 3
Analytics 3
Consulting 2
Product 2
Operations 1