Kevin O'brien
About Kevin O'brien
Kevin O'Brien is a Technical Writer with extensive experience in web development and technical documentation. He has worked for various companies, including Backbase, where he has implemented new documentation processes and collaborates with development teams in Cardiff, United Kingdom.
Work at Backbase
Kevin O'Brien has been employed at Backbase as a Technical Writer since 2019. In his role, he collaborates closely with Product Owners, developers, and architects to create procedures and supporting documentation for the Backbase platform. He has faced the challenge of working remotely with colleagues in Amsterdam, focusing on refining documentation processes for the Backbase Digital Sales product. O'Brien has implemented a new documentation way-of-working across four development teams, which has led to a significant reduction in friction and improved efficiency.
Previous Experience in Technical Writing
Before joining Backbase, Kevin O'Brien held various positions in technical writing and web development. He worked at Nokia as a Technical Author from 2011 to 2017, where he gained six years of experience. He also served as a Technical Bid Writer at Civica Digital for one year in 2010, and as a Technical Writer/Web Developer at Claritum for four months in 2018. Additionally, he worked at Visa as a Technical Author from 2007 to 2010, accumulating three years of relevant experience.
Web Development Background
Kevin O'Brien has a background in web development, having worked as a Trainee Web Developer at Mayden for four months in 2018. He also served as a Web Developer at Lovehoney for eight months from 2018 to 2019. His experience in web development complements his technical writing skills, allowing him to create more effective documentation for technical products.
Education and Expertise
Kevin O'Brien studied at the University of Southampton, where he earned a Bachelor's degree in Philosophy from 1996 to 1999. His educational background provides him with critical thinking skills that enhance his technical writing and documentation processes. He utilizes the 'docs-as-code' methodology, creating documentation using asciidoc in an IDE, and employs Git and Bitbucket for review and documentation control.