Workday SSE 6YOE Reject Q3 2025
- Experience
- 6 years
- Posted
- 12 Jan 2026
Summary
I interviewed for a Senior Software Engineer role at Workday and was rejected. The interview included behavioral questions, a coding challenge on parenthesis validation with a memory optimization follow-up, and an OOP-focused system design question for a document creator system.
How it went
R1
With HM.- Tell me about yourself
- What is the role that I'm looking forward? - Lead developer or manager?
- Tell me a complex project that you have worked on and what were the challenges faced
- Explain the platform project and your contribution towards it
- Hackerrank: Find if the string is valid or not - paranthesis validator. Follow-up question to understand if the input is super high, and the memory overflow happens that heap is full. How will you solve the problem?
R2
Coding round in hackerrank, he asked me to design a document creator system, maintain versions, retrive all the versions, update only on the latest versions, etc. It was focussed on OOP, and few questions about my decisions like ArrayList vs Hashmap vs linkedhashmap, how to return objects that can be immutable, how to avoid race conditions, etcQuestions asked (6)
- 01
Tell me about yourself
Behavioral
Standard 'Tell me about yourself' behavioral question.
- 02
Role Preference: Lead Developer or Manager
Behavioral
What is the role that I'm looking forward? - Lead developer or manager?
- 03
Complex Project and Challenges
Behavioral
Tell me a complex project that you have worked on and what were the challenges faced.
- 04
Platform Project Contribution
Behavioral
Explain the platform project and your contribution towards it.
- 05
Parenthesis Validator with Memory Optimization
Data Structures & Algorithms · Medium
Hackerrank: Find if the string is valid or not - paranthesis validator. Follow-up question to understand if the input is super high, and the memory overflow happens that heap is full. How will you solve the problem?
- 06
Document Creator System Design
System Design · Hard
Design a document creator system, maintain versions, retrieve all the versions, update only on the latest versions, etc. It was focused on OOP, and few questions about decisions like ArrayList vs Hashmap vs linkedhashmap, how to return objects that can be immutable, how to avoid race conditions, etc.