You know I know folks who've actually taken these kind of opportunities and sometimes it works, but other times it results in a) you finding out there are problems with the transfer (headcount or manager blocks transfer) and b) being distracted from getting out of your current situation.
It's 20/20 hindsight, for sure - but I like to think of opportunities missed as simply "outside my light-cone". How likely was it you would have broadcast your departure early?
That's always a judgement call on your part. Were your problems just with your part of the management tree, or were they more systematic with the company? If it's the former case, switching teams might help. In the latter, best to get a fresh start and new perspective. Most people feel a bit of exceptionalism when it comes to their team being not like the others, without knowing what your particular issues with your current situation are. In my personal experience "if only you'd have let me know beforehand" comes more from a place of self-interest in finding/retaining talent than necessarily interest in the other person's career.
What people say they will do for you after you've already said goodbye and what they'll do when you just ask for change are often very different things.
It's one of the reasons they say not to take the counter-offer. Because one day while you're brushing your teeth you realize that if they could cough up that much money or control when you tried to quit, why hadn't they factored that into your previous review, when half as much might have prevented the situation in the first place?
Biggest downside is economic; can't negotiate new pay when changing teams by policy and you've gotta build a new case for promos/etc. People who have changed companies 2-3 times are likely making significantly more money than I am. I try to keep it in mind that I'm paying for quality of life by staying, so I need to get my money's worth or it's not worth it.
Some recent Apple threads seem to support the idea that there was intense internal competition and lower overall compensation at Apple, compared to other tech companies of similar caliber.
If they have enough resources, it doesn't matter. Google and Apple don't seem to have any trouble paying talent.
This statement really nails it. If you change teams and are still unhappy you can always quit. If you quit without having changed teams and then hate your new job, you might not be able to go back to your previous company (but new team). I think it's general good practice to give another team a change before you leave the company if you're on the fence. If you know it's a company problem, bail, but if you think it could just be your team, give it a shot.
Maybe it's just me, but I like to minimize the amount of decisions I make that I cannot undo.
Why? If a person can learn bunch of algorithms and apply them to custom problems they probably can do quite a bit with computers. And it shows that they probably can learn new stuff rapidly as well. I don't get why so many developers hate Leetcode. I love it personally, I think it's great. And also, I think people are just lazy and don't want to learn new stuff so they whine instead. I don't think whining will help them.
I'm not trying to denigrate it by labeling it useless - competitive problem solving/"sport programming" is a fun activity and can be a rewarding hobby, but it's important to recognize it as such, as a hobby that's only tangentially related to most actual development work once you move above a certain base competency level ( I'll grant it that it is useful for people without much practice in actual programming to do a bit of it.)
It's a problem from the industry perspective if we as industry have many people spend a lot of time doing things that don't benefit the employer (since grinding leetcode doesn't make a non-junior person better at their development job, it's an orthogonal skill) and that doesn't benefit themselves personally (we're talking about people who don't want to do leetcode just because they enjoy it) but only through the zero-sum game of competing for jobs effectively by "peacock signaling" of who invested/wasted the most effort in leetcode. This is effectively a lose-lose competition, spending a lot of everyone's time without a net benefit.
If that was the case, you think all of the biggest tech companies that have billions of dollars would continue using it? Did you ever consider that you might be wrong?
And when is the last time you had to balance a binary tree or write Djikstra’s algorithm from memory anyways?
I didn’t reproduce it from memory though (but I did choose to port a Java version in preference to any of the existing Python versions I found, because it’s code was structured in a way that I grokked much easier. Possibly due to my not totally expert idiomatic Python skills, I’m really a Perl coder deep down.)
(And I never had to do any whiteboard performative coding to land this gig either.)
Totally wouldn't work for Google Maps doing shortest path routing globally, but for an event with only a couple of hundred POIs and intersections, it's a cheat that seems almost magical to people who have some concept of the algorithmic problem, but haven't worked out the "trick".
If I were asked to whiteboard this, I would 100% be asking that constraints of the dataset up front. (I'm not too sure I'd have been smart enough to do that a couple of decades back, when I last had a "perform for us code-monkey!" type of job interview...)
No...
> at least not one that’s possible to administer cheaply.
Ah, yes. AFAIK, Behavioural interviewing works, but it does require training and thoughtfulness. You have to know what you're looking for, and ask questions specifically targeting that. You definitely cannot just throw a random employee into an interview with a list of questions and expect it to work.
Mostly what you deal with is architectural problems. And when it comes time to fix slow code, the problem won't be O(n^2) code but a mountain of code where the constant factor C is somewhere between log(n) and sqrt(n).
Now imagine your dance skills accounted for 99% of your score during the courtship (hazing) ritual.
Leetcode is even less relevant. I can google algorithms. Dancing's an actual skill.
But these topics are very, very far from being everything important. I would put them under soft skills, especially in cross-collaboration and working with non-engineering groups. And I would put them under having the type of knowledge and experience in approach that, especially combined with the above soft skills, allow us to push the direction of the company forward.
As a dumb example off the top of my head: It's great if you know how to average a batch of numbers efficiently. It's better if you know how to do such in a streaming fashion, and recognize that we can use that within our architecture to materialize savings. And, it's best if you can convince the business that there's no need to calculate the average because we can do streaming estimates for any quartile.
I think algorithms per se don't necessarily give you much of an advantage. For example, LIS[0] is fairly frequently-run algorithm if you work with web stuff, but nearly no one in that specialization knows how to write it from memory (and knowing about it doesn't translate to being able to write other algorithms)
Where I think leetcode helps is in giving you an opportunity to practice the skill of putting together various building blocks in a semi-realistic fashion (e.g. having to use a memoization trick to get under the run time threshold is something that is similar to real life performance work, despite the exercise itself being completely unrealistic).
[0] https://en.wikipedia.org/wiki/Longest_increasing_subsequence
I think people are just lazy and don't want to learn new stuff so they whine instead.
For example, a large employer may want a willingness to do arbitrary, difficult tasks that appear meaningless. These same employers may have a variety of software maintenance tasks that require recognizing a pattern of problem, knowing the appropriate algorithm from Ye Olde Textbook, and quickly applying it.
These edge cases might exist, although I argue the more likely problem is that hiring is hard, expectations can be unrealistic, and so it’s easier to fall back on puzzles and call them an objective measure of technical competency and soft skills. Project Euler is fun, but Stack Overflow is likely more relevant for your day to day for solving business problems with software.
I find that many junior-level candidates scrape by with Stack Overflow, but sadly have little competence when it comes to reading documentation. Candidates for more senior roles have a similar problem regarding systems design. They can find and parrot little statements they've seen on forums, but when you ask them to explain, their understanding turns out to be shallow.
I don't use programming exercises as a sufficient measure, but they are a necessary one.
Now I feel obligated to add that footer: We're hiring! ;-)
Side note: you should put some contact info in your profile so people know who you are hiring for anf how to contact you. :)
Exactly! Thank you for formulating what I always knew subconsciously.
That's not to say they're a bad option, but it still seems like you've gotta jump to a different company to maximize earnings.
Some companies will flat-out refuse to negotiate in this way as a matter of policy, and some will really appreciate you giving them the opportunity to bid to keep you; it really depends on the company and their comp strategy. I think as long as you're earnest about the conversation and don't try to run a bidding war, most companies won't burn bridges with you over a round of negotiations in this fashion.
The biggest issue we encountered was arbitrary requirements in the paper documentation of the role we were aiming to move me into, including a ‘hard’ requirement for an engineering degree with honours, which suddenly became less of an issue when the argument was ‘im going to accept another role but you can match it with x salary and title’ in a polite discussion with department head.
This will only apply to very large companies though, ymmv.
A few years ago I started a job where, within the first week or two, I had serious enough doubts about whether or not it was going to work that I spoke to my manager and said that I wanted to leave (even though I had nothing else lined up). He was really good about it and after we talked I decided to make more of a go of it, but it was the wrong decision and I've always regretted it.
In the end I stayed for 8 months and was miserable and frustrated for the entire time. This was, I think, a contributory factor (though by no means the only factor) to the breakup of a relationship that I valued very deeply, and that I have also always regretted the end of. The end of that relationship was really the final straw: the moment I realised I needed to bail, and that I should have bailed long before.
I still I didn't have anything definite lined up, although I did have three options on the table. In the end I chose one of them and started after taking a month off to recover. Even had I left at the beginning, I don't think I'd have struggled for work though.
Every situation is different, and staying is not always the right thing to do especially not - as was the case in my situation - where the cultural and ways of working gulf is so large. I have no awkward explaining to do about my CV but there are sometimes more important concerns in life.
(I've omitted a lot of specifics because I don't want to name either the organisation involved, or impugn the people either - many of them were great. There was certainly nothing unpleasant going on of the sort we've seen discussed a few times recently on HN. It was simply a case of an unresolvable culture clash. The commute was also a horrible slog - anything between 60 and 90 minutes each way even on a motorcycle, and I hadn't realised how exhausting that amount of riding every day would be.)
If you have a 45 minute commute which is allegedly "normal". It's an hour and a half. I would add another hour to that to make that a true door-to-door figure, i.e. from the time you decide to get ready (past breakfast/morning coffee) to when you're actually productive at your desk. Same in the evening from the time you shut work to when you're back home.
If you sleep 7 hours a day, you have 21 waking hours. You're spending 15% of your time (2.5 hours) on a commute. That in my opinion is a lot of waste.
My point being most people seriously underestimate the cost of the commute. It's almost like saying you have to work at least 2.5 more hours a day but you won't be paid for it.
Exactly this.
The way it worked for me is that on the way in just the ride itself would be 70 - 80 minutes, and then on the way home it would be anything between 90 and 115 minutes.
The longer duration on the way home was firstly because the traffic was generally worse, and secondly because I'd always have to stop for fuel. My tank range was 160 - 180 miles, and I was doing around 115 for the round trip. In theory I could alternate fuel stops between morning and evening, stopping on every third trip, but I never like to run the tank that low in case - for whatever reason - something happens that means I need more fuel.
The net result was between 2h40 and 3h05m of travel time every single day. And that's with filtering through traffic. If I weren't doing that you could probably add another 30 - 45 minutes on to both trips, which would mean spending up to 4h35m commuting. That's on top of 8 hours in the office.
Riding a motorcycle is much more tiring than driving a car. Partly this is because it is more physical, and you are of course exposed to the elements so your body will be burning more energy to stay warm even wearing proper winter gear, but also because you have to concentrate a lot more and be a lot more aware of your surroundings because you're so much more vulnerable.
That amounts to an 11 hour day where you're "on" - i.e., basically working. You're probably more "on" during the commute than you are in the office because, believe me, you cannot afford for your attention to waver for a second. This in itself suggests the commute is too damn dangerous and you probably shouldn't be doing it. A couple of minor incidents, and one that was more serious where somebody drove into the side of me, brought this starkly into focus, and also contributed to me moving on.
A few years ago, I was looking for a new job after being laid off. I had two competing companies to choose from, and chose the one that sounded like it would be more exciting. After about five months, though, I was miserable and called the other company to see if they'd still take me; they did, and I've been happily working here since.
But after I announced my departure, a few engineers from other teams came up and told me they wished I'd let them know before quitting, since they would have been glad to have me on their team instead. They knew the reasons I was feeling frustrated, and felt confident that those issues were either not a problem on their team, or were at least being worked on. I still kind of wonder how true that was, and what would have happened if I'd made the switch internally, instead.
Anyway, that was kind of a long and boring story - two whole paragraphs! - but I think this was probably the one of the more valuable parts of OP's post. An internal team change is often a lot less stressful and less risky than going to a different company.