Space Robotics Tech Support Specialist- ROS 2, Docker & Linux (US only) (Remote)

@RaspberryOculus

Drawing from my extensive experience as a Systems Architect with a specialization in hardware integration in high-stakes environments, I'm confident in my ability to support your Space Robotics project. Think Fiber Glass submarine! Combat-ready Rovers! Custom Drone Frames! I've built and troubleshooted just about everything the space robotic project could throw at me. With over 27 years of experience delivering complex, scalable systems on software and electronics, I bring a unique perspective to the table. Moreover, as someone who has worked extensively with FPGA and RF technology (Xilinx Zynq-7020, PYNQ, HackRF), your need for advanced Linux troubleshooting, Docker expertise and dealing with complex software environments is right up my alley. My background in Aerospace Communications Equipment for Mountain RF gave me an intimate understanding of Linux/Ubuntu systems; and having implemented containerized workflows extensively with Docker (including Docker Compose), I have a deep-rooted familiarity with the very tools you require support with.

@mengw3

I integrate robot platforms and I live in Linux. With a university lab I designed a set of robot platforms for inspection, teaching and sorting and guided the student team that assembled them: a tracked mobile base, and a dual-arm mobile robot on an omnidirectional base carrying LiDAR and a depth camera, both running ROS 2. My part was whole machine integration, the ROS 2 side of it, and the vision algorithms. My portfolio also carries a security and waste collection robot running YOLO on a live feed, delivered with video. On the support half of your brief: Linux and Ubuntu are my daily environment, and Docker with Docker Compose is how I ship and reproduce them, ROS 2 nodes included. Driver, configuration and integration faults across several systems that only misbehave together is the kind of thing I chase to root cause, and I write down what I find instead of fixing it silently. On availability: I can commit to the full contract period, November 2026 through December 2027, full time Monday to Friday during 9 to 5 Central Time business hours. Please contact me to discuss details.

@Georgeoustar

Hi there! Supporting advanced space robotics through robust technical troubleshooting is crucial for mission success, and I’m excited by the opportunity to bring my expertise to your project. With a Master’s degree and over four years of hands-on experience in robotics and software environments, I have a deep background in Linux/Ubuntu, Docker, and Docker Compose, as well as strong exposure to ROS 2 and related middleware. I have successfully resolved complex integration and configuration issues in both research and industry settings, collaborating with engineers to diagnose root causes, streamline containerized workflows, and document solutions for future reference. My approach is systematic and detail-oriented—ensuring minimal downtime and clear communication throughout the process. Could you share more about the types of robotics platforms or hardware the technical support will focus on? And, will there be opportunities to contribute to process improvements or workflow automation during the contract? Best Regards, George

@TidewaterDev

Hello, Adam from New Jersey here. The hard part of this Space Robotics Tech Support Specialist role is maintaining stable, containerized ROS 2 workflows on Linux/Ubuntu under tight operational constraints without disrupting ongoing robotics development. My approach aligns with your stack and contract needs: 1. First deliverable: Full audit and documentation of current Docker/Docker Compose and ROS 2 environments to identify fragility points. 2. Implement robust troubleshooting protocols for Linux kernel, driver, and container integration issues. 3. Collaborate closely with robotics engineers to provide timely, practical fixes and maintain detailed solution documentation. 4. Set up continuous monitoring tools for container health and ROS 2 node stability. I supported a similar ROS 2 and Docker-based robotics project where I resolved complex container orchestration failures and Linux driver conflicts, improving uptime by 30%. Also, I handled Linux and Docker Compose troubleshooting for a robotics middleware platform, ensuring seamless integration across distributed systems. Could you share the current ROS 2 distribution and Docker versions in use? Are there specific recurring issues or logs you want prioritized in the initial audit? Please send repository or staging environment access to start the assessment. Thanks, Adam.

@vasudharao9

Hi, I am a graduate from UC Berkeley with a specialization in Artificial Intelligence and Computer Science. I have read the terms and conditions for the project and I am interested in applying. I have over 10 years of experience working in this space and can help you out. Looking forward to chatting with you!

@serdarp4

