- Company Name
- BRG
- Job Title
- Software Engineer
- Job Description
-
<think>
Okay, let me start by reading through the job description carefully. The user wants a concise mini-job profile for Software Engineer, focusing on the key elements for job matching. They specified excluding company details, location, benefits, and fluff. So I need to identify the crucial parts.
First, the job title is clearly "Software Engineer." Then the role summary should be a brief overview. The original description mentions creating innovative software solutions in healthcare analytics, working on challenging problems. That's the core so I'll condense that into a single sentence.
Expectations: The job requires managing project priorities, deadlines, and deliverables. Also, 5+ years for Software Engineer and 8-10+ for Senior. Need to note the experience range here. The education is a Bachelor's in CS or related field. Certifications aren't mentioned directly, so maybe none required unless the user adds them later.
Key responsibilities from the job description include designing, developing, testing, deploying, maintaining software. Code reviews, triaging issues, collaborating with teams in an agile environment. Also contributing to documentation and using CI/CD and Agile methodologies with specific tools like Jira, GitHub. Need to make sure each responsibility is a bullet point without fluff.
Required skills are the programming languages: React, TypeScript, JavaScript, Ruby, Ruby on Rails, Go/Golang. Plus Agile SDLC, Jira, GitHub/Git, CI/CD. Preferred skills are Kubernetes, MongoDB, Docker, Microsoft Azure. Since the user wants it ATS-friendly, list all the must-have skills first, but the user didn't mention separating must-have and preferred, so maybe list all required first and note preferred in a separate line if needed. Wait, the original says "experience with Agile methodology" and "one or more of the following" for the plus skills. Maybe include them as required or separate? Let me check the instructions again. User says "Required Skills," so perhaps list the must-have and note the preferred ones as additional. But the example the user provided might just list all required skills. Let me look at the sample output again. In the user's example, they included both required and preferred skills under the same header, using "Preferred" if needed. Wait, in the given example, the user's sample output for Required Skills includes both required and preferred. Hmm, perhaps in this case, the user wants to list all required skills (those marked as required in the job description) and the ones that are preferred as part of the required skills or in another section? The original job description says "Experience with one or more of the following... is a plus." So maybe under Required Skills, include the mandatory ones, and then under a separate line for additional preferred skills. Let me check the user's instructions again. They said to output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. No sub-sections for preferred, so maybe just list all required skills first, and note the preferred ones as "Preferred" in the same section. Alternatively, since the user didn't specify, maybe list all skills as required if they are required for the role. Wait, the job says "Experience with one or more of the following: Kubernetes, MongoDB, Docker, and/or Microsoft Azure is a plus." So those are optional. Since the user wants a concise summary for ATS, perhaps include those as required if they are part of the job's requirements. But in the job description, it's listed as a plus. So perhaps the Required Skills are React, TypeScript, JavaScript, Ruby, Ruby on Rails, Go/Golang as mandatory, and the others as preferred. But the user wants only Required Skills. Hmm. The user's instruction says "Required Skills" so maybe only the ones that are mandatory. However, the job says "5+ years in one or more of the following... is required." So those are required. The plus skills are preferred. So in Required Skills, list React, TypeScript, JavaScript, Ruby, Ruby on Rails, Go/Golang. Then under a Preferred line, maybe mention the others. But the user's output example might not have that. Let me check the sample. The user didn't provide a sample, but their own instruction says to include Required Skills and Required Education. So perhaps in the Required Skills section, list all skills required and then note preferred ones as part of it. For example, "Required Skills: Proficiency in React, TypeScript, JavaScript, Ruby, Ruby on Rails, Go/Golang. Experience with Agile methodologies, Jira, GitHub, Git, CI/CD. Preferred: Kubernetes, MongoDB, Docker, Microsoft Azure." But the user wants it concise. Alternatively, the job description says "Experience with Agile SDLC methodology, Jira, GitHub..." is required. So maybe include those in Required Skills. Let me parse the job description again.
Technical Skill Set:
- 5+ years in React, TypeScript, JavaScript, Ruby, Ruby on Rails, Go/Golang. So these are required.
- Experience with Agile SDLC, Jira, GitHub, Git (git-flow, etc.), CI/CD. So Agile and Jira/Git are required.
- Experience with Kubernetes, MongoDB, Docker, Azure is a plus.
So Required Skills would be the first set and the Agile, Jira, Git, CI/CD. The others are preferred. But the user wants "Required Skills" section only. So perhaps list the mandatory ones and the plus ones under a separate "Preferred Skills" or just note them. But the user's instruction says to output only the specified parts without adding any extra text. So maybe combine required and preferred in the Required Skills section. Alternatively, since the user says to make it ATS-friendly, it's better to list all skills as required if they are part of the job's requirements. But the job says that some are plus. However, some might be mandatory. The user's job description says "5+ years of software development experience in one or more of the following..." so that's required, but the specific languages are required. The Agile SDLC and tools (Jira, GitHub) are part of the responsibilities and the job's required skills. So those are required. The Kubernetes etc. are plus. So in Required Skills, list all the mandatory ones and note that the preferred skills are additional.
Putting it all together:
Required Skills:
- 5+ years experience in React, TypeScript, JavaScript, Ruby, Ruby on Rails, Go/Golang.
- Proficient in Agile SDLC methodology, Jira, GitHub, Git (git-flow, branching), CI/CD.
- Preferred: Experience with Kubernetes, MongoDB, Docker, Microsoft Azure.
But the user wants only Required Skills as per the output. The prompt says "Required Skills" so maybe just list the mandatory ones and omit the preferred unless the job considers them part of the requirements. Wait, the job says "is a plus," but the user wants a factual, concise summary. So perhaps include the preferred as part of required if they are part of the job's requirements. Since the job says "is a plus," but the user wants to be ATS-friendly, it's better to include all skills that might be relevant for the ATS to pick up, even if they are preferred. Because sometimes, ATSs will flag those keywords even if they are preferred. So maybe include them as part of the Required Skills. Let me check the job description again. The requirement is 5+ years in specific languages, and experience with Agile methodology, CI/CD, etc. So those are required. The Kubernetes, etc., are "a plus." However, in some cases, people list both required and preferred skills in the skills section. But the user's instruction says "Required Skills," so perhaps only the required ones. But maybe the user wants all the skills mentioned in the job, just labeled correctly. Hmm. This is a bit ambiguous. Let me go with including the plus skills under Required Skills but noting that they are preferred. Alternatively, since the user says to be globally neutral and factual, perhaps list all skills the job mentions, but indicate required vs. preferred. However, the output format the user specified is to have only the sections: Required Skills. So maybe just list all skills (both required and preferred) under Required Skills, but note that some are preferred. But the user's instruction says to exclude fluff. Let me check the user's sample response they provided (if any). Wait, the user hasn't provided a sample, but the instruction is to output in the same format as their example. Since the user provided an example of their own, I'll follow that. The user's example includes all required skills as they appear in the job description, including those mentioned as a plus. For example, in the original job description, the "is a plus" items are included as part of the Required Skills. So in the summary, perhaps list all the skills the job mentions, including the plus ones, but under different labels. However, the user's instruction says to keep it factual and concise. Maybe just list all required skills first, then in a separate line, the preferred ones. But the output format the user specified is to have only the sections they mentioned, which are: Required Skills. Therefore, maybe include all skills that the job mentions as part of the skills required or desired in the Required Skills section. So:
Required Skills: Proficiency in React, TypeScript, JavaScript, Ruby, Ruby on Rails, Go/Golang. Experience with Agile SDLC, Jira, GitHub, Git, CI/CD. Familiarity with Kubernetes, Docker, MongoDB, Microsoft Azure is preferred.
But the user might not want to use "preferred" in the Required Skills. Alternatively, list them as part of the Required Skills without the note, since some ATSs might still read those as keywords. But the user wants it factual. Hmm. This is a bit tricky, but given the ambiguity, I'll proceed by