At Stripe and each of my jobs before that, I had had a short commute to a beautiful office, and got to experience the instant gratification associated with developing purely software-based products. Now, I was stuck taking a crowded train to a dark office littered with hardware parts, working on a product that would take many years to reach mass-market adoption due to pesky little things like manufacturing and road s…
Quitting a New Job
101–110 of 246 posts
Re: Quitting a New Job
#102I recently started a new, lucrative team lead job in a problem space I was interested in that promised to be structured, ambitious, and full of opportunity. I even requested a follow-up post-offer to make sure it was a good fit. But after only two weeks, I realized it was a command-and-control death march.
No product ownership. Design your database up front. Complete waterfall but with developers and team leads responsible for each phase. A drive-by micromanaging executive with a team far too large to micromanage. Implementation teams of (only) junior developers had spent months prior to my arrival talking/meeting/designing - with virtually nothing to show for it.
Every day was a calendar full of meetings to prepare for other meetings. Other teams and their managers were reporting fraudulent statuses creating the illusion of progress when no actual progress actually existed. Asking questions or offering any pushback was met with passive-aggressive anger. Any effort to create a little bit of structure amidst the chaos was, almost immediately, thrown away.
So I decided it was best if I resigned. They even kept me around for a couple of weeks after I resigned which was nice, and that two weeks confirmed I made the right decision. A number of other team members and peers reached out and expressed agreement or envy - they wanted to leave as well.
But despite those assurances that I'd made the right choice, it was a tough pill to swallow. I've never worked anywhere less than 18 months. I love building good software and I hate job hunting. I'm debating whether to put this experience on my resume or not because it's such an outlier in my professional experience and was such a short stent.
Here's hoping the next opportunity is a better match. If you're an employer in DFW (or willing to take on a remote) looking for a Team Lead or hands-on Development Manager that can code, I'd love to chat.
Re: Quitting a New Job
#103Earlier quoted context omitted.
> This is all on top of the fact that engineers are woefully underpaid. I have finance friends that make literal millions in yearly bonuses. This is virtually unheard of in software, even though we provide orders of magnitude more value. That doesn't necessarily mean engineers are woefully underpaid. It may just be that your finance friends are obscenely overpaid. Though whether all/most engineers provide "orders of…
"Provide value"? Hmmm. To whom? Not humanity in general, I think." The organization they're employed at. Which is obvious because we're talking about jobs here; that's what salaries are, in part, based on.
Though I am not quite sure the average finance person makes more than the average software engineer.
Re: Quitting a New Job
#104After 4 months, I felt numb and that would last every week from Monday to Friday. I wanted to be somewhere else so bad.
But instead of option 2 ("Start exploring new opportunities but don’t quit until something better is lined up"), I chose option 3 ("Stick it out for at least a year") for these reasons:
- With only €800 saved up (had just invested €5,000 in a fishing business that had failed) at the moment I realized it wasn't a good fit I couldn't afford even a month of bills.
- It would look bad on the resume, and might have to justify it to next prospective employers.
Also due to unfortunate circumstances, my life was administratively a mess: there was a massive 6-month delay in the delivery of new residence permits. And by the time my papers got processed, social security information was no longer up-to-date (only valid for 3 months), causing an additional nerve-wracking 5-month delay. As a consequence I couldn't quit or even get fired as, in addition to the mess above, I would have to update employment information (and get possibly another 5-month delay). After my annual review with my boss and a PIP, my salary got cut 10% (had no choice)
The happy ending? When I finally managed to get my residence permit and successfully updated my social security information 18 months after I joined the company. I looked for and found a new job, handed in my resignation and joined the other company.
Re: Quitting a New Job
#105Earlier quoted context omitted.
Not 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.
Leetcode, 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 f…
Exactly! Thank you for formulating what I always knew subconsciously.
Re: Quitting a New Job
#106Seems to me like he felt out of place at a robotics company where the bar is quite a bit higher than your typical webapp company. Different strokes, different folks.
Re: Quitting a New Job
#107> 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 t…
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.
Re: Quitting a New Job
#108Earlier quoted context omitted.
How was he discovered? It would be easier to do this nowadays, given the whole remote thing.
The other employer found out, IIRC, through his LinkedIn profile and contacted us. Been several years though so I’m only moderately confident in that memory.
If this continued for a while and you were happy with his work prior to discovering this, why let him go?
Re: Quitting a New Job
#109"When I started my second job search, I was worried that the short tenure in the job I was trying to leave would be a turn-off to perspective employers. In reality, however, it wasn’t a big deal- people asked about it, but seemed satisfied with my 20 second summary and then moved on to other things." Alternatively, you can simply leave your new position off your resume and not talk about it in the interviews at all.…
Re: Quitting a New Job
#110After what they had done, it was a surprise how bad they took it. Very serious threats to my future employability and well being. I really suffered during the whole call, trying not to laugh and keep it professional.
It was also a hardware company. I worked for another hardware company later. Not sure if there are other kind of hardware companies there in the Valley. But for me, there's a clear rule: never work for another hardware company.