- Every state transition must be correct, auditable, and traceable
- You have 3+ years building serious internal systems
- You have designed relational data models that survived real usage
- You think in states, events, queues, and failure modes
- You care deeply about data integrity and correctness
- You can work end-to-end: backend, frontend, and database
- You have built systems used daily by non-technical operators
- You are comfortable saying “no” when complexity is unjustified
- You want full ownership—not a narrow slice of a massive org
- You only want to work on consumer apps
- You avoid responsibility for production systems
- You rely on buzzwords instead of fundamentals
- You have never owned a system after launch
- You need heavy process, layers of management, or vague requirements
- Led development of a business-critical system end-to-end
- Experience deploying and operating systems in AWS
- Strong SQL and relational data modeling (Postgres, SQL Server, MySQL)
- Backend API design (REST or GraphQL)
- Deep understanding of Cyclone’s operational reality
- Clear system architecture and data model
- 6–12 Months
- Leadership making decisions from live operational data
- Immediate real-world impact instead of abstract metrics
- You don’t get to hand-wave complexity away with abstractions or process theater
- There’s a well-known story in engineering circles—not because of the specifics, but because of the principle behind it—where a team estimates months to solve a complex technical problem
- Is comfortable sitting with complexity instead of avoiding it
- Prefers solving the real problem rather than managing around it
- Understands that speed comes from clarity, not shortcuts
- Is willing to take responsibility for outcomes—not just effort
If you want to build something that lasts, take ownership over years—not months—and solve problems most people avoid—quickly, correctly, and decisively—then you’ll have the authority and backing to do it here
