Software Engineer Interview Experience - San Francisco, California
Process
My interview experience at Twitch was by far the best I've ever had.
It started with an introduction from a recruiter, during which we discussed my past work and what I was looking for. Afterwards, they introduced Twitch's engineering teams and where they believed I could be a potential fit.
Next in the process was a technical phone screen, followed by a day of onsite interviews. Every single team member I met was consistently approachable and energetic, which really put me at ease and kept most of the interview nervousness to a minimum.
Out of respect to the NDA I signed, I can't discuss any specifics, but do expect to work through typical coding/whiteboarding exercises. It seems they really try to design the interviews to find strong generalists, which is great since you should be able to shine in some parts of the interview and show basic competency in others.
Overall, an amazing experience that made me even more excited to join the team.
Was this helpful?
Interview Statistics
The following metrics were computed from 37 interview experiences for the Twitch Software Engineer role in San Francisco, California.
Success Rate
Twitch's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having good feelings for Twitch's Software Engineer interview process in San Francisco, California.
Twitch Work Experiences
- 5.0Fun Company, Smart People!Software Engineer • Former EmployeeSan Francisco, California, United StatesMarch 18, 2021Pros: Fun company and smart people.Cons: No cons, fun, and innovative.
- 1.0No Focus On QualitySoftware Engineer • Current EmployeeSan Francisco, California, United StatesAugust 30, 2017Pros: The product is interesting, at least.Cons: Engineering takes a back seat to getting releases out. Frequently, these releases have key features (or sometimes even central features) removed to hit deadlines. We used to have centralized quality teams, but they've been cannibalized for feature team headcount. The result is slower development because each feature team is having to create its own operations and development tools, because what's left of devtools can't support the company anymore. There's no good way to share these tools cross-org. A lot of teams have insane deadlines and overwork themselves trying to hit them. Product quality is in free-fall, and everyone's more interested in tricking Amazon into thinking we're accomplishing things than improving anything. Quality of life is trending downward: perks are being cut, food/drinks aren't being restocked, and wage increases were below inflation last year org-wide. Half the company's manager upline doesn't go through the CEO and instead goes through some Amazon guy now. Things are going bad real fast. A new building is opening up next year, but they're cutting 6 inches off everyone's desk to make it work. It's not clear how we'll fit our monitors in our workstation at that point.
- 5.0Amazing place to work!Software Engineer • Current EmployeeSan Francisco, California, United StatesAugust 12, 2014Pros: It's really hard to list the best thing about working at Twitch. The leadership is solid, the ability to work on unique projects, and the culture is phenomenal. The twice-a-week breakfasts and daily lunch/dinner is a much-added convenience versus going out and getting lunch.Cons: Sometimes things are moving at such a rapid pace, communication can get messed up.
Twitch Interview Questions