Hi, Serdar here from The Colony. I understand the role: full-time support for a space robotics project from November through December 2027, CT hours, diagnosing issues across Linux/Ubuntu, Docker and Docker Compose, and working alongside robotics engineers on system, driver, configuration and integration problems. The part I'd expect to matter most day to day is the interaction layer — where containerized workflows meet hardware. Device passthrough, udev rules, permissions on serial and USB devices, and clock sync across containers cause a disproportionate share of robotics support tickets, and they present as application bugs rather than environment problems. Root cause is usually one layer below where the symptom shows up. Documenting those solutions is what compounds — the same driver or permissions issue resurfaces across engineers, and a written answer saves the second and third occurrence. Availability: I can commit to the full contract period at CT business hours. U.S. citizen and resident, able to meet background screening for badging. Q – Is this on-site for badging, or remote with badging for occasional access? Best, Serdar

@dinobartolome

I run Docker and Docker Compose workflows daily across production Linux servers and embedded Linux devices (Raspberry Pi fleet, systemd services, headless Ubuntu setups). Troubleshooting containerized environments is probably 30% of my week -- broken mounts, networking between containers, compose orchestration issues, driver conflicts on Ubuntu. Your posting maps well to my Docker and Linux troubleshooting background. I've done enough embedded Linux and IoT gateway work (Arduino + Pi architectures, sensor integration, USB device bridging) that I'm comfortable in hardware-adjacent software environments where things break in weird ways between system layers. Diagnosing root causes across multiple interacting systems is what I do -- add debug logs, reproduce, isolate, fix, document. Honest gap: ROS 2 isn't part of my daily work. I've read through it enough to know the node/topic/service architecture and how it maps to containerized deployments, but I haven't shipped production ROS 2 systems. If you specifically need deep ROS 2 expertise from day one, better to filter now. If you need someone who can pick up ROS 2 quickly because the Docker, Linux and systems troubleshooting foundation is already solid -- that's me. I'm available for the full Nov 2026 to Dec 2027 contract during CT business hours. Want to talk through the role specifics?

@aminedakhlii

Hi, I’m a software engineer with a Master’s degree in Software Engineering from the University of Michigan–Dearborn and several years of hands-on experience building, deploying, and troubleshooting complex software systems. My background is particularly relevant to the software/infrastructure side of this role: • Linux/Ubuntu development and troubleshooting • Docker and containerized application environments • Backend services, APIs, databases, and system integrations • Diagnosing configuration, dependency, deployment, and environment issues • Working across multiple interconnected software components and identifying root causes • Strong experience taking systems from development through deployment and production support While my primary background is software engineering rather than dedicated robotics support, I’m comfortable working with complex technical environments and can ramp up quickly on ROS 2 and the project’s robotics-specific stack. One point I want to clarify upfront: I meet the technical/education requirements, but I am not a U.S. citizen. If U.S. citizenship is an absolute project-badging requirement, I understand that this would prevent me from qualifying. If there is flexibility on that requirement, I’d be very interested in discussing the position, I can work in the US I have a valid OPT status that ends in April 2027. I am currently abroad visiting family but will be back soon.

@vw1877941vw

⚡Hello! The failure mode this role exists to handle is the one where nothing is broken individually. A ROS 2 node that works on the engineer's machine and not in the container is usually not a code problem — it's DDS discovery failing across the network namespace, or a device node the container can't see, or a mismatched RMW implementation between two images. Those cost engineers days precisely because every component tests fine in isolation. Background: 15+ years in software, with Linux as my daily environment throughout. Ubuntu troubleshooting at the level this needs — systemd units, udev rules, kernel messages, permissions on device access, library and driver version conflicts. Docker and Compose in production, including privileged containers, device passthrough, host networking, and multi-stage builds where the runtime differs from the build environment. How I'd work: reproduce first, isolate the layer, then fix the root cause rather than the symptom. And document it, since the same class of issue recurs across a project this long. Available full-time, Monday to Friday, Central Time, for the full November 2026 to December 2027 period. Two things worth deciding early: 1. Is support primarily for internal engineers, or also flight hardware? 2. Which ROS 2 distribution? Thank you.

