My common advice for people looking for comp bio jobs.
Recently, I have been talking with some job seekers and interviewing for a couple of positions on my team. I was reminded how difficult it is for job seekers to get noticed and, on the flip side, for hiring managers to identify relevant candidates from a pile of candidates. I wanted to write down a few ideas in case they could be helpful.
Liberally. Interviews are good practice. You should not waste people’s time if you have no intention of accepting a new role, but if you are seeking a job, don’t count yourself out by not even applying.
Introductions and talking to people you know at a company is absolutely a good idea. I have heard the cynical view that no one gets hired that was not referred. That has not been my experience. At least at established companies, most people hired are not friends or connections. However, the current climate (March 2024) is tough for applicants. Companies are getting way more candidates than they could review. Any help you can get to get your resume even seen seems worth the effort.
There is already more advice than you could use on the internet about writing a good resume. Here is my approach.
While employers often have flexibility, it is best to be in active interviews when you can start the role within six weeks. A hiring manager would like the new hire to begin as soon as possible. A complete interview process, from reading your CV to extending an offer, could be as short as two weeks or as long as six weeks.
This advice is most salient to people completing full-time degrees. I see many applications from people who will not graduate for several months. I completely understand the need to look for a job while completing your degree, but the timeline has to make sense.
The timeline gets fuzzier if you are more established in your career. You should network and strategize to find your next role, which can take a long time (people say one to two years) to build connections and learn about possible future opportunities.
Be prepared! I cannot emphasize enough that the interview process is often less about how you answer our questions and more about how you ask us questions. I frequently hear that hiring managers are looking for curiosity, passion, and potential. Having good questions about the company and the role can set you apart. Here is my advice: Ask people you have worked with, or you know who hire people about the best questions they have been asked by candidates. Ask your favorite chat LLM for inspiration, too.
The other recommendation I have for candidates is about responsiveness. If at all possible, do not delay replying to emails about scheduling. I will read this as a passive “no thanks.” It’s fine, but I prefer a polite decline rather than no response. If you will be traveling or unresponsive, send a note to that effect. It is extremely obvious how interested a candidate is based on how quickly they reply to schedule interviews or answer questions.
On a related note, fewer and fewer people send thank-you notes after interviews, so I do not consider that when forming an opinion on a candidate. I don’t really even notice anymore. If I were interviewing, I would send a thank you. I don’t see any downside, so why not?
A caveat: My work has been entirely in the life sciences, biotech, and pharma space, and I don’t know how generalizable this perspective is.
In the past decade, I have participated in many interviews at large and small companies (easily in the hundreds). Feel free to reach out if you are applying for roles in biotech and pharma and are interested in talking about it. I have set aside some time to talk about these sorts of issues. I would be happy to provide resume advice or answer your questions about interviewing.
pander::pander(sessionInfo())
R version 4.3.0 (2023-04-21)
Platform: aarch64-apple-darwin20 (64-bit)
locale: en_US.UTF-8||en_US.UTF-8||en_US.UTF-8||C||en_US.UTF-8||en_US.UTF-8
attached base packages: stats, graphics, grDevices, utils, datasets, methods and base
loaded via a namespace (and not attached): digest(v.0.6.31), R6(v.2.5.1), fastmap(v.1.1.1), xfun(v.0.39), cachem(v.1.0.7), knitr(v.1.42), distill(v.1.6), memoise(v.2.0.1), htmltools(v.0.5.5), rmarkdown(v.2.21), cli(v.3.6.1), pander(v.0.6.5), downlit(v.0.4.2), sass(v.0.4.5), jquerylib(v.0.1.4), withr(v.2.5.0), compiler(v.4.3.0), rstudioapi(v.0.15.0), tools(v.4.3.0), bslib(v.0.4.2), evaluate(v.0.20), Rcpp(v.1.0.10), yaml(v.2.3.7), jsonlite(v.1.8.4) and rlang(v.1.1.1)
If you see mistakes or want to suggest changes, please create an issue on the source repository.
For attribution, please cite this work as
Walsh (2024, March 26). Alice Walsh: Improving Your Job Search. Retrieved from https://awalsh17.github.io/posts/2024-03-26-improving-your-job-search/
BibTeX citation
@misc{walsh2024improving, author = {Walsh, Alice}, title = {Alice Walsh: Improving Your Job Search}, url = {https://awalsh17.github.io/posts/2024-03-26-improving-your-job-search/}, year = {2024} }