Interview Frustrations

&gt;A company that will remain nameless (unless someone convinces me otherwise)<p>I&#x27;ll give it a shot. They&#x27;re going to keep doing it because they keep getting away with it. You&#x27;ve tied this to (I&#x27;m assuming) your real identity, so that makes it a little more difficult to call them out because they can respond. But if you don&#x27;t let us know, we can&#x27;t know to avoid them. Even avoiding spending time getting to a final round, only to be asked to do this, would be helpful.<p>They got you to work for free. They probably didn&#x27;t benefit directly unless you gave them new ideas they didn&#x27;t know about before, but you still put the time in. It was work to you. And they obviously didn&#x27;t respect it at all, much less take the time to read your resume. Maybe they weren&#x27;t even interested in hiring you?<p>The only saving grace for that could be an exceptional position with great responsibility and great pay. But even if that&#x27;s true, they flippantly sent you through interviews for that position, so they&#x27;re likely a bad company from the inside. They only way they would face consequences is if they&#x27;re named.

Companies these days expend way too much energy interviewing people, and people then fail to prepare for the interviews or communicate internally afterwards. When I went for interviews I hated it when people did not even read my resume and sometimes did not even know what position it was for. Companies demand so many interviews from their existing people that they become jaded and no longer care.<p>I once went for an interview as a contractor and they scheduled 8 consecutive interviews in a row. Half never showed up, or asked the same lame questions. Also what they were looking for was actually different than what they had told me, so I flew to another city (they paid) for nothing. I didn&#x27;t get (or want) the job.<p>Good thing too, a month later the entire division was shut down.

I did some interviewing last year. I&#x27;ve been in my current position for about 5 years; I enjoy it, but was looking to see what else was out there. After going through about 5 interviews I decided to call it quits. The entire process of tweaking resumes, writing cover letters, and applying eats up your post-work hours. Once you get a call back, preparing for the different interview stages will take up the rest of your nights, or weekends if you are assigned a work project. Working from home makes it easy to schedule calls during lunch hours, but that just makes your regular work day more stressful.<p>After my fifth interview I decided to take a break. It was a good experience for me; I was incredibly rusty during my first few interviews, but gained a lot of confidence by my last one. Overall though it was incredibly stressful. This authors experience sounded terrible, but not at all surprising. I think job hunting while out of work would be stressful for other reasons, but being able to commit your full attention to searching and preparing would be advantageous in my opinion.

My main takeaway from this article is that the author wasn&#x27;t necessarily frustrated with spending 12 hours to prepare a 1-hour long presentation - though this does seem like a big ask - but was more frustrated that they didn&#x27;t even get the opportunity to present it because the company was<p>&gt; looking for someone with a few years of experience working with a specific technology I had never used. But… they knew that from my resume. And from my first interview. And from my second interview. And when they told me that I needed to prep a talk.<p>Shouldn&#x27;t the company have seen this deal breaker before the interview process started? Or at least after the first interview or two? Acknowledging that the author wasn&#x27;t the right fit would have saved both the company and the candidate the time and effort of going through an interview process that the company should have known wouldn&#x27;t yield an offer.<p>I&#x27;m not sure if this is common practice, but I&#x27;ve encountered something similar, going through multiple rounds of interviews over many hours only to have the recruiter tell me that &quot;based on your resume, you don&#x27;t have the skills we&#x27;re looking for in a candidate for this position&quot;. Why waster my time, and yours, going through the interview process then?<p>I don&#x27;t think any of these rationales are very satisfying, but here are some possibilities: 1) The company didn&#x27;t know what it was looking for when it started the process and came to a different understanding of the job requirements as the candidate moved deeper in the process. 2) The company is covering up the real reason they didn&#x27;t want to move forward and &quot;lack of relevant skill&quot; is an easy excuse. 3) The company&#x27;s recruiting process is immature&#x2F;messy&#x2F;sloppy&#x2F;ineffective and they literally missed the lack of required skills until the very end. 4) The position had to be filled and the company wanted to maintain a backup candidate in case their first choice didn&#x27;t work out.<p>I&#x27;d love to hear from those with experience on the recruiting&#x2F;hiring manager side to see whether any of these reasons ring true or if something else might be at play.

