Accountability:
The key to every interview process is to understand the topics that the employer cares about. Everyone is hired because there is a need and they are looking for someone to fill that need.
Do your homework and learn as much as possible about the position, take the initiative and investigate products, methodologies that you might be working with.
Try and explain this to a Bioinformatics friend - what you've been working on, how you went about designing the workflow on the project and justify your choices. Check if you can explain the bigger picture behind your activities. State a few challenges you faced and how you solved them, and try and summarize how your approach to problem solving has evolved.
Your target is to prove that you are in control of the details and you are also conscious of the bigger picture. You're learning as well as getting things done.
This is how I'd approach it. This means more time reflecting on how to market what you've done and less time spent on learning new stuff just for the interview - interviewers can spot such quick learning pretty easily.
Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
version 2.3.6
Your spelling.....? If you know what you are talking about you won't need any preparation at all, at least that worked for me ;)
How much time do you have to prepare yet? I mean, this is almost impossible to answer, it totally depends.
I am aware of my project, just curious about Genomics part, Like what he will ask lets say about - Exome sequencing, RnaSeq Etc
An observation: Attention to details and an ability to quickly judge what's standards are is important in any job. Your apparent inability to notice the "add reply" button and that every answer you give gets moved to an answer is telling in this regard.
If I were your interviewer, my main concern would be your ability to convey results in a coherent manner to my clients (i.e., the "preparing reports" portion of the job description). If the manner in which you're presenting yourself here is the same as in your interview, then I would never hire you.
+1 on the attention to detail. You'll get better at it over time but boy does it help you! Also, Devon, OP's relatively new to the UI, might need a bit more time to orient themselves.
Thanks Ryan, Actually I am new here.
Even so, only so much can be excused from folks that need keen observation and quick learning as part of their profile, Gaurav. I can personally vouch for the importance of quick learning, it got me my current job :)
Thank you sir
Ummm, why are you thanking me again?
Scientists man - they don't like waste - "you thanked me already ;-)"
lol but this is a different user and that thank you sounds half-apologetic. I was wondering why.
This is easy to accidentally do if you use the social login option and have multiple gmail accounts. For example, when we were on vacation, my wife would check her gmail account from my laptop. I would then get logged into biostars as her: kamueller79.
In the interviews I've attended, I've always been asked to explain my project. Questions usually were on if I knew basic algorithms, such as Burrows Wheeler, and where they are applied and why. This may also be because my experience at the time was with de novo RNA-seq with De Bruijn graph based tools, a tech that most established places I interviewed in rarely used.
I'm not sure if you specifically refer to an interview in academia on industry and which position you are applying for. papers are also another important part, at least in academia. you can do lots of bits and pieces in different projects but most people use papers as final proof that what you do is of good quality and that you are productive. if you don't have papers then you need (as others explained already) a very good understanding of the ins and outs of your project and how you can use what you learn to give an advantage to your employer. as Istvan said, do your homework...and I'd add, as if you were in war, the better you know your enemy, the better chances you have to win... :)