We’re building a pretty ambitious product. It’s a complex challenge, but doable, and honestly a lot of fun.

Most AI products help individuals save minutes. Stacksync helps companies run their operations. Our enterprise AI is built on years of expertise in connectors, syncs, and workflow orchestration, allowing businesses to automate the processes that directly impact e-commerce, supply chain, logistics, operations.
Under the hood, the product handles deep technical infrastructure: asynchronous jobs, data mappings, approvals, errors, retries, and multi-system orchestration.

What Makes This Role Different

Our extensive suite of connectors and deep expertise in syncs and workflows form the foundation of our enterprise AI. To design, scale, and continuously improve our 'genies,' you will need to:

• design highly performant, modular architectures capable of handling high-throughput data streams
• build agentic workflows handling real-life enterprise use cases while simultaneously driving architecture improvements across the shared, generic codebase
• work with:
  • queues and event-driven systems
  • workflows execution engine
  • large-scale data movement in real time
  • Postgres-heavy architectures
  • deep ownership over the internal platforms and heavy infrastructure powering our AI agents from architecture to production

This Opportunity IS for You If

• You enjoy difficult engineering problems
• You care deeply about system quality and maintainability
• You thrive in fast-moving, high-ownership environments
• You enjoy scaling distributed systems
• You think like a product owner, not just an implementer
• You naturally take initiative without waiting for permission
• You want to build infrastructure used by real enterprise customers that power critical operations
• You are extremely ambitious
• You want to work with a very strong technical team

This Opportunity IS NOT for You If

• You only enjoy building simple CRUD applications
• You dislike operational complexity
• You need highly structured environments
• You avoid ownership
• You prefer maintaining existing systems over building new ones
• You think shipping one feature per day is “fast”
• You are uncomfortable with ambiguity or pressure
• You believe scaling infrastructure is mostly solved already

Tech Stack

• PythonGo
• React
• Postgres
• Distributed queues and workflows

⚠️ Apply By Answering ⚠️

1. What excites you about building infrastructure systems at Stacksync? (2 sentences max)
2. Rate yourself from 0–10 on:

• Python
• Go
• React
• Postgres
• Designing real-time systems

For each, include one concrete example demonstrating your depth.

3. Describe the most technically challenging system you worked on:

• Context
• Your exact contribution
• Why it was difficult
• Key learnings

4. What is one of the biggest risks or bets you’ve taken in your career or life?

• Meet with the CTO
• Real-world technical scenarios (not LeetCode)
• System design and architecture discussions
• Production/debugging-oriented conversations