Writing me a recommendation? Thank you.
The hardest part is starting. Pick any two or three of the prompts below. They're shortcuts, not a checklist. The button further down opens an email draft to me with your answers pre-filled. With your permission I'll post it on my site or on LinkedIn.
Want a sense of what other people have written? See all my LinkedIn recommendations , or read the Derrick Parkhurst example further down.
Nothing is sent or stored until you click send.
Write a recommendation
Every field is optional. As you fill things in, the preview at the bottom assembles into a recommendation you can email me or paste into LinkedIn. Your draft is saved in your browser so you can come back to it.
An example: Derrick Parkhurst
Derrick and I worked together at Condé Nast on paywalls and shared UI for The New Yorker, Vanity Fair, and Wired. He wrote this in December 2018.
I have worked closely with Oli for the last year and a half at Conde Nast developing software for a variety of very high-traffic websites including wired.com, newyorker.com, and vanityfair.com. The codebases for these sites are written in JavaScript (ES6/7 and Node) and leverage libraries such as React, Redux, Lodash, Hapi, Webpack, Babel, Eslint, Mocha, Jest, and Puppeteer. Working together on these various projects, I have seen Oli become proficient at writing production quality code in state-of-the-art JavaScript stacks. Not only has Oli become a valuable member of our agile team, he has become very skilled at communicating and collaborating with other teams, working in their codebases and within their processes when required.
I have had the opportunity to work on few green field projects with Oli. I was very happy to see that he showed a sense of ownership in these projects. It was not uncommon for him to suggest improvements and make personal contributions towards those ends on his own initiative. It can tell from his work that he values both quality and maintainable code. I have also appreciated that he is willing and able to take on the sometimes tedious, but very necessary work assigned to our team. This work included updating legacy code, application maintenance, manual testing, on-call support, and documentation.
No matter the type of work, Oli maintains a level of commitment, dependability and accountability that exceeds many of his, more senior, colleagues. He is also humble where his own contributions are concerned and is always on the lookout for opportunities to learn from other engineers with the goal of improving his own work.
Of particular note, Oli has the very valuable ability to communicate clearly and precisely both in his speaking and writing. His technical communication skills are very strong. This facility in discussing technical topics makes him a joy to work with in daily meetings and especially when pair programming. This skill also afford him clarity in his code, tests, documentation and the pull requests. Speaking of pull requests, I am always glad when Oli reviews my pull requests. It has been my experience that even at my level of skill, his attention to detail, and thoroughness of review has often helped me uncover issues that I missed, and provided valuable suggestions to improve my code.
It is hard to overstate the value that Oli brings to the table as an Engineer. I enjoy working with him and hope to have the opportunity to work with him on projects in the future.
Preview
Fill in some fields above to see the recommendation assemble here.
Your draft is long enough that the email button might fail on some mail clients. Use Copy recommendation instead and paste into a fresh email.
Send it
Two ways to get your draft to me. The mail button
opens a draft to oliver.treadwell@gmail.com
with everything pre-filled. The copy button puts the
recommendation on your clipboard so you can paste it
straight into LinkedIn's recommendation flow.