Application - Kongsberg Discovery / Seatex, Lead Engineer DevOps and Test Infrastructure (Trondheim): resume, cover letter (+ paste text), verbatim JD, session and critique. Submitted 2026-10-08 via EasyCruit as a deliberate cold application on a user override of the embedded-SW hard gate (Evidence Fit 69, Document Quality 84). Recorded in applications.json and decisions.json. - Google Senior SWE Full Stack Commerce: session and verbatim JD from 2026-10-03 (no-go on the frontend gap, held, not submitted). Knowledge base - claims.json: ED-1 (embedded/robotics coursework, none since studies), SW-9 (current unit testing, pytest), new skills (pytest, unit testing, embedded systems (coursework), VHDL, robotics (coursework)), and Jenkins and GitLab CI/CD registered from existing GN-1/FC-1/BS-6/SW-3 scopes. - Earlier uncommitted KB work: 2026-09-18 Python frameworks / enterprise SaaS clarification, 2026-10-03 data-product design / no-frontend clarification, 2026-10-06 working-model rule (3 homeoffice days baseline) in config.md and application_strategy.md, plus related experience/bundle/taxonomy updates. - CLAUDE.md corrections log: 2026-10-08 entry for the three canonical gaps. Scout - 2026-10-08 run triaged by JD read: NVIDIA DGX Cloud Senior Production Engineer, Google SRE III Prod AI / Senior SRE / Staff Shopping Graph and Amazon RIVR DevOps logged as maybe; GenAI FDE family, Kraken AI Platform, PostFinance DevOps and five Kdo Cy reqs logged as skip with reasons. Housekeeping - .gitignore: ignore .cache/ and raw HTML page dumps under output/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
119 lines
7.4 KiB
Markdown
119 lines
7.4 KiB
Markdown
# Skills Taxonomy — Evidence-First
|
||
|
||
> Canonical authority: `resume_builder/canonical/claims.json`.
|
||
> This file helps select and group skills; it may not promote a skill beyond its canonical evidence level.
|
||
|
||
## Evidence Levels
|
||
|
||
| Level | Meaning | Output rule |
|
||
|---|---|---|
|
||
| Production — current | Used in current professional delivery | May appear plainly when relevant |
|
||
| Production — historical | Shipped professionally, but not current | Include with role/date context when recency matters |
|
||
| Hands-on — current | Used directly, but without verified production ownership | Use precise verbs such as used, configured or integrated |
|
||
| Project / proof of concept | Used in a bounded PoC | Label the PoC; never imply platform-scale operation |
|
||
| Certification / coursework | Learned through formal study | Keep in certification context; not professional experience |
|
||
| Unverified / never used | No reliable evidence | Do not include |
|
||
|
||
Do not use Expert/Proficient/Familiar labels in resumes. Evidence and recency are more useful than self-ratings.
|
||
|
||
## Current Production Core
|
||
|
||
| Skill | Evidence | Typical use |
|
||
|---|---|---|
|
||
| Python | Swisscom pipelines/apps; prior Bosch/Vizrt work | Always for data/platform roles |
|
||
| SQL | Swisscom and prior data roles | Always for data roles |
|
||
| PySpark | Swisscom current work | When distributed processing is relevant |
|
||
| Apache Kafka | Swisscom production ingestion | Data/event-driven roles |
|
||
| Apache Airflow | Swisscom AWS migration scope | Orchestration/data roles |
|
||
| AWS | Swisscom production work; SAA certification | AWS-relevant roles |
|
||
| S3, Glue, Athena, Iceberg, Redshift | Swisscom owned-domain migration/data products | Name only relevant services |
|
||
| CloudFormation / IaC | Swisscom production provisioning | Say CloudFormation; never substitute Terraform |
|
||
| Kubernetes, Docker | Swisscom application delivery; Bosch ML integration | Production platform/MLOps roles |
|
||
| GitLab CI/CD | Swisscom delivery | Platform and engineering roles |
|
||
| Oracle, Teradata | Swisscom pipelines | Data roles when relevant |
|
||
|
||
## Historical Production Evidence
|
||
|
||
| Skill | Evidence | Constraint |
|
||
|---|---|---|
|
||
| Java | Bosch, Fraunhofer, Generali | Historical; do not imply current daily use |
|
||
| C# | Bosch and Fraunhofer | Historical; strong when Spotfire/.NET is relevant |
|
||
| C++ | Vizrt distributed backend | Limited historical evidence |
|
||
| JavaScript / Express.js | Fraunhofer MISSION | Historical and bounded; TypeScript is unverified |
|
||
| Hadoop / Impala | Bosch data services | Historical production context |
|
||
| Ansible | Bosch ML integration | Historical production context |
|
||
| Jenkins | Fraunhofer and Generali | Historical production context |
|
||
| BDD, Selenium, JBehave | Generali | Earlier-career testing evidence |
|
||
| TIBCO Spotfire | Bosch co-ownership and C# extensions | Preserve co-ownership |
|
||
|
||
## ML, AI and Observability
|
||
|
||
| Skill | Evidence level | Safe framing |
|
||
|---|---|---|
|
||
| ML inference deployment | Production — historical | Integrated containerized inference into a 24/7 Bosch fab |
|
||
| Image classification | Production application context | Worked on inference integration; model-training ownership not verified |
|
||
| MLOps | Bounded production evidence | Use only when defined as deployment/operation, not full model lifecycle |
|
||
| NLP / speech recognition | Research-project contribution | Contributed components at Fraunhofer; no publication/model ownership |
|
||
| ELK, Kafka anomaly detection | Proof of concept | Always retain the PoC label |
|
||
| Grafana, Prometheus, Loki | Proof-of-concept/monitoring context | Do not imply enterprise observability ownership |
|
||
| LiteLLM | Hands-on — current | LLM API gateway use/integration; no serving-platform ownership |
|
||
| Domain-grounded assistants/custom GPTs | Hands-on — current | Configured with curated knowledge; no fine-tuning or formal evaluation |
|
||
| Copilot, Kiro | Hands-on — current | AI-assisted engineering tools, not LLM product engineering |
|
||
|
||
| Linux administration | Professional 2020–2022 (BS-6) + personal and current (PP-3) | Employer-side use ended Dec 2022; PP-3 is a personal Debian server and must be named as such. Not evidence of physical-datacenter work |
|
||
| Ansible | Professional — intensive at Bosch (BS-6) | Configuration management and IaC, including self-written extensions. Does NOT license Terraform. **GitOps is forbidden** — push-based execution, no reconciliation agent |
|
||
| Bash / shell scripting | Professional-historical + personal-current (BS-6, PP-3) | Added to `claims.json` 2026-09-05. Does NOT license Groovy, nor systems/kernel-level claims |
|
||
|
||
## Personal-Project Framework Experience
|
||
|
||
| Skill | Evidence level | Safe framing |
|
||
|---|---|---|
|
||
| Django, Flask, FastAPI | Project / proof of concept — private/hobby projects (PP-4) | Used in personal projects, user-confirmed 2026-09-18. Never used professionally. Project details, dates and depth are not established; do not attach to an employer or a named project without confirmation. |
|
||
|
||
## Certification-Only Signals
|
||
|
||
| Skill | Evidence |
|
||
|---|---|
|
||
| TensorFlow / Keras | IBM AI Engineering coursework |
|
||
| PyTorch | **Certification-backed** (IBM AI Engineering, 4 Jun 2020, verify code 3ZBZFVAL6A34). `claims.json` output policy is `certification-context-only`: list only beside the certificate |
|
||
| Spark ML | Coursework context only unless professional evidence is added |
|
||
| AI for Trading / quantitative ML | Udacity/WorldQuant Nanodegree |
|
||
|
||
## Forbidden Until New Evidence Is Added
|
||
|
||
- LangChain, LangGraph, LlamaIndex, AutoGen, CrewAI or Semantic Kernel
|
||
- Azure, Azure ML, Azure OpenAI or AKS
|
||
- GCP, BigQuery, Dataflow or Flume hands-on experience
|
||
- Terraform
|
||
- Formal model or LLM evaluation
|
||
- LLM fine-tuning, red-teaming or model-training ownership
|
||
- Enterprise SaaS/SSO administration — user confirmed 2026-09-18 that he has not performed it. Do not infer enterprise identity administration from personal hosting or secrets-management work.
|
||
- TypeScript
|
||
- Frontend/UI development — user answered no to frontend experience on 2026-10-03. Backend JavaScript and Selenium UI testing do not establish frontend development; do not claim Full Stack expertise.
|
||
- Petabyte-scale ownership
|
||
|
||
## Certifications
|
||
|
||
| Certification | Issuer | Year/status |
|
||
|---|---|---|
|
||
| AWS Certified Solutions Architect — Associate | AWS | 2024; active to Sep 2027 |
|
||
| Data Engineering with AWS Nanodegree | Udacity | 2026 |
|
||
| iSAQB CPSA — Foundation | iSAQB | 2016; no expiry |
|
||
| ITIL Foundation | PEOPLECERT / AXELOS | 2016; no expiry |
|
||
| AI for Trading Nanodegree | Udacity / WorldQuant | 2021 |
|
||
| IBM AI Engineering Specialization | IBM / Coursera | **Completed 4 Jun 2020**, no expiry, verify code 3ZBZFVAL6A34 (certificate read 2026-08-27). Explicitly non-credit — never present as an academic qualification |
|
||
|
||
The Swisscom Security Champion assignment is not a certification and does not belong in this table.
|
||
|
||
## Resume Grouping
|
||
|
||
Use 4--6 compact lines, selected for the JD. A normal International Tech grouping is:
|
||
|
||
1. Languages: Python, SQL; selected historical languages only when required.
|
||
2. Data: Kafka, Airflow, PySpark, Oracle/Teradata, data products and governance.
|
||
3. Cloud/platform: AWS services, CloudFormation, Kubernetes, Docker, GitLab CI/CD.
|
||
4. ML/operations: ML inference deployment and bounded observability evidence.
|
||
5. Certifications: one line, only the most relevant credentials.
|
||
|
||
Never add a skill only to mirror a JD. Every listed skill must have a canonical evidence level and an interview-ready example.
|