Principal Software Architect

Company Overview

Trianz is an applied AI solutions company that accelerates customer business transformation through AI powered "Transformation Services as a Software Model". With 25+ years of transforming enterprises, we've evolved to a product-led, platform-driven organization serving global enterprises across Financial Services, Insurance, Healthcare, Hi-Tech, Manufacturing, and other industries.

With global presence across 4 continents, our platform portfolio under the unified Concierto brand delivers end-to-end transformations including solutions for Migrate, Manage, Maximize, Modernize, Insights & Agentic AI, and SecOps - delivered through strategic partnerships with leading hyperscalers.

We're building the premier innovation-led organization in the digital transformation space through AI-first methodologies and data-driven excellence - RevolutionAIzing Transformations.

Role Overview

Trianz is unifying its multi-module enterprise SaaS platform — Concierto — into a single, cohesive deployment and customer experience. Today, product modules operate as separate deployments. Your mandate is to design the blueprint that eliminates that fragmentation: a single deployable artifact, shared data model, unified API contracts, toggle-based module enablement, and one operational experience for every enterprise customer.

This is a pure individual contributor architecture role. You produce the specifications; the product engineering team implements them. You will not own feature delivery — you will own the standards, contracts, and architectural decisions that govern how the entire platform evolves.

This role requires someone who has been here before — someone who has actually designed and delivered a unified multi-module SaaS product in production, in a regulated enterprise environment, and produced implementation-ready specifications that engineering teams built from without needing the architect in the room.

If you produce slide decks but not buildable specs, this is not the role for you.

Key Responsibilities

Unified Platform Architecture

• Design a unified deployment architecture enabling multiple product modules to run as a single deployable artifact
• Define the shared data model: how core entities (workloads, assets, operational state) are owned and shared across all product modules
• Specify cross-module API contracts and event contracts so modules operate independently or together without tight coupling
• Produce the toggle-based module enablement specification: a customer adds a new module without re-deploying the base product

Enterprise Deployment & Regulated Verticals

• Design the self-service deployment experience for enterprise customers
• Produce reference architectures for regulated enterprise verticals: financial services, government, multi-cloud
• Architect for enterprise requirements: security, compliance, private deployment, and customer-level customization
• Define deployment patterns that support air-gapped, on-premises, and hybrid customer environments

Decomposition & Decoupling

• Identify and document the decomposition path for all existing coupling between modules
• Specify bounded context boundaries and inter-module communication patterns
• Define migration paths that allow incremental decoupling without breaking existing deployments
• Design the event-driven architecture for cross-module state synchronization

Architecture Governance

• Provide architectural governance to the product engineering team: review designs, enforce standards, maintain the architecture decision record (ADR)
• Produce implementation-ready specifications — clear enough that engineering teams build without needing the architect present
• Review all system designs before implementation and sign off on architecture decisions
• Establish and maintain platform design standards across all product modules

Ideal Candidate Profile

Experience: 15+ years

Platform & Product Architecture:

• Designed a shared data model or unified platform layer across multiple products or services in production
• Delivered a multi-module SaaS product where customers could enable or disable modules independently
• Microservices architecture at enterprise scale: decomposition, API contract design, event-driven patterns
• Produced implementation-ready specifications that engineering teams built from without further interpretation
• Worked in a regulated enterprise environment: financial services, government, or healthcare
• 10+ years in enterprise/software architecture with at least one unified multi-module product delivered

Technical Depth

• Deep expertise in shared data model design across distributed systems
• Strong command of API contract design: versioning, backwards compatibility, deprecation strategies
• Experience with event-driven architecture for cross-module communication
• Proficiency in decomposition patterns: bounded contexts, strangler fig, anti-corruption layers
• Understanding of enterprise deployment patterns: multi-tenancy, tenant isolation, feature toggles
• Knowledge of compliance requirements in regulated verticals (financial services, healthcare, government)

Specification Quality

• Ability to produce unambiguous, implementation-ready architecture documents
• Experience authoring Architecture Decision Records (ADRs) and platform design standards
• Comfort producing data model schemas, API contracts, and event schemas — not just diagrams
• Track record of engineering teams building from your specs without daily clarification

Mindset & Fit

• Architect-first mindset: you define the what and why; engineering defines the how
• Comfortable with long-term architectural ownership, not project-based consulting
• High written communication standard — your specs are your product
• Capable of holding architectural authority in the face of engineering pushback
• Motivated by platform coherence and long-term system health, not feature delivery

Good to Have

• Domain-Driven Design (DDD) — bounded context decomposition and context mapping
• API gateway design — rate limiting, versioning, backwards compatibility patterns
• Event-driven architecture — Kafka or Pub/Sub for cross-module communication
• Architectural governance experience — providing design authority to product engineering teams
• SaaS platform experience — multi-tenancy, module marketplace, self-service provisioning
• Cloud-native patterns — Kubernetes-based deployment, Helm chart architecture, operator patterns
• Infrastructure as Code — Terraform-based deployment architecture standards

This Is NOT This Role

❌ A solutions architect who produces slide decks but not implementation-ready specifications

❌ Someone who needs to own feature delivery — this role produces standards, not features

❌ A consultant profile without long-term architectural ownership

❌ A general enterprise architect without multi-module SaaS product experience