Live data from Hacker News

Interview questions to ask your interviewer

daveceddia.com

101–110 of 183 posts

Re: Interview questions to ask your interviewer

#101

Earlier quoted context omitted.

> Ask if you can see the employment contract before accepting an offer. I'm a bit puzzled by this answer. What's wrong with: "I read the contract and I don't like the terms sorry"

Usually there's a surprise contract waiting for day one of a job, after you've left your other job. Yes, you can still walk away, but it's better to review that contract sooner. If you don't ask to see the contract, it will almost certainly be a day one surprise. And even if you do ask, the legal department, who neither you nor the people interviewing you frequently communicate with, might still have some surprises i…

I've been sprung with these before. Usually trivial, unenforceable issues, but annoying none the less. The worst was I once even had a background check _after_ accepting and signing. Nothing came up, but that could have left me with no job and no recourse.

How do you avoid this? It's a particular kind of institutional trickery that may not even be intentional but is very frustrating.

Re: Interview questions to ask your interviewer

#102

Earlier quoted context omitted.

> "What are the company's non-compete rules? If I wanted to make and sell an app in my spare time, is that allowed? What isn't allowed?" I would not be surprised at all if the people interviewing me gave a nice answer and then on day one I'm asked to sign a contract that doesn't match what they said. Ask if you can see the employment contract before accepting an offer.

Signing means accepting an offer. To sign, one needs to get a copy of a contract. So one always sees a contract before signing, no? Let’s look at it from a different angle. One does not file a resignation before receiving a countersigned copy from the company.

On the contrary, you can have a job without a contract.

Corollary: continuing employment may depend on adherence to policies you don't control, regardless of prior agreement.

Not all law is contract law, and this remains true of employment law.

Re: Interview questions to ask your interviewer

#103
post #95
post #92

This is probably too involved to be a question for your interviewer, but I kinda want to ask, "Imagine you have multiple instances of a production service with different 90% latencies, how would you measure the overall latency of the service?" A surprisingly large number of SWEs are really bad at statistics, which is kinda necessary when you're asking whether a service is fast enough.

What's your answer? I'm tempted to average them?

You can't average percentiles - it's not mathematically meaningful, so your number will move depending on random details. E.g., if you changed your load balancing algorithm, and then observed the number go down, you can't conclude that latency was improved, because you changed how the requests are aggregated and it affects the result in random directions.

(You may get a usable number if all servers are more-or-less equivalent and events are randomly distributed, but then you're basically assuming the thing you want to validate.)

I'm not an expert but I know two correct ways: collect the records of all individual requests and compute 90% just once on the whole set (doable if there aren't too many requests - modern machines are quite powerful), or generate per-server histograms which can be merged safely.

Re: Interview questions to ask your interviewer

#104
For questions like this

> Who supports the product once it's released? Pager duty? Monitoring email?

and this

> Typical working hours? Flexibility? Crunch times?

In my experience it’s a huge mistake to leave such questions in its vague form as the author has shown in his post, especially if you’re living in a third world country like India where the managers and centre heads often project “getting engineers to work at any hour” as one of their USPs to their bosses, who are - very often - CEO and CTOs in USA and Europe where engineers cost more and often refuse to work absurd hours (rightly so).

Rather ask specific questions like:

- clearly state your intended normal working hours and ask whether there’ll be a problem with that.

- what is the on-call frequency (if there’s one)?

- what is the on-call hours going to be for you whenever that happens?

- Is there a follow the sun policy or not? (It’s a red flag if the product is used around one timezone and engineers mostly live in another, far from it)

- ask whether there’s any requirement to have an app like PagerDuty active for your phone number or needed to installed on your phone and would you be expected to be reachable also during other than your “normal working hours” and your “scheduled on call rotation” whenever that happens?

- The point above is very important - my last manager tried to soft bully/pressurise me into activating pager-duty for my personal number 24x7 saying “anyway the call will be at most 2-3 times a quarter” (and I knew he was probably right) and “others are doing it”. Luckily he was my hiring manager also and I had already discussed all this with him - I confronted him right then!

- ask clear questions about how often you’d be asked to attend “scheduled/recurring” calls out of your normal working hours.

You don’t have to be available 24x7. You must not - under any pretext! You are made to do that only because you end up saying “yes”.

