feat(app): BIS jr100498 Senior/Lead Data & Analytics Engineer (MED IT) submitted; KB gaps closed; scout triage 2026-10-14

Application
- BIS Basel, Senior/Lead Data & Analytics Engineer, Monetary and Economic
  Department IT (jr100498, 3-year term): resume, cover letter, verbatim JD,
  session, critique and the four portal free-text answers. Submitted
  2026-10-15 via the BIS portal, cold (Evidence Fit 78 Core, hard gate PASS,
  Document Quality 88 after Tier 2 polish). Different unit from the rejected
  jr100429 (Banking Technology). Recorded in applications.json and
  decisions.json.

Knowledge base
- claims.json: BS-9 and SW-10 (onboarded and mentored junior developers at
  Bosch and Swisscom); skills TIBCO Spotfire, Teradata, Oracle Database and
  Hadoop / Impala registered from existing claim scopes; SDMX registered as
  forbidden (user-confirmed never used); SW-4 scope records the
  prototype-and-iterate approach with B2B business, architects and engineers.
- Clarification note 2026-10-14 with verbatim user answers, including
  "schedule yes, budget no" for project planning (unattributed, so not a
  claim yet).
- CLAUDE.md corrections log: 2026-10-14 entry.

Scout
- 2026-10-14 run (37 companies, 101 new): 19 JDs read; BIS jr100498 taken
  forward; Snowflake Engineering Productivity (mis-titled "Sr SWE,
  Enterprise"), Google SWE III Shopping Graph Feeds and Meta SWE
  Infrastructure logged as maybe; 15 roles logged as skip with the failing
  JD line quoted. Found: BIS RSS adapter stamps every vacancy as Basel
  (jr100491 is Hong Kong); Confluent Ashby board returns no jobs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

output/BIS_Lead_Data_Analytics_MED/JD_bis_senior_lead_data_analytics_engineer.txt

@@ -0,0 +1,111 @@
+Senior/Lead Data & Analytics Engineer - Basel, Switzerland
+Employer: Bank for International Settlements (BIS), Monetary and Economic Department (MED), MED IT unit / MED Data Engineering
+Requisition: jr100498
+URL: https://www.bis.org/vacancy/jr100498
+Retrieved: 2026-10-14 via headless Chromium (job_scout .venv Playwright), rendered page text. Verbatim body below; site navigation and footer removed, nothing else changed.
+Posting status: LIVE on 2026-10-14 (posted 12 Oct 2026, deadline 02 Nov 2026 end of day)
+-----
+
+Application deadline: 02 Nov 2026
+Senior/Lead Data & Analytics Engineer - Basel, Switzerland
+Apply now
+ 
+ 
+ 
+GEOGRAPHICAL LOCATION
+
+Basel, Switzerland
+
+LOCATION
+
+BIS Headquarters Basel
+
+DEPARTMENT
+
+MED Data Engineering
+
+DATE POSTED
+
+12 Oct 2026
+
+APPLICATION DEADLINE
+
+02 Nov 2026
+
+CONTRACT DURATION
+
+3 years
+
+The Bank for International Settlements (BIS) is hiring a Senior/Lead Data & Analytics Engineer within the Monetary and Economic Department, MED IT unit.
+
+Application deadline: Please note that the deadline for applications is Monday 2 November 2026 at the end of day.
+
+Please note that this role is offered as a three-year fixed term contract.
+
+This role is based in Basel, Switzerland; however, thanks to our status as an international organization, we can hire globally and welcome applications from candidates of all nationalities and located anywhere in the world. Relocation support is available for the successful candidate and their dependent family members.
+
+ 
+
+Purpose of the job:
+
+The mission of the BIS is to support central banks' pursuit of monetary and financial stability through international cooperation, and to act as a bank for central banks.
+
+The Monetary Economic Department (MED) supports this mission by gathering and analysing a large array of data and statistics on global financial systems and macro-/micro-economic activity. From this, we generate a variety of insights that are used and relied upon by central banks, financial regulatory institutions, and other stakeholders around the world. Indeed, some of the source data sets we work with and the ways in which we combine them are unique to our organisation.
+
+But we know that our full potential is yet to be achieved. Our aim is to collect a wider variety of data and harness new technology to generate more powerful insights. This is a chance to be involved in a step change in our capability.
+
+ 
+
+By joining the MED IT team, you will:
+
+Directly contribute to our mission as a part of a collaborative team who are solving a range of complex data and software challenges, including data management, advanced analytics, and business intelligence.
+Lead the design and delivery of data and analytics applications, platforms, interfaces, and services that support the Bank’s strategic objectives.
+Shape data-driven solutions by translating complex business needs into effective architectures, insights, and technology improvements.
+Help us explore and exploit cutting-edge technologies, including AI and Machine Learning, Lakehouse engineering, high-performance computing, Kubernetes ecosystems, and big data platforms.
+Find yourself looking outwards and collaborating; not just among the team but with expert economists, technologists, data scientists and statisticians – and counterparts in other international organisations and central banks.
+
+ 
+
+Principal Accountabilities:
+
+Partner with MED stakeholders to define and implement the IT strategy and target architecture for statistical and analytical applications, ensuring alignment with security, IT governance, and data management standards.
+Gather business requirements and translate into IT solutions.
+Lead the design and implementation of data and analytics applications, interfaces, and services.
+Support official-statistics data collection and dissemination programmes, international data standards, particularly the Bank’s SDMx activities.
+Oversee data collection mechanisms and their alignment with data architecture, working with internal and external stakeholders to maintain data quality and accuracy.
+Apply advanced, responsible AI/ML methodologies to streamline, automate, and enhance business operations and processes (e.g., document processing, anomaly detection, forecasting).
+Provide technical guidance and end-user support, oversee production support activities, and ensure timely resolution of issues.
+Support IT project and product management, including resource planning, delivery tracking, and preparation of materials for IT steering committees.
+Maintain effective stakeholder relationships, support junior colleagues, and represent the BIS at external events when required.
+Maintain professional knowledge of data and analytics engineering, technology, regulation, and industry best practice through ongoing development and external engagement.
+
+ 
+
+Qualifications, skills and experience:
+
+Bachelor’s degree or equivalent qualification.
+More than six years’ relevant experience, including substantial experience in data and analytics engineering or a related field.
+Experience providing general supervision and task-specific guidance to junior colleagues.
+Advanced ability to acquire, organise, protect, process, and analyse data, identifying patterns, trends, and insights to support decision-making.
+Proficiency in querying databases, using database reporting and business intelligence tools, and working with query languages and data conversion techniques.
+Experience analysing, modelling, and documenting data flows, state changes, processes, requirements, use cases, and user stories.
+Ability to design architectures that incorporate system and service requirements and to develop software using relevant programming languages.
+Ability to plan and manage small project assignments within agreed cost, time, and quality parameters.
+Ability to interpret and apply policies and procedures in alignment with organisational strategy and objectives.
+Strong stakeholder-management, communication, problem-solving, and technical-support skills.
+
+Please note that the BIS's corporate language is English, which is used for all internal and external communication.
+
+ 
+
+Who we are:
+
+Internationalism is at the core of our identity and the best representation of this is our workforce. With employees from over 66 countries and offices in nine locations, the BIS is a global organisation with a truly international workforce. By joining us, you will work in a unique, highly rewarding, and international work environment. We are committed to equal opportunities at the BIS and aim to build a workforce that reflects our global membership. We strive to attract the best talent and foster an inclusive environment. We welcome applications from all qualified candidates, including those with a breadth of professional experience. You can discover more about our inclusive working environment here. 
+
+ 
+
+What the BIS offers:
+
+We want your time at BIS to be a rewarding and career-enriching experience. We offer an agile and flexible working environment with hybrid working opportunities including home office and working from abroad days. To support our international applicants, we offer relocation support that extends to your dependent family members. In addition, we offer a competitive compensation and benefits package, including support for working families including childcare and education allowances (where applicable). Finally, we offer a genuinely unique international working environment, which will give you exposure to the global financial system and the opportunity to collaborate with passionate experts from all over the world. 
+
+#LI-FC1

output/BIS_Lead_Data_Analytics_MED/critique_bis_senior_lead_data_analytics_engineer.md

@@ -0,0 +1,145 @@
+# Critique: BIS Basel — Senior/Lead Data & Analytics Engineer (MED IT, jr100498)
+
+Date: 2026-10-14. Rubric: `critique_framework.md` (2026-09-11).
+Documents: `e2e_bis_senior_lead_data_analytics_engineer_resume.tex/.pdf`, `e2e_bis_senior_lead_data_analytics_engineer_cover_letter.tex/.pdf`.
+JD: `JD_bis_senior_lead_data_analytics_engineer.txt`, verbatim, live on 2026-10-14.
+
+> **Self-review caveat.** This critique was written in the same session that produced the documents. Treat its leniency with suspicion. The claim audit below was done line by line against `claims.json`, not against the session plan.
+
+## 1. Fit verdict and hard gates
+
+**Core. Hard gate PASS.** No required qualification is a Gap.
+
+| Gate check | Result |
+|---|---|
+| Minimum/required qualification a Gap? | No. Nine of ten Direct. Q8 (*"plan and manage small project assignments within agreed cost, time, and quality parameters"*) is Adjacent: the user confirmed schedule responsibility but **no budget responsibility**, and no project is attributed, so nothing on the page shows it. |
+| Title-defining capability not Direct? | No. Data and analytics engineering is Direct (SW-1/2/4/7, BS-2/3/8). |
+| Level needs absent scope? | No. "Lead" asks for supervision and guidance of juniors, not line management. BS-9/SW-10 (onboarding and mentoring) plus BS-7 cover it, though unquantified. |
+| Location / authorization / relocation unresolved? | No. Basel is about 90 min from Thun, and memory accepts the commute for BIS tax-free pay. Office days are not stated, so ask at first contact. The 3-year fixed term against his permanent Swisscom post is a real trade-off for the user to weigh, not a gate. |
+
+## 2. Evidence Fit — 78/100 (Core)
+
+| Dimension | Weight | Score | Reason |
+|---|---:|---:|---|
+| Required qualifications | 35 | 31 | Direct: degree, >6 yrs, junior guidance, data handling, querying + BI, modelling/documenting flows and user stories, design + development, policies, stakeholders/support. Adjacent: project planning (no cost/budget). |
+| Core responsibilities | 25 | 18 | Direct: lead design/delivery within his scope, requirements → solutions, data collection and quality, production support, external events (TAF 2022). Gap: SDMX / official-statistics programmes. Adjacent: IT strategy and target architecture for MED, steering-committee material, AI/ML (integration and a PoC, not model work). |
+| Level and ownership | 15 | 11 | Staff title, component and application owner, mentors juniors. Design authority beyond his own data products is not established. |
+| Recency and depth | 10 | 8 | Lakehouse data-product work is current. BI evidence is 2020–22 (Spotfire) and ART B2B (dashboards); both are past. |
+| Domain/tool transfer | 10 | 6 | Central-bank / official-statistics domain is new. SDMX and HPC absent. Python/SQL/lakehouse/Kubernetes transfer directly. |
+| Practical constraints | 5 | 4 | Commute workable; office days unknown; fixed term. |
+
+Unchanged from the session's pre-critique score. Nothing in the documents changes the fit.
+
+## 3. Document Quality — 86/100 (resume)
+
+| Dimension | Weight | Score | Reason |
+|---|---:|---:|---|
+| Truth and provenance | 25 | 24 | Every bullet traces to a canonical claim within scope (audit in §6). −1: the skills block lists historical tools (Kafka, Kubernetes, Ansible) without a recency mark while the Programming line marks Java/C#/Kotlin "historical". This is inconsistent, and a reader may take Kafka/Kubernetes as current. The 2026-09-15 log specifically warns against presenting Swisscom Kubernetes/Kafka as current. |
+| Information hierarchy | 20 | 17 | Clean employer/title/date hierarchy, with promotions shown at Swisscom and Bosch. Experience starts at 45.8% of page 1, which is fine. The skills block renders at 9 lines, just over the 4–8 guide. The Bosch entry splits 3/2 across pages, which is acceptable. The header-only Bundeswehr line reads as intentional. |
+| Bullet evidence and impact | 20 | 15 | Specific and scoped, with systems, data types and responsibilities named. No outcomes or metrics anywhere, correctly, since none are verified. The cost is that a "Lead" reader sees activity rather than results. BS-1 is the only bullet with a stated consequence. |
+| Relevance and terminology | 15 | 12 | Covers data and analytics engineering, BI (Spotfire), data quality, requirements, backlog/user-story work, modelling, lakehouse, Kubernetes, ML and anomaly detection, junior guidance and an external talk. Statistics/SDMX/central-bank vocabulary is honestly absent. "Business intelligence" appears only as "BI". |
+| Skills evidence | 10 | 9 | All canonical. `pytest` is `allowed-with-context`; its context (unit tests at Swisscom) is carried only by "unit-tested" in the SW-1 bullet, which is acceptable but thin. |
+| Mechanics/readability | 10 | 9 | Compiles, 2 pages, 0 box warnings, parses in order, validator 0 cadence warnings. Triples are in about 5 of 13 bullets, under half. −1: three bullets open with "Developed" (BS-2, FC-1, VZ-2), and the FC-1/VZ-2 pair is adjacent in reading order. |
+
+## 4. Channel Strength — Weak
+
+Tailored cold application. No named contact is published; the only lead is the `#LI-FC1` LinkedIn recruiter tag. BIS says it hires globally, so a cold pool will be large. The last BIS cold submit (jr100429) was rejected without interview.
+
+Warm actions, in order of cost:
+1. Search LinkedIn for BIS talent acquisition with initials F.C. (the `#LI-FC1` tag) and send a 3-line note naming jr100498.
+2. Search LinkedIn for "Bank for International Settlements" + "MED" / "Monetary and Economic Department" + data engineer, to find a team member for a short question about the role.
+3. Check for former Swisscom, Bosch or Fraunhofer colleagues now at BIS.
+
+## 5. Competitive read and reader sequence
+
+- **Obvious-fit competitor:** a data engineer from a central bank, statistical office or regulator, with SDMX collection/dissemination work and BI for economists.
+- **Dennis's real advantage:** the modern lakehouse stack the posting wants to explore, in current hands-on use; production ownership with governance and on-call; relational modelling of governed data products with metadata and lineage; a demonstrated habit of building close to domain specialists (fab engineers).
+- **Competitor's real advantage:** SDMX and statistics-domain fluency; a central-bank network; experience with economists as users. A bridge is not worth as much as that direct evidence.
+
+| Reader | Verdict | Reason / first challenge |
+|---|---|---|
+| Parser/ATS | Pass | Clean text extraction. Plain-text mode groups "employer + title" then "dates + location", which is normal for this template. Core terms present; SDMX absent (true). |
+| Recruiter glance | Forward | 11 years visible, Staff title, "Data, Analytics & AI Engineer" maps to the req title, Swiss-based, English. |
+| Hiring manager (MED IT) | Maybe → Interview | Strong engineering and stack. Doubts: no statistics/central-bank domain; "Lead" evidence is mentoring rather than leading delivery for a business unit. |
+| Technical reviewer | Credible | Likely first challenges: how the Glue jobs are unit-tested; what data-quality controls the Teradata ETL had; which tool the Swisscom dashboards were built in (**not recorded in the KB, so prepare an answer**); what the coordinate-system normalisation actually involved. |
+
+## 6. Claim audit
+
+| Claim | Canonical ID | Direct/Adjacent | Safe? | Fix |
+|---|---|---|---|---|
+| Headline "Staff Data, Analytics & AI Engineer" | SWISSCOM `display_title` | Direct | Yes | — |
+| Headline "AWS Lakehouse & BI" | SW-1/SW-7; BS-5 | Direct (BI historical) | Yes | Optional: BI is not current work (Tier 2) |
+| "over ten years in software and data engineering" | Visible record May 2015 → about 11.4 yrs | Direct | Yes | — |
+| "Currently designs and builds governed relational data products on AWS (Glue, Iceberg, Athena)" | SW-7, SW-1 | Direct | Yes | — |
+| "technical Application Owner for the fab's Spotfire analytics environment" | BS-5, BS-3 | Direct | Yes | — |
+| Skills: Kafka, Kubernetes, Ansible unmarked | skills (production-historical) | Direct, historical | Yes, but recency is ambiguous | Tier 2 #1 |
+| Skills: Oracle Database, Teradata, Hadoop/Impala, Spotfire | skills, registered 2026-10-14 from SW-2/BS-2/BS-5/BS-8 | Direct, historical | Yes | — |
+| Skills: pytest | skills (allowed-with-context, SW-9) | Direct | Yes (context via SW-1 bullet) | — |
+| SW-7 bullet | SW-7 | Direct | Yes; "within Swisscom's company-wide Data Mesh" keeps scope | — |
+| SW-1 bullet: "in owned domains … contributing to Swisscom's wider cloud migration" | SW-1, SW-6, SW-9 | Direct | Yes | — |
+| SW-2 bullet (past tense) | SW-2 | Direct | Yes | — |
+| SW-4 bullet: "Translated … requirements into data products and dashboards; shaped and prioritised backlog items" | SW-4, SW-3 | Direct | Yes (both ART B2B, past) | Prepare: dashboard tool name |
+| "Onboarded and mentored junior developers" (Swisscom) | SW-10 | Direct | Yes; past tense because phase not recorded | — |
+| BS-3/5 bullet, "co-owned TIBCO Spotfire environment" | BS-3, BS-5 | Direct | Yes | — |
+| BS-2 bullet | BS-2 | Direct | Yes | — |
+| BS-8 bullet: "including performance tuning; co-presented … TIBCO Analytics Forum 2022" | BS-8, BS-5 | Direct | Yes. Tuning stated at canonical level, no query/index claim | — |
+| BS-1/4 bullet: failure-consequence wording; "proof of concept" | BS-1, BS-4 | Direct | Yes. No model-training claim; PoC labelled | — |
+| BS-9/7 bullet: "one Bachelor thesis" | BS-9, BS-7 | Direct | Yes; not pluralised | — |
+| FC-1 bullet (no quality-gate claim) | FC-1 | Direct | Yes | — |
+| VZ-2 bullet | VZ-2 | Direct | Yes | Tier 2 #3 (verb) |
+| GN-1 bullet | GN-1 | Direct | Yes | — |
+| Bundeswehr header line | BW-1 | Context only | Yes; no command or clearance claim | — |
+| Capgemini | document_exclusions | — | Correctly absent | — |
+
+Forbidden-term scan: validator PASS (no SDMX, LangChain, GitOps, Terraform, Snowflake or global forbidden patterns).
+
+## 7. Fixes
+
+**Tier 1 (truth/fit): none.**
+
+**Tier 2 (presentation, optional):**
+1. **Skills recency.** Mark historical tools consistently, e.g. "Kafka (historical)" and "Kubernetes, Ansible (historical)", or drop the "historical" label from the Programming line. Recommended: add the marks. It costs no extra line on the Data engineering line; check the Platform line wrap.
+2. **Headline "AWS Lakehouse & BI".** BI is 2020–22 and ART B2B work. Defensible as identity, but a "Data Quality" or "Data Governance" third term would be current. Low priority.
+3. **Opening-verb repetition.** VZ-2 directly follows FC-1 and both open "Developed". Reshape VZ-2, e.g. "Automated product testing with test suites wired into the CI/CD pipeline as quality gates."
+
+**Interview preparation (not document changes):**
+- Name the Swisscom dashboard tool (SW-4); the KB does not record it.
+- Have one attributed example for "schedule yes, budget no" (Q8). Recording which project it was would also let it enter `claims.json`.
+- Prepare an honest SDMX answer: never used; how data collection, validation and metadata work in SW-2/SW-7 maps to it; how you would learn the standard.
+- Prepare a "Lead" story: a design you drove end to end within your own data products, plus how you guide juniors.
+- Decide in advance how you weigh a 3-year fixed term against the permanent Swisscom post.
+
+## 8. Cover letter
+
+- **Should it exist?** Yes. BIS is a mission-led international institution, the portal accepted a letter for jr100429, and the letter adds motivation the resume cannot show.
+- **Adds information:** yes. It explains why MED (data central banks and regulators rely on), and a working style built close to domain specialists, tied to MED's economists and statisticians. Paragraph 1 was rewritten before review because the first draft reworded two resume bullets.
+- **Hooks:** only the posting itself (first-party, saved verbatim). No unverified programme, product or statistic.
+- **Claims:** all present in both `claims.json` and the resume; "co-owned" Spotfire kept; mentoring tense-safe.
+- **Weaknesses:** "Dear Hiring Team" is unavoidable without a contact. The Lead dimension is carried only by mentoring. The literal date must be updated at submission.
+- **Would deleting it improve the application?** No.
+- Length: 237 words, one page, 0 box warnings.
+
+## 9. Mechanical verification
+
+- `validate_resume_system.py --document <resume> --document <letter>`: PASS, 0 errors, 0 warnings.
+- MiKTeX pdflatex, 2 passes each: resume 2 pages, letter 1 page, 0 overfull/underfull boxes.
+- PDF metadata: Title/Author empty; Producer MiKTeX pdfTeX; no generator-term leakage.
+- `pdftotext`: header → summary → skills → experience in reverse chronology → Bundeswehr → education; employer/title/date order intact; no LaTeX leaking into text.
+- `page_metrics.py`: experience starts at 45.8% of page 1; 52 text lines, 408 words on page 1.
+- Visual: both resume pages and the letter inspected at 80 dpi; no clipping, overlap or isolated headings.
+
+## Verdict
+
+**Recommended for submission after a warm-channel attempt**, with or without the three Tier 2 polish items. Core 78, hard gate PASS, Document Quality 86, channel Weak.
+
+## Re-report after fixes (2026-10-15)
+
+User: "apply the polish items and finalize".
+
+| Tier 2 item | Outcome |
+|---|---|
+| 1. Skills recency | **Fixed.** "Kafka (historical)"; Platform line now reads "AWS, CloudFormation, Docker; Kubernetes, GitLab CI/CD, Linux, Ansible (historical)". GitLab CI/CD (SW-3/BS-6, both past) and Linux (professional side ended 2022) were moved into the historical group too. pytest moved to the Programming line, where it keeps the Platform line to one rendered line without a hyphenated "(his-torical)". |
+| 2. Headline | **Fixed.** Now "Staff Data, Analytics & AI Engineer \| Governed Data Products & Pipelines \| AWS Lakehouse": current work only (SW-7, SW-1). |
+| 3. Opening-verb repetition | **Fixed.** VZ-2 now reads "Automated testing through test suites connected to the CI/CD pipeline as quality gates." |
+
+Post-fix verification: validator PASS on resume + letter (0 errors, 0 warnings); MiKTeX compile 0 box warnings; resume 2 pages, experience starts at 45.8% of page 1; letter 1 page, date set to 15 October 2026; both inspected at 80 dpi. Document Quality is re-rated **88/100**: truth/provenance +1 (recency now explicit), mechanics +1 (verb repetition gone). Evidence Fit unchanged at 78 (Core); channel unchanged (Weak).

output/BIS_Lead_Data_Analytics_MED/e2e_bis_senior_lead_data_analytics_engineer_cover_letter.tex

@@ -0,0 +1,50 @@
+% BIS Basel - Senior/Lead Data & Analytics Engineer, MED IT (jr100498). Cover letter.
+% Claims used: SW-7, SW-2, BS-3/BS-5, BS-2, BS-8, BS-9/SW-10 - all present in the resume.
+% Employer hook: the posting itself (https://www.bis.org/vacancy/jr100498, saved verbatim in this folder).
+
+\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}
+Bank for International Settlements\\
+Monetary and Economic Department, MED IT\\
+Basel, Switzerland
+
+\vspace{1em}
+% Literal date, set at finalization. Update to the actual sending date if it differs (deadline 2 Nov 2026).
+15 October 2026
+
+\vspace{1em}
+\textbf{Application for Senior/Lead Data \& Analytics Engineer (jr100498)}
+
+\vspace{0.8em}
+Dear Hiring Team,
+
+Your posting describes MED's aim to collect a wider variety of data and use newer technology, including lakehouse engineering, for a step change in capability. That is close to my current work: at Swisscom I build data products on an AWS lakehouse stack with Iceberg and Athena, after owning ETL components that kept business-critical data flowing into a warehouse. The appeal of MED is applying that experience to data that central banks and financial regulators rely on.
+
+My most useful work has been done close to the specialists who use the data. At Bosch I was technical Application Owner for the co-owned Spotfire environment and the defect management system used by fab engineers, and I built data services for their analysis teams. One of the hardest parts was normalising spatial wafer data across the different coordinate systems of the fab's tools so that it could be analysed together at all. Combining sources that were never designed to fit, for economists and statisticians who depend on the result, is the kind of problem I want to work on.
+
+I have worked in Germany, Norway and Switzerland and enjoy international teams. At Bosch and Swisscom I have also onboarded and mentored junior developers, which I see as part of a senior role rather than an extra. I would welcome a conversation about how I could contribute to MED's data and analytics engineering.
+
+Kind regards,
+
+\vspace{1.5em}
+Dennis Thiessen
+
+\end{document}

output/BIS_Lead_Data_Analytics_MED/e2e_bis_senior_lead_data_analytics_engineer_resume.tex

@@ -0,0 +1,85 @@
+% BIS Basel - Senior/Lead Data & Analytics Engineer, MED IT (jr100498).
+% International Tech profile, English. Generated 2026-10-14 from claims.json and the
+% experience files; no historical output used as a source.
+
+\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}
+\hyphenation{semiconductor}
+\pagestyle{fancy}
+\fancyhf{}
+\renewcommand{\headrulewidth}{0pt}
+\fancyfoot[R]{\small \thepage/\pageref{LastPage}}
+
+\name{Dennis Thiessen, M.Eng.}
+\headline{Staff Data, Analytics \& AI Engineer $\vert$ Governed Data Products \& Pipelines $\vert$ AWS Lakehouse}
+\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}
+{\sloppy Data and analytics engineer with over ten years in software and data engineering across telecom, semiconductor manufacturing, research and insurance. Currently designs and builds governed relational data products on AWS (Glue, Iceberg, Athena). Previously at Bosch: technical Application Owner for the fab's Spotfire analytics environment and ML inference integration in 24/7 production.\par}
+\end{rSection}
+
+\begin{rSection}{Skills}
+\skillline{Programming}{Python, SQL, pytest; Java, C\# and Kotlin (professional, historical)}
+\skillline{Data engineering}{PySpark, Airflow, AWS Glue, Apache Iceberg, Athena, Redshift, Kafka (historical); relational data modelling}
+\skillline{Databases and BI}{Oracle Database, Teradata data warehouse, Hadoop/Impala; TIBCO Spotfire}
+\skillline{Platform}{AWS, CloudFormation, Docker; Kubernetes, GitLab CI/CD, Linux, Ansible (historical)}
+\skillline{Certifications}{AWS Certified Solutions Architect -- Associate; Data Engineering with AWS (Udacity); IBM AI Engineering; iSAQB CPSA-F; ITIL Foundation}
+\skillline{Languages}{German (native), English (fluent)}
+\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 Design and build governed data products within Swisscom's company-wide Data Mesh on AWS: logical and physical relational models, source onboarding, and metadata and lineage in Atlassian Compass.
+\item Migrated legacy ETL pipelines in owned domains to AWS as unit-tested Python/PySpark Glue jobs on Apache Iceberg, Athena and Airflow, contributing to Swisscom's wider cloud migration.
+\item Owned the ETL components that loaded business-critical Fulfillment data from Oracle into the Teradata data warehouse. Accountable for data quality and data-protection compliance, root-cause analysis, and 2nd/3rd-level support with on-call duty.
+\item Translated internal B2B stakeholders' requirements into data products and dashboards; shaped and prioritised backlog items with the Product Owner.
+\item Onboarded and mentored junior developers.
+\end{rSubsection}
+
+\begin{rSubsection}{Robert Bosch Semiconductor Manufacturing Dresden GmbH}{Feb 2020 -- Dec 2022}{Senior Data Engineer, Data Analysis (promoted from Data Engineer, Jan 2021)}{Dresden, Germany}
+\item Served as technical Application Owner for the KLA Defect Management System and the co-owned TIBCO Spotfire environment, defining SLOs, working with vendors and internal customers, and delivering user training and documentation.
+\item Developed data services and analysis applications in Python, Java and C\# (including Spotfire extensions) over Oracle and Hadoop/Impala, serving defect-management, wafer-inspection and PCM electrical-parameter data to fab analysis teams.
+\item Normalised spatial wafer data across the differing coordinate systems of fab tools for analysis in Oracle (SDO\_GEOMETRY) and Spotfire, including performance tuning; co-presented the wafer-map work at TIBCO Analytics Forum 2022.
+\item Integrated containerised ML inference for image-based defect classification into the continuously operating fab, where a software defect could have halted production; built an ELK/Kafka anomaly-detection proof of concept.
+\item Mentored junior developers through onboarding, and served as supervisor and second examiner for one Bachelor thesis.
+\end{rSubsection}
+
+\begin{rSubsection}{Fraunhofer-Center for Maritime Logistics and Services CML}{Sep 2018 -- Oct 2019}{Research Software Engineer}{Hamburg, Germany}
+\item Developed C\# crew-scheduling software on Microsoft SQL Server and introduced Jenkins with build jobs for automated deployment.
+\end{rSubsection}
+
+\begin{rSubsection}{Vizrt}{Jul 2017 -- May 2018}{Test Automation / DevOps Engineer}{Bergen, Norway}
+\item Automated testing through test suites connected to the CI/CD pipeline as quality gates.
+\end{rSubsection}
+
+\begin{rSubsection}{Generali Deutschland Informatik Services GmbH}{May 2015 -- Jun 2017}{IT Consultant}{Hamburg, Germany}
+\item Introduced behaviour-driven test automation through a proof of concept, then held technical responsibility for the suite and trained project members to work with it.
+\end{rSubsection}
+
+% Header-only entry by user decision 2026-10-14 (BW-1: organisational context only).
+\Needspace{3\baselineskip}%
+{\bfseries Bundeswehr (German Armed Forces)}\hfill{\small Jul 2008 -- Nov 2014}\par
+{\itshape Officer Candidate / Officer (Second Lieutenant at separation)}\hfill{\itshape Germany}\par
+
+\end{rSection}
+
+\begin{rSection}{Education}
+\compactentry{M.Eng. Computer Aided Engineering}{Apr 2012 -- Oct 2013}
+Universität der Bundeswehr München; focus Software Design \& Engineering.
+
+\compactentry{B.Eng. Information and Telecommunication Technologies}{Oct 2009 -- Oct 2012}
+Universität der Bundeswehr München.
+\end{rSection}
+
+\end{document}

output/BIS_Lead_Data_Analytics_MED/portal_answers_bis_jr100498.md

@@ -0,0 +1,41 @@
+# BIS jr100498 — portal free-text answers
+
+Submitted 2026-10-15 with the resume and cover letter. These are the answers **as drafted in the session**. The user pasted them into the portal and may have edited them; treat this as the best available record, not a verbatim copy of the submission.
+
+Sources: `claims.json` (GN-1/GN-3, FC-1..3, BW-1, VZ, EDU-MENG, SW-1/2/3/4/7, BS-1/2/3/5/6) and the user clarifications of 2026-10-14/15 (`knowledge_base/extractions/2026-10-14_mentoring_spotfire_sdmx_clarification.md`).
+
+## Q1. Have you previously worked in an international organisation, financial institution, central bank or other public authority (eg NSO)? Please describe your experience.
+
+Not in an international organisation, central bank or national statistics office. The closest experience: from 2015 to 2017 I was an IT consultant at Generali Deutschland Informatik Services, the IT services company of the Generali insurance group, working on Java development and test automation for a workflow application. From 2018 to 2019 I worked at Fraunhofer CML, a publicly funded applied-research institute, where I developed software for research projects. Before that I served six years in the Bundeswehr as officer candidate and officer, leaving as Second Lieutenant, and earned both of my degrees at the Bundeswehr University Munich. I have also worked internationally, in Norway at Vizrt, and wrote my master's thesis at Tongji University in Shanghai.
+
+## Q2. Do you have previous experience working with the SDMX, XBRL or other relevant standards? Please provide details.
+
+I have no experience with SDMX or XBRL. The closest work is at Swisscom, where I model governed data products as logical and physical relational models and document their metadata and lineage in a data catalogue (Atlassian Compass). Our lakehouse tables use the open Apache Iceberg table format. SDMX keeps data structures and metadata separate, which is familiar from that work, but the standard itself is something I would need to learn on the job.
+
+> Note: SDMX "never used" is user-confirmed (2026-10-14). XBRL was never asked about; "no XBRL" was flagged to the user for confirmation before pasting.
+
+## Q3. Please describe your experience designing and implementing data or analytics applications, interfaces, or services. Include an example of a solution you delivered, outlining your role, the technologies used, and the outcome.
+
+At Swisscom I design and build governed data products on AWS, and I migrated legacy ETL pipelines in my domains to Python/PySpark Glue jobs on Iceberg, Athena and Airflow. At Bosch I built data services over Oracle and Hadoop/Impala for the fab's analysis teams, and I was technical Application Owner for Spotfire and the defect management system.
+
+Example: ML inference service in a 24/7 semiconductor fab (Bosch, 2020–2022).
+
+Role: I devised and executed the strategy for integrating an image-based defect-classification model into production. The model itself was developed by others.
+
+Technologies: Python, Docker, Kubernetes and Ansible, on Linux servers I administered.
+
+Constraint: the fab runs continuously, and a software defect could in the worst case have halted production.
+
+Outcome: defect classification was automated in production, which reduced manual classification work for the engineers. The reduction was not quantified.
+
+## Q4. Please describe your experience gathering and translating business requirements into technical solutions through stakeholder interviews, workshops, or workflow analysis. Include a specific example, explaining how you managed differing stakeholder perspectives and ensured that the solution met business needs.
+
+At Swisscom I worked with internal B2B stakeholders and product owners to turn their requirements into data products, dashboards and analyses, and I shaped and prioritised the resulting backlog items with the Product Owner. Today I design and model governed data products on AWS, from the relational model to source onboarding and documented metadata and lineage. At Bosch I was technical Application Owner for the defect management system and the Spotfire environment, and I handled communication between the software vendors and the fab's internal users, defined SLOs, trained users and wrote documentation. Earlier, at Generali, I gathered requirements for new automated test cases and introduced behaviour-driven development, where tests are written as business-readable scenarios.
+
+A specific example is a data product I delivered for B2B stakeholders at Swisscom. The B2B business side, the architects and the engineers each brought their own requirements, and these could not be fully settled up front. Rather than waiting for complete agreement or a finished specification, I built a prototype, proposed it to all three groups and then iterated on it with their feedback. The prototype gave everyone something concrete to react to, and each iteration brought it closer to what the business needed. It took more iterations than a fully specified approach would have, but in my judgement we reached the result much faster than if we had waited for agreement first.
+
+## Interview follow-ups these answers invite
+
+- Q2: be ready to explain how you would learn SDMX, and what "data structures and metadata separate" means in your Compass/relational-model work.
+- Q3: the integration strategy. What made it safe in a fab where a defect could halt production? How was the rollout done?
+- Q4: which B2B data product this was; what the business, architects and engineers each wanted; how many iterations; what "much faster" was compared with.

output/BIS_Lead_Data_Analytics_MED/resume.cls

@@ -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
+}

output/BIS_Lead_Data_Analytics_MED/session_bis_senior_lead_data_analytics_engineer.md

@@ -0,0 +1,152 @@
+# Session: Bank for International Settlements (BIS) — Senior/Lead Data & Analytics Engineer (MED IT, jr100498)
+
+## JD Integrity
+- File/source: `JD_bis_senior_lead_data_analytics_engineer.txt` (this folder); https://www.bis.org/vacancy/jr100498
+- Retrieval method and date: headless Chromium via the job_scout `.venv` Playwright, rendered page text, 2026-10-14. Raw render kept at `job_scout/reports/2026-10-14-fit-sources/bis_lead_data_analytics_eng.txt`.
+- Verbatim posting: YES (only site navigation and footer removed)
+- Posting status: LIVE 2026-10-14. Posted 12 Oct 2026; deadline **Monday 2 Nov 2026, end of day**. 3-year fixed-term contract, Basel HQ, MED IT unit (department field: MED Data Engineering).
+
+## Application Decision
+- Audience profile: International Tech (English is BIS's corporate language; international organisation, not a traditional Swiss employer). 2 pages, no photo.
+- Evidence Fit: **78/100**
+- Fit class: **Core**
+- Hard gate: **PASS**. No required qualification is a Gap. Junior supervision moved from Partial to Direct after the 2026-10-14 user clarification (BS-9, SW-10). Project planning is Adjacent, not a Gap.
+- Channel Strength: Weak (tailored cold application)
+- Channel plan: no named contact is published, only the `#LI-FC1` LinkedIn recruiter tag. Before submitting, find the BIS talent-acquisition recruiter (initials FC) or a MED IT engineer on LinkedIn and send a short note. The last BIS cold submit (jr100429, Banking Technology) was rejected without interview on 2026-09-11.
+- Named contact published? NO
+- Prior BIS history: jr100429 *Senior Data & Analytics Engineer – AI* (Banking Technology), applied 2026-07-10, rejected 2026-09-11 with no interview; closed, so stacking does not apply. **Different department:** this req is MED IT, and its emphasis is data and analytics engineering rather than applied AI.
+- Decision: PROCEED (plan confirmed by the user 2026-10-14: "go")
+
+## Requirements
+| # | Requirement | Required/preferred | Direct/Adjacent/Gap/Constraint | Canonical evidence | Gate? |
+|---|---|---|---|---|---|
+| Q1 | Bachelor's degree or equivalent | Required | Direct | EDU-BENG, EDU-MENG | Yes |
+| Q2 | More than six years' relevant experience, substantial data & analytics engineering | Required | Direct | SWISSCOM 2023–present (SW-1/2/4/7), BOSCH 2020–22 (BS-2/3/8); visible record since 2015 | Yes |
+| Q3 | General supervision and task-specific guidance to junior colleagues | Required | Direct (unquantified) | **BS-9**, **SW-10** (onboarded and mentored junior developers, user-confirmed 2026-10-14), BS-7 (students; one thesis as Zweitpruefer), GN-1 (trained project members in BDD) | Yes |
+| Q4 | Acquire, organise, protect, process and analyse data | Required | Direct | SW-2 (quality, security, data protection, compliance), SW-1, SW-6, BS-2, BS-8 | Yes |
+| Q5 | Querying databases, database reporting and BI tools, query languages, data conversion techniques | Required | Direct | SQL; Oracle, Teradata DWH (SW-2), Athena/Iceberg (SW-1), Hadoop/Impala (BS-2); **TIBCO Spotfire** (BS-5, registered 2026-10-14); CRS normalisation and transformation (BS-8) | Yes |
+| Q6 | Analyse, model and document data flows, state changes, processes, requirements, use cases, user stories | Required | Direct | SW-7 (relational logical/physical models, design, metadata and lineage in Compass), SW-3 (shaped and prioritised backlog with PO), SW-4 | Yes |
+| Q7 | Design architectures incorporating system and service requirements; develop software | Required | Direct (scoped) | SW-7 (design of his data products), BS-1 (designed and executed integration strategy), BS-2, FC-3; iSAQB CPSA-F | Yes |
+| Q8 | Plan and manage small project assignments within cost, time and quality | Required | Adjacent | BS-3 (Application Owner: SLOs, vendors, training), BS-4 (PoC), GN-1 (estimation for new test cases). No formal project-management role | Yes |
+| Q9 | Interpret and apply policies and procedures | Required | Direct | SW-2 (Security and Data Governance compliance), SW-5 (not used) | Yes |
+| Q10 | Stakeholder management, communication, problem-solving, technical support | Required | Direct | SW-2 (2nd/3rd-level support, on-call, root cause), SW-4, BS-3 (vendors, internal customers) | Yes |
+| A1 | Define IT strategy and target architecture for statistical/analytical applications | Accountability | Adjacent | SW-7 design is scoped to his data products; no strategy ownership | No |
+| A2 | Gather business requirements, translate into IT solutions | Accountability | Direct | SW-4, SW-3 backlog | No |
+| A3 | Lead design and implementation of data and analytics applications, interfaces, services | Accountability | Direct (scoped) | SW-7, BS-2, BS-3/BS-5 | No |
+| A4 | Official-statistics collection/dissemination, international data standards, **SDMX** | Accountability | **Gap** | none; SDMX user-confirmed never used, registered `forbidden` 2026-10-14 | No |
+| A5 | Oversee data collection mechanisms; data quality and accuracy | Accountability | Direct | SW-2, SW-7 (source onboarding) | No |
+| A6 | Responsible AI/ML for document processing, anomaly detection, forecasting | Accountability | Adjacent | BS-1 (ML inference integration, not model development), BS-4 (ELK/Kafka anomaly-detection PoC), FC-2 (contribution) | No |
+| A7 | Technical guidance, end-user support, oversee production support | Accountability | Direct | SW-2, BS-3 | No |
+| A8 | Support IT project/product management, materials for IT steering committees | Accountability | Adjacent | SW-3 backlog with PO; no steering-committee evidence | No |
+| A9 | Support junior colleagues; represent the BIS at external events | Accountability | Direct | BS-9, SW-10; BS-5 (co-presented at TIBCO Analytics Forum 2022) | No |
+| T1 | Explore AI/ML, Lakehouse engineering, HPC, Kubernetes ecosystems, big data platforms | Context | Lakehouse Direct (Iceberg/Athena/Glue, current); Kubernetes Direct-historical (SW-3, BS-1); big data Direct (PySpark, Hadoop/Impala); HPC Gap; AI/ML Adjacent | SW-1, SW-6, SW-3, BS-1, BS-2 | No |
+| C1 | Basel, hybrid incl. home office and working-from-abroad days; 3-year fixed term | Constraint | Workable | ~90 min from Thun; memory accepts BIS tax-free pay for that commute. Office-day count NOT stated - ask at first contact | No |
+| C2 | English corporate language | Constraint | Direct | English fluent | No |
+
+### Evidence Fit — 78/100
+| Dimension | Weight | Score | Reason |
+|---|---:|---:|---|
+| Required qualifications | 35 | 31 | Nine of ten Direct; project planning Adjacent |
+| Core responsibilities | 25 | 18 | Design/delivery, requirements, data quality and production support Direct; SDMX/official statistics Gap; IT strategy and steering committees Adjacent |
+| Level and ownership | 15 | 11 | Staff engineer, component and application owner, mentors juniors; "Lead" design authority beyond his own data products is not established |
+| Recency and depth | 10 | 8 | Current AWS lakehouse data products; BI/Spotfire and dashboards are historical (2022 / ART B2B) |
+| Domain/tool transfer | 10 | 6 | Central-bank/official-statistics domain is new; SDMX absent; HPC absent; core tools transfer |
+| Practical constraints | 5 | 4 | Commute and office days to confirm |
+
+## Competitive Read
+- Obvious-fit candidate: a data engineer from a central bank, statistical office or financial regulator, with SDMX and official-statistics collection experience plus BI.
+- Dennis's advantage: a current, hands-on lakehouse stack (Iceberg, Athena, Glue, PySpark, Airflow) of the kind the posting wants to explore; production component and application ownership with governance and on-call; relational modelling of governed data products with metadata and lineage; ML integration in a 24/7 regulated-adjacent industrial environment.
+- Their advantage: SDMX and statistics-domain fluency; existing central-bank network; experience working with economists.
+- Level/scope comparison: matches Senior; "Lead" will probe architecture ownership and steering-committee exposure.
+
+## Framing Strategy
+- Professional identity: Staff data, analytics and AI engineer who designs and builds governed data products and the pipelines behind them, and has owned the analytics applications that business users depend on.
+- Strongest proof points: SW-7 (relational data-product design on AWS lakehouse, metadata/lineage); SW-2 (DWH ETL component ownership with governance and support); BS-3/BS-5 (application owner for Spotfire and DMS); BS-8 (data conversion across coordinate systems); BS-9/SW-10 (junior mentoring).
+- Honest adjacent bridges: Spotfire → BI tools generally; BS-1/BS-4 → applied ML for operations; BS-3 → small-project ownership.
+- Explicit gaps: SDMX/official statistics; HPC; formal project management; IT strategy ownership. Do not paper over any of these in the resume.
+- User directives: none beyond the 2026-10-14 clarifications.
+
+## Resume Plan (confirmed 2026-10-14)
+- Summary: 2–3 lines.
+- Skills: ~5 lines (Programming; Data engineering; Databases and BI; Platform and delivery; Certifications), plus spoken languages.
+- Swisscom (5): SW-7 lead, SW-1 (+SW-6, SW-9), SW-2 (past), SW-4 (past, + SW-3 backlog), SW-10 (short).
+- Bosch (5): BS-3+BS-5 (Application Owner), BS-2, BS-8 (+TAF 2022 from BS-5), BS-1, BS-9+BS-7 (short).
+- Earlier experience: Fraunhofer FC-1 (1); Vizrt VZ-2 (1); Generali GN-1 (1). Bundeswehr header-only line (BW-1) by user decision 2026-10-14. Capgemini omitted.
+- Total bullets: 12–13.
+- Impact evidence still needed: none required. No verified metrics exist for any selected claim; none invented.
+- Q8 follow-up (2026-10-14): user answered "schedule yes, budget no" to bounded-project planning. No project or employer named, so it is recorded in the clarification note only, not as a claim, and is not in any bullet. Q8 stays Adjacent; ask which project if an interview probes it.
+
+## Cover Letter Decision
+- YES (proposed with the plan; user replied "go")
+- Reason: mission-led international organisation where motivation is material; the letter can explain the move into central-bank statistics and why MED's data work fits.
+- Information it adds beyond resume: motivation for MED (data that central banks and regulators rely on) and a working style built close to domain specialists. SDMX deliberately OMITTED (registered forbidden 2026-10-14; simplest not to raise it).
+- Verified hook sources: the posting itself, https://www.bis.org/vacancy/jr100498, saved verbatim as `JD_bis_senior_lead_data_analytics_engineer.txt` (retrieved 2026-10-14). No other hook used.
+
+## Output Files
+- Resume: `e2e_bis_senior_lead_data_analytics_engineer_resume.tex` + `.pdf` (compiled here)
+- Cover letter: `e2e_bis_senior_lead_data_analytics_engineer_cover_letter.tex` + `.pdf`
+- Critique: `critique_bis_senior_lead_data_analytics_engineer.md`
+
+## Critique Summary
+- Critique: `critique_bis_senior_lead_data_analytics_engineer.md`, 2026-10-14 (self-review in the generating session)
+- Evidence Fit: 78/100, Core
+- Hard gate: PASS
+- Document Quality: 86/100 at critique; 88/100 after the Tier 2 fixes (2026-10-15)
+- Channel Strength: Weak
+- Tier 1 fixes: none
+- Tier 2: all three applied 2026-10-15 on user instruction (skills recency marks, headline without historical BI, VZ-2 verb)
+- Interview prep: Swisscom dashboard tool (not in KB), attributed Q8 schedule example, SDMX answer, Lead story, fixed-term trade-off
+
+## Status
+- Fit gate: DONE 2026-10-14, Core 78, hard gate PASS
+- Resume: DONE 2026-10-14; user proceeded to /make-cl (taken as approval)
+- Cover letter: DONE 2026-10-14, awaiting user approval (update the literal date at submission)
+- Critique: DONE 2026-10-14 (EF 78 Core, gate PASS, DQ 86, channel Weak, no Tier 1)
+- Application/outcome: **SUBMITTED 2026-10-15** via the BIS portal (tracker app-bis-jr100498, outcome `applied`, channel Weak)
+- Package: FINALIZED 2026-10-15. Submission copies: `Dennis_Thiessen_Resume.pdf`, `Dennis_Thiessen_Cover_Letter.pdf` (byte-identical to the e2e builds). NOT submitted.
+- Next: await BIS response. At first contact ask office days and total package; weigh the 3-year fixed term against the permanent Swisscom post. Interview prep: critique §7 and `portal_answers_bis_jr100498.md`.
+
+## KB changes made this session (2026-10-14)
+- `claims.json`: new claims BS-9, SW-10; skills `TIBCO Spotfire` (allowed) and `SDMX` (forbidden).
+- `knowledge_base/extractions/2026-10-14_mentoring_spotfire_sdmx_clarification.md`.
+- `CLAUDE.md` corrections log entry 2026-10-14.
+
+## As-built resume (2026-10-14)
+- Profile: International Tech, English (British spelling), 2 pages A4, no photo. Contact line Bern.
+- Headline: Staff Data, Analytics & AI Engineer | Data Products & Pipelines | AWS Lakehouse & BI
+- Summary: 3 rendered lines.
+- Skills: 6 skill lines (Programming, Data engineering, Databases and BI, Platform, Certifications, Languages), 9 rendered lines. Experience starts at about 46% of page 1 (visual estimate; `page_metrics.py` failed because Git's pdftotext lacks `-bbox`). A first build carried a separate "Data management" line and rendered 11 lines; it was cut because SW-7/SW-2 bullets prove the same content.
+- Bullets: 13. Swisscom 5 (SW-7, SW-1/6/9, SW-2, SW-4/3, SW-10); Bosch 5 (BS-3/5, BS-2, BS-8/5, BS-1/4, BS-9/7); Fraunhofer FC-1; Vizrt VZ-2; Generali GN-1. Bundeswehr header only.
+- Page break: Swisscom and the first three Bosch bullets on page 1; remaining Bosch bullets, earlier roles, Bundeswehr and Education on page 2. Page 2 is about half full; no filler added.
+- Validator: `validate_resume_system.py --document` PASS, 0 errors, 0 warnings (cadence included).
+- Compile: MiKTeX pdflatex, 2 passes, 2 pages, no overfull/underfull boxes. Both pages inspected at 80 dpi; `pdftotext -layout` order is header, summary, skills, then employer/title/date blocks in reverse chronology.
+- Scope checks applied by hand: SW-2/SW-4/SW-3 in past tense (ART B2B); SW-1 scoped to "owned domains" plus "contributing to Swisscom's wider cloud migration"; SW-7 "within Swisscom's company-wide Data Mesh"; ODP-Flow omitted (external employer); BS-1 written as a failure consequence, no model-training claim; BS-4 labelled proof of concept; BS-7 exactly one thesis; FC-1 without any quality-gate claim; no metrics; no SDMX, LangChain or other forbidden term.
+- Post-review revisions (same day, before presenting):
+  - BS-8: "and tuned the queries behind it" changed to "including performance tuning". BS-8 records tuning as a main difficulty but not what was tuned, and spatial indexes and operators are unconfirmed. The `Oracle Database` skill note in claims.json was corrected the same way.
+  - Cadence: SW-4 became a single-object bullet ("Translated internal B2B stakeholders' requirements into data products and dashboards; ..."). BS-9/7 became "Mentored junior developers through onboarding, and served as supervisor and second examiner for one Bachelor thesis."
+  - Employer string corrected to the canonical "Fraunhofer-Center for Maritime Logistics and Services CML".
+  - `\hyphenation{semiconductor}` keeps the term whole for ATS parsing. The summary is set `\sloppy` to absorb the resulting overfull box.
+  - Final: validator PASS (0 warnings), 2 pages, no overfull/underfull boxes. `page_metrics.py` (MiKTeX pdftotext on PATH) measures experience starting at 45.8% of page 1, with 52 text lines and 408 words on page 1.
+
+## Cover letter as built (2026-10-14)
+- The user moved to `/make-cl` after the resume was presented; that is taken as resume approval.
+- File: `e2e_bis_senior_lead_data_analytics_engineer_cover_letter.tex` + `.pdf`. One A4 page, 3 paragraphs, 237 words after revision (salutation to sign-off). British spelling.
+- What it adds beyond the resume: motivation for MED (who the data is for, economists and statisticians) and a working style built close to domain specialists. These are the two evidence themes: (1) governed data products and DWH data quality (SW-7, SW-2); (2) combining sources never designed to fit (BS-3/BS-5, BS-2, BS-8).
+- Employer hook: the posting itself only. Its text says MED aims "to collect a wider variety of data and harness new technology" for "a step change in our capability", and names "Lakehouse engineering". Source: https://www.bis.org/vacancy/jr100498, saved verbatim as `JD_bis_senior_lead_data_analytics_engineer.txt`, retrieved 2026-10-14. No other BIS programme, product or statistic is named, so nothing else needed verifying.
+- Claim checks: every work claim is also in the resume. "co-owned Spotfire" kept. Mentoring is written as "At Bosch and Swisscom I have also onboarded and mentored", because SW-10's phase is not recorded. SW-2 is past tense. "Worked in Germany, Norway and Switzerland" matches the resume locations. "Enjoy international teams" is the user's stated motivation (memory: international mobility). SDMX, the prior BIS application and the 3-year term are deliberately not mentioned. Recipient address limited to "Basel, Switzerland" (street address not verified).
+- Date: literal "14 October 2026". **At submission: update it to the sending date, recompile, and refresh `Dennis_Thiessen_Cover_Letter.pdf` (config.md Output Rules), so the attached copy does not carry the old date.**
+- Validator: PASS on resume + letter together (0 warnings). Compile: MiKTeX, no overfull/underfull boxes, page inspected at 80 dpi.
+- Status: cover letter DONE, awaiting user approval. Next: `/critique`.
+- Revision before presenting (2026-10-14): paragraph 1 was rewritten. The first draft reworded the SW-7 and SW-2 resume bullets (artefact list, plus an unsupported 'for each product'). It now states the connection (the lakehouse stack named in the posting, plus the operating side of warehouse ETL) and the motivation (data that central banks and financial regulators rely on, paraphrased from the JD). The 'not the analysis but' contrast in paragraph 2 was dropped.
+
+## Finalization (2026-10-15)
+- User approved: "apply the polish items and finalize".
+- Tier 2 polish applied (see critique re-report). Skills: Programming "Python, SQL, pytest; Java, C# and Kotlin (professional, historical)"; Data engineering "... Kafka (historical); relational data modelling"; Platform "AWS, CloudFormation, Docker; Kubernetes, GitLab CI/CD, Linux, Ansible (historical)". Headline "Staff Data, Analytics & AI Engineer | Governed Data Products & Pipelines | AWS Lakehouse". VZ-2 reworded.
+- Cover letter date set to 15 October 2026.
+- Shared-ops finalization checks: session, resume source/PDF, critique and cover-letter source/PDF exist; validator PASS on both submitted documents; submission copies created and verified identical with `cmp`. Application registered in `job_scout/state/applications.json` (app-bis-jr100498, outcome `open`, application_date null until submission); the cohort projection already carries it, so no separate `cohort_tracker.py add` was run.
+
+## Submission (2026-10-15)
+- Submitted by the user via the BIS portal: `Dennis_Thiessen_Resume.pdf`, `Dennis_Thiessen_Cover_Letter.pdf` (dated 15 October 2026, matching the sending date) and four portal free-text answers.
+- Portal answers: `portal_answers_bis_jr100498.md` (as drafted; the user may have edited them in the portal). They introduced one new canonical fact, the prototype-and-iterate approach on a Swisscom B2B data product (recorded in the SW-4 scope and the clarification note on 2026-10-15). XBRL was flagged for the user to confirm before pasting.
+- Channel: no warm contact was recorded before submission, so Weak/cold.
+- Recorded in `job_scout/state/applications.json` (outcome `applied`, application_date 2026-10-15; views re-rendered and checked) and `job_scout/state/decisions.json` (`applied`).