3 ms·
Software engineers tend to over estimate their value and seniority. It's the opposite for their main customers, who tend to under value what they get for their
by jillesvangurp 5y ago
Software engineers tend to over estimate their value and seniority. It's the opposite for their main customers, who tend to under value what they get for their money. So, this combination of poorly matched supply and demand makes for a lousy market. A good strategy is to be above that. I don't do coding exercises and I set my rate above the rate where that would be a thing at all. That puts a stake in the ground: you are hiring someone with seniority. Either that's what you are looking for or you are wasting both our time. It's that simple. Of course up to me to live up to that. It's not all about being cocky here but actually managing to get to the stage in your career where you can do that and get away with it.
The value of OSS and being part of its development is that it's done in the open and that the active contributors are undeniably very good at what they do if that is apparently keeping a lot of OSS users happy. If I have to choose between two engineers and one of them is behaving professionally on Github with a nice track record of issues, pull requests, perhaps a few nice repositories with lots of stars, etc. It's no contest at all. I'll be extremely biased towards the latter given their proven track record and not really interested in why that other person might feel above doing that.
IMHO it's impossible for good developers to engage with the OSS world and not contribute to it. At minimum, you are going to run into issues and act professionally by investigating and engaging on the issue tracker. It's just basic due diligence. And it includes looking through existing issues, the comments, and where necessary the code. A lack of any Github activity whatsoever for me is a red flag when it comes to seniority. You can't be senior and not do that.
Leverage in business negotiations comes from understanding your customer and being able to address their real needs (as opposed to what they are asking for). A simple strategy is to ask for more than they are offering. This puts them on the defensive. Now they need to argue your value down and they are actively thinking about what you could do for them. When they say no, it needs to hurt them a little because they are missing out. They have to actively regret the decision. You won't always get what you want obviously and if you consistently don't either your sales skills suck or you are the problem and you need to own that. Either way, try to level up. If it's the latter, engaging with some OSS projects isn't the worst plan.