Principal Software Architect

The Role

Bring classically trained, broad software architecture expertise to the Digital Journey Architecture and
Solutions team. DJAS architects have developed deep knowledge of Lumen's systems through years of
embedded work - this role brings the architectural discipline, patterns, and methodologies that complement
that institutional depth. The Principal Software Architect raises the architectural quality bar across DJAS's
design work by bringing formal architecture practices, modern system design patterns, and a perspective
that isn't shaped entirely by how things have been done at Lumen.
This is not a domain specialist role. The value is breadth, discipline, and the ability to apply proven
architectural principles to complex, multi-system problems - including the emerging domain of
AI-augmented and agentic systems.

Location

This is a remote opportunity open to candidates located anywhere in the U.S.

The Main Responsibilities

• Apply proven software architecture principles to DJAS design work: microservices, event-driven
  patterns, distributed systems, API-first design, domain-driven design
• Lead architecture design sessions and design reviews - challenge assumptions, surface tradeoffs,
  ensure solutions address NFRs (performance, reliability, scalability, observability, security) from the start
  Produce high-quality architecture artifacts: solution designs, ADRs, integration specifications,
  architecture standards
• Define architecture governance practices: what makes a design "good enough to ship" vs what needs
  more work; codify standards the team applies consistently
• Evaluate and adopt modern architecture patterns and methodologies - not just what Lumen has done,
  but what the broader engineering discipline has learned
• Apply AI-augmented engineering practices: LLM-assisted design, agentic workflow architecture,
  integrating AI capabilities into system designs safely and observably
• Architect for operational excellence: observability-first design, chaos engineering readiness,
  runbook-aligned failure handling
• Bridge the gap between architecture and implementation: stay present through delivery, validate that
  what gets built matches the design intent, surface gaps early
• Mentor architects and engineers on architecture fundamentals, design patterns, and how to think about
  system design rigorously
• Partner with cloud, IAM/security, and domain architects to ensure cross-cutting concerns are
  addressed coherently across DJAS's portfolio
• Challenge technical debt patterns where they emerge in designs - not to block delivery, but to ensure
  the team is making conscious choices

What We Look For in a Candidate

• Bachelor's degree in computer science, engineering, or related field with 12+ years of software
  architecture experience or
• Master's degree with 10+ years of software architecture experience
• AI-first practitioner - actively integrates AI tools (LLMs, coding assistants, AI-powered analysis and
  design tools) as a routine part of architecture and engineering work, not as an occasional experiment.
• Candidates must demonstrate specific, current examples of how AI has meaningfully accelerated or
  improved their work.
• Classically trained software architecture background: formal education or structured architecture
  practice exposure (not exclusively developed through a single company's environment)
• Deep expertise in distributed systems: microservices, event-driven architecture, saga patterns, CQRS,
  async messaging
• API design authority: REST, gRPC, GraphQL - knows when to use each, how to version, how to
  govern
• Domain-driven design (DDD) and bounded context modeling
• Non-functional requirements design: performance engineering, reliability patterns (circuit breakers,
  bulkheads, retries), scalability modeling
• Observability architecture: OpenTelemetry instrumentation, metrics design, distributed tracing, alerting
  standards
• Security architecture integration: threat modeling, secure design patterns, data classification in
  architecture
• Strong written and verbal communication: can produce ADRs and solution designs that are clear,
  precise, and decision-quality
• Track record of delivered production systems - not just designs, but architectures that were built and
  operated

Preferred

• Experience architecting AI/ML-augmented systems: LLM integration patterns, RAG architecture,
  agentic workflow design
• Cloud-native architecture depth (AWS, Azure, or GCP) - complements the dedicated Cloud Architect
  role
• Experience in telecom, network automation, or NaaS domains - reduces ramp time on Lumen-specific
  context
• Platform architecture experience: designing systems that other teams build on, not just end-user
  applications
• Architecture governance experience in a multi-team engineering organization: standards enforcement,
  design review processes, exception handling
• Contributions to technical standards bodies, open source architecture frameworks, or published
  architectural thinking

Compensation