Founding Software Engineer

Founding Software Engineer

Full-Time 60000 - 80000 € / year (est.) No home office possible
Seeing Systems (YC W26)

At a Glance

  • Tasks: Design and build the core autonomy stack for cutting-edge drones.
  • Company: Join Seeing Systems, a pioneering team in autonomous drone technology.
  • Benefits: Founding-level ownership, equity, and the chance to shape engineering culture.
  • Other info: Fast-paced startup environment with opportunities for rapid growth.
  • Why this job: Make a real impact on robotics and drone intelligence from day one.
  • Qualifications: Strong software skills, experience in robotics, and a passion for innovation.

The predicted salary is between 60000 - 80000 € per year.

About Us

Seeing Systems is building autonomous drone systems that can perceive, navigate, and act intelligently in complex real‑world environments. We focus on advancing autonomy through monocular vision, sensor fusion, and robust system design, enabling drones to operate reliably where traditional systems fail. Seeing Systems was founded by brothers Matthew and Alex Le Maitre, combining deep experience across software, robotics, and defense.

The Role

We’re hiring a Founding Software Engineer to help design and build the core autonomy stack powering our drones. This is a deeply technical, hands‑on role where you’ll work across perception, planning, and systems infrastructure—owning critical pieces of the product from day one. You’ll partner directly with the founders to define architecture, make key technical decisions, and ship systems that perform reliably both in simulation and in the field.

What You’ll Do

  • Design and build core components of the autonomous drone stack
  • Develop perception and state estimation systems using monocular vision and sensor fusion
  • Work with and extend robotics frameworks like ROS / ROS2
  • Build and test algorithms in simulation environments such as AirSim, and deploy to real systems
  • Implement and optimize SLAM, localization, and navigation pipelines
  • Interface with sensors, compute systems, and flight controllers
  • Contribute to system architecture across software, hardware, and communications layers
  • Rapidly prototype, test in the field, and iterate on real‑world performance
  • Leverage modern AI tools and workflows to accelerate development and experimentation
  • Help define engineering culture, tooling, and hiring as a founding team member

Within your first 30 days, you’ll deploy your first vision‑based navigation update to a physical drone and test it in the field, and within 90 days, you’ll be co‑owner of our internal autonomy stack, responsible for large‑scale development and direction of our primary software product.

What We’re Looking For

  • Strong software engineering skills, with Python preferred (C++, Rust or OCaml is a plus)
  • Experience building robotics, real‑time, or distributed systems
  • Familiarity with ROS / ROS2 and working across simulation + hardware
  • Strong intuition for systems, debugging, and performance tradeoffs
  • Comfortable operating in ambiguity and moving quickly in a startup environment
  • High ownership mindset—you build, test, and ship end‑to‑end
  • Heavy user of AI tools (e.g., Claude code) to accelerate output
  • Willing to go outside with us and test in the real world!

Nice to Have

  • Experience with SLAM, visual odometry, or 3D reconstruction
  • Background in computer vision (especially monocular/depth estimation)
  • Experience with sensor fusion (e.g., IMU + camera, Kalman filters)
  • Familiarity with AirSim or similar simulation platforms
  • Experience working with drones, UAV systems, or embedded systems
  • RF or communications systems experience
  • Prior startup or founding engineer experience

Why Join

  • Founding‑level ownership and significant equity
  • Opportunity to build cutting‑edge autonomous systems from first principles
  • Work on real‑world robotics problems with immediate, tangible impact
  • Tight iteration loop between simulation and deployment
  • Small, high‑agency team moving quickly

If you’re excited about building autonomous systems that operate in the real world—and want to help define the future of drone intelligence—we’d love to talk.

Founding Software Engineer employer: Seeing Systems (YC W26)

At Seeing Systems, we pride ourselves on being an exceptional employer that fosters innovation and collaboration in the rapidly evolving field of autonomous drone technology. Our dynamic work culture encourages hands-on involvement and offers founding-level ownership, allowing you to make a significant impact from day one while working alongside experienced founders. With opportunities for professional growth and the chance to tackle real-world challenges, you'll be part of a small, agile team dedicated to pushing the boundaries of robotics and perception.

Seeing Systems (YC W26)

Contact Detail:

Seeing Systems (YC W26) Recruiting Team

StudySmarter Expert Advice🤫

We think this is how you could land Founding Software Engineer

Tip Number 1

Network like a pro! Reach out to people in the industry, attend meetups, and connect with potential colleagues on LinkedIn. You never know who might have the inside scoop on job openings or can put in a good word for you.

Tip Number 2

Show off your skills! Create a portfolio showcasing your projects, especially those related to robotics and autonomous systems. This will give you an edge and demonstrate your hands-on experience to potential employers.

Tip Number 3

Prepare for technical interviews by brushing up on your coding skills and understanding key concepts in robotics and AI. Practice common interview questions and consider mock interviews to build your confidence.

Tip Number 4

Apply through our website! It’s the best way to ensure your application gets seen by the right people. Plus, it shows you’re genuinely interested in joining our team at Seeing Systems.

We think you need these skills to ace Founding Software Engineer

Software Engineering
Python
C++
Rust
OCaml
Robotics Frameworks (ROS / ROS2)
Simulation Environments (AirSim)

Some tips for your application 🫡

Show Your Passion for Robotics:When you're writing your application, let your enthusiasm for robotics and autonomous systems shine through. We want to see that you’re not just skilled but genuinely excited about the work we do at Seeing Systems.

Tailor Your Experience:Make sure to highlight your relevant experience in software engineering, especially with Python, ROS, or any robotics frameworks. We love seeing how your background aligns with our needs, so don’t hold back on those details!

Be Clear and Concise:Keep your application straightforward and to the point. We appreciate clarity, so avoid jargon unless it’s necessary. Remember, we want to understand your skills and experiences without wading through fluff.

Apply Through Our Website:We encourage you to apply directly through our website. It’s the best way for us to receive your application and ensures you’re considered for the role. Plus, it shows you’re keen on joining our team!

How to prepare for a job interview at Seeing Systems (YC W26)

Know Your Tech Inside Out

Make sure you’re well-versed in the technologies mentioned in the job description, especially Python, ROS/ROS2, and SLAM. Brush up on your understanding of sensor fusion and real-time systems, as these will likely come up during technical discussions.

Showcase Your Problem-Solving Skills

Prepare to discuss specific challenges you've faced in previous projects, particularly those related to robotics or autonomous systems. Be ready to explain how you approached these problems, the solutions you implemented, and the outcomes.

Demonstrate Your Hands-On Experience

Since this role is very hands-on, be prepared to talk about any practical experience you have with drones or simulation environments like AirSim. If possible, bring examples of your work or projects that highlight your ability to build and test algorithms in real-world scenarios.

Emphasise Your Ownership Mindset

Seeing Systems is looking for someone who takes ownership of their work. Share examples of times when you’ve taken initiative in a project, whether it was leading a team, making key decisions, or driving a project from concept to deployment.