Here's a more technically-slanted list of questions I've used during interviews: http://www.reddit.com/r/programming/comments/apae9/interview...

Realistically it shouldn't be a problem if they handled the interview correctly, but some prefer not to take the risk.

In itself, this is a useful indicator of corporate culture.

If you're being interviewed, turn yourself into the interviewer at this stage. Be prepared -- take notes, bring materials from the website or other content to reference during the conversation, and have your questions planned out thoughtfully ahead of time.

Generally, a recruiter is not the best person to ask questions, though. Try to ask questions to the hiring manager. Strive to learn the organizational/corporate pain points. Ask questions to gain information, but also to get beyond understanding "culture" to understanding biases and preferences. Rarely do interviewers make that clear, in spite of the intentions of their communication.

Last, one general comment about questions: if they can't be answered to your satisfaction, mark it as a red flag. If you, the candidate, can think about something in the short term and a business that's focused on that thing can't or won't respond in a way that's clear, that should be a clear indication of a problem.

We're interviewing lots of folks these days and here are some more questions I think candidates should ask or which we've been asked which I appreciate:

1. How many months (or years) of cash do you have in the bank?

The founder might not say the exact number of dollars, but they should be willing to give you a # of months/years left esp if they're not revenue generating and are reliant on other people's money (VCs, angels). If it's 3 or 6 months, I'd think twice as there are no guarantees of funding being raised and do you really want to be job-seeking in 3 or 6 months or get laid off cuz of the Last In, First Out principal? There are no guarantees of more money being raised. Plus they might be exaggerating about how much they actually have. If I were a candidate, I'd love to hear 2 years but 1 year at a minimum. 2 years only happens generally if the business is real (making revenues/profits)

Clarification: On the money in bank question, you're looking for real money in the bank now. Not what they expect based on their projections or if they land that big customer they are "on the verge of landing" or the "we have termsheets from investors and will be closing in the next few weeks" -- none of those are money, they are promises/hope. So perhaps the better way to ask this is "If you earned no more revenue or got more financing after today, how long will the money you have in the bank today last the company?" -- Also, this is a question you should only ask of a founder, CEO as they'll prob be in the best position to actually answer it.

2. What specific projects do you see me working on if I were to join?

This may in all likelihood change by the time you join, but they should have a clearly defined plan for the areas your talents and skills be used. This will help give you a sense for what you'll be doing as well and whether it's interesting. I also think if they articulate some nasty, unpleasant work you'll be doing, that is good as well. Jobs are rarely all rainbows and butterflies so someone who is going to be honest with you about the good, bad and ugly up front is probably better than someone trying to sugarcoat up front with all the amazing stuff you'll be doing every day to "change the world and make people's lives better."

My only comment on the post is the question about "What technologies do you want to be utilizing?"

Technology enables solutions to problems. So whether some company is adopting some new, shiny technology is less relevant than whether they're using technology in a way that is solving a real problem and ideally becoming a real, fast-growing business.

I think the better question is to somehow gauge their receptivity to being flexible about technology if there is a real benefit to doing so. Not sure the right question to test for "technology rigidity" but that is the question I'd ask if I were a candidate talking to us or any startup.

To this, I'd add another question if interviewing at a non-revenue generating startup -- "How will the company make money?" And you should assess how realistic this sounds. You don't need to be a VC here but it should pass your own innate b.s. filter.

But if they do answer, "We're going to have millions of users (one day in the future) and will monetize through advertising", my recommendation would be to run the other way (quickly).

Another way to put this: "can I see your current balance sheet and cashflow statement"?

Serves two purposes:

1. If they say yes, you get to see their actual assets and cash flow, unless they're flat out liars.

2. Whether they say yes or no, their degree of reluctance or acceptance is informative about managerial culture.

Think about it from our perspective: part of the point of being a non-public company is that you can keep some things close to the vest, like profits and balance sheet. Perhaps 50% of the people we interview don't end up getting a position. What if you take that info and share it with competitors, or plaster it on TechCrunch?

This is particularly true if this was a follow up to a previous question (which is borderline) about how many months of cash were in the bank.

Should you judge the financial health of a company? Sure. Look them up on CrunchBase, observe the surroundings, do some research into market size yourself. But have some tact.

Now this is interesting. What triggers that reaction? Is it asking for the particular documents, or is it the request for meaningful information?

> Perhaps 50% of the people we interview don't end up getting a position. What if you take that info and share it with competitors, or plaster it on TechCrunch?

Good point, and looking at it from your perspective, sure, I'd be reluctant to open the kimono too. The main thing that stops me, since we're swapping data points, is that it would be the wrong thing to do. Betraying confidences is both unethical and often contrary to the protections of common law.

> This is particularly true if this was a follow up to a previous question (which is borderline) about how many months of cash were in the bank.

If you then smiled and cut me short, I'd be suspicious. It sounds like we both lost.

It's sort of like a woman who asks you what car you drive right off the bat, on the first date. It indicates she is only in it for the money. And that she also lacks the social intelligence necessary to gain information without revealing that she's only in it for the money.

For a startup to succeed its people need to be a bit irrational. A pure profit maximizing strategy for a good developer is just to do something boring at Google. You aren't joining a startup to do median case profit maximization, you're doing it to (a) do something interesting for a change and (b) have a shot at a big payday.

Now, there's a certain undercurrent here at HN that says "F you, pay me". OK, but this is not the type of personality that is likely to build something great. They are the first ones to bail when things get rough, the first ones to trash their former (or current) employers, the first ones to lay blame.

