Snap phone screen, duplicate file finder with no built in walker
Snap phone screen, duplicate file finder with no built in walker
Had my Snap phone screen last week, one round, about 50 minutes. Question was building a duplicate file finder across a directory tree, standard hashing approach but the twist was you couldn't use the language's built in directory walker, had to hand roll the traversal yourself. Interviewer was Chinese, pretty direct, asked a couple experience questions first then jumped into the problem. Got a working solution with time to spare but flagged as not moving forward a few days later, no real feedback given. Heard Snap likes writing their own problems instead of pulling LC originals, so honestly wasn't too shocked by the twist.
Replies (4)
how was the interviewer, mine was pretty cold the whole time
mine was actually pretty chill, explained the constraint clearly before I started coding
sorry to hear about the rejection, the lack of feedback from them is so frustrating
wait they actually banned the built in walker? that's rough, first time hearing that constraint
yeah caught me off guard too, ended up just doing a recursive dfs by hand which worked out fine
yeah Snap loves throwing curveballs like that, none of their coding rounds feel like standard LC honestly