Writing Brain Teasers for NASA's Next Mars Rover

I'm working on software for the Mars 2020 rover – so the code and tools that allow the rover to function on Mars. My team is rover simulation and planning. The rover planners are the people who take in all the information from the scientists and the rover and write commands to send to the rover through the Deep Space Network, which is basically the internet for space. As the simulation team, we make sure that the commands that we're going to send are going to be effective and that they're going to be safe so that this rover we send to Mars after all this painstaking work isn't going to get stuck in a hole or break because of a wrong command.

I work on creating tests that humans couldn't come up with. The average testing for software is you write tests to make sure that the code isn't going to fail when you add in certain instructions. But humans – specifically the humans who write the tests – tend to be the same people who write the code. They're not going to be able to come up with as good of a test, because if they knew what was going to break, they wouldn't have written the bug in the first place.

What I do is use a couple of testing frameworks that use generational input adjustments. They develop in an evolutionary way, starting from a simple input that I put in. So, say we're working on commands for the rover. We can start with, "Go forward," and then the system will modify the instructions based on a dictionary of information I provide. So I say, "These are words that might make sense to the rover. Try coming up with combinations of these that might result in behavior that we haven't seen before." If that behavior is defined, then everything's fine, but if it's going to cause a problem, then it's important that we know that so we can update the code.

I study computer science at Harvard. I hadn't done any programming before coming to college. I thought I wanted to do something in the area of technology and possibly business, but I didn't really know. So I took the intro to computer science class, and I really loved it. I loved the challenge of feeling like my homework was a puzzle and not a chore. That drew me to it, and I started taking all the classes that I could in that realm.

I don't think anyone should have an ultimate career goal. I think careers should be a fluid thing and that people should build up skills that allow them to do the things that are most interesting to them. Right now, my goal is making sure that the Mars 2020 rover lands on Mars and everything goes swimmingly when it gets there. But, ultimately, I want to work on cool things with interesting people.

When I came here, my main goal was having a tangible impact on the project. I wanted something where every minute I spent working would be important to meeting the goal of the project. I find bugs every day, and I fix them, and that's great. Hopefully, before the summer's over, I will have a patch that I can write for the software that will end up on the rover.

I had a friend who interned here two years ago, and he recommended it really highly, saying he had a terrific time and his team members were great. I applied online, but when you apply, it's a general application and you could be picked for any project based on your set of skills.

I knew that I wanted to work on Mars 2020, so I went on the JPL website, and I researched teams and people working on robotic software for the mission. I emailed Jeng Yen, my group supervisor. I said, "Here's my resume. This is what I'm interested in. Are there any projects that I could work on?" He said, "One of my team members, Steven Myint, is working on something that fits your profile pretty well. You should talk to him." So I talked to him, and the rest is history.

Oh, easy. One of my team members, Trevor Reed, is a rover planner for Curiosity. Every morning the team has a tactical meeting in which they go over the schedule for the day for the rover, and they give instructions to the rover planners who will write the commands that tell the rover what to do. When I found out that one of my teammates drives the Curiosity rover, I was like, "Can I please, please shadow you for that process?"

So I showed up at 8 o'clock in the morning in the Curiosity rover tactical office, or conference room, and there's the head scientist, Ashwin Vasavada, who I'd read about in articles. I watched them send the actual commands to the rover. I learned all about the planning and tolerances that are involved in the simulations that we do. I got to see the software that I'm working on in action, because it's also used for Curiosity. It was a pretty amazing experience to sit there for a couple of hours and watch them go through the entire process of a day on Mars.

Every kid wants to be an astronaut, right? I mean, if you're offering … As much as I would love to be an astronaut, my interests in the short term are contributing to and building projects that I think are important. So for those future missions, I think I would want to have more input on the design, the structure and the planning, overall. So maybe I would want to be a systems engineer or even work on the design.

This Q&A is part of an ongoing series telling the story of what it takes to design, build, land, and operate a rover on Mars, told from the perspective of students interning with NASA's Perseverance Mars rover mission. › Read more from the series

• JPL Internships and Fellowships
• JPL Jobs

The laboratory’s STEM internship and fellowship programs are managed by the JPL Education Office. Extending the NASA Office of STEM Engagement’s reach, JPL Education seeks to create the next generation of scientists, engineers, technologists and space explorers by supporting educators and bringing the excitement of NASA missions and science to learners of all ages.

Career opportunities in STEM and beyond can be found online at jpl.jobs. Learn more about careers and life at JPL on LinkedIn and by following @nasajplcareers on Instagram.