Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

Comment on the key moments of an interview, in the report and the replay

Đang mở
  • Có gì không ổn?
#258 2 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
45/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
rust
Lĩnh vực
backend-api-design, full-stack

Hướng nghiên cứu

Start from where phase judgments are produced and grounded by quote_is_grounded, then from where the report is assembled from the in-memory session, since the moment rules (hint requested, failed-then-passed test run, long response window, first REACTO/STAR step, large rewrite) must read recorded session events. Then trace the replay page's existing "Moments" list to attach notes to matching entries, using event occurrence times rather than evidence-recording times (see #169). Done means a capped "Key moments" section renders with quotes verified against the session, ungrounded notes dropped, scores unchanged, and replay links only when a recording exists.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

Who is affected

Candidates reviewing an interview afterwards. The report says what went well and what to improve, but in general terms ("relied on hints", "could have planned the dictionary update after the lookup"). It does not say where in the interview each of those happened. The replay page lists every editor snapshot, test run and response window under "Moments", but leaves the candidate to work out which ones matter and why.

Desired outcome

A handful of moments, picked from what the session recorded, each with one or two sentences of coaching tied to its time. They appear in the report as a "Key moments" section, and in the replay as notes on the matching entries under "Moments", so the candidate can open the moment and see the code and transcript as they were.

An example from one of my local test interviews, on Chargeback Pair Match:

  • 04:40, tests failed on [3,2,4], 6. You read the failing case, saw that 3 had matched itself, and moved the insert after the lookup. Next time, list the case where the target is twice one amount before writing the loop, and the bug never appears.

Proposed shape

  1. The platform picks the moments, by rule. The session already records the events that make a moment worth a note, so a model does not need to search for them: a hint requested (given, or withheld), a test run that failed and a later one that passed, a long response window, the first time each REACTO or STAR step was recorded, and a large rewrite of the code. A cap, for example at most six, keeps the list short.
  2. The report model writes the notes, grounded the way the phase judge is. Each note must quote the candidate's words or the code from that moment, and the server keeps a note only when the quote is found there, as quote_is_grounded does for phase judgments. A note with no grounded quote is dropped, not shown with a warning. Notes coach; they do not score, and they change nothing in the report's scores.
  3. The times come from when the event happened, not from when its evidence was recorded, so the notes do not repeat #169.
  4. It works without recording. The report is written from the session in memory, so the "Key moments" section does not need recording to be provisioned. The links into the replay appear only when a recording exists.

Later, and optional: a highlight video

With the moments and their notes in hand, a short video could walk through them: the code at each moment, the transcript as captions, and the note as narration. HyperFrames renders HTML compositions to video and would suit this. It needs Node.js, a headless Chrome and FFmpeg, which the runtime deliberately does without, so it belongs in an offline script that reads a downloaded report or replay, not in the server. It should use only the code, the board and the transcript, never the camera.

Open questions

  • Should the moment rules be fixed, or depend on the interview loop (coding only, coding plus behavioral, whiteboard)?
  • Does the note pass belong in the report call, or in a separate call after it? A separate call adds latency but keeps the report schema unchanged.
  • How many moments are useful before the list becomes another wall of text?

Related: #169 (evidence timestamps), #242 (a review aimed at learning).

Ngôn ngữ chính
Rust
Star
160
Fork
64
Merge trung bình
1 ngày 10 giờ
Pull request đã merge (30 ngày)
116

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của sysprog21/codetrial

Tất cả issue của sysprog21/codetrial

Issue tương tự

Thêm issue về Rust

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.