Four candidates describe Parsons Software Engineer interviews that range from casual phone or in-person conversations about projects and data structures to online or live coding exercises, starting from a career fair, a recruiter, or a manager.
$116K
Avg. Base Comp
$135K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Parsons Software Engineer interview as mostly friendly, but the four reports differ in format. One candidate recruited at a career fair talked through hash table operations, average versus worst-case complexity, and the two main ways hash tables are implemented in a casual courtyard conversation, with no whiteboard. Another had a phone-only technical discussion where the interviewer opened their GitHub and asked about architectural decisions and NLP techniques in a project. That candidate later received an internship offer and, after finishing a degree, a full-time conversion offer.
The other two reports show where candidates can stumble. One candidate completed a third-party online assessment with anagram, averaging and string-sorting problems. The recruiter said they had not followed the instructions, though the candidate was not told which ones. The other had a career-fair phone screen, then a live coding session in a Google Doc-style editor with Java questions (abstract classes versus interfaces) and TCP networking. That candidate felt rushed and declined an offer.
Prepare to explain your own projects and core data structures out loud. Practice Java fundamentals without an IDE, and read coding prompts for exact input and output requirements. With only four reports, expect the format to vary.
Synthesized from 5 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 Parsons Corporation 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 Parsons Corporation
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Over-Budget Projects | |
| Top 3 Users | |
| First Touch Attribution | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Hurdles In Data Projects | |
| Employee Project Budgets | |
| One Element Removed | |
| Level Of Rain Water In 2D Terrain | |
| Project Budget Error | |
| Sort Strings | |
| String Mapping | |
| Find Duplicate Numbers in a List | |
| Words in Encrypted String | |
| Target Indices | |
| Swiping App Design | |
| Priority Queue Using Linked List | |
| Slow SQL Query | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Merge N Sorted Lists | |
| Nightly Job | |
| KNN From Scratch | |
| Loan Model | |
| User Event Data Pipeline | |
| Swap Variables | |
| Seller Type Modeling | |
| Distributed Training Instability | |
| Subway Machine Learning Model | |
| The Longest Journey |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report getting started in different ways: a career-fair conversation, a recruiter phone call, or emails with a manager interested in their work. Early calls typically covered introductions, experience, and the positions available, and may include career-goal questions.
Two candidates describe a relaxed technical conversation with no coding. One discussed hash table operations, complexity trade-offs, and implementation approaches. Another walked through GitHub projects, including architecture choices and NLP techniques. Expect to explain your reasoning, not just recite definitions.
Some candidates report a coding step. One took an online assessment with simple string and averaging problems and was told they missed instructions. Another coded live in a Google Doc-style editor, answering Java and TCP questions. This step may not apply to every candidate.
Reported outcomes were mixed. One candidate received an offer email about two weeks after the conversation. Another got an internship offer, then a full-time conversion. One was not advanced after the online assessment, and one declined an offer. Timelines vary and no overall duration was reported.
