Files
claude-resume-kit/output/Isovalent_DataEngineer/session_isovalent_data_engineer.md
T
dennisthiessen b4b5e3fbe1 chore(resume): shelve Isovalent Data Engineer package (role pulled, ~86/100)
Finalized package retained for reuse; role closed (Cisco scrape 2026-06-02:
not on board, Recruitee link dead). PDFs/build artifacts gitignored.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-06 20:46:11 +02:00

17 KiB
Raw Blame History

Session: Isovalent (Cisco) — Senior Data Engineer, Observability

Status: Phase 0: DONE — awaiting user confirmation before Phase 1 Created: 2026-06-02 JD source: output/Isovalent_DataEngineer/JD_isovalent_data_engineer.txt Output folder: output/Isovalent_DataEngineer/

JD Info

  • Role: Senior Data Engineer, Observability
  • Company: Isovalent (creators of Cilium + eBPF; now part of Cisco)
  • Location: Mountain View, Zurich, or Remote → CH-based / Europe-remote, works from Bern. DIRECT match.
  • Bundle (primary): Staff / Senior Data Engineer (bundle_data_engineer.md)
  • Bundle (secondary): Data Platform / Infra (bundle_data_platform.md) — for K8s / cloud-native / distributed-systems bridge
  • Format: Resume (2-page, resume.cls) + 1-page cover letter
  • Salary/Details: Not posted. Cisco/Isovalent CH eng band ~CHF 180250k+ — clears comp bar.

JD Analysis

Requirements

# Requirement Match Evidence
1 M.Sc. CS or equivalent DIRECT M.Eng. Computer Aided Engineering (Software Design & Engineering), Univ. der Bundeswehr München
2 Remote teams + cross-functional collaboration DIRECT Swisscom Component Owner across Fulfillment + Product Analysis domains; Bosch App Owner; international career (DE/NO/CH)
3 Kubernetes, Cloud Native workloads, distributed systems DIRECT K8s at 2 employers (Swisscom + Bosch); AWS cloud-native data platform; Vizrt distributed video transcoding
4 Data pipelines, storage & analysis (the core of the role) DIRECT Swisscom Data Mesh / data products, Kafka pipelines, Teradata at scale; Bosch fab data
5 Go (desire to write efficient Go) BRIDGE (LOW-MED) Polyglot: Python + Java production; C++ systems at Vizrt. NO Go production yet — frame as "desire/aptitude", emphasize systems + perf mindset. Do NOT claim Go experience.
6 Robust APIs / gRPC BRIDGE (MED) Built/served production APIs; LiteLLM API gateway at Swisscom; REST services. gRPC specifically NOT confirmed — bridge as "API design", do not claim gRPC.
7 Strong SQL + query optimization for large datasets DIRECT Teradata + large-scale SQL pipelines at Swisscom; performance tuning on big analytics workloads
8 Large distributed columnar databases for analytics DIRECT (bridge to their stack) Teradata (MPP/columnar analytics); AWS Redshift/Athena; data-warehouse modelling
9 ClickHouse (plus) BRIDGE (HIGH) Columnar-analytics-DB experience directly transferable; frame "columnar analytics DBs (Teradata/Redshift; transferable to ClickHouse)"
10 Observability domain (Cilium/Tetragon/Hubble) BRIDGE (HIGH — strong) Bosch observability stack: ELK + Grafana + Prometheus + Loki; on-call SLA at Swisscom. Real observability-platform operator.

Net: 6 DIRECT, 3 strong bridges, 1 genuine gap (Go). One of the cleanest fits on the board — the role IS data engineering for an analytics/observability platform, which is Dennis's exact lane.

ATS Keywords

  • Core: data engineer, data pipelines, data platform, analytics, storage, query optimization
  • Cloud-native: Kubernetes, cloud native, distributed systems, containerized workloads
  • Data stores: SQL, columnar database, ClickHouse, data warehouse, MPP, large-scale datasets
  • APIs: API design, gRPC, services
  • Languages: Go (aspirational), Python, Java
  • Domain: observability, monitoring, security posture, eBPF, Cilium, Tetragon, telemetry
  • Soft: remote teams, cross-functional collaboration, ownership

Gap Assessment

  • Direct: education, K8s/cloud-native/distributed, data pipelines/storage/analysis, SQL + optimization, columnar analytics DBs, cross-functional/remote collaboration
  • Bridge: ClickHouse (HIGH — columnar DB transfer), observability domain (HIGH — Bosch stack), APIs/gRPC (MED — API design without gRPC claim)
  • Gap (do NOT claim): Go production experience (frame as aptitude/desire only); gRPC specifically (say "API design", not "gRPC")

