4 ms·
Eh. He probably just didn't like the team/felt that they didn't know what they were doing/they wasted more time on meetings and discussion in general rather tha
by cncrnd 8y ago
Eh. He probably just didn't like the team/felt that they didn't know what they were doing/they wasted more time on meetings and discussion in general rather than him just not wanting to justify his approach.
- EpicEng 8y agoI just can't imagine being able to judge that in a two week period unless it's a total shit show. I have no reason to doubt the GP and I think its more likely this is just a case of "I know better".
- the-pigeon 8y agoAnd honestly unless the hiring manager straight up lied during interviewing that's the employees fault for not asking better questions about the position during the interview process. So many people forget that interviews are a two way street. I don't want to hire someone that is going to be unhappy in the position because unhappy programmers have poor output and bring down team morale. They need to ask specific questions about the things that are important to them in a job so I know they are really thinking about whether the position is right for them or not. Candidates who ask me no questions after being prompted for them never make it past the phone screening interview despite sometimes being very technically capable.
- cncrnd 8y agoIt's difficult to get an accurate perception of a team without working with them for a bit.
- madeofpalk 8y agoEither way, trying to get a reference from a team you were only at for a few days seems ill-advised. (btw, the comment you replied to never mentioned the gender of the person)
- deleted 8y ago[deleted]