feat(applications): archive Aker BP package, add Compass evidence, extend scout
Aker BP ASA — Data Product Architect (FINN 469067315): archive the finalized resume/CL sources, JD, session and critique. Submitted 2026-07-30 ahead of the 2026-08-02 deadline; logged as applied in the scout decision log and marked SUBMITTED in Active Sessions. KB: record Atlassian Compass as Swisscom's metadata/catalogue platform for data products and lineage (user-confirmed 2026-07-29). Practitioner use only — claims.json forbids claiming administration, rollout or ownership, and it is explicitly not a substitute claim for Purview, Collibra or Alation. Also: close out the Google Business Home session (no interview), extend the job scout, and allow the job-board domains used during the Aker BP research. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Claude Opus 5
@@ -0,0 +1,142 @@
|
||||
# Critique: Aker BP ASA — Data Product Architect, AI-ready Data Products
|
||||
|
||||
**Date:** 2026-07-29
|
||||
**Documents:** `e2e_akerbp_data_product_architect_resume.tex` (2pp), `e2e_akerbp_data_product_architect_cover_letter.tex` (1pp, 258 words)
|
||||
**JD:** `jd_akerbp_data_product_architect.md` — verbatim FINN 469067315, retrieved 2026-07-29. **JD integrity: PASS.**
|
||||
|
||||
> **Reviewer-independence caveat.** This critique was produced by the same agent that generated the package. That is a real weakness. The most consequential findings in this application came from the user's own review pass (Pass 2), not from self-critique. Treat the scores below as directional; treat the Tier findings as the useful output.
|
||||
|
||||
---
|
||||
|
||||
## 1. Fit Verdict and Hard Gate
|
||||
|
||||
**Evidence Fit: 79/100 — Adjacent** (top of band, one point below Core)
|
||||
**Hard gate: PASS**
|
||||
|
||||
| Dimension | Weight | Score | Note |
|
||||
|---|---:|---:|---|
|
||||
| Required qualifications | 35 | 33 | All Direct once Atlassian Compass closed the catalogue-platform gap |
|
||||
| Core responsibilities | 25 | 15 | **Weakest.** Builds products inside a governance framework; the role authors one |
|
||||
| Level and ownership | 15 | 10 | Staff IC → architect. Component/Application Owner titles are real; org-wide architecture authority is not |
|
||||
| Recency and depth | 10 | 10 | SW-7 is current and directly on-topic |
|
||||
| Domain/tool transfer | 10 | 7 | AWS vs their Microsoft/Cognite/Databricks stack; Compass is a real catalogue tool but not theirs |
|
||||
| Practical constraints | 5 | 4 | English ✅, EEA work rights ✅, relocation + 4-day deadline |
|
||||
|
||||
**No hard-gate failure.** English-only, no Norwegian clearance, no sponsorship needed, Master's held, location accepted by user.
|
||||
|
||||
**Flagged, not failed:** `critique_framework.md` §1 lists "company-wide architecture authority" as a NO-GO trigger, and the JD does say "across the organization". Not scored as NO-GO because the JD places the role *alongside* a Data Product Governance Lead and a Data Catalogue Owner, and states training will be given. This is the honest stretch and it is why Core responsibilities scores 15/25.
|
||||
|
||||
---
|
||||
|
||||
## 2. Document Quality: 93/100 — Pass
|
||||
|
||||
| Dimension | Weight | Score | Assessment |
|
||||
|---|---:|---:|---|
|
||||
| Truth and provenance | 25 | 25 | Validator PASS on both documents. Every claim traces to a canonical ID. Scope discipline held: no "built the Data Mesh", no framework authorship, no Purview/Collibra/Alation, no Azure/Terraform/dbt/LangChain. |
|
||||
| Information hierarchy | 20 | 19 | Employer/title/dates/location dominant; governance evidence leads Swisscom and Bosch. |
|
||||
| Bullet evidence and impact | 20 | 16 | Specific and interviewable, but **no verified metric anywhere** — the single largest remaining weakness. |
|
||||
| Relevance and terminology | 15 | 14 | Post-fix, JD vocabulary coverage is strong (see §4). |
|
||||
| Skills evidence | 10 | 10 | Every listed skill now has a visible supporting bullet — including Applied AI, which did not before Pass 2. |
|
||||
| Mechanics/readability | 10 | 9 | 2pp, no overfull boxes, no orphaned bullets, no "(continued)" header. Page 1 ~78% full by design. |
|
||||
|
||||
---
|
||||
|
||||
## 3. Channel Strength: **Weak**
|
||||
|
||||
Cold application. A named contact exists (Per Olav Marthinsen). Channel is the one variable that has been Weak across all thirteen applications in this repo and is not fixable by document quality.
|
||||
|
||||
---
|
||||
|
||||
## 4. ATS / Vocabulary Scan
|
||||
|
||||
Post-fix coverage of JD terminology:
|
||||
|
||||
| Present | Absent (accepted) |
|
||||
|---|---|
|
||||
| data products · data mesh · metadata · lineage · cataloguing · data quality · ownership · lifecycle · governance · discoverability · adoption · architecture · analytics · AI · automation · cloud · English · Norwegian | information architecture · semantic models · intelligent agents · "energy" |
|
||||
|
||||
The absent terms are either unevidenced (information architecture, semantic models) or would require claiming work not done. Correctly omitted rather than keyword-stuffed.
|
||||
|
||||
---
|
||||
|
||||
## 5. Reader Sequence
|
||||
|
||||
- **ATS:** **PASS.** Clean extraction; employer/title/date order verified via pdftotext.
|
||||
- **Recruiter (10s):** **BORDERLINE → FORWARD.** Staff level, "Governed Data Products · Metadata · Data Mesh" in the headline, Compass named. Concerns are relocation and architect scope, both addressed in the letter.
|
||||
- **Hiring manager (2min):** **MAYBE.** Production-grounded governance is genuinely attractive and rare. Framework authorship will decide it.
|
||||
- **Technical reviewer (10min):** **CREDIBLE.** Expect immediate probing on setting standards across many teams, catalogue depth beyond Compass, ownership assignment, and how adoption is measured.
|
||||
|
||||
---
|
||||
|
||||
## 6. Competitive Read
|
||||
|
||||
**Obvious-fit competitor:** a Norwegian data architect who already owns a Collibra or Purview deployment, has authored data-product standards, and knows Cognite Data Fusion.
|
||||
|
||||
- **Dennis's advantage:** current hands-on delivery inside a company-wide Data Mesh, plus production accountability (Component Owner, on-call, data quality). He knows which standards survive production because he has lived under them.
|
||||
- **Their advantage:** framework authorship, catalogue-tool ownership, Norwegian energy domain, Microsoft/Cognite fluency, no relocation friction.
|
||||
|
||||
---
|
||||
|
||||
## 7. Claim Audit
|
||||
|
||||
| Claim | Canonical | Safe? |
|
||||
|---|---|---|
|
||||
| Governed data products + metadata/lineage in Atlassian Compass, Data Mesh | SW-7 (updated 2026-07-29) | YES — practitioner scope, no platform ownership |
|
||||
| Component Owner, Fulfillment ETL | SW-2 | YES |
|
||||
| Migrated domains' pipelines to cloud-native architecture on AWS; contributed to wider programme | SW-1 | YES — object scoped to his domains, hedged verb on the programme |
|
||||
| Data products with product owners / B2B stakeholders | SW-4 | YES |
|
||||
| Domain-grounded LLM assistants, model selection, curated knowledge | SW-8 | YES — no fine-tuning, RAG or deployment claim |
|
||||
| Application Owner: SLOs, vendors, coordinating adoption via docs/training | BS-3 | YES — "coordinating adoption" matches the canonical 3L variant; earlier "got genuinely adopted" was a causal overclaim and was removed in Pass 2 |
|
||||
| Containerized ML inference into 24/7 fab | BS-1 | YES — integration claim only, no model-training claim |
|
||||
| Spotfire co-ownership + TAF 2022 | BS-5 | YES — verified credential |
|
||||
| Languages: German native, English fluent, Norwegian basic | identity.languages | YES |
|
||||
|
||||
**No unsafe claims.**
|
||||
|
||||
---
|
||||
|
||||
## 8. Tiered Improvements
|
||||
|
||||
### Tier 1 — found in this critique, **APPLIED**
|
||||
1. **"Architecture" appeared nowhere** in a resume for an *Architect* role where "modern data architecture" is a required qualification. Fixed two ways, both canonical-backed: SW-1 now reads "onto a cloud-native architecture on Swisscom's AWS platform" (matches the experience-file variant), and the iSAQB certification is now spelled out as "Certified Professional for Software Architecture (CPSA)".
|
||||
2. **No Languages line**, despite fluent English being a stated requirement and Norwegian being materially relevant to the relocation story. Added.
|
||||
3. **"Catalogue" and "adoption" absent** though both are JD-central and both canonically supported. Added to the skills line and the BS-3 bullet respectively.
|
||||
|
||||
### Tier 2 — not actioned, by decision
|
||||
- **No verified metrics.** All 21 canonical claims carry `metrics: unverified`. Asked twice; user has none to supply. Inventing them is forbidden. This remains the package's largest weakness and directly caps the Bullet-evidence dimension at 16/20.
|
||||
|
||||
### Tier 3 — cosmetic, rejected
|
||||
- Page 1 bottom whitespace (~22%). `resume_reference.md` §4/§9 forbid adding content to reduce whitespace.
|
||||
- Russian (basic) omitted from the Languages line: not relevant to the role, and volunteering it on a Norwegian continental-shelf application subject to a high-risk-country affiliation assessment adds noise for no benefit. Omitting a basic non-professional language is normal practice, not concealment. **User can override.**
|
||||
|
||||
---
|
||||
|
||||
## 9. Cover Letter
|
||||
|
||||
**Decision: KEEP.**
|
||||
|
||||
Adds three things the resume cannot: relocation intent with EEA work rights, genuine Norway history (Vizrt Bergen), and the practitioner-to-architect rationale. All hooks verified first-party (see session file hook table). One company reference only — `cl_reference.md` warns against spending a paragraph proving familiarity.
|
||||
|
||||
**Pass 2 corrected its most serious defect:** the sentence "I have not authored an enterprise governance framework myself" handed the reviewer a ready-made rejection rationale and violated the explicit ban on defensive gap lists in `cl_reference.md` and `ai_fingerprint_rules.md`. This was the same failure mode identified in the 2026-07-28 Google post-mortem and partly reproduced here. Now replaced with transferability-led phrasing that names the Governance Lead and Catalogue Owner collaboration from the JD.
|
||||
|
||||
---
|
||||
|
||||
## 10. Mechanical Verification
|
||||
|
||||
- Canonical validator, both documents: **PASS — 0 warnings**
|
||||
- Compile: resume **2 pages**, cover letter **1 page**, **no overfull/underfull boxes**
|
||||
- pdftotext: employer / title / dates / location order correct
|
||||
- Contact details and email (`dennis@thiessen.io`) correct per `config.md`
|
||||
- Bullets: **12**; no orphans, no split subsections, no "(continued)" header
|
||||
- Certifications listed once; Education template-locked and unmodified
|
||||
- Forbidden terms confirmed absent: Azure, Terraform, dbt, LangChain, Purview, Collibra, Alation, "petabyte scale", French/Italian
|
||||
|
||||
---
|
||||
|
||||
## Recommendation
|
||||
|
||||
**Submit.** Document Quality 93/100 with no unsafe claims; Evidence Fit 79/100 Adjacent with no hard-gate failure. The residual risks — framework authorship, no energy domain, AWS vs their stack, no metrics — are evidence realities, not document defects, and no further editing pass will change them.
|
||||
|
||||
**Before submitting:** attach the diploma/grade transcript (explicitly required by the posting). Expect the high-risk-country affiliation assessment to surface the Tongji/Shanghai thesis; answer plainly.
|
||||
|
||||
**Highest-leverage action outside the document:** email Per Olav Marthinsen. Channel Strength has been Weak on every application in this repo, and it is the one variable never yet tested.
|
||||
+47
@@ -0,0 +1,47 @@
|
||||
\documentclass[11pt,a4paper]{article}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage{lmodern}
|
||||
\usepackage[a4paper,left=0.85in,right=0.85in,top=0.7in,bottom=0.7in]{geometry}
|
||||
\usepackage{parskip}
|
||||
\usepackage{xcolor}
|
||||
\usepackage{hyperref}
|
||||
\hypersetup{hidelinks}
|
||||
\pagestyle{empty}
|
||||
\setlength{\parindent}{0pt}
|
||||
|
||||
\begin{document}
|
||||
|
||||
{\Large\bfseries Dennis Thiessen, M.Eng.}\par
|
||||
Bern, Switzerland $\vert$
|
||||
\href{mailto:dennis@thiessen.io}{dennis@thiessen.io} $\vert$ +41 795 955 585 $\vert$
|
||||
\href{https://linkedin.com/in/dennis-thiessen}{LinkedIn}
|
||||
|
||||
\vspace{1.5em}
|
||||
Per Olav Marthinsen\\
|
||||
Aker BP ASA\\
|
||||
Norway
|
||||
|
||||
\vspace{1em}
|
||||
29 July 2026
|
||||
|
||||
\vspace{1em}
|
||||
\textbf{Application for Data Product Architect -- AI-ready Data Products}
|
||||
|
||||
\vspace{0.8em}
|
||||
Dear Per Olav Marthinsen,
|
||||
|
||||
The role addresses at enterprise level a problem I already work on in production. At Swisscom I model and build governed data products inside the company-wide Data Mesh, onboard the source systems behind them, and document their metadata and lineage in Atlassian Compass. Getting those products trusted and discoverable enough that analytics and AI consumers actually rely on them is the daily work, and it is the same foundation the agent use cases you are building on Cognite Atlas AI depend on.
|
||||
|
||||
My experience is on the practitioner side of governance. As Component Owner for business-critical Fulfillment pipelines I carry the data quality, incident resolution and on-call duty for them, rather than handing standards to someone else to live with. Earlier, as Application Owner at Bosch Semiconductor in Dresden, I defined SLOs and wrote the documentation and training that supported adoption across engineering teams in a 24/7 fab. Years of implementing standards in production is how you learn which of them stay adoptable and which get quietly bypassed, and that is the perspective I would bring to evolving your framework alongside the Governance Lead and Catalogue Owner.
|
||||
|
||||
Practically: as a German citizen I need no sponsorship to work in Norway, and I am ready to relocate for this role. I know the country a little already, having spent a year at Vizrt in Bergen, and my Norwegian is elementary but something I would build on. I work in German and English.
|
||||
|
||||
I would welcome the chance to discuss how this experience could support the Data Delivery team.
|
||||
|
||||
Kind regards,
|
||||
|
||||
\vspace{1.5em}
|
||||
Dennis Thiessen
|
||||
|
||||
\end{document}
|
||||
@@ -0,0 +1,78 @@
|
||||
\documentclass{resume}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage{lmodern}
|
||||
\usepackage[a4paper,left=0.65in,right=0.65in,top=0.55in,bottom=0.55in]{geometry}
|
||||
\usepackage{xcolor}
|
||||
\usepackage{hyperref}
|
||||
\hypersetup{hidelinks}
|
||||
\usepackage[version=4]{mhchem}
|
||||
\usepackage{fancyhdr}
|
||||
\pagestyle{fancy}
|
||||
\fancyhf{}
|
||||
\renewcommand{\headrulewidth}{0pt}
|
||||
\fancyfoot[R]{\small \thepage/\pageref{LastPage}}
|
||||
|
||||
\name{Dennis Thiessen, M.Eng.}
|
||||
\headline{Staff Data Engineer $\vert$ Governed Data Products $\cdot$ Metadata $\cdot$ Data Mesh $\vert$ AWS}
|
||||
\contactline{Bern, Switzerland $\vert$ \href{mailto:dennis@thiessen.io}{dennis@thiessen.io} $\vert$ +41 795 955 585 $\vert$ \href{https://linkedin.com/in/dennis-thiessen}{LinkedIn}}
|
||||
|
||||
\begin{document}
|
||||
|
||||
\begin{rSection}{Summary}
|
||||
Data engineer with over ten years in production delivery, currently modelling and building governed data products and their active metadata inside Swisscom's company-wide Data Mesh on AWS. Component Owner for business-critical Fulfillment pipelines, previously Application Owner for analytics systems in 24/7 semiconductor manufacturing; iSAQB CPSA Foundation certified.
|
||||
\end{rSection}
|
||||
|
||||
\begin{rSection}{Technical Skills}
|
||||
\skillline{Data governance and products}{Data products, data mesh, metadata, lineage and cataloguing in Atlassian Compass, source onboarding, data quality, ownership and lifecycle responsibility}
|
||||
\skillline{Data engineering}{Python, SQL, PySpark, Apache Kafka, Airflow, ETL/ELT, Oracle, Teradata, Hadoop/Impala}
|
||||
\skillline{Cloud and platform}{AWS (S3, Glue, Athena/Iceberg, Redshift), CloudFormation, Kubernetes, Docker, GitLab CI/CD}
|
||||
\skillline{Applied AI}{Production ML inference integration; domain-grounded LLM assistant configuration and LiteLLM API use}
|
||||
\skillline{Languages}{German (native); English (fluent); Norwegian (basic)}
|
||||
\skillline{Certifications}{iSAQB Certified Professional for Software Architecture (CPSA) -- Foundation; AWS Solutions Architect -- Associate; Data Engineering with AWS; ITIL Foundation}
|
||||
\end{rSection}
|
||||
|
||||
\begin{rSection}{Professional Experience}
|
||||
|
||||
\begin{rSubsection}{Swisscom (Schweiz) AG}{Oct 2023 -- Present}{Staff Data, Analytics \& AI Engineer (promoted from Senior, Apr 2025)}{Bern, Switzerland}
|
||||
\item Model and build governed data products within Swisscom's company-wide Data Mesh on AWS, onboarding source systems and documenting their metadata and lineage in Atlassian Compass so that analytics and AI consumers can discover and trust them.
|
||||
\item Own business-critical Fulfillment ETL components as Component Owner: production operation, data quality, governance compliance, incident resolution and on-call duty across Oracle, Kafka, Python and Teradata processing.
|
||||
\item Migrated the Fulfillment and Product Analysis domains' pipelines from Teradata and Oracle onto a cloud-native architecture on Swisscom's AWS platform, using S3, Glue, Athena/Iceberg, Redshift, Airflow and CloudFormation, and contributed to the wider migration programme.
|
||||
\item Partner with product owners and internal B2B stakeholders to turn open business questions into data products, analyses and dashboards.
|
||||
\item Configured domain-grounded LLM assistants in a Swisscom web interface, selecting available models and supplying curated domain knowledge for question answering, migration support and data mapping.
|
||||
\end{rSubsection}
|
||||
|
||||
% Keep the Bosch block whole: without this the role splits across the page break and
|
||||
% two bullets orphan onto page 2 without their employer header. No "(continued)"
|
||||
% heading — the section simply carries on.
|
||||
\newpage
|
||||
|
||||
\begin{rSubsection}{Robert Bosch Semiconductor Manufacturing Dresden GmbH}{Feb 2020 -- Dec 2022}{Senior Engineer, Data Analysis (Data \& ML Engineering)}{Dresden, Germany}
|
||||
\item Served as Application Owner for semiconductor analytics applications and their upstream pipelines, defining SLOs, managing software vendors, and coordinating adoption across analysis teams through documentation and user training.
|
||||
\item Integrated containerized ML inference with Docker, Kubernetes and Ansible into a continuously operating semiconductor fab, replacing manual wafer inspection with automated image-based defect classification.
|
||||
\item Developed data services in Python, Java and C\# over Oracle and Hadoop/Impala for the defect-management and process-analysis teams.
|
||||
\item Co-owned Bosch's TIBCO Spotfire analytics environment, built C\# extensions and wafer-map visualizations, and co-presented the work at the TIBCO Analytics Forum 2022.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Fraunhofer-Center for Maritime Logistics and Services CML}{Sep 2018 -- Oct 2019}{Research Software Engineer}{Hamburg, Germany}
|
||||
\item Set up Jenkins CI/CD with quality gates, developed C\#/.NET scheduling software and built containerized JavaScript microservices for maritime research platforms.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Vizrt}{Jul 2017 -- May 2018}{Test Automation / DevOps Engineer}{Bergen, Norway}
|
||||
\item Contributed Python and C++ engineering to a distributed video-transcoding backend and developed automated audio/video integration tests wired into CI/CD quality gates.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Generali Deutschland Informatik Services GmbH}{May 2015 -- Jun 2017}{IT Consultant}{Hamburg, Germany}
|
||||
\item Introduced BDD through a proof of concept, held technical responsibility for test automation and Jenkins jobs, and trained colleagues in the Java community.
|
||||
\end{rSubsection}
|
||||
|
||||
\end{rSection}
|
||||
|
||||
\begin{rSection}{Education}
|
||||
\compactentry{M.Eng. Computer Aided Engineering (Software Design \& Engineering), Universit\"at der Bundeswehr M\"unchen}{Apr 2012 -- Oct 2013}
|
||||
Thesis at Tongji University, Shanghai: \textit{Development of a Web-Based Remote Fault Diagnosis System}; grade 1.0.
|
||||
|
||||
\compactentry{B.Eng. Information and Telecommunication Technologies, Universit\"at der Bundeswehr M\"unchen}{Oct 2009 -- Oct 2012}
|
||||
\end{rSection}
|
||||
|
||||
\end{document}
|
||||
@@ -0,0 +1,88 @@
|
||||
# Aker BP ASA — Data Product Architect, AI-ready Data Products
|
||||
|
||||
- Source: https://www.finn.no/job/fulltime/ad.html?finnkode=469067315 (FINN-kode 469067315)
|
||||
- Apply: https://www.finn.no/job-apply/469067315/apply
|
||||
- Retrieved: 2026-07-29
|
||||
- Retrieval method: FINN ad page fetched directly, HTML stripped to text — verbatim body below
|
||||
- Cross-checked against: arbeidsplassen.nav.no (NAV national register), ad uuid 8958b122-51ff-4f61-88be-de60c4dae1a1
|
||||
- Posting status: LIVE — apply control visible; last modified 2026-07-06
|
||||
- Locations: Stavanger, Oslo, Trondheim (registered sites 1366 Lysaker, 4020 Stavanger, 7011 Trondheim)
|
||||
- Employment type: Fast (permanent), 100%
|
||||
- Working language: English (NAV `workLanguage: ['Engelsk']`; JD requires "fluent English, written and spoken")
|
||||
- Application deadline: 02.08.2026
|
||||
- Contact: Per Olav Marthinsen — per.marthinsen@akerbp.com
|
||||
- Employer sector: Private, oil and gas. NAV job function tags: IT-sikkerhet, Systemarkitekt, Utvikler (generell)
|
||||
|
||||
## Body (verbatim)
|
||||
|
||||
Aker BP aims to be the exploration and production company of the future by transforming the way we work and operate. We are setting new standards by focusing on safe production and low emissions in the oil and gas industry.
|
||||
|
||||
We have big plans - do you want to join us?
|
||||
|
||||
This position is part of Data Delivery which amongst other have the responsibility for the data product governance framework and data catalogue.
|
||||
|
||||
As part of the Data Platforms & Delivery organization, you will help shape how Aker BP governs and enables AI ready data products across the enterprise.
|
||||
|
||||
You will work closely with the Data Product Governance Lead and the Data Catalogue Owner to evolve our governance framework, establish best practices, and ensure our data products are trusted, discoverable and ready for analytics, automation, AI and intelligent agents.
|
||||
|
||||
Our data products range from datasets and semantic models to reports, applications, APIs, machine learning models and AI products.
|
||||
|
||||
### Typical work tasks can be:
|
||||
|
||||
- Develop and evolve the Data Product Governance Framework, ensuring trusted, reusable and AI-ready data products
|
||||
- Define governance principles, architecture patterns and lifecycle practices for data products across the organization
|
||||
- Establish practical standards for metadata, lineage, ownership, data quality and business context
|
||||
- Collaborate with platform teams, architects and product teams to improve discoverability and adoption of governed data products
|
||||
|
||||
### Skills and qualifications:
|
||||
|
||||
- Master's degree in a relevant discipline. Relevant experience may compensate for formal education
|
||||
- Experience working with modern data architecture, information architecture, data governance or similar disciplines
|
||||
- Experience designing or governing data products, data platforms or analytical solutions
|
||||
- Strong communication skills and fluent English, written and spoken
|
||||
- Ability to collaborate across business and technology domains
|
||||
- Experience with Microsoft Purview, Collibra, Alation or similar metadata/catalogue platforms
|
||||
- Understanding of how governed data products enable analytics, AI and automation
|
||||
- Experience working with cloud data platforms or modern data ecosystems
|
||||
- Experience from energy, industrial or other complex enterprise environments
|
||||
|
||||
The successful applicant will be given the necessary training to succeed.
|
||||
|
||||
### We think you will thrive in Aker BP if this resonates with you:
|
||||
|
||||
- Our SAFER values are the foundation for everything we do. Working with us means identifying with being Seekers, Accountable, Foreseeable, Engaged and Respectful.
|
||||
- Aker BP is an AI-first company, committed to leading our industry in AI adoption, moving fast to unlock the full transformative power of AI across the business. We put AI at the core of how we work, innovate, and create value, from automating routine tasks to enabling smarter decisions and strengthening data security.
|
||||
- Cooperation is the very core of Aker BP. Working with us means wanting to be part of our ONETEAM-culture.
|
||||
- At Aker BP, we put safety first. When working with us, we expect you to do the same.
|
||||
- You like to work in teams, and you are a good and effective communicator.
|
||||
- You like to see the bigger picture and how things are connected.
|
||||
|
||||
### Our commitment to you:
|
||||
|
||||
- We are convinced diversity is an important element for success, and everyone in Aker BP should feel involved, included, and respected.
|
||||
- We want you to develop. That's why we are committed to providing you with varied experience and enhancing your expertise so you can build a CV for the future!
|
||||
- We will offer you a competitive compensation package including a share savings program, and a solid pension scheme.
|
||||
- We know that your health and a work-life balance are key factors for job satisfaction. That's why we have good cafeterias, work-out facilities, and flexibility - in working hours.
|
||||
- If something should happen to you, we will make sure you get help from the company health service and our insurance programs.
|
||||
- Our offices have a universal design - accessible for all.
|
||||
|
||||
Locations: Stavanger, Oslo, Trondheim
|
||||
Application deadline: 02.08.2026
|
||||
|
||||
Background checks will be performed, following consent from relevant candidates. We ask that you enclose your diploma/grade transcript with your application. Furthermore, an assessment of affiliation to high-risk countries is carried out as part of the recruitment process for all positions in Aker BP.
|
||||
|
||||
Contact information: Per Olav Marthinsen - per.marthinsen@akerbp.com
|
||||
|
||||
## About the employer (verbatim)
|
||||
|
||||
Aker BP is a company engaged in exploration, field development and production of oil and gas on the Norwegian continental shelf. The company operates six field centres: Alvheim, Ivar Aasen, Skarv, Edvard Grieg, Ula and Valhall, and is a partner in the Johan Sverdrup field.
|
||||
|
||||
Our headquarter is in Fornebu, outside of Oslo, and we have offices in Stavanger, Trondheim, Harstad and Sandnessjøen.
|
||||
|
||||
## Screening notes (not part of the JD)
|
||||
|
||||
- **Diploma/transcript required with the application.** Not optional — the ad says "We ask that you enclose your diploma/grade transcript."
|
||||
- **High-risk-country affiliation assessment.** Standard for Norwegian continental-shelf operators. Dennis's M.Eng. thesis was carried out at Tongji University, Shanghai (2013). Factual and already on the CV; expect it to surface in screening and answer it plainly rather than omitting it.
|
||||
- **No Norwegian-language requirement and no Norwegian security clearance requirement** — both distinguish this from the Telenor Norge reqs assessed 2026-07-29.
|
||||
- **Catalogue-tool gap is real:** Purview / Collibra / Alation appear in the qualification list, and `claims.json` has zero evidence for any of the three, nor for a named lineage or catalogue product. Mitigated by "The successful applicant will be given the necessary training to succeed."
|
||||
- **Scope caution (see CLAUDE.md Scope Discipline and claims.json SW-7):** the role authors an enterprise governance framework. Dennis's verified scope is building governed data products and onboarding sources *within* Swisscom's company-wide Data Mesh. Never imply he authored or owns Swisscom's framework or mesh.
|
||||
@@ -0,0 +1,59 @@
|
||||
\ProvidesClass{resume}[2026/07/27 Evidence-first professional resume]
|
||||
\LoadClass[11pt,a4paper]{article}
|
||||
|
||||
\RequirePackage{enumitem}
|
||||
\RequirePackage{ifthen}
|
||||
\RequirePackage{lastpage}
|
||||
\RequirePackage{parskip}
|
||||
\RequirePackage{needspace}
|
||||
|
||||
\pagestyle{empty}
|
||||
\setlength{\parindent}{0pt}
|
||||
|
||||
\def\@resumename{}
|
||||
\def\@resumeheadline{}
|
||||
\def\@resumecontact{}
|
||||
|
||||
\newcommand{\name}[1]{\def\@resumename{#1}}
|
||||
\newcommand{\headline}[1]{\def\@resumeheadline{#1}}
|
||||
\newcommand{\contactline}[1]{\def\@resumecontact{#1}}
|
||||
|
||||
\newcommand{\printresumeheader}{%
|
||||
{\LARGE\bfseries \@resumename}\par
|
||||
\vspace{0.15em}
|
||||
\ifthenelse{\equal{\@resumeheadline}{}}{}{\@resumeheadline\par}
|
||||
\vspace{0.1em}
|
||||
{\small \@resumecontact}\par
|
||||
\vspace{0.45em}
|
||||
}
|
||||
|
||||
\AtBeginDocument{\printresumeheader}
|
||||
|
||||
\newenvironment{rSection}[1]{%
|
||||
\vspace{0.35em}
|
||||
{\bfseries #1}\par
|
||||
\vspace{0.1em}\hrule\vspace{0.35em}
|
||||
}{%
|
||||
\vspace{0.2em}
|
||||
}
|
||||
|
||||
% Arguments: employer, dates, formal title, location.
|
||||
\newenvironment{rSubsection}[4]{%
|
||||
\Needspace{6\baselineskip}%
|
||||
{\bfseries #1}\hfill{\small #2}\par
|
||||
{\itshape #3}\hfill{\itshape #4}\par
|
||||
\vspace{0.1em}
|
||||
\begin{itemize}[leftmargin=1.25em,label=\textbullet,itemsep=0.18em,topsep=0.15em,parsep=0pt,partopsep=0pt]
|
||||
}{%
|
||||
\end{itemize}
|
||||
\vspace{0.25em}
|
||||
}
|
||||
|
||||
\newcommand{\skillline}[2]{%
|
||||
\textbf{#1:} #2\par
|
||||
\vspace{0.08em}
|
||||
}
|
||||
|
||||
\newcommand{\compactentry}[2]{%
|
||||
\textbf{#1}\hfill #2\par
|
||||
}
|
||||
@@ -0,0 +1,157 @@
|
||||
# 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`
|
||||
Reference in New Issue
Block a user