Enphase Energy Software Engineer Interview Questions
& Process

I applied off the campus and the process started after 2 months. There was a Hiring Manager Round, which was pretty basic and resume-based for fitment. Then, a Technical Round to check fundamentals and skills alignment. After that, an HR Round for behavioural and salary discussion. Finally, a round with the Senior VP for basic behavioural questions. The Senior VP had concerns about my 2 years of experience being too less for a switch and also about the 90 days notice period. It's a humble request to not waste time if you are not clear about the experience level. What matters is what the candidate can bring to your organization with their skills and if the reason to switch is genuine.

The interview process kicked off with a Hiring Manager chat. Next, there was a Leetcode round, specifically for a mid-level role. Following that, a technical screen focused on my resume and past experience. The final round was a behavioral interview with a senior Vice President; they mentioned that if you get to this stage, you're pretty much set to get hired.

So this was a really weird interview process, like, one of the strangest I've been through. It was a multi-step thing with a lot of overlap, almost like they wanted to make you feel lucky they'd even talk to you. They'd expect you to change interview times last minute a lot, and spend hours talking to people who acted like they barely had time for you. Why have so many rounds if the stuff you presented earlier never gets passed on, and you have to start over with each new person? There were like, over a dozen conversations in total. By the end, I guess I kept going out of curiosity to see the people in charge (I had another offer already). Everyone kept repeating how collaborative and team-oriented they are, but their questions were all about making themselves seem smart. This backfired when one interviewer got mad because I asked follow-up questions, and it turned out the basic math he used in a problem was wrong. Some people also trashed other departments, all while trying to do this 'google-ish socratic' thing with confusing questions. The higher up I went, the more interviewers talked about themselves. They see themselves as 'Silicon Valley model' so expect long hours, and they have opaque questions to test you. They also said you do your actual work before or after business hours because of constant meetings. Management knows this is an issue and has policies for meetings that seem to make things worse. They said they release weekly because it's 'Agile', which is a terrible reason. The software is simple, and the engineers are smart, but management seems to compete and overcomplicate things. After the last interview, the hiring manager said I was a top candidate and they'd decide fast... then nothing. I took my other offer. But seriously? No follow-up from the hiring manager. Bottom line, this seems like a bad place to work.