3 ms·

It's not bad to look for something else after six months. Shit jobs exist. Keep looking. Hard questions for yourself: How did I get in this situation? How did

It's not bad to look for something else after six months. Shit jobs exist. Keep looking. Hard questions for yourself: How did I get in this situation? How did I get such a mismatch between your expectations and reality? Why didn't I see this at the job interview? Answering these will help you evaluate future job offerings. Ofcourse I do not know how the interview went. Maybe you didn't ask, maybe you did and they didn't answer fairly. In the first case, ask these questions next time (for example: "Describe to me your process on how you go from source code to a production build?" "How do you run your projects? What methodologies do you use?" "How do you document/test/maintain your code quality?" "What kind of meetings do you have around here?"). See if you can ask about cultural difference as well (you mention Asia vs Europe), and avoid yes/no questions but rather something open. If they didn't answer fairly during the interview, you have no reason to feel bad for running away.

fractal618 5y ago
He said it was > a long period of job hunting I've also been met with a lot of "You're new" "You'll get used to it" "we know it's a mess, but it's not going to change"
austincheney 5y ago
> How did I get in this situation? As somebody who has been interviewing recently and worked as a developer for a long time I am confident it is due to poor expectation management. First of all definitions of "senior developer" vary wildly. At some places that could mean somebody who perform architecture and writes precise roadmaps for new efforts and integrations. At some places "senior developer" really just means been doing the same junior stuff for long enough to warrant a title bump for retention. As an example many places reward repeated "hard work" with promotions when really the goal of software is automation, so that you don't have to work as hard on repeated efforts later. That said it doesn't matter if as a senior developer they are actually are brilliant or are some expert beginner framework junkie. If they are wildly out of alignment to the new shop it is far easier to blame that new shop than perform some self-reflection. My solution for this alignment problem is to qualify decision making capacity during the interview process. If, for example I were a senior developer applying for a full-stack position, I would drill down into things like formalizing documentation (writing things down that are not code) and original code (solving a problem directly instead something external or downloaded).
PragmaticPulp 5y ago
> It's not bad to look for something else after six months. Shit jobs exist. Keep looking. Agreed, and I want to underscore this point: Don’t just quit and then look for other jobs. Find a new job first and then move to the new job. It’s easier to find another job when you’re already employed. Whether we like it or not, many hiring managers will be wary of resumes from people who are currently unemployed. But this situation is even more difficult as the OP found this job after being unemployed for a long time. Adding another period of unemployment after a short 6-month employment would start to raise red flags with most hiring managers. Remember that the person reading your resume can’t really know if the company was bad or if you were fired for other reasons. Start the job search but don’t quit until you are starting a new job.

fractal618 5y ago

He said it was > a long period of job hunting I've also been met with a lot of "You're new" "You'll get used to it" "we know it's a mess, but it's not going to change"

austincheney 5y ago

> How did I get in this situation? As somebody who has been interviewing recently and worked as a developer for a long time I am confident it is due to poor expectation management. First of all definitions of "senior developer" vary wildly. At some places that could mean somebody who perform architecture and writes precise roadmaps for new efforts and integrations. At some places "senior developer" really just means been doing the same junior stuff for long enough to warrant a title bump for retention. As an example many places reward repeated "hard work" with promotions when really the goal of software is automation, so that you don't have to work as hard on repeated efforts later. That said it doesn't matter if as a senior developer they are actually are brilliant or are some expert beginner framework junkie. If they are wildly out of alignment to the new shop it is far easier to blame that new shop than perform some self-reflection. My solution for this alignment problem is to qualify decision making capacity during the interview process. If, for example I were a senior developer applying for a full-stack position, I would drill down into things like formalizing documentation (writing things down that are not code) and original code (solving a problem directly instead something external or downloaded).

PragmaticPulp 5y ago

> It's not bad to look for something else after six months. Shit jobs exist. Keep looking. Agreed, and I want to underscore this point: Don’t just quit and then look for other jobs. Find a new job first and then move to the new job. It’s easier to find another job when you’re already employed. Whether we like it or not, many hiring managers will be wary of resumes from people who are currently unemployed. But this situation is even more difficult as the OP found this job after being unemployed for a long time. Adding another period of unemployment after a short 6-month employment would start to raise red flags with most hiring managers. Remember that the person reading your resume can’t really know if the company was bad or if you were fired for other reasons. Start the job search but don’t quit until you are starting a new job.