From Dream to Launch Console: Your Blueprint to Becoming a NASA Ground Systems Problem Solver

Introduction

Imagine standing in a firing room, watching a rocket roar to life as it carries humanity back to the Moon. For Anton Kiriwas, that vision began with a simple poster at a college job fair—a photo of the Moon and Mars that seemed impossibly distant. Today, he’s the senior technical integration manager for NASA’s Exploration Ground Systems Program, solving the very problems that make Artemis missions possible. This guide breaks down the steps he took and the path you can follow to transform your own fascination into a career as a ground systems problem solver. Whether you’re a student or a professional pivoting into aerospace, here’s your roadmap.

What You Need

• Education: A bachelor’s degree in engineering (electrical, systems, or aerospace preferred). Advanced degrees (master’s or PhD) can help but aren’t mandatory.
• Experience: At least 5–10 years in systems integration, project management, or launch operations. Internships with NASA or aerospace contractors count.
• Skills: Strong problem-solving, cross-disciplinary communication, and ability to work under pressure. Familiarity with ground systems (e.g., electrical, mechanical, software) is a must.
• Mentality: Curiosity, resilience, and a willingness to learn from failures. Anton’s words: “I solve problems for the ground systems.”
• Network: Connections within the aerospace industry—attend conferences, join professional organizations (AIAA, SWE).

Step‑by‑Step Guide

Step 1: Cultivate Your Curiosity About Space

Just as Anton was captivated by that Moon‑and‑Mars booth, you need a genuine spark. Start by following NASA missions (like Artemis), reading engineering blogs, and watching launch webcasts. This passion will fuel your long journey. Pro tip: visit a Kennedy Space Center launch viewing or a job fair with NASA representatives to solidify your dream.

Step 2: Earn a Relevant Engineering Degree

Anton’s background began with electrical engineering. Enroll in a program at a university with strong ties to NASA (e.g., University of Central Florida, Texas A&M, Caltech). Focus on courses in power systems, controls, data analysis, and project management. Get involved with student rocket teams or CubeSat projects—they simulate real ground systems work. Keep your GPA competitive to qualify for NASA co‑ops and internships.

Step 3: Land an Aerospace Internship or Entry‑Level Role

Before joining NASA as a civil servant, Anton worked for United Launch Alliance—the same company that ran that college booth. Target internships at NASA centers (especially Kennedy Space Center), primes like Lockheed Martin, Boeing, or SpaceX, and contractor firms like United Launch Alliance. These roles let you experience ground systems firsthand. For interns, apply through NASA’s STEM Gateway; for roles, check USAJobs.gov for NASA civil servant positions or company career pages.

Step 4: Build Your Problem‑Solving Portfolio

In his own words, Anton’s official title is “way too long” but his job is simple: solve problems for ground systems. Start documenting issues you’ve resolved—design bugs, process improvements, or cross‑team coordination triumphs. Use concrete examples: reduced test time by 20%, resolved a safety interlock problem, or integrated multiple systems before launch. This portfolio is your key to advancing into integration management.

Step 5: Transition Into Systems Integration

Anton moved from designing electrical systems to overseeing integration across all engineering disciplines. Look for roles like “systems integration engineer” or “project engineer” within NASA or its partners. At this stage, learn to speak the language of both hardware and software teams. Become the bridge that connects test management to the firing room—like Anton at his console in Firing Room 1. Offer to lead cross‑functional reviews; that visibility gets you noticed by launch directors.

Step 6: Master the Launch Console Role

Anton serves as a launch project engineer, sitting at the integration console in the Launch Control Center. To get there, volunteer for countdown simulations (like NASA’s Artemis II simulations in October 2025) and learn every system’s telemetry. You must be comfortable making split‑second recommendations to the launch director. Practice by participating in simulated launch scrubs or real-time decision‑making drills.

Step 7: Become the Go‑To Problem Solver

The core of this job is being the final technical recommendation on launch‑day issues. That means earning trust by solving problems quickly and safely. Follow Anton’s example: work across all engineering disciplines, communicate clearly under pressure, and always prioritize crew and spacecraft safety. Once you’ve proven yourself, you’ll be tapped for senior integration manager roles.

Step 8: Network With Artemis‑Related Teams

Anton’s journey came full circle when he joined the same program he saw as a poster. Attend industry events (Space Symposium, AIAA forums), connect with Exploration Ground Systems team members on LinkedIn, and ask to visit Kennedy Space Center’s Launch Control Center. Your network will open doors to roles like his—senior technical integration manager where you “live” in the firing room.

Tips for Success

• Embrace simulations. They’re dry runs for real pressure; each one sharpens your instincts.
• Stay flexible. Ground systems evolve constantly—be ready to pivot from electrical to software to mechanical challenges.
• Document everything. Your decisions during countdown become post‑launch lessons; keep a log.
• Listen more than you talk. Anton’s role requires him to be a hub; absorbing input from all teams is key.
• Keep the big picture. Every problem you solve enables Artemis to return humans to the Moon—remember that on stressful days.

Anton Kiriwas once thought the Moon was a distant dream. By following a methodical path of education, experience, and relentless problem‑solving, he now sits at the heart of NASA’s Artemis launches. Your journey can mirror his—start with curiosity, build your skills, and never stop solving. The launch console is waiting.