4 ms·

There are a few things I want to know about when looking at job posts: tech stack, target salary, what the company is, and a small list of perks. This will give

There are a few things I want to know about when looking at job posts: tech stack, target salary, what the company is, and a small list of perks. This will give me an idea of what the office environment is like. I hate it when job postings start listing out needed skills. I read one the other day listing 5+ years of HTML5 and CSS3 experience. When it comes to years of experience, you're more likely looking for a particular level of knowledge and some people are going to get there in a year or less, and others will not get there no matter how many years of experience they have.

Bahamut 13y ago
It also is a red flag to me when I see that - I know I am performing close to on par with some people with industry experience of 10+ years on the frontend. All things equal, you will want the rising star, since that person hasn't hit a ceiling yet, and there's a decent chance you can get away with underpaying that person.
- scrabble 13y ago
  The real kicker is that while a lot of frontend skills are still valuable and very relevant, it's also a space that's changing rather quickly. People set in older patterns who haven't adapted aren't going to be as valuable as people versed in the newer patterns and tools. And those people won't be as valuable as people familiar with the older patterns who also adapt and keep up with the current state of things.
  - Bahamut 13y ago
    Also agreed. I do envy those with more experience with me who are doing more with current technologies, since they have the advantage of having done it longer. But it makes me wonder what the heck are these companies thinking when they are looking to hire if they care about # of years. You can be in the industry for a long time but be terrible.
- collyw 13y ago
  Hmm. You think you are on par with someone with 10+ years experience. As someone with +10 years experience, I now see my skillset a lot differently from ten years ago. I know a lot more now. I can not do trivial pursuit programming questions as well as I could in the old days. Or clever hacks. I can't come up with a clever algorithm quickly like I used to. I can however design a database well. I think it is easy, but then my colleagues come up with some hacky solution, I can see instantly that it will cause confusion later down the line (e.g. using the same variable for two things), and suggest a better solution. I haven't read about design decisions in a book, that comes from experience. Then again maybe the person you are comparing yourself to is a "one years experience ten times" person.

Bahamut 13y ago

It also is a red flag to me when I see that - I know I am performing close to on par with some people with industry experience of 10+ years on the frontend. All things equal, you will want the rising star, since that person hasn't hit a ceiling yet, and there's a decent chance you can get away with underpaying that person.

scrabble 13y ago
The real kicker is that while a lot of frontend skills are still valuable and very relevant, it's also a space that's changing rather quickly. People set in older patterns who haven't adapted aren't going to be as valuable as people versed in the newer patterns and tools. And those people won't be as valuable as people familiar with the older patterns who also adapt and keep up with the current state of things.
- Bahamut 13y ago
  Also agreed. I do envy those with more experience with me who are doing more with current technologies, since they have the advantage of having done it longer. But it makes me wonder what the heck are these companies thinking when they are looking to hire if they care about # of years. You can be in the industry for a long time but be terrible.
collyw 13y ago
Hmm. You think you are on par with someone with 10+ years experience. As someone with +10 years experience, I now see my skillset a lot differently from ten years ago. I know a lot more now. I can not do trivial pursuit programming questions as well as I could in the old days. Or clever hacks. I can't come up with a clever algorithm quickly like I used to. I can however design a database well. I think it is easy, but then my colleagues come up with some hacky solution, I can see instantly that it will cause confusion later down the line (e.g. using the same variable for two things), and suggest a better solution. I haven't read about design decisions in a book, that comes from experience. Then again maybe the person you are comparing yourself to is a "one years experience ten times" person.