4 ms·
I basically implemented join tables to keep track of reputation, along with a periodic reputation calculation algorithm that accounts for freshness and other fe
by biscottigelato 8y ago
I basically implemented join tables to keep track of reputation, along with a periodic reputation calculation algorithm that accounts for freshness and other feed prioritization metrics. Without knowing the words 'Joint Table' or 'Freshness'. This is one of the hundreds fo things I did. I can harp about marketing, conversion funnel. or UI/UX design. or Customer Validation and Lean Startup...
But all I ended up getting is 'Cool App'. But 'Your technical competency because you can't finish implement a working Trie in the 30 minutes that's left after you spent 15 minute talking about your cool project.'... So basically 99% weighting is on the algorithmic puzzles.
- padseeker 8y agoHow many interviews did you go on? All of your interviews went that way? I like to think I'm pretty clever, and I've been tripped up in interviews before. The content of an interview is based on usually one or two people. Sometimes they think they're smarter than everyone else, and ask obscure or difficult questions within a limited time frame. They are looking for people at least as knowledgable and clever as themselves, but have a tendency to overlook other skill sets. You built something yourself, you know how to make decisions. Those are valuable skills to have. I just don't want to see you get discouraged because of 1 or 2 interviews. I've been tripped up myself, I have a CS degree. There are some places where I've fallen short. Make notes from each interview, what you need to improve upon. However each interview is unique, you can't expect to learn lessons from one interview and get identical questions in the next. Don't get discouraged. I have faith in you. Seriously, there are a lot of pretentious people making decisions on what gets asked in an interview. Not succeeding is not necessarily a reflection on you and your skill set.