Pacemaker Quest Admin · Team Brief

A shared operating system for delivering two first-interview opportunities

Quest Admin is not a final hiring-results tracker. It helps the Pacemaker and Quest teams see whether each candidate in scope has completed two Pacemaker first interviews tied to two different confirmed job opportunities.

Goal: 2 completed first interviews External sources = employer leads Resumes stored securely Dashboard-first operations
Definition

1. The one-sentence definition

Quest Admin is a candidate-first operations hub that helps the team move each candidate from 0 of 2, to 1 of 2, to 2 of 2 completed first-interview opportunities. It brings candidate progress, employer lead follow-up, and interview completion into one shared operating view.

1

Candidate-first progress

The main question is not “how many job posts do we have?” It is “which candidates still need interview opportunities, and what is blocking them?”

0 of 2 · 1 of 2 · 2 of 2
2

Employer lead development

External job sources help the team discover businesses that may be hiring. A team member still confirms the opportunity before candidates are contacted.

Lead source, not final proof
3

Completed interview opportunity

Email outreach, acceptance, and scheduling are important steps, but the goal only moves forward when the first interview actually happens.

Completed first interview
Operations

2. The full operating flow

The system follows the day-to-day work: add candidates and resumes, find possible employers, confirm who is actually hiring, match candidates to confirmed opportunities, send outreach, schedule interviews, and mark the interview as completed.

1

Add candidates

Upload a spreadsheet and resume folder, use a secure upload link, or add a candidate manually.

2

Find employer leads

Use external job sources to identify businesses, roles, and locations that may be worth following up on.

3

Contact employers

A Pacemaker team member confirms whether the business is currently hiring.

4

Confirm opportunity

Only verified hiring opportunities become ready to share with candidates.

5

Reach out to candidates

Select suitable candidates and send or record the outreach message.

6

Run first interview

When the candidate accepts, schedule and complete the Pacemaker first interview.

7

Reach 2 of 2

The candidate is fully served after two completed first interviews for two different confirmed opportunities.

Lead Policy

3. External listings are lead sources, not verified opportunities

A listing from an external source is only a signal that a business might be hiring. It should not be treated as a ready-to-send opportunity until the team confirms the business, role, and current hiring status.

What we avoid

Forwarding raw posts
We do not send scraped or copied job posts directly to candidates.
Assuming it is active
A listing is not treated as current until the team verifies it.
Unverified matching
Candidates are not matched to an opportunity before employer confirmation.

What we do

Build employer leads
Use external job sources to find businesses worth contacting.
Confirm hiring status
A team member contacts the employer and records the result.
Create shareable opportunities
Only confirmed opportunities become available for candidate outreach.
Admin View

4. Dashboard concept

The dashboard is not just a reporting page. It is the team’s daily action board: who still needs interview opportunities, which accepted candidates need scheduling, which interviews need an outcome update, and which employers need follow-up.

Quest Interview Opportunity Dashboard
Upload Candidates Add Opportunity Create Outreach
120
Candidates in scope
163 / 240
First interviews completed
61
Candidates fully served
59
Still need support

Candidate Progress

0 of 2
34
1 of 2
25
2 of 2
61
Out
7

Priority Actions

ActionCountStatus
Candidates need two opportunities34High
Accepted candidates need scheduling18Queue
Interview outcomes need update5Today
Employers need follow-up42Lead

Confirmed Opportunity Pipeline

OpportunityOutreachAcceptedDone
Obong · Server1253
Sushi Yeon · Kitchen721
Korean Village · Server1032

Employer Lead Pipeline

Leads
320
Contact
42
Hiring
15
Opportunities
9
Data Model

5. What the system keeps track of

Instead of showing database terms, this view describes the real-world information the team needs to manage: candidates, employers, confirmed opportunities, outreach, first interviews, resumes, and import reviews.

Candidates
  • Name and contact details
  • Resume status
  • Preferred role
  • Notes and availability
  • 0 of 2 · 1 of 2 · 2 of 2
Employers
  • Company name and area
  • Contact status
  • Hiring interest
  • Follow-up notes
Confirmed Opportunities
  • Role and workplace
  • How it was confirmed
  • Who confirmed it
  • Active / paused / filled
First Interviews
  • Date and time
  • Candidate and opportunity
  • Completed / no-show / cancelled
  • Counts toward the 2 of 2 goal
External Leads
  • Source listing
  • Company name
  • Role and location clue
  • Follow-up needed
Candidate Outreach
  • Email draft or sent message
  • Accepted / declined / no response
  • Phone, email, or chat notes
  • Next follow-up owner
Resumes
  • Uploaded file
  • File type and date
  • Secure access only
  • Download history
Import Reviews
  • Spreadsheet and resume folder
  • Rows needing review
  • Possible duplicates
  • Approved candidate records
Rollout Phases

6. Outreach and interview phases

The first version can work even before full email automation. The team can start with email previews and manual status updates, then add candidate response links and automated sending later.

Phase 1 · Manual outreach

Email preview
The system prepares a candidate-specific message that the team can review.
Manual send
A team member sends the message through the team’s existing email workflow.
Response notes
Phone, email, or chat responses can be recorded by the team.

Phase 2 · Guided candidate response

Automated send
The system can send approved messages directly later.
Response links
Candidates can accept or decline from a secure link.
Scheduling queue
Accepted candidates move into a queue for first-interview scheduling.
Operating Setup

7. How the system should operate safely

Because the tool handles candidate contact information and resumes, it should be separate from the public marketing website, access-controlled for the team, and designed so resume files are stored privately.

Separate admin siteRun Quest operations away from the public marketing website.
Team-only accessOnly approved Pacemaker or Quest users can sign in.
Role-based permissionsOwners, managers, and viewers get different levels of access.
Private resume storageResume files are not public links and are only available to authorized users.
Bulk upload supportImport candidate lists and resume folders with a review step.
Employer lead collectionUse external job sources as starting points for employer follow-up.
Email preview firstStart with reviewed messages before full automation.
Daily action dashboardShow the next operational actions, not just summary numbers.
Activity historyTrack important edits, downloads, and status changes.
Export-ready recordsLet the team pull clean CSV reports when needed.
Open Decisions

8. Decisions to align on before building

These are operating rules the team should agree on early. They affect how the dashboard prioritizes work and how consistently the team records candidate progress.

Should we start with email preview and manual sending?

This lets the team begin using the system before full automated email is ready.

Who can mark a candidate out of scope?

Duplicates, no-consent cases, removal requests, and unsupported cases need a clear approval owner.

What counts as a confirmed opportunity?

The team should agree whether phone, email, in-person confirmation, or another method is enough.

When should unanswered outreach become stale?

A clear follow-up window keeps the action queue clean and prevents old messages from lingering.