What will I be doing?

1. Building and evolving the Feature Store

• Implement and maintain online and offline feature pipelines that feed our enterprise Feature Store, combining:

  • Flink‑based streaming jobs ingesting large volumes of events from multiple sources (payments, fraud, anomaly, etc.) into online stores.

  • Databricks / Spark pipelines for offline feature computation, backfills and training datasets.

  • Ensure:

    • Point‑in‑time correctness for offline training and backtesting.

    • Low‑latency, high‑throughput online feature serving with clear SLAs, TTL semantics and multi‑tenant safety.

    • Contribute to the feature catalog and specs:

      • Define entities, feature views, schemas, SLAs, PII classification and owners.

      • Help data scientists and domain teams onboard new features safely and consistently across Flink and Databricks.

      • Develop tooling for:

        • Backfills and materialization coordination between Flink and Databricks (Lakehouse / Delta).

        • Offline-online parity checks, data quality, drift and freshness monitoring for critical feature groups.

        • Unified feature retrieval APIs (online/offline/batch) and SDK/CLI usage from models and services.

        2. MLOps platform implementation (training, serving, observability)

        • Implement and improve training and evaluation pipelines:

          • Reproducible workflows, experiment tracking and model registry integration.

          • Promotion flows from dev → staging → production, following platform standards.

          • Work on online and batch inference paths:

            • Model packaging and deployment.

            • Rollout strategies (canary, shadow, rollback) aligned with SRE/Infra.

            • Instrument pipelines and services with metrics, logs and traces:

              • Integrate with our observability stack (e.g. OTel, Coralogix).

              • Expose dashboards and alerts for ML components (latency, errors, drift, freshness).

              3. AI‑assisted automation for MLOps and Feature Store

              • Integrate and extend agents and AI services (built by the AI Team and MLOps) to automate key parts of the Feature Store and MLOps workflows (health checks, drift and quality analysis, documentation/specs, incident triage, FinOps suggestions, etc.).

              • Design these automations with clear guardrails: observable, auditable and easy to roll back, always keeping humans in control of production decisions.

              4. Reliability, security and compliance in practice

              • Implement changes that respect platform standards around:

                • Access control, secrets management and PII handling in features and models.

                • Environment separation and change management for ML/AI components.

                • Participate in on‑call rotations or escalation paths for ML pipelines and feature infrastructure:

                  • Diagnose and fix incidents.

                  • Contribute improvements to playbooks, dashboards and tests.

                  5. Collaboration and technical contribution

                  • Work closely with:

                    • MLOps Technical Referent to align on architecture and technical direction.

                    • Data Science squads and the AI Team to understand requirements and unblock use cases.

                    • Fraud, Anomaly and other product squads as consumers of features and models.

                    • Contribute to internal documentation, RFCs, examples and onboarding guides so other engineers and data scientists can adopt the platform more easily.

                    • Mentor mid‑level engineers on good practices in pipelines, testing, observability and automation.