# Session: Aker BP ASA — Data Product Architect, AI-ready Data Products

## JD Integrity
- File/source: `output/AkerBP_Data_Product_Architect/jd_akerbp_data_product_architect.md` — FINN-kode 469067315
- Retrieval method and date: FINN ad page fetched directly, HTML stripped to text (2026-07-29); cross-checked against arbeidsplassen.nav.no (NAV national register), ad uuid `8958b122-51ff-4f61-88be-de60c4dae1a1`
- Verbatim posting: YES — full body captured, not summarized
- Posting status: LIVE (last modified 2026-07-06). **Deadline 02.08.2026 — 4 days from retrieval.**

## Application Decision
- Audience profile: **International Tech** (English-working Norwegian operator; US/intl tech conventions apply)
- Evidence Fit: **79/100** (revised from 74 on 2026-07-29 — Atlassian Compass)
- Fit class: **Adjacent** (top of band, one point below Core)
- Hard gate: **PASS** — with one flagged level-scope caution, see below
- Channel Strength: **Weak** — cold application. Named contact exists (Per Olav Marthinsen, per.marthinsen@akerbp.com); a pre-application email would upgrade this to Moderate.
- Cohort slot: Adjacent
- Decision: **PROCEED** — user-confirmed 2026-07-29 (location accepted, honest practitioner framing chosen)

### Evidence Fit breakdown
| Dimension | Weight | Score | Note |
|---|---:|---:|---|
| Required qualifications | 35 | 33 | All Direct after Atlassian Compass closed the catalogue-platform gap (2026-07-29) |
| Core responsibilities | 25 | 15 | **Weakest.** He builds products *inside* a governance framework; the role *authors* one |
| Level and ownership | 15 | 10 | Staff IC → architect. Holds Component/Application Owner titles; not org-wide architecture authority |
| Recency and depth | 10 | 10 | SW-7 is current, ongoing, and directly on-topic |
| Domain/tool transfer | 10 | 7 | AWS vs Aker BP's Microsoft/Cognite/Databricks stack; Compass is a real catalogue tool but not theirs |
| Practical constraints | 5 | 4 | English ✅, EU/EEA work rights ✅, relocation + tight deadline |
| **Total** | **100** | **79** | Revised up from 74 on 2026-07-29 (Atlassian Compass). Top of Adjacent, one point below Core. |

### Hard-gate audit
- **Language:** English only. PASS. (Contrast: Telenor Norge reqs assessed 2026-07-29 all required `norsk`.)
- **Clearance:** None required. PASS. (Contrast: every Telenor Norge req required Norwegian clearance.)
- **Work authorization:** German citizen → EEA free movement covers Norway. PASS, no sponsorship needed.
- **Location:** Stavanger / Oslo / Trondheim, registered sites 1366 Lysaker, 4020 Stavanger, 7011 Trondheim. Requires relocation from Bern. **User accepted 2026-07-29.**
- **Level scope — FLAGGED, not failed.** `critique_framework.md` §1 lists "company-wide architecture authority" as a NO-GO trigger, and the JD does say "define governance principles, architecture patterns and lifecycle practices for data products **across the organization**." It is not a NO-GO because the JD explicitly places him *alongside* a Data Product Governance Lead and a Data Catalogue Owner — he contributes architecture inside a governance team that already has owners — and states "the successful applicant will be given the necessary training to succeed." Treat as an honest level stretch, not a fabricable gap.

