Senior Technical Lead and Principal Architect
Senior Technical Lead & Principal Architect – client
Modernization Programs
Location: Remote
Type: Full-Time
Seniority: Principal Engineer / Lead Architect**
Reports to: Executive Technical Sponsor
Role Summary
Our client is embarking on a multi-year modernization of its dental technology ecosystem to create a unified, secure, scalable, and interoperable digital experience for practices, DSOs, and
partners.
We are seeking a Senior Technical Lead & Principal Architect to own the end-to-end technical direction, architecture, and engineering execution for all modernization workstreams, including:
â—ŹPlatform Architecture Modernization
â—ŹPostgres migration (SQL Anywhere EOL 2028)
â—ŹAPI expansion and de-coupling from release cycles
â—ŹToken deprecation & partner integration redesign
●“One-Agent” cloud service & writeback model
●DataCore / Data Lake (Bronze → Silver → Gold) modernization
â—ŹCross-product unified schema ( + + )
â—ŹDoc manager modernization
â—ŹRelease engineering, quality engineering, and CI/CD uplift
This role is the technical brain of the modernization effort—defining patterns, building
reference architectures, reviewing implementation, making the critical go/no-go decisions, and
ensuring client’s future platform aligns with enterprise-grade scalability, extensibility, and
interoperability expectations.
Key Responsibilities
1. Architectural Ownership Across All client Modernization Tracks
â—Ź Define the end-state architecture for modernization, Data Platform/Data Lake
integration, agent strategy, and multi-product interoperability.
â—ŹEstablish architectural guardrails, coding standards, and modernization patterns for legacy C++, PowerBuilder, WCF, and .NET Framework components.
â—ŹDesign the future state of:
â—‹SOA/API layer
â—‹Version-agnostic, independently deployable API
â—‹Partner integration layer (REST, event-driven, potential FHIR entry points)
â—‹Real-time bidirectional sync model via sockets or event streams
â—‹Data ingestion, replication & transformation pipelines
â—‹Unified cloud marketplace & vendor access architecture
2. Lead the Architecture Transformation
●Guide the migration from SQL Anywhere → Postgres.
â—ŹDefine how legacy WCF services evolve into 3-tier services, REST endpoints, or new microservices.
â—ŹEstablish validation rules, dependency mappings, and object relationships for safe
writeback operations (currently undocumented and embedded in code).
â—ŹArchitect the deprecation and retirement of the shared database token used by
partners.
â—ŹOversee modernization around installation, self-updating mechanisms, telemetry, and
performance monitoring.
â—ŹServe as the primary architectural reviewer for SmartDoc modernization.
3. Architect the Data Lake + Microsoft Fabric Data Platform
â—ŹDefine ingestion patterns and eServices data.
●Build transformation models to move data from Bronze → Silver → Gold, ensuring a unified schema across legacy systems.
â—ŹDesign patterns for PHI-safe handling, separation of sensitive data, and identity-based access.
â—ŹAlign with Azure Data Factory, OneLake, DataBricks, and Synapse tooling.
●Define “developer-friendly” integration endpoints above the lake (REST, events, websocket patterns).
â—Ź Guide long-term interoperability strategy, including future phase HL7/FHIR enablement.
4. Design & Lead the Agent / Cloud Connectivity Strategy
Define and architect the “ Admin Agent” including:
â—ŹUnified last-mile connector for updates, telemetry, scripts, health checks, and data sync
â—ŹReal-time or near-real-time bidirectional sync mechanism
â—ŹSocket-based, event-based, or relay-based communication patterns
â—ŹReduction of multiple vendor-installed agents to a single secure agent
â—ŹHandling of PHI, encryption, and secure identity modeling
â—ŹAgent-managed writebacks into via API or controlled DB gateway
5. Partner Integration Architecture
â—ŹDesign how external partners (RCM, imaging, scheduling, etc.) integrate with client via:
â—‹REST API
â—‹Event-driven messaging
â—‹Cloud-based partner integration layer
â—‹The new vendor marketplace
â—ŹDefine versioning strategy, API evolution, and deprecation pathways.
â—ŹBuild a robust developer experience (Swagger, examples, validation rules).
â—ŹEnsure writebacks from partners are safe, validated, and performant.
6. Drive Quality Engineering, Test Coverage, and CI/CD Modernization
â—ŹArchitect test automation frameworks aligned with modernization (unit, service, API
contract, integration tests).
â—ŹDefine CI/CD pipelines compatible with multi-version on-prem deployments.
â—ŹIntroduce coverage gates, performance budgets, and security gateways (SAST/DAST).
â—ŹEnsure legacy areas (PowerBuilder, mixed C++/.NET codebase) are testable through seams and adapters.
7. Cross-Product Schema Alignment ( + + )
â—ŹLead design of a unified data model enabling cross-product analytics and platform interoperability.
●Leverage client’s existing conversion mapping logic to build a canonical schema.
â—ŹDefine domain-driven boundaries, patient/provider/entity definitions, and data normalization standards.
8. Technical Leadership & Mentorship
â—ŹLead senior engineers, data engineers, and API developers across all workstreams.
â—ŹAct as chief problem solver for hard technical constraints (legacy code, real-time sync, performance bottlenecks, security concerns).
â—ŹConduct architecture reviews, code reviews, and system design sessions.
●Mentor client engineers undergoing skill transitions (e.g., PowerBuilder → .NET, SQL
Anywhere → Postgres).
9. Security, Compliance & Interoperability by Design
â—ŹEnsure architectures support HIPAA, PHI encryption, auditing, and least-privilege access.
â—ŹImplement FHIR/HL7 readiness in future phases.
â—ŹDesign logging, tracing, and monitoring frameworks across all services.
Required Experience
Technical Expertise
â—Ź10+ years in architecture roles leading multi-system modernization or enterprise platform rebuilding.
â—Ź Deep expertise in:
○.NET Framework → .NET Core migration patterns
â—‹Service-oriented architecture and microservices
â—‹Legacy systems modernization (C++, PowerBuilder strongly preferred)
○SQL database migrations (SQL Anywhere → Postgres ideal)
â—‹REST API design and API lifecycle management
â—‹Event-driven architectures (Kafka, EventHub, socket communication)
â—‹Cloud data lakes (Azure preferred)
â—‹ETL/ELT pipelines, data normalization, and data governance
â—ŹExperience architecting integrations for vendor ecosystems or marketplaces.
â—ŹArchitectural experience with real-time data sync, agents, relays, or hybrid-cloud connectors.
Industry Expertise
(Not mandatory but strongly preferred)
â—ŹHealthcare / dental / medical software
â—ŹFamiliarity with PHI, HIPAA, HL7, and FHIR
●Experience with on-prem → cloud transition patterns
Soft Skills & Leadership
â—ŹAbility to collaborate closely with client leadership, engineering managers, product owners, and external vendors.
●Exceptional communication—able to simplify complex technical topics for executive audiences.
â—ŹSkilled in architectural decision-making and balancing pragmatism vs. ideal design.
â—ŹProven ability to lead modernization initiatives in environments with legacy code, missing documentation, and partial APIs.
â—ŹComfortable owning high-risk, high-visibility technical initiatives.
Required skills experience
| C# | 10 years |
| .NET | 10 years |
| REST API | 10 years |
Required languages
| English | C1 - Advanced |