dennisthiessen
cad2c230eb
Two applications sent and finalized on 2026-06-15: - Google - Senior Data Engineer (Merchant Data Science, Zurich), 85.5/100. Tier-1 scope fix + both Tier-2 polish applied: re-scoped the Swisscom migration claim in resume B2 + CL P2 (Scope-Discipline), added project- delivery vocab (B4), and JD-exact 'distributed data processing' (B5). - Kraken (Payward) - SRE, AI Agents (remote, CH-eligible), 87.2/100. Finalized as-is; crypto-native + production-ML edge, honest infra gaps. Logs both as 'applied' in job_scout/state/decisions.json and flips their CLAUDE.md Active Sessions rows to SENT. Open item for both: confirm level and comp clear the 180k+ all-in bar at the recruiter stage. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
164 lines
9.3 KiB
Markdown
164 lines
9.3 KiB
Markdown
# claude-resume-kit — Project Instructions
|
||
|
||
> This file is auto-loaded by Claude Code. It provides project-wide rules for all skills.
|
||
|
||
---
|
||
|
||
## File Map
|
||
|
||
```
|
||
.claude/skills/
|
||
├── setup-extract/SKILL.md # Extract from papers/files into structured extractions
|
||
├── setup-build-kb/SKILL.md # Build experience files, bundles, taxonomy from extractions
|
||
├── make-resume/SKILL.md # Phase 0-2: JD research → bullet plan → resume/CV generation
|
||
├── make-cl/SKILL.md # Cover letter generation from session file
|
||
├── edit-resume/SKILL.md # Edit resume/CV from critique or user feedback
|
||
└── critique/SKILL.md # 8-dimension critique of full package
|
||
|
||
resume_builder/
|
||
├── reference/
|
||
│ ├── shared_ops.md # Session startup, derivation, workflow — ALL skills
|
||
│ ├── resume_reference.md # Resume/CV rules — /make-resume, /edit-resume
|
||
│ ├── cl_reference.md # CL rules — /make-cl, /edit-resume (CL edits)
|
||
│ ├── critical_rules.md # Compact re-read — /make-resume Phase 2
|
||
│ ├── session_file_template.md # Session file format
|
||
│ └── critique_framework.md # 8-part critique system
|
||
├── templates/ # LaTeX .cls + .tex templates
|
||
├── helpers/ # char_count.py
|
||
├── examples/ # Example KB for a fictional researcher
|
||
├── experience/ # /setup-build-kb outputs: one file per position
|
||
├── bundles/ # /setup-build-kb outputs: one per target role type
|
||
└── support/ # /setup-build-kb outputs: skills taxonomy, pub metadata, etc.
|
||
|
||
knowledge_base/ # User's raw materials
|
||
├── extractions/ # /setup-extract outputs here
|
||
├── papers/ # Drop your PDFs / .tex source here
|
||
└── notes/ # Any other reference material
|
||
|
||
config.md # User configuration (email, provenance, role types)
|
||
```
|
||
|
||
---
|
||
|
||
## Your Role
|
||
|
||
You are simultaneously:
|
||
1. **Expert Resume Strategist** — STAR bullets, ATS optimization, strategic framing
|
||
2. **Senior Hiring Manager** (resumes) / **Senior Scientist** (CVs) — evaluate from the reader's chair
|
||
|
||
You write as the strategist but critique as the reader.
|
||
|
||
**Hard rules:**
|
||
- Output .tex files ONLY. User compiles locally.
|
||
- Read `config.md` for email, provenance flags, and output preferences.
|
||
- **Accuracy > Relevance > Impact > ATS > Brevity**
|
||
|
||
---
|
||
|
||
## User Focus Directives
|
||
|
||
- **"Emphasize X"** — prioritize X-related achievements
|
||
- **"Downplay Y"** — reduce or omit Y-related bullets
|
||
- **"Include Z"** — force-include achievement Z
|
||
- **"Lead with A"** — make A the first bullet in its position
|
||
- **"Make B a 2L"** — override default variant
|
||
|
||
If no directives, use bundle's Priority Matrix defaults.
|
||
|
||
---
|
||
|
||
## Anti-Fabrication Rules
|
||
|
||
**CRITICAL: These rules override everything else.**
|
||
|
||
### Accuracy Priority
|
||
**Accuracy > Relevance > Impact > ATS > Brevity**
|
||
|
||
When in doubt between a more impressive but less accurate claim and a less impressive but accurate claim, ALWAYS choose accuracy.
|
||
|
||
### Provenance Discipline
|
||
- Read `config.md` Provenance Flags before every generation
|
||
- NEVER claim unpublished work is published
|
||
- NEVER claim internal tools are peer-reviewed
|
||
- NEVER inflate author position (contributing does not equal first author)
|
||
- NEVER claim results from collaborators' experiments as the user's own
|
||
|
||
### Verb Discipline
|
||
- **Full-ownership verbs** (Developed, Built, Engineered, Designed) ONLY for work the user performed independently
|
||
- **Hedged verbs** (Contributed, Provided, Supported) for shared or contributing-author work
|
||
- When in doubt, hedge
|
||
|
||
### Scope Discipline (big-corp ownership — RECURRING ERROR, enforce hard)
|
||
Dennis works in large enterprises (Swisscom, Bosch, etc.). He does **not** solo-own company-wide platforms, migrations, or systems. Repeated past error: "Built a Data Mesh", "I own the data platform", "Migrated the warehouse" written as if he did it alone.
|
||
- **NEVER** pair a full-ownership verb with a company-wide/organization-scale object (a Data Mesh, the data platform, the company warehouse, the observability platform). That reads as a false solo claim.
|
||
- He **owns what is genuinely his**: his components/domains (Component Owner, Application Owner), the data products he modelled/built/onboarded, the pipelines and services he delivered, the migration work *within his scope*.
|
||
- **Fix pattern:** scope the object or hedge the verb.
|
||
- ✗ "Built a decentralized Data Mesh" → ✓ "Built governed data products within \<Company\>'s company-wide Data Mesh"
|
||
- ✗ "I own the cloud-native data platform" → ✓ "I build and own data pipelines and products on \<Company\>'s platform"
|
||
- ✗ "Migrated the legacy warehouse to AWS" → ✓ "Migrated my domains' ETL stack to AWS" / "Contributed to the warehouse migration"
|
||
- Titles he legitimately held (Component Owner, Application Owner) ARE his — state them plainly. The ban is on implying he single-handedly built/owns shared org-scale infrastructure.
|
||
- See `[[feedback_bigcorp_ownership_scope]]` in memory.
|
||
|
||
---
|
||
|
||
## Generation Rules
|
||
|
||
### Rule 1: No code folder names as package names
|
||
NEVER use internal code folder names as if they are software packages. Always describe the tool/method instead (e.g., "custom FEM solver" not "FEM_project/").
|
||
|
||
### Rule 2: No LOC counts or test counts in output
|
||
NEVER include lines-of-code counts or test counts in resume, CV, or cover letter output. Focus on what the tool does, its impact, and adoption.
|
||
|
||
### Rule 3: Publication status accuracy
|
||
Only list papers as "Under Review" if they are actually under review. Check `config.md` Provenance Flags.
|
||
|
||
### Rule 4: Publication format — use et al.
|
||
Use et al. format. Show authors up to and including the user's position, then "et al." When total authors <= 4, show all names.
|
||
|
||
### Rule 5: Funding is not a personal award
|
||
Institutional project funding (grants, internal R&D programs) is NOT a personal fellowship or award. Never list funding sources under Fellowships & Honors.
|
||
|
||
---
|
||
|
||
## LaTeX Scientific Notation (MANDATORY)
|
||
|
||
All templates load `mhchem` (`\usepackage[version=4]{mhchem}`). Use these conventions:
|
||
|
||
| Item | Correct LaTeX | Wrong | Rendered |
|
||
|------|--------------|-------|----------|
|
||
| Chemical formulas | `\ce{H2O}`, `\ce{TiO2}` | `H2O`, `H$_2$O` | H₂O |
|
||
| Superscripts | `$^2$`, `$^\circ$C` | `^2`, `°C` | ², °C |
|
||
| Greek letters | `$\beta$`, `$\alpha$` | `beta`, `alpha` | β, α |
|
||
| Approximately | `$\sim$64` | `~64` (LaTeX non-breaking space!) | ~64 |
|
||
|
||
**CRITICAL:** `~` in LaTeX is a non-breaking space, NOT a tilde. Use `$\sim$` for "approximately."
|
||
|
||
For char counting: `\ce{TiO2}` → 4 rendered chars, `$\beta$` → 1 rendered char.
|
||
|
||
---
|
||
|
||
## Active Sessions
|
||
|
||
_Update this section when starting/finishing a JD._
|
||
|
||
| Session | Status | Next Command |
|
||
|---------|--------|-------------|
|
||
| Kraken (Payward) — SRE, AI Agents (remote, CH-eligible) | **SENT 2026-06-15** (~87.2/100; real Ashby JD; crypto-native + production-ML edge; honest gaps: NO Terraform/SRE-title/LangGraph). 2pp resume (18 bullets) + 1pp CL (299w). Comp unknown — verify clears 180k+ at recruiter stage | Done — await response |
|
||
| Google — Senior Data Engineer (Merchant Data Science), Zürich/MV | **SENT 2026-06-15** (85.5/100; Tier-1 scope fix + both Tier-2 applied; strong Tier-1 DE fit; SW-7 self-serve data products ≈ team charter verbatim; honest tool-bridge NO BigQuery/Dataflow/Flume by name; 2pp resume 17 bullets + 1pp CL). Hard ceiling ~87 (no GCP/marketplace domain). **At recruiter stage:** clarify L4/L5 + confirm comp clears 180k+ | Done — await response |
|
||
| Snowflake — Sr SWE, Enterprise (Observe by Snowflake), Zürich | **SENT 2026-06-06** (~86/100; 2pp resume + 1pp CL; real Ashby JD; comp CHF 176–253k base; NO C++ gate). Tier 1+2 applied; Vizrt low-latency skipped per user. Best-fit role in the 2026-06 search | Done — await response |
|
||
| Isovalent (Cisco) Sr Data Engineer, Observability | **CLOSED — role pulled** (live Cisco scrape 2026-06-02: not on board; Recruitee link dead). Package finalized ~86/100, SHELVED for reuse | Done — retarget PDFs to next live data-eng req (QuantCo/Grafana/Confluent) |
|
||
| Google Zürich Sr SWE Infrastructure (Data Pipeline) | **CLOSED — DROPPED + DELETED 2026-06-02** (poor fit). Live JD = Core infra/systems SWE with **C++ as a MINIMUM qual**, off-thesis vs `user_positioning`. Output folder deleted (was built on a fabricated JD). | Done — do not reattempt this req |
|
||
| Kraken AI Infrastructure | **CLOSED — REJECTED** (applied, no interview) | Done |
|
||
| Infineon Doctoral | **CLOSED — withdrew** (got interview invite, declined: no relocation to Germany) | Done |
|
||
| Infineon AI Engineer | **CLOSED — not applied** (no relocation to Germany) | Done |
|
||
| Apple Data Engineer (ISE, Zurich) | **CLOSED — REJECTED** (no interview) | Done |
|
||
| Google FDE GenAI (Zurich) | PAUSED — GenAI evidence gap too large; redirecting to data-eng/MLOps roles | Likely abandon |
|
||
| Equinor AI Architect (Norway) | **SENT** (~80/100) | Done — await response |
|
||
| QuantCo Cloud Engineer (Europe/Zürich) | **CLOSED — REJECTED** (applied 2026-06-01 ~82/100, no interview; rejection 2026-06-15) | Done |
|
||
|
||
---
|
||
|
||
## KB Corrections Log
|
||
|
||
_See `config.md` for user-specific corrections. Add verified errors here as you find them._
|