I am a frontend developer and I have an upcoming interview with a company. Through my interview experiences I know that I am not very good at conveying my work experiences and knowledge to the interviewers.<p>Any resources that would help me to prepare for my interview and be more expressive?
I suggest to steer conversation on how end customers / end users benefited from your work.<p>Example:<p>"More sales due to improved experience and better user interface", "Higher rankings due to ....whatever work you did...", etc...<p>This basically helps you to escape (but not guarantee) stupid low level conversations on deep technical bits.
Convey that your work and experience helps to boost company business and it's relationship with paying customers vs. "I have N years of experience and know X and can also do Y".<p>Company is investing in you and want to understand their return on investment.<p>My suggestion works better when having conversation with higher level, intelligent decision making person vs. low level technical idiot manager armed with stupid coding puzzles, but worth trying anyways.
I like to go through my work history and basically cover:<p>1. What did I actually work on there. I usually pick one thing I'm especially proud of that I can talk in great detail about and answer any and all questions about.<p>2. What did I wish I could have done and talk about why - at the time - it wasn't. Examples: time constraints, lack of knowledge then that I have now.<p>3. What did I learn at that company that I was able to immediately apply at the next company I went to?<p>The first is usually all people get asked about in an interview. But the second and third items are far more important. As a hiring manager, I want to know that someone is capable of noticing trade-offs, weak areas in design, and able to learn and grow.<p>Also, if you can, talking about the second and third items with respect to non-technical things can also be big bonuses. For example, did you have a problem co-worker that you had a hard time interfacing with, but learned better strategies? Or maybe you did a poor job with time estimates, but recognized why and were able to improve on them? These are all things everyone can relate to.
Practice. Write scripts. When you find you were in a situation and were inarticulate you might think about what you should have said after the fact -- write this down!<p>Get people who know you to talk about your experience & knowledge. One time I was talking to my boss about an evaluation I was doing and he remembered something I didn't think of.