jpluscplusm

Voted no, but I'll get the 2nd gen when this 14 month-old macbook dies. It's a cheaper casual/home browsing device - nothing more.

What's another name for a manager who meticulously checks all the code that his or her charges are producing because they're still in a position to understand it? A micromanager :-)

I think you're underestimating the power of an engineer to royally screw things up with excessive and inappropriate honesty! I forget the relevant Dilbert cartoon ... :-)

In any case; if you ask, the worst they can do is lie and say "it's all good." Then use the metadata surrounding their replies to the "most/least proud" questions to figure out if this sounds reasonable. Are they proud of a sizeable chunk of functionality, or just the user avatar widget indexing? Do they seem reticent about either reply? Ask them "why's that?" to each reply. Do they seem to have difficulty choosing their most/least-proud part? Is that because there're too many options, or too few? :-)

Perhaps ask them (before the "codebase state" question) about something you /know/ isn't 100% in the company. People complain about stuff they shouldn't, online: use the googles to your advantage and find out what things might be a good litmus test for their co-workers' honesty.

My 2 €-cents

2 suggestions:

1) Why not ask the question you asked here? "How much of this role will be new feature development?"

2) Don't assume that the /manager/ really has the low-level information that will dictate how your time will be spent. Ask to meet the coders you'll be working with (not a bad idea in any interview process!) and pop the questions:

"What state do you feel the codebase is in? How does new feature development tend to get divvied out across the team? Which part of the product are you most proud of? ... and least proud of?"

HTH