JobHire.AI

• Proactively engage users via **chat** and **calls** during onboarding and early usage; • Reach out to users showing low activity or early churn signals and help them get back on track; • Act as a **human recovery layer**: understand user frustration, diagnose issues, and rebuild trust through real conversation; • Help users understand what can be improved to get better results, using clear and empathetic communication; • Recommend profile, CV, or job search improvements, including relevant paid add-ons (e.g. resume review) when they add real value; • Share user feedback and recurring patterns with Product to improve the overall customer experience.

• Main deliverable: v1 of the continuous performance management system, live across the full team of 38, with a monthly grade refresh and individual dashboards. • Finalize the three axes (results / skills and AI leverage / teamwork), their weights, scales, and the thresholds for moving between A, B, and C. Build on our current ABC framework, don't start from scratch. • Map out where the system pulls data for each axis. What gets collected automatically (Notion, Slack, GitHub, analytics, OKR tracking), what comes from managers, what comes from peer reviews. Keep manual input to a minimum. • Design the monthly loop: what runs automatically, what needs a manager's confirmation, and how each person sees their grade and track. • Dashboards. For the individual (my grade, my track, what to work on). For the manager (my team, who we're growing, who we're parting with). For C-level (TDI, A-player density by competency, risks). • Templates for individual plans. B to A with measurable criteria and an ETA. C to A with performance based and time based boundaries. No fuzzy language. • Run a pilot on two competencies (for example, Engineering and Product), collect feedback, refine, and roll out to the full team.

• Design and own the outcome of the continuous performance management system. • Finalize the three axes (results / skills and AI leverage / teamwork), their weights, scales, and thresholds for moving between A, B, and C. • Map out where the system pulls data for each axis (e.g., Notion, Slack, GitHub). • Design the monthly loop including what runs automatically and how each person sees their grade and track. • Create individual dashboards for tracking performance and grade while providing templates for individual plans. • Conduct a pilot on two competencies, collect feedback, refine, and roll out to the full team.

• Your job is to design the system and own the outcome, not to ship the code. • Main deliverable: v1 of the continuous performance management system, live across the full team of 38, with a monthly grade refresh and individual dashboards. • Finalize the three axes (results / skills and AI leverage / teamwork), their weights, scales, and the thresholds for moving between A, B, and C. Build on our current ABC framework, don't start from scratch. • Map out where the system pulls data for each axis. What gets collected automatically (Notion, Slack, GitHub, analytics, OKR tracking), what comes from managers, what comes from peer reviews. Keep manual input to a minimum. • Design the monthly loop: what runs automatically, what needs a manager's confirmation, and how each person sees their grade and track. • For the individual: dashboards that show my grade, my track, and what to work on. For the manager: dashboards for team growth and potential parting. • Templates for individual plans. B to A with measurable criteria and an ETA. C to A with performance based and time based boundaries. No fuzzy language. • Run a pilot on two competencies (for example, Engineering and Product), collect feedback, refine, and roll out to the full team.

• Your job is to design the system and own the outcome, not to ship the code. • Main deliverable: v1 of the continuous performance management system, live across the full team of 38, with a monthly grade refresh and individual dashboards. • Finalize the three axes (results / skills and AI leverage / teamwork), their weights, scales, and the thresholds for moving between A, B, and C. Build on our current ABC framework, don't start from scratch. • Map out where the system pulls data for each axis. What gets collected automatically (Notion, Slack, GitHub, analytics, OKR tracking), what comes from managers, what comes from peer reviews. Keep manual input to a minimum. • Design the monthly loop: what runs automatically, what needs a manager's confirmation, and how each person sees their grade and track. • For the individual (my grade, my track, what to work on). For the manager (my team, who we're growing, who we're parting with). For C-level (TDI, A-player density by competency, risks). • Templates for individual plans. B to A with measurable criteria and an ETA. C to A with performance based and time based boundaries. No fuzzy language. • Run a pilot on two competencies (for example, Engineering and Product), collect feedback, refine, and roll out to the full team.

• Finalize the three axes (results / skills and AI leverage / teamwork), their weights, scales, and the thresholds for moving between A, B, and C. Build on our current ABC framework, don't start from scratch. • Map out where the system pulls data for each axis. What gets collected automatically (Notion, Slack, GitHub, analytics, OKR tracking), what comes from managers, what comes from peer reviews. Keep manual input to a minimum. • Design the monthly loop: what runs automatically, what needs a manager's confirmation, and how each person sees their grade and track. • For the individual (my grade, my track, what to work on). For the manager (my team, who we're growing, who we're parting with). For C-level (TDI, A-player density by competency, risks). • Templates for individual plans. B to A with measurable criteria and an ETA. C to A with performance based and time based boundaries. No fuzzy language. • Run a pilot on two competencies (for example, Engineering and Product), collect feedback, refine, and roll out to the full team.

• Your job is to design the system and own the outcome, not to ship the code. • Main deliverable: v1 of the continuous performance management system, live across the full team of 38, with a monthly grade refresh and individual dashboards. • Finalize the three axes (results / skills and AI leverage / teamwork), their weights, scales, and the thresholds for moving between A, B, and C. Build on our current ABC framework, don't start from scratch. • Map out where the system pulls data for each axis. What gets collected automatically (Notion, Slack, GitHub, analytics, OKR tracking), what comes from managers, what comes from peer reviews. Keep manual input to a minimum. • Design the monthly loop: what runs automatically, what needs a manager's confirmation, and how each person sees their grade and track. • For the individual (my grade, my track, what to work on). For the manager (my team, who we're growing, who we're parting with). For C-level (TDI, A-player density by competency, risks). • Templates for individual plans. B to A with measurable criteria and an ETA. C to A with performance based and time based boundaries. No fuzzy language. • Run a pilot on two competencies (for example, Engineering and Product), collect feedback, refine, and roll out to the full team.

• Analyze requirements and participate in clarifying tasks before development starts • Identify ambiguities, risks, and formulate questions about the product • Perform manual testing (frontend / backend) of new features and changes • Write and maintain automated tests (TypeScript + Playwright) • Verify edge cases, negative and regression scenarios • Work with logs (Kibana) to search for and analyze errors • Validate data in databases (SQL / NoSQL) • Update test cases when functionality changes • Expand the regression test suite • Create and maintain test documentation • Participate in improving testing processes

• Analyze requirements and participate in clarifying tasks before development starts • Identify ambiguities, risks, and formulate questions about the product • Perform manual testing (frontend / backend) of new features and changes • Write and maintain automated tests (TypeScript + Playwright) • Verify edge cases, negative and regression scenarios • Work with logs (Kibana) to search for and analyze errors • Validate data in databases (SQL / NoSQL) • Update test cases when functionality changes • Expand the regression test suite • Create and maintain test documentation • Participate in improving testing processes

• Analyze requirements and participate in clarifying tasks before development starts • Identify ambiguities, risks, and formulate questions about the product • Perform manual testing (frontend / backend) of new features and changes • Write and maintain automated tests (TypeScript + Playwright) • Verify edge cases, negative and regression scenarios • Work with logs (Kibana) to search for and analyze errors • Validate data in databases (SQL / NoSQL) • Update test cases when functionality changes • Expand the regression test suite • Create and maintain test documentation • Participate in improving testing processes