Yahoo Software Engineer candidates report background and cloud discussions alongside coding, cache-design, and arithmetic-expression problems.
$154K
Avg. Base Comp
$193K
Avg. Total Comp
Not reported
Typical Rounds
1-2 weeks
Process Length
Yahoo Software Engineer interview reports describe a mix of conversation about experience and hands-on technical evaluation. One candidate reported a hiring-manager discussion focused on their background, followed by a technical round that spent substantial time on cloud experience; the candidate’s AWS background was discussed alongside the team’s use of GCP. Be ready to explain what you built, the decisions you made, and how your cloud experience transfers across platforms.
The reported coding work is specific enough to guide practice. Candidates encountered arithmetic-expression evaluation with operator precedence, framed as a stack-based data structures and algorithms problem. Another report described designing a cache for high-throughput, concurrent requests and implementing a caching strategy in Java during the same one-hour first-round interview. Practice choosing and explaining data structures, clarifying edge cases, and turning a design into working code.
These accounts do not establish one fixed sequence or universal round count. Still, they point to a practical preparation focus: communicate your background clearly, work through stack-based parsing carefully, and articulate tradeoffs in a concurrent cache design. A separate candidate reported receiving a verbal offer after multiple rounds, so keep offer discussions distinct from interview preparation and seek clear written confirmation if you reach that stage.
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 Yahoo process.
One round — the tech round at Yahoo — and that was the whole story. Interviewer joined 15 minutes late, no apology, no context, just straight into questions like the clock hadn't moved. That set the tone. He seemed checked out the entire time — flat, distracted, like he was doing this between other things rather than actually evaluating me. The rough part: at one point he actively steered me toward a wrong approach on a problem. I went with his direction since he was, in theory, the expert in the room — and it predictably didn't land well. Hard to tell in the moment whether that was carelessness on his part or some kind of pressure test, but it didn't feel deliberate. It felt like he just wasn't paying attention. Rejected after. No real feedback, which stung more than the rejection itself — when the process feels that lopsided, you walk away with zero signal on whether it was you, him, or just bad luck on interviewer assignment. Confident going in on the fundamentals; the wobble came entirely from being nudged off course by someone who wasn't actually engaged enough to notice he'd done it.
Questions asked: The question: Evaluate an arithmetic expression given as a string — something like "3+5*2-8/4" — and return the computed result,
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 Yahoo
Find how many users logged in a certain number of times on a given day
| Question | |
|---|---|
| P-value to a Layman | |
| Type I and II Errors | |
| Annual Retention | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Top Three Salaries | |
| String Shift | |
| Top 3 Users | |
| Comments Histogram | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Largest Salary by Department | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| First Touch Attribution | |
| Job Recommendation | |
| Delivery Estimate Model | |
| Minimum Change | |
| Recurring Character | |
| Find Bigrams | |
| Scrambled Tickets | |
| Detecting ECG Tachycardia Runs | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported a hiring-manager conversation centered on background and experience. Candidates may be asked to connect recent work to the role, including how their cloud experience transfers when a team uses a different platform.
A candidate reported a coding round with an arithmetic-expression evaluation problem involving operator precedence. Prepare to explain your approach, ask about requirements and edge cases, and code a correct stack-based solution.
One first-round report combined system design with Java cache coding in a one-hour interview. The candidate was asked to design for high-throughput concurrent requests and implement a caching strategy; this may be a focused technical screen rather than a universal format.
