Senior Full Stack Software Engineer

About Us

Integrate is a Seattle-based company building multiplayer project management software for the world’s most ambitious machines. We focus on the hardest coordination problems in deep tech like rocket launches and advanced manufacturing, where progress depends on seamless collaboration across companies. Increasingly, this work sits at the intersection of two of the most consequential forces shaping the modern world: defense and artificial intelligence, where both the pace of innovation and the stakes of execution are exceptionally high.

Integrate enables teams to collaborate with vendors, customers, and partners as fluidly as modern tools support internal teams. Our mission is to modernize how organizations build together in the emerging deep tech economy, reducing friction, misalignment, and unnecessary work at every step.

Traditional project management tools weren’t designed for the speed, scale, and interdependence of modern hardware development. Integrate is purpose-built for this new reality. We provide a platform that brings clarity and structure to complex, cross-organizational programs helping teams communicate effectively, stay aligned, and move faster with confidence. By improving how critical information is shared and decisions are made, we enable organizations to focus on what matters most: building the future.

We’re hiring a Full Stack Software Engineer to help us build and evolve the product layer of Integrate’s platform. This role spans the full stack — from React-based UI surfaces to Go APIs and the integrations that tie them together — and sits at the center of where our product meets our users. That last part matters: we want engineers who feel the weight of that position, not just the technical scope of it.

The near‑t focus includes feature work on our cross‑domain solution workflows, improving how we surface complex project data to end users, and contributing to the API and integration services that sit beneath it. You’ll work closely with product, design, and backend engineers to ship things that matter — and you’ll be expected to show up as a full participant in product thinking, not just an executor of specs.

That means understanding the user problem behind the work, speaking up when something doesn’t serve them well, and treating polish and UX quality as engineering requirements. We’re a small team. There’s no handoff culture here. If you build it, you own it.

• Build and iterate on React-based UI surfaces that make complex project workflows legible and fast for end user
• Design and maintain REST APIs and GraphQL layers in Go, working across internal and external consumers
• Own and evolve data models in PostgreSQL — schema design, query optimization, and migration management
• Contribute to our GraphQL integration layer, ensuring resolvers are well‑structured and performant
• Build and maintain integration services in Go that connect internal systems and external APIs, owning the full contract from interface design to error handling and observability
• Write and maintain CI/CD pipelines using Git Hub Actions including build, test, and deployment stages across environments
• Ship clean, tested, maintainable code across the stack — and leave things better than you found them

• React
• Golang
• GraphQL
• REST
• PostgreSQL
• Git Hub Actions

• 3–5+ years of full stack engineering experience in a product‑focused environment
• Strong React fundamentals — component architecture, state management, and performance;
  Apollo Client familiarity is a plus
• Solid HTML5 and CSS3; able to build clean, responsive interfaces without leaning on a framework crutch
• Go on the backend — REST API development, middleware, and service patterns
• PostgreSQL — comfortable with schema design, query writing, and migrations
• GraphQL — can read and reason about a resolver, understands n+1 patterns and common pitfalls; bonus if you’ve worked with complex or graph‑structured data models
• Familiarity with integration patterns — webhooks, third‑party API design, or similar
• Some exposure to broader backend concerns: caching, rate limiting, or async processing
• Git Hub Actions or similar…