To be honest I feel I was discriminated against and that contributed to my being excluded from meetings and not being given things to do despite asking repeatedly. I can't say those things in an interview. Should I turn the focus to personal projects and just pretend I was working on those at work instead of at night? Should I pretend the team was mostly doing maintenance rather than adding new features? Another issue is that if I talk about things the team did they still have questions as to why the team also didn't do much. I've gotten questions as to after doing that what were we working on. Would it be ok to say we were an inexperienced team with that language and it took us quite some time to ramp up so output was much lower than if we were more knowledgeable about the language. Also it was a big company so things proceed at a slower pace than small companies. But if I say that then I look like not a good fit because used to a slower worker pace than a small company can accommodate. Any suggestions?
When asked why youâre leaving, say youâre not learning as much as youâd like and there was too much process which hindered productivity. There are lots of reasons why development at a large company takes more time (maybe more legacy code, more integration points, slow build.) You also explain those things as reasons why youâre looking. Youâre used to being more productive. Also, it sounds like you learned a new language.
Just donât mention politics. Just say you are hitting a ceiling and feeling unappreciated, and want to move on to another company where you feel there is growth.
It was all new code and despite being there a year I don't learn the language because of the slow pace and not having things to do.
Who exactly knows which features were going in which release. Try researching past 3-4 years and what features were added or what future features are going to be added in your team. Then articulate a response about what you have done etc. Dont try to go in detail and stay floating on the topics. Predict the questions which could be asked and be prepared for the answers. After all in 1 hr interview with atleast one coding question. Usually they cant ask much and articulate your responses and prepare in same way. All the best. I feel for you đ
This is good advice. I'll pretend things from the past three years were done in one.
Just pick one feature... Do not lie. It's unethical and interviewers can smell bullshit.
Try to glean as much good from your current role as you can. If you tell people you fix bugs all day long, your career cannot go anywhere. Take the initiative to find something to do, something to improve upon, and write that on your resume. Usually managers will not stop you from doing a good and valuable piece of work if it doesnât eat into your expected work. In your interviews, you will be asked this question. What was your most significant project, what did you do, and what did you learn? Have a ready answer before the interview.
Yes I've thought of using a personal project as something I worked on at work as the personal project could be useful at work.
I think that would be helpful. Whatever you do, just focus on how to answer that one interview question. That is one question that almost every interviewer will ask you, like âTell me about yourselfâ. The other question is, âWhy do you want to join our company?â
Turn lemons into lemonade
Heâs asking how
Look up how to make lemonade