That's a heck of an interview question. I like what he was tempted to write better. I really don't want engineers toiling for hours over something a language or framework already provides.
I get the purpose, of course, but geez.
I get the purpose, of course, but geez.
But an entire JSON parser? That's nuts!
Maybe it makes sense if you assume the input has already been tokenized so you are not expected to deal with the minutiae of string literal escape sequences and such and can focus on the high level design/flow...