11–20 of 96 posts
What's on your resume? You sound like a full stack dev + DevOps. Both are in high demand.
Ive put "tech lead" because I developed + orchestrated everything (code, severs, "internal services" (AutoDesk (AutoCAD, Revit), MS Office, ETC). You think that's to much? Technically my job title is "Director of IT" but I dont go to enough board meetings to justify that title.
Because it sounds like there's something about your CV that is causing it to be ignored. UK standards for this are different, but make sure you don't include things like age, gender, race, or a photo. Do make sure there is correct spelling and grammar. Focus on how you used technology to solve business problems.
The other possibility is that you've hit an industry-wide hiring lull. It's getting towards the end of the year (budget time), and the economy is slowing down.
Consider befriending some people in your industry who are in a position closer to the type that you would be interested in, and asking them for feedback on your CV or at least absorbing the way they talk and present themselves by osmosis. I'm not in the UK, but at least in the European location I'm in there are many tech people circulating on local meetup (social) apps.
Throwaway acct. I left my first sysadmin job after about 3 years because the advice I recieved is that if you work solo for too long, you develop your own ways of doing things, become unable to integrate into more mainstream best practices, and become effectively "unhirable". I wonder if that has something to do with your lack of success in the job hunt. It sounds like maybe there's a lot of 'institutional knowledge'…
I don't think threatening your current employer about how in-disposable you are and how they'll have production outages if you leave shows you're a very good teammate/employee/team player.
If you've worked for 8 years doing all that and aren't getting any interest, your CV may well suck. If you were hiring a new PHP developer, consider the things you would care about in a CV you were reviewing.
I've never hired at the level i'm applying and have 0 to compare against.
I would be very cautious about negotiating a salary when you're in the position of knowing you can't get a better salary on the market. Fix what's wrong with your resume, get a better offer, and then negotiate (or not). Just not a good negotiating spot to be in if you know you ultimately have to accept what they say.
Step two: Do your job, as described in the job offer, and stop doing extra. They place no value on that extra work.
But in the long term, don’t stay, even if they do give you a raise or exceed another offer. After all, they didn’t value you before; imagine how little they will value you when you’re a bigger cost to them.
Throwaway acct. I left my first sysadmin job after about 3 years because the advice I recieved is that if you work solo for too long, you develop your own ways of doing things, become unable to integrate into more mainstream best practices, and become effectively "unhirable". I wonder if that has something to do with your lack of success in the job hunt. It sounds like maybe there's a lot of 'institutional knowledge'…
> it might very well be worth having that sit-down with your employer where you lay out exactly what will happen to their infrastructure when you leave. I don't think threatening your current employer about how in-disposable you are and how they'll have production outages if you leave shows you're a very good teammate/employee/team player.