feat(app): Swisscom Data Engineer - Geo Platform (internal, R-0006447), submitted
Internal application, submitted 2026-09-15. Evidence Fit 78, hard gate FAIL (ArcGIS and FME required, never used), overridden by the user. Document Quality 89, no Tier 1 findings. Channel Moderate: hiring manager Marianne Temerowski was contacted first and encouraged the application - the first time a named contact was used before applying. 2-page English resume, no cover letter (internal). KB CORRECTIONS FOUND ON THE WAY - BS-8: geospatial work at Bosch (Oracle SDO_GEOMETRY; normalizing and transforming wafer data across coordinate reference systems; performance tuning) was missing from claims.json. The first assessment also wrongly assumed wafer data carries no CRS; the user corrected it. ArcGIS, FME, QGIS, PostGIS, GeoServer and GDAL are registered as forbidden. - Swisscom was recorded as one undifferentiated current role. It is two units: ART B2B (past - Teradata DWH component ownership, Kubernetes, GitLab CI/CD, Kafka) and ART DPT, Team Offering (current - AWS data products with ODP-Flow, PySpark/Python, Glue, Iceberg, Athena, Airflow). The first build wrote the B2B ownership in present tense. Kafka and Kubernetes are now production-historical. Official internal title recorded (Engineer IV, III before Apr 2025); the unit switch date deliberately not. - Confirmed: SW-1 migration in Python Glue jobs with ODP-Flow; SW-3 multi-environment deployments; SW-7 relational data models. SW-3 narrowed: he worked with automated GitLab CI/CD and did not build it. - Skills added: Apache Iceberg, relational data modelling, ODP-Flow, Oracle SDO_GEOMETRY, coordinate system transformation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
dennisthiessenandClaude Opus 5 committed
1 parent
34299bce54
commit
881d904e68
12 files changed
+749
-23
No files matched your search
@@ -86,7 +86,34 @@
|
||||
"start": "2025-04",
|
||||
"end": "present"
|
||||
}
|
||||
]
|
||||
],
|
||||
"official_title": "Data, Analytics & AI Engineer IV",
|
||||
"official_title_source": "Swisscom Zwischenzeugnis Okt 2025 ('Data, Analytics & AI Engineer IV'); user-confirmed 2026-09-15, including that the grade before the Apr 2025 promotion was III. Use the official title on INTERNAL Swisscom applications; display_title ('Staff ...') remains the external rendering.",
|
||||
"internal_title_history": [
|
||||
{
|
||||
"title": "Data, Analytics & AI Engineer III",
|
||||
"start": "2023-10",
|
||||
"end": "2025-04"
|
||||
},
|
||||
{
|
||||
"title": "Data, Analytics & AI Engineer IV",
|
||||
"start": "2025-04",
|
||||
"end": "present"
|
||||
}
|
||||
],
|
||||
"org_history": [
|
||||
{
|
||||
"unit": "ART B2B",
|
||||
"phase": "first part of the Swisscom tenure - PAST",
|
||||
"scope": "Legacy Teradata DWH: component ownership of the Fulfillment ETL (SW-2), Python applications on Kubernetes with GitLab CI/CD (SW-3), dashboards and analyses (SW-4), Kafka."
|
||||
},
|
||||
{
|
||||
"unit": "ART DPT, Team Offering",
|
||||
"phase": "current",
|
||||
"scope": "Migration and implementation of the new AWS-based data products (SW-1, SW-6, SW-7). Stack, user-confirmed 2026-09-15: AWS, ODP-Flow, PySpark/Python, Glue, Iceberg, Athena, Airflow. The Offering domain also covers Fulfillment and Product data; the user does not want that detail on documents."
|
||||
}
|
||||
],
|
||||
"org_history_note": "User-supplied 2026-09-15. The switch date between the units is NOT recorded and the user ruled it not relevant: never put dates on the two units. Unit names 'ART B2B' and 'ART DPT' (ART is the SAFe term; user-confirmed 2026-09-15 that 'ART' and 'Art' are both acceptable). The Zwischenzeugnis lists duties from both units as one undifferentiated list; it is not evidence that any of them is current."
|
||||
},
|
||||
{
|
||||
"id": "BOSCH",
|
||||
@@ -178,7 +205,7 @@
|
||||
"source": "Swisscom Zwischenzeugnis, Oktober 2025 (primary document, read 2026-09-11)",
|
||||
"ownership": "individual within his domains; contributor company-wide"
|
||||
},
|
||||
"scope": "Migration of legacy ETL pipelines and build-and-operate of cloud-native applications on AMAZON AWS (S3, Glue, Athena, Redshift, Apache Airflow) - verbatim from the Zwischenzeugnis. Primary engineer for pipelines in his owned Fulfillment and Product Analysis domains; contributor to the wider company migration.",
|
||||
"scope": "Migration of legacy ETL pipelines and build-and-operate of cloud-native applications on AMAZON AWS (S3, Glue, Athena, Redshift, Apache Airflow) - verbatim from the Zwischenzeugnis. Primary engineer for pipelines in his owned Fulfillment and Product Analysis domains; contributor to the wider company migration. IMPLEMENTATION, user-confirmed 2026-09-15: the migration and its automation were written in PYTHON as AWS GLUE JOBS, together with ODP-FLOW, Swisscom's internal framework for creating data products. ODP-Flow is Swisscom's framework, not his - he uses it; never claim he built or owns it. PHASE, user-confirmed 2026-09-15: this is CURRENT work at ART DPT, Team Offering, on AWS, ODP-Flow, PySpark/Python, Glue, Iceberg, Athena and Airflow.",
|
||||
"allowed_verbs": [
|
||||
"migrated",
|
||||
"implemented",
|
||||
@@ -198,12 +225,12 @@
|
||||
"source": "Swisscom Zwischenzeugnis, Oktober 2025 (primary document, read 2026-09-11)",
|
||||
"ownership": "component - Komponentenverantwortung, documented"
|
||||
},
|
||||
"scope": "Komponentenverantwortung (component ownership) for the ETL pipelines that move business-critical Fulfillment data out of Oracle databases into the TERADATA DATA WAREHOUSE (DWH) and make it available for analysis - verbatim from the Zwischenzeugnis. Includes quality, security, data protection and compliance per Security and Data Governance, root-cause analysis on application problems, and 2nd/3rd-level support plus on-call (Rufbereitschaft).",
|
||||
"scope": "Komponentenverantwortung (component ownership) for the ETL pipelines that move business-critical Fulfillment data out of Oracle databases into the TERADATA DATA WAREHOUSE (DWH) and make it available for analysis - verbatim from the Zwischenzeugnis. Includes quality, security, data protection and compliance per Security and Data Governance, root-cause analysis on application problems, and 2nd/3rd-level support plus on-call (Rufbereitschaft). PHASE, user-confirmed 2026-09-15: this was the legacy DWH at ART B2B, the first part of his Swisscom tenure - it is PAST. Write it in past tense ('Owned', 'operated'); never 'own' or 'owns'.",
|
||||
"allowed_verbs": [
|
||||
"own",
|
||||
"operate",
|
||||
"maintain",
|
||||
"serve"
|
||||
"owned",
|
||||
"operated",
|
||||
"maintained",
|
||||
"served"
|
||||
],
|
||||
"metrics": "unverified"
|
||||
},
|
||||
@@ -213,11 +240,15 @@
|
||||
"source": "Swisscom Zwischenzeugnis, Oktober 2025 (primary document, read 2026-09-11)",
|
||||
"ownership": "individual - implementation and operation"
|
||||
},
|
||||
"scope": "Implementation, administration and operation of Python applications on KUBERNETES CLUSTERS, and automation of CI/CD processes in GITLAB - verbatim from the Zwischenzeugnis. Also drives automation of technical processes and workflows, and shapes and prioritises backlog items with the Product Owner.",
|
||||
"scope": "Implementation, administration and operation of Python applications on KUBERNETES CLUSTERS, and automation of CI/CD processes in GITLAB - verbatim from the Zwischenzeugnis. Also drives automation of technical processes and workflows, and shapes and prioritises backlog items with the Product Owner. User-confirmed 2026-09-15: the GitLab CI/CD pipelines deploy across MULTIPLE ENVIRONMENTS (he answered yes to dev/test/prod; exact environment names are not recorded - write 'multiple environments'). PHASE, user-confirmed 2026-09-15: Kubernetes and GitLab CI/CD belonged to the legacy B2B system at ART B2B - PAST; the current ART DPT stack is AWS-native. Write in past tense. SCOPE, user-clarified 2026-09-15: he WORKED WITH automated GitLab CI/CD pipelines - he did not build or design the CI/CD automation. The Zwischenzeugnis wording 'automation of CI/CD processes in GitLab' overstates his part; write 'deployed through automated GitLab CI/CD pipelines'.",
|
||||
"allowed_verbs": [
|
||||
"build",
|
||||
"deploy",
|
||||
"operate"
|
||||
"built",
|
||||
"deployed",
|
||||
"operated"
|
||||
],
|
||||
"forbidden": [
|
||||
"built the CI/CD automation",
|
||||
"designed the CI/CD pipelines"
|
||||
],
|
||||
"metrics": "unverified"
|
||||
},
|
||||
@@ -227,12 +258,12 @@
|
||||
"source": "Swisscom Zwischenzeugnis, Oktober 2025 (primary document, read 2026-09-11)",
|
||||
"ownership": "individual"
|
||||
},
|
||||
"scope": "Deliver data products, dashboards and analyses with internal B2B stakeholders and product owners; not external consulting or strategic-account delivery.",
|
||||
"scope": "Deliver data products, dashboards and analyses with internal B2B stakeholders and product owners; not external consulting or strategic-account delivery. PHASE, user-confirmed 2026-09-15: ART B2B, legacy system - PAST; write in past tense.",
|
||||
"allowed_verbs": [
|
||||
"deliver",
|
||||
"translate",
|
||||
"partner",
|
||||
"support"
|
||||
"delivered",
|
||||
"translated",
|
||||
"partnered",
|
||||
"supported"
|
||||
],
|
||||
"forbidden": [
|
||||
"customer-embedded delivery",
|
||||
@@ -265,7 +296,7 @@
|
||||
"source": "user confirmation 2026-09-11",
|
||||
"ownership": "individual - hands-on use"
|
||||
},
|
||||
"scope": "Hands-on PySpark use at Swisscom (user-confirmed 2026-09-11).",
|
||||
"scope": "Hands-on PySpark use at Swisscom (user-confirmed 2026-09-11). PHASE, user-confirmed 2026-09-15: current, at ART DPT, Team Offering.",
|
||||
"allowed_verbs": [
|
||||
"use",
|
||||
"develop",
|
||||
@@ -279,7 +310,7 @@
|
||||
"source": "unrecorded",
|
||||
"ownership": "unrecorded"
|
||||
},
|
||||
"scope": "Build governed data products and onboard sources within Swisscom's company-wide Data Mesh; never claim ownership or construction of the shared mesh/platform. Atlassian Compass is the metadata/catalogue platform used for data-product metadata and lineage (user-confirmed 2026-07-29); Dennis uses it as a practitioner and does not administer or own the tooling.",
|
||||
"scope": "Build governed data products and onboard sources within Swisscom's company-wide Data Mesh; never claim ownership or construction of the shared mesh/platform. Atlassian Compass is the metadata/catalogue platform used for data-product metadata and lineage (user-confirmed 2026-07-29); Dennis uses it as a practitioner and does not administer or own the tooling. User-confirmed 2026-09-15: the data-product modelling is RELATIONAL - logical and physical table models. Data products are created with ODP-Flow, Swisscom's internal data-product framework (see SW-1); he uses the framework and did not build it. PHASE, user-confirmed 2026-09-15: current work at ART DPT, Team Offering.",
|
||||
"allowed_verbs": [
|
||||
"build",
|
||||
"model",
|
||||
@@ -296,7 +327,10 @@
|
||||
"own the data platform",
|
||||
"own Atlassian Compass",
|
||||
"administered Compass",
|
||||
"rolled out Compass"
|
||||
"rolled out Compass",
|
||||
"developed ODP-Flow",
|
||||
"own ODP-Flow",
|
||||
"built the ODP-Flow framework"
|
||||
],
|
||||
"metrics": "unverified"
|
||||
},
|
||||
@@ -657,6 +691,27 @@
|
||||
"taught a course"
|
||||
],
|
||||
"metrics": "one Bachelor thesis as Zweitpruefer/supervisor is confirmed; the wider number of students supervised is unverified"
|
||||
},
|
||||
{
|
||||
"id": "BS-8",
|
||||
"evidence": {
|
||||
"source": "user confirmation 2026-09-15; partly corroborated by the TAF 2022 co-presentation 'Understanding Spatial Variability in Semiconductor Products with Spotfire Map Charts' (experience_bosch.md, BS-5)",
|
||||
"ownership": "individual - hands-on work inside the Bosch data-analysis team"
|
||||
},
|
||||
"scope": "Worked extensively with GEOSPATIAL DATA at Bosch (2020-2022) to visualize, locate and analyze wafer data, using TIBCO Spotfire and Oracle databases with Oracle's SDO_GEOMETRY spatial data type (user-confirmed 2026-09-15). The tools and systems involved used DIFFERENT COORDINATE REFERENCE SYSTEMS; normalizing the data and transforming it from one coordinate system to another was, in the user's words, probably the biggest pain point of the work, with PERFORMANCE TUNING the other. Pairs with BS-5, which covers the Spotfire map-chart side and the TAF 2022 talk. CORRECTION RECORDED 2026-09-15: the first assessment of the Swisscom Geo Platform posting asserted that wafer coordinates carry no coordinate reference system; the user corrected it the same day - CRS normalization and transformation was the central difficulty of this work, not an absent one. LIMITS: the coordinate systems were those of fab tools and systems for WAFER data. Geographic and geodetic specifics - datums, ellipsoids, map projections, EPSG codes, Swiss LV95/LV03 - are NOT established; ask before writing any of them. SDO_GEOMETRY is confirmed; specific spatial operators and spatial indexes were not separately confirmed. User-confirmed 2026-09-15 that he has NEVER used ArcGIS, FME, QGIS, PostGIS, GeoServer or GDAL, nor shapefile/GeoJSON/GeoTIFF or swisstopo data. DOCUMENT WORDING, user-approved 2026-09-15: for geo/GIS audiences write SPATIAL wafer data, not geospatial - wafer coordinates are not Earth-referenced, and a Geomatik reader takes 'geospatial' to mean they are.",
|
||||
"allowed_verbs": [
|
||||
"worked with",
|
||||
"normalized",
|
||||
"transformed",
|
||||
"analyzed",
|
||||
"visualized",
|
||||
"tuned"
|
||||
],
|
||||
"forbidden": [
|
||||
"GIS specialist",
|
||||
"geodetic datum transformation"
|
||||
],
|
||||
"metrics": "none verified; no query-performance or data-volume figures exist"
|
||||
}
|
||||
],
|
||||
"skills": [
|
||||
@@ -677,14 +732,21 @@
|
||||
},
|
||||
{
|
||||
"name": "Kafka",
|
||||
"evidence": "production-current",
|
||||
"output": "allowed"
|
||||
"evidence": "production-historical",
|
||||
"output": "allowed",
|
||||
"note": "Downgraded from production-current 2026-09-15: at Swisscom, Kafka belonged to the legacy B2B system (ART B2B), not the current ART DPT AWS stack. Still genuine production evidence - just not current."
|
||||
},
|
||||
{
|
||||
"name": "Airflow",
|
||||
"evidence": "production-current",
|
||||
"output": "allowed"
|
||||
},
|
||||
{
|
||||
"name": "Apache Iceberg",
|
||||
"evidence": "production-current",
|
||||
"output": "allowed",
|
||||
"note": "User-confirmed 2026-09-15 as part of the current ART DPT stack (AWS, ODP-Flow, PySpark/Python, Glue, Iceberg, Athena, Airflow). Previously appeared only in experience_swisscom.md and skills_taxonomy.md, not as a canonical skill."
|
||||
},
|
||||
{
|
||||
"name": "AWS",
|
||||
"evidence": "production-current",
|
||||
@@ -701,10 +763,24 @@
|
||||
"output": "allowed",
|
||||
"note": "Metadata/catalogue platform for data-product metadata and lineage at Swisscom (user-confirmed 2026-07-29). Practitioner use only — do not claim administration, rollout or ownership. Satisfies 'or similar metadata/catalogue platform' phrasing; is NOT a substitute claim for Purview, Collibra or Alation, which remain unevidenced."
|
||||
},
|
||||
{
|
||||
"name": "relational data modelling",
|
||||
"evidence": "production-current",
|
||||
"output": "allowed",
|
||||
"note": "User-confirmed 2026-09-15: logical and physical relational (table) models for data products at Swisscom (SW-7), alongside component ownership of the ETL into the Teradata DWH (SW-2). Previously only implied by SW-7's verb 'model'."
|
||||
},
|
||||
{
|
||||
"name": "ODP-Flow",
|
||||
"evidence": "production-current",
|
||||
"output": "allowed-with-context",
|
||||
"context": "Swisscom-internal framework for creating data products, used in the migration (SW-1) and in data-product work (SW-7).",
|
||||
"note": "User-supplied 2026-09-15. An internal name that only Swisscom readers recognise - always pair it with the descriptor 'Swisscom's internal data-product framework', and omit it for external employers unless explained. He USES it; never claim he built, designed or owns it."
|
||||
},
|
||||
{
|
||||
"name": "Kubernetes",
|
||||
"evidence": "production-current-and-historical",
|
||||
"output": "allowed"
|
||||
"evidence": "production-historical",
|
||||
"output": "allowed",
|
||||
"note": "Downgraded from production-current-and-historical 2026-09-15: at Swisscom, Kubernetes (with GitLab CI/CD) belonged to the legacy B2B system at ART B2B, and Bosch ended 2022. The current ART DPT stack is AWS-native. Never present Kubernetes as current work."
|
||||
},
|
||||
{
|
||||
"name": "Ansible",
|
||||
@@ -948,6 +1024,56 @@
|
||||
"output": "allowed-with-context",
|
||||
"context": "Generali 2015-2017 (GN-3): migrated web services onto a new deployment procedure.",
|
||||
"note": "Added 2026-09-11 from the Arbeitszeugnis."
|
||||
},
|
||||
{
|
||||
"name": "Oracle SDO_GEOMETRY",
|
||||
"evidence": "production-historical",
|
||||
"output": "allowed-with-context",
|
||||
"context": "Bosch 2020-2022 (BS-8): Oracle geospatial data type used to visualize, locate and analyze wafer data.",
|
||||
"note": "User-confirmed 2026-09-15. Previously ABSENT from claims.json - the fifth real skill found missing this way, after Ansible, Linux administration, Bash and Kotlin. Spatial SQL on Oracle does NOT license PostGIS, and it does not license ArcGIS geodatabase work."
|
||||
},
|
||||
{
|
||||
"name": "coordinate system transformation",
|
||||
"evidence": "production-historical",
|
||||
"output": "allowed-with-context",
|
||||
"context": "Bosch 2020-2022 (BS-8): normalizing wafer data across the different coordinate reference systems of fab tools and systems, and transforming between them - the main difficulty of that work.",
|
||||
"note": "User-confirmed 2026-09-15. Establishes CRS normalization and transformation. Does NOT establish geodetic datums, map projections, EPSG codes or Swiss LV95/LV03 work - ask before writing any of them."
|
||||
},
|
||||
{
|
||||
"name": "ArcGIS",
|
||||
"evidence": "none",
|
||||
"output": "forbidden",
|
||||
"note": "User-confirmed 2026-09-15: never used. Required together with FME in the internal Swisscom posting Data Engineer - Geo Platform (R-0006447): 'Fundierte Praxis mit ArcGIS und FME'. Registered so the document scanner can catch it, for the same reason as Groovy and Snowflake. Spotfire map charts (BS-5) and Oracle SDO_GEOMETRY (BS-8) are the honest spatial evidence and do not substitute for it."
|
||||
},
|
||||
{
|
||||
"name": "FME",
|
||||
"evidence": "none",
|
||||
"output": "forbidden",
|
||||
"note": "User-confirmed 2026-09-15: never used. Required together with ArcGIS in Swisscom R-0006447. General ETL pipeline experience is transferable context, never a claim of FME practice. See ArcGIS."
|
||||
},
|
||||
{
|
||||
"name": "QGIS",
|
||||
"evidence": "none",
|
||||
"output": "forbidden",
|
||||
"note": "User-confirmed 2026-09-15: never used. See ArcGIS."
|
||||
},
|
||||
{
|
||||
"name": "PostGIS",
|
||||
"evidence": "none",
|
||||
"output": "forbidden",
|
||||
"note": "User-confirmed 2026-09-15: never used. Oracle SDO_GEOMETRY (BS-8) is the real spatial-database evidence and does not license PostGIS. See ArcGIS."
|
||||
},
|
||||
{
|
||||
"name": "GeoServer",
|
||||
"evidence": "none",
|
||||
"output": "forbidden",
|
||||
"note": "User-confirmed 2026-09-15: never used. See ArcGIS."
|
||||
},
|
||||
{
|
||||
"name": "GDAL",
|
||||
"evidence": "none",
|
||||
"output": "forbidden",
|
||||
"note": "User-confirmed 2026-09-15: never used. See ArcGIS."
|
||||
}
|
||||
],
|
||||
"global_forbidden_output_patterns": [
|
||||
|
||||
@@ -59,6 +59,8 @@
|
||||
|
||||
### Achievement SW-3: Python Applications on Kubernetes + GitLab CI/CD
|
||||
|
||||
> **CORRECTED 2026-09-15 (user).** (1) **Phase:** this was the legacy B2B system at **ART B2B**, the first part of the Swisscom tenure - it is **past**; the current ART DPT stack is AWS-native (see `claims.json` SWISSCOM `org_history`). Write it in past tense. (2) **Scope:** he **worked with** automated GitLab CI/CD pipelines; he did not build or design the CI/CD automation. The variants below ("automated the full CI/CD lifecycle", "GitLab-managed quality gates and rollback controls") overstate his part and must not be reused. Safe form: *"Built and operated Python applications on Kubernetes, deployed through automated GitLab CI/CD pipelines across multiple environments."*
|
||||
|
||||
**Source:** thiessen_swisscom_zwischenzeugnis.md, thiessen_linkedin_profile.md
|
||||
**User's role:** Primary developer / operator
|
||||
**Status:** Active / ongoing
|
||||
|
||||
@@ -31,6 +31,7 @@ Use current outcome and next action below. Imported legacy notes are historical,
|
||||
| Google FDE GenAI (Zurich) | paused | not recorded | Likely abandon |
|
||||
| Equinor — Manager / AI Architect, Agentic systems (Stavanger/Oslo/Rotvoll/Sandsli; req JR106747) | rejected_no_interview | not recorded | Closed; no pending application action. Read recorded history before reopening. |
|
||||
| QuantCo Cloud Engineer (Europe/Zürich) | rejected_no_interview | not recorded | Closed; no pending application action. Read recorded history before reopening. |
|
||||
| Swisscom (Schweiz) AG — Data Engineer - Geo Platform, Bern/Worblaufen (internal, req R-0006447) | applied | not recorded | Await response. Interview prep (critique section 7): say plainly that ArcGIS and FME are unused; name the Bosch coordinate systems and how the transformations were done; geographic CRS (WGS84, LV95, datum shifts) is new ground. |
|
||||
|
||||
## Current targeting notes
|
||||
|
||||
|
||||
Reference in new issue
Block a user