cameronwp

Onsite at NASA JSC through Jacobs Technology | Senior Full-Stack Engineer | Houston, TX + Remote | Full-time

https://jacobs.taleo.net/careersection/ex/jobdetail.ftl?job=...

Have you ever imagined your code being used in space? Do you daydream about astronauts walking on the Moon? Here's your chance to be a part of the team that's building decision support tools for human spaceflight today and tomorrow!

Work with NASA flight controllers, scientists, and engineers to build web platforms for planning, executing, and analyzing spacewalks. We are looking for a full-stack engineer who will primarily take the lead on building and deploying Geographic Information Systems (GIS) for lunar exploration. In essence, you will build systems to help NASA decide the "where", "what", and "when" for the next astronauts on the Moon.

Technologies and languages include but are not limited to:

* TypeScript, JavaScript

* React, Redux

* Node

* Python

* SQL

* Docker / K8s

* Various AWS services

Prior experience in GIS is preferred but not required. Must be a US citizen. This is a US government contractor position. If remote, you may be asked to travel to Houston on occasion.

Feel free to respond in thread with any questions!

Not the OP but I can tell you about my experience. I used to work at Udacity, both on engineering and content creation.

We for sure had engineers who were self-taught / learned using online resources (myself included). In fact, I hold zero certifications related to programming.

Over the years we recruited and employed a handful of engineers who pretty much learned everything they knew about programming through Udacity courses. Frankly, I always felt it was a very supportive environment for non-traditional engineers :)

I'm at NASA JSC. We're using Open MCT in a few research projects to monitor simulated spacewalks. We've got dashboards where we're tracking a mix of human physiology data (heart rate, CO2 flow, etc) and spacesuit telemetry (that's mostly simulated at this point).

Great tool! We're looking at relying on it more heavily. I'm actually planning on developing a new widget for Open MCT in the near future :)