24 ms·
Questions to ask a company during a job interview
- deleted 7y ago[deleted]
- a3n 7y agoWhy doesn't the interviewee ever ask the interviewer a whiteboard or puzzle question, "to see how you think?"
- ThePadawan 7y agoI do, and I have excluded companies for the wrong answers. Why would you not? You're taking the risk of wasting a few months until you find out that the fit is poor.
- snow_mac 7y agoHow has that gone over? Did you get interviewers to refuse the question?
- greymalik 7y agoCan you give an example?
- ThePadawan 7y agoTo be fair, I never ask "puzzles" as such. But I do ask things that show if the technical recruiter actually knows what they are talking about. "What strategy do you use to complete Pull Requests?" There are many ways to answer that question that will show you don't know. In general, I ask things that make me see if the other person is reasonable, and I can talk to one-to-one, but also that they make conscious decisions and don't just carry around cruft. This might involve asking "What ORM do you use?", then responding to their answer with "Oh, why didn't you use <other ORM>?".
- dominotw 7y agoBecause unless you are some sort of celebrity engineer, "interview is a conversation between both parties" is nonsense. Company is interviewing the candidate not the other way around, no matter what we like to think. Edit: Sorry I should've clarified. I am specially referring to companies that don't really have to care about your feelings towards their interviews. FAANGs for example. They simply don't care and there are million others who are willing and happy to go though whiteboarding. They just don't have to put up with your stuff. Ofcourse you have leverage when you are interviewing at your local java enterprise shop. But who cares about those jobs, pointless to interview them with your smartass questions, we all know they are pretty much all the same more or less.
- iamthepieman 7y agoThis was true in my first job out of college. After that I definitely was interviewing the company. I've had the fortune to always be interviewing while having a stable job so I never needed the job I was interviewing for and it's wise to be picky if you can afford to be. There's a lot of risk associated with changing jobs and I do what I can to either minimize that or at least know what it is. I've said no to two companies. One because I got a better offer and another because I didn't want to do the kind of work they were doing which was really only evident after going through their sample project.
- chrisweekly 7y agoStrong disagree; it is not always this way. I'm no celebrity, and I flail at adversarial technical whiteboard exercises, but I've been paid well to do software-related things for over 20 years. Maybe in part because I insist on treating every interview as bi-directional. It is not necessary to accept a "please may I have this job" attitude towards a potential employer. Software developers are radically more empowered than many of them (us) realize, and IMHO part of the reason so many corporate hiring processes for technical roles are so brutal is that it reinforces the mindset of subservience and is an effective way to assert and maintain dominance. [In the US some of this is a structural problem tied to larger concerns like health insurance being tied to employment, which tips the scales of power, putting employees in a position where they may actually need the employer more than the other way around...] TLDR if you don't think you're interviewing the company too, you're doing yourself a big disservice and selling yourself short.
- sidlls 7y agoI don't because I think those kinds of questions are just not good signals.
- alistairSH 7y agoAsk their own whiteboard question? That would be strange, as I'm a manager and don't write much code these days. But, if I ask a whiteboard question (or any tech question), asking me related questions as a means to further the discussion would be a good signal.
- fatnoah 7y ago> That would be strange, as I'm a manager and don't write much code these days. I'm a manager that rarely codes as well, but was still asked coding questions in an interview. It's a bit annoying, but having had managers that have never written a line of code ever, I understand wanting to verify that the manager could theoretically do the work themselves.
- alistairSH 7y agoI can theoretically do the work and I certainly understand the technical problems my teams are solving. I'd happily write some pseudocode to prove I know general things, but asking me to write the fastest version of X isn't going to prove I can manage people. Heck, that's not even a good question for most developer positions.
- fatnoah 7y agoFWIW, I recently interviewed for a manager role and there was a coding element. It required a small amount of cleverness and some knowledge of basic data structures. It felt appropriate to me, at least to establish that I would have some clue about how things work. That said, it was the only one of my four interviews that actually included any coding.
- noarchy 7y ago>Ask their own whiteboard question? That would be strange, as I'm a manager and don't write much code these days. I don't write much code on a whiteboard, so that makes two of us. But I agree that having a discussion about such problems can be productive. It may help separate legitimate problem-solving from mere hazing.
- rocqua 7y agoBecause the coding ability of one employee is not a good reason for a candidate to refuse or accept an offer.
- arethuza 7y agoIf that employee is doing the interviewing of someone who is being expected to write code then I would say it does indicate something about a company.
- theamk 7y agoDuring the last interview, I've had similar thing happen to me -- after we discussed whiteboard design question, the candidate asked, "how would you solve this?". This resulted in a pretty nice exchange of opinions. In a somewhat related point, last time I was designing the coding question, I tested it on my teammmates. They all solved it, and their response was very helpful, and it allowed me to clarify some points in the problem.
- dominotw 7y ago> They all solved it But did they all solve in under the interview conditions? ( time pressure, coding infront of strangers, possiblity of not getting the job that you need etc). I can pretty much solve all leetcodes on my own computer with noone staring at me like hungry wolf eyeing its next meal.
- theamk 7y agoI usually allocate up to 20 minutes for that problem during the interview, maybe extending this to 30 minutes if they are not doing too well. My goal was that the co-workers solve it under 10 minutes -- that 3x length factor is trying to compensate for harsher interview conditions. As for leetcodes -- I just looked at the site, and my interview question would be rated 'easy'. In fact, I'd say that most of the 'easy' questions there are too hard for the programming interview.
- dominotw 7y ago> My goal was that the co-workers solve it under 10 minutes do you have an example of this? I have hard time imagining solving algortihm qs under 10 mins.
- neilv 7y agoBecause it's a poor source of information about experienced candidates, and more about cargo culting and/or hazing. I suppose that briefly turning it around on the immediate interviewer could be constructive, with some people, but I doubt I could pull that off even half the time. My impression, from HN comments and firsthand, is that people still doing it seem to be thinking one-sided about it (i.e., they want to assess and/or manipulate "the candidate", and they seem to assume it's implied that everyone at the company is good). They probably also think this is convention, and perhaps resent or are suspicious of anyone not complying. Personally, rather than turning the tables with the hazing, which can come across as hostile or combative, my natural inclination is to have a candid and thoughtful discussion about it. (Warning: I've had poor success with trying to discuss with people who want to do the leetcode/puzzle-style whiteboard coding hazing. Maybe partly because the conversation only has occasion to happen with people who are still doing it, so it's not a representative sample of the field. I also suspect that, when it's with the more HR/recruiter-type people (not engineers or managers), they tend to not be participating in the discussion in the same way I am, but instead are performing the right head nods, while focusing on their normal modes, such as looking for red flags in what "the candidate" says, formulating how they'll report this, and being careful what they say.)
- koffiezet 7y agoThat's not very useful tbh. If you want to question their technical knowledge, ask for their road-map, what technologies they're looking into to adopt, what their tech-stack is, if and how they plan to migrate their legacy stuff, and their idea of an ideal dream setup. I also ask 'company culture' related questions, my go-to question is ask what the team I would end up in did as a teambuilding event last year, and follow up with who decided the type of event. It tells you a lot on the freedom you'll get, the company's attitude towards people working there, and how healthy the company is.
- PeterisP 7y agoBecause in a two-sided interview the interviewer is trying to evaluate you, but you're trying to evaluate the company and its processes, not the interviewer as an individual. Usually it literally does not matter how the interviewer thinks and what they believe is right, you want to know the actual company policy, which often will not be the same as the interviewer might want to. However, if you're being interviewed by your future direct manager, then you do want to get a perspective on how they think, as their individual attitude towards various aspects of work life will be relevant to you - but usually most interviewers aren't that relevant.
- 2rsf 7y agoHmmm, I did discuss some of the technical questions from the list and I have to admit that it's not easy to make a decision based on them. It's a great start for discussions, and definitely something to consider but your time is limited, the other side will beautify the answer, the same as you do, and you might end up in another totally different team than this of your interviewer. Remember that things tend to be fluid, re-organizations happens often, having a bug tracking system doesn't make bug handling efficient and CI/CD doesn't mean your time to deliver is necessarily short.
- viraptor 7y agoCompletely agree. Would you mind if I stole your second paragraph? (Or could you submit it as a pr?) Those are definitely seeds of conversations rather than something you can 100% rely on. But if you have doubts about the organisation and then hear "no bug tracking, we don't need it" without explanation, then something's definitely fishy. That's one of the red-flag questions. Then again if they don't but have an explanation, maybe there's something really interesting behind it.
- 2rsf 7y agoSure no problem, go ahead and steal it
- acollins1331 7y agoInterviewing the interviewer has been THE best way to get the job. It just oozes a confidence that you already know you're good enough to get the job, and you're trying to figure out if they are good enough for YOU. Figure out questions before hand that describe the type of good working environments or fixes for bad ones that you've had in the past. The interviewer will quickly shift and try to sell the position to you (harder than normal). It sounds silly, and like something they'd probably be used to by now, but in every case I've done this it's landed me an offer. This is coming from someone who needs to interview well because my degree/experience doesn't usually perfectly line up to the jobs I'm applying for.
- viraptor 7y ago> The interviewer will quickly shift and try to sell the position to you I wonder if that's often how it's perceived on the other side. I love when the people I interview ask me questions. If they're interested in something, not only am I going to answer as best as I can, I'm going to be interested in why you it's important to you. It can be a great conversation, and I'm not even trying to sell the position :-) People really don't do it often enough - that's why I decided to post my own list.
- alistairSH 7y agoThe best interview I ever conducted, the candidate not only aced the technical questions, but was able to ask solid follow-up questions on those topics. "I solved it this way, what would you have done differently?" "This solution was quick to write and simple to understand, would you prefer a more performant solution?" And during the "social" part of the interview, he asked detailed questions about the company and our niche, not just generic "how big is the team" stuff.
- dver 7y agoDid they get an offer, if so did they accept?
- 7y ago
- CalRobert 7y agoThat's a really good list. I really wish I'd asked a few of those in the past. "Where do you plan to be in 5 years" is actually a really good question to ask a company. Many have no idea (which is possibly fine, but good to know) Interviews can also be a fantastic place to get real feedback - but you have to do it during the interview; almost nobody gives real feedback after the fact. "What would give you concerns about hiring me?" "If you could have your dream candidate for this role, what would they look like?" "What in my application caused you to call me in for an interview?" Are a few that I've found helpful.
- alfiedotwtf 7y agoFor early startups, these are important: - Are you profitable - If not, how long is your runway
- tomekowal 7y agoI would change the part: ``` Do you use source control? Do you test code? Do you use bug tracking? Do you use CI/CD? ``` to ``` How do you use source control? How do you test code? How do you perfrom bug tracking? How do you solve CI/CD? ``` For really good companies asking if they test code seems insulting :P
- viraptor 7y agoGreat suggestion. Feel free to edit the readme :-)
- wastedhours 7y agoThat also moves the question from being closed to being open - potentially leading to a secondary question that will highlight your ability to ask insightful Qs.
- rvz 7y ago> For really good companies asking if they test code seems insulting :P Well that's the general expectation anyway for 'tech companies' to be testing and adopting best practices these days. There are even companies nowadays that are tech enabled with apps, engineering departments, etc and they call themselves 'tech companies', but they don't have any tests, code reviews or a CI and take the shiniest tool for the job. So if I was interviewed at any company, startup or large corp for a software engineering role and they don't have any of the above, I would gently terminate the interview. Imagine if hardware engineers were to tell us that they don't do verification or tests on components that they ship.
- scarface74 7y agoIt depends - I know plenty of companies that believe in the Mechanical Turk style of testing - just hire more QAs (usually outsourced). If they are okay with that, I’m not going to push back.
- ryandrake 7y agoBut for the bad companies, the answer might really be NO and you want to avoid them! I joined a place once without any of these. No source control, no bug tracker, no QA or testing, failing builds were the norm, and people worked to make things compile just before releases happened. Releases, by the way, were cut from whatever happened to be on the lead developer’s workstation on the day the Eng manager decided to release. It was a circus. As much as we’d like to believe tech shops are at least all run by grownups, things like source control and working builds are NOT to be assumed!
- codingdave 7y agoI'd focus your questions to only the ones where answers might make a difference as to whether you accept the job. Are you really going to turn down a job because their on-boarding process isn't optimal? Or to a bad tech answer... would you turn down the offer, or help them improve from the inside? I do like this list, but filter it down to what you need to respond to an offer. And that filter will be different for everybody. Typically when I am in an interview, I explicitly draw that line with the interviewer, saying, "I have more questions, but I also have the answers I need to make a decision if you extend an offer, so we can get the rest answered later if we move forward together."
- viraptor 7y agoTurn down an interesting offer because of onboarding? Maybe not. Choose between two roughly equivalent companies, because one has a good onboarding process which likely means both investing in growth and caring about documenting things for people who didn't have lots of existing context? Definitely possible.
- codingdave 7y agoGood point. Like I said, everyone's filter will be different. There are probably valid reasons to ask every question on the list. And also valid reasons to skip every question. We all have different goals and preferences with our careers.
- protonfish 7y agoOne I am going to start to ask is "Are all developers allowed to have local admin access of their computers?" I've struggled against this in my last 3 positions. This is a dealbreaker for me, and should be for all developers.
- kemiller2002 7y agoI agree. I have never been at a place where developers don't have admin access and seen development be successful in anything they've created. This seems to be a decent indicator of overall culture towards development and removing obstacles to getting things done.
- relax88 7y agoFrom an infosec professional perspective, this one is always a challenge for security sensitive places. I agree with you that developers need admin rights on their development machines, but I have witnessed first hand why many companies attempt to take away local admin rights. When I'm responding to security alerts where developers have downloaded random .dll files from the internet, or some "troubleshooting utility" that is actually malware, it doesn't take long until the local admin conversation comes up. This is one of those classic "technical solutions for bad human behaviour" scenarios where a small number of idiots ruin it for everyone. If you want local admin as a developer, then we need to be able to trust that you aren't going to do something stupid. It seems the best way to do this is to issue developers multiple boxes (corporate laptop + dev box only for dev), and or use a good software whitelisting program that tracks elevations & the reasons for them, instead of just blanket giving everyone local admin on their own PC.
- chii 7y agoi wonder if making the development machine use something similar to qubes (https://www.qubes-os.org/ https://www.qubes-os.org/) by default works. Also, if a compromised machine on the internal network destroys your company's security assumptions, then there must not have much defense in depth.
- 7y ago
- CalChris 7y agoThere is a question about funding. So I'll assume the company is a startup at some stage. But I'm surprised there aren't any questions about stock.
- viraptor 7y agoActually it wasn't supposed to be about a startup only. Established companies also grow through external funding, whether it's a loan, partnership, selling shares, or something else. Each of those may change how the company works and whether you're comfortable working that way.
- CalChris 7y agoNot only. But if you’re going to ask about runway then some intelligent questions about stock are in order.
- sanj 7y agoFor many years I gave a talk titled "Questions Engineers Should Ask" This list is missing the two most important [busines] questions: 1. How do you make money? If you can't understand, or the interview can't explain, then I'd run away. This can also lead to interesting questions about risks, competitors, etc. 2. What's preventing you from making more money? The answer that you want to hear is engineering effort. If not, you're (at best) a wallflower at the party. Don't be the chump that's at Goldman Sachs acting as a code monkey for the traders. Don't be writing code at a company (like Enron) which has its success based on digging holes in the ground. I can dig up the slides if anyone is interested.
- viraptor 7y agoI'd love to include those questions with links to the talk if you can find it! (Like the siblings comment, I may disagree with "The answer that you want to hear is engineering effort", but the questions are definitely valid in some situations)
- opendomain 7y agoI would appreciate it as well. Thank you!
- uniclaude 7y agoThat's highly disrespectful to software engineers working outside of software companies. There are many of them and they are not necessarily less smart than others. Working in the profit center of a company is often enviable, but let's not forget that cost centers in large companies can also offer benefits in things like work/life balance.
- smashface 7y agoI don't think the GP intended to call engineers at those kinds of companies lesser. I think the point that was made was that working at companies where the company makes more revenue by having better software is a better company to work for. If your role is a cost you're treated (explicitly or implicitly) as such. It's a lot easier to show your value to a company by being part of the revenue side of the equation. Reducing costs is great but there is a bias towards investing to generate revenue vs investing to reduce cost.
- okaleniuk 7y agoI think, the "source control question" comes from the Joel Test which is 19 years old. Almost every company uses source control now so it doesn't make as much sense. A better question would be "why do you use [the source control they use]". The answer, if coming from a knowing person, may tell you quite a lot about how the technical decisions are taken in the company.
- nitePhyyre 7y agoAlmost is the key word there. Although I would say that "what source control do you use?" is important also. Cause if the answer is "source safe" or something like that...
- james_s_tayler 7y agoYeah, I'd avoid a TFS shop too.
- mcv 7y agoThere was definitely a time when that was an important question, because the answer could be "CVS", "nothing" or even "what is that?". Nowadays the answer is practically always "git".
- okaleniuk 7y agoIndeed. But why git? I worked for 3 companies that adopted git for completely different reasons. The first was open sourcing parts of their code so they just started using GitHub. Makes sense. The second used to work with Subversion, and they stayed with it. The process was built around having one and only one server with all the CI, and the hooks, and the locks. Git was used with the SVN gate purely for developers' convenience. Makes sense. The third one was on TFS, and they couldn't quite align their process with it. So they thought "our process is a mess so let's do git". This is a red flag. If you can't get your process straight with relatively simple tool, some more sophisticated tool will (and it did) only make it worse.
- 7y ago
- wodenokoto 7y ago> Is there a support / marketing / other call-heavy team close to my new team? What does that mean?
- smashface 7y agoI assume the author meant that since those teams will be speaking a lot to people as part of their daily work they add a lot of ambient noise to a workplace. That could matter to some people in open office plans or cube farms where you can't separate yourself from that noise.
- viraptor 7y agoThat's it. "Is the office loud" is subjective. "Is there a team handling calls a few metres away" has a simple objective answer... usually.
- woodrowbarlow 7y ago"will i be listening to people answering the phone all day, every day?"
- jfb 7y agoI am now a Mr Manager Person, so I have a different but related set of questions: 1. What is the demographic breakdown of the engineering team? And, what does the company affirmatively do to foster diversity? 2. What resources do the founders have available — investors, board, mentors, for instance — to help them as the company grows? 3. What is the near term vision for the company? 1yr/5yr? 4. What resources are available for professional development for managers/directors? 5. At $CURRENT_COMPANY, the company is serious about reviews upwards — as a manager, my direct reports are consulted in a formal process at review time. Is there a similar process at $POTENTIAL_EMPLOYER? 6. What is the cadence and process for reviews?
- corey_moncure 7y agoWhat does "diversity" mean in your question #1 and how is it relevant to successful outcomes?
- jfb 7y agoDemographic diversity, diversity of backgrounds, diversity of experience. Monocultures are actively destructive of successful outcomes, and lead to miserable working environments. The question is asked open-ended in that fashion because I want to discover what a potential employer thinks is important.
- james_s_tayler 7y agoWhat about if you're a hiring manager for a software company in Japan or Korea?
- jfb 7y agoI'll cross that bridge if I come to it.
- mttyng 7y ago> What's the on-call plan/schedule? (what's the pay for standby and call-out) I’ve never been in a position where we were paid for on-call (i.e. fix prod at 2am) work. Is that not typical?
- viraptor 7y agoI've never been in a position where I've not been paid for each call out. (And only one place which didn't pay for standby)
- mttyng 7y agoWhoa. That gives me pause. It makes absolute sense, but it never occurred to me.
- viraptor 7y agoI'm lucky though. I see recurring conversations about it on /r/devops and I'm aware not everyone is in the same situation. Some even wear it as a badge of honour that they improve reliability so they shouldn't be paid for things breaking. (Which I completely disagree with) But working after hours is working after hours - if it doesn't feel right, maybe you should have a conversation about it.
- bri3d 7y agoWhen I have seen this done, the amount is often inconsequential in relation to the amount of effort to be on-call. I don't love this incentive structure because the cost of being on-call is somewhat fixed up front. Needing to avoid being out of page coverage / availability and having a computer available is a high cost paid by the employee regardless of actual page-out workload. Paying for standby certainly helps, but I haven't seen standby pay match well with the perceived effort. Maybe some companies do this right, but higher negotiated upfront pay has appeared more effective in my experience.
- saint_abroad 7y agoWhere devops works is that there's shared call-out responsibility when things go wrong at 2am. It won't happen again because they'll take the time to fix things. If management don't also share in the responsibility, it -might- will happen again because they won't allocate the time (and-a-half) to fix things.
- worldexplorer 7y agoData science version of this is highly required and must be asked with every company one is supposed to join.
- viraptor 7y agoI'm not familiar with that environment, but if you have specific questions - there's always space for more sections :-)
- dswalter 7y agoThere are a bunch of questions that attempt to proxy how mature the data pipeline/data engineering is of the company you're looking at. * Do you do batch and/or streaming computation? * What kind of access do you have for querying/accessing the data this role will predominately be working using? * Do you have dedicated data engineers and data infrastructure people * What's your workflow orchestration engine? * What is the data access pattern for historical data (there had better be at least SQL access here). * Do you have built-in feedback loops for your machine learning products? * What is your serialization format of record for production and for OLAP? * How often do schemas change in your databases?
- harimau777 7y agoA problem that I've had is that every company says that they value code quality, emphasize developer growth, value developer's technical feedback, etc. even if they don't in practice. I've debated taking a page from old school behavioral interviewing and asking questions like: Tell me about a time that you made a decision to improve code quality or architecture at the expense of a deadline. Tell me about a time that you invested resources into an engineer's technical development even though there would be no immediate, short term benefit to the company. Tell me about a time that you pushed back on a decision from business or design because one of your engineers said that it was the wrong technical decision.
- reallydontask 7y agofriend of mine joined a company that in theory checked all the boxes, in practice, none. Extreme case but ...
- RobertDeNiro 7y agoNot that extreme. Interviews are meant to ensure candidates aren't lying on their resumes, but nothing is done to ensure companies aren't lying too.
- rat9988 7y agoI'm pretty sure you can leave in the first weeks easily in most countries.
- freedomben 7y agoSure, but then you've lost out on other offers that you may have declined, and you're back to unemployed.
- WorldMaker 7y agoIndeed. The labor market is quite illiquid from the point of the laborer, with a lot of ugly sunk costs and worse opportunity costs. There's not enough safety nets if you buy the wine-and-dine sales pitch but find the reality is a lot more of a lemon than you were sold. (There are no lemon laws for the labor market, sigh.)
- dnl_pozzobon 7y agoI'm slightly bothered by the "reverse-interview" concept. To me interviews should be bidirectional you are there to find out about the company as much as they are there to find out about you. It should be treated as the starting phases of a negotiation where you gain information about the value of the asset you are going to acquire. I'm certainly happy that viraptor shared this valuable resource, don't get me wrong, every little step in the right direction is a good thing. I simply would have liked it to have a better name in order to convey a different message.
- viraptor 7y agoIt's very much a tongue in the cheek name. I completely agree with the bidirectional conversation idea, but wanted to concentrate on the part I found lacking. I'll improve the introduction to make it clearer.
- AmericanChopper 7y agoInterviews already are bidirectional, even if the interviewer thinks they’re not. If you’re so keen for the job that you don’t ask any questions, then you look a) desperate and b) like you’re trying to bs your way through the interview, which isn’t great. My only objection to these questions is a some of them are essentially negotiating the terms of employment, which isn’t appropriate for most interviews.
- jrjarrett 7y agoHow much annual / personal / sick / parental / unpaid leave is available? This is a great question; when I have searched for jobs, it's one of the more important benefits to me. Sadly, however, I've found most places have gone to "PTO" -- combining time off for illness and vacation into one bank -- how have others successfully negotiated an appropriate level of time off? (Context: For a very long time, I worked for companies where sick time was essentially a non-issue; it was essentially unlimited, with appropriate rules around requiring a doctor's explanation or having to switch to short-term disability after a protracted period, but the occasional day or two to recover from a cold and not spread virus to the whole company without having to choose between that and visiting family.)
- iamthepieman 7y agoI just tell them how much time off I'll need during salary negotiations. I know you offer two weeks PTO and 3 weeks after 5 year, 4 weeks after 10 years etc. But I'm not restarting my PTO every time I switch companies. So I will come in with PTO equal to my experience at a minimum.
- psim1 7y agoHas this approach actually worked for you? In all places I have worked, PTO is a non-negotiable, other than "I already have this vacation/trip lined up for two months from now and require the time off," which is okayed even if it's outside of their normal new-hire policy.
- iamthepieman 7y agoYes, I negotiated an extra week at my current job and my last one.
- scarface74 7y agoPTO is nothing special. It’s just another benefit you can place a monetary amount on. If they won’t give you more than two weeks paid time off and they will let you take unpaid time off, add the amount that week of unpaid time off is worth to your required salary - of course take into account that PTO is a non taxed benefit. I feel the same way about 401K matching.
- reallydontask 7y ago> Is there a support / marketing / other call-heavy team close to my new team? This is so important. I can probably live with most open plan set ups, sure there will be annoying times, but if there is a call-heavy team nearby, forget it. I refuse to wear noise cancelling headphones all day long. FWIW, interviewers will blatantly lie. I asked at an interview about equipment quality and was told that they'd not heard any complaints. This was 100% bullshit. I was given an ancient laptop, which seemed to re-ignite complaints about the quality of the equipment and were taken up with, none other than my interviewer.
- Diederich 7y ago> I refuse to wear noise cancelling headphones all day long. May I ask why? Even when I work at home alone, and there are no stray noises at all, I'll still wear my headphones when I want to really focus. Years of mental conditioning has led me to a place where it's much easier to deeply focus when I'm wearing headphones listening to white noise.
- viraptor 7y agoNot the op, but also wouldn't wear them. Weird ear shape means earbuds start hurting after a while, while the over-ear solutions make me sweaty/uncomfortable.
- matneyx 7y agoNot to mention earrings -- I've yet to find headphones that I can wear comfortably for a couple of hours that won't leave my piercings sore.
- damontal 7y agoNoise cancelling, at least the Bose version I've experienced, gives a feeling of pressure in the ears. I've read that others experience this, though obviously not everyone. I can only handle it for short amounts of time before I'm tearing them off my head.
- jrootabega 7y ago
- exabrial 7y agoI'd love to ask, "Why do people quit?" during an interview, but can't think of a way to phrase it without sounding accusational or pretentious.
- AmericanChopper 7y agoWhat’s wrong with the way you phrased it there?
- CPLX 7y agoI think asking something like “when people don’t work out and end up leaving the company what are some of the typical causes of that mismatch?” wouldn’t raise a red flag.
- exabrial 7y agoThat gives the interviewer a reason not to say 'well we messed up'
- saint_abroad 7y agoI always ask about staff turnover numbers, especially in ratio to new hires. If they're not prepared to discuss or don't know the answer then it's not important to them.
- james_s_tayler 7y agoI remember in my first job interview I asked "have you ever hired someone who didn't work out?" I got a genuine and thoughtful answer. It helped me to establish quite clearly what value systems wouldn't fly in the company which guided me on how to behave. It worked out well. Essentially you're trying to figure out "if you hire me and what is true about me then things won't work out?". You want to know if you have those qualities. If you do, you shouldn't accept an offer if you get one. It's a reasonable and good question. I've known excellent people flame out in weeks because the companies values just didn't match their own. They weren't bad employees either. It was just a difference of opinion.
- kostarelo 7y agoI wrote this[1] a few years ago. Since then I changed these questions quite a lot (I need to write a new post) but the concept is still the same. Whenever I'm going to interviews I never go as I will be the interviewee. For quick reference: - What will my job be? At first and after few months? - What is your work policy for employees? - Software/hardware that I will get? - Can I participate on/run side projects? - Is there a budget for conferences, further education, bonus? - What is the history of this company and how do you see the future? - Will you measure my productivity and how? [1]: https://kostasbariotis.com/interviewer-vs-interviewee/ https://kostasbariotis.com/interviewer-vs-interviewee/
- oe 7y agoI created a short questionnaire with TypeForm that asks some of these questions and linked it to my LinkedIn profile. Now any recruiter either answers ten or so qualifying questions or skips the questionnaire and goes straight to trash for not even reading my profile.
- jcadam 7y agoProblem: Interviewers lie. I once interviewed with a company that brought me into a new, shiny, well-appointed building on the corporate campus for an interview. I did well answering their questions. And they answered my usual questions correctly. Stuff like "Can developers here choose their own tools?" and "My title is going to be Lead Engineer, will I actually be a Lead Engineer?" After I was hired, I found out everybody uses Eclipse, no exceptions, and I was absolutely not going to be leading anything (I was basically going to be used like an overpaid junior engineer). The best part: "Oh, you won't be working in the new building..." and was taken to an old, windowless, leaky, mold-smelling building with peeling paint and flickering fluorescent lights (think the opening scene from "Joe vs the Volcano"). My office was a supply closet that was being converted into an office (by that I mean, "we just pulled most of the stuff out of here, but otherwise just rearrange the furniture however.") I was given an old 70s vintage desk that was too low, a sort-of broken chair, and a laptop and left to my own devices for three weeks while waiting for my new project to get started. Then I was suddenly moved to even worse accommodations - a cubicle, which belonged to an employee who had recently died (his stuff was still there, and it was a month before anyone came to take it away). I started looking for a new job about 2 days in. Took me a year to find something else (I eventually had to move to a new city).
- neogodless 7y agoAt first, I was like, it's crazy that this company did this. And then as I was reading through the description, I realized this actually happened to me. It wasn't identical, but there are similarities. First, the project was described as "green-field, we're doing cool stuff writing MVC apps from the ground up." I was assigned to build SSRS reports. Second, the shiny building with the sales people, recruiters, executives - I did work there, on a second or third floor, corner office with windows! For about a week. Then I was moved a mile down the road to the building they got through an acquisition. I was on the ground level (I think?) and I had a whole office! But the office was small, dark brown and had no windows. Even the door was solid dark brown. (The office wasn't all that old or terrible - the kitchen was kind of awesome. But the actual area where I worked was pretty dreadful.) I don't exactly feel like it was intentional, or at least, it didn't occur to me at the time. But looking back, of course they didn't want to highlight that they really wanted someone to grind through reports. And they clearly didn't intend for me to spend my time occupying a corner office with windows! I was there for about 4 months.
- SamuelAdams 7y agoI'd like to see a section specific to large projects. It's not uncommon for companies to hire for specific projects, especially in the contracting world. ERP, SAP, and other projects come to mind. Something I wish I asked during my last big interview: Do you have a project schedule? Can you show that to me? If there is no schedule, or a very ambiguous one, that's a big red flag.
- destitude 7y agoWhat affects does it have on a company to not hire ANY junior level developers?
- viraptor 7y agoOne effect I'm familiar with: lack of documentation. Everybody is experienced with the system, everybody knows how things work... until they don't. Having someone around to ask the simplest questions and prompt for explanations is very healthy. Another is that people with lots of experience know and rely on straightforward, correct, reasonable solutions. It sometimes takes a someone new to say "why don't we try X?". Finally, sometimes there's just work to do, not new things to figure out. If everybody is senior but lots of work is pretty basic, at some point they'll get bored and leave.
- jeygeethan 7y ago"Definitely don't try to ask everything from the list." ^ I wouldn't agree to this. If the interviewer can ask many questions about my working style, why can't I ask the same about the company with whom I am going to spend the most of my daylight with?
- viraptor 7y agoIt's more about "choose what's important to you and respect each other's time". Not all questions will apply to a company. Many of them you can answer by reading company's website/blog, maybe looking at public repositories. If you ask something that shows you did no research or don't understand the role description at all, that's actually going to count against you later. Same for holding someone busy with simple questions if you had a scheduled interview slot.
- Diederich 7y agoI've been interviewing with Google since 2006 or so, off and on, though I've never accepted an offer from them. I do this because I always learn several things from the rigorous on-site interviews, it's a lot of fun, and the machine that runs the process seems to not mind being turned down in the past. Back in the beginning of that time period, I used to ask (fairly jokingly) the same question: "How many servers do you have?" I would use the response to gauge the interviewer, and mostly just for fun. Of the dozens of Google interviewers I've spoken to over the years, only one responded with a number range, and the rest of the responses were largely grouped into either active playful discomfort. In my last two rounds of interviews (with various companies, including Google), I asked three questions: 1. What brought you here? 2. What keeps you here? 3. What keeps you up at night? The responses to those three have been illuminating.
- baddash 7y agoWhat were the responses by Google to those three questions?
- Diederich 7y agoOf course, Google didn't answer my questions, people who were working at Google at the time did. (: As to the specific responses, I'd have to check my old notes, which I don't have handy at the moment. For "tier 1" companies, such as Google, common responses to "What brought you here" and "Why do you stay" are excellent comp, being able to work with many very talented people, and the ability to move around in the org. I've found the "what keeps you up at night" question has the most diverse responses. In general, I've been pretty surprised at the amount of apparent honesty I get. It's hard to verify the responses, of course, but any time I get a response that's not completely positive or 'canned' in some way, it seems pretty legit.
- arikr 7y ago> I've found the "what keeps you up at night" question has the most diverse responses. > In general, I've been pretty surprised at the amount of apparent honesty I get. It's hard to verify the responses, of course, but any time I get a response that's not completely positive or 'canned' in some way, it seems pretty legit. Could you please give a few high-level examples?
- destitude 7y agoHas anyone tried to get the company they are interviewing for to provide written and signed answers to any of their questions relating to the company or job? Maybe even have ramifications if what was written turns out not to be true? Seems like this is the only way to keep companies from falsifying everything they say just to get a hire.
- z0rn_3301 7y agoDuring interviews I really like to propose a reversed interview. Usually I can identify faster a high potential from a benefit seeking hooker. Thx for sharing tho
- k__ 7y agoPro tip: Get the stuff that is important to you into the contract!
- rajacombinator 7y agoI tried this in my last round of interviews. It is very difficult to get any meaningful information from this process, because, just like candidates, interviewers are incentivized to not tell the full truth. Except in the worst cases when the interviewer just dgaf, they can’t really share negative information for fear of reprisal. (And it doesn’t benefit them either.) Your best bet is to ask a question that allows them to answer honestly, without sounding like they are answering negatively. The problem is it’s hard to come up with such questions.
- megous 7y ago"If I was hypothetically a person that likes to refactor/maintain confusingly tangled mess of a code, would I enjoy working here?" :D
- weliketocode 7y agoThe phrase 'hiring is broken' seems to have become synonymous with companies improperly judging candidates. BUT! This problem pales in comparison to the difficulty involved for candidates trying to judge companies. Now, I won't go as far as some of the other posters here and point to rampant deceit. However, interviewers will generally try to be positive, and it's very difficult for an interviewer to say "don't work here".
- dinsjg3434 7y agoSee the point is sometimes you need to choose between 1. Ape Shit company . 2 Stinking Bat shit company 3 Piles of Horseshit company ;-) Sometimes people make choices out of necessity. To escape your worst nightmare bozo boss to get a short term reprieve.
- Beldur 7y agoIn my experience it's important to not ask "easy" questions that can be answered by a simple yes/no. Instead of: Are you friendly to remote work? Ask: Will I be working with anyone who is remote, or who works from home on a regular basis? Instead of: Is the work life balance good? Ask: How responsive are people to emails/Slack over the weekends and after 6pm? Instead of: Can I have a good career path? Ask: Did any of your senior engineers start out as junior engineers here?
- rhizome 7y agoI've never asked it yet, but I've been thinking along these lines, and for the last one I think a good construction is "Do you work with anybody who was hired under a different title than they have now?"
- kempbellt 7y agoI like this method of inquiry. You would probably make a good investigator.
- ram_rar 7y agoI love this method of inquiry. Feels like you're genuinely probing into the company at the same time getting answers to your questions.
- nsilvestri 7y agoI disagree with the career path question. Rising within the company does not necessarily mean that the same skills are effective at other companies.
- deleted 7y ago[deleted]
- peterwwillis 7y agoOP: I am too lazy to file a PR, but here are some of my questions, feel free to use as you wish: https://pastebin.com/7ztvPwnY https://pastebin.com/7ztvPwnY
- ensiferum 7y agoLet's be honest, most developers are not in capable of performing at interviews at such a level that they can actually get to "choose" where they want to work. They get one offer out of a round of interviews and that's and you either take it or leave it.
- apocalyptic0n3 7y agoOne thing to note with these is that they seem to target companies/jobs where you will work on a single product/suite of products. A lot of these questions would be out of place in many agencies or the interviewers would not have answers or the answers would just not be as good as you would expect from a more focused team. Of note: - What does the onboarding look like? In large part because of how rapid development is in agencies, how often you change projects, and how small agencies tend to be, onboarding is often non-existent beyond showing you the software they use and showing you how to set up your Vagrant or Docker. Most of it is on an as-needed basis and you'll be given the information you need for each project you work on, thanks in large part to how ad hoc each job can be. I've experienced this myself at all three agencies I've worked at, I have friends at two others who say the same thing, and it's what I was told to expect in school. - How do you test code? This will almost always be "put a dump in the code and see what's wrong". Agencies don't often unit test and because of how often they switch projects, having a consistent debugging environment is often more trouble than it's worth. You should still ask this, just don't expect the greatest answer. - How do you integrate and deploy changes? Is it CI/CD? Due to the quantity of projects, this will often be "no" unless the agency primarily focuses on larger, months/years-long projects. For the most part, clients don't want to the time it takes to pay for automated tests/deployments and often don't host with you anyway, so it's usually either "run a git pull and compile assets" or "package the code in a zip and send via Dropbox". - How do you prepare for disaster recovery? Disaster recovery is often an after thought at agencies. Usually the disaster recovery is "spend a few days restoring backups and eat the costs". Unless you are interviewing for a security or senior position, this question doesn't really make sense to ask at an agency anyway as you are unlikely to be involved in any recovery. - How quickly can you respond to security issues in the code or dependencies? Because everything is paid for by the clients, if they don't pay for it, they don't get it. Don't expect much more of a response from your Agency interviewer. If you get an intricate response, I would suspect it's exaggerated. There are exceptions, but agencies don't make money making sure the sites and apps they build are up to date, unless the clients want them to be (and most clients do not see the value in it) - What's the product/service schedule? (n-weekly releases / continuous deployment / multiple release streams / ...) Again due to how many projects you work on regularly, this may not get a good response. Maybe a "Our Wordpress sites take 2-3 weeks to build, 1 week to test and fix, and 1 week for client review" type response, but anything more standardized than that likely isn't happening. - What are some ongoing challenges the team is experiencing that you are yet to resolve? This one also likely won't get much of a response due to how many projects there are and given that most of the team is working on different things than their neighbor. - What's the promotion process? How are requirements / expectations communicated? - Is there a separate tech and management career path? Agency structures are generally really flat. 1 guy at top, maybe a few seniors below him, then everyone else (but everyone, including the seniors, report to the 1 guy at top). Don't expect promotions, but raises will happen regularly. You can ask this one, but you'll probably be more interested to hear when/what to expect from your raises (agencies are often generous in this respect) - Are there any company-wide resources for learning available, like ebooks subscriptions, or online courses? Regardless of company type, know that this will depend entirely on company size. If you're interviewing with a 300 employee company, you should expect it. If it's a 10-40 person company, you probably shouldn't and it may not be worth asking and may make the interviewers think you're looking for something they aren't providing. - Can I contribute to FOSS projects? Are there any approvals needed? This is a GREAT question to ask during the interview if you are hoping to work on FOSS. Agency rules on this vary greatly and it's one I personally like hearing from candidates. - Are there any non-compete or non-disclosure agreements I'll be asked to sign? Another great one to ask simply because you will work on so many different projects from so many different clients from so many different industries. My previous employer tried to get me to sign one saying I wouldn't work with any competitor of their customers for 3 years after I left. That would have killed my ability to find a job at another agency afterward. It was part of the reason I quit there. My current agency is basically "Don't talk about specifics that may be confidential during development, don't steal our customers after you leave" which is more reasonable and acceptable. - Are you profitable? (+ the other financial questions) If your interviewers are developers at an agency who don't also own the company, they likely will not know any financials specifics - Remote Work If this is important to you, make sure to ask about it in the interview. It varies greatly from agency to agency. I interviewed at a place that only expected you be in the office once a week and work from home 4 days a week. My current place prefers if you keep the remote work to a few days a month at most.
- matneyx 7y agoI -just- started compiling my own list as I head back out to find a new job. This will be so helpful!
- longcommonname 7y agoHow often do you load to production? What's a project here you are most proud of? What was your last prod issue, how was it observed, how long to resolution, what changes did you implent to help going forward? These are sre focused, the first one indicates if sres are toil driven or overloaded. The second shows that you have agency as a sre and can have a positive impact. The third goes into their culture around mistakes, monitoring and on call.
- EnderWT 7y agoI'll give a shoutout to https://www.keyvalues.com/culture-queries https://www.keyvalues.com/culture-queries where questions like these are explained in more depth, for example: Can you give me an example of a mistake you've made here, and how it was handled? Ideally, your interviewer will answer honestly. If people are comfortable discussing big failures, it suggests that the company has created a safe environment for people to fail, and signals that it’s an environment conducive to taking risks and experimenting. On the other hand, if people are guarded when it comes to discussing failures, they might be working in a culture of blame. You can follow up by asking about their practices around investigating issues, writing post-mortems, and overall documentation.
- quotemstr 7y agoI use the comment test. It's pass/fail and goes like this: "Suppose I'm reading some code and I see an obvious typo in a comment. What's the process for fixing it?" (Note: I've actually gotten all of these answers, albeit sometimes only after I joined a group (prompting me to develop this test in the first place)). Fail: "just edit the file lol" Pass: "edit the file and check it in" Pass: "edit the file, send a diff, get a +1, and check it in" Suspicious: "edit the file, send a diff, get your code and style approvers, wait for presubmit, and check it in" Hard fail: "file a bug..." WTF are you even doing: "we can focus on code quality issues after this milestone"
- protomyth 7y agoRemember to ask about 'code lockdowns', some coding jobs have seasons of a sort.
- agumonkey 7y agoI asked about turnover on the last one, recruiter wasn't at ease. Is it a lack of tact on my side or were they hiding something ?
- Wildgoose 7y agoI usually like asking what their staff turnover is like. It was very telling many years ago when I was told "very low, almost non-existent" and then promptly learned from my new colleagues that it was extremely high....
- muttled 7y agoI wonder if you could ask something like "Do you have going away parties for departing employees?" Can be very telling.
- jupiter90000 7y agoAsk a question like "Given a non-negative integer numRows, generate the first numRows of Pascal's triangle." If they can't answer without using Google I end the interview as they didn't pass the round. :-)
- kempbellt 7y agoI'm not sure if this is satire. Sounds like it may be, considering your emoji. Getting asked questions like this, in most cases, is enough for me to end the interview. I don't want people who can cite off memorized answers to random questions. I want driven people who are excited to learn what needs to be learned in order to push the company forward and make work a fun place to be. Confident people can learn to solve difficult problems on the fly, with ease. This is more valuable than being able to recite a textbook answer during an interview. One of my favorite interviews of all times: Interviewer: "Hello. I have your resumé in front of me. I am going to ask you a bunch of questions in rapid succession, and I just want yes and no answers. Are you ready?" Me: "No." Interviewer: "Excuse me?" Me: click
- neilv 7y ago> What's the status of / view on diverse hiring? As someone who believes in value of diversity (just to be clear), for both organizational and societal reasons, I think this is an important question, for a variety of reasons -- but also a question that candidates might not want to ask. Candidates might not want to ask, due to not knowing how the asking will be perceived. Or due to not wanting to mention some unapparent quality (e.g., being gay), because they don't know how welcome that will be, or they just want to be treated as, say, a developer, at that stage of meeting prospective colleagues. It's much better if the company communicates its real policies/practices/culture and status proactively (beyond the standard HR equal opportunity statements), so no one has to ask.
- umvi 7y agoIt could also be asked for the opposite reasons. For example, some developers might consider it a "red flag" that companies prioritize diversity hiring and will want to stay away.
- kristianc 7y ago> Candidates might not want to ask, due to not knowing how the asking will be perceived. Or due to not wanting to mention some unapparent quality (e.g., being gay), because they don't know how welcome that will be, or they just want to be treated as, say, a developer, at that stage of meeting prospective colleagues. Wouldn’t it be much better to be aware of this at the outset?
- PorterDuff 7y agoSo, am I actually going to start laying down track for this new product you hired me to do? or are you going to kidnap me to work on legacy software emergency patches the second I walk in the door? An invaluable question if honestly answered.
- kempbellt 7y agoWhy should I work here? It's a forward question, but your time is valuable. If you are going to spend a large chunk of your foreseeable future working at a company, they should have a good answer to this question. If they hop around all awkwardly while trying to come up with an answer - next. I want to work with people who are excited by the work they do. Plain and simple. Always remember, the interview goes both ways. Be sure to interview the interviewer.
- donretag 7y agoFor companies that offer "unlimited" PTO, it is good to ask what is the average number of days actually taken off by employees. Are multi-week vacations doable? Have vacations ever been denied (happened to me)?
- dobleboble 7y agoWhat are the hardware specifications of the average developer workstation?
- docker_up 7y agoOne of the most important questions: What is the attrition rate for the manager and for the company in general. If a manager has high attrition rate, that's definitely a red flag.
- samirm 7y agowdym by attrition rate?
- wonderwonder 7y ago"Does the company provide hardware and what's the refresh schedule?" - I really wish I had thought to ask this on my first remote job. Everyone is surprised when I show up at company meetings and don't have a laptop I can develop on. I work on a desktop, if you want me to have a laptop capable of running windows docker at the meeting we have every 6 months on the other side of the country, buy me one.
- alkonaut 7y agoMy 2 favorites: - how many quit in the last 3 years (followed by ”why so many” or ”why so few”) And - can I sit with someone that shows me some code I’ll be working on?
- waynesonfire 7y agoit's insufficient to know the questions. to gauge whether a company is the right fit, you must understand what it is that you're looking for. this is a culmination of past experiences and lessons learned. the questions will follow.
- testing_aws 7y ago* how many aws account do you currently run across your entire company? * how much time does it take to approve/create certificates? * how many engineers quit within first year of joining company?
- MichaelMoser123 7y ago'how do you know that somebody has done a good job at your company' and follow up questions on what kind of processes they have: in build automation and CI / bug database etc / are unit tests required for fixes? Do you do integration tests?
- dredmorbius 7y agoWhat's your disaster recovery plan? What circumstances does it cover? What is your threat model? (Depending on response, address missing elements: external threats, natural disasters, power out, hardware failure, fumbling fingers, network-based attacks, insider threats, APTs. Acknowledging and not further addressing some particular threat is acceptable, ignoring it completely is not.) How frequently do you drill for threats / failures? Practices such as Netflix's "chaos monkey" are close to best of class. Not at all is unfortunately the norm. Here I'd like to see some positive answer, but a widened eyes "oh, we should do that" would be encouraging, Dismissal would be many red flags. People respond to disasters according to their training and drilling, and failure to do either leads to poor response. What is your professional development process? Name specific programmes / practices for entry-level to senior staff. "What's a really good day?" "What's a really bad day?" Who's been promoted recently? Why? What reasons have you had for making staff redundant? What reasons have staff had for leaving?
- dredmorbius 7y agoMeta-comment: I'm increasingly suspecting that it's not tech hiring that's broken, but the tech labour model. Specialisation is high, training is long, skillsets frequently expire quickly (at least relative to careers / education), certification lags worse than training does, in many instances, and information aquisition costs on both sides of the hiring line are high: employers have difficulty in finding good/suitable candidates, candidates have difficulty in finding and/or assessing good employment fits. Rewards once on a gig are highly disproportionate, with some high-paying companies, a strong gamble on equity (usually fails to pay off, very rarely does), and increasingly draconian employment terms and contracts (again, California law is exceptional, but as labour gets priced and simply slotted out by housing prices and unavailability, other centres with far less favourable working conditions may gain traction). The idea of working as an individual at a given company for 18-36 months, then moving on (typical job tenancy) seems highly inefficient. Chunking labour into a force that can be deployed might address that. Less a union than a guild, perhaps. Structuring that (and accommodating various state's and nation's employment and organisation laws) is an interesting challenge.
- disordinary 7y agoIn the past when I was unsure I've asked to just have a candid chat outside of the office with my prospective co-workers. Worked well.
- sabujp 7y agoAt a faang you'll never get the chance to ask the team you're joining this many questions directly, unfortunately it's also really heavily dependent on the team and manager. HR will usually give you some of these answers and will often stretch the truth except for benefits. Even then expect things like promotion processes to evolve, many things are never statically configured, even down to the small perks you receive every day. So here's the #1 question you need to ask, esp. at large companies: 1) How long has the team/project I'll be joining been around? Are you joining a team that's in maintenance mode or are they projects other than just refactoring/simplifying or migrating code to the latest and greatest <programming language/stack(cloud)/jdk version/whatever>. As an eng and even manager you really want to join very young teams and large teams >= 6 people (is the company serious about this project? burn rate > 1 million year). That gives you most runaway to develop something new and then brag about all the features you landed at promotion. Most large companies give fledgling teams 2-3 years to become viable. Try to stay away away from teams that have been around for a long time unless it's your area of expertise or you're excited about the project/work. 2) What's the churn rate? Who's the oldest eng. team member (in terms of how long they've been on the team of course) and was the person promoted while working on the project? The higher the level this person is on the team the easier it will be for you to get promoted.
- bcyng 7y agoNow that I’m the interviewer, I think it’s better to not ask questions than ask a question you don’t really want the answer for. Most questions I get asked by interviewees lower the impression I get of them.
- deleted 7y ago[deleted]
- dustinmoris 7y agoI hate these typical questions which hiring managers or candidates ask each other with no real meaning behind. E.g. "how do you use source control"? What is the intention of this question. What value do I gain from this question? It implies that I have a specific way of interacting with source control in mind and if they don't follow the say way then I'm unhappy or what? Interviews take such a long time, I am of the opinion that I only want to ask questions which genuinly help me later to make a decision. e.g. instead of "what tech do you usually use?" I'd ask "I've been recently playing with X and think it's a brilliant use case for doing Y. If I were on your team and I'd want to do Y with X, would that be an option, or what's the protocol in tech decisions in your team?" With a concrete question like this the interviewer has to explain to me how they actually decide on tech and give me a more or less yes/no answer to whether what I want would be possible. I find this a lot better than a generic tech question and then get bombarded with a ton of buzz words which don't really say much about how open the tech teams are to picking their own tools for the job, etc.
- christinaupton 7y agonot enough in here about explicit mentorship. will there be someone better than me who is incentivized to level me up?
- reubeniv 7y agoI normally ask what opportunities for growth exist, eg training/certs/online courses etc, and what they like about the company, can normally tell if they like the job/you by how enthusiastic they answer or whether it comes across as scripted
- sohodlers 7y agoDo you pay for this job?
- vadikkiev 7y agoI ask for your help! Hello everyone, I'd like to get 2 karma point so that I would have 2 karma points in total, so that I can prove my HackerNews account into my Keybase account. Unfortunately I have no idea how can I gain karma, since I haven't used HackerNews that much. Can someone help me. Thanks.
- carapace 7y ago"Can I talk to the last dev to work on this?" "What happened to the last dev to work on this?"
- sectorcleaar 7y agoI have a similar problem about the question "mention 5 advantages in you and 5 deficiencies in you".
- Balanceinfinity 7y agoWhen was your last vacation? Where did you go? When was the last time you thought about changing jobs? Why? When you joined this company, what were your goals? How many of them have you met?