7 ms·
> As I noted in a previous post, switching teams is a lot easier than switching jobs. I didn’t do this before I left Stripe because there weren’t any other team
by pavel_lishin 6y ago
> As I noted in a previous post, switching teams is a lot easier than switching jobs. I didn’t do this before I left Stripe because there weren’t any other teams that I was super enthusiastic about at the time. But, in retrospect, I probably should have given this a try before quitting.
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.
- MattGaiser 6y agoDoes this solve the other problem, that job hopping is the best way to get a raise?
- 0x445442 6y agoNot only that, but I'm getting the feeling a developer's best option these days for maximizing pay increases is to spend their free time on Leetcode. Which in my opinion is a problem from an industry perspective.
- whitepaint 6y ago> Which in my opinion is a problem from an industry perspective. 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.
- ashtonkem 6y agoBecause learning a bunch of algorithms doesn’t translate well into day to day programming capability. This is exactly why those dumb whiteboard problems aren’t good for interviews; you’re not measuring what makes someone successful on a day to day basis.
- whitepaint 6y ago> This is exactly why those dumb whiteboard problems aren’t good for interviews; you’re not measuring what makes someone successful on a day to day basis. 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?
- ashtonkem 6y agoI mean, for a while there Google thought that asking how many basketballs could fit into a school bus was a good way to find good coders. Just because Google does it doesn’t mean it’s smart. And when is the last time you had to balance a binary tree or write Djikstra’s algorithm from memory anyways?
- bigiain 6y agoCuriously, in my non coding management role, I busted out Djikstra’s algorithm last year to the amazement of most of the developers, who thought the problem in front of them was insoluble. It turned out that yes, it is in the general case, but it was totally possible to brute force the results required for the constrained task at hand on a laptop in Python and store the ~60k optimal solutions in a lightning fast key/value store. 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.)
- xapata 6y agoLeetcode, Project Euler, etc. may not feel like a programmer's daily tasks, but they may yet be a good proxy for many behaviors that large employers desire. 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.
- toomuchtodo 6y ago> 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.
- xapata 6y agoI also measure my candidates' ability to fix bugs by learning the details of a language feature they're not familiar with, by finding examples and documentation. 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! ;-)
- toomuchtodo 6y agoI absolutely agree they’re necessary, but should be a realistic problem that needs solving (as you’re doing).
- 6y ago
- ketzo 6y agoIn my admittedly limited experience, nope. Team changes are almost never accompanied with a raise; usually your job title isn't even changing. 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.
- lhorie 6y agoIn my experience, no. I did an internal team transition at a company several years ago, and while it gave me a pretty good salary increase, it was not as big an increase (percentage-wise) compared to my wife's job hopping during roughly the same time span. I hopped jobs a couple more times a few years later and currently make three times more than I did back then. Some of this is attributable to differences in pay levels between cities but there's generally just a lot more room for negotiation with a new company than there is within the same company. I know many colleagues that left a company because of the ease of negotiating better offers outside of one's company.
- hinkley 6y agoIt could even go the other way because now your yearly review is thrown out of whack.
- theptip 6y agoThe power move is to have an offer in hand and then tell your company that you're considering leaving for <reason>, but you'd like to give them a chance to beat your new offer by <increasing salary to $X, resolving reason X with a team move>. 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.
- totablebanjo 6y agoDo you really think you’ll be treated the same by management if you pull that?
- howlgarnish 6y agoIn larger companies management, HR and compensation are all separate teams, and a decent manager will be negotiating "with" you and "against" the other two to get your salary match.
- totablebanjo 6y agoAh, that’s a fair point and I can definitely see that working out.
- PebblesHD 6y agoTo ~howlgarnish’s point, this is how I got my most recent promotion and it was very much a case of myself and my direct manager arguing against an opaque HR/Payroll team who generally didn’t approve promotions. no egos to damage in our immediate area by pushing hard. 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.
- austinl 6y agoI can appreciate this — I stayed with my previous company for 5 years, which seems like an eternity to most folks I talk to, but I worked on 3 very different teams during that time period. It felt like joining a brand new company each time with new challenges and things to learn. I'd recommend exploring that route before leaving if it's open to you.
- crandycodes 6y agoI've done this as well. Been at MSFT for 7 years, been on 5 different teams, and switched between PM and Dev a few times. It's been great from a quality of life perspective, I think. I've got a lot of experience I wouldn't have had if I stayed on the same team and work has stayed pretty interesting. I've also got a pretty large network of folks I know, which is helpful for a variety of reasons. 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.
- syndacks 6y agoMaybe find a team you think you can really impact with your PM+Dev skills, deliver an impactful project, then use that as leverage to get promoted within this team and/or a fleet of teams. I like what you have to say r.e. learning and enjoyment, but don't sell yourself short. You're probably a lot more valuable to the group/division than you realize.
- munchbunny 6y agoThey 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. 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.
- hinkley 6y agoYou don't know what you've got 'til it's gone. 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?
- r00fus 6y ago> 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. 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?
- monkeybutton 6y agoI've done this and having a strong manager advocating for me made all the difference.
- whoisburbansky 6y agoHow did the initial conversation with your manager go about you leaving? I've definitely left companies before instead of just switching teams because it felt like I had a tough time explaining that my wanting to switch teams wasn't the manager's fault and it was easier to explain wanting to switch companies instead without making it seem like a personal affront to the manager. I'm wondering now if I wasn't giving my old manager enough credit for taking bad news well.
- beckingz 6y agoI was rebuked in my transfer request at a startup because "transfers were rewards" and my manager didn't like me.
- jnwatson 6y agoThis strongly depends on the company structure and the political structure. There are many managers that would rather have an employee leave than go to a rival team.
- lhorie 6y agoIf there are rival teams, then doesn't that mean that by definition resources are allocated less efficiently? (and by extension that competitors will be able to outbid for talent) 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.
- pavel_lishin 6y ago> If there are rival teams, then doesn't that mean that by definition resources are allocated less efficiently? (and by extension that competitors will be able to outbid for talent) If they have enough resources, it doesn't matter. Google and Apple don't seem to have any trouble paying talent.
- srtjstjsj 6y agoConsidering that they colluded to avoid paying talent, it seems that do have some trouble. Having money isn't the same as spending it.
- bird_monster 6y ago> An internal team change is often a lot less stressful and less risky than going to a different company. 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.
- bartread 6y agoI have a habit of slogging through difficult patches that has, for the most part and with only perhaps two notable exceptions, served me well. However, I want to tell the story of one of these exceptions as a counterpoint to other comments here. 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.)
- gautamdivgi 6y agoAbout the commute. 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.
- batter 6y agoI have changed my first project because manager was unbearable. After spending one more year in the same company but different project and almost ideal manager i have realized that company in general has so many problems that make me unhappy that i have started job search outside. It's really hard sometimes to predict what difficulties are waiting for you in new team/company.
- hluska 6y agoThis story isn't boring at all - it's valuable advice, particularly for younger engineers. This is yet another comment on here that I really wish I could email myself twenty years ago.....:)