Resume screening

A workflow explanation by Jayson Bautista · Original robot guide: Dennice

1 / 24
Read the complete transcript
  1. The question: Let’s follow resume screening through the source diagram.
  2. The challenge: A diagram shows the connections, but not every configuration or runtime result.
  3. Our route: Therefore, we’ll trace the visible steps and finish with the evidence limits.
  4. Read an application: A Google Sheets row-added trigger starts the visible workflow.
  5. Read an application: ReadConfig follows the trigger before a URL-ID extraction code node.
  6. Read an application: A Google Drive download node retrieves the referenced file.
  7. Extract the resume: An Extract PDF node follows the file download.
  8. Extract the resume: A parsing code node prepares the extracted content.
  9. Extract the resume: The prepared content reaches an AI Screening Agent connected to Groq.
  10. Record the assessment: A parser follows the screening agent.
  11. Record the assessment: An Update Sheet node records the resulting output.
  12. Record the assessment: The screenshot does not expose the screening prompt or evaluation rubric.
  13. Route the response: An If node branches after the sheet update.
  14. Route the response: The diagram labels Gmail branches for Hot and Warm/Cold applicants.
  15. Route the response: A Slack Alert HR node is visible alongside the Hot applicant path.
  16. Keep review accountable: This is a screenshot-based implementation case study.
  17. Keep review accountable: Fairness, hiring quality and classification accuracy are not validated by this image.
  18. Keep review accountable: Human review and a documented screening rubric should be verified before use.
  19. Recap: start: A Google Sheets row-added trigger starts the visible workflow.
  20. Recap: process: An Extract PDF node follows the file download.
  21. Recap: route: A parser follows the screening agent.
  22. Recap: output: An If node branches after the sheet update.
  23. Evidence boundary: The supplied screenshots show architecture. They do not verify production outcomes.
  24. Takeaway: Follow the connections, inspect the source, and validate configuration before operational use.

Source: local automation2 screenshot. This film explains visible node connections; prompts, credentials and execution results are not supplied. Robot and props are explanatory illustrations. Back to the case study.