But it doesn't have to end here! Sign up for the 7-day coding interview crash course and you'll get a free Interview Cake problem every week.
You're in!
Hooray! It's opposite day. Linked lists go the opposite way today.
Write a method for reversing a linked list. Do it in place.
Your method will have one input: the head of the list.
Your method should return the new head of the list.
Here's a sample linked list node class:
We can do this in space. So don't make a new list; use the existing list nodes!
We can do this is in time.
Careful—even the right approach will fail if done in the wrong order.
Try drawing a picture of a small linked list and running your method by hand. Does it actually work?
The most obvious edge cases are:
Does your method correctly handle those cases?
Log in or sign up with one click to get immediate access to free mock interview questions
We'll never post on your wall or message your friends.
Actually, we don't support password-based login. Never have. Just the OAuth methods above. Why?
Log in or sign up with one click to get immediate access to free mock interview questions
We'll never post on your wall or message your friends.
Actually, we don't support password-based login. Never have. Just the OAuth methods above. Why?
time and space. We pass over the list only once, and maintain a constant number of variables in memory.
This in-place reversal destroys the input linked list. What if we wanted to keep a copy of the original linked list? Write a method for reversing a linked list out-of-place.
Log in or sign up with one click to get immediate access to free mock interview questions
We'll never post on your wall or message your friends.
Actually, we don't support password-based login. Never have. Just the OAuth methods above. Why?
Reset editor
Powered by qualified.io