\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}{QuantCo\\Engineering Team\\Z\"urich, Switzerland}
\date{\today}
\opening{Dear QuantCo Engineering Team,}
\makelettertitle

\begin{justify}
QuantCo is expanding the AWS and Kubernetes platform that already runs your customers' production pricing and claims systems, and your engineering blog sets a clear bar: open-source tooling with sensible defaults, like datajudge for testing database data inside pytest. That is the work I do now. As Staff Data, Analytics \& AI Engineer at Swisscom, Switzerland's largest telecom, I build and run the AWS data platform our business-critical pipelines depend on, and I'd bring that same builder-operator habit to your Cloud Engineer role in Z\"urich.

The throughline of my work is owning infrastructure end to end. At Swisscom I migrated a legacy Teradata and Oracle ETL estate to a cloud-native AWS stack (S3, Glue, Athena on Iceberg, Redshift, Airflow), provisioned as code with CloudFormation. I also helped build the company-wide Data Mesh that product teams now query directly: governed data products with metadata, shipped through GitLab CI/CD. I deploy and run our Python applications on Kubernetes, and I hold 2nd- and 3rd-level on-call for the pipelines, so reliability is not abstract to me. Earlier, in Bosch's 24/7 semiconductor fab in Dresden, I containerized ML defect-classification inference with Docker, Kubernetes, and Ansible into a line with no maintenance window, where a bad deploy costs wafer yield.

What draws me to QuantCo is the pairing: high-stakes enterprise production, where a pricing or claims error is expensive, alongside a small engineering-led team that open-sources its tools and argues about defaults. I'm AWS Solutions Architect certified, Bern-based, and glad to be in Z\"urich on a hybrid schedule. Where I'm most useful is the messy middle, running a platform while it scales to new services and clusters. I'd welcome the chance to talk about where you want to take the platform next.
\end{justify}

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

\end{document}
