7 ms·

IMHO, this was not cheating. This is a phenomenon called success. If you are fortunate (?) to be around in the entrepreneurial world long enough, you will real

• afpx 4y ago
  The thing is, for 20+ years you didn’t have to study. Only within the last decade or so have things become so competitive. There’s been a fundamental shift in supply and demand.
• giantg2 4y ago
  "If you are fortunate (?) to be around in the entrepreneurial world long enough, you will realize that intelligence, hard work, good time management etc are not adequate." Not just as an entrepreneur. I have found that these traits don't guarantee a reward for ICs, or anyone really. I used to work hard. Now I just work hard enough. Pays the same either way.
  • hirvi74 4y ago
    What does IC stand for?
    • technofiend 4y ago
      Incentive Compensation. It's a fancy way of saying bonus.
  • Isamu 4y ago
    >Now I just work hard enough. My review from management actually got much better once I stopped knocking myself out working too hard and instead worked just enough. That was a pivotal moment for me. That and also learning how to manage your manager.
    • iboisvert 4y ago
      Would you be able to share some tips or sources on managing your manager? It sounds like a really valuable skill
      • silksowed 4y ago
        https://www.notion.so/Manage-your-manager-26a26b82bd824f97bf44de754d79a94f https://www.notion.so/Manage-your-manager-26a26b82bd824f97bf... found this link on HN a while back but never really put it into practice. could be useful could not
      • camjohnson26 4y ago
        I had a similar realization, but it’s not really about working hard vs. not working hard, it’s about knowing what’s important to your manager. Early in my career I would never say no to any task, and would give the time estimate I thought the manager wanted, and then work over time to get it done. Half the time the finished product had bugs, got delivered too late, or ended up not matching what the client wanted, so the “hard work” didn’t translate directly into success. Now I try to figure out what the client’s actual needs are and how to meet them as quickly and with as little work as possible, and when something is requiring overtime, I immediately stop working on it and communicate that it’s a bigger issue than expected, and either push the project, get additional engineers, or find a different way to solve the issue. I think programmers really enjoy solving problems and we never like to admit that something is more difficult than we expected because we feel like we failed, but actually that’s just an expected part of the job. Obviously this only works if you have a good manager who actually cares about results. Bad managers are easy to manipulate because you just optimize for whatever BS metric they’ve decided is important, but those jobs are soul crushing.
    • 4y ago
  • stevenjgarner 4y ago
    I agree that this is the common experience for those of us that never experience overwhelming "serendipity" (i.e. luck) - meaning no disrespect (or lack of gratitude for being so incredibly fortunate) - but for those few that do get shot out of a canon, it would appear that hard work (focused hours on task) makes all the difference on becoming industry dominant (Musk, Jobs, etc). When you get a tiger by the tail, you need to stay focused and not fall asleep.
• bricemo 4y ago
  I agree, this is definitely not cheating. This is interview preparation. When I prepared for my FAANG interviews I googled so many questions that I couldn’t find another blue link, they were all purple. I prepped for them all. The more you want the job, the more you prep
  • ctxc 4y ago
    Really nice way to put it!
  • Agamus 4y ago
    As the adage goes, success is all about luck. Oh, and hard work. And the harder you work, the luckier you get.
    • mjd 4y ago
      "Fortune favors the prepared mind" (Louis Pasteur)
    • fartcannon 4y ago
      Its just luck. What you worked hard at is also luck.
      • Agamus 4y ago
        I tend to think that fate and free will work like electricity and magnetism. I call the combined result 'destiny'.
  • codechicago277 4y ago
    The only mistake the OP made was in acting like they hadn’t seen the question before, but other than that everything was fine. These code screen questions are usually a basic gut check and the real evaluation comes later at the on-site. Honestly the interviewer did a bad job though because the question clearly gives an advantage to someone who has seen it before. Once I had a candidate struggle with my screening question, flattening an array of nested arrays, and that’s fine because I normally use that as an opportunity to see how they ask questions and work together on finding a solution. But the candidate went silent for about 5 minutes and then came back with a perfect solution, using iterators, which are a pretty obscure JavaScript feature. I later found that exact code block on the MDN site, and I was pretty shocked at how brazen an action it was, because if they had just asked for direction and admitted they were struggling they could have still passed the interview.