Company Context

  • Mission: Isovalent (Cilium/eBPF creators, now Cisco) builds cloud-native networking, security & observability on eBPF. The observability stack = Hubble (network observability for Cilium) + Tetragon (runtime security observability), with data pipelines/storage/analysis behind them.
  • This role: Build the data backbone behind that observability — ingest high-volume eBPF telemetry, store it in columnar analytics DBs (ClickHouse-class), and build analysis that assesses customer security posture and surfaces recommendations. Success = scalable pipelines + fast analytical queries over very large telemetry datasets.
  • Culture: Open-source-first (Cilium is CNCF graduated), deeply technical, remote-friendly distributed eng org, Zurich is a real eng hub (Thomas Graf / founding team CH-based).
  • "Why them" angle: Dennis operated observability stacks (Grafana/Prometheus/Loki/ELK) as a user in a 24/7 Bosch fab and built large-scale data pipelines/products at Swisscom — this role is building the platform side of exactly what he ran. Plus cloud-native (K8s) + columnar-analytics-DB depth. Authentic, not a stretch.

Framing Strategy

  • Lead narrative: Senior data engineer who builds large-scale, cloud-native data platforms — pipelines, columnar analytics stores, and the SQL/query-optimization layer — and who has operated production observability stacks firsthand.
  • Reframing map:
    • Data Mesh / data products → "cloud-native data platform / analytics pipelines"
    • Teradata / Redshift → "large distributed columnar analytics databases (transferable to ClickHouse)"
    • ELK/Grafana/Prometheus/Loki (operator) → "observability telemetry at scale"
    • Kafka pipelines → "high-throughput data ingestion pipelines"
    • SQL tuning → "query optimization over large datasets"
  • Emphasize: K8s/cloud-native, data pipelines + storage + analysis, SQL/query optimization, columnar analytics DBs, observability domain credibility, distributed systems
  • Downplay: GenAI/agentic content (off-thesis here), pure DevOps/IaC unless it supports the platform story, C++ overselling (per memory)
  • CL hooks: Cilium/Hubble/Tetragon observability data pipeline; running Grafana/Prometheus/Loki/ELK in a 24/7 fab; eBPF telemetry → columnar analytics; Cisco/Isovalent open-source ethos
  • User directives: No Go fabrication (gap). No gRPC claim (bridge as API design). Don't oversell C++ (memory). Honesty per anti-fabrication rules.

Critique Context

  • Reviewer persona: Isovalent/Cilium senior eng or eng manager — deeply technical, open-source-native, allergic to buzzword padding. Cares about real distributed-systems + data-at-scale chops, not titles. Will respect honest "I've run observability stacks, here's the data-platform work I've shipped."
  • Competitive landscape: Backend/data engineers from observability vendors (Datadog, Grafana Labs, Elastic) and cloud-native shops with Go + ClickHouse on their CV. Dennis's edge: operated the observability tools in a high-stakes 24/7 setting + broad data-platform ownership; his risk: no Go, no named ClickHouse.
  • Domain vocabulary: eBPF, Cilium, Hubble, Tetragon, CNCF, columnar OLAP, ClickHouse, cardinality, telemetry ingestion, Kubernetes operators, gRPC.

Cover Letter Plan

  • Institution type: Industry (open-source-rooted, cloud-native)
  • Paragraph count: 34 paragraphs, 250300 words (1 page)
  • P1 hook: Reference Cilium/eBPF observability (Hubble/Tetragon) + the data-pipeline-behind-the-telemetry framing; connect to having operated Grafana/Prometheus/Loki/ELK in production.
  • P2P3 evidence: Swisscom large-scale data pipelines/products + SQL/query optimization on big analytics workloads; K8s/cloud-native; columnar analytics DB depth (transferable to ClickHouse).
  • Domain pivot: "Operated observability at scale; eager to build the data platform that powers it" + honest Go-aptitude note (systems/perf mindset).
  • Jargon level: Technical (insiders read it)
  • "Why them" hook: Cisco/Isovalent open-source ethos + CH eng hub + the exact platform/data overlap.

Bullet Plan (Phase 1 — CONFIRMED 2026-06-02; generate 17: SW-2/1/7/3/6/4, BS-4/2/1/3, FC-3/1/2, VZ-1/2, GN-1/3)

Position title themes (FLIPPED format — bold theme + role subtitle):

  • Swisscom: Cloud-Native Data Platform, Pipelines & Observability at Telecom Scale
  • Bosch: Observability, Production ML & Data Services in 24/7 Semiconductor Manufacturing
  • Fraunhofer: Microservice Engineering & Applied Data Research
  • Vizrt: Distributed Real-Time Backend Engineering at Broadcast Scale
  • Generali: Test Automation, CI/CD & Java Backend

