Software Engineer - AI & Internal Systems

SOFTWARE ENGINEER, INTERNAL SYSTEMS & AI

Quindar is building The Grid: an AI-native system that connects how the entire company thinks, communicates, and executes.

We’re looking for an engineer to operate like a Forward Deployed Engineer — except your customer is Quindar. You’ll embed across Product, Engineering, Sales, Marketing, Programs, and Operations to understand how work gets done and then use software, AI agents, integrations, and automation to make it dramatically better.

This is a unique engineering role for someone who doesn’t just want to receive tickets. You’ll sit within Operations / Business Operations but work across the entire company. You’ll learn how every part of a technology company operates, identify problems yourself, and build the systems that solve them.

The Grid should make information flow through Quindar automatically. A Product Manager writes a specification. From there:

• Engineering requirements and tickets are generated with the context needed for coding agents to begin implementation.
• Engineers review, test, and approve agent-generated software.
• Customer and administrator documentation stays synchronized with the product.
• Marketing can generate accurate blogs, release materials, and technical collateral.
• Sales and Capture teams can access approved product capabilities, architectures, and past performance when building proposals.
• Sensitive information — including CUI and other controlled data — stays within the appropriate security boundaries.

Your job is to build the connective tissue that makes this possible.

• Embed with teams across Quindar to understand how they actually work.
• Identify repetitive, manual, or fragmented workflows that should become software.
• Connect SaaS tools, APIs, databases, internal systems, LLMs, and AI agents.
• Build custom software when an integration or off-the-shelf product isn’t enough.
• Create workflows that turn Product specifications into structured engineering work.
• Give coding agents reliable context from which they can generate software for engineers to review.
• Build systems that keep internal, customer, and administrator documentation continuously current.
• Connect Product knowledge to Marketing, Sales, Capture, and Programs.
• Create secure AI-assisted workflows for government proposals and other controlled information.
• Help establish how humans and agents work together across Quindar.
• Measure what’s working, kill what isn’t, and continuously improve The Grid.

We care more about agency, curiosity, technical judgment, and speed than title or tenure.

• Write production software and is comfortable learning unfamiliar systems quickly.
• Uses AI coding tools naturally and is excited about agentic software development.
• Likes talking to users and understanding the problem before building.
• Can work across APIs, data, automation, backend systems, and lightweight interfaces.
• Comfortable deploying software and writing backend/frontend code
• Is comfortable being handed an outcome rather than a detailed specification.
• Has strong curiosity about how businesses operate.
• Moves quickly and prefers shipping something useful over debating the perfect architecture.
• Can communicate effectively with engineers and non-engineers.
• Has unusually high ownership and isn’t afraid to question an existing process.
• Experience with enterprise integrations, developer tooling, LLMs, agents, knowledge systems, security, or government environments is helpful but not required.

Most engineers spend their careers going deeper into one part of the stack. In this role, you’ll go across the company.

You’ll see how Product decisions become software, how software becomes customer value, how Marketing explains it, how Sales sells it, how government proposals are built, how security affects architecture, and how a growing company actually operates.

If you eventually want to start a company, become an engineering or product leader, or simply understand how technology businesses work end-to-end, there are few engineering seats with this much surface area.

• Product requirements move into Engineering with…