We’re building a pretty ambitious product. It’s a complex challenge, but doable, and honestly a lot of fun.
We already have a product that our customers love, but we’re looking for more great people to help us make every part of it exceptional.
At Stacksync, we help companies run critical business operations across their enterprise systems. For example, companies like Just Ingredients rely on us to power and automate key processes such as order management.
What Makes This Role Different
We solve difficult distributed systems problems involving:
- queues and event-driven systems
- agentic workflows
- large-scale data movement in real time
- Postgres-heavy architectures
This is not a typical CRUD SaaS role.
We are building a category-defining infrastructure company and are looking for strong product-minded engineers who want ownership over real systems, internal platforms, and infrastructure products from architecture to production operations.
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
- Python
- React
- Postgres
- Distributed queues and workflows
- What excites you about building infrastructure systems at Stacksync? (2 sentences max)
- Rate yourself from 0–10 on:
- Python
- React
- Postgres
- Designing real-time systems
For each, include one concrete example demonstrating your depth.
- Describe the most technically challenging system you worked on:
- Context
- Your exact contribution
- Why it was difficult
- Key learnings
- What is one of the biggest risks or bets you’ve taken in your career or life?