Skip to main content

Gather AI

Full Stack Engineer (Hybrid)

Pittsburgh, PAmidAdded 2 months ago

About this role

Join Gather AI as a Full Stack Engineer to architect and build enterprise-grade integrations for a vision-powered warehouse intelligence platform. You'll own the technical direction of platform integrations, lead the transition from growth-era patterns to production standards, and serve as the primary US-based point of contact bridging customer requirements and shipped engineering work.

What you'll do

  • Design and implement distributed systems, APIs, and integrations with performance, fault-tolerance, and horizontal scalability as core concerns
  • Establish and maintain non-functional quality targets for scalability, reliability, availability, latency, security, and observability across the full stack
  • Decompose monolithic APIs into well-bounded services and introduce data-access abstractions to improve scalability and database connection management
  • Partner with Customer Success to translate ambiguous customer requirements into clear, well-scoped engineering deliverables
  • Retire reliability and compliance debt through upgrades, production observability setup, and CI/CD improvements
  • Mentor senior engineers and elevate engineering practices across backend and infrastructure teams

What they're looking for

  • Python, Go, and Node.js
  • PostgreSQL at production scale
  • Kubernetes on Azure
  • REST APIs, protobuf, messaging, and OAuth
  • CI/CD pipeline design and automation
  • Production observability (logs, metrics, traces, SLIs/SLOs)
  • Distributed systems architecture and failure analysis
  • AI-assisted engineering and code validation
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Gather AI

View all jobs at Gather AI

Likely interview questions

  • Walk us through a time you took a large, stateful system to enterprise-grade scale and reliability—what were the key architectural decisions?
  • Describe your experience decomposing a monolithic or overloaded API into well-bounded services; what patterns did you use to manage the transition?
Unlock all 7 questions free — and practice them live →