Plastipak Software Engineer candidates most often report a practical, resume-led process: an assessment or technical screen, technical discussion, and management or HR conversations. Expect stack-specific questions across Java, SQL, automation, frontend, or core programming.
$93K
Avg. Base Comp
$105K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Plastipak Packaging Software Engineer interviews are reported as practical and strongly shaped by the team’s stack. Some candidates encountered an aptitude or coding assessment before technical and HR conversations, while others described a technical interview followed by managerial and HR rounds. The available evidence does not establish one standard sequence, so confirm the expected format with the recruiter.
The technical content varies by role. Java-oriented candidates reported Stream API exercises, Spring Boot annotations, third-party API integration, SQL, AWS, Jenkins, Kubernetes, microservices, and deployment questions. Other interviews focused on .NET and practical SQL concepts such as DELETE versus TRUNCATE, partitioning, and indexes. A Salesforce-oriented candidate was asked to write a trigger from a scenario and explain exception handling in Apex Flows or Triggers. The recurring thread is applied explanation: be ready to write a short solution and then explain how it behaves in a realistic project or production situation.
Several reports describe detailed discussion of previous projects and the technologies listed on the résumé. Prepare concise examples covering your contribution, technical decisions, requirements, challenges, and error-handling choices. Management conversations may explore teamwork, leadership, conflict, decisions under pressure, and alignment with workplace goals. For general preparation, refresh basic programming, binary search, SQL, and the language or platform named in the job description, but give the most attention to hands-on use of your stated stack.
Synthesized from 21 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 Plastipak Packaging, Inc. process.
The most practical part of my virtual interview was being asked to write code that finds the second-highest number. The interview was fairly broad rather than focused on a single area. They covered software-testing concepts, exception handling, and SQL, including a join query. Because the role had an automation angle, they also asked how I would open a webpage and identify the XPath for a web table, along with questions about Selenium waits and REST APIs.
The discussion also touched on programming fundamentals and object-oriented concepts. There were questions around C# and OOP, and SQL remained an important part of the conversation. I was also asked to introduce myself and explain my responsibilities at my current company. The overall difficulty felt manageable, but the breadth was the main challenge: I had to move quickly between coding, database queries, web automation, API knowledge, and questions about my experience.
I was not selected after the interview. My main takeaway is to prepare for a practical, mixed technical screen rather than expecting only algorithm questions. Be ready to write a short program such as finding the second-highest value, construct SQL joins, explain exception handling, and discuss Selenium topics like XPath selection and wait strategies. If your version of the position is full stack, C#, LINQ, Angular, and OOP may also come up.
Prep tip from this candidate
Practice coding the second-highest-number problem and writing SQL join queries without assistance. Also review XPath for web tables, Selenium waits, REST APIs, exception handling, and—if the role is full stack—C#, LINQ, Angular, and OOP.
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 Plastipak Packaging, Inc.
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Bagging vs Boosting | |
| Hurdles In Data Projects | |
| Loan Model | |
| Production Rollout Challenges | |
| Your Strengths and Weaknesses | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Game Feature Home | |
| Employee Salaries | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Comments Histogram | |
| Random SQL Sample | |
| Like Tracker | |
| Weighted Keys | |
| Prime to N | |
| Upsell Transactions | |
| Largest Salary by Department | |
| Over-Budget Projects | |
| Top 3 Users | |
| Raining in Seattle | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report aptitude-style tests, online coding assessments, and initial screens before deeper interviews. Assessment content has included basic mathematics, pseudocode, and data-structure problems; this stage may vary by team.
Candidates report practical questions tied to Java, SQL, automation, frontend work, .NET, or core programming. Expect to explain a solution or technical concept and connect it to projects rather than relying only on definitions.
Candidates report follow-up discussions with managers, team members, or panels about prior projects, communication, teamwork, conflict, and how they approach workplace problems. Some processes also include a take-home assignment before a final panel.
Candidates report HR conversations covering salary expectations, benefits, policies, availability, and next steps. This may be a distinct final stage or combined with another conversation.
