Earlier quoted context omitted.
> PTO is a non taxed benefit. I'm not sure what you mean by that, but income from PTO/vacation/sick leave is taxed the same as any other income.
If you make 140400 a year and are getting 2 weeks of vacation. You are making $2700 a week. If you took another week off of unpaid time off. You will lose $2700 for that year. If they gave you an extra week of vacation. Your taxes wouldn’t change. If instead they gave you an extra $2700 in salary and you took a week off of unpaid time off, you have to pay 24% in Federal taxes on that income + 1.45% in Medicare (you a…
Questions to ask a company during a job interview
311–320 of 467 posts
Re: Questions to ask a company during a job interview
#312Earlier quoted context omitted.
I've never been in a position where I've not been paid for each call out. (And only one place which didn't pay for standby)
Ditto. On-call work was just regular hours, and we could use those against our 40/week obligation aka cut out early, or else file for comp time. We had a quarter of big router changes and I got enough comp time to take a decent vacation (padded by PTO days, mind you) Some data center techs I knew would get time-and-a-half for any on-call work they had to do.
Re: Questions to ask a company during a job interview
#313One I am going to start to ask is "Are all developers allowed to have local admin access of their computers?" I've struggled against this in my last 3 positions. This is a dealbreaker for me, and should be for all developers.
From an infosec professional perspective, this one is always a challenge for security sensitive places. I agree with you that developers need admin rights on their development machines, but I have witnessed first hand why many companies attempt to take away local admin rights. When I'm responding to security alerts where developers have downloaded random .dll files from the internet, or some "troubleshooting utility"…
Re: Questions to ask a company during a job interview
#314Earlier quoted context omitted.
From an infosec professional perspective, this one is always a challenge for security sensitive places. I agree with you that developers need admin rights on their development machines, but I have witnessed first hand why many companies attempt to take away local admin rights. When I'm responding to security alerts where developers have downloaded random .dll files from the internet, or some "troubleshooting utility"…
> use a good software whitelisting program that tracks elevations & the reasons for them, instead of just blanket giving everyone local admin on their own PC You can propose such a thing. If you're in charge at a company, you might get to implement it. But if you do, know that it's a huge black mark against your company. I've seen how these whitelists work in practice. They're massive wastes of time. They get in the…
Code is more dangerous than data. Personally, I'd be most worried by someone getting a virus that hacks into other computers and encrypts them and/or wrecks the network. Both can be protected against, first by cold backups and second by resilient / disaster recovery network, but both would also severely affect the company for a few days, so I'd rather avoid them.
Re: Questions to ask a company during a job interview
#315Interviewing the interviewer has been THE best way to get the job. It just oozes a confidence that you already know you're good enough to get the job, and you're trying to figure out if they are good enough for YOU. Figure out questions before hand that describe the type of good working environments or fixes for bad ones that you've had in the past. The interviewer will quickly shift and try to sell the position to y…
Re: Questions to ask a company during a job interview
#316A problem that I've had is that every company says that they value code quality, emphasize developer growth, value developer's technical feedback, etc. even if they don't in practice. I've debated taking a page from old school behavioral interviewing and asking questions like: Tell me about a time that you made a decision to improve code quality or architecture at the expense of a deadline. Tell me about a time that…
I came here to say basically this. I've worked at enough companies to know that their ideas of what their values are may not be accurate. Instead of asking about values, ask about behavior. No one is going to say no to "Do you value code quality?" Aking what they've done (and sacrificed) to support code quality will give you a better idea of what their relative values are. Asking about their tech ladder will get you…
The idea being that you will learn much more about someone / something if you ask questions that are anchored to a time and place rather than generic "unembodied" questions.
So the first question you list "Do you value code quality?" is an "unembodied question" and there is no hook for the person to dig into reality and give you an honest answer.
The second, "Who was the last person promoted?" is "embodied" in that it is anchored in time and place. And because of that, a person is going to use their memory, rather than their rehearsed "value system" answers.
Anyway, it's basically exactly what you said, but I just wanted to recommend that I thought the podcast was a worthwhile listen.
Re: Questions to ask a company during a job interview
#317Problem: Interviewers lie. I once interviewed with a company that brought me into a new, shiny, well-appointed building on the corporate campus for an interview. I did well answering their questions. And they answered my usual questions correctly. Stuff like "Can developers here choose their own tools?" and "My title is going to be Lead Engineer, will I actually be a Lead Engineer?" After I was hired, I found out eve…
This almost sounds like a joke it's so bad. When a market is hot, how can they expect you to just go along with it?
It helps that places that are awful also usually can't imagine that you would want to leave. Good places, ironically, worry a lot more about employee satisfaction. Bad places typically believe that everyone is really worried that they might not get promoted/have a long career at company XYZ so are very weak at spotting employees that have checkedout. The stick they wave is usually "you won't get promoted next year if you don't play the game!"
Of course this depends a lot on how much energy the job drains from you, but if you can still learn some stuff during the day and don't feel drained when you go home, a year is not such a bad sentence to serve for a nice bump to your savings... just don't make a career out of it.
Re: Questions to ask a company during a job interview
#318Interviewing the interviewer has been THE best way to get the job. It just oozes a confidence that you already know you're good enough to get the job, and you're trying to figure out if they are good enough for YOU. Figure out questions before hand that describe the type of good working environments or fixes for bad ones that you've had in the past. The interviewer will quickly shift and try to sell the position to y…
Your advice is correct, but depressing. These body-language games people play with each other are manipulative, and sometimes deceptive. Even if there's truth behind the assertion of confidence, the assertion was made to manipulate the outcome. No doubt, the most obvious rebuttal is that the interviewer will be doing their best to manipulate no matter your tactic, so you either circumvent them or acquiesce to them.
Re: Questions to ask a company during a job interview
#319A problem that I've had is that every company says that they value code quality, emphasize developer growth, value developer's technical feedback, etc. even if they don't in practice. I've debated taking a page from old school behavioral interviewing and asking questions like: Tell me about a time that you made a decision to improve code quality or architecture at the expense of a deadline. Tell me about a time that…
It's like they're selecting for people who make major decisions based on little or no information. I'm sure that will end well...
Re: Questions to ask a company during a job interview
#320A problem that I've had is that every company says that they value code quality, emphasize developer growth, value developer's technical feedback, etc. even if they don't in practice. I've debated taking a page from old school behavioral interviewing and asking questions like: Tell me about a time that you made a decision to improve code quality or architecture at the expense of a deadline. Tell me about a time that…
I came here to say basically this. I've worked at enough companies to know that their ideas of what their values are may not be accurate. Instead of asking about values, ask about behavior. No one is going to say no to "Do you value code quality?" Aking what they've done (and sacrificed) to support code quality will give you a better idea of what their relative values are. Asking about their tech ladder will get you…
But it's hard in some cases not to feel lied to when you see the gap. At least in dating when this happens you can get out early. You don't get the same trial period with work arrangements.