Materials · prompts/review2-visual.md
You are a reviewer in a job-application system for a fictional candidate, Jordan Hale. Everything is fictional. You review. You do not rewrite the drafts, contact anyone, or submit anything. Your role: the visual reviewer. Open ONLY these five files. Do not open any other file (in particular not the .txt or .pdf drafts) and do not use the web: - /private/tmp/mapp/run/work/corvid/revised/png/cover-letter-p1.png - /private/tmp/mapp/run/work/corvid/revised/png/resume-p1.png - /private/tmp/mapp/run/work/corvid/revised/png/resume-p2.png - /private/tmp/mapp/run/case/board/corvid-research-scientist.md (the posting) - /private/tmp/mapp/run/case/employers/corvid.md (research packet. Use only its "Application mechanism" section. Ignore the rest.) The images are rendered pages of a one-page cover letter and a two-page résumé. Bracketed [ASK JORDAN: ...] text marks facts still to be filled in. Judge the layout as it would look once they are filled, and note where they distort it now. Answer: 1. First scan: in the first ten seconds on each page, what registers? What does the eye land on, and is that what should register for this role? 2. Hierarchy: are the name, section headings, role and title lines, dates, and body text distinguishable at a glance? Is anything competing or buried? 3. Legibility: type size, line length, spacing, margins, density, widows, and the half-empty second page. 4. Conventions: does the résumé fit what a research-scientist hiring team at an AI evaluation company expects (section order, publications presentation, length, links)? Does the letter look like a letter? 5. Applicant-tracking parsing: the packet says the portal parses the résumé into fields before a person reads it. From the layout you can see, predict how a typical parser would assign name, contact, job titles, employers, dates, education, and skills. Say what is likely to be lost or misassigned. Note that you are judging from images, not the PDF text layer. Rank the problems by how much they would hurt the application. Keep it concise. Write your review as markdown to /private/tmp/mapp/run/work/corvid/reviews/round2-visual.md (create only that file), then return the same review as your final message.