SafetyChain is building the next generation of enterprise software for the supply chain—systems that actually help operators think, decide, and act in real time.
Requirements
- 8+ years building modern web applications or distributed systems (enterprise experience strongly preferred).
- Strong background in at least one of: TypeScript, Python, Go, Java, or C-Sharp.
- Experience with multiple data storage models—document, columnar, relational—and clear reasoning about tradeoffs.
- Ability to design and debug systems that operate at real-world scale and complexity.
- Experience building and maintaining APIs, data pipelines, or backend primitives.
- Strong architectural intuition around distributed systems, eventing, and state management.
- Ability to design clean contracts between backend and frontend.
Responsibilities
- Building high-performance services and applications in an end-to-end TypeScript environment (Deno backend + unified front-end framework).
- Working in a monorepo with strong engineering conventions and automated tooling to accelerate iteration.
- Using AI-driven developer workflows (code generation, scaffolding, automated tests, modeling, inference-based data mapping, etc.) to dramatically speed up delivery.
- Making pragmatic architectural decisions—knowing when to build, when to buy, and when to rely on the surrounding ecosystem.
- Designing systems where platforms emerge from real demand rather than speculative abstraction.
- Building enterprise-scale features with attention to reliability, data semantics, and real-world operational constraints.
- Partnering closely with Product and AI/ML teams to translate domain complexity into clean, scalable systems.
Other
- Comfort with hybrid work and in-office collaboration for high-context problem-solving.
- Contributing to an “office-first when collaboration matters” culture that values high-bandwidth problem solving and clear ownership.
- You’re allergic to cargo-cult engineering and prefer reasoning from first principles.
- You default to outcome-based decisions instead of theoretical purity.
- You don’t chase platform work for its own sake—platforms should *emerge from repeated need.
