We are a product development team building a cloud-native, ERP-agnostic SaaS platform focused on warehouse and operations management. Our architecture is built around a .NET 9 core backend with a connector-based design that allows us to integrate with any ERP system — current and future. We're looking for a senior engineer who can own the technological platform: cloud infrastructure, CI/CD, and the architectural decisions that keep a heavily customized, multi-tenant product stable and scalable as it grows. This is not a pure backend role, and it's not a pure DevOps role. It sits at the intersection of both — the person we're looking for writes production code and designs the systems that ship and run it reliably. The position is fully remote. Flexible 40h/week with at least 4 hours overlap during 8am–12pm Pacific. We hire worldwide.

Responsibilities

• Design and evolve our AWS-native infrastructure using infrastructure-as-code (AWS CDK preferred), ensuring environments are reproducible and auditable.
• Own CI/CD pipelines that support a heavily customized product — where a release for one customer must not destabilize another.
• Implement branching strategies, environment promotion workflows, and release gating that work at the pace of a product team.
• Write and review production-grade .NET 9 code across the core platform and connector framework.
• Design APIs and integration patterns that ERP connectors can implement consistently, regardless of the underlying system.
• Lead technical design of new modules and features with an explicit focus on backward compatibility and not breaking existing behavior.
• Define and maintain observability: structured logging, distributed tracing, and alerting that surfaces real problems before customers do.
• Collaborate with the rest of the team on system design, code reviews, and platform reliability.

Required Qualifications

• Senior-level .NET — C# with .NET 6+ in production; comfortable with .NET 9 and migration paths from older versions.
• AWS depth — hands-on with ECS/EKS, Lambda, SQS/SNS, RDS, and the surrounding ecosystem; able to make architecture decisions, not just deploy resources.
• Infrastructure as code — AWS CDK strongly preferred; Terraform or CloudFormation acceptable.
• CI/CD design — experience designing branching models, deployment strategies (blue/green, canary), and rollback mechanisms for complex software products.
• Multi-tenant SaaS — experience with tenant isolation, per-tenant configuration, and the release engineering challenges that come with customization-heavy products.
• Distributed systems — event-driven patterns, message queuing (SQS/SNS, RabbitMQ, or Kafka), and resilient service communication.
• SQL and NoSQL — query optimization and data modeling across relational (SQL Server preferred) and non-relational stores (MongoDB, Redis, DynamoDB).
• Containerization — Docker in production; experience with orchestration at meaningful scale.
• Testing — strong practice around unit, integration, and end-to-end testing; experience designing test strategies for systems where regressions in existing behavior are a real business risk.

Preferred Qualifications

• Experience building or maintaining a connector, plugin, or integration framework where teams implement against a defined contract.
• ERP integration experience — SAP Business One (DI API, ServiceLayer) or Acumatica API are directly relevant; any deep ERP integration work translates.
• WMS domain knowledge — warehouse workflows, inventory models, and real-time operational complexity.
• Observability tooling — CloudWatch, OpenTelemetry, Datadog, or equivalent.
• NuGet package authoring or open source library maintenance — experience publishing and versioning reusable .NET packages, particularly in an SDK or framework distribution model.
• AI agent development — experience building or integrating AI agents and agentic workflows, particularly in the context of automating complex, multi-step processes.
• Frontend fluency — TypeScript-based framework (React, Vue, Angular, or SAPUI5) sufficient to review and contribute to the UI layer when needed.

#LI-DNI