It means they didn’t like you or felt your co-workers would not like you.
There’s nothing you can do about it unless you are doing something egregiously stupid, like showing up to an interview smelling of booze.
It does matter. Our company is very friendly, informal, polite, and not at all authoritarian. Performance is expected but overtime expectations are reasonable, and working ridiculous hours is not encouraged. Productivity is important but, because of the nature of the business we are in, ethics are much more important than productivity. On the few occasions we have hired people who didn’t fit with those things it NEVER worked out, irrespective of their skills.
If I already made the mistake of engaging in this conversation, I would do my level best to not offer any information. I wish it were a different world, but it’s not. And there is a non-zero chance that statements made may be used in a lawsuit so there is low chance of very high costs and very little benefit to having that conversation. I’d gladly have it with friends or in a non-professional setting, but it would be irresponsible to do that as an agent of my employer.
We didn’t have to do that from the start, just when they decided to show management how much effort they were putting in. But they did have lots of turnover.
I’ve done a fair amount of interviewing for tech companies and cultural fit is very important. It’s sort of a catch-all for non-technical evaluations. We’ve said no for cultural reasons like:
Being a jerk. Candidate started argument with female interviewers.
Not Agile. Candidate came from Waterfall background.
Not self-starter. Smaller companies don’t have enough managers to keep everybody busy so candidates need to be able to figure out what to do on their own.
Not passionate. We’d prefer not to hire people who look at engineering as just a job.
There are probably other reasons that I’m forgetting.
Every job I’ve ever had, whether it was in a store, restaurant, office, or hospital, had people who just didn’t belong there. The last paragraph made me think of a pharmacist my old hospital hired a year before she actually started (they had to sell their old house first) and I knew on the 2nd or 3rd day that she was going to be a problematic employee; in short, she wanted our whole 60-person department to change their methods to suit her. At the end of her second WEEK there (yes, week) she went to the boss’ office on Friday afternoon and said she wasn’t going to be coming back. :eek: When he told some of us about it, I said, “Good. I could tell that she was going to be a big troublemaker.”
I found out a couple years ago that she bought an independent pharmacy in a nearby small town. That didn’t surprise me, and because she Did Not Play Well With Others, I shudder to think what kind of boss she must be.
There are distinct differences in the cultures. Agile is more self-managed, more self-directed teams. When we made the transformation from waterfall to scaled agile, some engineers struggled with the changes.
They should find another job. I’ve had to do this.
My previous employer didn’t care about work-life balance; it was expected, if you wanted to get ahead, that you would travel enormously and put in a huge number of hours. That’s just how it worked, and once I had a family it was incompatible with my goals, so I left before my kid’s second birthday. For some people that company’s a great fit because their kids are grown up, or they don’t have kids. Note that I’m male, so it does affect men, too.
My current employer doesn’t require that of most people, so it fits well for me, but it has other disadvantages.
Lord, yes. One at my office is used to being the Head of All Engineers, and he really doesn’t like that each engineer is now directed to pull the next piece of work themselves, not to check in with anyone. He also doesn’t like having “his” engineers pulled to help if we’re blocked in another area.
It’s amazing to me how men never have children in these conversations. I work with guys who have pictures of children on their desk, but these must be fake pictures.
I’m pretty sure an equal number of men and women have children.
I do agree that it is not a good policy on any level, outside of emergencies (which a well-organized company hopefully doesn’t have many of). But another part of fighting for equality is recognizing that men can and should take an equal role in child-raising.
There was a much higher proportion of men in this place than there is in the place I’m working now. And come to think of it kids and family was not a topic of conversation there, but is here. Lots of people bring their kids to work here during vacations and stuff, we have offices and they are never a problem. (Both men and women do this, by the way.) There I took my kid on bring your daughter to work day, and it was considered very odd.
The company is well organized, but the project I was working on wasn’t, and became a famous and expensive disaster, so local group culture might be more important than company culture.
Then Voyager’s workplace would be a terrible fit for them, male or female. My point was that a company that expects employees to work every day until 9 should damn sure tell them that up front. It would save them a lot of time and energy in the hiring process, since for a substantial portion of the population that’s an immediate, non-negotiable dealbreaker.
And having your job change from a leave-by-6 to stay-till-9 is even worse.
Like any requirement, none are set in stone. If we had a candidate that was obviously great in all ways but came from waterfall we’d hire her. If the candidate was borderline in many areas then waterfall could be the deciding factor.
Damn right. I don’t have kids or a partner, and I expect to be out of there by 4:30 (I start early in the morning). And don’t expect that I won’t “count” early-morning calls with software engineers half a world away, because that’s work, too.
(I don’t generally clock-watch, but damn I’m stupid by 5 pm after starting at 7 or 8 am; the days when I have a conference call at 6:15 am, I’m stupid by 2:30.)
I’m so lucky that my current job is focused on output and meeting deadlines, not on staying late. Over the summer I clocked many weeks where I worked 60+ hours because of an understaffed project, but I was compensated and thanked for that work. It felt great and made me really like my boss and corporate culture even more.
I know what folks are getting at, but I don’t consider agile experience as a must-have. It would be nice, but if the person is otherwise a fit and is willing to learn agile, that’s fine.
We do, however, occasionally have issues with people who just can’t leave waterfall behind. They tend to think they are agile but really, they just try to cram waterfall into agile ceremonies. It’s a personality/culture thing, I think. Some people are just not comfortable not planning out a project down to a very detailed level before starting to work on that project. I have one on my team now, and it’s very, very difficult to work with that person.
Also - from what I can tell, every company does agile a little differently. Just because person A has agile experience, it doesn’t mean that they do agile the way WE do it. So there’s always a bit of learning curve.