An Interview With A Systems Engineer

March 28, 2025

Jessica A. Dennehy

11th Grade

Williamsville East High School


This is an interview with Guoqing Dennehy, a current systems engineer specializing in the aerospace industry. She controls the system requirement management to ensure products satisfy customers’ needs. In her spare time, she enjoys reading autobiographies, adventuring outdoors, and challenging herself—mentally, physically, or intellectually.

Tell us about the trajectory of your career in engineering.

I started my engineering career at John Deere. I was a mechanical engineer responsible for designing, testing, and verifying heavy construction and mining equipment. I then transitioned into a systems engineering role in the aerospace engineering field. Many people would think there's a big difference between the two industries, but I think there are so many skills—for me, it was physics and math-intensive analysis—that easily transferred from my prior line of work to my current one.

What sparked your interest in engineering?

It really started when I worked as a manager’s assistant. At the time, I was responsible for all engineering-related tasks on the production floor. I'd witnessed the complexities and challenges within the various projects and how everyone had limited time and resources to provide optimum solutions. But the engineers... the engineers were able to combat these challenges; they were able to provide alternative solutions and make sound decisions. That control—that was what sparked my interest in engineering.

Did you always know this was the path for you?

No. I didn't even know what engineering was when I was a kid. Growing up, I didn’t have a strong grasp on what I wanted to do for a living. But once I was exposed to the engineering field, it became easy for me to know what I needed to do. I had a goal. I just had to get there.

Where did you study, and what degree(s) did you earn?

I received my bachelor’s in mechanical engineering at Alfred University, with a minor in mathematics. Then I got my first master's in mechanical engineering at the University of Wisconsin–Madison. I recently graduated with my second master's in systems engineering at Georgia Tech.

Were there any particular subjects that had a big impact on you as an engineer?

It depends on what specialty of engineering. Every field requires different backgrounds and different skills. For me, in both mechanical and systems engineering, a mastery of basic, foundational math and physics is essential. I always liked math. I tutored mathematics when I was in college, and I enjoy teaching others how to solve math problems to this day—save for my daughters. They don't ask for my help, so now I'm a bit rusty.

Do you think a master’s or PhD is necessary to advance in this field, or is a bachelor’s degree enough?

Advanced degrees are always helpful; I believe that is a known fact. But in engineering, if people have a desire to continue learning, they should definitely continue to pursue further education. People need to understand that an additional advanced degree should be for their own self-improvement, not just for employment purposes. 

Do you have any recommendations for someone planning to pursue aerospace engineering?

For prospective engineers, having an understanding of what field you are going to focus on and identifying your own interests is important. I think if students are showing interest in aerospace or any other engineering fields, they should try to participate in activities relating to those fields. Being involved can open your eyes to the near-endless possibilities and potential career paths you can pursue. Every space shuttle and aircraft is supported by thousands of individuals. You can be one of them.

Do you feel your education prepared you well for the real-world challenges of your job?

Of course. Education is a tool—one that helps me to understand the complexities of various projects. My education also allows me to process problems and learn how to solve them. I think of education as a door, a pathway to further opportunities. 

What do you do as a systems engineer?

Systems engineering, at least in aerospace, primarily focuses on system integration. From hardware to electronics, software to testing equipment, we have to ensure that our system satisfies the requirements needed from the customer. When it comes to testing systems, we have to ask two questions: did we design the system correctly, [and] did we design the correct system? Those aren’t the same things.

What types of projects do you usually work on?

I have spent the last nine years of my career as an engineer, and I have never had a “usual” project. Each and every one has its own nuance and life cycle. Some projects are existing technologies with some minor updates; others have to be started from scratch. I've worked on fighter jets. I’ve worked on satellites. I've even worked on eVTOLs…[which are] electric vertical take-off and landing aircraft. It’s this new emerging technology—think something like an air taxi. It can hover, take off, and land vertically, all through electric power. I’m currently working on a project relating to helicopters, though. My team is at the beginning of the architectural design phases for this one.

What software, tools, or technology do you use regularly in your work?

Matlab, Simlink, Simscape. Those are the main tools I use for controls and systems analysis. For the processing of data and data visualization? Probably Python. Also Cameo, if you’ve heard of it. I usually use it for system architecture software. I find that it helps with requirement management and system architectural design and documentation.

Do you enjoy what you do?

I enjoy it. I really do. I found that, in both industries, I could bring a unique perspective and manner of thinking to the table, especially in a work environment so dominated by men. I’ve found that female engineers have a tendency to be more detail-oriented than their male counterparts. Having more women in the field of engineering would contribute to greater efficiency in the overall engineering workforce.

How do you typically start your workday?

Every role has slight variations in their day-to-day, and every program has different stages in their life cycle. So it depends. For me, right now, I will start by checking my emails and answering questions or documenting potential concerns from both customers and internal teammates. I will provide answers correspondingly, which is a process of gathering data, processing data, and presenting data. This process may involve others; I will reach out and collaborate with the corresponding person to solve problems together.

And as the day progresses?

I would work with my team and test systems. If something happens in the testing lab, I spend my time running and troubleshooting tests before reporting problems to customers and the management team.

What do you enjoy the most about your job?

What I enjoy the most is testing integration. This is the critical phase for my team to verify our system capabilities since this is when we connect hardware and software for the very first time. While we do this, we also want to make sure no unexpected behavior occurred and that all failure modes are captured under the design review. The fun part for us is troubleshooting what goes wrong—because something always goes wrong.

What’s the most challenging aspect of your job? 

Dealing with ambiguity. If I don't even know what the problem is, I’ll lose sight of potential risks. So as a system lead, I need to find the best way to quantify those unknown risks and identify their corresponding mitigation strategies. This process is a team effort; it's challenging but also fulfilling.

What’s the most valuable lesson you’ve learned in your career so far?

Don't give up and never take no for an answer.

What’s one piece of advice for those interested in pursuing a career in engineering? 

Be open-minded and be eager to learn. Treat others how you want to be treated.