I don&#x27;t think anyone would disagree with the statement that hiring is terribly, atrociously, and disastrously broken. It&#x27;s been talked about ad nauseum. But I don&#x27;t think I&#x27;ve ever seen (nor do I personally have) any practical solutions to improve it.<p>Hiring is a two-way hard problem. On the company&#x27;s side, they have conflicting interests where they want to hire someone as quickly and cheaply (cheap as in not spending hundreds of man hours interviewing just to fill a role), but also want to do due diligence so that they hire the right person. On the candidate&#x27;s side, they also have conflicting interests where they just want a job and don&#x27;t want to spend multiple entire days doing interviews, but they also need to do their due diligence to make sure the job is actually something they want.<p>This almost necessitates spending a decent chunk of time with each other, but not too much. The balance that most big tech company&#x27;s seem to go with is 6-7 hours total in interviews for each candidate (and then ~10+ additional hours for both the candidate and the company doing preparation&#x2F;debriefs). I really don&#x27;t know why or how this was the number arrived at, though. From my perspective as a candidate, even after 6-7 hours of interviews I often come away still knowing very little about <i>what the job actually is</i>. And from my perspective as an interviewer, I know that requiring so much time from internal employees serving as interviewers is draining and stressful. It seems like it ultimately comes out to a lose-lose, but for some reason it&#x27;s still what big tech sticks with.

A few years back an SF startup asked me to prepare a presentation as part of the final round of interviews. It was supposed to be something I like to do. I chose making pizza on my charcoal grill using my KettlePizza [0]. At the time, our family tradition was to make homemade pizza on Friday nights so it wasn&#x27;t much of an imposition to snap a few photos during the process and slap it together into a Powerpoint.<p>Overall the presentation portion was a decent experience. I presented for 10-15 minutes and the folks in the room asked questions for about that long.<p>I didn&#x27;t get an offer because of &quot;concerns around culture &amp; team fit.&quot; I&#x27;m pretty sure that wasn&#x27;t a result of my presentation, but, rather, that I indicated I didn&#x27;t care much for death marches (and they were clearly on one at the time).<p>Had I put 10 hours into the presentation like Op I would have been annoyed. But an hour wasn&#x27;t bad. Altogether, I think it&#x27;s not a bad way to facilitate conversation and allow a broader group of folks to participate.<p>[0] <a href="https:&#x2F;&#x2F;www.kettlepizza.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.kettlepizza.com&#x2F;</a>

Sure, the presentation requirement is worth discussion, but what about the appalling tone of the email itself? It&#x27;s a laundry list of ways they hold you in contempt.<p>Prepare for interruptions. Manage your time wisely. Prepare perfectly and be perfect.<p>I&#x27;ll never be able to reconcile this industry&#x27;s complaints about engineer shortages with the way so many companies talk to us like we&#x27;re shit on their shoes.

Adjacent Idea Suggestion:<p>We should record job interviews.<p>Then both sides can review at their leisure.<p>Maybe then we can start improving.<p>--<p>Origin of Idea:<p>I ran for office. Lots of endorsement interviews. It&#x27;s just as bad as you&#x27;d expect. Comparable to our industry&#x27;s hazing rituals.<p>The better interviews were recorded. The best were shown on TV, available online.<p>Somehow everyone&#x27;s better behaved when there&#x27;s witnesses. (I quickly learned to make and release my own recordings of endorsement interviews.)<p>--<p>We should practice interviewing. Just like public speaking, stump speeches, etc.<p>Ages ago, I worked at a place that took recruiting and interviewing seriously. We had agendas, checklists, scripts, surveys. We practiced on each other, switching roles. We did all hand&#x27;s debrief after each candidate.<p>We treated our interviews as seriously as our usability labs.<p>Though we mocked the term at the time, I miss &quot;learning organizations&quot;. When some of us at least tried to get better.<p>Okay, rant over.

