Profile feedback for companion
1. Dataset Name
profile_feedback_for_companion
2. Description
A feedback-record-level dataset that exposes interview feedback forms for compliance and companion-assisted submission analysis. Each row represents one feedback record, including its submission status and a data_json field that carries a companion_session_rds_id when the AI Companion pre-filled the feedback. By filtering on this session reference, metrics can isolate companion-assisted feedback, enabling comparison of submission rates between companion-prefilled and manually authored feedback. This dataset powers feedback compliance and companion feedback impact metrics.
3. Source Tables
- customer_views.profile_feedback (sole source table — no joins)
4. Grain
One row per feedback record (id). Each record represents a single feedback form instance, which may be in any status (submitted, draft, incomplete). The companion_session_rds_id inside data_json is the key differentiator between companion-assisted and manually authored feedback.
5. Dashboards Supported
- AI Companion Dashboard
6. Metrics Supported
| Metric | Supported Breakdowns |
| Interview Feedback Submitted | No drilldowns |
| Feedback Submission Rate | No drilldowns |
| Companion-Filled Feedback Submission Rate | No drilldowns |
| Companion-Filled Feedback Submitted | No drilldowns |
7. Known Exclusions / Filters Applied
- All feedback metrics filter to feedback_type = 'interview_feedback' to exclude non-interview feedback types from the counts.
- Interview Feedback Submitted and Feedback Submission Rate use status = 'SUBMITTED' as the numerator condition and include all statuses in the denominator.
- Companion-scoped metrics (Companion-Filled Feedback Submission Rate and Companion-Filled Feedback Submitted) additionally require get_json_string(data_json, '$.companion_session_rds_id') IS NOT NULL, scoping both numerator and denominator to companion-assisted feedback only.
- NULLIF prevents division by zero in submission rate calculations when no feedback records exist for a given period.
- Companion-Filled Feedback Submitted has no date filter — it is an all-time count. The other three metrics filter by created_at.
8. Schema
| Column Name | Data Type | Notes |
| id | varchar | Primary key. Unique feedback record identifier; sourced from profile_feedback |
| feedback_type | varchar | Type of feedback record (e.g. interview_feedback); sourced from profile_feedback. All metrics filter to feedback_type = 'interview_feedback'. |
| created_at | datetime | Feedback record creation timestamp; sourced from profile_feedback. Primary date field for time-based filtering. |
| position_id | bigint | Position associated with the feedback; sourced from profile_feedback |
| status | varchar | Feedback submission status (e.g. SUBMITTED, DRAFT); sourced from profile_feedback. Key value: 'SUBMITTED' used as the numerator condition in all submission rate metrics. |
| submitted_timestamp | datetime | Timestamp when the feedback was submitted; sourced from profile_feedback |
| data_json | varchar | JSON payload containing additional feedback metadata; sourced from profile_feedback. Key field: companion_session_rds_id extracted via get_json_string(data_json, '$.companion_session_rds_id'). IS NOT NULL indicates the companion pre-filled this feedback record. |