Hey, it’s me!
Why writing?
Technical writing has always been a part of my work, before I even knew what it was:
Out of grad school, as an epidemiologist I wrote reports for the state
sldkj
lsdkjsdl
This thread
I have been working in technology since 2012 in various roles and setting. These experiences include: machine learning program management at universities, product data analysis at a start-up, and UX research in industry, among others.
All along, however, writing has been a part of my work. But I recently opted to professionalize in the discipline. For me, this has meant taking courses at Carnegie Mellon to better apply principles of Style, API and Technical writing, and Information Design.
The technical writing I did the past as an add-on to my regular duties, I now know how to accomplish at a different level. I find writing to be a fulfilling role because it ties together so much of my past experiences. I apply UX research methods to understand my end users and test documents. I use an analytic mindset to teach myself new programming languages. And program managing comes in handy with understanding the big picture of product development.
I also find it fulfilling because I am able to develop a product at the end of the day. Just in the way that coding filled this need for me, something real-feel provides satisfaction.
Ways of working
I aim to align and understand so execution comes with a bit more ease. I value context, curiosity, and the inclusion of all voices.Connect with me on LinkedIn here.
Me
I’m first-gen Ecuadorian/Hungarian. Dog-mom and mountain biker. When not doing research, writing, or reading, I’m enjoying the outdoors with my partner and pup. Connect with me on LinkedIn here.