Not too surprising when you consider there isn't really a standardized guideline and every interviewer asks questions of varying difficulty. Sometimes interviewers don't even ask candidates the same question and tailor them based on the candidate's resume and experiences. I've had interviews as simple as writing a function that outputs if two strings are anagrams, and other interviews that test dynamic programming knowledge and other interviews that tested my knowledge of concurrency. At the end of the day, its luck of the draw which interviewer you get and what questions he decides to ask you.
Maybe doctors should hire someone to help with the paperwork?
This seems like a case where scaling horizontally works better than scaling vertically. Like how some tech companies make use of QA departments while others do their own QAs, perhaps some doctors having an assistant on hand could make things more efficient.
This is true, but as others stated an over-simplification of Twitter's features. Even without the factor of scale, building Twitter for 1000 users would be hard when you consider things like private messages, e-mail notifications, on-site notifications, hash tags, retweets, favoriting, follower-lists, url shorteners, images / videos, ads, analytics, search, security, new features like their 'moments' tab, - and considering how all of these features work together on mobile as well as web. THEN start thinking about scale and how these features work together - not just the C and R of CRUD, but the U and D too.
"Yet this OP disproved this. So I don't get what the point is."
From the blog:
"David and I are living proof that if we can upgrade and improve the way we think, and overcome our mindset inequality, then maybe we can help others do the same"
Yes the blog clearly states that its not impossible, the OP is simply sharing how he overcame hurdles despite the challenges he faced being poor. It's meant to help others do the same and share insight.
Interesting that they have enough data, since I doubt even 1000 companies have gone through YC and counting the few hundred that have, probably only a small fraction of them have exited or died.
I think what people keep forgetting here is that you are comparing all start-ups to the Googles and Facebooks of the world. There are MANY promising start ups up there, it really depends on what your definition of a start up is. Number of employees? Publicly traded? Years since it was founded? Sure, working at Google/Facebook is probably better than working at Evernote. But is it better than working at Snapchat or Lyft?
I agree that its wrong to be giving pay raises / promotions to employees solely based on who worked longer hours. Obviously, pay and promotion should be judged on the value delivered not the effort put in. However, in my opinion, great developers who build robust systems and leave at 5 are not necessarily hard working, probably just more experienced / competent. If you can get your job done by 5 while your co-workers are slaving away until midnight fixing bugs, whats stopping you from putting in another couple extra hours to deliver even more value to the company? Sometimes taking initiative and showing passion is just as important as being smart.
The point of joining a start-up is to take risk and make more $. I'm not sure there is anyone who doesn't get that. Obviously joining a large stable company with consistent growth will net you high stable pay, the point is if you want to make an above average amount of money that moves the needle and makes your life feel different, a start-up is the way to go.
Surprised that people are finding this unusual, in web/mobile anyways. In my experience most engineers do some level of QA themselves, particularly in start-ups < 1000 people. In what ways does an engineer being their own QA negatively impact the company?
lol - so which features are you going to exclude? Is your weekend-twitter-app going to support a feed, favoriting / reteweeting only to your followers / dming only between followers / ability to block / filter / rate-limit users who tweet-spam / mobile app / push notifications / e-mails to new users who sign-up / and various other necessary features an app usually has before it even launches a MVP?
Why doesn't AirB&B work to reduce prices? Once it becomes less profitable for people to sublet their places for the sake of making it money, maybe people will see it as less of an evil. There are far too many hacker hotels in SF on AirB&B charging ridiculous rates, jamming up to 20 people into a single condo stacked with bunk beds.
Hmm, lets see I would guess they at the very minimum have a:
-Web team
-Mobile team
-Data team
-Infrastructure team
-Tools team
So assuming at least 5 people per team thats already 25 people ... why is it so hard to understand that building anything at scale involves lots of man power?
Thank you. For all this talk about Amazon being a 'data-driven' company, I have yet to see any data on their employee churn rates from the people defending Amazon. I wonder why we don't hear about these types of horror stories from other companies?
Fresh graduates are often better at programming / algorithm interviews than older experienced programmers who have been out of the interviewing game for a while. It's actually pretty important to know which demographic of users this data applies to.
The most stressful part is preparing for anywhere from 10-20 technical interviews during midterms. There is nothing worst than knowing you have to balance your University degree with future Job prospects. I'm glad I had to go through it because there is no way I would be ready for it in the real world otherwise. Technical interviews are tough and all of the best companies do them. The rewards however, are a blessing indeed:
Love how every time a post concerning interviews pops-up on hackernews everyone gets defensive. Like all things I think the nature of the interview should reflect the role the developer will have when hired. If the developer won't be in charge of developing an entirely new system or project on his own it seems overarching to ask this type of question. At the end of the day the core attributes that matter are intelligence, ability to learn, experience and motivation. In this case, this question really only tests experience.
People forget there's a distinction between Computer Scientist / Data Scientist / Software Engineer. They are not one and the same, and depending on your job you may only need to be one of those three categories. You don't need to know how quick-sort works create a CRUD web application, but you sure need to know how to write clear, maintainable code in all areas from the stack. But if that's all you know you can't expect to excel at a job like generating the Facebook news feed which actually involves theoretical knowledge.
I think its important to match interview style with the company. If you're a very theoretical data-oriented / machine learning company then knowing algorithms and computer science is very important so traditional coding tests are probably pretty important. On the other hand, there are times when all you need is a capable Software Engineer with experience and knowledge of a particular tech stack. In that case, whether or not he paid attention in algorithms is not going to give you a great indication of whether he can work full stack.