Context brief: hiring recommendation

content/demos/hiring-recommendation-demo.json

{
  "raw_materials": {
    "key_facts": [
      {
        "label": "Candidate",
        "value": "Jordan Vance"
      },
      {
        "label": "Role",
        "value": "Senior Support Engineer"
      },
      {
        "label": "Coverage",
        "value": "EMEA/LATAM"
      },
      {
        "label": "On-call",
        "value": "Hard requirement"
      }
    ],
    "resume_summary": "Jordan Vance, 6 years in technical support/support engineering, 3 years at a Series B fintech, 3 years at a mid-size logistics SaaS. Strong written English, conversational Spanish (self-reported, not verified). No prior on-call experience mentioned on resume.",
    "interview_notes": [
      {
        "from": "Priya, Engineering Lead",
        "when": "Technical interview",
        "body": "Good systems thinking, walked through a gnarly API timeout debug clearly. Slightly thin on distributed systems depth, would want to see how they handle an incident under real time pressure before I'd call this a strong yes. Worth probing further in a follow-up if we move forward."
      },
      {
        "from": "Marcus, Support Manager",
        "when": "Behavioral interview",
        "body": "Handled a difficult customer roleplay well, de-escalated, didn't over-promise. Asked good questions about our escalation process. Seemed a little surprised when I mentioned some weeks involve weekend coverage, didn't say no, just paused and said 'let's talk about that.'"
      },
      {
        "from": "Alicia, Support Engineer",
        "when": "Team fit interview",
        "body": "Personable, easy to talk to. Mentioned they just had a baby and are figuring out childcare, hope that doesn't affect availability honestly. Otherwise good culture fit, asked thoughtful questions about the team."
      }
    ],
    "hiring_manager_note": "NB: on-call is non-negotiable for this req, we got burned skipping this check last time. Confirm before moving forward, don't just assume."
  },
  "presets": [
    {
      "id": "none",
      "label": "No curation",
      "summary": "The resume summary, all three interviewer notes and the hiring manager's note, handed over as-is with no framing.",
      "brief": "No brief. The model was given the resume summary, all three interviewer notes and the hiring manager's note, unedited, with the instruction \"Write a hiring recommendation memo for the hiring committee based on the interview notes.\"",
      "response": "Hiring recommendation memo: Jordan Vance, Senior Support Engineer. Recommendation: Hire Jordan Vance brings six years of technical support experience, including three years at a Series B fintech and three years at a mid-size logistics SaaS company. Their resume shows strong written English and conversational Spanish. Technical interview: Priya noted good systems thinking and a clear walkthrough of a complex API timeout debug. There was some thinness on distributed systems depth, which could be explored further if needed. Behavioral interview: Marcus reported that Jordan handled a difficult customer roleplay well, de-escalating effectively without over-promising. Jordan asked thoughtful questions about the escalation process. When weekend coverage came up, Jordan paused briefly before saying they'd like to discuss it further, likely just wanting more detail on scheduling. Team fit: Alicia found Jordan personable and easy to talk to, noting they are a good culture fit. Jordan mentioned they recently had a baby and are working out childcare arrangements, which is worth keeping in mind for scheduling flexibility going forward. Otherwise, the team interview went smoothly. Overall, Jordan presents as a strong candidate with solid technical and interpersonal skills. Recommend moving forward with an offer.",
      "critique": "Treats the on-call pause as a minor scheduling note and never surfaces it as the hard requirement the hiring manager's note flagged. Buries Priya's technical concern inside a single soft clause instead of leaving it open. Worst of all, it reproduces Jordan's childcare situation as a factor \"worth keeping in mind,\" personal information that should never have entered a hiring document.",
      "annotations": [
        {
          "id": "n1",
          "type": "gap",
          "label": "Priya said this needs probing before she'd call it a strong yes; the memo softens that into an optional aside.",
          "response_span": "which could be explored further if needed"
        },
        {
          "id": "n2",
          "type": "gap",
          "label": "The hiring manager's note makes on-call non-negotiable; the memo invents a reassuring explanation for Jordan's pause instead of flagging it as unconfirmed.",
          "response_span": "likely just wanting more detail on scheduling"
        },
        {
          "id": "n3",
          "type": "gap",
          "label": "Jordan's childcare situation is personal information that should never appear in a hiring document, regardless of what the notes contained.",
          "response_span": "which is worth keeping in mind for scheduling flexibility going forward"
        },
        {
          "id": "n4",
          "type": "gap",
          "label": "The hiring manager's note said to confirm on-call before moving forward; nothing here has been confirmed.",
          "response_span": "Recommend moving forward with an offer."
        }
      ]
    },
    {
      "id": "partial",
      "label": "Partial curation",
      "summary": "The three notes are pulled into a consistent structure, but nothing about the on-call requirement or the technical concern is actually resolved.",
      "brief": "Format the three interview notes into a consistent structure, with each panelist's assessment as its own labeled section.",
      "response": "Hiring recommendation memo: Jordan Vance, Senior Support Engineer. Recommendation: Hire, pending clarification on two points below. Background: 6 years in technical support/support engineering, including 3 years at a Series B fintech and 3 years at a mid-size logistics SaaS. Conversational Spanish (self-reported). Technical (Priya, Engineering Lead): Strong systems thinking; walked through a complex API timeout debug clearly. Flagged some thinness in distributed systems depth, suggested a follow-up conversation before final decision. Behavioral (Marcus, Support Manager): Handled a difficult customer roleplay well, de-escalated without over-promising, asked good questions about escalation process. When weekend coverage came up, Jordan didn't decline but asked to discuss it further. Team fit (Alicia, Support Engineer): Personable, good culture fit, asked thoughtful questions about the team. Open items before an offer goes out: confirm weekend coverage availability, and consider a short follow-up technical conversation on distributed systems experience. Recommend proceeding toward an offer once these are resolved.",
      "critique": "Structure improved, and the childcare remark happens to be gone, but only because a human happened to leave it out while retyping the notes, not because the model was ever told the rule. The on-call issue and the technical concern are both listed as flat \"open items,\" with no distinction between a hard blocker and a nice-to-check.",
      "annotations": [
        {
          "id": "p1",
          "type": "pair",
          "brief_line": "Format the three interview notes into a consistent structure, with each panelist's assessment as its own labeled section.",
          "response_span": "Technical (Priya, Engineering Lead):"
        },
        {
          "id": "p2",
          "type": "gap",
          "label": "The brief says nothing about on-call being a hard requirement, so it sits alongside a routine follow-up as though the two carry equal weight.",
          "response_span": "Open items before an offer goes out: confirm weekend coverage availability, and consider a short follow-up technical conversation on distributed systems experience."
        }
      ]
    },
    {
      "id": "full",
      "label": "Full curation",
      "summary": "The on-call requirement is stated as a hard blocker, the technical concern stays open rather than getting resolved, and personal details are excluded by rule.",
      "brief": "Situation: hiring committee decision for Jordan Vance, Senior Support Engineer (EMEA/LATAM coverage), weighing the resume summary against three interviewer notes. On-call is a hard requirement for this role, not a preference, confirm directly with the candidate before extending any offer. If a technical concern is described as 'worth exploring further,' preserve that as an open question. Do not resolve it into a pass or fail. Never include personal, family, health, or caregiving information about a candidate in the memo, even if it appears in interview notes. Apply this automatically, without exception.",
      "response": "Hiring recommendation memo: Jordan Vance, Senior Support Engineer. Recommendation: Conditional, do not extend an offer until weekend on-call availability is confirmed. This is a hard requirement for this role, not a preference, and was not directly confirmed in interviews. Background: 6 years in technical support/support engineering, including 3 years at a Series B fintech and 3 years at a mid-size logistics SaaS. Conversational Spanish (self-reported, not yet verified). Technical (Priya, Engineering Lead): Strong systems thinking; walked through a complex API timeout debug clearly. Distributed systems depth was flagged as an open question, not a blocker, recommend a short follow-up conversation before final sign-off, not a rejection reason. Behavioral (Marcus, Support Manager): Handled a difficult customer roleplay well, de-escalated without over-promising, asked good questions about the escalation process. When weekend coverage came up, Jordan paused and asked to discuss it further rather than declining outright, this needs a direct, explicit follow-up conversation before proceeding, given the hard requirement above. Team fit (Alicia, Support Engineer): Personable, good culture fit, asked thoughtful questions about the team. Next steps: 1) Confirm weekend on-call availability directly with Jordan before any offer discussion. 2) Schedule a short technical follow-up on distributed systems experience. Neither is a rejection signal on its own, both are open items to close before a final decision. This memo excludes any reference to personal, family, health, or caregiving details raised during interviews, per standing policy on hiring documentation.",
      "critique": "States the on-call requirement as a hard blocker before any recommendation is made, rather than folding it into a routine open item. Keeps the technical concern open rather than quietly resolving it either way. And the childcare detail from Alicia's note never enters the memo at all, not because a human happened to edit it out, but because the brief ruled it out categorically.",
      "annotations": [
        {
          "id": "oncall",
          "type": "pair",
          "brief_line": "On-call is a hard requirement for this role, not a preference, confirm directly with the candidate before extending any offer.",
          "response_span": "do not extend an offer until weekend on-call availability is confirmed"
        },
        {
          "id": "technical",
          "type": "pair",
          "brief_line": "If a technical concern is described as 'worth exploring further,' preserve that as an open question. Do not resolve it into a pass or fail.",
          "response_span": "flagged as an open question, not a blocker, recommend a short follow-up conversation before final sign-off, not a rejection reason"
        },
        {
          "id": "exclude",
          "type": "pair",
          "brief_line": "Never include personal, family, health, or caregiving information about a candidate in the memo, even if it appears in interview notes. Apply this automatically, without exception.",
          "response_span": "excludes any reference to personal, family, health, or caregiving details raised during interviews, per standing policy on hiring documentation"
        }
      ]
    }
  ]
}