Hello! I am a senior technical writer who documents software and hardware. As a creative asset to teams, I intuitively understand the social currents that keep a team thriving. I am currently employed as a senior technical writer for an AI software company.
A meticulous, detailed master of shifting deadlines and multiple projects, I’m a highly professional team player who gets on well with all personalities while still working independently to produce high-quality material. I’m a positive, well organized storyteller with keen technical curiosity, and a champion of the brands I write about.
My significant experience with highly technical material, marketing, and design means I’m well rounded and agile. I’m an expert in creating content that both advances project goals and centers on the customer, with a deep understanding of brand. I excel at project management and as a core member of functional teams, I’ll ask questions and come up with creative solutions.
I am also a published author with a traditional publisher. I know how to work on deadline and contribute positively to a remote team environment.
Skills:
- API documentation
- Markdown, VSCode, GitHub
- Agile development environment including Confluence
- Work in a modern documentation toolchain
- Editor and peer reviews
- Adobe Creative Suite
- Expert at UX effect on writing
- Team player
- Dynamite organization skills
- Efficient and fast
I was given a case study to write with very little starting information. I only had a PPT with test results and some acronym-heavy charts.
My first step was to understand the audience. Who was the target reader? My second step was to create an outline. The third was to determine what information I was lacking that fit into that outline. Then I contacted the product manager to fill those gaps. In this way, a good case study could be written with all the information a similar customer might want to know–and which would influence their decision to purchase.
I wrote a whitepaper and sent it to a colleague to review. The colleague wasn’t able to give me specific feedback, but suggested something was “not right” with the paper. Rather than get upset, I recognized that the manager was trying to communicate something but wasn’t sure how. I suggested as a solution that we hold a meeting, talk about what worked and what didn’t in the paper, and then zero in on the parts that didn’t work. The parts that didn’t work would tell me what it was that didn’t match the manager’s expectation. It turned out that the paper was fine, but the manager wanted to communicate a specific message. The triage meeting helped the manager communication that.
This is such an important question as more organizations realize the benefits of a distributed workforce. The upshot of a remote culture is a better work-life balance and increased productivity for those workers (like me!) who excel in comfortable environments and who do not need the extras of an office to thrive – like water coolers, gossip, and late-night foosball tournaments. Team building is incredibly important, but remote work culture has reinvented what a team is, in many positive ways, and edited out the harmless, inefficient elements.
That said, nothing replaces a face to face experience – we get deep understanding of our colleagues by looking at their faces. So we find other ways, like an increase in thoughtful replies, a commitment to regular chats, an understanding that not every video call needs to be about work, and a respect for the way others communicate.
Remote culture is not for everyone, but I am sensitive enough to understand the challenges and come up with ways to overcome those, with the results of efficient, great work.