Help me out here tweeps: Assuming all other things being equal and an appropriate project, etc., a finishing PhD student with 8 pub'd papers (2 as 1st author) would be a strong contender for pretty much any post-doc position, right? That's a damn good CV for that stage, yes?
-
-
Hope this helps!

-
Definitely. Of course, a lot depends on how they perform at the interview, exact content of the pubs, general 'fit' with the lab, etc. I guess I was really asking "Would this be sufficient to get them an interview?"
-
Yes, it would IF they explain they fit the required and even some of the optional stuff, even better if they address all. Would help even more if they have an active github/equivalent and informative website. Underlining: I'm speaking about the labs I have worked in.
-
Basically, they have to make it clear how they fit in with the required job and the culture of the lab. Write clearly how they fit the bill, a CV is not enough to show ideas for the future, etc. Is this making sense Matt?
-
Yes, absolutely. Very helpful.
-
They need to link to the all the relevant stuff BTW. I will not try to figure out what their webistes are and will certainly not Google them.
End of conversation
New conversation -
-
-
This Tweet is unavailable
-
I think skills are a weirdly intangible thing to describe. I'd outline things I've accomplished which evidence the use of that skill (assisted with the preprocessing and analysis of an fMRI dataset; trained several students to conduct fMRI analysis; written analysis pipelines)
-
I'm speaking from my limited perspective, which is mainly coding skills. But yes, even fMRI skills is something I've seen somebody lie about on their CV and admit to it in private.
-
I can elaborate on what other lies I have seen, e.g., people saying they have experience in Python but admit in private they have never coded in Python. Same with git. Does this help clarify?
-
Also
@froukehe "What for one person are strong fMRI skills are rather limited to another." It's not so much about qualifying as strong or not, just the presence of having done it. More of a binary thing. -
This Tweet is unavailable
-
I mean using it in published work — something you can point to with evidence.
End of conversation
-
-
-
So true. Especially easy, when you overestimate your coding skills! If you're honest about your abilities, it will be much more likely that other skills will be weighed to compensate. If you lie, how do I know you can do the other things?
-
Exactly. And everything should be backed up with something. Don't just say "I know Python" actually indicate where you have used it. Although for Python you might not have to if you have tons of projects that use it publicly available.
-
I actually asked my applicants some coding related questions and this was super informative. One person had like 5 relevant languages in their CV, but could not tell me how to move data from A to B.
-
I am not a massive fan of coding questions during interviews, but I think you asked some really basic stuff, which actually I agree with.
-
Why are you not a fan of coding questions? (Genuinly interested, as I am new to the hiring game.)
-
I am not a fan because I google everything as I go
-
This Tweet is unavailable
-
I think this is a bit by-the-by. Obviously if you are hiring somebody to write custom algos they will have tons of github/equivalent evidence they can write stuff.
- 8 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.