You only have free questions left (including this one).
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:
public class LinkedListNode
{
public int Value { get; set; }
public LinkedListNode Next { get; set; }
public LinkedListNode(int value)
{
Value = value;
}
}
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:
the list has 0 elements
the list has 1 element
Does your method correctly handle those cases?
Start your free trial!
Log in or sign up with one click to get immediate access to free mock interview questions
Actually, we don't support password-based login. Never have. Just the OAuth methods above. Why?
It's easy and quick. No "reset password" flow. No password to forget.
It lets us avoid storing passwords that hackers could access and use to try to log into our users' email or bank accounts.
It makes it harder for one person to share a paid Interview Cake account with multiple people.
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.
Start your free trial!
Log in or sign up with one click to get immediate access to free mock interview questions
Actually, we don't support password-based login. Never have. Just the OAuth methods above. Why?
It's easy and quick. No "reset password" flow. No password to forget.
It lets us avoid storing passwords that hackers could access and use to try to log into our users' email or bank accounts.
It makes it harder for one person to share a paid Interview Cake account with multiple people.
“Interview Cake was the closest thing to having an actual interviewer on hand. Being able to simulate the type of back and forth you have an in interview was a huge help.
—
Adam