• wrnr 4y ago
  I once aced an interview after the recruiter handed me the list questions, all soft balls like "what is the difference between a promise and an observable". Naturally I googled every one of them and during the interview had to hold myself back as to not to totally dunk on the questions. Afterwards the recruiter called me back with the good news, I said it was almost unfair how easy it was, he just laugh and said that not everyone that gets the questions on a silver platter actually passes the interview.
• WillPostForFood 4y ago
  "Calling Eli was your serendipity" He didn't call Eli randomly, he called to research an interview. That's putting the work in. That the question was the same might have been serendipitous (especially if the question was one of many possibilities). And he didn't just call and get the question, he then put in the effort to research an answer.
• drewcoo 4y ago
  What was the point of the question? That would help determine whether or not this was cheating. Normally with things like this the interviewer claims to want to "see how you think." If some prepared rote answer passed this interview phase, at the very least, the interview failed to meet its stated goal. What's the difference between cheating and what's needed for your version of "success?" Can someone cheat their way to success? Or does seeing the answer key before the exam just mean being better prepared than the competition? If the fraud in your story hadn't been discovered, would that have been success?
  • stevenjgarner 4y ago
    > Can someone cheat their way to success? Yes people "cheat" their way to success. I hate it, but they do and we support it. From just a position of basic human integrity (forget about the law), Apple "cheated" by implementing the graphical user interface from Xerox Parc without adequate compensation. Then Microsoft "cheated" by implementing Apple's GUI as Windows. Then came the lawsuits. This happens again and again. I have experienced this personally - the USDA RUS broadband program had written rules where an ISP had to work with their regional office and not walk their application through the front door in Washington DC. Yet being the first to apply through the regional office resulted in significant delays over our competitor walking their application into USDA headquarters against procedure. They got the $20 million. We did not. Any attempt to object or litigate would only hurt us further. > If the fraud in your story hadn't been discovered, would that have been success? I do not consider the author talking with Eli to be fraud. There was no obligation of disclosure. For all we know the reason why Microsoft repeated this question with so many applicants may have been deliberate to see how many applicants would actually get the solution by asking around. After all, isn't that how all of us code?
  • indrora 4y ago
    These sorts of screener questions are at the level of "can you write a simple function and can you answer basic questions about it" A surprising number of candidates I've seen interviewed cannot do the following, my code screener question: "Write a function that, given a set of integers, determines the amplitude (difference between biggest and smallest) of the set." This is literally max(set) - min(set) in more words. I have seen countless people attempt this in different ways. My favorite was the guy that sorted the list and took the end values. The worst is when I ask the follow up question: "where might I use this function?" I almost never get the answer of where I stole the function from (matplotlib): "the size of a graph", instead usually getting an "I don't really know".
• pfhayes 4y ago
  The serendipitous knowledge of the question isn’t the cheating. The cheating is the deception in the interview that this is a question being encountered for the first time. It’s cheating because it’s the type of unethical behavior you wouldn’t want in a colleague: pretending that they are brilliantly generating insights on the spot that they have actually researched previously. I don’t think it’s an unforgivable sin, particularly for someone new to interviewing. But as a candidate, I’ve considered it appropriate to make it clear to my interviewer what my level of experience with the question was before diving in. And as an interviewer, I’ve always looked positively on candidates who have done the same
  • fsckboy 4y ago
    > it’s the type of unethical behavior you wouldn’t want in a colleague we're talking about Microsoft here, embrace, extend, extinguish, and all manner of other perfidy.I'd say he fit right, apart from his conscience.
• victor106 4y ago
  This is not cheating. Maybe I am being too cynical but I think the author knows this too but I think he wanted to frame it this way to get more attention and indirectly promote his company