111–120 of 415 posts
I’ve been interviewing for 8 months. Getting to many final rounds, 1 lowballed offer, 1 rescinded offer, and it’s playing a mental toll. Today, I got a rejection that went along the lines of “everyone loved you and there was absolutely 0 negative feedback, but we just found a better fit.” I almost broke down, but hid behind a facade of positivity because the long weekend was starting and my kids can’t afford a bummed…
What’s the ideal interview? HR screen, tech interview, and team lead interview? I don’t know that you can reasonably compress things down to less than three interviews without relying on individuals to be better at interviewing than they might actually be.
Earlier quoted context omitted.
> We have a probation period to work out if they’ve over-promised I'm curious what you mean by over-promised? Unless you only do this for people who don't already have a job, this sounds more toxic than multiple interviews. "Oh yeah we want you to work for us, but quit your old company, we'll try you out for a few weeks and if not we'll go our separate ways" ... but they quit their previous company so it's not as nic…
If they said in the interview they’re very comfortable with Vue.js and Postgres, and then you find out after a few weeks that actually they barely know Vue or Postgres, they actually come from a React/SQLite background, they’ve overpromised. Rather than ensuring every bullet point on their resume is factual through six interviews I’ve found it’s better to assume they’re honest and as capable as advertised, interview…
Earlier quoted context omitted.
If they said in the interview they’re very comfortable with Vue.js and Postgres, and then you find out after a few weeks that actually they barely know Vue or Postgres, they actually come from a React/SQLite background, they’ve overpromised. Rather than ensuring every bullet point on their resume is factual through six interviews I’ve found it’s better to assume they’re honest and as capable as advertised, interview…
I agree with the other poster. The possibility of ending up unemployed is a bit stressful here. What percentage of people get let go within 90 days?
Earlier quoted context omitted.
You’re selling your life, focusing on chasing ever more money is a poor trade IMO. Not saying you have to join a non profit, just consider what you want to work on, who you want to work with, and the kind of hours you want to put in.
It always amuses me seeing programmers chasing as much money as possible when they make a fraction of executives or many other professions. Even if they're at the "elite grand master SRE" level. Still a fraction of some MBA.
I’ve been interviewing for 8 months. Getting to many final rounds, 1 lowballed offer, 1 rescinded offer, and it’s playing a mental toll. Today, I got a rejection that went along the lines of “everyone loved you and there was absolutely 0 negative feedback, but we just found a better fit.” I almost broke down, but hid behind a facade of positivity because the long weekend was starting and my kids can’t afford a bummed…
Earlier quoted context omitted.
Depends which section of the industry you end up in, but in the big banks which are some of the largest java shops, a cadet/intern will end up around $45k, a junior around $55-65k, an ordinary dev around $80-90k, and a senior anywhere from $115-$150k but weighted toward the lower end. Then of course there’s the rest of the buzzword fleet, DevOps engineers are a bit of a premium on those figures, architects the same.
I am seeing interns joining at 90k+ atm and you can extrapolate but on a <45deg angle from there. I even know a junior (<2yr experience) at 140k, not any kind of superstar but lucky I guess. Are you talking Aussie market? Maybe for entrenched big java teams that are reluctant to restructure their compensation for the whole team. I’d advise anyone to look at newer teams that can accommodate market rates easier.
Earlier quoted context omitted.
Depends which section of the industry you end up in, but in the big banks which are some of the largest java shops, a cadet/intern will end up around $45k, a junior around $55-65k, an ordinary dev around $80-90k, and a senior anywhere from $115-$150k but weighted toward the lower end. Then of course there’s the rest of the buzzword fleet, DevOps engineers are a bit of a premium on those figures, architects the same.
I am seeing interns joining at 90k+ atm and you can extrapolate but on a <45deg angle from there. I even know a junior (<2yr experience) at 140k, not any kind of superstar but lucky I guess. Are you talking Aussie market? Maybe for entrenched big java teams that are reluctant to restructure their compensation for the whole team. I’d advise anyone to look at newer teams that can accommodate market rates easier.
I’ve been interviewing for 8 months. Getting to many final rounds, 1 lowballed offer, 1 rescinded offer, and it’s playing a mental toll. Today, I got a rejection that went along the lines of “everyone loved you and there was absolutely 0 negative feedback, but we just found a better fit.” I almost broke down, but hid behind a facade of positivity because the long weekend was starting and my kids can’t afford a bummed…
This is why I just interview endlessly. At least one a week. You need to develop a callus to interviewing. Find the time for it by rubber stamping a few code reviews. It gets boring after a while. Just a very repetitive process after 100 or so.
1. Interviewing is a career skill that has an outsized influence on your earning potential. You need to practice it to get good and keep those skills sharp.
2. Interviewing regularly (minimum twice per year, YMMV) keeps you up to speed on what skills are in demand and what problems companies are trying to solve.
3. It's a great way to network. I'm up-front about being a passive candidate and I still get takers for interviews. Even if you don't take the job after passing an interview, you'll have a foot in the door if you revisit your interviewee in the near future or have somebody you can send their way.
4. You never know when you'll need to change jobs. Job satisfaction, change in life circumstances, layoffs/economic downturns, or any number of things completely outside of your control can force a change in your employment.
It doesn't matter if you're happy, busy, or hate interviewing--interview regularly or suffer the consequences for being unpracticed and unprepared.
I’ve been interviewing for 8 months. Getting to many final rounds, 1 lowballed offer, 1 rescinded offer, and it’s playing a mental toll. Today, I got a rejection that went along the lines of “everyone loved you and there was absolutely 0 negative feedback, but we just found a better fit.” I almost broke down, but hid behind a facade of positivity because the long weekend was starting and my kids can’t afford a bummed…
This is why I just interview endlessly. At least one a week. You need to develop a callus to interviewing. Find the time for it by rubber stamping a few code reviews. It gets boring after a while. Just a very repetitive process after 100 or so.
The amount of deception you’ll have to do is what holds me back from constant “practice” interviewing