@ZenDevelop

Hello, this is Ryan from San Fransico. This role is a strong match for my background in software engineering, Linux systems, containerized applications, and hardware-integrated development. I have 10+ years of software experience working across Python, C/C++, backend systems, automation, Linux/Ubuntu environments, Docker, and system integrations. My recent work has included Raspberry Pi and hardware-connected applications where troubleshooting involves software, operating-system configuration, services, drivers, permissions, device interfaces, and communication between multiple components. I’m comfortable diagnosing issues from logs and system behavior, reproducing failures, isolating root causes, and turning fixes into clear documentation for engineering teams. While ROS 2 has not been the primary focus of my recent projects, I understand robotics software architecture and can work with ROS 2 nodes, topics, services, launch/configuration workflows, and Linux-based robotics environments. My broader software and systems background makes me comfortable learning project-specific robotics stacks quickly. I can support the full November 2026 through December 2027 contract and the required 9:00 AM–5:00 PM Central Time schedule. I can also provide the required degree, residency, citizenship information directly during screening. My question: what ROS 2 distribution, Ubuntu version, and primary robot/hardware platform will the support team be working with? Best Ryan.

@ianb65

Hello, I have a strong background in software engineering, Linux-based systems, Docker/Docker Compose, cloud and containerized environments, and troubleshooting complex multi-service applications. I’m comfortable diagnosing issues across Ubuntu/Linux, containers, dependencies, drivers, networking, configuration, and application integration. My experience includes supporting Python and C++ based systems, containerized deployments, CI/CD pipelines, APIs, real-time services, and distributed software environments. I’m also familiar with robotics-adjacent development workflows and can work effectively with ROS 2 environments, nodes, topics, services, launch configurations, and containerized robotics stacks. I am a U.S. citizen, can meet project screening/badging requirements, and can be available full-time Monday–Friday, 9:00 AM–5:00 PM Central Time for the complete November 2026 through December 2027 contract period. I would be happy to discuss the current robotics stack, development environment, and the most common support issues your engineering team expects to encounter. Best regards, Ian Brown

@elisabethg18

Hello, I’m very interested in supporting your space robotics project and believe my combination of software engineering, embedded systems, and technical troubleshooting experience aligns well with this role. My background includes hands-on work with Linux/Ubuntu, Docker, Docker Compose, Python, C/C++, embedded systems, hardware/software integration, and production software environments. I’m comfortable diagnosing complex issues across applications, containers, operating systems, drivers, devices, and configuration layers, then documenting the root cause and providing practical solutions. I also have experience working with real-time/embedded systems, serial communications, CAN, sensors, and hardware interfaces, which provides a strong foundation for supporting ROS 2-based robotics environments. I can quickly troubleshoot unfamiliar systems and collaborate effectively with robotics and software engineers. I’m available for the full November 2026–December 2027 contract and can work Monday–Friday, 9:00 AM–5:00 PM Central Time. I’d welcome the opportunity to discuss your robotics environment and support requirements.

@Jkeo22

Hello, I’m very interested in supporting your space robotics project because the technical work you describe closely matches the direction of my current robotics work: troubleshooting ROS 2, Linux/Ubuntu, Docker, simulation, and software integration problems. I currently work with ROS 2 Jazzy and Gazebo in Linux-based development environments. My hands-on robotics work has required me to troubleshoot problems involving ROS 2 builds and dependencies, robot configuration and URDFs, transforms, LiDAR and sensor behavior, simulation compatibility, and interactions between multiple software components. I have also worked with Docker/containerized environments, Git/GitHub, GitHub Actions, Python, and C++. Contact me discuss relevant experience I want to be transparent that I am earlier in my career than the qualifications listed. I am currently completing my B.S. in Computer Science and do not yet hold a master’s degree or 2–5 years of professional robotics experience. I am applying because the actual technical responsibilities align unusually well with the robotics, Linux, and troubleshooting work I am already doing. I would be happy to discuss my ROS 2 projects or walk through specific technical problems I have diagnosed and resolved. Thank you for your consideration, Julie Keosourinha