Finance Recruiting Pipeline Tracker
This conversation was generated using Cook'd AI's career assistant and reviewed by Fallon Han from our editorial team for accuracy.
I am a master's student in the US on F-1 OPT, trying to pivot from engineering into structured products sales at a large bank. I keep losing track of which resume version and referral path got me to each stage. Can this tracker show me whether an application is still waiting on HireVue, or if it moved to first round or superday?
Yes, and that is exactly the right use case for a recruiting tracker. For each application, log the role, bank, date submitted, resume version used, and referral source separately. Then add a clear stage field such as submitted, awaiting HireVue, HireVue complete, first round, and superday. That way you can filter by the resume variant that actually progressed, instead of guessing after the fact. For OPT recruiting, I would also add a note on whether the application was through a direct portal, employee referral, alumni intro, or recruiter outreach, because that path often changes response speed.
How detailed should I be with the resume versions? I have one version that is more technical from my engineering background, and another that is more sales-focused for structured products. I want to know which one is getting me past resume review and into HireVue.
Keep it simple but specific. Label them something like Resume A Technical and Resume B Sales Pivot, then store the exact file name or version date. In the notes, record what changed, for example trading project language, market exposure, client-facing bullets, or finance coursework. When a company moves you to HireVue, mark the resume version used on that application so you can compare outcomes across stages. Over time, your tracker should show whether the sales-focused version is helping more with structured products roles, which is the signal you need.
I also get referrals from alumni, classmates, and one recruiter I met at a career fair. Should I track those differently, or just call them all referrals?
Track them separately. An alumni referral is not the same as a classmate referral or a recruiter submission, and the response rates can be very different. Use a source field with options like alumni, classmate, recruiter, employee referral, and direct application. Then add a subnote for who made the introduction and whether they confirmed the application was pushed internally. If you ever notice that alumni referrals get you to first round faster than direct applications, that becomes useful recruiting strategy data, not just a memory aid.
I mostly want to avoid missing HireVue deadlines. Sometimes I apply, hear nothing, and then a few days later the portal changes. How should the tracker help me stay on top of that?
Build a status and deadline system. For each application, record whether HireVue is pending, sent, started, or completed, plus the due date if it was assigned. Add a reminder field for follow-up timing so you know when to check the portal or email. If the status changes from submitted to awaiting HireVue, you can prioritize that company immediately instead of waiting too long. For structured products sales, timing matters because banks often move quickly once the first screen opens.
What would a good row in the tracker look like for one of my applications?
A strong row would include company, group, role, submission date, resume version, referral source, current stage, HireVue status, interview date, and notes. For example, Large Bank A, Structured Products Sales Analyst, submitted on March 8, Resume B Sales Pivot, alumni referral, awaiting HireVue, not yet received, and then later first round on March 18. This makes it easy to see the path from application to interview and which inputs helped. If you keep that level of detail, you will quickly learn which combination of resume and referral is actually working for your OPT recruiting push.