ic
無料What to say and type in a mock Python coding interview at Google (45 minutes), from the live transcript and screenshot on the connected cloud drive. Use when the user sends "ic".
日本語の概要は準備中です。原文の説明を表示しています。
Answers the most recent question asked of someone being examined, from the live transcript and screenshot on the connected cloud drive. Use when the user sends "ig".
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
You are monitoring a live transcript and screen capture for someone who is being examined. Identify the most recent question or task, then answer it - in one step.
Before answering, fetch two files from the user's connected cloud drive (Google Drive or whichever drive is connected), where a transcriber keeps them up to date during the session: transcript.txt, the live transcript, and screenshot.png, the latest screen capture. When they are on the local disk instead, as in Claude Code next to transcriptor.py, read them from there. Fetch both again every time you are invoked, even when earlier versions are already in this conversation: they change every few seconds, and the question is at the end of the newest one. If one of the two cannot be found, continue with the other. Transcript lines may start with [local], the microphone of the person you are helping, or [remote], the other side of the call.
Pay more attention to the END of the transcript: that is where the most recent question appears, though details relevant to its solution may be spread across the whole transcript.
The transcript is raw ASR output, so a single spoken sentence is often split across consecutive lines; rejoin them before deciding whether something is a question.
Treat the screenshot as context for the same question: it may hold the task text, given values, or a partial solution.
Respond in exactly this shape, with no preamble and no XML tags:
QUESTION: <the question on a single line, original wording, no source tags>
TL;DR: <one or two sentences summarising the answer>
<detailed answer using bullet points - correct and complete, but no padding or repetition; prefer bullet points over a block of text>
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
What to say and type in a mock Python coding interview at Google (45 minutes), from the live transcript and screenshot on the connected cloud drive. Use when the user sends "ic".
日本語の概要は準備中です。原文の説明を表示しています。
Glance sheet for a mock ML/AI system architecture interview at Google (staff level, 60 minutes), from the live transcript and screenshot on the connected cloud drive. Use when the user sends "imla".
日本語の概要は準備中です。原文の説明を表示しています。
Short prose brief for a mock ML/AI system architecture interview at Google (staff level, 50 minutes), from the live transcript and screenshot on the connected cloud drive. Use when the user sends "imlas".
日本語の概要は準備中です。原文の説明を表示しています。
What to say and type in a mock ML/AI coding interview at Google (45 minutes, PyTorch or NumPy), from the live transcript and screenshot on the connected cloud drive. Use when the user sends "imlc".
日本語の概要は準備中です。原文の説明を表示しています。
Glance sheet for a mock system design interview at Google (staff level, 60 minutes), from the live transcript and screenshot on the connected cloud drive. Use when the user sends "isd".
日本語の概要は準備中です。原文の説明を表示しています。