There is a role for highly skilled mercenaries, just as there is a role for really beautiful golddiggers. But they should gravitate to Google/really rich men, as that's where they'll find a mutually satisfactory exchange.

It's the same thing: I want a sense of the risk I'm taking, but without signalling (incorrectly IMO) that I'm just such a mercenary.

Sounds like basic due diligence when checking out a potential new employer to me.

I think your point #2 is valid even if you ask my initial question about "real money in the bank". If they don't know how much burn they have left or can't answer immediately or are reluctant, that is still a problem.

Small company: I think it's not unreasonable to know at least the headlines of the financial state. After all, small businesses are inherently riskier and I may be making financial commitments based on the presumption that I will have a job.

Big company: I can probably just look it up myself.

Medium company: That's where it gets tricky.

> I think your point #2 is valid even if you ask my initial question about "real money in the bank". If they don't know how much burn they have left or can't answer immediately or are reluctant, that is still a problem.

Or if they say "cashflow statement?"

I'd also want to know exactly how they make money or are planning to make money.

And the companies ability to pay that paycheck every Friday are of critical importance. We are all investors either with our money or our time (a paycheck is just a return on a time investment). I don't invest either without plenty of research.

I carry enough savings to get by for a few weeks if they go broke or tire of my lame puns; but for many people certainty is worth money. That's why lots of folks prefer steady paycheques to high hourly rates or equity.

1) Companies don't owe you any of this information as an interviewee. Sure, ask about the financial health of the company. But a balance sheet? Good luck.

2) You're going to get lied to in an interview about the health of the company. Do you really think a hiring manager is going to say "Yeah, we're throwing as many bodies as we can to finish this project, or else we're toast"? They want you to believe everything is fine from the day you start.

3) Even the financially secure companies hit the wall, get sued into oblivion, have their core product copied by Google, etc etc etc. You just don't know what will happen next.

They may not owe it to you just as you don't owe the company anything like showing up for an interview. It's what people do when they want a job and it's what the company should do if they want good people (this applies a lot more to small startup companies than a big corp because a big corp will have a lot of public information already out there). Good people will simply go somewhere else rather than take unneeded risks.

2) You're going to get lied to in an interview about the health of the company. Do you really think a hiring manager is going to say "Yeah, we're throwing as many bodies as we can to finish this project, or else we're toast"? They want you to believe everything is fine from the day you start.

Once again, if you lie to someone to get them to start work expect them to start looking to leave the day they find out you lied. They also will not likely work very well while they are still there. Of course, like #1, if the company is only hiring crappy people then it doesn't really matter. They are usually happy to take a job anywhere and ride the company into the ground.

3) Even the financially secure companies hit the wall, get sued into oblivion, have their core product copied by Google, etc etc etc. You just don't know what will happen next.

This is common sense. No one expects the company to know everything. That's all the more reason the company should be fairly open with potential employees so employees can walk in knowing what to expect. Let the employee decide before being hired if they want to be a part of a company that can easily be copyable or be a potential scam.

Wasn't it mentioned somewhere else in this thread that a lot of small VC-backed startups are contractually compelled to not disclose their finances?

And when a small startup says "okay, Mr Experienced Developer With High Salary Requirements, we can't afford you (because we're very tight on cash), but take this Awesome Restricted Stock in lieu of comp", what do you say? Isn't that the big risk that is supposed to lead to the Big Payday?

That's when you hammer them on what exactly they are doing. What is their product, market, sales strategy, exit strategy, pricing, and finances. Ownership, options, etc... are worthless in a worthless company. Risk doesn't mean going in blindly.

And yes, I've turned down options and jobs before because the CTO couldn't really answer these types of questions during an interview. Interestingly enough, the one company that was most secretive and offered me the most options was the one that went out of business a month after I turned them down. Others, I've heard after the fact how they are horrible places to work. The interview process is a two way street, especially in small companies.

If that's their situation, I won't complain.

> Isn't that the big risk that is supposed to lead to the Big Payday?

Sure, it's a bit of a gamble. But experienced punters check the form guide.

Now I've gotten into the habit of only looking at directors statements on their annual reports when I need to research a company. I get so little from the rest of their website, I can spend hours and not understand anything more than the names of their products/services. I have the distinct impression that coding teaches me to only believe what is stated, whereas parsing marketing text is all about reading the lines, which I am terrible at.

"How often do you expect your employees to work extreme hours in order to be competitive in your company?"

If the culture of the company supports 60-80 hour weeks, it may not be apparent in a job interview... and even if it doesn't, asking this question incorrectly may paint you lazy or unwilling to put in time if(hopefully infrequently) necessary

There was nothing in my question about lying, It just seems that is very tough to emphasise your dislike of constant 60-80hr weeks and still be able to convey the fact that you wont shy away from a late night work when absolutely necessary.

By the way, I wouldn't call someone who doesn't want to do overtime "lazy". For instance, just because I'm "used" to working long hours doesn't mean that I'm indifferent to it.

Or, you know, how to avoid them ;)

Good advice by the way. I have always made a point of asking this my self, and when I have been hiring, I would always try to answer as well and honest as possible, if candidates ask for it.

There is nothing in those questions that could lead an employer to think that you wouldn't be suitable. They are intelligent, natural questions and the answers are very relevant to someone applying for a job.

Once an offer has been made, the opportunity to ask detailed questions is gone. If someone posed these questions to me after the offer I'd simply think why didn't they ask during the interview if it was important.