Software Architect

Founded in 2004, NetBrain is the leader in no-code network automation. Its ground-breaking Next-Gen platform provides IT operations teams with the ability to scale their hybrid multi-cloud connected networks by automating the processes associated with Diagnostic Troubleshooting, Outage Prevention and Protected Change Management.  Today, over 2,500 of the world’s largest enterprises and managed services providers leverage NetBrain’s platform.

What We Need

NetBrain is looking for a Software Architect to own the end-to-end technical architecture of our next-generation SaaS platform on AWS. This is a senior, hands-on leadership role at the intersection of infrastructure, platform engineering, and product strategy — ideal for someone who has successfully taken a product from on-premises or private cloud to public SaaS and wants to do it again at scale.

The Impact You'll Make

As a Software Architect, you will set the foundational technical direction for NetBrain’s cloud platform. Your architecture decisions will determine how the product scales, how securely it handles enterprise customer data, and how efficiently engineering teams across the organization can build on top of a shared, well-governed infrastructure. You will work directly with engineering leadership and product management, mentor senior engineers, and produce the standards, ADRs, and documentation that give teams clarity and autonomy.

What You'll Do

• Define the reference architecture for NetBrain’s SaaS platform on AWS, covering compute, networking, data, messaging, and observability layers.
• Lead the multi-tenancy design strategy, including data isolation, tenant routing, and compliance boundaries.
• Own the Infrastructure-as-Code strategy using Terraform and AWS CloudFormation, establishing reusable modules and IaC governance across engineering teams.
• Design the container and Kubernetes orchestration platform: cluster topology, workload scheduling, autoscaling, and namespace conventions.
• Architect the event-driven messaging layer using RabbitMQ (preferred) or Kafka, including schema governance, dead-letter handling, and consumer patterns.
• Define the polyglot persistence strategy across relational databases and MongoDB, including data modeling standards and backup/recovery procedures.
• Establish the observability stack (metrics, tracing, logging, alerting) and SLI/SLO frameworks aligned to enterprise customer expectations.
• Embed security into the platform architecture: encryption, IAM, secrets management, network segmentation, and a path to SOC 2 Type II.
• Produce architecture decision records (ADRs) and documentation that guide engineering teams and inform product leadership.