1. on campus interview: two technical questions: a) write a function to calculate fibonacci(n). b) given a set of 2-D points, find the maximum number collinear points. - a) is straight-forward. I struggled a bit on b), and had it done eventually with several hints. 2. 48-hour code challenge: write a web crawler to retrieve search results from a given url. - The decision was made fast (3 days after submission), although no feedback on the implementation is given. 3. phone interview (behavioral): In addition to normal questions, such as Why BrightEdge?, emphasis was on how I feel about long working hours. The same question was asked in several different ways. 4. on-site interview: two tech interview in the morning, about database and some stack/tree related question, not difficult at all. had lunch in company (free friday lunch for all employees, but few engineers show up or mingle with interviewees, which is surprising for a startup). A large programming task was introduced after lunch. The task is similar to the 48-hour challenge: Building general page fetcher and parser to obtain some information from several given web pages. Some java / database connector would help. The offer was extended with in a few days after the on-site interview.

basic question with some take-home assignment, overall not too difficult but takes some time to review it and the interview is some basic question for python and ask a lot from resume.