If you can, ask this questions on email preferably to your hiring manager keeping recruiter in CC - at least I do that.

Out of 7 verbal offers I had said yes to (around a year ago) 1 company demurred from issuing the final offer letter after these questions, others were very open and candid about it and didn’t mind at all (at least in the mail).

Goldman Sachs clearly mentioned I’ll be required to be ready whenever needed, others were reasonable, Cisco was semi reasonable but seemed skittish to me, Uber flat out lied which I later found out (and hence I left within a month).

Re: Interview questions to ask your interviewer

#105
post #101

Earlier quoted context omitted.

Usually there's a surprise contract waiting for day one of a job, after you've left your other job. Yes, you can still walk away, but it's better to review that contract sooner. If you don't ask to see the contract, it will almost certainly be a day one surprise. And even if you do ask, the legal department, who neither you nor the people interviewing you frequently communicate with, might still have some surprises i…

I've been sprung with these before. Usually trivial, unenforceable issues, but annoying none the less. The worst was I once even had a background check _after_ accepting and signing. Nothing came up, but that could have left me with no job and no recourse. How do you avoid this? It's a particular kind of institutional trickery that may not even be intentional but is very frustrating.

Don't quit until you sign something that says they will be hiring you and paying you until one of you decides to terminate the agreement?

Re: Interview questions to ask your interviewer

#106
I recommend against one question in particular:

> Do you have a favorite part of the job? Least favorite?

When I asked the "least favorite" question in my interviews a few months ago, the answers all fell into 2 buckets:

1) it's a big company, harder to get things done (I have only worked at big co's, I already know it's hard... so this is not an insightful answer)

2) COVID makes life/work harder (I understand it's hard, but some of these people just use this excuse to avoid talking about their job/team)

Re: Interview questions to ask your interviewer

#107
These examples are weak! They're common questions asked over and over... Things you can just look up if you use blind, levels.fyi, glassdoor. "What's the size of the company?" Come on...

Don't burn your time with filler. Instead, make yourself stand out in the last moments:

The questions should be softball, but detailed and enjoyable for the interviewer to answer. Allow them to paint the role and company positively. i.e. don't dig into Google's stance on user privacy.

Use questions to show your enthusiasm-- that you're here for this job and not a job.

You should do research on the company and interviewer before the session. What they are involved in? (languages, concepts, methodologies). Usually blogposts, GitHub and LinkedIn content is useful.

Try to impress the interviewer with your knowledge about said role, company, or relevant topic. Mention a change or new beta product you've been testing. Ask for their thoughts on something you know they like to talk about.

Examples:

Does google have plans to expand the usage of Go in their cloud stack?

What benefits were there after switching from Borg to Kubernetes?

How do people get new ideas get onto the Pub/Sub team's radar when they are busy shipping features at breakneck speed?

How did the team architect the new protobuf API while maintaining compatibility with the old one?

Re: Interview questions to ask your interviewer

#108
During my last batch of interviews, I was salty when one of the companies I interviewed with asked me the "Super Egg Drop" question, I actually don't mind LeetCode type questions in interviews but that super egg drop question is so ridiculous that as soon as I heard the question I knew they didn't wanna hire me. So at the end of the interview I asked my interviewer to solve a LeetCode hard (Alien Dictionary) as a laugh. The interviewer did not see the humor in the situation.

Re: Interview questions to ask your interviewer

#109

Earlier quoted context omitted.

I have exactly the opposite idea. I hate Mac and WSL2 is perfect for development. I've never seen an ad in windows 10 as well.

While one point of view is subjective, truth isn't, but I'll play the game and ask you if i and others news source are just having a collective visions https://duckduckgo.com/?q=windows+10+ads+start&t=fpas&ia=web

Who uses the start menu? Click the windows key and start writing a search

Re: Interview questions to ask your interviewer

#110

Earlier quoted context omitted.

Windows with WSL2 is great. Have you tried that? VSCode can run from WSL2 and have access to its file system

Tell me you don't use Linux without telling me you don't use linux Wsl is pretty terrible in my experience. your better off using a vm you manage yourself. Every vendor has shared folders. Each one can use a x server to display programs in your windows window manager.

X servers suck though.

Vscode renders sharply without having to do extra work.

Both wsls are reasonably enjoyable. Much better than ssh-ing to a Linux host

Post reply on HN