## Requirements
| # | Requirement | Req/pref | Class | Canonical evidence | Gate? |
|---|---|---|---|---|---|
| 1 | Master's degree in relevant discipline | Required | **Direct** | EDU-MENG (M.Eng. Computer Aided Engineering, Software Design & Engineering) | Yes |
| 2 | Modern data architecture, information architecture, data governance or similar | Required | **Direct** | SW-7 (governed data products, active metadata, Data Mesh); SW-2 (governance of owned components) | Yes |
| 3 | Designing or governing data products, data platforms or analytical solutions | Required | **Direct** | SW-7 (model/build governed data products), SW-4 (deliver data products), SW-2 | Yes |
| 4 | Strong communication; fluent English written and spoken | Required | **Direct** | identity.languages English fluent | Yes |
| 5 | Collaborate across business and technology domains | Required | **Direct** | SW-4 (product owners, internal B2B stakeholders) | No |
| 6 | Microsoft Purview, Collibra, Alation or similar metadata/catalogue platforms | Listed | **Adjacent** *(upgraded from Gap 2026-07-29)* | **Atlassian Compass** — Swisscom's metadata/catalogue platform for data-product metadata and lineage; user-confirmed 2026-07-29, added to claims.json SW-7 + skills. Satisfies "or similar". Practitioner use only — do not claim administration or rollout. Purview/Collibra/Alation themselves remain unevidenced and must not appear. | No |
| 7 | Understanding of how governed data products enable analytics, AI and automation | Listed | **Direct** | SW-7 (supports analytics and AI use cases); SW-8 (domain-grounded LLM assistants) | No |
| 8 | Cloud data platforms or modern data ecosystems | Listed | **Direct** | SW-1, SW-7 (AWS S3/Glue/Athena-Iceberg/Redshift/CloudFormation) | No |
| 9 | Energy, industrial or complex enterprise environments | Listed | **Direct** | BOSCH (24/7 semiconductor manufacturing = industrial); SWISSCOM (complex enterprise). Not energy specifically. | No |
| 10 | Diploma/grade transcript enclosed with application | Constraint | **Action** | Dennis must attach transcripts — not a document task | — |
| 11 | High-risk-country affiliation assessment | Constraint | **Disclose** | M.Eng. thesis at Tongji University, Shanghai (2013) — already on the CV. Answer plainly if raised; do not omit. | — |

## Competitive Read
- **Obvious-fit candidate:** A Norwegian data architect from an operator or industrial vendor who already owns a Collibra or Purview deployment, has authored data-product standards, and knows Cognite Data Fusion. Likely already in the Norwegian energy data community.
- **Dennis's advantage:** Genuinely *current*, hands-on delivery inside a company-wide Data Mesh — modelling data products, onboarding sources, maintaining active metadata — plus production accountability as Component Owner (on-call, data quality, governance). He knows what makes a governance standard survivable in production because he has had to live inside one. Industrial 24/7 background at Bosch. Multi-country European delivery.
- **Their advantage:** Named catalogue-tool ownership, framework authorship, Norwegian energy domain, Microsoft/Cognite ecosystem fluency, and no relocation friction.
- **Level/scope comparison:** The competitor arrives having *set* standards; Dennis arrives having *implemented under* them. That is a real difference and the resume must not blur it.

## Framing Strategy
- **Professional identity:** A hands-on data engineer who builds and operates governed data products inside a company-wide Data Mesh — someone who has lived the practitioner side of exactly the governance surface Aker BP is formalising.
- **Strongest proof points:** SW-7 (governed data products, source onboarding, active metadata within Swisscom's company-wide Data Mesh on AWS) — this is the lead. Then SW-2 (Component Owner: data quality, governance, incidents, on-call), SW-1 (AWS migration of his domains' pipelines), SW-4 (data products with product owners and B2B stakeholders), BS-3 (Application Owner: SLOs, vendors, documentation, training — the closest thing to standards-and-adoption work).
- **Honest adjacent bridges:** "Active metadata management" → catalogue/lineage discipline without naming a product he has not used. Application Owner documentation/training → adoption and enablement. SW-8 → understanding of what AI-ready actually demands of data.
- **Explicit gaps — state, never paper over:**
  1. ~~No named catalogue or lineage product at all.~~ **CLOSED 2026-07-29** — Atlassian Compass is the metadata/lineage platform for data products at Swisscom. Purview / Collibra / Alation specifically remain unevidenced and must never appear; Compass is named honestly as itself under the JD's "or similar".
  2. Has not authored an enterprise data-product governance framework. Per `claims.json` SW-7: *"never claim ownership or construction of the shared mesh/platform."*
  3. AWS-native; Aker BP runs Microsoft + Cognite Data Fusion + Databricks. Azure is `forbidden` in claims.json (unverified) — must not appear.
  4. No energy/oil-and-gas domain experience.