Swisscom (5 bullets) — Staff Data, Analytics & AI Engineer, Oct 2023Present

* ID Achievement Variant JD Match
* SW-2 Component Owner — Fulfillment+Product Analysis ETL (Oracle/Kafka→Teradata, Python); governance, on-call SLA 2L Direct (pipelines/storage)
* SW-1 AWS migration (S3, Glue, Athena/Iceberg, Redshift columnar, Airflow, CloudFormation) 2L Direct (cloud-native + columnar DB)
* SW-7 Data Mesh, data products & metadata management on AWS — governed, discoverable data platform 2L Direct (data platform/storage+analysis)
* SW-3 Python data services on Kubernetes + GitLab CI/CD, containerized delivery 2L Direct (K8s/cloud-native)
* SW-6 PySpark distributed processing over large datasets in the Data Lake 2L Direct (distributed/large-data + SQL)
x SW-GenAI custom GPTs / LiteLLM agent assistants -- OFF-THESIS here — omit
o SW-4 B2B data products + process automation 2L Available (page-fill option)

Bosch (4 bullets) — (Senior) Data Engineer, Feb 2020Dec 2022

* ID Achievement Variant JD Match
* BS-4 Observability stack: ELK + Kafka + Grafana/Prometheus/Loki, centralized monitoring/telemetry for 24/7 production 2L Bridge HIGH (observability domain — key hook)
* BS-2 Data services over OracleDB + Hadoop/ImpalaSQL; query optimization for large analytics datasets 2L Direct (SQL/query-opt + columnar-ish)
* BS-1 Containerized ML inference (Docker/K8s/Ansible) into 24/7 fab 2L Direct (K8s/distributed infra)
* BS-3 Application Owner — SLOs, vendor mgmt, cross-functional adoption 2L Direct (ownership + cross-functional)

Fraunhofer (23 bullets) — Research Software Engineer, Sep 2018Oct 2019

