ResumeLens/data/example_google.json
2026-01-27 23:11:23 -07:00

80 lines
11 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

{
"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 users 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 users grading prompt\n- Parse the users 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 0100 and 010 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": "Google Public Sector brings the magic of Google to the mission of government and education with solutions purpose-built for enterprises. We focus on helping United States public sector institutions accelerate their digital transformations, and we continue to make significant investments and grow our team to meet the complex needs of local, state and federal government and educational institutions. The US base salary range for this full-time position is $92,000-$122,000. Our salary ranges are determined by role, level, and location. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Your recruiter can share more about the specific salary range for your preferred location during the hiring process.\n\nPlease note that the compensation details listed in US role postings reflect the base salary only, and do not include bonus, equity, or benefits. Learn more about benefits at Google.\n\nResponsibilities\n\nCreate and support a productive and innovative team including working with peers, managers, and teams.\nDevelop scripts to automate routine tasks.\nAnalyze information and evaluate results to choose the best solution to effectively solve problems.\nApply knowledge gained in computer science courses to real world problems.\n\nMinimum qualifications:\n\nPursuing a Bachelor's degree or post secondary or training experience with a focus on subjects in software development or other technical related fields.\n\nExperience in software development and coding in two or more general purpose programming languages (e.g., C, C++, Java, JavaScript, Python, etc.).\n\nExperience with data structures or algorithms gathered from inside or outside of school or work.\n\nPreferred qualifications:\n\nCurrently attending a degree program in the US and available to work full time for 12 weeks outside of university term time.\n\nPenultimate academic year or returning to a degree program after completion of the internship.\n\nExperience programming in three or more of the following languages: C, C++, C#, Java, JavaScript, Kotlin, Go, Python, TypeScript, or similar.\n\nExperience with web application development, Unix/Linux environments, mobile application development, distributed and parallel systems, machine learning, information retrieval, natural language processing, networking, developing large software systems, or security software development.",
"output": {
"overall_score": 82,
"summary": "The candidate demonstrates strong alignment with the minimum qualifications through active pursuit of a software engineering degree, broad programming language experience, and applied project work. The resume shows hands-on experience with backend, web, cloud, and distributed systems that map well to the roles responsibilities. Some preferred qualifications, such as explicit internship availability details, are not fully documented.",
"criteria_scores": [
{
"criterion": "Education in software development or related field",
"score": 9,
"evidence": "Bachelor of Science in Software Engineering with a Cybersecurity minor; relevant coursework in data structures, algorithms, and software construction.",
"comments": "Education is directly aligned with the role and demonstrates strong academic performance; degree is still in progress."
},
{
"criterion": "Programming experience in multiple general-purpose languages",
"score": 9,
"evidence": "Lists Go, Python, C#, JavaScript, Java, C/C++, and others; professional experience using C# and .NET.",
"comments": "Exceeds the minimum requirement and meets preferred qualification for three or more languages."
},
{
"criterion": "Data structures and algorithms experience",
"score": 8,
"evidence": "Completed coursework in Data Structures and Analysis of Algorithms; applied query optimization reducing database operations by 80%.",
"comments": "Evidence supports both academic and practical exposure, though depth of algorithmic complexity is not detailed."
},
{
"criterion": "Ability to automate tasks and build scripts",
"score": 7,
"evidence": "Engineered CI/CD pipelines and developed serverless functions to automate data extraction and processing.",
"comments": "Automation experience is present, primarily in DevOps and cloud contexts; explicit scripting examples are limited."
},
{
"criterion": "Problem-solving and analytical skills",
"score": 8,
"evidence": "Resolved N+1 query issues, designed migration using the Strangler pattern, and optimized system throughput.",
"comments": "Demonstrates structured problem analysis and solution selection in real systems."
},
{
"criterion": "Teamwork and collaboration",
"score": 8,
"evidence": "Led a team of students in a sponsored research project; collaborated on full-stack development in a professional role.",
"comments": "Leadership and collaboration are indicated, though scale of teams and cross-functional exposure are not fully described."
},
{
"criterion": "Experience with web, distributed systems, or related domains",
"score": 9,
"evidence": "Full-stack web development, distributed IoT system using MQTT, AWS IoT pipelines, and cloud deployments.",
"comments": "Strong breadth across several preferred technical domains."
},
{
"criterion": "Preferred internship availability and academic timing",
"score": 5,
"evidence": "Expected graduation May 2028 suggests penultimate year, but no explicit statement of 12-week full-time availability.",
"comments": "Partial alignment inferred from dates; explicit availability details are missing."
}
],
"strengths": [
"Broad programming language proficiency across backend and systems languages",
"Strong academic performance with relevant coursework",
"Hands-on experience with distributed systems and cloud platforms",
"Demonstrated problem-solving through measurable system improvements",
"Exposure to DevOps practices and CI/CD automation"
],
"weaknesses": [
"Internship availability and work authorization timing not explicitly stated",
"Limited detail on scale and complexity of algorithms beyond coursework",
"Scripting experience not described in depth outside DevOps contexts"
],
"missing_information": [
"Explicit confirmation of 12-week full-time internship availability",
"Details on size and scope of teams worked with in professional roles",
"Examples of standalone scripting languages or tools used for automation"
],
"recommendation": {
"label": "Strong fit",
"rationale": "The candidate meets all minimum qualifications and most preferred qualifications through relevant education, multi-language programming experience, and applied project work. Minor gaps relate mainly to availability details rather than technical capability."
}
}
}