Software Engineer 1 Interview Experience - Oakland, California
Process
There were 4 rounds. The 1st round was a technical chat about background and basic Java/database questions. The 2nd round was a coding challenge (max heap question). The 3rd round was an on-site (virtual) 3-hour interview with a mix of behavioral, technical, and coding. The final round was a 30-minute behavioral interview with the manager.
Questions
Explain advantages and disadvantages of normalizing and denormalizing a database.
Why are strings immutable in Java?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Fivetran Software Engineer 1 role in Oakland, California.
Success Rate
Fivetran's interview process for their Software Engineer 1 roles in Oakland, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Experience Rating
Candidates reported having very negative feelings for Fivetran's Software Engineer 1 interview process in Oakland, California.
Fivetran Work Experiences
- 1.0Good product, rigid cultureSoftware Engineer • Current EmployeeOakland, California, United StatesSeptember 24, 2025Pros: Good product, and the office setup is nice.Cons: Work-life balance sucks and micromanagement.
- 4.0Good entry-level companySenior Software Engineer • Current EmployeeOakland, California, United StatesJanuary 6, 2025Pros: - Good pay - Helpful teamCons: - Lots of changes happened recently - Redirection of work
- 2.0Disorganized, Niche ProductSoftware Engineer II • Current EmployeeOakland, California, United StatesJuly 31, 2024Pros: - Local - Great 401k matching - Opportunity to deep dive into databases and big data metrics - Lunch and snack perksCons: The more obscure engineering teams may be disorganized, so opt for product-to-consumer as much as possible. On my team, the management chain was disorganized and consistently unsure of the purpose of a project. Even with explanation from myself, a manager, and a more "senior" coworker, the rest of the team failed to understand the long-term significance of projects. Compensation was mid and strict compared to the market. My direct manager often forgot the strategy for product scoping.
