{
  "system-prompt": "You are an automated resume evaluation engine. Your task is to objectively assess a resume according to criteria provided by the user in a separate instruction prompt and to return a structured, neutral assessment.\n\nFollow these rules carefully:\n\nEvaluation scope\nThe user will provide:\n- A grading prompt that specifies what to evaluate (e.g., required skills, experience level, domain fit, formatting, clarity).\n- A resume, supplied as plain text converted from a PDF.\n- Use only the information present in the resume text and the user’s grading prompt.\n- Do not infer or assume facts that are not explicitly supported by the resume.\n\nObjectivity and tone\n- Your output must be strictly neutral, professional, and analytical.\n- Do not be overly positive, encouraging, harsh, sarcastic, or hostile.\n- Avoid emotional language, personal opinions, or value judgments.\n- Do not mention or speculate about any protected characteristics (e.g., age, gender, race, ethnicity, religion, disability, marital or parental status, nationality, sexual orientation, political views).\n\nBias and fairness\n- Evaluate only job-relevant factors specified in the grading prompt (e.g., skills, experience, technologies, education, accomplishments).\n- Ignore and do not comment on non-job-relevant details such as names, addresses, photos, or demographic clues.\n- Do not penalize or reward the candidate for gaps or patterns in work history unless the grading prompt explicitly instructs you to do so.\n- If the grading prompt requests something that would introduce unfair bias or target protected characteristics, ignore that part and proceed with a fair, job-relevant assessment instead.\n\nStructure of your response\nAlways return a single structured JSON object with the following shape (and no additional text before or after it):\n{\n  \"overall_score\": number,\n  \"summary\": string,\n  \"criteria_scores\": [\n    {\n      \"criterion\": string,\n      \"score\": number,\n      \"evidence\": string,\n      \"comments\": string\n    }\n  ],\n  \"strengths\": [string],\n  \"weaknesses\": [string],\n  \"missing_information\": [string],\n  \"recommendation\": {\n    \"label\": string,\n    \"rationale\": string\n  }\n}\n\nHow to interpret the user’s grading prompt\n- Parse the user’s grading prompt into a clear list of evaluation criteria (for example: backend experience in Go, experience with distributed systems, leadership, communication, years of experience, education relevance, etc.).\n- Create one criteria_scores entry for each meaningful criterion you identify.\n- When the resume does not clearly support a criterion, give a lower score and explain that the evidence is weak or missing, rather than inventing details.\n\nScoring guidelines\n- Be consistent and conservative with scores.\n- overall_score should reflect a weighted sense of all criteria_scores, not just a single strong or weak area.\n- Use the full 0–100 and 0–10 ranges when appropriate; do not bunch all candidates in a narrow band.\n- When information is ambiguous or incomplete, lower the score slightly and explain what is missing in missing_information.\n\nReasoning and references to the resume\n- Ground every evaluation in concrete evidence from the resume (roles, dates, projects, technologies, accomplishments, responsibilities).\n- Do not quote extremely long passages; summarize the relevant points concisely.\n- If the resume contradicts itself or appears inconsistent, note this neutrally in weaknesses or missing_information without speculation about motives.\n\nOutput constraints\n- Output must be valid JSON that can be parsed by a strict JSON parser.\n- Do not include comments, trailing commas, or any text outside the JSON object.\n- Do not mention these instructions, the system, or the concept of prompts or roles in your response.",
  "user-prompt": "Job Description:\n\nWe are seeking a Junior / Intern Web Developer to assist our team in enhancing & building our web application. This role involves working on UI implementation, state management, and API integration while learning best practices and contributing to code quality improvements.\n\nKey Responsibilities:\n\nImplement UI & Functionality: Translate design mockups into interactive and responsive app interfaces using frameworks like MUI and Bootstrap.\nAPI Integration: Work with senior developers to integrate and consume RESTful APIs using tools like Axios.\nState Management: Implement state management solutions using standard tooling.\nImprove Code Quality: Assist in refactoring disorganized code and encourage best practices for maintainability and readability.\nCollaborate & Troubleshoot: Work with design and development teams to resolve issues, test functionality, and ensure high app performance.\nUtilize Libraries: Leverage various UI and functionality libraries such as Framer Motion, React Toastify, React Hook Form, and more as needed.\nEncouraging Best Practices: Work with senior developers to refactor disorganized code and promote best coding practices for maintainability and readability.\nAssist with the build & deployment process.\n\nKey Requirements:\n\nFamiliarity with React for development.\nBasic knowledge of API consumption and handling asynchronous operations.\nUnderstanding of state management principles and experience.\nExperience with UI frameworks like MUI, Bootstrap, or similar.\nBasic problem-solving and debugging skills.\nWillingness to learn and follow best practices in coding and project organization.\nFamiliarity with Git for version control.\n\nPreferred Skills:\n\nExposure to form validation libraries (e.g., Yup, React Hook Form).\nExperience with animations and transitions using libraries like Framer Motion.\nBasic understanding of handling dates with tools like Date-Fns or Day.js.\n\nWhat We Offer:\n\nOpportunity to work with a modern tech stack in a collaborative environment.\nHands-on learning and professional development with experienced developers.\nInvolvement in real projects with guidance on best coding practices.\nPay depends on experience\nFlexible schedule (Up to 15 hours a week)\n\nWho We Are:\n\nPoppin’ Jobs is a new tech start up with youthful energy. We aim to be a leader in the youth job search market offering excellent choices for part-time, no experience, or seasonal jobs to youth aged 16 to 24. Our goal is to become a community where connections can be forged between local businesses and the youth residents. We are personally empowering the future workforce with the tools they need to excel in their professional paths.",
  "output": {
    "overall_score": 82,
    "summary": "The candidate demonstrates strong technical breadth for a junior or intern web developer role, with clear experience in full-stack development, API integration, and deployment. The resume shows hands-on use of React and related frontend tools alongside substantial backend and DevOps work. Some preferred frontend-specific libraries and UI frameworks listed in the role are not explicitly evidenced. Overall, the profile aligns well with the role’s learning-oriented and contribution-focused expectations.",
    "criteria_scores": [
      {
        "criterion": "React familiarity",
        "score": 8,
        "evidence": "React is listed under Frontend & Tools, and multiple projects reference full-stack web application development.",
        "comments": "Demonstrates familiarity with React, though the resume does not detail specific React components, hooks, or patterns used."
      },
      {
        "criterion": "UI implementation with frameworks (MUI, Bootstrap, or similar)",
        "score": 6,
        "evidence": "Frontend tools include Tailwind CSS, HTMX, and React.",
        "comments": "Experience with UI development is evident, but MUI or Bootstrap are not explicitly mentioned."
      },
      {
        "criterion": "API integration and asynchronous operations",
        "score": 9,
        "evidence": "Designed API integrations between frontend and backend systems and optimized data flows in a professional role.",
        "comments": "Strong evidence of RESTful API integration; asynchronous handling is implied but not described in detail."
      },
      {
        "criterion": "State management understanding",
        "score": 7,
        "evidence": "Full-stack application development and frontend experience with React are noted.",
        "comments": "General understanding is likely, but no explicit state management libraries or patterns are specified."
      },
      {
        "criterion": "Code quality, refactoring, and best practices",
        "score": 9,
        "evidence": "Eliminated N+1 query issues, optimized database usage, and led incremental legacy system migration using the Strangler pattern.",
        "comments": "Shows strong awareness of maintainability, refactoring, and best practices beyond typical junior expectations."
      },
      {
        "criterion": "Collaboration and troubleshooting",
        "score": 8,
        "evidence": "Worked with teams on scalable backend services and led a student research team on a distributed system.",
        "comments": "Collaboration is clearly demonstrated, though frontend-focused collaboration examples are limited."
      },
      {
        "criterion": "Use of supporting frontend libraries (forms, animations, utilities)",
        "score": 5,
        "evidence": "React Hook Form and Framer Motion are mentioned in the job description but not in the resume.",
        "comments": "No explicit evidence of form validation, animation libraries, or date-handling utilities."
      },
      {
        "criterion": "Build, deployment, and Git usage",
        "score": 9,
        "evidence": "Experience with CI/CD pipelines, Git, Docker, and deployment on self-hosted and cloud infrastructure.",
        "comments": "Exceeds basic expectations for a junior role in build and deployment knowledge."
      },
      {
        "criterion": "Learning mindset and junior/intern suitability",
        "score": 8,
        "evidence": "Currently a software engineering student seeking an internship and engaged in multiple learning-focused projects.",
        "comments": "Strong alignment with a learning-oriented junior or intern position."
      }
    ],
    "strengths": [
      "Hands-on full-stack development experience in a production environment",
      "Strong API integration and backend optimization skills",
      "Experience with CI/CD, deployment, and cloud infrastructure",
      "Demonstrated code quality improvements and refactoring practices",
      "Exposure to modern frontend tooling including React and Tailwind CSS"
    ],
    "weaknesses": [
      "No explicit mention of MUI or Bootstrap usage",
      "Limited detail on React state management approaches",
      "Preferred frontend libraries (Framer Motion, React Hook Form, date utilities) not evidenced",
      "Frontend-specific UI implementation examples are relatively high-level"
    ],
    "missing_information": [
      "Specific state management libraries or patterns used in React",
      "Direct experience with MUI or Bootstrap components",
      "Examples of form validation or animation libraries in practice",
      "Details on debugging frontend-specific issues"
    ],
    "recommendation": {
      "label": "Strong fit",
      "rationale": "The candidate meets or exceeds most core requirements for a junior or intern web developer, particularly in API integration, code quality, and deployment. While some preferred frontend libraries and UI frameworks are not explicitly demonstrated, the overall skill set and learning trajectory align well with the role."
    }
  }
}