Mario Rosales, software engineer III for Beck Technology, is part of the Research & Development team and works on new features and functionality of the DESTINI suite products. See how software engineer duties vary greatly in A Day in the Life of a Software Engineer III at Beck Technology.
Software Engineer Duties
It’s Tuesday here at Beck Technology, and my week is off to a good start. As a software engineer for Beck Technology, Software Engineer III to be exact, I’m involved in all aspects of software development – everything from design to testing to maintenance.
The first thing on my to-do list most mornings is to check in with Yvonne, a very bright intern at Beck Technology, to see how her morning is going and if she has any problems she needs help with. After this, I move on to my own work.
Today’s Priority: New user stories
One of the most fulfilling aspects of my job at Beck Technology is always feeling like I’m a step ahead in the industry. DESTINI Estimator 2017 2.0 hasn’t been released yet and I’m already working on the next update. Today, I’m going over the details for the new user stories assigned to me for the DESTINI Estimator 2017 3.0 release. A new user story is a high-level breakdown of a new feature that will be developed, including an explanation of how the feature will integrate into the existing product.
After familiarizing myself with my new user stories, I sat down with Eric, our systems architect, to give him feedback on his current implementation details for a new user story that will allow users to associate cost with rows in the Takeoff Summary in Estimator. Eric’s job is to figure out how a new feature will fit into the product and make it happen, without hindering previous or future functionality.
After meeting with Eric and before checking in with Yvonne again, I head to the YMCA for a smoothie for lunch. When I get back to the office, I scroll through my SoundCloud and make a playlist to listen to for the rest of the day. I’m a music person, so it’s easier to work on projects and troubleshoot problems when I’ve got something playing.
Troubleshooting: If at first you don’t succeed…
Speaking of troubleshooting, in my morning meeting with Yvonne, she brought to my attention a problem she was having with a client’s custom cost report in Estimator. I had her send me a copy of the report and the estimate file she was using for testing so we could explore different avenues for finding a solution, but to no avail.
One of the neat, and important, parts of my job is the need to view problems from various angles. After coming up short on a solution using our current strategy, we decided to review the report as it prints out the details to see if we could learn more about the issue. We discovered the problem was with how the report thinks it’s printing out the data. I suggested she send a ticket about the issue to the creator of the third-party tool kit we use to create the custom banded reports.
Towards the end of the day, I begin to come full circle with my tasks, returning to the new user stories assigned to me for DESTINI Estimator 2017 3.0. I go over the implementation details that Eric has written for the user stories assigned to me and work on tasking out, which means giving time estimates for each task.
Each day, my time is filled with making our products better and pushing them forward. Sometimes this means developing new user stories and sometimes this means troubleshooting functionality issues, but it always means working with a team of people who are equally as enthusiastic about their work as I am. And that’s what makes working at Beck Technology so great.