This is a remote position.

About Glīd Technologies

Glīd Technologies is transforming first-mile logistics with autonomous road-to-rail vehicles, AI-powered logistics platforms, and human-centered workforce strategies. Our products — GliderM, EZRA-1SIX, and Rāden — move goods cleaner, faster, and smarter while creating economic opportunities in the communities we serve.
Founded by a U.S. Army and U.S. Air Force veteran with SpaceX experience, Glīd is led by a team with deep technical and operational expertise from industry leaders including Bombardier, Google, and other world-class organizations. We combine a mission-driven mindset with relentless innovation to deliver solutions that benefit both industry and people.

Key Responsibilities

We're looking for a founding engineer to join our early-stage startup as one of our first software engineers. This isn't a typical engineering role—you'll be a key architect of both our product and company culture, with the primary mission of helping us achieve our vision rapidly.

As a founding engineer, you'll wear many hats and work directly with leadership to build something people truly want. You'll have significant learning and experiences along with the opportunity to shape our technical direction from the ground up.

Your engineering decisions, technology choices, and daily priorities should be guided by one overarching goal: building a product that users love and that creates a sustainable, profitable business.

Product Development

• Build features, MVPs and capabilities rapidly using strong development practices.
  

• Lead engineering decisions that balance speed of development and engineering excellence.
  

• Lead technical design reviews and conversations with CTO
  

• Balance technical debt strategically—use it tactically to accelerate development, pay it down when it blocks progress
  

• Evolve technical architecture as product requirements become clearer through user feedback
  

• Write high quality documentation, FAQs, and user guides.
  

Strategic Thinking

• Provide technical feasibility input before features are designed
  

• Help leadership understand complexity and time investment for different approaches
  

• Balance short-term feature delivery with long-term technical enablers
  

• Make build vs. buy decisions based on core competencies and resource constraints