Getting Up to Speed as a "Qworkineer"

As a recent graduate at San Jose State University, I was ecstatic realizing that I have an opportunity to be a part of something potentially large and diverse.

Speaking with Jon over the holidays between Thanksgiving and Christmas about the Qworky brand and what its plans are as a startup company really intrigued me. Those conversations alone enticed me to become a part of its diverse and energetic team and assist Qworky to achieve its company goals and aspirations.

At our first official Qworky meeting between Jon, Brandie and I, Jon demonstrated a quick but thorough rundown of the ongoings with Qworky and the engineering side of things. Wow, there was quite a bit of information to soak up! However, I was determined to tackle the abundance of information and I took it in stride. Once Jon recognized my determination and go-getter attitude, he gladly welcome me to the team and it was then and there that I knew it was my duty to get up to speed with the rest of the team, especially engineering, and document my every step of the way.

I’m the first Qworkineer (Qworky Engineer) to join this wonderful company “in stride.” Getting up to speed with the rest of the engineering team was a new experience for myself and Qworky. As a Qworkineer in my position, it was my responsibility from the get go to get up to speed to help with open source development and document my experience in order to make it a very fluid process for onboarding future Qworkineers.

If you think about it, the task that was on my plate could have been considered very overwhelming. However, I took it a step at a time (thank you Google!) and enlisted the assistance of Alem and Jon if there were technical problems I just couldn’t troubleshoot successfully after spending hours trying to figure it out on my own. One of the toughest examples was when it came to creating the feature that displays the time remaining until a meeting starts. Initially the mathematical logic took some time to implement but after some research and trial-and-error, I was able to create the feature successfully with some help from Brandie and Jon during our problem-solving/brainstorm session. Although the entire process was very time consuming and frustrating at times, I was able to successfully push through and accomplish my goals with my persistence and gung ho attitude.

With new team members like Andrea getting involved in the open source project, and Josh joining the team as QX developer, the documentation I produced is already proving useful. Of course there are still plenty of questions, and the documentation will improve over time. Our goal is to have a very fluid onboarding process with minimal hiccups while sparing people from the technical hardships I encountered along my journey.