I would caution people against spending an entire weekend on their "48 hour project". I completed the two day coding/quant project very successfully, achieving all the required objectives, and in fact identified several problems with their formulation of it (in school parlance, I "corrected the question"). Then they scheduled an interview. The job description was heavily focused on a certain technical field that I'm very good at - in fact it mentioned this field no less than three times - so I brought it up in the interview. At first they didn't know what I was talking about (didn't they look at their own job description?) Then they said they don't even do that at their firm because they don't think it works. Well then why was it in the job description three times? Then I received a generic rejection letter with no feedback. I guess they have some narrow expectation of candidates which is not reflected in their job description or their project, and which they don't realise themselves until well into the process. Just be aware that succeeding thoroughly at their project doesn't mean you're what they're looking for, the job description seems to have nothing to do with what they're looking for, they don't seem to know themselves what they're looking for. I just think they should have the interview before the 48 hour project to avoid wasting the time of so many people. And make the project 2-3 hours instead of 48. They don't seem to care much about the outcome of the project anyway. And write a JD that actually reflects what they're looking for instead of one that seems designed to make themselves look good.