Software Engineer applicants have rated the interview process at Sunrun with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 25% positive. To compare, the company-average is 49.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 16 days to get hired, when considering 10 user submitted interviews for this role. To compare, the hiring process at Sunrun overall takes an average of 18 days.
Common stages of the interview process at Sunrun as a Software Engineer according to 10 Glassdoor interviews include:
Phone interview: 36%
Group panel interview: 27%
Skills test: 18%
Background check: 9%
IQ intelligence test: 9%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1+ week. I interviewed at Sunrun (San Francisco, CA) in Apr 2015
Interview
HR screen, followed by a same day technical phone screen. Onsite interview the next week was well organized and enjoyable. I had an assigned room, with a rotation of interviewers from various teams and roles. Everyone is friendly - not a hostile interviewer in the bunch. I did get thrown off by a few questions on technologies I haven't worked on, but most of the questions were softballs for any experienced developer.
4
Other Software Engineer Interview Reviews for Sunrun
The recruiter's expectations didn't match those of the manager or the person conducting the technical interview. I had a screening with a headhunter, a conversation with a potential manager, and a technical test.
Interview questions [1]
Question 1
They were interested in solving LeetCode problems.
I was reached out to by a recruiter who then spoke with about the responsibilities for the role. A few days after, I spoke with the engineering manager who then gave me a technical interview and asked more about my experiences.
Interview questions [1]
Question 1
How would you calculate a total value given an extremely large amount of data that doesn't fit into memory?
I applied online. I interviewed at Sunrun (San Francisco, CA) in May 2017
Interview
Recruiter Screen, Phone Screen and then onsite.
Phone Screen: Reverse in place “one two three” -> “three two one”
First round is Java Questions. Final, Finally, Finalize,
Second round is Spring. Describe when a service should be created at start-up or initialized lazily? Explain Authentication - Basic, Digest. And autherization: OAuth2
Third: List what a new service requires and what technologies you would consider. (Caching, Data layer, Logging, Code coverage, Static Analysis, Metrics, Authentication)
Fourth: SQL Update Statement. Optimistic Locking vs Pessimistic Locking. Drawbacks of ORM.
Fifth: VP of Eng. You get to ask questions about the future of the company.
Interview questions [1]
Question 1
Find all pairs of numbers with min difference. (1 2 5 8 9) -> [[1,2][8,9]]