A few years back I did a phone screen with an org that seemed interested in me; the phone screen went really well so they asked for an onsite. But they warned me that they wanted to take advantage of having me onsite, so the onsite would last all day. Ok, I thought, fair enough. I took a day off of my then-current job and showed up at 9 AM and spent the next 6 or so hours interviewing with various people (nobody ever thought to ask if I&#x27;d eaten lunch, which I didn&#x27;t that day). The recruiter said it went well, but a few weeks later told me that there were some other people who wanted to talk to me in person. So they wanted another all-day on site. At that point, I figured I had already sunk so much time into this interview that I might as well go ahead and do it and - surely! - they wouldn&#x27;t invite me back for a second all-day onsite interview if they weren&#x27;t nearly positive they wanted to hire me by that point.<p>I was wrong. After another all-day onsite (this time I had the foresight to bring some snacks because, again, there was no break for lunch although I spent quite a bit of time sitting by myself waiting for interviewers to show up), I never heard back from them again.

I guess the moral is only spend time and effort on stuff that can be reused for multiple job candidacies, like a resume, website, or side project.

This happened to me as well. A recruiter told me that I had done very well in the PS, and would move me forward to the virtual onsite. I prepared for a week, including a whole weekend. Then I received a call from the recruiter telling me that the team that wanted me to interview changed their product direction, and would not move forward with me anymore. I was pretty upset, I just said thank you for letting me know since I did not know and do not know what else I could say. It was a totally waste of my time. I was actually pretty busy in that week, I could have done something else over that weekend. I guess this is how life goes.

Feels like we constantly talk about how interviews suck, but we kind of all know why.<p>1. It&#x27;s tough to fire people (in that, if you ask someone to move and it turns out they aren&#x27;t a good fit, it&#x27;s kind of a jerk move to then drop them like a hot potato).<p>2. Performance indicators are tough. How do you know someone is doing bad vs good?<p>3. Keeping on a bad hire (especially one you can&#x27;t identify), is damaging as heck. Best case scenario they don&#x27;t get much work done, worst case scenario they suck away the time of all your good hires through bad decisions.<p>So while I agree that interviewing sucks, I&#x27;ve come to terms with why it is so bad.

The only company I encountered recently who wanted me to give a presentation when applying for a software engineering job was Snowflake. I guess asking everyone to jump through that hoop is one way of cutting down on the number of candidates.

I remember a fintech here at my country contacted me for a possition and they asked me to perform a technical assessment which I diligently executed even since I though that the technical things they were trying to test could be easily asked during an interview, and that it going to cost me some money because they were asking me to use an AWS account, anyways. After finishing the technical thing, I sent an email to notify and proceed with the process, after that they were so difficult to provide availability for the next interview, they wanted a single time which I told them I wasn&#x27;t able to meet at that time because I was working on that time so they took more days and I ended up loosing 20 bucks and so frustrated because they didn&#x27;t provide the actual time to proceed with the process, I told the recruiter that if they don&#x27;t have enough time to get more people with their team then maybe they don&#x27;t have enough time to actually spend on different things than working. Anyhow, I just wanted to rant that.

Good riddance, if they don&#x27;t respect your time probably it is not a company to sink some portion of your life into it. Unfortunately people on the other side of hiring process have less respect for the candidates. Somehow they feel more powerful than the interviewee and forgetting that they were and will be on the other side one day.

Years ago, after doing well on regular interviews, I was once asked to do a presentation like this and I withdrew instead. For a regular interview, both candidate and employer give equal time. But for take home assignments, the employer is not putting in an equal amount. They&#x27;re asking for more commitment than they&#x27;re willing to put in (sometimes significantly so).<p>Maybe fixing the technical interview process starts with the highly qualified candidates decisively saying no to these things. I understand that not everyone is in a position to do this, but those who are should just say no and maybe it will help fix things (the takehome assignment fad and other brokenness).

They just have a organizing issues, its normal to give a presentation for a high level competitive job, but they should have gone through with it regardless if they found a better candidate. They don&#x27;t know how to make a situation a win&#x2F;win.<p>At the end of the day you never know what you&#x27;re getting from an interview, some great candidates turn into duds and vice versa. It&#x27;s amazing how many people in hiring positions are just really shit at judging character, instead they rely on some bullshit metrics and process to fill in their lack of intuition.

Never really had to deal with interviews as been lucky all my career but recently looking for new work I&#x27;ve had to do a few, it&#x27;s extremely frustrating.<p>The last one I went through 3-4 hours worth of remote interviews.<p>In the first interview I made it clear I&#x27;m in no rush to move, I get payed well, they contacted me, i&#x27;m only listening as looking for new interesting work. They where a bit fuzzy about the role&#x2F;salary saying they are looking for smart people then decide the role for the person etc etc so I said in order not to waste both our time this is my current salary, I&#x27;ll happily move for that if it sounds interesting, not interested in less, can&#x27;t afford to live on less.<p>I get to the end of the interviews, recruiter: so where do you want to start negotiation on your salary, then announces a value 30% less than what I am now. After me replying &quot;you want me to take a 30% pay cut, a substantial risk moving job with no reward from the risk and leaving me worse off, I can&#x27;t accept that&quot;, I haven&#x27;t heard back since.<p>The annoying part is I mentioned several times, if they want me to do more interviews I don&#x27;t want to get to the end to find out salary range is not in the same ballpark as don&#x27;t want to do remote skype calls after working all day for nothing. I was assured yes it&#x27;s fine multiple times. The only thing I can think off is they thought I was bluffing on the salary so thought I&#x27;d go for the low ball.

The company might not have considered their request a burden (though it was -- company&#x27;s mistake and author is right to be upset). Here&#x27;s an example where that could be true:<p>My gf has a PhD in $FIELD. She always has to give a &#x27;job talk&#x27; for every job (since I&#x27;ve known her that&#x27;s been all of FAANG plus some non-early-stage startups -- so most of the gamut). The talk isn&#x27;t that different from the post doc job talk or faculty job talk, except the content is a bit more industry focused. Of course this is a function of the kinds of jobs she looks for. Every time she&#x27;s decided to change jobs she worked on her job talk first (as Jessime had done for her talks as well). And to have the audience be more than just the engineering side is consistent with that. So the hiring team may have just assumed this was a &quot;job talk&quot; position, and assumed that the candidate would already have it ready to go.<p>Clearly the company was quite wrong, and that lead to an unreasonable burden on the candidate. It&#x27;s a good reason to avoid the company: if they can&#x27;t get the first impression right, well, perhaps the first impression is actually accurate as to how everything else in the company is run.<p>Again, I&#x27;m not trying to defend this unknown company in the slightest, just trying to imagine how this kind of thing could happen. Sounds like Jessime dodged a bullet, job-wise.

To be fair, whatever time you prepare for this specific company is useful preparation for your current job search cycle anyways.<p>My job search cycle is once every 2-4 years. Within each cycle, I&#x27;ve always found my later interviews go much smoother than the early ones, due to incremental preparations adding up to much smoother execution.<p>The first new interviews are always rough, after a long hiatus. I generally look at those as warm-up interviews...<p>So it&#x27;s not necessarily a net-zero reward, for the story portrayed by the author.

a presentation about your projects you&#x27;ve worked on? hmmm, when I interview someone about their projects its pretty much a conversation where there is no set plan. Quite often you end up swapping what projects you talk about based on questions asked. I find freeform pretty effective to get to the interesting things.

I&#x27;m building something to help for this on the hiring manager side! I think that all hiring software is focused on the recruiting funnel side of things rather than optimizing the actual interview&#x2F;panel interview process to ensure fair data collection and execution overall.<p>After having done a lot of hiring interviews (100s) over the years, I can say that my own methodologies have improved substantially in terms of asking the right questions and being as objective as possible, but ultimately 1) members of my panel might not have that many experiences to hone their skills and 2) the data capture and evaluation process is a &quot;clunky spreadsheet&quot; exercise at best.<p>EDIT: The book &quot;Who: The A Method for Hiring&quot; is a great resource for this.

This is an interesting post in that it’s complaint is totally different than the usual gripes we see about interviewing on HN.<p>I totally expected to see complaints about DS+A style questions, some discussion about how leetcode is useless for actual job performance etc. When people who make those complaints are pressed for alternative interview styles, a common response is to suggest a presentation very similar to the one described in the OP.<p>I’m somewhat skeptical that this style of interviewing is any better than the standard leetcode method, but I’m interested in hearing if there people who have the opposite view. Would anyone prefer an hour long presentation over an hour long algo heavy white boarding session?

I have the good fortune of working remotely in a country much cheaper than the USA, so I can afford to be selective about what I&#x27;m willing to do during a hiring process. For starters, I haven&#x27;t had to do an unpaid take home assessment in a while, so I would reject outright a request like the one in TFA, but I&#x27;m aware that many are not in my position.<p>This type of expectation of free work during the process needs to change. Maybe if enough people reject stuff like this, it will, but again, many can&#x27;t afford not to jump through all the hoops the company decides to put in place. It&#x27;s a tricky problem, to say the least.

&gt; That’s fair, I suppose. They were looking for someone with a few years of experience working with a specific technology I had never used. But… they knew that from my resume<p>We all know very well that the company had a few other candidates in the pipeline that were more qualified, and they were simply covering their butt with a &quot;less qualified but still maybe good candidate&quot; while they were extending an offer to the candidate they really wanted in case they turned it down.<p>I would do the same thing as a job seeker. Interview with a company even though I&#x27;m waiting for an offer from a more desirable organization.

I&#x27;ve seen this pattern at least 3-5 times recently, at either the beginning or end of the series. The dirtiest one imo, is letting someone get to the 3rd or later interview with nothing more than &quot;thanks ttyl&quot; when they say no or cancel. It burns me out. Most recently it was a series of 6 interviews across 3 stages. Only after I responded to their automated rejection by emailing each of them personally, asking for feedback, did I get anything.

The moment I read &quot;show us how enthusiastic you are&quot; I always suspect a trap.<p>Motivation, drive, and enthusiasm, are important. Not doubting that.<p>But experience teaches that most companies use the notion of enthusiasm to mean you&#x27;re going to work overtime, not get paid for said overtime, and generally get heaps and heaps of work loaded on to you, far more than reasonable, and if you complain, they&#x27;ll &quot;doubt your enthusiasm&quot;.<p>Not a workplace I want to be part of.

Sounds exciting. Some time ago during a ~5h interview I got to present my coded solution to a UI problem to the entire (~10 person) company at the end, panel-style. This was told to me after they described the problem they wanted solved in a couple hours. In hindsight it was kind of fun; in retrospect perhaps I could&#x27;ve done without the adrenaline.

I&#x27;m sorry about the rejection, it hurts when you put time and effort into something. The best remedy is to apply to other companies quickly!<p>I read through the presentation, it was very interesting! But it seemed more about advertising and marketing than bioinformatics or programming. Was the job related to data acquisition and experiments?

I went through something similar as a Junior engineer, except the presentation didn’t get cancelled.<p>The experienced engineers in the audience absolutely tore me and my code apart. It was a blood bath and semi-traumatizing.<p>On the upside, I took their criticisms seriously and came out a better engineer in the end.

My experience of the last year has taught me that if I need a job I am willing to put up with the interview process, but if I don&#x27;t I am not. Companies however seem to think they can treat everyone they call in as if that person desperately needs the job.

Another loser protecting a faceless corporation that they owe nothing to. In fact the corporation owes them for the pointless waste of the authors time. This is why the world sucks because of spineless twerps like this author that refuse to name names.

Tesla made me give a presentation, that&#x27;s the only time I&#x27;ve encountered this request. That was fine with me. The presentation bit went well and they were an easy crowd. Someone else got the job though.

Invoice them for your prep time, the time you&#x27;d have presented it (and recovery period), and double it for wasting your time.

Yeah, that is annoying. I am surprised they didn&#x27;t tell Jessime that they were looking for someone with a PhD.

We should start charging fee for our time during interview. Thats the only way to fix this.

Has there been a study on the percentage of borderline personalities or maybe just run-of-the-mill sociopaths in &quot;Human Resources&quot; occupations? The name kinda says it all.

I was laid off at the end of October from my position of 6 years, due to then employer&#x27;s client base being 95% NYC&#x2F;NYS government agencies. Those agencies got hit with budget cuts due to stalls in tax revenue, and as a result contracts dried up as well. Those 6 years were the most toxic and mentally&#x2F;emotionally draining years of my life, and left me a different person than when I went in (long story short, text book definition of workplace sociopath for a boss).<p>After the first four years of holding up a smidge of hope that things would get better there, I decided to start applying elsewhere. I got quite a few responses from some well known organizations that I had wanted to work for. Passed their screener interviews, passed their technical assessments&#x2F;take home projects, went through final interviews with a good number of them, only to get the email response of, &quot;Thank you for interviewing with xyz. Unfortunately...&quot;. When following up for feedback, rarely were the responses substantial or in a couple cases, even believable.<p>Now, I totally understand that one will never pitch a perfect game, but man, when you go through 12 interviews at some solid places, where 7 of them seemed to go really well, and you left them thinking, &quot;Man, I feel great after that. Pretty sure I aced it!&quot;, and even had the managers saying things like, &quot;We think you&#x27;re gonna be a great fit! Look forward to hearing from us in the next couple days&quot;, one would reasonably think they&#x27;d be receiving an offer soon after. Unfortunately, that was not the case for me, and after getting the last rejection response I called it quits. The emotional&#x2F;mental toll of putting in so much time and effort into processes which in most cases looked to have favorable outcomes yet amounted to nothing, was just piling onto and worsening my existing state of feeling beaten down, and it wasn&#x27;t worth furthering that.<p>Then came the layoff in October and I immediately began applying away. This time around I&#x27;ve been getting more responses than ever before during a job hunt, and once again with reputable organizations, again with many times making it through each step of their interview&#x2F;testing process, again with having some great experiences and feeling confident about the outcomes, again with the overly positive&#x2F;leading statements from managers, and again being let down each and every time.<p>The best was with a mid-large ad agency, where I passed the first interview, then was given a timed online technical where 60 minutes was allotted to write vanilla JS and build one toggle button whose text&#x2F;styling would toggle, and a second button that replaced an href in an anchor... 60 minutes for that. I finished it in 5, then spent another 3-5ish minutes writing comments just to show attention to detail and care for potential others having to work with whatever I wrote. You know what the response was? &quot;Sorry, but we&#x27;re looking for someone who has a bit more technical experience&quot;. I shit you not. It was laughable.<p>To top it off, I&#x27;ve been ghosted a few times, which has been a new experience. One guy even had the balls to reach out to me a month later, after saying he was going to setup an interview with his team two days after we had what seemed like an awesome call, but then he ghosted lol.<p>At this point, after feeling left burned, I&#x27;m saying fuck it and taking a break from interviewing to work on my own projects for the time being, with the hope of becoming at least somewhat financially independent&#x2F;less reliant on an employer. The application&#x2F;interview process is such an incredibly disheartening process and I feel for anyone who has also been ran through the wringer.

12 hours of unpaid labor to just get your foot in the door? I&#x27;ll take the hardest conceivable pass, please.<p>If a company sees no issue with asking for a TED talk just to consider you for a position, imagine what kind of work&#x2F;life balance you can expect once hired. What kind of last minute assignments, what kind of weekend calls to wipe some higher up&#x27;s rear end after they foot-mouthed with a client, and promised the moon, and now you&#x27;ve gotta go to Kroger and find 40 tons of cheese and carve it up so they don&#x27;t need to look stupid.<p>I&#x27;ve said it before and I&#x27;ll say it again: we as software devs&#x2F;code monkeys&#x2F;devops&#x2F;admins have fucking worth. You should not EVER be willing to put yourself through this kind of meat grinder, not just to avoid demeaning yourself, but for demeaning everyone else who practices your craft alongside you. They&#x27;re not worth so little as to need to do that, and neither are you.<p>You want me to write code for your company? Awesome, I&#x27;d love to do that. Pay me.

I know it&#x27;s a luxury that I&#x27;m in a position to do this, but anyway: in general I won&#x27;t continue interviewing with a company that expects me to put in significant effort into just preparing for the interview. Make a full presentation, build a small service or other not-trivial take-home coding challenge, put together a business proposal, etc.: I&#x27;m sorry, I don&#x27;t do any of that for free. My resume and references speak for my abilities, and while I&#x27;m happy to have them probed and challenged (heavily!) in an interview context, that doesn&#x27;t extend to my putting in hours of work just go conduct the interview at all.<p>This isn&#x27;t high school, and you&#x27;re not going to give me homework just for the chance to work for you. And I use the homework analogy intentionally, because just like with school, this doesn&#x27;t scale. I can&#x27;t interview at, say, 10+ companies all of whom are expecting me to put in paying-employee-level work just for the interview while also holding down my regular job. And I&#x27;m not going to go with a significantly shortened list of candidate companies just because their interview process is so onerous that I literally don&#x27;t have the time to talk to more.<p>Again, I know not everyone can do this, but realize that companies try to exploit you during the interview phase, too. You need to also have standards for what you&#x27;re willing to put up with.

My take on his presentation. I can&#x27;t read any of the text on the first slide because it is way too small.<p>And I shall say that I am on a 1920x1200 screen. If the interviewer was watching on a corporate laptop this might be 2 pixels per letter.