* ID Achievement Variant JD Match
* FC-3 Microservices (Express.js, Docker, REST APIs, SQLite) for MISSION data-exchange platform 2L Bridge MED (API design — gRPC proxy)
* FC-1 Independently set up Jenkins CI/CD with quality gates; SCEDAS DSS (C#/.NET/SQL) 2L Bridge (CI/CD initiative)
o FC-2 ARTUS ML/NLP sea-rescue transcription (hedged: "Contributed") 2L Available (ML breadth; off core thesis)

Vizrt (2 bullets) — DevOps Engineer, Jul 2017May 2018

* ID Achievement Variant JD Match
* VZ-1 Distributed real-time video transcoding backend (Python, legacy C++); CNN/BBC/Al Jazeera 2L Direct (distributed systems)
* VZ-2 Automated A/V test suite (Python) + CI/CD quality gates 2L Bridge (CI/CD)

Generali (2 bullets) — IT Consultant, May 2015Jun 2017 (Hamburg — KB corrected)

* ID Achievement Variant JD Match
* GN-1 Introduced BDD test automation; technical ownership + team training 2L Weak (initiative signal)
o GN-3 Java/J2EE features; XLDeploy; Apache Camel/Spring Boot PoC 2L Available (page-fill)

Recommended set: 5 + 4 + 2 + 2 + 1 = 14 core, expandable to 17 with o options (SW-4, FC-2, GN-3) for page fill. Go handling: NOT in any bullet (no fabrication). Go aptitude lives in Summary tagline + Skills only ("polyglot; Python/Java/C++; learning Go"). Security Champion (SW-5): omitted — JD's "security posture" is about the product, not the engineer; and per KB it's 2025/26 team role only, not an award.

Output Files

  • Resume: output/Isovalent_DataEngineer/e2e_isovalent_data_engineer_resume.tex
  • Cover Letter: output/Isovalent_DataEngineer/e2e_isovalent_data_engineer_cover_letter.tex
  • Critique: output/Isovalent_DataEngineer/critique_isovalent_data_engineer.md

Status

  • Phase 0: DONE
  • Phase 1: DONE (19 bullets confirmed: SW-2/1/7/3/6/4/5, BS-4/2/1/3, FC-3/1/2, VZ-1/2, GN-1/2/3)
  • Phase 2 Resume:
    • Summary: DONE
    • Skills: DONE (5 groups 4-3-2-2-2, retuned for data-eng/observability/columnar; crypto+agentic dropped)
    • All positions: DONE
    • Compile: DONE (2 pages; page 2 ~70% full — strong set, not padded)
  • Cover Letter: DONE (1 page, ~302 words, industry 4-para; compiled clean via MiKTeX)
  • Critique: CURRENT — 84.5/100 (2026-06-02); Tier 1 fixes applied 2026-06-02 → est. ~86/100
    • ✓ Bullet 3 reframed: "Built governed data products ... within Swisscom's company-wide Data Mesh" (no longer claims building the Mesh)
    • ✓ Summary scoped: "I build and own cloud-native data pipelines and products on ... telco's AWS platform"
    • ⚠ Still verify "currently learning Go" is literally true before sending
    • Recompiled clean (2pp), char counts OK (bullet 3 = 204)
  • FINALIZED 2026-06-02 — submission PDFs: Dennis_Thiessen_Resume.pdf, Dennis_Thiessen_Cover_Letter.pdf (~86/100). Reminder before sending: confirm "currently learning Go" is literally true.
  • 🔴 ROLE PULLED — CONFIRMED CLOSED (2026-06-02): Verified via live headless-browser scrape (job_scout .venv Playwright, keywords=Isovalent on careers.cisco.com). 10 live Isovalent/Cilium CH roles returned; "Senior Data Engineer, Observability" is NOT among them. Original Recruitee apply link also dead (→ recruitee.com/careers_not_hosted). Two independent signals = role closed/pulled.
  • Remaining live Isovalent roles are off-lane: Tetragon kernel/Linux-security eng + EMs, eBPF Agent/Datapath SWE, "Senior SWE Go — WAF" (Go-first), Dev-Experience SWE. All are low-level systems/Go/management — opposite Dennis's data-platform lane (per user_positioning). None worth retargeting this package to.
  • DISPOSITION: SHELVED. Finalized PDFs (Dennis_Thiessen_Resume.pdf / _Cover_Letter.pdf, ~86/100) kept as a reusable data-eng/observability package for the next live req. Natural next targets from scout: QuantCo, Grafana Labs, Confluent.

Critique Summary (2026-06-02 — score 84.5/100)

  • Verdict: Strong, submit-ready after 2 accuracy tightenings. One of the cleanest fits on the board (role IS data-eng for an observability/analytics platform). ATS ~85%, HM = INTERVIEW, ceiling ~8889 (capped by no production Go / no named ClickHouse).
  • Tier 1 (accuracy — do these):
    1. Bullet 3 "Built a decentralized Data Mesh" overclaims sole ownership of a company-wide platform → reframe to own the data products/modelling/onboarding within Swisscom's company-wide Data Mesh (per KB Data-Mesh ownership rule). +1.0
    2. Summary "I own ... the cloud-native data platform" too broad → scope to pipelines/products/domains (CL is already better-scoped; align summary to it). +0.5
    3. Verify "currently learning Go" is literally true before sending (blocking gate, not score).
  • Tier 2 (optional): Bosch position-title header wraps the date to a 2nd line — shorten title (+0.3); reconsider Security Champion bullet SW-7 (weakest, but mildly on-thesis since JD = "security posture" — defensible to keep); "high-volume batch" → "high-throughput ingestion" vocab swap.
  • Tier 3 (skip): vary ~8 trailing -ing participial-clause bullet endings; "AWS Solutions Architect" → "AWS Certified Solutions Architect".
  • AI fingerprint: PASS (0 em-dashes, no banned words/phrases). Compile: both clean via MiKTeX, resume 2pp / CL 1pp.
  • Accuracy verified clean: Generali=Hamburg, Bosch=Dresden, edu dates KB-correct, German/English only, no gRPC/Go fabrication, C++ downplayed, no LangChain.

CL Hook Verification (2026-06-02 — all VERIFIED)

  • Cilium = eBPF data plane, CNCF-graduated (Oct 2023) → confirmed
  • Hubble = Cilium network observability; Tetragon = runtime/network security observability built on Cilium/Hubble → confirmed
  • Isovalent acquired by Cisco (announced Dec 2023, closed 2024) → confirmed
  • Founding team (CTO Thomas Graf) Zurich-based; Isovalent HQ Cupertino + Zurich → confirmed CH eng hub
  • Sources: cisco blogs, sdxcentral, isovalent.com/about-us, theregister

Generation notes / accuracy flags

  • "currently learning Go" in summary + "Go (learning)" in skills: per user's confirmed honest-polyglot framing. VERIFY this is actually true before submitting (or start a Go tutorial first).
  • Go appears in NO bullet (no fabrication). gRPC NOT claimed (skills say "REST APIs ... OpenAPI" only).
  • "ClickHouse-class columnar analytics (transferable from Teradata/Redshift/Impala)" — framed as transferable, not claimed experience.
  • Education dates corrected to KB-verified (B.Eng Oct 2009Oct 2012, M.Eng Apr 2012Oct 2013). NOTE: the sent Kraken resume has WRONG dates (20072010 / 20102013).
  • Generali location = Hamburg (KB-corrected). Security Champion = 2025/26 team role, not award.