Question Details
Problem Design a PermanentStack class that behaves like a standard stack but never truly destroys data. When you pop() an element, it is moved to an internal "archive" rather than discarded. All previously popped elements must remain retrievable. Example: Follow-ups What if restore() must reinstate elements in LIFO order from the archive? How would you implement undo_all() to move every archived element back in original push order? What are the time and space complexities of each operation? How…
Full Details
🔒
Unlock all Affirm questions
Full insider details, leaked discussions, and candidate experiences.
Get full access — $100 a year, unlimited accessAbout This Question
This is a reported interview question from a affirm interview during the phone round.
It covers the following topics: Coding, Ood, Onsite, Phone, Stack .
More Affirm Interview Questions
1p3a
affirm fulltime software engineer tech phone screen interview overview
InterviewDB
Card Game - OOD Deck, Hand, and Turn-Based Game Engine
1p3a
Affirm Full-Time Tech Phone Screen Interview Experience
InterviewDB
Decision Tree - Implement Predict Traversal for a Binary Classification Tree
InterviewDB
Dispute Status - State Machine for Payment Dispute Lifecycle