Live data from Hacker News

Ask HN: Should I checkmate my employer?

news.ycombinator.com

1–10 of 96 posts

Ask HN: Should I checkmate my employer?

#1
Dear NH

I've been working at a company for 8~ years.

In those 8 years i've taken them from a small "home server" to a full 42U rack (AD, procurement + all services ) & 20K+ LOC (20+ git repos).

I'm currently earning £60K a year ($70K) and I'm beginning to feel "aggrieved", everyone tells me I should. They're a "SMB" but they wont/cant justify a raise.

The problem/s? They wont give me more engineers & nobody wants to hire me based on my current CV.

My CV has got 0 response. This is drafted fresh, with my entire circles feedback (though I out earn my entire circle).

I know they would counter, beyond what they want to, if I got another offer.

What do you do here? I'm applying for jobs in the £60-£100K range but get no response - is my CV BAD? Is my XP Bad (PHP, but everything I apply for is PHP)? What am I doing wrong?

I half want to runaway to "tourist destination" and serve drinks - I will fail if they dont expand my department soon.

Roast me HN.

Re: Ask HN: Should I checkmate my employer?

#4
post #2

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.

Re: Ask HN: Should I checkmate my employer?

#8
You would be better off asking this question to a recruitment consultant, ideally one that specialises in whatever it is that you would label your core skillset.

Without seeing your CV, my guess would be that you're missing some criteria that the orgs you're applying to are applying as a front-end filter. For example, maybe you don't have the right degree (or maybe you don't have a degree at all), and the places you've applied to auto-bin CVs which don't meet this standard. This is something a recruiter can likely help with, either by manually bypassing the filter or by pointing you towards orgs which don't have those requirements.

The other thing I would say is that it's pretty clear you actually want a raise, not a move. Is that coming across in your applications? I wouldn't personally waste time interviewing someone who didn't seem like they were genuinely looking for a job change.

Re: Ask HN: Should I checkmate my employer?

#9
post #4
post #2

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.

if you want to be an IC, then you are a "technical operations expert with operating and deploying services"

if you want to lead, embrace the "Director of IT" title and play up the fact it was an SMB if you're going for a relatively low level leadership role (team lead, etc).

whatever you do, get rid of the phrase "tech lead". i've yet to meet someone who described themselves with that term that didn't make me go "this fucking guy"

Re: Ask HN: Should I checkmate my employer?

#10
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' about how that 42U rack and the rest of the network is assembled that only you know. It would be expensive for your employer to replace you, but with an external consultancy that replaces a large fraction of your infrastructure with something they can manage, they could survive if you left.

If you're willing to take the risk and switch careers, 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.

Edit: I would reconsider how you wrote your CV.

- It's not a matter of the degree to which you fit some specific title (didn't go to enough board meetings to be the Director of IT, or whatever). It's not percent score match, it's pass/fail. Were you the director of IT, or weren't you?

- Eight years is a lot of problems to solve, and a lot of weird niche technologies to learn just enough about to be dangerous with. Those are specific examples of your ability to be really good at the stuff you've been doing. Mention it. Plus, who knows if someone else is looking for someone with experience with a weird niche technology?

- Given how long you've been doing this job, PHP dev might be too big a leap to make at one go. Might be worth looking for something halfway there, that's still perceived as similar to what you've proven you're good at.

Post reply on HN