Symantec Software Engineer interview typically runs 4 rounds: phone screen, technical interview, onsite, and manager/HR. Timeline is about 1 day to 2 months, and the process is often structured but can be uneven.
$118K
Avg. Base Comp
$207K
Avg. Total Comp
4-6
Typical Rounds
3-8 weeks
Process Length
Our candidates consistently describe Symantec as a place where the interviewers want to see whether you can reason from first principles, not just recite patterns. Across experiences, the strongest signal is comfort with core CS fundamentals: arrays, linked lists, sorting, bit manipulation, OS, networking, and even lower-level hardware concepts like transistors, CDC, FIFOs, and logic optimization. Multiple candidates reported that the questions were often straightforward in topic but less forgiving in how they were framed, which means the real test is whether you can explain your thinking cleanly when the prompt is broad or slightly awkward.
A recurring theme is that Symantec seems to care a lot about practical clarity over polished theory. We’ve seen candidates asked to analyze a system on a whiteboard, design storage or scheduler-style components, or talk through a past project in detail. In several accounts, the interviewer moved quickly from background questions into technical judgment, and one candidate noted that the interviewer seemed not to have read the resume closely. That makes preparation around your own experience especially important: if you can’t connect your past work to the role’s technical needs, the conversation can feel disorganized fast.
The other pattern we’ve seen is that the bar is broad rather than deeply specialized. Some candidates faced LeetCode-style mediums without coding, others got paper-based pseudocode, and others were pushed into JavaScript internals or system design. That mix suggests Symantec is looking for engineers who can stay composed across different formats and still make sound decisions. The candidates who did well were the ones who could move fluidly between DSA basics, system reasoning, and implementation tradeoffs without overcomplicating the answer.
Synthetized from 4 candidates 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 Symantec process.
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 Symantec
Design a database schema for a Tinder-style dating app and discuss needed optimizations
| Question | |
|---|---|
| Common Prefix | |
| Yelp-like System | |
| Ride-Sharing App Schema | |
| Client Solution Pushback | |
| Game Feature Home | |
| Google Docs Autosave System | |
| Reddit-like Notifications | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Weighted Keys | |
| Prime to N | |
| Largest Salary by Department | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Flatten N-Dimensional Array to 1D Array | |
| String Subsequence | |
| Get Top N Frequent Words | |
| Centralized Event Ingestion | |
| Cyclic Detection | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Binary Tree Conversion | |
| Sort Strings | |
| Find Duplicate Numbers in a List | |
| Valid Anagram | |
| Complete Addresses | |
| Term Frequency | |
| Target Indices | |
| Swapping Nodes |
Synthesized from candidate reports. Individual experiences may vary.
The process typically starts with an introductory phone call with a recruiter, employee, or hiring manager. This stage is mostly conversational and covers your background, interest in the role, and whether your experience matches the team’s needs.
Candidates then move into an initial technical screen, which may be remote or paper-based depending on the team. The questions focus on fundamentals such as C syntax, data structures, networking, OS concepts, debugging, or a medium-level coding problem, and in some cases candidates are asked to solve problems in pseudocode rather than write full code.
Successful candidates usually complete several technical rounds with senior engineers. These interviews emphasize core DSA and practical problem solving, with topics like arrays, linked lists, sorting, bit manipulation, multithreading, JavaScript fundamentals, and lower-level CS concepts such as CDC, FIFOs, and logic optimization.
At least one round can be a design-focused interview, sometimes described as hard and lasting more than an hour. Candidates may be asked to whiteboard or analyze systems such as blob file storage APIs, trellis board implementations, or a multithreaded scheduler, and explain tradeoffs clearly.
The final interview often includes the hiring manager and is more behavioral. Expect questions about your past projects, why you want the role, how your experience fits, and broader fit questions such as what you know about VMware or similar adjacent technologies.
Some candidates also had an HR round after the technical interviews, especially in the assessment-day format. After this stage, the team makes the final decision and extends an offer or rejection.