- **User directives (2026-07-29):** Location accepted. **Honest practitioner framing** — position as deep practitioner inside a company-wide Data Mesh; the architect step is the growth, not a claim. Norway comp bar does not apply. Company quality was the filter and Aker BP clears it (Glassdoor 4.5/5, 86% recommend, n=22 — small sample).

## Company Context
- **Mission/context:** Norwegian continental-shelf E&P operator. Six field centres (Alvheim, Ivar Aasen, Skarv, Edvard Grieg, Ula, Valhall) plus a Johan Sverdrup partnership. HQ Fornebu; offices Stavanger, Trondheim, Harstad, Sandnessjøen.
- **Digital programme:** **Eureka** — Aker BP's cross-functional transformation hub, built on **Cognite Data Fusion** as the industrial data platform, with the stated goal of making all Aker BP data available to authorised users with low latency. Legacy limited-governance, manual data practices drove a **Profisee master-data-management** foundation.
- **AI posture:** Publicly declared **"AI-first"** E&P company. Expanded Cognite **Atlas AI** partnership (Sept 2025) for AI agents in exploration and production; deployed **Cognite + NVIDIA** NV-Tesseract time-series models for offshore anomaly detection (Mar 2026); **Microsoft 365 Copilot** and AI agents internally; **SLB** co-development of an AI-driven digital platform (2024). Cognite–**Databricks** zero-copy sharing announced 2025.
- **Why this matters to the pitch:** The JD's phrase "ready for analytics, automation, AI and intelligent agents" is not boilerplate — it is the Atlas AI agent programme. The honest hook is that Dennis's current work is building the *data foundation* that agentic use cases consume, which is the same problem one layer down.
- **Culture signals:** SAFER values (Seekers, Accountable, Foreseeable, Engaged, Respectful); ONETEAM collaboration; safety-first; explicit diversity and accessibility commitments.

## Critique Context
- **Reviewer persona:** A data governance lead / enterprise architect in Data Platforms & Delivery, hiring a peer-level architect. Will probe framework authorship depth and catalogue tooling within the first five minutes.
- **Competitive landscape:** Norwegian energy-sector data architects with catalogue-product ownership.
- **Domain vocabulary:** data products, data product governance framework, metadata, lineage, ownership, data quality, business context, discoverability, adoption, semantic models, AI-ready, intelligent agents, data catalogue, MDM.
- **Likely first technical challenge:** "Walk me through a data product you modelled end to end — how was ownership assigned, how was quality enforced, and how did consumers discover it?" He can answer this honestly and well. The follow-up — "how would you set that standard for 3,000 people?" — is the stretch.

## Resume Plan
- Summary: 2–3 lines, governance/data-product forward
- Skills: 5–6 evidence-backed lines; add a data governance / metadata line; **no Azure, no Terraform, no catalogue product names**
- Swisscom: SW-7 (lead), SW-2, SW-1, SW-4 — 4–5 bullets
- Bosch: BS-3 (Application Owner — SLOs, vendors, docs, training), BS-2, BS-1 — 3 bullets
- Earlier experience: Fraunhofer, Vizrt, Generali — 1 each, compressed
- Total bullets: 11–13, natural length, no page-fill quota
- Impact evidence still needed: **all `metrics: unverified`** — number of data products modelled, source systems onboarded, consumers served. Worth asking Dennis before writing; would materially strengthen SW-7.

