
Ansys software engineering internship reports describe a short HR call, then a technical round covering CS fundamentals and easy-to-medium coding, with friendly interviewers and questions about your projects.
$103K
Avg. Base Comp
$136K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The available Ansys software interview reports come from two internship candidates, so treat them as a picture of what has been asked rather than a fixed loop.
Both reports begin with a short HR call. One lasted about 15 minutes, felt conversational, and covered basic qualifications and interest in the role. The other, with an HR manager, covered past internships, why Ansys and availability. A technical conversation followed. One candidate faced three engineers for about 30 minutes each, with questions on Java polymorphism, synchronous versus asynchronous communication, merge sort and quicksort, merging two linked lists, and a tree problem. That candidate did not move forward. The other described a technical manager round of about an hour with two to four easy-to-medium LeetCode-style problems, a focus on time complexity, Python written live, and questions on data structures, SQL and resume projects tied to the job posting. That candidate received an offer and heard back in about a week.
Both candidates described the interviewers as friendly and patient, and both were asked about their own work: one about research projects and interests, the other about projects related to the posting. Practice medium-level problems on lists, trees and sorting, be able to explain why quicksort can degrade, review time complexity and basic SQL, and prepare to talk through your projects in detail. Get comfortable coding while thinking aloud. One candidate wrote live Python, and the other answered Java concept questions.
Synthesized from 6 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 Ansys process.
I had applied to Ansys before for a different role and made it to the panel round before getting rejected. So when I applied again for this Senior Applications Engineer position, the same recruiter recognized me and skipped the initial phone screening, instead asking a few qualifying questions over email. That was actually a nice touch—it meant I could jump straight to the substantive rounds.
The second round was an hour-long video call with the hiring manager and another senior technical expert. They covered my background and experience pretty thoroughly, mixed in some fundamentals questions about the domain, and asked behavioral questions around teamwork and collaboration. I felt solid about my answers and left that conversation fairly confident.
The final round was the heavier lift: a panel of four very senior managers, all with strong technical chops. I presented for about 40 minutes on my previous work and background, then faced a Q&A session from the panel. The questions ranged from basic domain knowledge to specifics about the work I'd presented, and then they got into critical thinking—asking what I saw as the most pressing issues that needed to be addressed immediately. One question that stuck with me was around whether you can randomly assign strains to a structure, or if they need to follow certain restrictions. It was the kind of question that tested both technical depth and how I reasoned through constraints. Overall, the process felt respectful and rigorous, and I thought the conversations went well, though ultimately it didn't result in an offer.
Prep tip from this candidate
Be ready to discuss domain-specific constraints and tradeoffs in detail—the panel will ask probing questions about your past work and expect you to articulate not just what you did, but the reasoning behind technical decisions. Also prepare a tight 40-minute presentation on a significant past project, because you'll likely need to present and defend it to senior technical leadership.
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 Ansys
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Raining in Seattle | |
| Merge Sorted Lists | |
| Random SQL Sample | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Top 3 Users | |
| Find Bigrams | |
| Find the Missing Number | |
| N-gram Dictionary | |
| Upsell Transactions | |
| Minimum Change | |
| Scrambled Tickets | |
| Longest Streak Users | |
| Payments Received | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Size of Joins | |
| Customer Orders | |
| String Shift | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Get Top N Frequent Words | |
| Employee Salaries (ETL Error) | |
| Last Transaction | |
| Duplicate Rows | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Both internship candidates describe a short opening call. One lasted about 15 minutes, felt conversational and covered basic qualifications and interest in the role. The other was with an HR manager and covered past internships, why Ansys and availability.
The two internship reports center here. One candidate met three engineers for about 30 minutes each, covering Java polymorphism, sync versus async communication, sorting, a linked list merge and a tree problem. Another had an hour with a technical manager: two to four easy-to-medium problems, time complexity, live Python, data structures and SQL.
Interviewers also asked about past work. One candidate discussed research projects and interests. The other was asked about projects tied to the job posting and familiarity with different programming languages. One candidate noted time at the end for their own questions, and both described the tone as friendly and patient.
The candidate who received an offer heard back in about a week. The other candidate did not move forward and was unsure whether a second round would have followed.