People think that the new IE is Safari but it's actually Chrome. IE wasn't problematic because it lacked features, on the contrary, IE was very innovative but non-standart. This pushed developers into creating web pages using the fancy but IE only futures, thus to have full experience you had to use IE. "IE being bad but still had to use it" phase was only possible thanks to that.
In this particular case it might not be a Chrome specific thing but it gives me goosebumps when I see I'm directed to use a particular browser. Most of the times, its "Use Chrome for full experience".
I like Chrome, I don't like being pushed to use Chrome because I use Safari due to its performance, low battery impact and iOS-macOS integration.
The bad parts of IE happened when Microsoft dropped the ball but users had to use it anyway because everything was already made for IE the non-standart way and the developers had to keep making things for IE because everyone used IE. Catch-22.
I don't want make people stop using Chrome, it's a solid browser. I simply want me having the option not use it.
Today Chrome is very good but what happens if Google mismanages it like Microsoft or abuses its position because an MBA looked at it and had an idea? Some already argue that Chrome is not what used to be and Google already does some sketchy things.
It's unlikely to happen because the incentives are different.
00's Microsoft stopped IE development when they had a monopoly because they wanted everyone on Windows. The web was a competitor, they tried to stifle it.
Google makes all of their money on the web. They want everyone on their browser and for the experience to be as good as possible.
There are plenty of articles and reports on the loss of effectiveness of the Google Search and the dying of the self hosted content. There’s also a lot of attempts to transform the web into something else because it has become horrible.
I would not say that Google’s incentives are aligned with the rest of the participants. Google may very well take defensive actions against anything that challenges the status quo.
I don't know if it's worst that if you browsed the internet a bit carelessly you had some malware that basically showed you ads and pop-ups (IE) or that if you browse normally you are silently tracked and followed by your "user agent", all the time, no questions asked, to show you better ads (Chrome).
If you frame the situation like this, then the second is obviously better. If I'm targeted with better ads, my bank account might decrease thanks my own choices.
Having said that, phishing attacks sometimes use google ads, so it's not even black and white picture, but it's a lesser evil option :)
Exactly. This is extremely petty and particularly among software developers who are keenly aware of this sort of behaviour, a little bit self-defeating.
Exactly, I don't get these complains. It's literally for people who want to work at Google. If you don't want to use Google products you're clearly not the target audience.
Here's a description if your browser isn't supported: This is an app that simulates an interview where you respond to 5 typical questions (for example, "what are you looking for in your next job?"; "tell me about a time you delivered results despite obstacles"). The site requests mic access and transcribes your response. The material on the front page says:
> Practice answering interview questions.
> Get comfortable answering questions from industry experts. Just talk and your answers are transcribed in real time.
> Get insights about your answers.
> No grades, just insights about what you said. See job-related terms you used, your most-used words, and talking points you covered.
> Keep improving.
> Use what you’ve learned and jump back in for another round. Keep building your confidence in a judgement-free zone.
Or, and I find that more likely, they just didn't see the point to spend resources supporting other browsers if they don't have to. In the end, if you want to work at Google, they can probably expect you to use their products.
Okay. But there is a 90% chance that nothing on that page requires anything chrome-specific, and even if it did, it would probably be a line of code or two to make it degrade gracefully in firefox.
It was undoubtedly more work to implement "Sorry, your browser isn't supported" with user agent checking and whatnot than it would have been to support firefox, because in all likelihood, that site would Just Work without any real modifications(modulo styling).
I'm really surprised they included the strengths and weaknesses question. Anyone asking my weaknesses expect anything other than bullshit or humble bragging?
The execution of this page is so perfect that it gives me dystopian vibes. I think this might actually be just a tech demo for demoing speech capabilities :)
If anyone asks me my weaknesses I'm taking that as a sign they don't really know what they're doing and are just reciting questions they've seen or heard others use before. I honestly do not know what kind of useful information they'd get from this because you'll either get:
- bullshitters who have a prepared answer that sorta sounds good
- nervous people who cannot think of anything
- nervous people who will start listing off their worst qualities
Honestly the best response when faced with this is to joke about the cliche "I'm a perfectionist" response and hope that everyone is happy to move on
That's actually quite encouraging to hear. I have encountered it once when I was younger and I wish I had the self-confidence to deal with it the way I described in my comment. I think I just did the "nervous people listing off their worst qualities" thing.
I feel a bit bad at the "bullshitters" comment, I was trying to show the worst case scenario and didn't factor in "normal nice people who have a prepared answer" :)
Being able to answer BS questions such as that is likely strongly correlated to conscientiousness, social skills, and intelligence, even if the actual content of the answer is irrelevant.
You're probably overestimating the abilities of the interviewer asking these BS questions. Like they're some sort of masterminds playing 4d interview chess with you.
If you're going to get into the meta-interview thing, you need to realise that it goes both ways - candidates will judge you on your BS questions. Ok if Google it's maybe not a huge deal, but if you're a SME it's quite important
I quite like it - it gives me a chance to address areas where I might appear to be a great fit for the job, and set out why they shouldn't be blockers.
There are definitely better ways to phrase the infamous weakness question. This gives me idea to start asking: "Are there any aspects of how you work, which you’re trying to improve?"
That would gauge whether they're introspective, self-aware, and self-critical.
One phrasing that I got in an interview was "What would your current or previous managers say were your strengths", quickly followed by "... say you could improve".
It was interesting because it actually got us in a different discussion on how employees are evaluated at their company. My personal take though is that the candidate should be self-critical enough to be able to tell me what their weaknesses are and how they are mitigating them.
FWIW I added a "Flaws" section to the end of my resume when I recently revised it. The section opens with, "I'm not an ideal fit for every role or organization", and then briefly covers a couple of less-flattering (but fairly normal) aspects of my character. For example, I'm good with short-term high-stress, but not long-term high-stress.
As I see it, it helps to filter out some of the kinds of places or teams I wouldn't want to work with in the long term, or at all.
When I get asked my biggest weaknesses I just reply with brutal honesty. I say that sometimes I'm lazy to a fault, that I can't function in the morning at all and can be easily distracted during work so I need a quiet working environment (including no notifications). I think it lost me a potential job offer last week but I don't know if I'd like to work at a company with a toxic positivity problem.
Meh, I think it's fine to be honest about weaknesses for that question. It might disqualify you from some jobs, but IMO there's a lot of value in demonstrating you're able to self reflect.
I have a hard time staying enthusiastic about a project I don't understand the value of, for example. It makes me a bad candidate for teams that are siloed and jobs that highly compartmentalized, and I want to make sure the teams I'm working on have the tools they need to get value to the customer.
It would suck if I took a job like that, and my theory is by stating that out loud I can avoid roles that have those kinds of environments.
being this Google, I suspect it's all a clever facade to induce you to give them more of your info. The end game is targeted ads, as with everything they do.
I know many great guys from Google, they take very seriously all browser compatibility. I cannot think any company who took browser compatibility to the levels of Google. This fellow just made a big mistake developing something particular for a couple of browsers. It's not in Google ADN.
IDK, I worked at Google for a long time and the people who cared about browser compatibility by far the most were the Chrome and Workspace teams. The Chrome team tried to emphasis that it made it very hard to negotiate web standards and made them look bad if Google had Chrome-only properties and Workspace wanted browser compatibility because they needed to officially support browsers that their customers were mandated to use (but they didn't really care about the long tail of browsers).
Only if compatibility means "at least some functionality". Anything but latest Chrome, Safari or desktop Firefox gets a super basic version even though there appears to be no technical rationale. Just "it is too hard to test this on all of those browsers". Just faking the QA string gets you a working "chrome" experience.
What functionality is missing? Is it anything that people actually care about?
I did a search from Internet Explorer in Mac OS 9 a couple of years ago. I put in a term and a list of results came up. That's really all I could ask for.
If I look up lyrics to a song that's in a different language it will display the lyrics, but only chrome will offer the ability to click a button and translate.
I'm guessing that Mozilla takes browser compatibility even more seriously. And here's an addon to change the user-agent string for Google search so you get the same experience as a Chrome user: https://addons.mozilla.org/en-US/android/addon/google-search.... Off the top of my head, Google Groups content often hangs on my mobile Firefox browser, while Chrome access is always speedy.
You have to understand; supporting different browsers is a lot of work and cannot be stemmed by a small band of mavericks like this. It would need some big organization with serious engineering capacity.
That’s beyond laughable. As a solo developer at multiple startups this is hardly a dent in my time spent building web apps. The smoke test is that if you’re struggling with cross-browser compatibility, you’ve already done 100 other things wrong.
Yup, same here. As a web developer I'm always baffled when I have to make things work everywhere all the time but when it's Google they're like "oops, looks like you need to install another software to use our stuff".
"A visitor loads your webpage. They try to use the PgDn key to scroll through it, and nothing happens. You tell them they have to first click somewhere inside the page after loading it, being careful to not click on any element that will respond to the click. Then PgDn will work. Do you think this is a problem, and if so, how would you solve it?"
Yes, I realize the HN Guidelines say "Please don't complain about tangential annoyances—things like article or website formats, name collisions, or back-button breakage. They're too common to be interesting."
But good grief, the last I heard, I thought Google was a web company.
Isn't having a web page that Just Works part of that?
On to something more substantial (as if breaking something as fundamental as the PgDn key isn't substantial).
> Get insights about your answers. No grades, just insights about what you said. See job-related terms you used, your most-used words, and talking points you covered.
I am sorry, but this is really freaking me out. My job-related terms, most-used words, and talking points?
Maybe I should just call it a night and admit I'm not good enough for Google.
Am I the only one to think this is just a clever way to induce people into voluntarily disclosing more of their info to Google, so that a better user profile for ads can be built?
I hate hate hate questions that are "tell me about a time when..."
My mind literally goes blank. The pressure of sitting down with someone you've just met and they are testing your memory.
I don't remember times, I remember the lessons. Kind of like I can't remember any source material unless I have an intuitive understanding of it.
Ask me about what I learnt when x happened - or what lessons you've learnt previously that apply.
You might suggest that's what they're asking - but not in my experience. They want the actual story.
Basically I now prepare fake stories before hand. Seems pointless. Give me hypothetical scenarios any day of the week.
It's a me problem for not optimising for interviews, but the thought of gaming the system feels dishonest.
Basically, these interview warm up questions would be incredibly useful for people like me. If I ever go for an external interview, I would make use of this. Practising for something that is useless.
My problem is I usually don’t have a story, my career has been boring and stagnant.
I had one of these questions tossed at me in an interview last year. Something a long the lines of a “time I faced a difficult technical challenge and how I managed to solve it”, but I didn’t have any.
Well… ok not exactly true. In my professional career I’ve done more sitting around staring at the screen while bureaucrats debates than I have working on challenging technical problems. Any true difficult problems I’ve faced professionally have been predominately organizational.
However I’ve been programming in general for a lot longer, and in recent years, despite finding a continuous lack of interest in programming, I am very interested in things that end with me writing code and that’s created some of the work I’m most proud of l. Ofc the interviewer wasn’t interested in any of that, as they wanted something from a position off my resume.
> Any true difficult problems I’ve faced professionally have been predominately organizational.
If I was the interviewer I would love to hear that story.
Much like in political debates, answering the question asked is not required to persuade the voters. And in an interview, the end goal is to convince the voters.
This has been exactly my experience with questions like this. My brain just doesn't archive memories in that way at all and feels totally backwards to me.
To answer questions like those, I'd have to sit down and think for some minutes to re-index all my past experiences to fit the framework of that specific question.
I don't know if this is a shortcoming of my memory or character, but all this has done in the past was to make me sit down and prep examples for every possible "tell me about a time when..." question, which I find an absolutely grueling exercise.
It's not that I'm not an introspective person or learn from my past experiences; I just don't frame them in my mind in a way that I'd be able to single out specific past situations for an immediate retelling, especially during an interview.
I would go as far as to guessing that most people are probably like that, but we've accepted this is how interviews work, hence all the interview prep for questions like that.
I agree with you. Those kinds of questions feel awful, and it doesn’t feel great to make one up either. In the past I’ve tried to be honest and said that I don’t have a particular story (or w.e they called it in the question) but that I have something that I can to a similar situation and like you suggested I would also talk about what I learned / took away from that experience.
It’s similar to how whiteboarding is an inaccurate but useful model of coding ability. I’ve had candidates who could answer in general detail how they would implement an algorithm, but struggle to produce working code.
The purpose of these behavioral questions is to get you to produce details about how you actually act at work in challenging circumstances.
If we reject these models I think we’d be stuck with contract-to-hire as our evaluation model which seems more stressful for both sides.
> The purpose of these behavioral questions is to get you to produce details about how you actually act at work in challenging circumstances.
I think the idea is not that these are low-signal, but that the _recall_ of stories like these is not a given. I think the whiteboard example is apt, as both are nonzero-signal exercises that can be torpedoed by a lack of preparation that has nothing to do with your actual problem-solving ability.
It's universally-known that you need to practice for whiteboard-style coding questions, but I guess it hasn't yet seeped into our cultural knowledge that you need to do the same for behavioral-style questions. I'm currently in the middle of a jobhunt and I feel like I just independently discovered it.
I find these types of questions invaluable as an interviewer, at least for mid-level to senior roles. And you're right, I am looking for an actual story, not just the lessons learned.
The problem with just asking about lessons learned is that anyone can memorize and rattle off a set of best practices they found in a blog post somewhere. That doesn't tell me whether they have relevant experience or not. Asking to tell me about a time when X happened and how they dealt with it cuts right to the chase, and I'm afraid there's a big difference in a response that comes straight from memory and one that's fudged or invented. The initial story might be great, but most people visibly struggle to keep inventing answers to probing follow-up questions about what happened. ("Did you consider Y as a solution? Would it have worked in this case?")
I sympathize, though - it's not like our brains have all our work experience indexed and readily available. The interviewer's choice of X is crucial. If the prompt is too specific, most candidates genuinely won't have a good answer. Too general and it won't help select for this role in particular.
An incidental nice thing about this type of question for candidates is that it can give them a sense of what this role at this company is actually like without their having to ask. I often even phrase it as "One of the challenges we're facing as a team is X. Can you tell me about a time when you faced something similar?" The discussions that follow tend to tell me loud and clear whether the candidate is a fit for the role.
Now, although I'm claiming fake stories are easy to spot, I don't know what I don't know. It's possible someone has taken me for a ride and I ended up giving them the 'strong yes'. I don't think there's anything wrong with that. If you're able to craft a sufficiently detailed fake story and talk about it off the cuff for a while in depth, then you probably have enough relevant experience anyway!
I can't say whether this would help GP, but as someone who also struggles with these questions the main thing I'd ask for from the interviewer is time to think. I may need to pause for a solid 60+ seconds to go through my memories, please don't take that the wrong way.
I agree 100%. Also write down your star answers before an interview. I had 3 pages (took ~12 hours) of STAR stories/answers before anyone asked me a question.
As an interviewer I also like that kind of question for warm-up - but I ask it with context. Usually I would get the candidate to go over his previous employers/experiences and when he mentions one I find interesting I take note. Later I will come back to that and ask for an interesting story at that place.
Doubles nicely as mini-vetting for his/her bio as well, if the position given was exaggerated the story will usually show it.
I had the same problem with these questions. Then one day a recruiter said to me, "kageneko, your engineering skills are on top, but your question answering is really bad. I think it would help if you wrote down some questions and answers beforehand."
So, I did. I tried to remember every question every recruiter had asked me (and started taking notes from then on). I wrote down 1-2 paragraph answers for each question. I found that just the act of writing down these answers and reviewing them later helped even when the interviewer would ask questions that were not on my practice sheet. It would nudge my memory and keep things fresh and a lot of things could be used for related topics.
Those questions can also work against you if your career has been relatively drama free.
Like yeah, there have been some incidents during my background as a software engineer, good and bad, but they were pretty straight forward events. Incidents were simple to correct. The further I got into my career, the less often anything memorable has happened. I'd struggle to remember the last time I had to put out a fire or struggle to implement a novel solution. As you say, I have lessons I've learned, but my memory doesn't linger on a lot of individual events.
I think I've gotten pretty good at handling said interview questions, but internally I'm shrugging my mind's shoulders.
> Give me hypothetical scenarios any day of the week.
Hypothetical scenarios are just that, hypothetical. Competencies are much better evaluated through evidence, rather than speculation.
A classic example here would be conflict resolution: if you ask someone “how would you solve a conflict at work” you typically get a very standard - and often rehearsed - answer, whereas if you ask “tell me about a conflict you had at work” you end up with something much rawer and more revealing. The way we imagine we deal with conflict is often not how we actually behave.
Of course, not everyone has an answer to these questions. If I’m interviewing someone who’s only a year or so out of college they’re unlikely to have a wealth of work related stories to pull from.
A good interviewer recognises this, and adapts the questions to fit the background. Perhaps you’ve never experienced a conflict at work, but you definitely will have elsewhere (perhaps, for a college grad, at a student group or team project).
Interviews are part of why I work for myself now, and partly because of these questions. I might remember a specific implementation detail from 15 years ago but I can't even remember if I ate breakfast today.
So after thinking about it for the past 45 minutes, I don't think I ate breakfast today, nor do I recall stopping at any of the traffic lights that I would have had to stop at on drive this morning. But I recall a shell script maybe a decade ago that behaved differently between POSIX compliant shells due to the differences in how they handled processes in a pipeline. That's when I discovered POSIX was not unambiguous.
> Basically I now prepare fake stories before hand. Seems pointless. Give me hypothetical scenarios any day of the week.
I'm with you on this, as I find on-the-spot recall pretty hard too, especially depending on my mental state. I've just started doing a career retrospective before every job hunt, with an eye towards extracting communicable takeaways that can be communicated in interviews. It's actually a very useful exercise, excluding the part where I have to find a way to articulate the takeaways.
But I've found that, surprisingly, getting decent coverage of the stuff I learned from my job makes it a lot easier to answer arbitrary recall questions
Someone once asked me what was the most interesting bug I ever fixed. How the hell do I honestly answer that on the spot? Human memory is notoriously weak, and I don’t write down my bug fixes into a diary.
I ended up just making up a fake story on the spot that was uninteresting and barely coherent. That was the first question I was asked in the interview, and made me nervous for the rest of it. Didn’t get the job.
Clearly I should have taken an improv class in preparation.
But yeah, I learned the same lesson as you: prepare and rehearse a bunch of fake stories in advance. Completely stupid waste of time, but necessary.
It could be an interesting part of the interview that reveals a lot about the candidate, but realistically it’s going to favor the people with rehearsed fake stories. What are the chances that your genuine real-life experience is more interesting than someone else’s fake one specifically crafted to be as interesting as possible?
Yeaaaah. I got nailed with something like this too. I actually started talking about one bug and kind of confused it with another similar bug. I probably sounded like a moron or a liar and they passed.
Was a shame. But I guess I should really rehearse my "STAR" stories :-|
To me, it looks like questions about things like "most interesting bug" are unintentionally going to be biased towards more junior developers. Once you have a lot of experience under your belt, bugs and fixes sort of all look the same. They're no longer novel. I don't know how I'm supposed to wade through 20 years of experience and recall "the most interesting bug I ever fixed". Now, if I had 2-5 years of experience, that would likely be super easy to recall.
Such a 'senior' engineer then has not encountered sufficient bizarre bugs. Or more likely he had rehearsed it sufficiently (for a whole bunch of reasons) and you bought into it :)
I usually ask them to answer the questions back to me to see if it inspires a memory, and to give me some time to think about what mine was.
Edit: I say something along the lines of "Oof you put me on the spot now haha. What was one of yours? Maybe something comes back to me when I hear you"
I think people generally ask that in hopes to break the ice or to connect with the other person. So, either they will answer and it might nudge a memory (if they prepared/remember) or they'll blank as well and you'll have a laugh over the question and move on.
It's an interview, not an interogation! I know your livelihood depends on it, but being natural/relaxed helps your odds IMO; as it's less likely you'll get flustered or tilted. I realise this is easier said than done as I'm also plagued with anxieties and phobias, but I never saw interviewing as a stressful situation. At best, you get a job, at worst you forget about eachother in a few days lol.
Sometimes I get the feeling that the interview questions are (consciously or unconsciously) optimized to find people who know when to lie (and lie convincingly) to inquisitor types.
Surprise, your boss' boss just decided to drop in and is asking your new guy some pointed questions about the deadline. ~Tada~, the IRS is sending someone over who wants to interview a few people. Oops, that lawyer that your clients hired are going around and subpoenaing previous employees.
"So, uh, we need you to tell us your biggest weakness. And bonus points if by the end of your story the entire interview team is crying from laughing so hard."
So ideally, the most interesting bug story response would be a story about how awesome you are at finding bugs that are introduced by other organizations than the one you were working in AND make the listener like you.
* Look this candidate can fix bugs.
* Look this candidate knows not to talk about the dirty secrets of the org they are (were) a part of. And is able to defect blame to another entity.
* Look this candidate makes questioners like them which will hopefully keep too much scrutiny from being applied to them.
I just answer these things honestly: "gosh, ehm, I'm having a hard time thinking of a specific thing right now", and then turn around the question to answer something slightly different, for example a particular difficult bug that I might remember, or a somewhat (not necessarily "most") interesting or difficult thing I fixed recently (and is thus fresh in memory, stressing this is just something I did recently).
They don't really care what the most interesting bug is anyway, they just want to have a conversation surrounding bugs. You can also turn it to "well, in general [..]".
Also don't be afraid to say "ehm, let me think for a second", instead of feeling obliged to answer right away.
Like write down 5-10 of these questions and answers that are somewhat common.
Write down some anecdote and more or less use the same all the time.
The same with telling about yourself write down 5-10 sentences and use that every time. Of course you probably have to update it from time to time but remember that you don't have to come up with everything on the spot.
You might not get exact same questions but if you have some things written down you can still start by rehearsed anecdote to get yourself going. Because if it is open ended question it might be more important to keep conversation going than "being correct" on your answer.
Make something up. Piece together the various details of different bugs you solved in your career or that you were vaguely involved in the solution to something reasonably impressive and coherent. If you are a skilled developer you will be able to make the story convincing. Unless you happened to rehearse your answer to that specific question beforehand, there is no way to reliably deliver a good performance on questions like these. You always have the plausible deniability of "oh, this stuff happened years ago, so I'm a bit fuzzy on the details."
I'm really struggling to understand how telling someone about the things you've done in the past is a tough ask. "Tell me about a time when a project didn't turn out as expected" or "Tell me about a time when you disagreed with your manager" are common variants of this question, and honestly if you don't have these experiences you just might not be experienced enough for a role.
Telling stories about the things you've done is an essential part of human communication, not some weird "game" that hiring managers have come up with to mess with you.
In a very practical sense, if you can't explain things that happened to you it's going to be really hard for you to communicate issue involving solving problems with software.
What does make sense is plan old interview anxiety. Rather than make up stories walk though your resume and just refresh your memory of how projects went, what lessons did you learn from the projects, what was surprisingly easy, surprisingly hard etc.
I'm inclined to agree with this. I often rant to my friends about weird bugs I've been hit by or the one guy I worked with who went out of his way to create drama. I can't imagine that's a unique practice.
If I'm talking about these things in an interview, I just repeat stories I've told before but with toned down profanity. On the flip side, I'm super skeptical if I'm interviewing someone and say "tell me about a time when a project didn't go well" and they insist that all of their projects have always gone smoothly, even after I prompt that they to go far back as high school group projects.
Just ignore the question and tell a story you wanted to tell anyway.
"Tell me about a time when you had a conflict with a coworker"
==
"I know you have some stories about great things you've done in your career. I want to hear those stories - that's the whole point of this interview - but I don't know what to ask, so I am giving you a very open-ended prompt, on the assumption that at least one of your stories included some kind of disagreement with a coworker."
edit to add: don't make something up. Besides dishonesty being generally bad for a variety of reasons, it's very likely that the interviewer is better at spotting liars than you are at lying.
Most of my interview prep when I was last looking for a job was basically how to handle these type of questions. It took me a while, but I ended up with a lot of notes describing my past experiences. That way there was no memory test; all the hard work had been done.
I really recommend preparing for them; think hard about your projects, things you've done, why you did what you did, and so on. If you need prompts, I found Amazon's leadership principles (cringy though they may be) to be a good starting point.
In fact, having prepared for Amazon's, everyone else's was easy.
Now I ask these questions and it's super obvious when people haven't prepared for them. I feel bad sometimes. I personally prefer them to the hypotheticals, but people do tend to freeze up.
Understandable, given that you are a mere human being.
But if it's helpful, what they're really telling you is: "Look, we're just ticking boxes here. Go home and think up, or just use our search engine to look for a sufficient number of fake, but expected answers to this question. Then re-apply in 6 months."
"Tell me about a time when" is the bottom of the barrel for interview questions. I have never had a good interview experience that included that particular question.
> Basically I now prepare fake stories before hand.
I think interviews these days expect you to do prep before the interviews. Reciters even give you a list of these before hand. People practice (semi)fake answers to these and get the job.
"Tell us a time when you disagreed with someone..."
I feel like the only way to properly answer these types of questions is to make up some BS scenario and talk about how you worked to see the other person's perspective, added your thoughts and came to an even better solution than you could have done on your own.
Do people really disagree so much in workplaces? These questions feel like they're training people how to be sociopaths...
I hate this one. The other one that gets me is "Tell me about a time where a team member was underperforming. What did you do?"
I think the correct answer to this is to get on their ass about it or rat them out to their manager. In reality, what I have done is just do their work myself so it gets done.
Pretty sure this is why I failed my Amazon interview.
Ideally the manager should already know they're underperforming anyway.
But there are cases where they may not. I've told my manager that they should probably have a conversation with some people, or even let them go. I don't think that's "ratting" really. Like you already said: it's you who has to pick up the slack, and a lot of the time "underperforming" also means more stress and work for me (usually in the form of cleaning up after them, fixing their bugs, etc.) With some coworkers I genuinely wished they would just stay at home. This gets even worse if the quality (and thus, revenue) of the company gets affected by their underperforming, which also affects your salary, or even the company's survival!
I also try to explicitly praise people in 1-on-1s btw.
Yes, people disagree frequently in workplaces. I have quite a few real scenarios where I worked to see the other person's perspective and came to a better solution than I could have reached on my own, and when I interview people who don't that's a real concern. Resolving disputes about the right way to do something is typically a core job responsibility for anyone beyond the entry level.
I have a few that stick in my memory, but I don't know that they'd be appropriate - although they might give you a little insight.
1) We had a dev on the team who was adamant that we prefix all testing library functions in tests with their namespace. I argued that it in my experience it was pointless - no team I'd been on in the past ever had an issue with not prefixing them. He wouldn't budge on his stance. When he was on leave I changed all tests in the project, removing the namespace prefix. When he came back he seemed not too bothered by it, he got used to it and never brought it up again. We're still in contact now.
2) I was once brought in as a partner in a startup. They'd failed to make a product and I came in and built what they couldn't do from scratch into a working product in about 6 months. As more people used it the CEO started to become more active in the project. I was creating a new piece of functionality when he told me he wanted it another way. We didnt agree. I suggested taking it to users and getting their thoughts on it, he refused. We ended up disagreeing and then he pulled the "I am CEO card". Following the meeting I tried to understand why he wanted it the way he did and why I wanted it the way I did. I determined that my approach presented three separate bits of information in the graph, and his approach lost one of those pieces of information. I redesigned the UI to include all three parts of info but to look more like he wanted. I ended up essentially being pushed out of the business, he didn't give me any stock that was promised, and he ended up running that project into the ground. His company ended up failing and he's now a PM in some other company I believe...
3) I'm sure there are other instances but these are the two that pop into my mind. Most places I've worked people have discussions - perhaps there are disagreements, but they don't burn into my memory like the last two examples. Emotionally distressing events are much easier to remember.
Not sure how people would take those stories in an interview...
I got asked once about a time I disagreed with my manager. I talked about a time we differed on how to approach a problem, I made my case, but they asserted to do it their way. Since they were my manager, I did, and it worked well enough.
This did not play well during an interview. But idk, am I supposed to pretend I persuaded my boss to my side? Sometimes you gotta do what your boss asks even if you're not super jazzed about it.
If it was an amazon interview that would have went over well. Disagree and commit is explicitly about being able to stand up to your team/manager and voice your opinion about how to do something correct, but if the team/manager overrules you, you commit the the vision the manager or team is building.
Granted, it's hard to very any of that is true in an interview. 90% of people will disagree, then allow themselves to be overruled and then every chance they get rehash the arguments they lost anytime something tangential to it comes up. That's easy to hide in an interview.
Interviewing is such a crapshoot of luck. You can prep all you want, but if you get a grumpy interviewer or a challenge out of your wheelhouse things can go south and there's no way to show you're better.
There was a time I ended up convincing my manager and things went my way.
There was a time my manager ended up convincing me and we did things their way.
There was a time we just couldn't agree and I ended up doing things their way because "they're the boss".
There was a time we ended up putting it to a sort of "vote" for the entire team.
There was a time we made a compromise we could both live with.
There was a time another team member jumped in with an even better solution that either of us thought of.
There was a time I ended up quitting my job because we didn't agree and he was a gigantic dick about it for no reason.
---
All these things actually happened over my career, and no single one accurately describes how I'd deal with a situation where I disagree with my manager. I'd generally answer it like that, although I'd leave that last one out for obvious reasons (there was also a lot of build-up/context to that one that would take ages to explain, and is hard to explain in the first place).
> Firefox currently has a media.webspeech.recognition.enable flag in about:config for this, but actual support is waiting for permissions to be sorted out.
Once again, Google out in front of user permissions and protections getting finalized in standards bodies.
It uses speech recognition to transcribe what you're saying, but it lets you type your answer if you deny microphone access. That's a poor excuse to demand you run it in Chrome or Safari.
I suppose a spoken answer gives more realism to an interview simulation, but a simple "Your browser doesn't support speech recognition. You can use Chrome, Safari, or manually type your answers", would have sufficed.
Just completed my Google interview process, it was biggest waste of my time in recent years. Oh the technical questions can vary from Linux kernel question on how something interfaces with kernel/ring0 to front end library which fetches web images, then coding a esoteric algo.
I am disappointed in myself that I wasted small period of my life falling for recruiter/social hype of these companies. Worst mistake you can make while looking for a job is to prepare for one specific company, web is full of this garbage content to answer specific company questions.
Good luck and thanks for the resource, Google. But as I’ve told your recruiters over and over in the last year, you won’t even get me into an interview with your anti full time remote work policy.
This changed in 2022, they are taking on a lot of remote workers now. Although I think they may ask that you be in a certain zone, like some mileage away from a physical office. But I think that may be for tax reasons.
Interesting, that would make sense. In the last six months/yr I’ve been told by two different recruiters “all of these positions are hybrid. You may be able to start out full remote for one or two of them, but it’s going to reduce your options significantly.” This is for UX Engineer roles specifically if that matters
Yeah I don't exactly know why but it sounded like different jobs had to be within certain offices. Like if your team is in Mountain View and Seattle you can't necessarily work from Texas, you'd need to be an hour or whatever from one of those two offices.
Well, that hasn’t been the case any time I’ve talked to a recruiter in the last 6 months regardless. So there’s either misalignment internally or I’m just getting fed into the wrong pipelines.
This is Ceasar Chavez on Easter Sunday. The ego of people at Google is larger than their intelligence. They don't understand when they turn people off by their "smart" decisions.
I had to google "Ceasar Chavez on Easter Sunday" to find out what you are talking about. Seems like a storm in an easter egg. I 100% see why google would prefer to celebrate a national hero instead of celebrating a religion that a portion of the population care about.
Chrome has 3.4B users. Safari has 1B. Edge has 212M. Firefox has 180M. Not that surprised a small unique page like this only supports the top two browsers.
Here's confirmation that it doesn't (from the site's FAQ via its menu at the top right):
> What devices does this work on?
> You can practice with Interview Warmup on the latest versions of Chrome on OSX, Windows, and Android, as well as the latest version of Safari on iOS devices. Firefox and iOS 14.4 are not currently supported.
It looks like this is not for an interview at Google but something more generic. You can question what Google knows about the interview-in-general, but that's a different story...
I hope people who built this were more aware of the various reputations the Google interview process has had, and made it clear it's not for covering the peculiarity.
No thanks, if you could leave me alone on linkedin that would be nice too. I don't want to take a phone quiz or jump through your hoops, you're just not that impressive to me.
208 comments
[ 2.5 ms ] story [ 631 ms ] threadTotally unacceptable and shameful.
But no, the whole main content is blocked for non supported browsers (side pages like FAQ stay available)
In this particular case it might not be a Chrome specific thing but it gives me goosebumps when I see I'm directed to use a particular browser. Most of the times, its "Use Chrome for full experience".
You might dislike Chrome for its privacy concerns, but it's a damn solid browser.
The bad parts of IE happened when Microsoft dropped the ball but users had to use it anyway because everything was already made for IE the non-standart way and the developers had to keep making things for IE because everyone used IE. Catch-22.
I don't want make people stop using Chrome, it's a solid browser. I simply want me having the option not use it.
Today Chrome is very good but what happens if Google mismanages it like Microsoft or abuses its position because an MBA looked at it and had an idea? Some already argue that Chrome is not what used to be and Google already does some sketchy things.
I think Its vital to keep our way out intact.
00's Microsoft stopped IE development when they had a monopoly because they wanted everyone on Windows. The web was a competitor, they tried to stifle it.
Google makes all of their money on the web. They want everyone on their browser and for the experience to be as good as possible.
I would not say that Google’s incentives are aligned with the rest of the participants. Google may very well take defensive actions against anything that challenges the status quo.
Having said that, phishing attacks sometimes use google ads, so it's not even black and white picture, but it's a lesser evil option :)
> Practice answering interview questions.
> Get comfortable answering questions from industry experts. Just talk and your answers are transcribed in real time.
> Get insights about your answers.
> No grades, just insights about what you said. See job-related terms you used, your most-used words, and talking points you covered.
> Keep improving.
> Use what you’ve learned and jump back in for another round. Keep building your confidence in a judgement-free zone.
It was undoubtedly more work to implement "Sorry, your browser isn't supported" with user agent checking and whatnot than it would have been to support firefox, because in all likelihood, that site would Just Work without any real modifications(modulo styling).
Source: working on a transcription service that has, among others, a webapp that runs fine on any browser.
https://caniuse.com/?search=speech%20recognition
The execution of this page is so perfect that it gives me dystopian vibes. I think this might actually be just a tech demo for demoing speech capabilities :)
- bullshitters who have a prepared answer that sorta sounds good
- nervous people who cannot think of anything
- nervous people who will start listing off their worst qualities
Honestly the best response when faced with this is to joke about the cliche "I'm a perfectionist" response and hope that everyone is happy to move on
I feel a bit bad at the "bullshitters" comment, I was trying to show the worst case scenario and didn't factor in "normal nice people who have a prepared answer" :)
That would gauge whether they're introspective, self-aware, and self-critical.
It was interesting because it actually got us in a different discussion on how employees are evaluated at their company. My personal take though is that the candidate should be self-critical enough to be able to tell me what their weaknesses are and how they are mitigating them.
As I see it, it helps to filter out some of the kinds of places or teams I wouldn't want to work with in the long term, or at all.
Example: I am super focused and stay on something until it is done. I am also super focused and follow problem rabbit holes all the way to the bottom.
I have a hard time staying enthusiastic about a project I don't understand the value of, for example. It makes me a bad candidate for teams that are siloed and jobs that highly compartmentalized, and I want to make sure the teams I'm working on have the tools they need to get value to the customer.
It would suck if I took a job like that, and my theory is by stating that out loud I can avoid roles that have those kinds of environments.
No need to go through the interactive part to see these questions.
I did a search from Internet Explorer in Mac OS 9 a couple of years ago. I put in a term and a list of results came up. That's really all I could ask for.
search for: general.useragent.override
set it to: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.63 Safari/537.36
website then works a charm.
Alright then, keep your secrets
Instantly clicked on the close button.
Yes, I realize the HN Guidelines say "Please don't complain about tangential annoyances—things like article or website formats, name collisions, or back-button breakage. They're too common to be interesting."
But good grief, the last I heard, I thought Google was a web company.
Isn't having a web page that Just Works part of that?
On to something more substantial (as if breaking something as fundamental as the PgDn key isn't substantial).
> Get insights about your answers. No grades, just insights about what you said. See job-related terms you used, your most-used words, and talking points you covered.
I am sorry, but this is really freaking me out. My job-related terms, most-used words, and talking points?
Maybe I should just call it a night and admit I'm not good enough for Google.
My mind literally goes blank. The pressure of sitting down with someone you've just met and they are testing your memory.
I don't remember times, I remember the lessons. Kind of like I can't remember any source material unless I have an intuitive understanding of it.
Ask me about what I learnt when x happened - or what lessons you've learnt previously that apply.
You might suggest that's what they're asking - but not in my experience. They want the actual story.
Basically I now prepare fake stories before hand. Seems pointless. Give me hypothetical scenarios any day of the week.
It's a me problem for not optimising for interviews, but the thought of gaming the system feels dishonest.
Basically, these interview warm up questions would be incredibly useful for people like me. If I ever go for an external interview, I would make use of this. Practising for something that is useless.
I had one of these questions tossed at me in an interview last year. Something a long the lines of a “time I faced a difficult technical challenge and how I managed to solve it”, but I didn’t have any.
Well… ok not exactly true. In my professional career I’ve done more sitting around staring at the screen while bureaucrats debates than I have working on challenging technical problems. Any true difficult problems I’ve faced professionally have been predominately organizational.
However I’ve been programming in general for a lot longer, and in recent years, despite finding a continuous lack of interest in programming, I am very interested in things that end with me writing code and that’s created some of the work I’m most proud of l. Ofc the interviewer wasn’t interested in any of that, as they wanted something from a position off my resume.
If I was the interviewer I would love to hear that story.
Much like in political debates, answering the question asked is not required to persuade the voters. And in an interview, the end goal is to convince the voters.
This has been exactly my experience with questions like this. My brain just doesn't archive memories in that way at all and feels totally backwards to me.
To answer questions like those, I'd have to sit down and think for some minutes to re-index all my past experiences to fit the framework of that specific question.
I don't know if this is a shortcoming of my memory or character, but all this has done in the past was to make me sit down and prep examples for every possible "tell me about a time when..." question, which I find an absolutely grueling exercise.
It's not that I'm not an introspective person or learn from my past experiences; I just don't frame them in my mind in a way that I'd be able to single out specific past situations for an immediate retelling, especially during an interview.
I would go as far as to guessing that most people are probably like that, but we've accepted this is how interviews work, hence all the interview prep for questions like that.
The purpose of these behavioral questions is to get you to produce details about how you actually act at work in challenging circumstances.
If we reject these models I think we’d be stuck with contract-to-hire as our evaluation model which seems more stressful for both sides.
I think the idea is not that these are low-signal, but that the _recall_ of stories like these is not a given. I think the whiteboard example is apt, as both are nonzero-signal exercises that can be torpedoed by a lack of preparation that has nothing to do with your actual problem-solving ability.
It's universally-known that you need to practice for whiteboard-style coding questions, but I guess it hasn't yet seeped into our cultural knowledge that you need to do the same for behavioral-style questions. I'm currently in the middle of a jobhunt and I feel like I just independently discovered it.
The problem with just asking about lessons learned is that anyone can memorize and rattle off a set of best practices they found in a blog post somewhere. That doesn't tell me whether they have relevant experience or not. Asking to tell me about a time when X happened and how they dealt with it cuts right to the chase, and I'm afraid there's a big difference in a response that comes straight from memory and one that's fudged or invented. The initial story might be great, but most people visibly struggle to keep inventing answers to probing follow-up questions about what happened. ("Did you consider Y as a solution? Would it have worked in this case?")
I sympathize, though - it's not like our brains have all our work experience indexed and readily available. The interviewer's choice of X is crucial. If the prompt is too specific, most candidates genuinely won't have a good answer. Too general and it won't help select for this role in particular.
An incidental nice thing about this type of question for candidates is that it can give them a sense of what this role at this company is actually like without their having to ask. I often even phrase it as "One of the challenges we're facing as a team is X. Can you tell me about a time when you faced something similar?" The discussions that follow tend to tell me loud and clear whether the candidate is a fit for the role.
Now, although I'm claiming fake stories are easy to spot, I don't know what I don't know. It's possible someone has taken me for a ride and I ended up giving them the 'strong yes'. I don't think there's anything wrong with that. If you're able to craft a sufficiently detailed fake story and talk about it off the cuff for a while in depth, then you probably have enough relevant experience anyway!
So, I did. I tried to remember every question every recruiter had asked me (and started taking notes from then on). I wrote down 1-2 paragraph answers for each question. I found that just the act of writing down these answers and reviewing them later helped even when the interviewer would ask questions that were not on my practice sheet. It would nudge my memory and keep things fresh and a lot of things could be used for related topics.
Like yeah, there have been some incidents during my background as a software engineer, good and bad, but they were pretty straight forward events. Incidents were simple to correct. The further I got into my career, the less often anything memorable has happened. I'd struggle to remember the last time I had to put out a fire or struggle to implement a novel solution. As you say, I have lessons I've learned, but my memory doesn't linger on a lot of individual events.
I think I've gotten pretty good at handling said interview questions, but internally I'm shrugging my mind's shoulders.
Hypothetical scenarios are just that, hypothetical. Competencies are much better evaluated through evidence, rather than speculation.
A classic example here would be conflict resolution: if you ask someone “how would you solve a conflict at work” you typically get a very standard - and often rehearsed - answer, whereas if you ask “tell me about a conflict you had at work” you end up with something much rawer and more revealing. The way we imagine we deal with conflict is often not how we actually behave.
Of course, not everyone has an answer to these questions. If I’m interviewing someone who’s only a year or so out of college they’re unlikely to have a wealth of work related stories to pull from.
A good interviewer recognises this, and adapts the questions to fit the background. Perhaps you’ve never experienced a conflict at work, but you definitely will have elsewhere (perhaps, for a college grad, at a student group or team project).
I'm with you on this, as I find on-the-spot recall pretty hard too, especially depending on my mental state. I've just started doing a career retrospective before every job hunt, with an eye towards extracting communicable takeaways that can be communicated in interviews. It's actually a very useful exercise, excluding the part where I have to find a way to articulate the takeaways.
But I've found that, surprisingly, getting decent coverage of the stuff I learned from my job makes it a lot easier to answer arbitrary recall questions
I ended up just making up a fake story on the spot that was uninteresting and barely coherent. That was the first question I was asked in the interview, and made me nervous for the rest of it. Didn’t get the job.
Clearly I should have taken an improv class in preparation.
But yeah, I learned the same lesson as you: prepare and rehearse a bunch of fake stories in advance. Completely stupid waste of time, but necessary.
It could be an interesting part of the interview that reveals a lot about the candidate, but realistically it’s going to favor the people with rehearsed fake stories. What are the chances that your genuine real-life experience is more interesting than someone else’s fake one specifically crafted to be as interesting as possible?
Was a shame. But I guess I should really rehearse my "STAR" stories :-|
Edit: I say something along the lines of "Oof you put me on the spot now haha. What was one of yours? Maybe something comes back to me when I hear you"
I think people generally ask that in hopes to break the ice or to connect with the other person. So, either they will answer and it might nudge a memory (if they prepared/remember) or they'll blank as well and you'll have a laugh over the question and move on.
It's an interview, not an interogation! I know your livelihood depends on it, but being natural/relaxed helps your odds IMO; as it's less likely you'll get flustered or tilted. I realise this is easier said than done as I'm also plagued with anxieties and phobias, but I never saw interviewing as a stressful situation. At best, you get a job, at worst you forget about eachother in a few days lol.
Surprise, your boss' boss just decided to drop in and is asking your new guy some pointed questions about the deadline. ~Tada~, the IRS is sending someone over who wants to interview a few people. Oops, that lawyer that your clients hired are going around and subpoenaing previous employees.
"So, uh, we need you to tell us your biggest weakness. And bonus points if by the end of your story the entire interview team is crying from laughing so hard."
So ideally, the most interesting bug story response would be a story about how awesome you are at finding bugs that are introduced by other organizations than the one you were working in AND make the listener like you.
* Look this candidate can fix bugs. * Look this candidate knows not to talk about the dirty secrets of the org they are (were) a part of. And is able to defect blame to another entity. * Look this candidate makes questioners like them which will hopefully keep too much scrutiny from being applied to them.
They don't really care what the most interesting bug is anyway, they just want to have a conversation surrounding bugs. You can also turn it to "well, in general [..]".
Also don't be afraid to say "ehm, let me think for a second", instead of feeling obliged to answer right away.
Like write down 5-10 of these questions and answers that are somewhat common.
Write down some anecdote and more or less use the same all the time.
The same with telling about yourself write down 5-10 sentences and use that every time. Of course you probably have to update it from time to time but remember that you don't have to come up with everything on the spot.
You might not get exact same questions but if you have some things written down you can still start by rehearsed anecdote to get yourself going. Because if it is open ended question it might be more important to keep conversation going than "being correct" on your answer.
The recommendation for interviewers is to select a mix between past stories and hypothetical scenarios.
Telling stories about the things you've done is an essential part of human communication, not some weird "game" that hiring managers have come up with to mess with you.
In a very practical sense, if you can't explain things that happened to you it's going to be really hard for you to communicate issue involving solving problems with software.
What does make sense is plan old interview anxiety. Rather than make up stories walk though your resume and just refresh your memory of how projects went, what lessons did you learn from the projects, what was surprisingly easy, surprisingly hard etc.
If I'm talking about these things in an interview, I just repeat stories I've told before but with toned down profanity. On the flip side, I'm super skeptical if I'm interviewing someone and say "tell me about a time when a project didn't go well" and they insist that all of their projects have always gone smoothly, even after I prompt that they to go far back as high school group projects.
"Tell me about a time when you had a conflict with a coworker"
==
"I know you have some stories about great things you've done in your career. I want to hear those stories - that's the whole point of this interview - but I don't know what to ask, so I am giving you a very open-ended prompt, on the assumption that at least one of your stories included some kind of disagreement with a coworker."
edit to add: don't make something up. Besides dishonesty being generally bad for a variety of reasons, it's very likely that the interviewer is better at spotting liars than you are at lying.
I really recommend preparing for them; think hard about your projects, things you've done, why you did what you did, and so on. If you need prompts, I found Amazon's leadership principles (cringy though they may be) to be a good starting point. In fact, having prepared for Amazon's, everyone else's was easy.
Now I ask these questions and it's super obvious when people haven't prepared for them. I feel bad sometimes. I personally prefer them to the hypotheticals, but people do tend to freeze up.
Understandable, given that you are a mere human being.
But if it's helpful, what they're really telling you is: "Look, we're just ticking boxes here. Go home and think up, or just use our search engine to look for a sufficient number of fake, but expected answers to this question. Then re-apply in 6 months."
I think interviews these days expect you to do prep before the interviews. Reciters even give you a list of these before hand. People practice (semi)fake answers to these and get the job.
The only one I see using this is Google on their search website. This is fucked up.
I feel like the only way to properly answer these types of questions is to make up some BS scenario and talk about how you worked to see the other person's perspective, added your thoughts and came to an even better solution than you could have done on your own.
Do people really disagree so much in workplaces? These questions feel like they're training people how to be sociopaths...
I think the correct answer to this is to get on their ass about it or rat them out to their manager. In reality, what I have done is just do their work myself so it gets done.
Pretty sure this is why I failed my Amazon interview.
But there are cases where they may not. I've told my manager that they should probably have a conversation with some people, or even let them go. I don't think that's "ratting" really. Like you already said: it's you who has to pick up the slack, and a lot of the time "underperforming" also means more stress and work for me (usually in the form of cleaning up after them, fixing their bugs, etc.) With some coworkers I genuinely wished they would just stay at home. This gets even worse if the quality (and thus, revenue) of the company gets affected by their underperforming, which also affects your salary, or even the company's survival!
I also try to explicitly praise people in 1-on-1s btw.
1) We had a dev on the team who was adamant that we prefix all testing library functions in tests with their namespace. I argued that it in my experience it was pointless - no team I'd been on in the past ever had an issue with not prefixing them. He wouldn't budge on his stance. When he was on leave I changed all tests in the project, removing the namespace prefix. When he came back he seemed not too bothered by it, he got used to it and never brought it up again. We're still in contact now.
2) I was once brought in as a partner in a startup. They'd failed to make a product and I came in and built what they couldn't do from scratch into a working product in about 6 months. As more people used it the CEO started to become more active in the project. I was creating a new piece of functionality when he told me he wanted it another way. We didnt agree. I suggested taking it to users and getting their thoughts on it, he refused. We ended up disagreeing and then he pulled the "I am CEO card". Following the meeting I tried to understand why he wanted it the way he did and why I wanted it the way I did. I determined that my approach presented three separate bits of information in the graph, and his approach lost one of those pieces of information. I redesigned the UI to include all three parts of info but to look more like he wanted. I ended up essentially being pushed out of the business, he didn't give me any stock that was promised, and he ended up running that project into the ground. His company ended up failing and he's now a PM in some other company I believe...
3) I'm sure there are other instances but these are the two that pop into my mind. Most places I've worked people have discussions - perhaps there are disagreements, but they don't burn into my memory like the last two examples. Emotionally distressing events are much easier to remember.
Not sure how people would take those stories in an interview...
This did not play well during an interview. But idk, am I supposed to pretend I persuaded my boss to my side? Sometimes you gotta do what your boss asks even if you're not super jazzed about it.
Granted, it's hard to very any of that is true in an interview. 90% of people will disagree, then allow themselves to be overruled and then every chance they get rehash the arguments they lost anytime something tangential to it comes up. That's easy to hide in an interview.
I whiffed the Amazon interview more on pure algo problems iirc. It's been a while and I just haven't tried again.
Wish there was a better way.
There was a time my manager ended up convincing me and we did things their way.
There was a time we just couldn't agree and I ended up doing things their way because "they're the boss".
There was a time we ended up putting it to a sort of "vote" for the entire team.
There was a time we made a compromise we could both live with.
There was a time another team member jumped in with an even better solution that either of us thought of.
There was a time I ended up quitting my job because we didn't agree and he was a gigantic dick about it for no reason.
---
All these things actually happened over my career, and no single one accurately describes how I'd deal with a situation where I disagree with my manager. I'd generally answer it like that, although I'd leave that last one out for obvious reasons (there was also a lot of build-up/context to that one that would take ages to explain, and is hard to explain in the first place).
Using the latest version of Firefox on the latest version of Debian Linux. Fuck this page and fuck Chrome.
> Firefox currently has a media.webspeech.recognition.enable flag in about:config for this, but actual support is waiting for permissions to be sorted out.
Once again, Google out in front of user permissions and protections getting finalized in standards bodies.
I suppose a spoken answer gives more realism to an interview simulation, but a simple "Your browser doesn't support speech recognition. You can use Chrome, Safari, or manually type your answers", would have sufficed.
Sigh. Closes tab.
"Do you really want to exit?"
What do you think?
I am disappointed in myself that I wasted small period of my life falling for recruiter/social hype of these companies. Worst mistake you can make while looking for a job is to prepare for one specific company, web is full of this garbage content to answer specific company questions.
That is extremely weird for them to not be intelligent enough to make this firefox compatible.
I think whether or not it's intelligent depends their actual goal
It should definitely be messaged in the UI, but firefox unfortunately wouldn't support this webapp at the moment.
> What devices does this work on?
> You can practice with Interview Warmup on the latest versions of Chrome on OSX, Windows, and Android, as well as the latest version of Safari on iOS devices. Firefox and iOS 14.4 are not currently supported.
I hope people who built this were more aware of the various reputations the Google interview process has had, and made it clear it's not for covering the peculiarity.
(A Google employee, knows nothing about this.)
sign up today get your first hundred hours for free!