- Company Name
- Locality Streaming
- Job Title
- Jr. Software Engineer - AI & Prompt Engineering (Contract to Perm)
- Job Description
-
<think>
Okay, let's see. The user wants me to normalize a job description into a concise mini-job profile for job matching. The key points are to exclude company details, location, benefits, and fluff. The output should only include specific sections: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. It needs to be factual, concise, ATS-friendly, and globally neutral.
First, the job title is provided: Jr. Software Engineer - AI & Prompt Engineering (Contract to Perm). I need to make sure the title is clean. Maybe remove the (Contract to Perm) part since it's in parentheses and not essential for the matching. But sometimes including the contract type helps. Wait, the user says to exclude company details but maybe keep the contract info as part of the title. Let me check the original query again. They said to exclude location, benefits, company details. So perhaps keep the job title as is but maybe rephrase it slightly if needed. The original title is fine.
Next, the Role Summary. The job description mentions it's for an entry-level CS grad, contract to perm, excited about AI-augmented world. So the summary should capture that. Maybe something like "Entry-level software engineer role focused on integrating AI and prompt engineering into software development and automation."
Expectations would be the key qualifications. From the job description, they need someone with core CS fundamentals, prompt engineering, AI-assisted development. So expectations could be a Bachelor's in CS or related field, foundational CS knowledge, and some exposure to AI tools.
Key Responsibilities: Need to extract the main duties. The user listed several bullet points. Let me condense these. Designing prompts for development and automation, testing AI outputs for correctness and security, building and maintaining services that use AI APIs, writing clean code, debugging, code reviews, system design, monitoring AI performance, learning AI safety practices, version control with Git.
Required Skills: Programming languages like Python, JavaScript, Java. Software development fundamentals (debugging, testing, Git). Basic API and HTTP integration experience. Exposure to AI tools, prompt engineering.
Education: Bachelor's in CS or equivalent. Certifications aren't mentioned, so maybe not required here.
Now, checking for ATS-friendly keywords: "prompt engineering", "AI safety", "software development", "version control", etc. Make sure terms are consistent.
Need to avoid fluff and company details, so all the info about the company's culture and equal opportunity is out. Also exclude compensation details and location.
Check for conciseness. Each section should be a few lines. Maybe bullet points for responsibilities and skills. But the user said "exclude fluff" and "keep it factual", so need to use concise language. Also ensure it's in English, globally neutral.
Let me structure each section as per the user's instructions. Make sure each section is correctly labeled and there's no markdown. Use simple lists, maybe separated by commas or semicolons if needed. Avoid jargon but use technical terms where necessary for clarity.
Wait, the user specified "Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications." So each section is a separate line, starting with the section title in bold, followed by the content. But the user said to exclude any introduction or extra text. So perhaps each section is a bullet point.
Wait, but the user's example in the query shows specific sections. Let me check again. They want the output to have those six sections. Maybe each section is a line with the title followed by a colon and the content. Also, no markdown, so plain text with line breaks. Let me make sure to separate each section with line breaks, but since the user said "output only", without any extra text. Also, in the example, the user shows the job title first, then each section.
Wait, the user says "Output only: Job title, Role Summary, Expactations (probably typo for Expectations), Key Responsibilities, Required Skills, Required Education & Certifications." So the sections are as listed. The typo in Expectations is there in the query, but I should follow the user's instruction. So in the output, the correct term is "Expectations" (what the company expects from the candidate).
Now, compiling all together. The job title is Jr. Software Engineer - AI & Prompt Engineering. The Role Summary is a brief overview. Expectations are the prerequisites expected from the candidate. Key Responsibilities are the main duties. Required Skills are the necessary competencies. Education & Certifications are the academic and cert requirements.
Let me draft each section:
Job Title: As given.
Role Summary: Mention entry-level, contract to perm, focus on AI and prompt engineering in software development.
Expectations: Bachelor's in CS, foundational knowledge, prompt engineering experience.
Key Responsibilities: List all the main tasks from the job description, condensed.
Required Skills: List programming languages, API experience, AI tools.
Education & Certifications: Bachelor's in CS or related, no certs mentioned.
Need to ensure it's under 500 words. Probably okay. Also, check for any redundant or fluff information. Yes, the original job description mentions location and benefits, which are excluded.
Check for ATS-friendly terms. For example, "prompt engineering", "AI models", "APIs", "unit and integration testing", "code reviews", "Git", "system design", "AI safety", "hallucination detection", etc.
Double-check that each required section is included and formatted correctly. Use commas, semicolons, or bullet points as needed, but since the user wants it concise, maybe use bullet points with hyphens or something. However, the user said to output only the specified sections without markdown, so perhaps use commas or semicolons.
Wait, the user example shows in the job description using bullet points, but the output should be in a paragraph style but concise. Let me check the original instruction again: "concise summary for job matching. Max 500 words." But the user says to exclude fluff and be factual. So using bullet points is acceptable but in the output, the user said to output only the specified sections. However, the user might not want markdown. So perhaps use line breaks and separate sections with colons.
Wait, the user says "output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So each of these sections is separated, and each is a line. The user probably expects each section title followed by a list or a brief description.
But the initial example the user provided in their query (the one they pasted) shows that the assistant's answer uses bullet points. So maybe the assistant should format each section with line breaks and colons, perhaps with bullet points for items. But since the user says "exclude any introduction, explanation, or extra text," and "output only" the specific sections, we need to be precise.
In the user's message, the example response from the assistant uses bullet points for each item in the sections, but the user hasn't prohibited that. However, the user said "keep it factual, concise, ATS-friendly". So using bullet points in the format is acceptable if it's ATS-friendly.
But to ensure it's plain text without markdown, perhaps separate with commas or use semi-colons. Alternatively, use hyphen bullets. Since the user didn't specify, but provided an example in the query where the assistant used bullet points, maybe that's the way to go.
Wait, the user's example job description has bullet points, but when the assistant is creating the profile, they might need to use similar formatting. However, the user might not want markdown, so perhaps use asterisks or something. Alternatively, since the user says "exclude any introduction, explanation, or extra text," just list the content in each section with commas or semicolons.
But given that the user's example job description uses bullet points, and the user might be expecting a similar structure, perhaps using hyphens for the key responsibilities and required skills makes sense. For example:
Key Responsibilities:
- Design prompts for software development, data analysis...
- Test, evaluate AI outputs...
But ensuring that the entire thing is under 500 words. Let me count the words for the example. The user's example in the query is a bit long, but since the maximum is 500 words, the generated profile should be concise.
Putting it all together:
Job Title: Jr. Software Engineer - AI & Prompt Engineering
Role Summary: Entry-level software engineer role focused on integrating AI and prompt engineering into software development and automation workflows.
Expectations: Bachelor’s degree in Computer Science or related field; foundational knowledge of core CS concepts; exposure to AI tools and prompt engineering.
Key Responsibilities: Design and refine prompts for AI-assisted software development; test and validate AI-generated code for accuracy and reliability; build and maintain AI-integrated services with APIs; write clean, documented code; debug issues across application logic and AI outputs; participate in code reviews; contribute to system design by breaking down tasks; monitor AI-driven features in production; apply AI safety best practices; use version control systems.
Required Skills: Proficiency in Python, JavaScript, or Java; software development fundamentals (debugging, testing); API and HTTP integration experience; basic understanding of AI tools and prompt engineering.
Required Education & Certifications: Bachelor’s degree in Computer Science, Software Engineering, or related field.
Now check the word count. Let me see. The Role Summary is 14 words. Expectations: 15. Key Responsibilities: 50 words. Required Skills: 22. Education: 15. Total around 116 words. Well under 500. Looks good.
Check if all the key points from the job description are covered:
- Prompt design for development, data analysis, automation: