Rob Koch: interpreter preparation brief
Adapted from the existing Rob-Koch_Public-Professional-Meeting-Brief_Example.md and rechecked against the public sources below. Prepared with AI assistance in Codex; this is not a ChatGPT Deep Research export, screenshot, or transcript. The earlier working-style hypotheses have not been carried forward as facts.
Assignment boundary
Hypothetical data/AI architecture meeting. No real agenda, participant list, client records, or confirmed communication preferences were supplied. Rob is the Deaf professional in this demonstration; the interpreter is preparing to support communication, not advise on architecture.
Public professional context
AWS lists Rob as a Data Hero since 2019 and describes work in event-driven architecture and real-time data. [1]
His speaker page lists database, Kubernetes, analytics, and enterprise architecture experience. These topics are candidates for preparation, not a prediction of this meeting’s content. [2]
In his 2022 “Data what??” post, Rob compares data terminology and revises initial assumptions against researched definitions. This is an observable writing example, not proof that he prefers a particular pace, technical depth, or interpreting approach. [3]
A source issue to confirm with Rob
The Sessionize heading says “Senior Principal, Slalom”; its biography says “Principal at Slalom Build.” Ask which title and affiliation to use. Do not silently resolve the mismatch or present either as personally confirmed. [2]
Starter terminology — validate against the actual agenda
EDA — event-driven architecture: services communicate through events representing changes, such as an order being placed. [4]
Kubernetes / K8s — an open-source platform for managing containerized applications and services; K8s abbreviates Kubernetes. [5]
These are preparation definitions, not prescribed signs. Confirm meeting-specific meanings, product names, acronyms, and agreed terminology with Rob and the interpreting team.
Questions before the meeting
Ask the organizer: What decision is being made, who is attending, and can we receive the agenda, slides, diagrams, and acronym list through an approved channel?
Ask Rob: What is your role in this meeting, and which points or technical distinctions must come through accurately?
Ask Rob and the interpreting team: Which language, terminology, fingerspelling, clarification signals, pacing, and turn-taking arrangements work for this meeting?
Confirm the room or video layout, visibility of shared diagrams, and team-interpreter coordination. Do not infer access preferences from a biography.
Human review status
Not yet reviewed or approved by Rob. His replies remain blank until he provides them. On slide 31, Rob reviews this draft in his own words; on slide 32, add only the corrections he actually confirms and permits us to use.
Sources and retrieval notes
- AWS Builder Center — Rob Koch
Profile identifies a Data Hero since 2019 and describes event-driven architecture and real-time data work. Direct page extraction was empty; profile text was available through the search index. - Sessionize — Rob Koch
Speaker-page heading and biography use different role titles. Public profile statements are not confirmation of a specific meeting assignment. - Rob Koch — Data what?? (June 2, 2022)
A dated example of Rob comparing terminology, initial assumptions, and researched definitions. It is not evidence of fixed communication preferences. - AWS — What is event-driven architecture?
Primary technical source for the EDA definition. - Kubernetes — Overview
Primary technical source for Kubernetes and the K8s abbreviation.