Candidates describe Symantec software engineer interviews as a mix of recruiter or manager conversations, LeetCode-style array and linked-list coding, project walkthroughs, and sometimes JavaScript or system design.
$121K
Avg. Base Comp
$140K
Avg. Total Comp
Not reported
Typical Rounds
2 months
Process Length
Candidate reports for Symantec software engineer roles point to fundamentals over exotic puzzles. Coding questions were mostly easy-to-medium array and linked-list problems. One candidate was asked to detect a repeated number in an array and then count repeats. Another removed duplicates from a linked list and found the smallest subarray with a minimum sum. A third covered merge sort and a binary search style question similar to finding a bad commit.
The format varies a lot. One candidate started with a HackerRank assessment on data structures and Java, then an HR call, then a technical interview with the future manager. Another had a phone screen on past projects followed by a technical round that took about an hour. A third had a phone call with an employee and then an in-office interview with two interviewers. The longest report covered close to two months from start to finish. That process included a hiring manager call and a full day of technical interviews with around nine interviewers.
Project discussion matters too. One candidate was asked to sketch a flow diagram of a past project and explain resiliency and scale. Another was questioned on the design decisions behind past work. If your background is front-end, note that one candidate reported a JavaScript round covering polyfills, flattening an object, closures, and the event loop. System design came up as a multithreaded scheduler application and a trellis board implementation.
Tone varied. One candidate found the interviewers professional and patient. Another described an in-office interview with vaguely defined prompts and a LeetCode-style medium that was discussed without writing code. With only a handful of directly relevant reports, treat the exact mix as unconfirmed. Practice coding aloud, refresh basic array problems, and be ready to explain your own projects clearly.
Synthesized from 12 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 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 | |
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Flatten N-Dimensional Array to 1D Array | |
| P-value to a Layman | |
| String Subsequence | |
| Get Top N Frequent Words | |
| Groups of Anagrams | |
| Cyclic Detection | |
| Longest Increasing Subsequence | |
| Skyscanner Partner ETL | |
| Sort Strings | |
| Binary Tree Conversion | |
| Valid Anagram | |
| Term Frequency | |
| Complete Addresses | |
| Find Duplicate Numbers in a List | |
| Swapping Nodes |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report a conversational opener. One had a phone call with the hiring manager about background and motivation. Another had an HR round after an online assessment, and another had a phone call with an employee. Prepare a clear walkthrough of your experience and what you are looking for.
One candidate described a HackerRank assessment on data structures and Java as the first gate before the HR round. Not every report mentions an assessment, so it may depend on the team or hiring path. Practice fundamental array, string, and linked-list problems in your main language.
Candidates report easy-to-medium problems: repeated numbers in an array, removing duplicates from a linked list, and smallest subarray with a minimum sum. Others recalled merge sort and a binary search style question similar to finding a bad commit. One candidate was given a LeetCode-style medium problem but was not asked to write code. Explain your reasoning aloud and handle edge cases carefully.
Interviewers may ask you to explain past projects in detail. One candidate sketched a flow diagram and discussed resiliency and scale. Another reported design rounds on a multithreaded scheduler application and a trellis board implementation. Prepare specific design choices, alternatives, and trade-offs from your own work.
Reports differ on the final stage. One candidate had a full day of technical interviews with about nine interviewers, including a mostly behavioral manager round. Another had an in-office interview with two interviewers. Plan for stamina and expect some behavioral questions. The exact loop shape is not consistent across reports.
