Skip to main content

Top five mistakes scientists should avoid when writing a commercial CV

By Kim Nilsson, PhD
I used to be a scientist and wrote pages and pages of job applications that included conferences attended, proposals granted, publications etc. Then I wanted to leave academia for business and the process of learning how to write a commercially-aimed CV started. It was a painful exercise of trying to fit into a smaller wrapping and emphasise new parts – sort of like an extreme make-over of the CV. Unfortunately there were no plastic CV surgeons to help me then, and now, as a director of a recruitment firm helping PhDs, I see the same mistakes repeated over and over again. So, here it goes: the top five mistakes that you do not have to repeat again.
1: Publication list
The by far most common, yet so easily corrected, mistake scientists make is that they leave their publication (or conference/proposal) list in. Unfortunately it is of no interest to recruiters. You will be assumed to have published your work if you have a background in science but exactly how many, in which journal and as which author does not matter at all. Easy fix: delete it all.
2: Too technical
Another, relatively easy improvement is to avoid being too technical in your descriptions of your work. First of all, acronyms are not allowed. Think of it this way, if your parents would not know the acronym then leave it out or explain what it means. The only exception is programming languages which are ok to leave as acronyms. You further need to translate your science work into plain language. Again, imagine that you are explaining what you do to your parents. If they could afterwards sort of explain to their friends what it is you do, you have done a good job. That is the way to go on your CV.
3: Tasks not achievements
So you sit down to write your CV, you come to the work experience section and you think, ‘what did I do in my current role?’. Then you start to write the tasks that you worked on. Not a good idea. Work experience descriptions sounding like a job spec are wasted on a recruiter. Why? Because anyone can do it. The better way is to talk about your achievements to show what you can do. What did you achieve in your role? Quantify if possible, did you save the company/institute time or money? Did you produce code that exceeded expectations? Did you get published, invited, cited, awarded, recognised etc.? You need to show the recruiter that you can add value to whatever task you do which you do by clearly demonstrating how you have performed to date. Not the easiest fix, but certainly the most valuable.
4: Listing too many roles
A lot of the time I get work experience lists containing entries down to the very first jobs out of college which is not very useful. You may think that you are a) being accurate and b) showing your work ethic but what the recruiter sees is a) a reason to think that you are too old and b) a cluttered CV that will take too much effort to comb through for the good bits. Keep it to the two or three most important/recent roles and either leave out or bundle the other ones. That gives you more space to focus on your achievements in the important roles and to personalise.
5: Personalise
People hire people, which is why it is not wrong to personalise your CV a little to show personality. There are two main ways I always suggest people to do this. First, you can write a little “personal statement” or “summary” at the top of your CV. This is just a few sentences summarising who you are, what your background is and why you are looking for a new career. Second, I always recommend adding three personal interests at the bottom. This could be sports, cooking, arts and crafts, anything really as long as it is interesting and catches the attention of the recruiter. Make yourself memorable, likeable and interesting.
To conclude, there is no guarantee that these tips will land you a new job. The recruiter may dismiss it due to the font you use, the University you went to or the taste of the coffee that morning. On the other hand, not following these tips are quite likely to cause a rejection. Good luck!

Comments

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

标 题: 关于Daniel Guo 律师

发信人: q123452017 (水天一色), 信区: I140 标  题: 关于Daniel Guo 律师 关键字: Daniel Guo 发信站: BBS 未名空间站 (Thu Apr 26 02:11:35 2018, 美东) 这些是lz根据亲身经历在 Immigration版上发的帖以及一些关于Daniel Guo 律师的回 帖,希望大家不要被一些马甲帖广告帖所骗,慎重考虑选择律师。 WG 和Guo两家律师对比 1. fully refund的合约上的区别 wegreened家是case不过只要第二次没有file就可以fully refund。郭家是要两次case 没过才给refund,而且只要第二次pl draft好律师就可以不退任何律师费。 2. 回信速度 wegreened家一般24小时内回信。郭律师是在可以快速回复的时候才回复很快,对于需 要时间回复或者是不愿意给出确切答复的时候就回复的比较慢。 比如:lz问过郭律师他们律所在nsc区域最近eb1a的通过率,大家也知道nsc现在杀手如 云,但是郭律师过了两天只回复说让秘书update最近的case然后去网页上查,但是上面 并没有写明tsc还是nsc。 lz还问过郭律师关于准备ps (他要求的文件)的一些问题,模版上有的东西不是很清 楚,但是他一般就是把模版上的东西再copy一遍发过来。 3. 材料区别 (推荐信) 因为我只收到郭律师写的推荐信,所以可以比下两家推荐信 wegreened家推荐信写的比较长,而且每封推荐信会用不同的语气和风格,会包含lz写 的research summary里面的某个方面 郭家四封推荐信都是一个格式,一种语气,连地址,信的称呼都是一样的,怎么看四封 推荐信都是同一个人写出来的。套路基本都是第一段目的,第二段介绍推荐人,第三段 某篇或几篇文章的abstract,最后结论 4. 前期材料准备 wegreened家要按照他们的模版准备一个十几页的research summary。 郭律师在签约之前说的是只需要准备五页左右的summary,但是在lz签完约收到推荐信 ,郭律师又发来一个很长的ps要lz自己填,而且和pl的格式基本差不多。 总结下来,申请自己上心最重要。但是如果选律师,lz更倾向于wegreened,