HeyGen Software Engineer interviews, as three candidates describe them, include an online assessment and coding, and sometimes system design or metrics-heavy behavioral rounds. Includes prep priorities and pay estimates.
$233K
Avg. Base Comp
$275K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Three candidates describe HeyGen's Software Engineer interview, and each took an online assessment at some point; two say it was the first step. They describe the rest of the process differently, so prepare for variation rather than one fixed loop.
One candidate found the assessment harder than the live rounds. They faced three coding questions in 70 minutes: a 2D dynamic programming problem, a REST API task that involved extracting, cleaning and sorting information, and a decorator problem. Practice working through several problems under time pressure.
Live technical rounds read as more fundamentals-driven. One candidate got a hashmap-style coding question. Another got a single LeetCode-style data structures and algorithms question and lost momentum when they forgot a Python API detail, so know your language's standard library well. A third candidate reports filling in and optimizing class methods and designing a map with snapshot functionality.
Behavioral rounds may not be conventional. One candidate says the final behavioral round probed deeply into business and product metrics, and it was different from what the recruiter had described. Another reports a behavioral conversation with a hiring manager or CTO. Prepare to explain how you would measure a product's success, along with the usual project stories.
Timing also varied. One candidate reports about 3 to 4 weeks overall, while another reports roughly three months between the assessment and the technical interview. All three candidates report no offer, and two mention getting no feedback. Ask your recruiter about the format of each round up front.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the HeyGen process.
I was contacted by a third-party recruiter and moved fairly quickly through the interview process. Everything was scheduled at once, so I had a coding challenge, a system design interview, and a behavioral round with the hiring manager or CTO all lined up back-to-back. I didn't get much context about the role or team culture from the recruiter call itself—it felt more like a box to check.
The technical rounds covered a range of topics. One interview asked me to fill in methods for a class and optimize it. Another presented a design challenge around building a map with snapshot functionality. There was also a harder online assessment with three coding questions crammed into 70 minutes: a 2D DP problem, a REST API design question, and a decorator coding problem. The REST API question specifically asked me to extract, clean, and sort information. My technical interviewer seemed disinterested or lazy, which didn't help the vibe.
I didn't receive an offer. Looking back, I wish the recruiter had set clearer expectations about what to study and given me more insight into the actual team and role before diving into the gauntlet of interviews.
Prep tip from this candidate
Go deep on 2D dynamic programming, REST API design patterns, and decorator patterns before your interview. The online assessment is notably hard and time-constrained, so practice solving multiple problems under pressure.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at HeyGen
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Random SQL Sample | |
| String Shift | |
| Bagging vs Boosting | |
| Job Recommendation | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Minimum Change | |
| Top 3 Users | |
| Comments Histogram | |
| Find the First Non-Repeating Character in a String | |
| The Brackets Problem | |
| First Touch Attribution | |
| Flight Records | |
| Prime to N | |
| P-value to a Layman | |
| Level Of Rain Water In 2D Terrain | |
| Size of Joins | |
| Upsell Transactions | |
| Download Facts | |
| Find Bigrams | |
| Google Maps Improvement | |
| Daily Retention Summary |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates report an online assessment as the first step, and a third also took one. One describes three questions in 70 minutes: a 2D dynamic programming problem, a REST API question on extracting, cleaning and sorting data, and a decorator problem. Practice multiple problems under a timer.
Candidates describe different pacing. One says a third-party recruiter scheduled several interviews back-to-back, and another reports a recruiter who checked in before each behavioral round. A third waited about three months after the assessment. Expect timing to vary and ask for details on each round.
Candidates report coding rounds centered on fundamentals: a hashmap-related question, a single LeetCode-style DSA problem, and filling in and optimizing class methods. Clean implementation and fluency with your language's standard library appear to matter, since one candidate lost time on a forgotten Python API.
One candidate reports a design challenge around building a map with snapshot functionality. Only one account mentions this round, so it may not appear in every loop. Be ready to discuss data structures, state and versioning trade-offs if a design round is scheduled.
One candidate reports two behavioral rounds, with the last probing business and product metrics in depth. Another reports a behavioral round with a hiring manager or CTO. Prepare project stories, and practice explaining how you would define and measure product success.
