Senior engineer sounds about right.
How many years of experience do you have (both in total and in this org/position)? Also, can you estimate how much value you've brought to the org? Example: if the web app you wrote was not made, what would the loss be?
Nah, seems more like someone spamming thier site. Every post of ops links back to the same site. Used to be normal posts. Now they've moved to making some kind of shitty ragebait?
No, thank you. I'm done with putting in volunteer effort for these kinds of things. I transitioned to mostly lurking on reddit, and I'm likely to remain that way here as well. Modding requires too much of a time and effort commitment for something that I'll have nothing to show for depending on the whim of others.
That is an understatement. I'm a former mod of r/iama (u/Brownboy13) and I was signing on to handle a high profile ama when Victoria messaged that she wouldn't be able to help us as she was let go without notice. Admin didn't even bother informing the guest that the employee handholding them through the process would no longer be available. We were caught entirely off guard and I don't think /r/iama has ever been the same. There was a level of trust the /u/chooter would be in the same room as a guest or at least on a call and make sure it was them answering and not pr teams. It's been like fucking pr junket since then.
This was the start of my disillusionment with reddit, and it seems to have been finalized with this last shitshow of a decision.
Yeah, Senior Software Engineer is a good match then.
Works about right for the workload, responsibilities and the YOE.
The reason I asked about the impact/value is that it's a good way to argue your case. If you can quantify 'x' hours of manual effort (and the estimate should be an average person doing the work, not the best case), then you can start arguing using these numbers to show that you bring value to the org.
While it sounds like your supervisor seems to be pretty solid, it's possible you'll eventually sit down with someone esle who'll be deciding the final 'value' of your effort and would have a vested interest in paying as little as possible. For that conversation, whenever it may happen, you need to be fully prepared. That's going to involve hard number. Effort saved, value created, costs saved etc. It's difficult, but it's a useful dataset to have.
I've worked in smaller orgs like this in the past, and it's occasionally an uphill battle to get paid commiserate to the value you bring to the table. It's a good reminder for management that you're not easily replaceable and that they need to kep you interested enough that you don't wander off.