chore(applications): archive BIS + NATO submitted packages, ignore tmp/
Add BIS Basel and NATO JWC Stavanger application output (resume/CV, cover letter, session file, critique) plus the Bundeswehr experience file backing the NATO package; update session status tables in AGENTS.md/CLAUDE.md; record two new Bash allowlist entries for the job scout venv. tmp/ is scratch working files, now gitignored. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Claude Sonnet 5
@@ -0,0 +1,142 @@
|
||||
Job Title: Staff Officer (2030 Digitalisation - Artificial Intelligence Engineer)
|
||||
This vacancy notice is for a NATO-2030 agenda project-linked NATO International Civilian (PLN) post.
|
||||
This post is limited to a three-year definite duration project. It will be filled as soon as possible. In view
|
||||
of the urgency of this project, qualified candidates who hold or have recently held a valid NATO or
|
||||
National security clearance will be given priority consideration.
|
||||
Please note that the JWC is currently trialling a new organizational structure. Consequently, reporting
|
||||
lines, job titles, functional alignments and some duties may differ slightly from those outlined in the
|
||||
vacancy notice.
|
||||
NATO Body: Joint Warfare Centre (JWC)
|
||||
Primary Location: Stavanger, Norway
|
||||
Schedule: Full-Time
|
||||
Salary (Pay Basis): 93,933 NOK Monthly
|
||||
Grade: G15
|
||||
Clearance Level: NATO Secret (NS)
|
||||
Application Deadline: 9 August 2026
|
||||
The Joint Warfare Centre (JWC) is seeking a Staff Officer (2030 Digitalisation - Artificial Intelligence
|
||||
Engineer) for its civilian workforce within the CIS Services Branch.
|
||||
We are building a Data Science Team at NATO’s JWC in spectacular Stavanger, Norway. This team
|
||||
will lead the transformation of JWC’s exercises to incorporate the latest emerging defence
|
||||
technologies faster than ever before. The JWC’s AI and Automation initiatives will improve the mission
|
||||
impact of AI for NATO operations and streamline business processes across the centre.
|
||||
In this role, you will contribute as a key member of the JWC Data Science Team to deliver AI to NATO
|
||||
exercises, gaining experience in multi-level security, international, and operational environments. You
|
||||
will plan, develop, and deliver on a roadmap to bring cutting-edge AI (including latest generation LLMs,
|
||||
reasoning models, and agentic systems) to operate on NATO’s strategic, data-centric exercises and
|
||||
programs. Your hands-on experience will carry over as your team delivers and iterates with operators
|
||||
from across the alliance.
|
||||
NATO UNCLASSIFIED
|
||||
NATO UNCLASSIFIED
|
||||
What the role offers:
|
||||
High impact, portfolio-level work at the intersection of AI, defence, and NATO operations.
|
||||
An English-language environment with colleagues from across the 32-nation alliance
|
||||
An opportunity to live and work in one of Norway’s most beautiful coastal cities, with easy
|
||||
access to the fjord and flights across Europe.
|
||||
Tax free salary and privileges.
|
||||
If you are ready for a challenging role that will leverage your technical skills and expose you
|
||||
to an international cohort working on challenges at the highest strategic level, we encourage
|
||||
you to apply.
|
||||
Principal Duties
|
||||
The incumbent's duties are:
|
||||
• Provide subject-matter-expert advice, manage the development, refinement, and delivery of large
|
||||
language model (LLM) artificial intelligence tools in support of JWC’s digital transformation effort.
|
||||
• Highlight emerging technologies and opportunities for JWC to enhance its employment of its
|
||||
digital transformation using machine learning in JWC process improvement.
|
||||
• Deploy, optimize and manage large language model-powered applications in a JWC production
|
||||
environment
|
||||
• Fine-tune existing, pre-trained (LLM) to adapt to future JWC applications.
|
||||
• Develop multi-modal solutions to address hybrid search
|
||||
• Develop a roadmap for implementing Data initiatives and integrating NATO's digital
|
||||
transformation into JWC’s processes and exercise production;
|
||||
• Develop and apply validation methodologies to verify the accuracy and reliability of large data-
|
||||
centric programmes, such as Geographic Intelligence and others across the JWC to ensure
|
||||
cohesive LLM outputs in support of exercise delivery.
|
||||
• Recommend, coordinate, and initiate projects aimed at sustainably embedding AI-based solutions
|
||||
into JWC business processes.
|
||||
• Collaborate with stakeholders, internal teams, and working groups, as needed.
|
||||
• Provide expert advice and guidance on automation to the JWC’s leadership team and staff.
|
||||
• Remain abreast of industry trends and best practices in artificial intelligence systems, contributing
|
||||
to the continual enhancement of analytical processes and tools at JWC NATO.
|
||||
Essential Qualifications
|
||||
Education/Training
|
||||
• University Degree in information technology, economics, statistics, operations research or related
|
||||
discipline and 3 years function related experience,
|
||||
• or Higher Secondary education and completed advanced vocational training in that discipline
|
||||
leading to a professional qualification or professional accreditation with 4 years post related
|
||||
experience.
|
||||
Experience
|
||||
• At least 3 years’ functional experience of developing, managing, and adapting artificial intelligence
|
||||
systems including Large Language
|
||||
• Models (LLMs).
|
||||
• At least 2 year’s functional experience with Python, SQL and Spark or equivalent.
|
||||
• Certification in Microsoft Azure Data Scientist or equivalent.
|
||||
NATO UNCLASSIFIED
|
||||
NATO UNCLASSIFIED
|
||||
Language
|
||||
English – Upper Intermediate/Advanced
|
||||
Desirable Qualifications
|
||||
Professional Experience
|
||||
• Problem solving skills: Strong analytical and critical thinking skills to identify patterns, trends and
|
||||
outliers in data as well as being able to solve complex business problems using data-driven
|
||||
approaches.
|
||||
• Knowledge of and experience in programming, machine learning, data management, big data
|
||||
technology, ethical considerations of data and project management.
|
||||
Education/Training
|
||||
• Master’s Degree or equivalent in artificial intelligence systems, computational science, or related
|
||||
discipline.
|
||||
• A recognized Project management Qualification (APM, Prince, AgilePM, etc.)
|
||||
Personal Attributes/Competencies
|
||||
• Considerable maturity and professional judgement is required to make decisions on to ensure
|
||||
seamless provision of high-quality support to the JWC.
|
||||
• High level of organisational and coordination skills.
|
||||
• Excellent managerial, interpersonal, and communication skills with a visionary view to evolving
|
||||
requirements to meet future challenges.
|
||||
• Able to cope with stress and possessing good health.
|
||||
• Must be able to work as a member of a team in a multi-national environment.
|
||||
• An analytical, systematic and pro-active approach is important.
|
||||
• Strong analytical and critical thinking skills to identify patterns, trends and outliers in data as well
|
||||
as being able to solve complex business problems using data-driven approaches.
|
||||
• A capacity for original thought, including the incorporation of emerging
|
||||
• concepts.
|
||||
• Self-motivated and capable of working under pressure.
|
||||
Work Environment
|
||||
The work is normally performed in an office environment.
|
||||
NOTE: The work both oral and written in this post and in this headquarters as a whole is conducted
|
||||
mainly in English.
|
||||
Travel on temporary duty may be required for several conferences.
|
||||
Irregular working hours may be required, especially during exercises/events
|
||||
How to Apply for a Project Linked NATO Civilian Post at JWC:
|
||||
JWC, as an equal opportunities employer, values diverse backgrounds and perspectives and is
|
||||
committed to recruiting and retaining a diverse and talented workforce. We welcome applications from
|
||||
nationals of all NATO Member States and strongly encourage women to apply.
|
||||
Applications are to be submitted, in English, using the NATO Talent Acquisition Platform (NTAP)
|
||||
(https://nato.taleo.net/careersection/2/jobsearch.ftl?lang-en). Applications submitted by other means
|
||||
will not be accepted.
|
||||
NATO UNCLASSIFIED
|
||||
NATO UNCLASSIFIED
|
||||
NTAP allows for the adding of attachments. Candidates are to attach a copy of the
|
||||
qualification(s)/certificate(s) covering the highest level of education and vocational qualifications held
|
||||
to support their application.
|
||||
Applications are automatically acknowledged within one working day after submission. In the absence
|
||||
of an acknowledgement please make sure the submission process is completed or re-submit the
|
||||
application. Applications will not be accepted after the deadline.
|
||||
Remarks:
|
||||
|
||||
Notes for candidates: The candidature of NATO redundant staff at grade G15/A-2 will be considered
|
||||
before any other candidates.
|
||||
Notes for NATO Civilian Human Resources Managers: if you have qualified redundant staff at
|
||||
grade G15/A-2, who wish to be considered for this post, please advise JWC Civilian HR no later than
|
||||
the closing date.
|
||||
Final interviews are scheduled to take place during the second half of October 2026.
|
||||
Contract:
|
||||
This project post is limited to a definite duration of 3 years. There is no guarantee that this post will
|
||||
continue beyond that period. Successful applicants will be offered a 3-year definite duration
|
||||
employment contract. Serving staff will be offered a contract in accordance with the NATO Civilian
|
||||
Personnel Regulations.
|
||||
Salary:
|
||||
Starting basic salary is NOK 93,933.00 per month (tax-free). Additional allowances may apply
|
||||
depending on the personal circumstances of the successful candidate. For further details see NATO
|
||||
Terms & Conditions.
|
||||
|
||||
For any queries, please contact the Joint Warfare Centre Recruitment Team at
|
||||
jwc.recruitment@nato.int
|
||||
@@ -0,0 +1,229 @@
|
||||
# Critique: NATO JWC — Staff Officer (2030 Digitalisation - Artificial Intelligence Engineer)
|
||||
|
||||
**Resume:** `output/NATO_AI_ENGINEER/e2e_nato_ai_engineer_resume.tex`
|
||||
**Cover letter:** `output/NATO_AI_ENGINEER/e2e_nato_ai_engineer_cover_letter.tex`
|
||||
**JD:** `JDs/NATO_AI_ENGINEER.txt` (file provided; verbatim)
|
||||
**Date:** 10 July 2026
|
||||
**Overall package score:** **77.5/100**
|
||||
|
||||
---
|
||||
|
||||
## 1. Domain-Specialist Lens
|
||||
|
||||
### Reviewer Persona and Company Context
|
||||
|
||||
The primary reader is likely a JWC CIS Services Branch or Data Science Team lead, supported by civilian HR. At G15, they need someone who can advise senior staff and turn AI prototypes into dependable capabilities for NATO exercises. Generic cloud-tool lists will not impress them; production constraints, security awareness, operational judgement and credible LLM depth will. JWC's AI in Audacious Training work is already moving into implementation and focuses on practical exercise support with operator review.
|
||||
|
||||
### JD Vocabulary Extraction
|
||||
|
||||
| JD term | Importance | Resume match |
|
||||
|---|---|---|
|
||||
| LLM tools / applications | Essential | Partial: agent configuration, not delivery ownership |
|
||||
| Production environment | Essential | Strong bridge: Bosch 24/7 ML |
|
||||
| Python, SQL, Spark | Essential | Direct |
|
||||
| Fine-tuning | Essential | Absent |
|
||||
| Hybrid search / multimodal | Essential | Absent |
|
||||
| Validation methodologies | Essential | Partial: quality gates and observability |
|
||||
| Data roadmap / initiatives | High | Partial |
|
||||
| Multi-level security | High | Partial; no clearance |
|
||||
| Azure Data Scientist certification | Essential credential | Partial: AWS SAA is adjacent |
|
||||
| Multinational operational environment | High | Strong bridge: Bundeswehr and Norway |
|
||||
|
||||
### Domain Vocabulary Map
|
||||
|
||||
| Resume wording | JWC interpretation | Assessment |
|
||||
|---|---|---|
|
||||
| Production ML | AI delivered under operational constraints | Strong, especially Bosch |
|
||||
| Domain-grounded LLM agents | Internal LLM application configuration | Accurate; do not upgrade to “agentic system” |
|
||||
| Data Mesh / metadata | Governed foundation for data-centric operations | Good bridge, not hybrid search |
|
||||
| CI/CD quality gates | Validation and controlled delivery discipline | Useful bridge, not formal LLM evaluation |
|
||||
| Officer service | Operational judgement and structured responsibility | Appropriate, distinctive |
|
||||
|
||||
### Gap Ranking
|
||||
|
||||
- **Fatal / likely gate:** three years of functional LLM-system experience; Azure Data Scientist certification if applied literally; current/recent clearance if cleared applicants are available.
|
||||
- **Serious:** LLM fine-tuning, multimodal/hybrid search, reasoning/agentic-system delivery, formal LLM evaluation and production LLM operations.
|
||||
- **Cosmetic:** Geographic Intelligence and formal project-management certification.
|
||||
|
||||
### Methodology Transfer Test
|
||||
|
||||
| Achievement | JWC transfer |
|
||||
|---|---|
|
||||
| Swisscom LLM-agent configuration | Credible starting point for a domain-grounded exercise assistant, but does not prove secure deployment, evaluation or adaptation. |
|
||||
| Bosch 24/7 ML inference | Strong evidence of operating AI under high availability and integration constraints. |
|
||||
| Swisscom governed data products | Relevant to reliable, discoverable data for exercise systems and future AI use cases. |
|
||||
| Fraunhofer ARTUS NLP | Applied language-AI context in a safety-relevant setting, correctly hedged. |
|
||||
| Bundeswehr officer service | Supports maturity and organisational familiarity; does not imply NATO service or clearance. |
|
||||
|
||||
### Competitive Landscape
|
||||
|
||||
The obvious fit has current clearance, direct defence/NATO delivery, Azure credentials and recent LLM/RAG, evaluation, fine-tuning or agentic production experience. Dennis offers rare production ML in a continuous industrial environment, staff-level data ownership and authentic German officer service. The hard disadvantage is that the LLM work is internal-agent configuration, not three years of systems engineering.
|
||||
|
||||
---
|
||||
|
||||
## 2. Five-Perspective Read-Through
|
||||
|
||||
### ATS Robot
|
||||
|
||||
| Keyword group | Status |
|
||||
|---|---|
|
||||
| LLM / AI agents | Direct |
|
||||
| LLM production applications | Partial |
|
||||
| Python, SQL, Spark | Direct |
|
||||
| ML deployment, Docker, Kubernetes | Direct |
|
||||
| Data management, automation | Direct |
|
||||
| Validation, security | Partial |
|
||||
| Fine-tuning, hybrid search, multimodal, reasoning | Absent |
|
||||
| Azure Data Scientist, clearance | Absent |
|
||||
| Stakeholder and multinational work | Direct / bridge |
|
||||
|
||||
**Match rate:** 13/20 direct or semantic = **65%, marginal**. The missing terms are mostly unearned capabilities and should not be inserted as keywords.
|
||||
|
||||
### Recruiter Glance (10 seconds)
|
||||
|
||||
**Verdict: Forward, with caution.** The target title, Swisscom staff role, M.Eng., German nationality and officer service make the profile unusually legible for a NATO civilian role. Azure and senior LLM depth remain visible risks.
|
||||
|
||||
### HR Screen (30 seconds)
|
||||
|
||||
**Verdict: Borderline phone screen.** Degree, English, nationality, Python/SQL/Spark and relevant experience are clear. The decision is whether AWS SAA satisfies “or equivalent” and whether LLM-agent configuration meets the functional-experience requirement.
|
||||
|
||||
### Hiring Manager Read (2 minutes)
|
||||
|
||||
**Verdict: Maybe interview.** Bosch is the strongest proof point: AI delivered into a 24/7 environment. The manager will value the officer-service context but will immediately probe the Swisscom-agent architecture, evaluation, access controls and adoption.
|
||||
|
||||
**Predicted first question:** “Walk me through the Swisscom agents: what knowledge was supplied, how did you judge answer quality, who used them, and what constraints did you have?”
|
||||
|
||||
### Technical Reviewer (10 minutes)
|
||||
|
||||
**Truthfulness: strong.** LLM wording is restrained; Fraunhofer uses a contributing verb; Bosch ownership is supported; no clearance, Azure or fine-tuning claim is implied. The candidate must be able to distinguish configuring an internal agent from engineering an LLM system.
|
||||
|
||||
**Consistency: clean.** Resume and letter reinforce the same honest boundary. No publication claim is made, correctly.
|
||||
|
||||
---
|
||||
|
||||
## 3. Eight-Dimension Scoring
|
||||
|
||||
| Dimension | Score | Weight | Weighted | Notes |
|
||||
|---|---:|---:|---:|---|
|
||||
| ATS Keyword Match | 6.8/10 | 15% | 10.2 | Good data/ML coverage; core LLM gaps remain. |
|
||||
| Summary | 8.2/10 | 10% | 8.2 | Clear and honest bridge. |
|
||||
| Skills Section | 7.5/10 | 10% | 7.5 | Relevant and pruned; lacks requested LLM capabilities for valid reasons. |
|
||||
| Bullet Quality | 8.0/10 | 25% | 20.0 | Bosch and Swisscom are well selected and credible. |
|
||||
| Publication Selection | 7.5/10 | 10% | 7.5 | No publications is appropriate; certifications partly compensate. |
|
||||
| Narrative Coherence | 8.4/10 | 15% | 12.6 | ML delivery → data reliability → NLP → operational context is coherent. |
|
||||
| Page Fill & Visual | 6.5/10 | 5% | 3.3 | Clean two-page render; page 2 is intentionally sparse. |
|
||||
| Credibility Signals | 8.2/10 | 10% | 8.2 | 24/7 ML, AWS certification, officer service and international work are strong. |
|
||||
| **Total** | | **100%** | **77.5/100** | Polished package, capped by hard JD gaps. |
|
||||
|
||||
---
|
||||
|
||||
## 4. Interview Likelihood
|
||||
|
||||
| Reader | Probability | Key factor |
|
||||
|---|---:|---|
|
||||
| ATS | 55% | Exact LLM, Azure, fine-tuning and hybrid-search terms are absent for accurate reasons. |
|
||||
| Recruiter | 70% | German nationality and officer background make the role change credible. |
|
||||
| HR | 45% | Azure and three-year LLM requirements may be hard gates. |
|
||||
| Hiring Manager | 40% | Production ML and defence context earn curiosity; LLM depth remains uncertain. |
|
||||
| Technical panel | 35% | Agent architecture, evaluation and security answers decide. |
|
||||
|
||||
**Ceiling:** Current **77.5** → with truthful improvements **79–80** → theoretical maximum with current history **82**. The ceiling is direct LLM duration, fine-tuning/hybrid-search evidence and clearance, not wording.
|
||||
|
||||
---
|
||||
|
||||
## 5. Tiered Improvements
|
||||
|
||||
### Tier 1 — High impact
|
||||
|
||||
1. **Earn Azure Data Scientist Associate before interview only if genuinely achievable.** Do not list it until earned. This is the cleanest route to address the stated credential. **+1.5 to +2.0 points.**
|
||||
2. **Document the Swisscom-agent work for the application and interview.** Collect only verifiable facts: agent count, users/adoption, knowledge-source handling, quality review, model-selection rationale and data-access controls. Add to the package only if supported. **+1.0 to +1.5 points if facts exist.**
|
||||
3. **Address clearance and LLM gaps precisely in the application form.** State only truthful clearance history and retain the same distinction between configuration and production LLM ownership. **Risk reduction, not a score increase.**
|
||||
|
||||
### Tier 2 — Medium impact
|
||||
|
||||
1. Swap `Prompt engineering` for `DevSecOps / Security by Design` only if the 2025/26 Security Champion training can be stated precisely. This supports the security environment without implying clearance. **+0.5 points.**
|
||||
2. Add a clearly labelled current-learning line on LLM evaluation only if it is specific enough to defend. Do not call it experience. **+0.4 points.**
|
||||
3. Rebalance page 2 only if density matters more than the user’s concise-content directive. **+0.3 points.**
|
||||
|
||||
### Tier 3 — Cosmetic
|
||||
|
||||
1. Align “former German Armed Forces officer” in the summary with the exact dated experience entry.
|
||||
2. The letter could move the Bosch proof point earlier, but the current Swisscom-first sequence is defensible for an LLM-focused vacancy.
|
||||
|
||||
**Verdict:** Apply Tier 1 only where new credentials or facts genuinely exist. Do not keyword-stuff fine-tuning, hybrid search, Azure or clearance.
|
||||
|
||||
---
|
||||
|
||||
## 6. Interview Bridge Points
|
||||
|
||||
| Resume topic | Target equivalent | Interview opening line |
|
||||
|---|---|---|
|
||||
| Swisscom LLM agents | Domain-grounded exercise assistant | “At Swisscom I configured agents around domain knowledge; for JWC I would begin with user needs, allowed data and how output quality is reviewed.” |
|
||||
| Bosch ML inference | Production AI for operational exercises | “The difficult part was integrating and operating the model reliably in a 24/7 environment, not only selecting a model.” |
|
||||
| Swisscom governed data | Data-centric exercise foundation | “My current work makes data products discoverable, governed and reliable, which is the precondition for trustworthy downstream AI.” |
|
||||
| Fraunhofer ARTUS | Language AI in a safety-relevant setting | “ARTUS gave me applied NLP context; my role was a contribution within a research team.” |
|
||||
| Quality gates and observability | LLM validation discipline | “I have not run a formal LLM evaluation programme, but I have built quality gates and monitoring around production systems.” |
|
||||
| Bundeswehr officer service | Operational judgement | “My officer service does not make me a NATO practitioner, but it gave me respect for structured responsibility and operational users remaining in control.” |
|
||||
|
||||
---
|
||||
|
||||
## 7. Cover Letter Critique
|
||||
|
||||
### 7A. Anti-patterns
|
||||
|
||||
Pass: specific JWC opening, no generic opener, no defensive gap apology, active closing, no banned AI-writing phrases or em-dash excess. LLM scope is configuration, not training or deployment.
|
||||
|
||||
### 7B. Tailoring
|
||||
|
||||
Pass: names JWC and AI in Audacious Training, references operator review, data-centric exercise systems and digital transformation. It could name NATO-Maven Smart System once, but the present hook is already strong and restrained.
|
||||
|
||||
### 7C. Context-Specific Assessment
|
||||
|
||||
The tone is appropriate for an international defence organisation: mission-aware, technical but HR-safe, and not pretending to be a defence-AI specialist.
|
||||
|
||||
### 7D. CL ATS Check
|
||||
|
||||
8/10 high-priority terms appear directly or semantically: AI, LLM, data, Python, Kubernetes, CI/CD, ML, operational/multinational. Azure, fine-tuning, hybrid search and clearance remain correctly absent.
|
||||
|
||||
### 7E. Structural Checks
|
||||
|
||||
- One page; 324 body words, around 336 including closing. This fits the session’s 330–380-word plan.
|
||||
- Claims trace to resume bullets. The named programme is verified: https://www.act.nato.int/article/ai-audacious-training/
|
||||
- Bosch production ML in paragraph 3 is a minor hierarchy issue, not a credibility issue.
|
||||
|
||||
### 7F. Package Cohesion
|
||||
|
||||
The resume stands alone; the letter adds why-JWC context. Both repeat the same honest boundary around LLM work. No contradiction found.
|
||||
|
||||
---
|
||||
|
||||
## 8. Post-Generation Verification
|
||||
|
||||
### Mechanical
|
||||
|
||||
- [x] Resume compiled to 2 pages; cover letter compiled to 1 page.
|
||||
- [x] All 14 experience bullets passed the Resume-2L character gate; no OVER violations.
|
||||
- [x] No header wrap, clipping or broken layout found in visual review.
|
||||
- [ ] Resume page 2 has more than the target three lines of whitespace. This is an acknowledged user-directed compactness trade-off.
|
||||
|
||||
### Content
|
||||
|
||||
- [x] Configured email appears in both documents.
|
||||
- [x] Nationality, officer service, roles and dates are internally consistent.
|
||||
- [x] No unearned clearance, Azure, LangChain/LangGraph, fine-tuning, hybrid-search or production-LLM claim.
|
||||
- [x] Fraunhofer contribution uses a hedged verb.
|
||||
- [x] Cover-letter claims trace to resume; JWC hook verified.
|
||||
|
||||
### Structural and Authenticity
|
||||
|
||||
- [x] Company and role are correctly stated.
|
||||
- [x] Both `.tex` files have standalone preambles and compile.
|
||||
- [x] Dates and configured email are correct.
|
||||
- [x] No banned AI-fingerprint words, generic opener or em-dash excess found in the cover letter.
|
||||
- [x] No resume bullet ends in an “-ing” analysis phrase.
|
||||
|
||||
---
|
||||
|
||||
## Critique Summary
|
||||
|
||||
**Score: 77.5/100.** The package is polished, accurate and unusually well targeted for a production-ML/data-engineering candidate with authentic defence-context experience. The limitation is structural: the vacancy seeks senior LLM experience, credentials and security context that cannot be recreated through reframing. Submit only with an application-form explanation that remains as precise as the package.
|
||||
@@ -0,0 +1,42 @@
|
||||
\documentclass[11pt,a4paper,roman]{moderncv}
|
||||
\usepackage[english]{babel}
|
||||
\moderncvstyle{classic}
|
||||
\moderncvcolor{green}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage{ragged2e}
|
||||
\usepackage[scale=0.80]{geometry}
|
||||
\usepackage[version=4,arrows=pgf-filled]{mhchem}
|
||||
\renewcommand*{\makeletterclosing}{\par\vspace{2ex}\closingname\par}
|
||||
\microtypesetup{expansion=false}
|
||||
|
||||
\name{Dennis}{Thiessen, M.Eng.}
|
||||
\address{Bern, Switzerland}{}{}
|
||||
\phone[mobile]{+41~795~955~585}
|
||||
\email{dennis@thiessen.io}
|
||||
\extrainfo{\href{https://linkedin.com/in/dennis-thiessen}{linkedin.com/in/dennis-thiessen}}
|
||||
|
||||
\begin{document}
|
||||
|
||||
\recipient{Hiring Committee}{Joint Warfare Centre\\Stavanger, Norway}
|
||||
\date{10 July 2026}
|
||||
\opening{Dear Members of the Hiring Committee,}
|
||||
\makelettertitle
|
||||
|
||||
\begin{justify}
|
||||
JWC's AI in Audacious Training work is moving AI from concept into practical support for exercise teams: scenario content is being built, tested, reviewed and refined with operators. I am applying for the Staff Officer (2030 Digitalisation -- Artificial Intelligence Engineer) role because this is the work I want to do: build dependable AI-enabled capabilities that improve operational workflows while keeping the people who use the output involved in delivery and review. That emphasis on expert judgement matches how I approach applied AI.
|
||||
|
||||
At Swisscom, I configure domain-grounded LLM agents in a Swisscom-owned web interface, choosing available models and supplying knowledge bases for Q\&A, migration assistance and data mapping. The role also includes governed data products and metadata on AWS, plus Python services on Kubernetes with GitLab CI/CD. As Component Owner for business-critical Fulfillment pipelines, I work with data quality, governance, incident response and on-call responsibility. That work makes the link between governed inputs and useful AI output concrete. This is the operating discipline I would bring to JWC's data-centric exercise systems.
|
||||
|
||||
Previously at Bosch Semiconductor, I designed and implemented Docker, Kubernetes and Ansible integration for automated image-based defect classification in a 24/7 fab. There was no useful separation between an ML model and its operating environment: data access, delivery, monitoring and user trust all mattered. At Fraunhofer, I also contributed ML and NLP components to ARTUS, a research project for automatic transcription of sea-rescue communications. Together, those experiences give me practical ML delivery and applied language-AI context.
|
||||
|
||||
My six years as a German Armed Forces officer, ending as a Second Lieutenant, provide a genuine connection to the structured, multinational setting of the JWC. As a German national, I meet the nationality condition for this post. I would welcome the opportunity to discuss how my production ML, data engineering and careful LLM-application experience can support JWC's digital transformation and its operators.
|
||||
\end{justify}
|
||||
|
||||
\vspace{0.3cm}
|
||||
{Sincerely,\\
|
||||
Dennis Thiessen, M.Eng.\\
|
||||
Staff Data, Analytics \& AI Engineer\\
|
||||
Swisscom (Schweiz) AG}
|
||||
|
||||
\end{document}
|
||||
@@ -0,0 +1,136 @@
|
||||
\documentclass{resume}
|
||||
\usepackage{hyperref}
|
||||
\usepackage{enumitem}
|
||||
\usepackage{fontawesome}
|
||||
\usepackage{tikz}
|
||||
\usepackage{graphicx}
|
||||
\hypersetup{
|
||||
colorlinks = true,
|
||||
linkcolor = [rgb]{0.9,0.4,0.4},
|
||||
anchorcolor = [rgb]{0.9,0.4,0.4},
|
||||
citecolor = [rgb]{0.4,0.4,0.4},
|
||||
filecolor = [rgb]{0.4,0.4,0.4},
|
||||
urlcolor = [rgb]{0.0,0.0,0.99},
|
||||
}
|
||||
\usepackage{xcolor}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage{lmodern}
|
||||
\usepackage[version=4,arrows=pgf-filled]{mhchem}
|
||||
\usepackage[includefoot,left=0.5in,top=0.5in,right=0.5in,bottom=0.2in,textwidth=7.5in,textheight=10.8in]{geometry}
|
||||
\usepackage{fancyhdr}
|
||||
\pagestyle{fancy}
|
||||
\fancyhf{}
|
||||
\renewcommand{\headrulewidth}{0pt}
|
||||
\fancyfoot[R]{\hfill \thepage/\pageref{LastPage}}
|
||||
\newcommand{\tab}[1]{\hspace{.2667\textwidth}\rlap{#1}}
|
||||
\newcommand{\itab}[1]{\hspace{0em}\rlap{#1}}
|
||||
|
||||
\name{Dennis Thiessen, M.Eng.}
|
||||
\address{\href{https://linkedin.com/in/dennis-thiessen}{LinkedIn}}
|
||||
\address{dennis@thiessen.io \\ +41 795 955 585}
|
||||
\address{Bern, Switzerland $\vert$ Open to relocation to Stavanger, Norway}
|
||||
\address{{AI Engineer $\vert$ Production ML, LLM Applications \& Data-Centric Operations}}
|
||||
|
||||
\begin{document}
|
||||
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\begin{rSection}{Summary}
|
||||
Data and ML engineer with 11+ years building data platforms and applied AI in telecom and manufacturing. At Swisscom I configure domain-grounded LLM agents for Q\&A and migration/data-mapping assistance, and build governed AWS data products. At Bosch I designed and deployed containerised ML inference for image classification in a 24/7 semiconductor fab; at Fraunhofer I contributed NLP for sea-rescue transcription. German national and former German Armed Forces officer, I bring engineering discipline to international settings.
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\begin{rSection}{Technical Skills}
|
||||
|
||||
\begin{skillgroup}{LLM Applications \& Applied AI}
|
||||
\skilldash{\textbf{Python}, LLM-agent configuration, model selection, domain knowledge bases and Q\&A}
|
||||
\skilldash{Production \textbf{ML} inference, image classification, MLOps, applied NLP and speech recognition}
|
||||
\skilldash{Prompt engineering, migration and data-mapping assistance, custom GPTs with domain knowledge}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Data Engineering \& Governance}
|
||||
\skilldash{\textbf{SQL}, \textbf{PySpark}/Spark, \textbf{Apache Kafka}, \textbf{Apache Airflow}, ETL/ELT design and operation}
|
||||
\skilldash{Data products, metadata management, data governance, data quality and data modelling}
|
||||
\skilldash{Oracle, Teradata, Hadoop/Impala, Athena, Redshift and MS SQL}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Cloud \& Production Delivery}
|
||||
\skilldash{\textbf{AWS} (S3, Glue, Athena/Iceberg, Redshift, Lambda, Step Functions), SAA-certified}
|
||||
\skilldash{\textbf{Docker}, \textbf{Kubernetes}, Ansible, GitLab CI/CD, Jenkins, CloudFormation and serverless delivery}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Validation, Monitoring \& Quality}
|
||||
\skilldash{\textbf{Grafana}, \textbf{Prometheus}, Loki and ELK; alerting, incident response and production support}
|
||||
\skilldash{CI/CD quality gates, test automation, code review and structured root-cause analysis}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Certifications}
|
||||
\skilldash{\textbf{AWS Certified Solutions Architect -- Associate} (active to Sep 2027), Data Engineering with AWS}
|
||||
\skilldash{iSAQB CPSA -- Foundation, IBM AI Engineering Specialization, AI for Trading Nanodegree}
|
||||
\end{skillgroup}
|
||||
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\begin{rSection}{Professional Experience}
|
||||
|
||||
\begin{rSubsection}{LLM Applications, Governed Data Products \& Production Delivery}{\textcolor{black!60}{Oct 2023 -- Present}}{Staff Data, Analytics \& AI Engineer, Swisscom (Schweiz) AG}{Bern, Switzerland}
|
||||
\item Configured domain-grounded LLM agents in a Swisscom-owned web interface, selecting models and supplying knowledge bases for Q\&A, migration assistance and data mapping across enterprise data work.
|
||||
\item Built governed data products and metadata management within Swisscom's Data Mesh on \textbf{AWS} (Glue, Athena, CloudFormation), creating discoverable sources for dependable analytics and downstream AI use.
|
||||
\item Designed, deployed and operated \textbf{Python} data applications on \textbf{Kubernetes} with \textbf{GitLab CI/CD}, owning containerised delivery from build and test through deployment and operation in an agile DevOps team.
|
||||
\item Owned business-critical Fulfillment \textbf{ETL} pipelines from Oracle and \textbf{Kafka} to Teradata in \textbf{Python}; used PySpark for distributed workloads and maintained data quality, governance and on-call SLA.
|
||||
\item Led migration of my domains' Oracle/Teradata \textbf{ETL} to Swisscom's \textbf{AWS} platform (Glue, Athena/Iceberg, Redshift and \textbf{Airflow}), reducing manual operations through scalable serverless processing for analytics.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Production ML, Data Services \& Operational Reliability}{\textcolor{black!60}{Feb 2020 -- Dec 2022}}{Data \& ML Engineer, Robert Bosch Semiconductor Manufacturing}{Dresden, Germany}
|
||||
\item Designed and implemented ML inference integration for a 24/7 semiconductor fab, using \textbf{Docker}, \textbf{Kubernetes} and Ansible to automate image-based defect classification on active 300mm wafer production lines.
|
||||
\item Served as Application Owner for semiconductor analytics applications and pipelines, defining SLOs, training users, maintaining documentation and coordinating stakeholders for stable 24/7 operations.
|
||||
\item Delivered an anomaly-detection proof of concept with ELK and \textbf{Kafka} on \textbf{Docker}, adding \textbf{Grafana}, \textbf{Prometheus} and Loki to test centralised monitoring and alerting for semiconductor manufacturing systems.
|
||||
\item Built \textbf{Python}, Java and C\# data services over OracleDB and Hadoop/ImpalaSQL, supplying analysis teams with structured process and defect data for quality monitoring in a high-throughput 24/7 fab.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Applied NLP \& Quality-Controlled Delivery}{\textcolor{black!60}{Sep 2018 -- Oct 2019}}{Research Software Engineer, Fraunhofer-Center for Maritime Logistics CML}{Hamburg, Germany}
|
||||
\item Contributed \textbf{ML} and NLP components to ARTUS, a Fraunhofer research project for automatic transcription of sea-rescue communications, applying speech recognition in a safety-critical maritime setting.
|
||||
\item Independently established Jenkins \textbf{CI/CD} quality gates for SCEDAS decision-support software in C\#, .NET and MS SQL, introducing reliable build automation and release checks to the research team.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Distributed Software Delivery \& CI/CD Quality Gates}{\textcolor{black!60}{Jul 2017 -- May 2018}}{DevOps Engineer, Vizrt}{Bergen, Norway}
|
||||
\item Engineered Python/C++ components for distributed video transcoding and built Python A/V tests with CI/CD quality gates, supporting release delivery for Vizrt's Bergen-based broadcast software team.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Technical Ownership \& Team Training}{\textcolor{black!60}{May 2015 -- Jun 2017}}{IT Consultant, Generali Deutschland Informatik Services}{Hamburg, Germany}
|
||||
\item Introduced BDD test automation at Generali, running the initial proof of concept, owning technical implementation, administering Jenkins jobs and training colleagues within the Java community.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Officer Service}{\textcolor{black!60}{Jul 2008 -- Nov 2014}}{Officer, German Armed Forces (Bundeswehr)}{Germany}
|
||||
\item Completed officer candidate training and officer school during six years in the German Armed Forces, leaving service as Second Lieutenant with experience in a structured operational environment.
|
||||
\end{rSubsection}
|
||||
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\begin{rSection}{Education}
|
||||
{M.Eng.\ Computer Aided Engineering (Software Design \& Engineering)} \hfill {\textcolor{black!60}{Apr 2012 -- Oct 2013}}\\
|
||||
{Universit\"at der Bundeswehr M\"unchen}; thesis at Tongji University, Shanghai \hfill Thesis Grade: \textbf{1.0}\\
|
||||
{\small Thesis: \textit{Development of a Web-Based Remote Fault Diagnosis System} (Neural Networks, PSO, Fuzzy Logic)}
|
||||
|
||||
{B.Eng.\ Information and Telecommunication Technologies} \hfill {\textcolor{black!60}{Oct 2009 -- Oct 2012}}\\
|
||||
{Universit\"at der Bundeswehr M\"unchen}, Munich, Germany
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\begin{rSection2}{Certifications \& Awards}
|
||||
\item \textbf{AWS Certified Solutions Architect -- Associate}, Amazon Web Services (2024, active until Sep 2027).
|
||||
\item \textbf{Data Engineering with AWS Nanodegree}, Udacity (2026). AWS data pipeline architecture.
|
||||
\item \textbf{IBM AI Engineering Specialization}, Coursera. Deep learning, TensorFlow, Keras, Apache Spark ML.
|
||||
\item \textbf{iSAQB CPSA -- Foundation Level}, iSAQB (2016). Certified Professional for Software Architecture.
|
||||
\item \textbf{ITIL Foundation Certificate in IT Service Management}, PEOPLECERT / AXELOS (2016).
|
||||
\end{rSection2}
|
||||
|
||||
\begin{center}
|
||||
\vspace{0.1cm}
|
||||
\textit{German national; English fluent}
|
||||
\end{center}
|
||||
|
||||
\end{document}
|
||||
@@ -0,0 +1,160 @@
|
||||
# Session: NATO Joint Warfare Centre Staff Officer (2030 Digitalisation – AI Engineer)
|
||||
|
||||
## JD Info
|
||||
- **File:** `JDs/NATO_AI_ENGINEER.txt` (copied to this folder)
|
||||
- **JD source:** file provided by user; verbatim NATO JWC vacancy notice
|
||||
- **Role:** Staff Officer (2030 Digitalisation – Artificial Intelligence Engineer)
|
||||
- **Company:** NATO Joint Warfare Centre (JWC), Stavanger, Norway
|
||||
- **Bundle:** ML / AI Engineer (primary) + Staff / Senior Data Engineer (secondary)
|
||||
- **Format:** Resume (2-page, `resume.cls`) + 1-page cover letter
|
||||
- **Salary/Details:** G15; NOK 93,933 monthly tax-free starting salary; 3-year project-linked post; deadline 9 August 2026; NATO Secret clearance required.
|
||||
|
||||
## JD Analysis
|
||||
### Requirements
|
||||
| # | Requirement | Match | Evidence |
|
||||
|---|-------------|-------|----------|
|
||||
| 1 | Relevant university degree plus 3+ years' experience | Direct | M.Eng. in Software Design & Engineering; 10+ years of professional software/data/AI engineering. |
|
||||
| 2 | 3+ years developing, managing and adapting AI systems including LLMs | Direct experience / duration gap | Configured domain-grounded LLM agents in a Swisscom-owned web interface, selecting available models for Q&A and migration/data-mapping assistance; production ML inference at Bosch and NLP/speech-recognition research at Fraunhofer. The duration does not yet support a three-year LLM claim. |
|
||||
| 3 | 2+ years Python, SQL and Spark/equivalent | Direct | Long-running Python and SQL delivery; PySpark confirmed at Swisscom. |
|
||||
| 4 | Microsoft Azure Data Scientist certification or equivalent | Bridge (recruiter decision) | Active AWS Certified Solutions Architect – Associate, production AWS data-platform work, and IBM AI Engineering learning are credible adjacent evidence; do not state that they are equivalent to the Azure Data Scientist certification. |
|
||||
| 5 | Production AI deployment, optimisation and management | Direct (ML), gap (LLM-specific) | Designed and implemented ML-model integration strategy for 24/7 Bosch manufacturing; no prior production LLM deployment asserted. |
|
||||
| 6 | Fine-tuning, multimodal hybrid search, reasoning/agentic systems | Gap | No verified ownership. Learn-now plan may be described only outside experience claims. |
|
||||
| 7 | Validation, data management, ethical AI and roadmap delivery | Bridge (high) | Quality gates, governed enterprise data products, component/application ownership, and ML deployment; no formal LLM evaluation programme claimed. |
|
||||
| 8 | Stakeholder advice, coordination and multinational operational environment | Bridge (high) | Staff-level component ownership and cross-team delivery; German Armed Forces officer service (6 years, left as Second Lieutenant); Norwegian role at Vizrt. |
|
||||
| 9 | English advanced; national of a NATO member state | Direct | English fluent; German national (user-confirmed), therefore eligible to apply as a national of a NATO member state. |
|
||||
| 10 | Current or recent NATO/National clearance preferred | Gap / verify | Military service is relevant context, but no current or recent clearance is asserted. |
|
||||
|
||||
### ATS Keywords
|
||||
- **ML/AI:** artificial intelligence, machine learning, LLM, reasoning models, agentic systems, model validation, responsible AI
|
||||
- **LLM delivery:** LLM-powered applications, production deployment, fine-tuning, multimodal, hybrid search, evaluation, reliability
|
||||
- **Data/engineering:** Python, SQL, Spark, PySpark, data management, data-centric programmes, automation, Kubernetes, Docker, CI/CD
|
||||
- **Domain:** NATO, digital transformation, exercises, operational environment, multi-level security, interoperability, Geographic Intelligence
|
||||
- **Leadership:** roadmap, stakeholder collaboration, subject-matter expertise, coordination, process improvement, multinational environment
|
||||
|
||||
### Gap Assessment
|
||||
- **Direct:** Configuration of domain-grounded LLM agents for Q&A and task assistance; Python, SQL, PySpark; production ML integration; containerisation/orchestration; data pipelines; M.Eng.; advanced English; German nationality; officer-service and international-work context.
|
||||
- **Bridge:** Production ML reliability and CI/CD → production LLM operating discipline; NLP/speech-recognition contribution → language-AI context; data quality/quality gates → LLM evaluation methodology; officer and Staff-level ownership → operational coordination and mature judgement.
|
||||
- **Gap:** Three years of LLM systems; LLM fine-tuning; reasoning systems; multimodal hybrid search; formal LLM evaluation; current/recent clearance. Do not claim any of these. “Agent” refers only to the verified Swisscom assistant work; avoid broader agentic-system ownership. Azure Data Scientist remains unearned; present the active AWS certification and directly relevant AWS work as adjacent evidence, not as an equivalent credential.
|
||||
|
||||
## Company Context
|
||||
- **Mission:** The JWC prepares NATO through large, complex operational and strategic exercises. Its 2030 transformation work uses data and AI to modernise exercise planning and delivery.
|
||||
- **This role:** Help establish the JWC Data Science Team and move AI—including LLMs—into production, with validation, security and operational usability central to success.
|
||||
- **Culture:** English-language, multinational, mission-led and operationally rigorous; JWC’s 2026–2030 campaign stresses digital infrastructure, AI-enabled tools, modelling/simulation, interoperability and rapid adoption.
|
||||
- **Why them angle:** Dennis can contribute production ML/data engineering discipline and an informed military-operational perspective to a team that must turn AI experiments into dependable exercise capability. Recent JWC work with Maven Smart System and AI-enabled wargaming makes that connection concrete.
|
||||
|
||||
## Framing Strategy
|
||||
- **Lead narrative:** Production-minded data and ML engineer who has deployed ML in a constrained 24/7 environment, configures domain-grounded LLM agents, builds reliable data foundations, and brings genuine German Armed Forces officer experience to a NATO exercise setting.
|
||||
- **Reframing map:** Swisscom web-interface LLM-agent configuration with selectable models and domain knowledge → applied LLM delivery; Bosch ML model integration → production AI delivery; Swisscom component ownership/data quality → dependable data-centric operations; Fraunhofer speech recognition → applied NLP foundation; quality gates/observability → validation and reliability discipline; officer service → mature judgement in a structured, multinational defence environment.
|
||||
- **Emphasize:** Bosch ML deployment; Python/SQL/PySpark; Kubernetes/Docker/CI/CD; Fraunhofer NLP; secure/reliable enterprise delivery; German nationality; Bundeswehr officer service (six years; Second Lieutenant); prior Norway experience.
|
||||
- **Downplay:** Generic analytics/dashboard detail, older unrelated software work, exhaustive tool lists, and generic leadership language.
|
||||
- **LLM positioning, stated honestly:** Lead with Swisscom configuration of domain-grounded LLM agents for Q&A and migration/data-mapping assistance, using “grounded” or “configured” rather than “trained.” Models are selected in a Swisscom-owned web interface; do not imply API engineering, model hosting or production deployment. Include verified LiteLLM API/custom-GPT exposure in skills only if it refers to separate, confirmed work. In the cover letter, present current structured learning in evaluation, retrieval/hybrid search, agent safety and fine-tuning as preparation—not prior ownership. Pursue Azure Data Scientist Associate only if realistically completable before application/interview; it cannot be listed until earned.
|
||||
- **Certification positioning:** Put `AWS Certified Solutions Architect – Associate (active)` prominently in Certifications and pair it with the AWS migration/data-platform bullet. It supports the JD's “or equivalent” wording as cloud architecture and production-data evidence, but the resume and cover letter must never call it Azure Data Scientist equivalent.
|
||||
- **AI-authenticity guardrails:** Use fewer bullets, each anchored to a specific system, environment and responsibility. Avoid generic summaries, keyword stuffing, uniform verb–metric–method formulas, inflated superlatives and claims that cannot be discussed technically in interview. Text-detection tools are not reliable proof; credibility comes from verifiable, internally consistent detail.
|
||||
- **CL hooks:** JWC’s AI-enabled exercise transformation; AI in Audacious Training/Maven Smart System; practical production reliability under operational constraints; a German officer who later built AI/data systems in Switzerland, Germany and Norway.
|
||||
- **User directives:** Compact CV/resume with only decisive evidence; no hallucinated LLM ownership; German nationality is an application-eligibility advantage; Bundeswehr officer service should be used as relevant defence-context evidence.
|
||||
|
||||
## Critique Context (captured in Phase 0, used in /critique)
|
||||
- **Reviewer persona:** JWC Data Science/CIS leader screening for someone credible in both production AI and NATO operational culture; interested in evidence, security awareness, judgement and delivery—not AI hype.
|
||||
- **Competitive landscape:** Obvious fits will have current clearance, direct LLM fine-tuning/RAG/agentic production work, Azure certification and perhaps NATO/defence AI experience. Dennis differentiates with production ML in a continuous industrial setting, robust data infrastructure and authentic military context, but must not conceal the LLM gap.
|
||||
- **Domain vocabulary:** exercise delivery, interoperability, data-centric operations, multi-level security, validation, digital transformation, operational environment, AI-enabled decision support, responsible use.
|
||||
|
||||
## Cover Letter Plan
|
||||
- **Institution type:** International defence organisation / operational public sector
|
||||
- **Paragraph count:** 4 paragraphs, 330–380 words
|
||||
- **P1 hook:** JWC’s shift from AI experiments to AI-enabled exercise planning and delivery, including AI in Audacious Training.
|
||||
- **P2-P3 evidence:** Bosch 24/7 ML integration; Swisscom production data ownership and Python/Kubernetes delivery; Fraunhofer NLP contribution; concise officer-service and Norway context.
|
||||
- **Domain pivot:** “While my previous LLM exposure is limited to verified API/custom-GPT work, I am deliberately building the evaluation, retrieval and safety practices required for secure LLM delivery; my production ML and data-platform experience provide the operational foundation.”
|
||||
- **Jargon level:** Technical but HR-safe; use NATO terminology only where it accurately reflects the JD.
|
||||
- **Why them hook:** Contribute reliable, operator-aware AI delivery to JWC's multinational exercise transformation.
|
||||
|
||||
### Hook Verification
|
||||
- **Claim used:** JWC's AI in Audacious Training work is moving into practical support for exercise teams, with AI-enabled scenario content tested, reviewed and refined with operators.
|
||||
- **Evidence:** NATO ACT reports that the project transferred to JWC implementation in January 2026, is moving from prototype capability toward repeatable exercise value, and evaluates AI-enabled exercise design and execution with practical use and operator feedback.
|
||||
- **Source:** https://www.act.nato.int/article/ai-audacious-training/
|
||||
|
||||
## Bullet Plan
|
||||
|
||||
### Swisscom — Staff Data, Analytics & AI Engineer (5 bullets, 10 rendered lines)
|
||||
|
||||
| | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---|---|
|
||||
| * | SW-7 | Governed data products and metadata management within Swisscom's Data Mesh on AWS; frame as trustworthy, discoverable data foundations for downstream AI—not as agentic or hybrid-search delivery. | Resume-2L | 2 | Bridge |
|
||||
| * | SW-3 | Operated Python data applications on Kubernetes with GitLab CI/CD; production delivery and reliability. | Resume-2L | 2 | Direct |
|
||||
| * | SW-2 + SW-6 | Component ownership of business-critical Python/Kafka ETL, with PySpark distributed processing; data availability, quality, governance and on-call responsibility. | Resume-2L | 2 | Direct |
|
||||
| * | SW-1 | Led scoped migration of legacy ETL to AWS cloud-native services; reliable, scalable data infrastructure for AI/analytics workloads. | Resume-2L | 2 | Bridge |
|
||||
| * | SW-8 | Configured LLM agents in a Swisscom-owned web interface, selecting available models and supplying a domain knowledge base for Q&A, migration and data-mapping assistance; do not imply fine-tuning, API engineering, hybrid search or production deployment. | Resume-2L | 2 | Direct |
|
||||
| o | SW-5 | Designated team security point of contact (2025/26); cloud-security and DevSecOps training. Use only if space permits; not an award and not a clearance. | Resume-2L | 2 | Bridge |
|
||||
|
||||
### Bosch Semiconductor — Data & ML Engineer (4 bullets, 8 rendered lines)
|
||||
|
||||
| | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---|---|
|
||||
| * | BS-1 | Designed and implemented containerised ML inference for automated image-based defect classification in a continuous 24/7 production environment. | Resume-2L | 2 | Direct |
|
||||
| * | BS-3 | Application ownership for semiconductor analytics applications and upstream pipelines: SLOs, documentation, user training, vendors and stable operation. | Resume-2L | 2 | Direct |
|
||||
| * | BS-4 | ELK/Kafka anomaly-detection proof of concept with Grafana/Prometheus/Loki observability; validation/reliability bridge, clearly labelled PoC. | Resume-2L | 2 | Bridge |
|
||||
| * | BS-2 | Python/Java/C# data services over OracleDB and Hadoop/ImpalaSQL for analysis teams; structured data access in a high-throughput environment. | Resume-2L | 2 | Direct |
|
||||
| x | BS-5 | Spotfire ownership and conference presentation. Useful evidence of communication, but not selective enough for this AI/defence resume. | -- | -- | Weak |
|
||||
|
||||
### Fraunhofer CML — Research Software Engineer (2 bullets, 4 rendered lines)
|
||||
|
||||
| | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---|---|
|
||||
| * | FC-2 | Contributed ML and NLP/speech-recognition components to ARTUS, an automatic sea-rescue transcription research project; preserve the contributing role. | Resume-2L | 2 | Direct |
|
||||
| * | FC-1 | Independently introduced Jenkins CI/CD quality gates for a decision-support system; verification and delivery-discipline bridge. | Resume-2L | 2 | Bridge |
|
||||
| x | FC-3 | Maritime microservices research prototype. Solid engineering, but redundant with newer Kubernetes/Docker experience. | -- | -- | Weak |
|
||||
| x | FC-4 | Predictive-maintenance grant contribution. No outcome claim; reserve for cover-letter context only. | -- | -- | Weak |
|
||||
|
||||
### Vizrt — DevOps Engineer, Bergen, Norway (1 bullet, 2 rendered lines)
|
||||
|
||||
| | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---|---|
|
||||
| * | VZ-1 + VZ-2 | Python/C++ distributed backend delivery plus Python test automation and CI/CD quality gates; concise evidence of international Norway experience and operational-quality discipline. | Resume-2L | 2 | Bridge |
|
||||
|
||||
### Generali / Capgemini (0 recommended bullets)
|
||||
|
||||
| | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---|---|
|
||||
| x | GN-1 | Introduced BDD and led technical test-automation adoption. Strong early-career initiative, but not decisive here. | -- | -- | Weak |
|
||||
| x | GN-2–4, CA-1 | RPA, enterprise Java and early test automation. Omit to preserve relevance and readable density. | -- | -- | Weak |
|
||||
|
||||
### Additional service line (not an achievement bullet)
|
||||
|
||||
`German national | German Armed Forces Officer, 2008–2014; left service as Second Lieutenant` — place in a compact Additional Information line if the template permits. It establishes NATO eligibility and operational context; it does not imply technical, current-clearance or NATO-service experience.
|
||||
|
||||
**Recommended set:** 14 bullets / 28 rendered lines. Added after visual page-fill review: GN-1 (Generali technical ownership and team training) and BW-1 (German Armed Forces officer service). No other reserve bullets will be added unless the user requests them. **Budget Gate: PASS (user-directed compact exception).**
|
||||
|
||||
**Forced exclusions:** Any LLM fine-tuning, broader agentic-system ownership, hybrid search, multimodal solutions, formal LLM evaluation, Azure Data Scientist certification, current/recent clearance, and the disproven “three consecutive years” Security Champion claim.
|
||||
|
||||
**Focus-directive impact:** The standard ML/AI bundle would include more general data-engineering and older-career material. This plan instead adds direct Swisscom LLM-agent work and the scoped Data Mesh/metadata bridge, keeps officer service visible, and removes older or generic detail. It uses exact JD terms only where backed by work; no bullet claims fine-tuning or production LLM ownership.
|
||||
|
||||
## Output Files
|
||||
- Resume: `output/NATO_AI_ENGINEER/e2e_nato_ai_engineer_resume.tex`
|
||||
- Cover Letter: `output/NATO_AI_ENGINEER/e2e_nato_ai_engineer_cover_letter.tex`
|
||||
- Critique: `output/NATO_AI_ENGINEER/critique_nato_ai_engineer.md`
|
||||
|
||||
## Critique Summary
|
||||
- **Score:** 77.5/100
|
||||
- **Key findings:** Strong production ML/data-platform evidence, disciplined LLM framing, German nationality and officer-service relevance. The ceiling is direct LLM duration, fine-tuning/hybrid-search depth, Azure credential and current clearance.
|
||||
- **Tier 1 fixes:** Earn Azure Data Scientist only if genuinely achievable; document the Swisscom LLM-agent scope for application/interview; state clearance history truthfully in the application form.
|
||||
|
||||
## Status
|
||||
- Phase 0: DONE
|
||||
- Phase 1: DONE (14 bullets confirmed after user revision)
|
||||
- Phase 2 Resume: IN_PROGRESS
|
||||
- Summary: DONE
|
||||
- Skills: DONE
|
||||
- Experience: DONE (14 bullets; Generali and Bundeswehr added; skills trimmed to NATO-relevant evidence)
|
||||
- Compile: DONE (2 pages; all 14 experience bullets in Resume-2L range; visual layout verified)
|
||||
- Resume: DONE
|
||||
- Cover Letter: DONE (324 body words; 1 page; hook verified; visual and authenticity checks passed)
|
||||
- Critique: DONE (77.5/100; user approved finalization)
|
||||
- **Status:** SUBMITTED 2026-07-10 via NTAP.
|
||||
- **Submission files:** `Dennis_Thiessen_Resume.pdf` and `Dennis_Thiessen_Cover_Letter.pdf`
|
||||
- **Next CL:** /make-cl output/NATO_AI_ENGINEER/session_nato_ai_engineer.md
|
||||
- **Next Critique:** /critique output/NATO_AI_ENGINEER/session_nato_ai_engineer.md
|
||||
|
||||
## Resume Point
|
||||
- The original 12-bullet draft compiled cleanly to two pages but had excessive page-2 whitespace.
|
||||
- User chose a compact revision: add Generali and Bundeswehr experience only; do not add the other available bullets. Skills were reduced to direct NATO-relevant evidence.
|
||||
- Final verification: source compiled to two pages; every experience bullet passed the Resume-2L character gate; PDF pages were visually reviewed. Remaining page-2 white space is a deliberate result of the user’s concise-content directive.
|
||||
- Cover letter verification: 324 body words (about 336 including closing), one-page render, verified JWC AI in Audacious Training hook, and no AI-fingerprint rule violations.
|
||||
Reference in New Issue
Block a user