In this installment of our "Meet the Splunktern" series, we're featuring Jeannine Elmasri, a Technical Writing Intern currently in her third year at Stockton University. Continue reading to learn more about her journey to Splunk and her internship experience!
Initially, I saw the Technical Writing internship posting while browsing through job sites, and decided to apply after reading the description and further conducting research on Splunk.
I’m interested in working as a Technical Writer in the future because it combines both my passions for technology and writing. So, I felt this role would be the perfect fit. While doing research on the company, I was inspired by the wide range of people and businesses that use Splunk for their data management. I was shocked by the various ways Splunk products could be applied in different use cases and companies, and just how much I interacted with those companies, and in turn Splunk.
After doing research on Splunk, I thought there was no way I would get the internship for such an impactful company. However, despite my self-doubt, I pushed it aside repeating to myself, “The worst they can say is no.” Thankfully, we both said yes once I received the call offering me the internship!
It’s been super interesting so far! The team I am working with has been extremelyfun to chat and work with. Everyone is friendly and encourages you to explore a lot during your internship. I’ve been working on some very fascinating projects. I’m collaborating with the Product Experience documentation team to write features for new Splunk products. Additionally, I am responsible for writing scripts for Splunk videos, working on UI text reviews, and developing user guides with the editing team for a content authoring system. It never feels like I’m doing any busy work, and I truly feel like I’m part of the team.
I had the option to select what types of projects I want to work on and determine how to complete them. As long as my project meets the criteria of what I have to write, I am good to go! I usually reference the Splunk Style Guide when writing scripts or guides to make sure they adhere to Splunk’s writing standards. Since this is a remote internship, I like to visit my local coffee shop or library in the mornings before I have any meetings, to work distraction free.
This is my first internship working in technical writing, and I have gained insight into how writers work with engineers to write documentation. I have also learned how to effectively communicate and ask relevant questions. Additionally, I’ve gained a deeper understanding of Splunk products and the different tools technical writers use in their day to day life.
This internship is providing me with valuable experience in technical writing, and the opportunity to explore and try out different avenues in the field.
My day to day leader and manager, Andrew Yu, set up a meeting to introduce me to the technical writing team, and everyone was very warm and welcoming! They have all been super helpful, and are always willing to answer any questions. Everyone makes you feel welcome to ask questions, and encourages you to reach out. Some of the people on my team were past interns who had experienced the Splunktern program, and they were all excited for me to start working. They provided me valuable advice on how to make the most of my internship experience.
Along with that, I’m enjoying working with two technical writers, Candy Santos and Helena Sherman, on writing documentation for upcoming product features. During our weekly meetings, they are always willing to help me with any questions I have, and direct me to the appropriate resources and team members for further assistance.
There are two events that stuck out. The first was the Communications Professional Development Workshop with Lan Ly, which encouraged me to step outside of my comfort zone. During meetings, I usually keep my microphone muted. However, Lan encouraged us to speak up about our experiences with discussing difficult topics. She gave us some helpful tips and advice for effectively communicating with our managers and team members.
The other event I found helpful was the Executive Talk with Sonal Bablani. She shared meaningful advice on her personal experience as a Director of Software Engineering, and how she started her career. She encouraged us to make our voices heard, whether it is through asking to join meetings or asking questions. She emphasized everyone has been new to a subject at one point in their life, and it's the determination to understand that pushes people through and helps them stand out.
The Splunktern events have definitely motivated me to be unafraid of everything I don’t know yet.
Do not be afraid to ask questions and reach out for any help! You are here to learn as much as possible and contribute your unique skills to Splunk. It can definitely be a little nerve wracking to admit you don’t know something, but it is better to ask as soon as you’re confused than wait until the last minute. Nobody will make you feel bad for not understanding something immediately. Rather, it feels like every question I ask is valued and answered with a lot of care.
Want to join interns like Jeannine in growing your career? Visiting our career site to learn more and explore open opportunities.
The world’s leading organizations rely on Splunk, a Cisco company, to continuously strengthen digital resilience with our unified security and observability platform, powered by industry-leading AI.
Our customers trust Splunk’s award-winning security and observability solutions to secure and improve the reliability of their complex digital environments, at any scale.