It's not as if they have a consistent set of criteria they're searching for when they write that. Someone in HR or recruiting put it in there because it's what they've always done and they haven't seen a downside to it. In that sense it's just fluff. Fluff is bad for recruiting, but you shouldn't try to infer what a corporate culture is like merely from the flavor of fluff on job ads.
Interesting you put it that way, since I've learned to be on the lookout for boilerplate in job ads as a personal filter. Usually I've figured this out by just copying and pasting select texts from their ad into Google and seeing how many other job ads from different companies for similar (and in a few cases wholly different) roles.
You say "spiting yourself" I call it doing due diligence because you can best bet those companies are gonna be scrutinizing the hell out of whatever resume I give them, turnabout is only fair.
1. Choose a company that does something interesting and meaningful.
2. Try to understand what they are looking for, and if that's really what you want to do for 8+ hours every day.
3. Put everything on your resume that will maximize your chance to get the interview. This has nothing to do with your actual experience. Remember that you only need to be better than the rest of applicants, and usually it's not hard if you're good.
4. During the interview, evaluate the people. This is the most important step. These are the people who you will spent more time with than with your spouse, so choose carefully.
You can't get any idea about those people from the job ad, because they might not have even seen that ad. And even if they wrote it, phrases like "passion for what you do" mean different things for different people. Ultimately, yes, you should be somewhat passionate about what you do. If you're not, go to step 1.
What's right and what's wrong in this case here? I'm gainfully employed now, at a company I actually have come to really enjoy working for, making arguably the most I ever have in my career so far.
The method worked for me, doesn't mean it's universal, also doesn't mean this success can be directly and completely attributed to screening out copy/pasted job ads (nor any of the other criteria I look for in a potential employer). Only that I have a method that I've stuck to for deciding who I want to work for, and haven't found much of a reason to change it. Personal financial and professional goals are being met, and supported by my employer.
It works for me, if your system helps you succeed as a job seeker, more power to you-but if people here have systems that are working for them and getting the outcomes they're looking for in a career, I don't know if we should be so eager to tell these individuals they're "wrong".
And that's perfectly fine, for both parties.
I'm deliberately trying to stay as high above ground here and proffer that individual choices kind of matter here, and taking the broadly utilitarian viewpoint of: if the way you look for jobs results in you getting the kinds of jobs you want and opportunities you're looking for-not to mention satisfies the financial goals you have for yourself, great.
That's where it begins and ends for me personally.
But, critically you can only go to so many interviews. Thus missing out on a few openings is just not a big deal.
Mine position is going to be different then position of other people in same company, so it makes a lot of sense to evaluate things that signal what my specific position is going to be about.
It's just generic filler. That makes for a very arbitrary filter when you're choosing which companies to avoid.
I'm sure most if not all of us have taken jobs where all the things on our personal checklists were checked off in the interview only to discover the place didn't live up to expectations and certainly probably the opposite has happened.
What may be arbitrary for some might be the difference between accepting or declining a job offer for others. At the end of the day the only person who knows if what they see in a job interview matches what they're looking for in a workplace is that individual, and no one else.
You are giving up on companies based on a generic line in job offers, which is fairly standard recruiter/PR speak. It's like quitting a book after reading 5 sentences, or judging a full course meal based on the first appetizer.
You cannot accurately extrapolate from that one sentence.
You simply cannot have any idea of what the company culture or expectations are until you speak with someone related to the position you'd be working in. At that point you can begin to paint a fairly accurate picture of the company–doing that from one sentence in an ad is completely guessing. It's a night and day difference.
What recruiters regurgitate into an ad is often completely different than what the people you interview with show.
You really are doing yourself a disservice by being judgemental and automatically rejecting a position that has one sentence in an advertisement that is not written by people you'd actually be working with. The fact that you succeeded doesn't matter, because all you did was reduce potential opportunities. You succeeded -in spite of- arbitrarily choosing to limit your opportunities.
You don't get to determine that for someone. It is not my nor your, nor anyone else's place to tell someone what matters to them as an individual in their career goals or decisions.
It's fair to assess a choice as one you perhaps would or wouldnt take because your situations or living requirements may be different but one does not have any right or any authority telling someone what matters to them or why they are right or wrong for making decisions they feel are in their own best personal interests.
Especially if that individual is satisfied with the outcome and has found it beneficial for their career goals.
I don't think there's much that's going to change my mind on this.
Companies are made up of a constantly changing pool of individuals. People leave, new people are hired. Even if a company has a policy of not including that boilerplate in their job advertisements, there's a solid chance that they will hire a new recruiter at some point who doesn't know about that policy and falls back on what they used at their last company.
If you rule companies out based on boilerplate in job ads, you risk missing a great opportunity because that company hired a new recruiter and hadn't yet got them up-to-speed on their in-house standards for job ads.
Trust me, nobody does that. Resumes are quickly skimmed by 97% of people who gets them.
What should you infer corporate culture from? If job ads are written by HR, and not by say lead engineer is already telling.
Those companies deserve to be less desirable employers for workers who can be picky.
As a .NET developer you usually get a MSDN licence from your company and that will give you a generous amount of "free money" on Azure. My passionate colleagues have read up on what you can do and tried some cool things while most of my other colleagues have never even logged in to it.
My passionate colleagues might read an article from Hackernews about web architecture at lunch because they think it is interesting while my less passionate colleagues browse Facebook.
Cool, go to a meetup, not the place people go to because they like not starving.
> My passionate colleagues might read an article from Hackernews about web architecture
Reading Hacker News while eating lunch implicates reading StackOverflow in bathroom hour later. Better off relax and chew properly.
Sure, it is not guaranteed and there are risks as you say. Especially the tool part where people want to implement something new just because they read about it recently.
>Reading Hacker News while eating lunch implicates reading StackOverflow in bathroom hour later. Better off relax and chew properly.
I should have been clearer. Where I work we usually have 1 hour lunches and eat in about 30 min and then take a coffee and chat or browse some. But to be honest no one would bat an eye if you read an article like that during work hours either. Sometimes you need a break or you need to read things to keep up and that is fine as well.
I find the passionate ones tend to progress in their careers and thrive on that sense of achievement and the punch-in/punch-out types are happy just to hum along, take work and do it.
I think it's necessary for balance.
Edit: obviously in social or interview settings this is appropriate. I meant among co workers.
Creating software is very hard, and I’ve never worked with a person who has gotten good at it without having an above average level of interest. I believe that’s partly because developing good software, efficiently requires team members who can work independently with little guidance. And, to be able to do that, one has to have some interest in what they’re building. But, I may be wrong, and I’ll have to think about it more.
It’s good to know that people get turned off by that description, though. I’ve put that term in my job posts for a long time. It comes from my experiences in the 90s and 2000s when waves of people entered the industry only for the money. And, it always seemed to show in their work. Plus, because of shortages, often it’s easier to train passionate, entry-level developers than it is to find good experienced developers. And, that’s not because I low-ball on salary. It’s just very difficult to convince people to come work for you, especially when your a scrappy little startup with little revenue and high risk of going under.
Developing software is all the same, right?
Just like everyone tuning the engine in their race spec roadster must love doing oil changes and swapping rusted brake discs on their neighbor's 15-year-old nissan micra?
I know a lot of people who are passionate about the beautiful software they get to work on their spare time, on their own terms.. software not tainted by dysfunctional corporate culture, legacy, deadlines, budget constraints, ever growing technical debt, etc. I suspect most of them don't expect to find such passion-worthy projects in a commercial setting. It is quite likely that they won't love their job, even if they can do a heck of a good job at it.
So yeah, that kind of description can be a bit of a turn-off.
I just watched the Netflix documentary about the Fyre festival last night, and it seems analogous: it's actually worse to get people excited about a dream that doesn't exist than for people to be open-eyed about what something actually is.
I highly doubt that's a large number.
If employees are not responsible for their work, can't take chances and have every decision second guessed by more senior people fiercely guarding their little sphere of influence, that's when you breed such resentment.
You see this too with 'bikeshedding', there appears to be delegation taking place, but it is a farce. In this case there are too many captains on a single ship, nobody can take charge and nobody is responsible and free to give it their best and possibly fail.
The most important parts of most project work are grunt and grit, not "passion" and other such BS oriented at Disney-nurtured adults.
As for grit, nobody has ever paid me enough to deserve mine. Interest will get me to go above and beyond, otherwise I'll just perform well enough for 8h and I'm outta there. My grit is reserved for stuff that matters.
But also in the sense of grunt work.
An office full of miserable people usually indicates poor management, which no amount of passion can really offset.
I think there's a lot of pressure to "enjoy" work because good-paying work is a lot harder to find these days. Not to mention that our work is deeply ingrained in our identity (at least in the US). I get asked what I do for a living 95% of the time when I meet new people in the US, and exactly 0% when I meet new people in Europe.
Fluff like "passion" or "drive" or "initiative" is indicative of someone who has no idea why they are hiring someone. Let alone the fact that none of these things is reliably demonstrable, and all of them depend on what the job on offer is.
You're far better off responding to an ad that says "we want someone who has done x, y, and z, and wants to use it for a, b, and c". Specific things with a specific purpose. If someone has that, they've thought about what they actually need, not how they want to look.
Maybe a refined/alternate job req would be something like this: "You must be open to the idea that the work that you're doing has value and is intrinsically motivating. We will do our best to convey that value and provide that motivation, and you should try to harness that motivation to produce high-quality work." Certainly, as someone who has planned engineering tasks for teams, a lot of focus has been on making sure that everyone has a feel of ownership/vision and is working on things that they enjoy.
You're mistaking "passion for what you do" with "passion for a job". I've worked with a lot of people who love their field and I've never seen a correlation with hours worked. If anything the people closest to burnout are always complaining about their job and fantasize about leaving their field entirely. Those people are not passionate for what they do.
As a developer and former recruiter, I will say that most job ads are not written well. Many people cut & paste the text from other jobs ads and tweak it for their own purposes. The people with whom you'd work may not even be aware of what's in the job ad. Crafting a good job ad is hard.
You can make a job description a special snowflake, but then not reach the right candidates. In my experience, I will find job postings on a job aggregator website, which will lead me to a companies website for the position. These positings will usually include a boilerplate on what the job includes + other details on the company. If it seems interesting, I'll research the firm to see what they're doing, opinions on glassdoor etc.
Judging a company and their treatment of their employees by job description alone is a very narrow view of how business operates.
I asked the interviewer how both of those could be true and he said, "I'm not sure, I'll have to get back to you."
This description gets passed on to HR for posting and they append the company spiel to it. That's where generic HR keywords like 'passion', 'exciting', 'innovation','elite team', 'cutting edge', 'game changing', 'inspiring' get added. I don't have control over that.
So ignore the HR rubbish and checkout what the hiring manager and his/her team are like. Also note in mid-size (1000+) to large (10K+) companies each manager and team can have their own work culture based on the personalities in the team so don't write off such a company based on interviews with just one group.
To me "a passion for what you do" means that you care about your work and you don't half-ass it.
But I expect that it probably means other things for other people, including your interpretation of "tons of overtime".
I am not passionate about computers, I like solving problems and streamlining the tedious. Personally I don’t have a passion for my company either. I like them, I like what they pay me, and I like the benefits and culture.
I see my paycheck as a business transaction that is favorable to both myself and the company I work for.
With that being said, I do actually enjoy the work I do, but would never use the word passion to describe it.
Yet he works long hours, everything he does is extremely high quality and just watching him work you can tell he's pretty masterful at what he does. Though honestly, I'm not even sure if he sees himself that way.
Similarly, when I see "Made with (heart image) in (location)" at the bottom of a website, I'm pretty the developers weren't overflowing with emotion when they hit commit.
I've an extra criteria of late, which is not applying to anything that I don't find socially useful or that is obviously engaged in some anti-social behavior. Try that, and you'll skip nearly all jobs.
Sad world...
Hype oriented programming as it is.
Was blocked by HR/recruiting... :(
So you want someone who
- Understands modern computer architecture and operating systems: Hyperthreading, power management, cache coherency, memory bottlenecks, filesystems, graphics hardware tradeoffs and related debugging tools, Intel/AMD/ARM.
- Understands the computer software stack including webservers & frameworks, high performance software libraries, GPGPU programming, clang & LLVM, JIT compiler, CPU and GPU virtualization stacks including VMware, Azure, AWS.
- Understands hardware tradeoffs, DRAM memory, multicore, ECC, PCIe bus tradeoffs, display techonolgy, Freesync, Gsync, server storage technologies both nearline and long term, WiFi and ethernet. Backups. Servers and server management.
- Database servers both commercial and opensource and their setup for for reliability, backups, production and testing servers.
- Computer administration, linux, windows, bash and perl/python scripting for sys admins. Machine testing and validation for production use.
- Computer security, firewalls, Meltdown & Spectre vulnerability fixes, VPN setup and admin.
So did you finally hire your senior systems engineer? the one who knows computers ?
I have a really funny story about this involving a recruiter deciding I wasn't a good fit for one role, and recommending I take another because I didn't specifically list any experience with CSV files of all things on a DevOps resume.
Turns out a friend worked at first company, in the support team-made a referral and I was hired two weeks later after interviewing with the team lead and department head. During onboarding week I'm talking with a few team members at lunch and one of them mentions how they've been needing to hire the role but never put much effort into it, HR connects them with an agency and the recruiting company they hired never sent them any candidates, and only even emailed to say they "maybe" had one person, but that they were missing a few 'key' skills.
I smiled discreetly and listened on, but the whole time I had this image in my head: https://i.imgur.com/JbzO6uM.png
On the other hand, "a passion for what you do" could be code for, "you have to go full tankie on our company's 'we are making the world a better place' mission statement BS". And for companies that's true of, you'll probably be able to identify that trait pretty early in the actual interview process.
So, maybe you should apply to some of those jobs!
It doesn’t necessarily mean that they have to work until 8pm every day.
I try to learn and become a better developer.
I could give a rats ass about programmatic advertising and the "value" we bring clients.
The problem is that many people swing from being passionate to the other side of the spectrum by becoming cynical of work.
The amount of jobs I have skipped due to this "job responsibility" is ridiculous. I am good at what I do. I will come to work, work a full day maybe even longer, then go home and unwind or do something non software related. I am not trying to burn out. Why is it not enough to just be good at your job and work an honest day every day? Why do I have to love every moment of it as well? I am not going to fake it because that lead to burnout at my last job. Who has a passion for writing crummy software for someone else anyways?
By skipping those jobs, I think I have found the right one where I am surrounded by down to earth like minded people who are still good at what they do. I start in a couple weeks and I am actually looking forward to working now.