Role Summary

As a Principal Software Engineer, you will lead the design and evolution of the core ingestion, normalization, and integration capabilities that power ECOLAB3D. You will own architectural strategy for multicloud data pipelines, external partner integrations, high‑volume measurement data ingestion, and microservice‑based platform components.
 

Key Responsibilities

1. Architecture & Platform Leadership

• Own the architecture for multiple initiatives, including token‑based authentication using service principals, universal JSON schema ingestion, and multi‑system API routing patterns.
• Design scalable ingestion pipelines leveraging Kafka, RabbitMQ, Elasticsearch, MongoDB, and platform microservices.
• Shape the “North Star” architecture for platform‑wide data transformation, normalization, and standardization across diverse partner formats.

2. External API & Integration Ownership

• Lead design and evolution of customer‑facing APIs
• Define integration patterns for partners sending high‑volume measurement data via universal JSON format, handling validation, error categorization, dead‑letter routing, and metadata enrichment.
• Drive the creation of connectors and integration accelerators for diverse customer ecosystems (e.g., Snowflake, CloudHub, Mulesoft proxies).

3. Data Modeling, Schema Governance & Observability

• Establish schema governance for Universal JSON, asset hierarchies, measurement types, category definitions, and spans (as discussed in integration sessions).
• Define and implement platform‑wide metrics and observability standards for ingestion, normalization, and downstream data processing.

4. Technical Leadership & Mentorship

• Provide architectural guidance and hands‑on mentorship to engineers contributing to External Ingress, Egress, Device Management, and Data IE microservices.
  (Teams discussions reference ongoing work in ExternalIngress & ExternalEgress services.)
• Lead critical design evolution and reviews, API contract reviews, integration pattern decisions, and code quality initiatives across platform teams.

5. Collaboration & Cross‑Functional Alignment

• Work closely with Product, Data Engineering, Solution Architects, and business stakeholders to map data needs to scalable platform capabilities.
• Engage with engineering leadership on roadmap planning, integration strategy, and evaluation of third‑party tools for normalization and connectors.

Required Technical Skills

• Expertise in distributed systems and event‑driven architectures (Kafka, RabbitMQ).
• Strong experience in API design, OAuth/SPN authentication flows, and secure partner integrations.
• Deep knowledge of data ingestion pipelines, transformation frameworks, and schema‑driven processing.
• Hands‑on cloud experience (Azure) and microservices architecture (as referenced in E3D platform services).

Preferred Qualifications

• Experience building integration accelerators or connector frameworks to support heterogeneous customer ecosystems.
• Familiarity with high‑volume IoT/measurement data flows.