\documentclass[11pt,a4paper,roman]{moderncv}
\usepackage[english]{babel}
\moderncvstyle{classic}
\moderncvcolor{green}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{lmodern}
\usepackage{ragged2e}
\usepackage[scale=0.79]{geometry}
\usepackage[version=4,arrows=pgf-filled]{mhchem}
\renewcommand*{\makeletterclosing}{\par\vspace{2ex}\closingname\par}

% ========== CONTACT ==========
\name{Dennis}{Thiessen}
\address{Bern, Switzerland}
\phone[mobile]{+41 795 955 585}
\email{dennis@thiessen.io}
% =============================

\begin{document}

\recipient{To}{Snowflake\\Observe Engineering, Enterprise Team\\Z\"urich, Switzerland}
\date{\today}
\opening{Dear Observe Engineering Team,}
\makelettertitle

\begin{justify}
When Snowflake announced its roughly \$1 billion agreement to acquire Observe in January, the architecture caught my eye before the price did: an AI SRE and a context graph sitting on a telemetry lakehouse built on Apache Iceberg. I have spent the last few years on both halves of that picture. At Robert Bosch's semiconductor fab I built an observability and anomaly-detection proof of concept on ELK, Kafka, Grafana, Prometheus and Loki, and at Swisscom I now own production data pipelines on an Iceberg lakehouse end to end. I'm writing about the Senior Software Engineer role on the Enterprise team.

At Swisscom, Switzerland's largest telco, I am Component Owner for the Fulfillment and Product Analysis pipelines: Oracle and Kafka ingestion into Teradata and, increasingly, an AWS lakehouse on S3, Glue and Athena with Apache Iceberg. I carry the on-call SLA and 3rd-level root-cause analysis for those flows, and I ship the Python backend services and APIs that move the data, running on Kubernetes through GitLab CI/CD. Java is my second language, from Bosch data services over Oracle and Impala back through earlier J2EE work. Building a telemetry pipeline and then operating production data systems under SLA is exactly what an observability backend asks for.

On the AI-assisted side I work day to day with LiteLLM as an LLM gateway and custom GPTs fed with domain knowledge, the same direction your AI SRE points. I'll be straight that my telemetry runs at telco and fab scale, not Observe's petabyte tier, but the hard parts are the ones I solve every week: ingestion, schema evolution, query performance and reliability under load. I'm based in Bern, so Z\"urich is a short commute. I'd welcome the chance to talk about where I could contribute on the Enterprise team.
\end{justify}

\vspace{0.3cm}
{Sincerely,\\
Dennis Thiessen, M.Eng.\\
Staff Data, Analytics \& AI Engineer\\
Swisscom (Schweiz) AG}

\end{document}
