🧠 Overview
For enterprise customers, Guide offers the ability to export interview and scheduling data to a dedicated Amazon S3 bucket, enabling you to integrate raw data into your internal business intelligence tools (e.g., Snowflake, Tableau, Looker).
This setup is ideal for companies who want to supplement or replace in-app analytics with custom dashboards or internal reporting pipelines.
🗂️ Folder Structure & File Format
Each S3 bucket is organized by table, with a separate folder for each dataset. Within each folder, data is exported in gzip-compressed CSV files (.csv.gz).
Tables include interview-level, candidate-level, and event-level data
Each folder typically contains ~4 partitions per export job to support scalable parallel reads
Upon request, Guide can consolidate exports into a single CSV file per table.
🔄 Export Frequency & Update Behavior
All S3 exports are currently full dataset exports, not incremental deltas. That means:
Each export contains the complete snapshot of all records
Updated records will replace previous values (entities retain consistent IDs across exports)
This makes it easy to treat each export as a fresh source of truth without needing to reconcile deltas
✅ File Readiness and Handshake Pattern
Guide does not yet support a formal “handshake” or delivery confirmation mechanism to indicate when all files are fully written and ready for consumption.
This support document will be updated when there is a mechanisms for detecting readiness.
🔒 Access and Security
Each S3 bucket is provisioned privately and securely, with customer-specific credentials and permissions. Your team will receive:
Bucket URL
Access keys and credentials
Sample schema reference (if needed)
Guide follows AWS best practices for data security and access control in all enterprise exports.
🧾 Understanding the Exported Data Tables
🔍 Sample Data Format
Find below a sample export to help your team review the structure of the data before integration. These exports are anonymized and include example rows across key tables (e.g., interviews, candidates, interviewer availability).
Please click the file and request access.
Guide’s S3 reporting export includes multiple structured CSV files, each representing a key part of your scheduling and interview coordination data. Here’s a quick overview of the most common files you’ll receive:
📅 Interviews.csv
Contains one row per confirmed interview. This is your central table for interview analytics. Includes:
Candidate ID, job title, interview stage
Interviewer assigned, scheduled time
Calendar metadata and coordination method
📬 Scheduling_requests.csv
Tracks every interview scheduling request made in Guide.
Includes:
Request creation time and requestor
Associated job and stage
Whether the request was handled manually or by automation
Status and time to schedule
📤 Availability_requests.csv
Logs every time Guide requested availability from a candidate.
Includes:
Request timestamps
Whether the candidate responded and how
Availability method (self-schedule vs. coordinator-led)
⚙️ Automated_actions.csv
Captures every scheduling action taken by Aria, Guide’s AI assistant.
Includes:
Action type (e.g. assign panel, propose slot, auto-schedule)
Success/failure flag
Associated request ID and timestamp
🧑💻 Interviewer_pools.csv
Represents the state of your interviewer pools — which interviewers are eligible for which types of interviews.
Includes:
Interviewer IDs and assigned tags
Pool name, stage, and configuration metadata
📈 Interviewer_pool_load.csv
Tracks the load and availability of interviewers in each pool over time.
Includes:
Weekly interview cap
Interviews completed vs. scheduled
Pool saturation and balance metrics
🧾 Interviewer_pool_events.csv
Logs changes made to interviewer pools (e.g. new assignments, removals).
Includes:
Event type (add/remove)
Timestamp and user who made the change
Interviewer and pool involved
These tables are designed to be joined using common keys such as request_id, candidate_id, or interview_id, depending on your analytics needs.
If you need a data dictionary or sample schema reference for integration, contact your Guide CSM or Support team.