Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,026 | Comments: 44,842

filter by tags archive

Interview challenges: Decompress that

time to read 1 min | 137 words

I’m always looking for additional challenges that I can ask people who interview at Hibernating Rhinos, and I run into an interesting challenge just now.

Implement a Decompress(Stream input, Stream output, byte[][] dictionary) routine for the following protocol:

Prefix byte – composed of the highest bit + 7 bits len

If the highest bit is not set, this is a uncompressed data, copy the next len from the input to the output.

If the highest bit is set, this is compressed data, the next byte will be the index in the dictionary, copy len bytes from that dictionary entry to the output.

After writing the code, the next question is going to be, what are the implication of this protocol? What is it going to be good for? What is it going to be bad for?



Interesting. Do you ask candidates to solve this whilst you are watching them, or do you allow them the freedom to solve the problems in their own comfortable environment with their preferred tools?

Jahmai Lay

@Jake I imagine it's something like this: http://y2u.be/rUY8HysBzsE

Oğuzhan Eren

http://en.wikipedia.org/wiki/Dictionary_coder ?

Pop Catalin

I think this kind of compression whould be good for Json and XML documents, and in a typical Json or XML document the members names are higly repeated and not too many (so 127 dictionary entries limit would be pretty good, also max size of 255 for an entry (256 if you modify the alghoritm to copy len+1 bytes) is prety good for this use case.

I think it gets a good tradeof between speed (very fast) and size (good for certain documents types)

Ayende Rahien

Jake, No, I usually let them either do that on a separate room with a development machine or they do it at home


Resembles my WBXML work i did for telco industry >8 years ago ;)

Comment preview

Comments have been closed on this topic.


No future posts left, oh my!


  1. Technical observations from my wife (3):
    13 Nov 2015 - Production issues
  2. Production postmortem (13):
    13 Nov 2015 - The case of the “it is slow on that machine (only)”
  3. Speaking (5):
    09 Nov 2015 - Community talk in Kiev, Ukraine–What does it take to be a good developer
  4. Find the bug (5):
    11 Sep 2015 - The concurrent memory buster
  5. Buffer allocation strategies (3):
    09 Sep 2015 - Bad usage patterns
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats