Open Source Your Knowledge, Become a Contributor
Technology knowledge has to be shared and made accessible for free. Join the movement.
Common Coding Interview Questions: Palindromes
Palindromes are a common topic for interview questions as they lend themselves to algorithmically interesting solutions.
In this article we will go through several interview questions related to palindromes.
Verifying a palindrome
A string of letters is a palindrome if it is identical to it's reversion. However we don't need to reverse the string to verify this is true.
Using two iterators, we can simply walk over the string from the start and end, verifying each pair of corresponding letters. Keep in mind that both "aba" and "aa" are palindromes (which is a corner case we don't have to deal when using iterators).
For palindromic sentences we need to include aditional checks. For example: "Was it a car or a cat I saw?" is a palindromic sentence, but our
is_palindrome function will return false, since the string does not exactly match its reversion.
In either case, we visit each character in the string once, leading to time complexity. We only store two iterators, leading to time complexity.
Searching for palindromes
Most palindrome related interview questions involve searching for palindromes within a given string. This can be finding the longest palindrome, splitting a string into palindromes, or simply returning all the palindromes contained within a string.
Brute force solution
To find all the palindromes within a string we can use the same process we used for verifying a palindrome, but instead of starting from the outside we start from the center. Again, we need to keep in mind that a center of palindrome can be either one or two characters.
We can extend the code to return all palindromes by simply emmiting each palindrome when its encountered in the
grow lambda is time complexity, since we invoke it for each position in the string (potentially twice) we end up with time complexity.
Space complexity is since the only thing we are storing are the maximum palindrome length and its boundaries.
The solution - Manacher's algorithm
Let's look at our brute force solution: What is the extra work that we are doing? Well, we keep re-checking the same characters multiple times, since we start the growth of the palindrome from each potential center. Can we exploit the properties of palindromes in some way?
Let's consider a string
yabacabax. If we just determined that the palindrome with the center
c is length
7, can we use this information for the following potential centers? Indeed, for this particular case, we can simply re-use the information from the mirrored section, since the palindromes with centers in
a are all fully contained within the bigger palindrome at center
In actuality there are 3 situations we can run into:
- the palindrome at the mirrored position is fully contained within the bigger palindrome
- the palindrome at the mirrored position extendeds past the left border of the bigger palindrome
- the palindrome at the mirrored position is a prefix of the bigger palindrome (ends at the left border of the bigger palindrome)
For case 1, we can simply copy the information, since the palindrome is fully contained, its mirror will be also fully contained.
For case 2, let's consider an example.
xabaxcxabay, the palindrome at center
abaxcxaba. What can we say about the palindrome at center
b? Well, it's mirrored palindrome extends beyond the left side of the bigger palindrome. Is it possible that it extends past the right side of the palindrome? It isn't possible. If the palindrome at center
b extended past the right side of the palindrome, the entire string would have to be
xabaxcxabax. But that is in conflict with palindrome at center
For case 3, this is the only case where we can't determine the length of the palindrome from the mirrored section. We at least know that the part fully contianed within the greater palindrome is already a palindrome, so we can continue checking just after the greater palindrome.
We still need to deal with one small problem. This algorithm relies on having a center of a palindrome be a single character. Fortnuatelly we can simply pad the string with special characters, in which case if the center of the string is inbetween two characters, it will now be on the special character.
Since we calculate maximum palindrome at each center this way, the algorithm can be used as basis for solutions that require more than just the maximum palindrome.
All the iterators in our solution are monotonically increasing, leading to time complexity. Since we store the lengths of iterators at each center, this solution has space complexity.
Interview questions regarding generating palindromes are quite diverse, however most of them boil down to some form of edits.
For example: "Given a string, determine the minimum number of inserts to turn the string into a palindrome."
Dynamic programming solution
Let's consider when we need to make an insertion. If we start from the outside of the string, we only need to insert new character when we find a mismatch. However, then we need to be careful, the minimal number of insertions can be reached by inserting on either side of the string.
We can express this as a recursive relationship. Given a substring, spanning from index to index we can have two situations:
- the characters at indexes and match, the number of required inserts is the same as for the substring spanning from to .
- the characters at indexes and do not match, we need to make an edit. The number of required inserts is therefore .
We can build this recursion bottom up, using dynamic programming. Single characters are palindromes, so they require zero edits. Two character sequences either require 0 (if the characters match), or 1 edit. Building up from there, we simply iterate over all the lengths of substrings and every starting position, using our recursive formula to determine the minimum number of edits.
The two main loops are in the order of N each, leading to time complexity. This particular implementation also has (this can be optimized down to ).
Previous: data structure
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Šimon Tóth 2020 (email@example.com)