This is a post that was originally published on my blog. See original post here.
I wrote a post a few weeks ago about how I regretted specializin...
For further actions, you may consider blocking this person and/or reporting abuse
My ‘title’ is a front end developer. Why I do day to day is mostly back end and DevOps. But as far as the business outside of my team cares, all I do is develop UI’s.
This frustrates me to no end. I am comfortable and far more interested in working across the entire stack. I enjoy how everything ties together and being able to build all the pieces and watch them for together.
It seems as though the only places that will let me hold that role are start ups, and while they are fun and highly rewarding, the pressure and stress is high.
I wish larger companies (at least where I am from) would consider roles that are more broad in definition.
Really great write up.
I agree with the hiring issue. As a people leader (always a developer) I look for practical skills that go beyond knowledge of a framework.
I get 10 year veterans that only know one framework. I get junior developers apply for senior roles, because that is what they were, at their previous job.
Safely it is the breath of skills that help.
We do give a technical exam. But it is the same one regardless if level. It is also done over the phone and in a collaborative code pen. And it focuses on practical every day skills.
Junior developers get through it with some communication and support. Mid level developers complete it. Senior developers offer advice to make our “app” better.
Long story short, I believe in rewarding the everyday skills. I also do this because I feel developers are historically bad at resumes. Too often people bloat the skills list, but don’t master any. Because they were stuck in the same tech stack for too long.
Companies that are hiring have no idea what the hell they are doing. Uh-oh, I don't have 8 years of experience in some technology, rejected. What does 8 years of experience looks like? How does the number of years I have worked with it demonstrate that I know anything? Hell, if I have 5 years of experience with React, I have to unlearn 4 of those to keep up with the latest changes.
The longer the list of desired skills, the less the company knows about what they are looking for. They're hoping if they bring a ton of trendy technologies into the same room that a great product will magically appear. I think that all in all, recruiters do more harm than good and 98% of them give the 2% that are legitimately helpful a bad name. Job descriptions are the way they are in part so that recruiters can "screen" candidates for the companies. You would think it is in their best interest to get you the highest-paying gig you love, but a lot of recruiters get paid if you show up for work the first day. They'll assign you anywhere in hopes that they get a "rockstar" candidate or that they get a more interesting assignment to fill next time.
I had a typo in my resume (sleep is important!) and sent it to a dozen recruiters before one of them pointed them out to me. I assume that means the other 11 didn't even look at my resume before they submitted it. At this point, I am putting a lot more emphasis on maintaining relationships with a handful of incredible recruiters and bidding the rest of them a good day.
I wish I knew what the solution was. My last two comments were about similar issues in the industry, toxic companies and how I have gone with it to escape reality and hide from other problems and what coding challenges can say about the companies who present them. I'd type more but if I keep sharing all my thoughts on this subject I will have a novel written in a week.
Spot on, also the description of the average recruiter. As an industry we're definitely not making the best choices, see also the naive belief that tech is a cure for all our society's woes.
Right on. Hyperspecialization creates less creative teams that don't know how to solve their own problems. Many game projects I have worked on have gone to hell because people in the programming team didn't work with people on the design team where a works with programing minded designers or design minded programers would make a better end product for everyone.
I think you have a point here ... tech culture is way too one-sided, too much of a monoculture.
Funny though that in all of my career I never did one single real "code interview". I just talked about my passion for the job and the company I was applying with, and about what I thought were my qualities. Isn't that just what an interview should be?
And yeah sure they can include a technical/knowledge oriented part in it too in order to weed out the wouldbe devs.
But the obsession with code interviews/tests seems to be something of the last decade (you can guess how old I am, haha).
Okay, at the end of 12 minutes I'm happy to come out as a multipotentialite. It's no surprise to me really, but it's nice to have a label to stick on the inside of my mind to look at when culture tries to make me conform. Thanks for raising the issue and for the link to the TED Talk.
For sure the interview process is broken in many companies. And we definitely need more diversity. And the more tools you have the further you can go. In fact, I lead a small agency with different nationalities inside, more women than men and where we encourage people on going further than their current skillset (by example with trainings unrelated to their initial job).
Now I'd like however to underline something. No mistake must be made that if we hire a developer we intend that this person's main focus is going to be development. Other skills are complimentary. And for as much as we receive completely different projects all the time, when we start a project we still need to see it through (versus "get bored doing the same thing each and every day"). And that is simply because that's what we're paid to do. I'd love to see a fresh new problem sliding down a rainbow every day but it's not always the case.
So there's this but there's also that. I believe that a diverse culture is essential but on the other side I get the feeling that it doesn't fix as many problems as you think.
In any case, this article is a fascinating insight, thank you for sharing!
This is something that has come up a lot in talks lately.
I'm multi-passionate too and not only in tech areas, but many other areas too.
So what I've seen is that, the larger the company, the more specialized the employees. Smaller companies have the employees fill a wider array of functions.
Going from a smaller company to a much larger specialized corporate outfit is quite an adjustment unless it's specifically structured to operate as a small company or startup.
You mentioned about having the freedom to write about a multitude of different topics without being forced into a niche. I feel this way about development work too.
The real problem solving an creativity happens way outside the lines of code that are finally written to solidify an idea. That is far more precious to me.
Made me think about my attempts to specialise and how my tendency to jump from one interest to another over the years have played against each other lol.
Great article!
Really well written article, with a lot of very concerning truths regarding hiring in the development sector.