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.
The process I went through was pretty structured and moved fast. It started with a phone screen, then a remote technical interview with the headquarters, and finally an onsite round at the location. The first call was mostly personal and introductory, while the second round was more of a basic knowledge check for the role. The onsite was where things got more technical and practical, and I was asked basic transistor knowledge and how I’d apply it to real situations. That part felt less like memorizing definitions and more like showing that I understood the concepts well enough to use them in context. What stood out most was how different the rounds were from each other. One review I saw described the process as happening all in one day with a software engineer, where they asked about a past project and then wrote a system question on the board and had the candidate analyze it and explain the solution. Another process was more interview-heavy, with four rounds total: three LeetCode-style coding rounds and one system design round that took more than an hour and was described as hard. The coding questions sounded standard, mostly around arrays, lists, maps, and sets, while the system design focused on API design for blob file storage, retrieval, and modifications. There was also a behavioral round with the hiring manager and a question about what you know about VMware. the technical screen was a paper test with 20 C questions covering syntax errors, data structures, networking, OS, architecture, and debugging, mostly fill-in-the-blank or descriptive. Overall, the interviews leaned toward fundamentals rather than trick questions, but the system design portion could get intense and time-consuming. I ended up not getting an offer, so I’d say the safest prep is to be very solid on core coding patterns, be ready to explain a system design clearly on a whiteboard, and review basic OS, networking, and C concepts if that’s part of the role.
Prep tip from this candidate
Be ready for a long system design round on blob file storage/retrieval/modification, and don’t neglect fundamentals like arrays, lists, maps, sets, plus basic OS/networking/C syntax questions. Also prepare to explain a past project clearly and answer why you know VMware.
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 | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Flatten N-Dimensional Array to 1D Array | |
| String Subsequence | |
| Get Top N Frequent Words | |
| Cyclic Detection | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Binary Tree Conversion | |
| Sort Strings | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Complete Addresses | |
| Term Frequency | |
| Centralized Event Ingestion | |
| 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.