Here's the deal: Employers will exploit your age no matter how old you are. There is no "perfect age" for a developer. When you're young, they exploit you because you are inexperienced (especially at negotiation). When you are "old" they exploit by trying to play the age card. "Not a cultural fit"--LOL--fix your stupid culture and stop exploiting people, you smug fools! So what is there? A ten year "ripe" age range w…
> "Not a cultural fit"--LOL--fix your stupid culture and stop exploiting people, you smug fools! If you're hiring someone 15+ years older than the rest of your team, there are going to be some cultural differences.
Thank HN: From Google form to $1k in revenue in one month
191–200 of 255 posts
Re: Thank HN: From Google form to $1k in revenue in one month
#192Earlier quoted context omitted.
That isn't the problem. The problem is that the young guys THINK that the old guy will do this.
Sorry, I'm not clear on what you mean: they think that the old guy will write the specification and architect everything, or they think he will hack stuff together with them?
Re: Thank HN: From Google form to $1k in revenue in one month
#193Earlier quoted context omitted.
What the hell is wrong with posting a wide salary range and stating you are looking at all sorts of people then? We're trying to prevent people wasting their time chatting to people when the remuneration will never be sufficient.
Because the second you post a wide salary range, people assume they are going to land on the mid-upper end of it no matter what the range is. If somebody lands on the lower end of it, they are going to feel slighted or insulted for just about all cases aside from new grads. If I post a salary range of $50,000-$150,000 most people are going to look at it and decide that it probably pays $100,000-120,000. If somebody a…
In itself it might be enough of a red flag not to work there.
Re: Thank HN: From Google form to $1k in revenue in one month
#194Here's the deal: Employers will exploit your age no matter how old you are. There is no "perfect age" for a developer. When you're young, they exploit you because you are inexperienced (especially at negotiation). When you are "old" they exploit by trying to play the age card. "Not a cultural fit"--LOL--fix your stupid culture and stop exploiting people, you smug fools! So what is there? A ten year "ripe" age range w…
> "Not a cultural fit"--LOL--fix your stupid culture and stop exploiting people, you smug fools! If you're hiring someone 15+ years older than the rest of your team, there are going to be some cultural differences.
Re: Thank HN: From Google form to $1k in revenue in one month
#195Earlier quoted context omitted.
Just my 2c -- I'm in the US and I disagree. For example, many of the jobs allow for a very broad experience. For example, in my current job, we are often looking for a smart, energetic people to work on X. Someone with a BS just out of college? An engineer with 10 years of matching experience? Tech lead wo just built X elsewhere? We will take either (if we like them) and adjust responsibilities instead. This approach…
> Someone with a BS just out of college? > An engineer with 10 years of matching experience? > Tech lead wo [sic] just built X elsewhere? Sounds like you have three job postings crammed into one listing. Y'all on that tight of a budget?
We cannot post three postings with intent to hire one person: Our group works on X. There is a group working on Y across the hall (and a bunch of others) and if we advertise three postings they will go to top management and HR and argue that one of our postings should be theirs.
Competition between groups on lab space, office space and good employees is friendly but extremely tough. Hiring someone who is a good fit and will likely work in our group for at least a few years is a huge benefit. Thus we would rather spend extra time trying to find a person who is smart, likes what we do and is genuinely interested in working on X, at whatever experience level, and snag him. This makes us open the "skills" window pretty wide.
Re: Thank HN: From Google form to $1k in revenue in one month
#196I thought I was on medium.com.. You need to add a call to action to the end of your post! Add a short line - "if you've experienced ageism checkout these job listsing at /link" or "to see what I built visit /link" or something similar. Lots of lazy people want to click a link at the end of your post to see your site rather than trying to find a link in your profile or scrolling all the way to the top. Plus when someo…
http://devmarketing.xyz/ by https://news.ycombinator.com/user?id=mijustin
Re: Thank HN: From Google form to $1k in revenue in one month
#197Re: Thank HN: From Google form to $1k in revenue in one month
#198Can you do another good deed and require your posters to include salary range in their job ads? It's the norm in the UK and we successfully forced this in Poland (though posters almost NEVER post salaries here). How? The companies need IT staff so much that almost all IT job boards (at least the most popular ones - like FB groups or https://nofluffjobs.com ) started requiring the salary range. I think your idea is pr…
I agree completely and I think this is solid advice for OP.
Re: Thank HN: From Google form to $1k in revenue in one month
#199Earlier quoted context omitted.
What the hell is wrong with posting a wide salary range and stating you are looking at all sorts of people then? We're trying to prevent people wasting their time chatting to people when the remuneration will never be sufficient.
Honest question: Is a salary range of $50 - $100k really valuable to you as a job seeker?
Re: Thank HN: From Google form to $1k in revenue in one month
#200Earlier quoted context omitted.
What the hell is wrong with posting a wide salary range and stating you are looking at all sorts of people then? We're trying to prevent people wasting their time chatting to people when the remuneration will never be sufficient.
Honest question: Is a salary range of $50 - $100k really valuable to you as a job seeker?
If I came from a place that paid $50k, I'd expect them to be able to give me a small bump but likely land me in the low-to-mid part of the range and I'd apply. If I came from 75k I'd expect higher end of the range, and I'd apply. That could be unreasonable depending on how they place different tiers of engineer on that range, but if it is then it's better to split out the jobs by title (Software Eng Jr./Sr/Staff/Principal). If I came from over 100k I'll pass because I don't think they can afford me regardless of title.