0 Fork 0

Files

T

dennisthiessenandClaude Opus 5.5 3a9c2faf44 feat(app): NVIDIA Senior Production Engineer, DGX Cloud submitted; on-duty, GPU and networking KB gaps closed; triage 2026-10-22

Application (submitted 2026-10-22, Workday):
- NVIDIA JR2027105, Switzerland Remote. Evidence Fit 65, Stretch (SLIs and
  error budgets not evidenced), hard gate PASS, channel Weak, no cover letter.
- Package in output/NVIDIA_ProdEng_DGX_Cloud/: session, resume .tex, critique
  (Document Quality 85 before Edit 1; Tier 1 + all Tier 2 applied), verbatim JD.
- Prior NVIDIA req JR2024256 was pulled (last listed 2026-09-18; page gone
  2026-10-22): noted on that application, so there was no stacking conflict.

KB (claims.json, user-confirmed 2026-10-22):
- SW-11: current rotating engineer-on-duty role, Opsgenie alerting, alerts and
  bugs auto-create Jira tickets; he writes alert thresholds (e.g. data quality).
- BS-1: the Bosch inference ran on NVIDIA GPUs; CUDA registered forbidden as a
  skill (system context only, little configuration done).
- BS-4: the PoC included Grafana, Prometheus and Loki; ELK Stack, Grafana,
  Prometheus and Loki registered as PoC-context skills.
- networking: certification context only (AWS SA Associate); work uses
  automated landing zones.
- Extraction and CLAUDE.md log row added.

Scout state:
- decisions: RUAG Senior DevOps (Kubernetes) C5I parked (home-office terms);
  SLB Data Scientist skipped (user); NVIDIA JR2008695 skipped (C++/Rust 8y);
  JR2027105 applied; Norway/Apple/Swiss JD-read triage decisions.
- employer_reputation: SLB (Glassdoor 3.9), MazeMap and SpareBank 1
  Nord-Norge (unchecked).

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

2026-10-22 22:29:27 +02:00

3.5 KiB

Raw Blame History

On-duty alerting, networking and Bosch GPUs — user clarification

Source: direct user message, 2026-10-22, during the NVIDIA Senior Production Engineer, DGX Cloud (JR2027105) fit check. Three questions were asked because the KB has repeatedly under-recorded ordinary operations work (Ansible, Linux, Bash, Kotlin, Jenkins/GitLab).

Questions and verbatim answers

Monitoring in your current Swisscom unit: do you monitor or get alerted on your Glue/Airflow pipelines (CloudWatch alarms, failure alerts, dashboards)? Is there on-call in your current team?

Yes, we get alerted ... we are using opsgenie and we have a engineer on duty role which rotates. Bugs and Alerts also automatically create Jira issue tickets which we dann asign an fix.
Networking at work: any AWS VPC, security group or private-endpoint work at Swisscom, or firewall, DNS, proxy or load-balancer work at Bosch?

No, not really - probably only my AWS solution architect cert covers AWS network topics... but day to day work is using automated landing zones.
GPUs at Bosch: did the ML inference containers run on GPUs?

The ML inference did ran on NVIDIA GPUs (using CUDA for performance boost - but i never did much configuration there)

Follow-up questions and verbatim answers (same day)

Bosch monitoring PoC: your earlier CV says it also included Grafana, Prometheus and Loki; the Bosch reference letter only mentions ELK. Correct? and 5. Do you also write or adjust the alerts for your own pipelines, or only respond to them?
1. both are correct 2. yes, i wrote e.g. thresholds for data quality etc....

Established facts

BS-4 stack: the Bosch PoC covered ELK and Kafka plus monitoring and alerting with Grafana, Prometheus and Loki. It is still a proof of concept.
SW-11 alert definitions: he defines alert thresholds for his own pipelines; data-quality thresholds are the named example. Other alert types are not established.
Current on-duty (new claim SW-11): his current Swisscom team uses Opsgenie for alerting and has a rotating engineer-on-duty role that he takes part in. Bugs and alerts automatically create Jira tickets, which the team assigns and fixes. This is the current counterpart of the past SW-2 on-call at ART B2B.
Networking (skill networking, certification context only): no professional network configuration. AWS networking is covered by the AWS Certified Solutions Architect – Associate (26 Sep 2024, active). At work he uses automated AWS landing zones that the platform provides.
Bosch GPUs (BS-1 scope): the containerized ML inference he integrated ran on NVIDIA GPUs, with CUDA used for acceleration. He did little CUDA or GPU configuration himself.

Not established

Who built or configured the alerting, the Opsgenie routing or the Jira automation.
Which metrics or logs feed the alerts; SLIs, SLOs or error budgets at Swisscom.
Incident counts, response times, MTTR or availability figures.
Whether the on-duty role covers nights and weekends (do not write 24/7).
Any professional VPC, security-group, firewall, DNS, proxy or load-balancer work.
Building or designing landing zones or network topology.
CUDA programming or configuration, GPU tuning or GPU performance analysis. GPU model, count and serving framework at Bosch.

Canonical destination

claims.json: new claim SW-11; BS-1 scope and forbidden list; skills Opsgenie (allowed-with-context), CUDA (forbidden; system context only) and networking (certification-context-only).

3.5 KiB Raw Blame History Unescape Escape