[banna2]

Can you please share why do you advice to stay at a company for 2 years? If someone is not getting challenging kind of work to push your knowledge and technology beyond limits? And how to portrait your accomplishments in resume for such role when u r just building API's

[scarface74]

The two years part was the “what works for 90% of the people 90% of the time” type of advice. From what I have read on HN and from my personal anecdotal experience is that a job stint of less than two years looks bad on your resume unless you have a good reason and a good story to tell - layoff, contracting, etc.

On the other hand, if you start interviewing after a year, what’s the harm? There are only two outcomes. You won’t find a job until year two and you won’t be considered a “job hopper” or you will and it doesn’t matter.

[starbugs]

I did not advice anyone to stay at a company for two years. And I wouldn't advice anything that drastical based on a short HN text and some vague interpretation of what op is up for.

IF someone is unchallenged as you imply I'd say a good first step would be to talk to your superior before following a generic "change company every two years" advice for no reason.

[scarface74]

I also wasn’t implying you should change jobs after two years. I was saying you probably shouldn’t change jobs in less than two years.

There are switching costs to changing jobs (https://news.ycombinator.com/item?id=17796166), but statistically, job switchers make more than people who stay (https://www.fastcompany.com/3055035/you-should-plan-on-switc...)