## Cover Letter Decision
- **YES/NO:** YES (provisional — reassess after resume)
- **Reason:** Two things the resume cannot carry: (a) why a Bern-based Swiss engineer is credibly moving to Norway, which a recruiter will otherwise treat as a flight risk; (b) an honest, confident statement of the practitioner-to-architect step rather than leaving the reviewer to infer overreach.
- **Information it adds beyond resume:** Relocation intent and EEA work rights; genuine Norway history (Vizrt, Bergen 2017–18); motivation tied to Eureka / Cognite Data Fusion / AI-first agenda.
- **Verified hook sources:** Aker BP newsroom (Cognite Atlas AI, 2025-09); worldoil.com (Cognite–NVIDIA anomaly detection, 2026-03); Microsoft customer story (M365 Copilot); tietoevry blog (Eureka data journey); JD verbatim.
- **Caution:** Do NOT repeat the Microsoft/Google mistake of a defensive level-mismatch paragraph. Here the step is *upward*, so state ambition plainly and move on.

## Bullet Plan (user-confirmed 2026-07-29)
**Swisscom (5):** SW-7 (lead), SW-2, SW-1, SW-4, SW-8
**Bosch (3):** BS-3 (lead — standards/adoption evidence), BS-2, BS-5 (Spotfire + TAF 2022, swapped in for BS-1 by user decision)
**Fraunhofer (1):** FC-1 + FC-3 combined · **Vizrt (1):** VZ-1 + VZ-2 combined · **Generali (1):** GN-1
**Total: 11** vs target 11–14 — Budget gate PASS.
Excluded: SW-5 (no security requirement in JD), SW-6 (folded into skills), BS-1, BS-4 (observability off-topic).

## Output Files
- Resume: `output/AkerBP_Data_Product_Architect/e2e_akerbp_data_product_architect_resume.tex` + `.pdf` (2 pages)
- Cover letter: `output/AkerBP_Data_Product_Architect/e2e_akerbp_data_product_architect_cover_letter.tex` + `.pdf` (1 page, 275 words)
- Critique: pending

## Cover Letter Hook Verification (2026-07-29)
| Claim in CL | Evidence | Source |
|---|---|---|
| Aker BP is building agent use cases on Cognite Atlas AI | First-party: "Cognite Atlas AI offers pre-built agents and a low-code workbench for building industrial AI agents"; "Our 'AI-first strategy' was developed to help lead the energy sector into a data-driven future" | akerbp.com newsroom — *Aker BP leverages Cognite Atlas AI to pioneer an AI-first future in exploration and production* |
| Addressed to Per Olav Marthinsen | Named contact in the posting | JD verbatim, FINN 469067315 |
| Data Delivery team | "This position is part of Data Delivery" | JD verbatim |
| Atlassian Compass for data-product metadata and lineage | User-confirmed 2026-07-29; canonical claims.json SW-7 + skills | Canonical KB |
| Vizrt, Bergen — one year in Norway | employment.VIZRT, Jul 2017 – May 2018 | Canonical KB |
| German citizen, no sponsorship for Norway | identity.citizenship (EU) → EEA free movement | Canonical KB |
| Norwegian elementary | identity.languages Norwegian: basic (A2, user-confirmed 2026-07-29) | Canonical KB |

All hooks verified against first-party or canonical sources. **No unverified claims.**

