Wiley software engineer candidates report very different loops: one describes practical debugging and Java/OOP conversations, another an online assessment, group discussion, bot interview and HR round with long gaps.
$128K
Avg. Base Comp
$175K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe Wiley's software engineer interviews differently, so prepare for more than one format. One candidate who received an offer described a practical, platform-focused technical round. Interviewers gave code samples from Wiley's system and asked the candidate to find and fix errors, and three engineers asked about OOP concepts and Java fundamentals. That candidate also had an HR screen, a conversation with the team manager, and a final round with a technical leader.
A second candidate, who did not receive an offer, described a more screening-heavy pipeline. It began with an online assessment on easy-to-medium fundamentals such as string traversal, basic bit manipulation and theoretical OOP. A group discussion followed, then a bot-conducted interview covering SQL normalization and some coding, and finally an HR interview. This candidate reported gaps of a month or more between rounds.
The practical takeaway is to prepare on two fronts. Practice reading unfamiliar code, spotting bugs and explaining your fixes. Be ready to explain Java and OOP principles in your own words rather than reciting syntax. Review SQL normalization and simple string problems for the assessment-style route. Candidates in both reports described the technical bar as fundamentals rather than hard algorithm puzzles.
Timing is hard to predict. One candidate said the process moved over a couple of weeks, and the other said it stretched across several weeks with long pauses, so stay ready and ask the recruiter about next steps. A separate principal-level candidate reported a longer loop with a take-home assignment, system-style questions and a demanding final round. That is a different level, so treat it as context for senior roles rather than the standard software engineer path.
Synthesized from 4 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 Wiley process.
I interviewed at Wiley for an internship position in 2024. The process started with an online assessment, which I completed before moving to the main interview stages. After that, I had an automated video interview where questions appeared on screen one after another with just thirty seconds to think before I needed to start recording my answer. That was honestly the most nerve-wracking part because there's no time to compose yourself between questions. One of the questions they asked was about my motivation to work, which seemed straightforward but I had to be concise given the time constraint. Following the automated round, I had a follow-up interview with HR. They asked about my background, what drew me to the role, and a few technical questions related to the job description. The whole experience lasted a few weeks from initial assessment to final interview. What surprised me most was how little time you get in the automated video round — it really tests whether you can think on your feet and articulate answers quickly.
Prep tip from this candidate
Practice answering behavioral and motivation questions in thirty-second bursts — the automated video round gives very little thinking time, so mock interviews with a timer will help you stay composed and articulate under pressure.
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 Wiley
Write a query to return whether each user's subscription date range overlaps with any other completed subscription
| Question | |
|---|---|
| Merge Sorted Lists | |
| User Experience Percentage | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Triplet Counting | |
| Google Maps Improvement | |
| Longest Increasing Subsequence | |
| Most Repetition | |
| Success Measurement | |
| Target Indices | |
| Median O(1) | |
| Binary Tree Validation | |
| Messenger Service Design | |
| Matrix Rotation | |
| Type I and II Errors | |
| Target Value Search | |
| Filling Supermarket Bag | |
| Slow SQL Query | |
| User Event Data Pipeline | |
| A/B Testing a Checkout Button Change | |
| Check Matching Parentheses | |
| Moving Window | |
| Inherited Model Evaluation | |
| 5th Largest Number | |
| Confidence Interval Explanation | |
| News Alert Latency | |
| Pathfinder in Maze | |
| Blob Indexing | |
| Impossibly Iterative Fibonacci |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. One began with an HR screening, while another began with an online assessment on data structures, algorithms and language concepts. Reported problems were easy to medium, including string traversal, basic bit manipulation and OOP theory, so the entry point may vary by team or hiring route.
One candidate who received an offer reports a conversation with the team manager about their background and why they left their last role. Another reports a group discussion that felt like a culture and communication check. Candidates may meet one or the other, so prepare a clear career story and practice speaking concisely in group settings.
One candidate reports being given code samples from Wiley's system and asked to find and fix errors. Three engineers also asked about OOP and Java fundamentals. Another candidate reports a bot-conducted interview covering SQL normalization and coding problems. Prepare to read existing code, explain your reasoning and review database design basics.
The candidate who received an offer reports a final round with a technical leader focused on long-term team fit. The candidate with no offer reports a final HR interview on fit and background. Expect the last conversation to be less about puzzles, and consider asking the recruiter what it will cover and when to expect a decision, since gaps between rounds were reported.