## Review Pass 2 — applied 2026-07-29 (user critique)
| # | Finding | Action |
|---|---|---|
| 1 | `Applied AI` skills line claimed "production ML inference integration" with no corresponding bullet visible | **Fixed** — BS-1 added to Bosch (now 4 bullets, total **12**). Skills claim is now evidence-visible. |
| 2 | Add verified scope metrics | **Not actioned** — user has supplied none; inventing them is forbidden. Still the package's weakest point. |
| 3 | Headline "Data Engineer" undersells level | **Fixed** — now "Staff Data Engineer". Accurate: official title is Staff Data, Analytics & AI Engineer. Still does NOT say "Architect" (`resume_reference.md` §8). |
| 4 | Overfull hbox 2.3pt in BS-2 bullet; `visualisations`/`containerized` spelling inconsistency | **Fixed** — bullet reworded (no overfull lines remain), `visualisations` → `visualizations`. Remaining word splits in pdftotext are normal LaTeX hyphenation, not defects. |
| 5 | Page 2 sparse — do not pad | **Resolved by #1**, plus page-break fix below. |
| CL-A | "I have not authored an enterprise governance framework myself" — hands the reviewer its rejection rationale | **Fixed.** Also a rules violation: `cl_reference.md` bans a "defensive gap list" and `ai_fingerprint_rules.md` requires bridges be "short and evidence-led". Replaced with transferability-led phrasing that keeps the honesty and names the Governance Lead / Catalogue Owner collaboration from the JD. Same failure mode as the 2026-07-28 Google post-mortem. |
| CL-B | "one layer down" is self-subordinating | **Fixed** — "The role addresses at enterprise level a problem I already work on in production." |
| CL-C | "documentation and training that got analytics systems genuinely adopted" overclaims causation vs BS-3 | **Fixed** — "that supported adoption". Provenance-level fix, not style. |

**Page-break fix:** adding BS-1 caused the Bosch role to split across pages, orphaning two bullets on page 2 with no employer header. Resolved with a single targeted `\newpage` before Bosch — **not** the template's blind break, and **no "(continued)" heading**. Page 1 now ends after Swisscom (~78% full), page 2 carries all remaining roles intact (~85% full).

## Mechanical Verification (2026-07-29, re-verified after Pass 2)
- Canonical validator, **both documents**: **PASS — 0 warnings**
- Compile: MiKTeX pdflatex — resume **2 pages**, cover letter **1 page**, no errors, **no overfull/underfull boxes**
- pdftotext extraction: employer / dates / title / location order correct
- Cover letter body: **258 words** (target 200–300)
- Bullet count **12**; lengths 17–37 words, natural mix. `char_count.py` "dense" flags are parser artifacts (it bleeds following section text into the bullet), not real.
- No "Professional Experience (continued)" header anywhere — the template default was dropped deliberately after it produced a broken-looking page 1 in the Google package.
- Deliberate AI-fingerprint control: trailing gerund purpose-clauses varied on purpose (that uniformity was a finding in the 2026-07-28 Google post-mortem). Bullet shapes now mix colon-list, plain object-ending, and short forms.
- Forbidden terms confirmed absent: Azure, Terraform, dbt, LangChain, Purview, Collibra, Alation.

## Status
- Fit gate: **DONE** — Adjacent 74/100, hard gate PASS, PROCEED confirmed by user
- Phase 0: **DONE**
- Phase 1: **DONE** (11 bullets confirmed)
- Resume: **DONE** — compiled and verified
- Cover letter: **DONE** — 1 page, 258 words, validator PASS, all hooks verified
- Critique: **CURRENT** — Evidence Fit 79/100 Adjacent, Document Quality 93/100, hard gate PASS, Channel Weak. 3 Tier 1 findings applied (architecture vocabulary, Languages line, catalogue/adoption terms). See `critique_akerbp_data_product_architect.md`.
- Finalized: **YES 2026-07-29** — `Dennis_Thiessen_Resume.pdf`, `Dennis_Thiessen_Cover_Letter.pdf`; cohort entry added (evidence-first-2026-01, adjacent 1/2)
- Pre-submission actions outstanding: **attach diploma/grade transcript** (required by posting); optional cold email to Per Olav Marthinsen
- Application/outcome: **SUBMITTED 2026-07-29** (4 days before the 2026-08-02 deadline). Cohort outcome set to `applied`. Awaiting response.
- Next: `/make-cl output/AkerBP_Data_Product_Architect/session_akerbp_data_product_architect.md`
- Then: `/critique output/AkerBP_Data_Product_Architect/session_akerbp_data_product_architect.md`
