- Company Name
- Stem IT
- Job Title
- Senior Software Engineer
- Job Description
-
<think>
Okay, let me tackle this. The user wants a job description normalized into a concise mini-profile for job matching. First, I need to extract the key elements.
Job Title is clear: Senior Software Engineer. The Role Summary should summarize the main purpose. The startup is venture-backed, focusing on a data matching platform for clients. The role involves back-end work, system design, building APIs, and AI/ML. Need to exclude company details, location, etc., so just mention the core responsibilities.
Expectations: The required skills are 5+ years of experience, specific programming languages. Education is a bachelor's in CS. Maybe list exact languages as per the job desc. Also mention the tech stack here? Wait, the user said to exclude tech stack, but the required skills include specific tech. Need to differentiate between the two.
Wait, the user's instruction says to include "Tech Stack" but in the example output, they didn't. Wait, looking back, the user says to exclude tech stack. The example output includes "Required Skills" and "Key Responsibilities". The tech stack in the job description is under the company's tech stack, but the user says to exclude it. Wait, the user's instruction says "Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications."
So the tech stack here is part of the company's information, so it should be excluded. But the tech stack in the Required Skills section is part of the job's required skills. So for the Required Skills, I need to mention Node.js, Go, Scala, etc.
Key Responsibilities: System design, shipping products from scratch, building RESTful APIs, AI/ML integration.
Required Education: Bachelor's in CS or related. Certifications? None mentioned.
Need to make sure everything is concise, ATS-friendly. Avoid any fluff. Ensure the summary is under 500 words. Also, translate if needed, but the original is in English. Exclude location, benefits, etc. So, no Alexandria, Virginia, no equity, healthcare, etc.
Wait, the original job description mentions "back-end leaning", so should include that in Role Summary. Also, "crafting robust APIs" and "developing AI/ML solutions".
Check Desired Skills, but the user says to focus on Required Skills. The Desired Skills include Master's, experience with data tools, etc. But the user's instruction is to focus on Required Skills and Required Education. The example output includes Required Skills and Required Education. The Desired Skills are optional, so maybe not include them unless specified. The user says to exclude fluff, so maybe only the required ones. The job description's Required Skills are bullet points. Need to rephrase those into concise phrases. For example, "5+ years of professional software engineering" becomes "5+ years of professional software engineering experience" or just "5+ years experience in software engineering."
Need to structure the sections properly. Let me outline each part step by step.
Role Summary: Senior Software Engineer role in a venture-backed startup, back-end focused, involved in system design, feature development, API creation, and AI/ML solutions.
Expectations: Possibly the expectations from the company, like years of experience. Wait, the original didn't have a separate expectations section. The user might be referring to the required experience here. Maybe the "Expectations" section is for the required qualifications. Hmm, maybe the user meant to list the required skills under Required Skills and Responsibilities under Key Responsibilities. So perhaps "Expectations" is redundant here. But the user's example output includes "Expectations" as part of the output. So in the example output provided by the user, they have:
Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications.
So "Expectations" is a separate section. But what goes there? Perhaps the expectations the company has from the candidate, such as "5+ years of experience," but in the example, the Required Skills already include that. Let me check the example provided by the user.
Looking at the example given in the user's message: the output for the sample job would have:
Role Summary: Senior Software Engineer role in a venture-backed startup focusing on data matching platform for commercial and federal clients. Back-end focused, system design, feature design, robust API development, and AI/ML solutions support. Ground floor opportunity in a high-growth organization.
Expectations: 5+ years professional software engineering experience. Proficiency in multiple programming languages including Node.js, Go, Scala, Python, or TypeScript. Experience in system architecture, product shipping, and RESTful API development. Bachelor’s degree in computer science or related field.
Key Responsibilities: Design and implement system architecture and features. Develop and maintain robust RESTful APIs. Collaborate on AI/ML solutions. Contribute to back-end development and product lifecycle.
Required Skills: Node.js, Go, Scala, Python, TypeScript. System architecture and feature design. Product shipping. RESTful API building.
Required Education & Certifications: Bachelor’s in computer science or related field.
So the "Expectations" section in the example includes some of the required skills and education. But the user's instruction says to output Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. So perhaps the example uses "Expectations" to include the experience and some skills, then Required Skills as a separate list. But in reality, the Required Skills should be a list, and Expectations is redundant. Maybe the user wants the required experience and education in the Expectations and Required Skills in a bullet list.
But the user's example shows that the "Expectations" section includes the required experience and some skills. Wait, in the example, the user's sample output includes in "Expectations" the required years of experience, the programming languages, and the education. But in the "Required Skills" section, it's a list of the same. Hmm. Maybe there's a mistake here. Alternatively, maybe "Expectations" is meant to hold the experience and education, while "Required Skills" are the technical skills.
In the given user example, the Expectations section includes 5+ years experience, proficiency in languages, etc. Then Required Skills is a list of the same. That seems redundant. Maybe the user wants the Expectations to be the non-technical requirements (like experience years, education) and the Required Skills to be the technical ones. But in the example, they mixed them. Perhaps the user wants a concise structure and perhaps the example is illustrative but not perfect. I need to adhere to the user's instruction.
The user's instruction says: Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. So split these into their respective sections.
So in the example, the user's own example shows that "Expectations" includes experience and programming languages. So perhaps the user wants the "Expectations" to include the required experience (like years of experience and education) and the Required Skills to be separate tech skills. But the example includes both in the Expectations. It's a bit unclear, but I'll follow the example. Let's proceed.
So for the current job description, the Expectations would include the required years of experience (5+), proficiency in specific languages (Node.js, Go, Scala, Python, Typescript), experience with system architecture and product shipping, etc. Then Required Education is a Bachelor's. Key Responsibilities are system design, API development, AI/ML support. Required Skills are the same as the required programming languages and other technical skills.
Need to make sure the output is ATS-friendly, using keywords from the job description. Also, globally neutral, avoiding location specifics. Exclude benefits and fluff. Keep everything concise, under 500 words.
Let me structure it step by step.
Role Summary: Senior Software Engineer role in a venture-backed data matching platform startup. Back-end focused, involved in system design, full lifecycle development of features, API development, AI/ML integration. Opportunity to build from scratch.
Expectations: 5+ years professional software engineering. Proficiency in Node.js, Go, Scala, Python, or TypeScript. Experience in system architecture, feature design, product shipping. RESTful API development. Bachelor’s degree in CS or related.
Key Responsibilities: Design and implement system architecture for scalable solutions. Own features from design to deployment. Develop and maintain RESTful APIs. Collaborate on AI/ML initiatives. Contribute to backend system development.
Required Skills: Node.js, Go, Scala, Python, TypeScript. System architecture. RESTful API development. Product shipping experience.
Required Education & Certifications: Bachelor’s degree in computer science or related field.
Wait, the required skills section should list the skills mentioned in the job description. The job description lists:
Required Skills & Experience
- 5+ years professional software engineering
- Programming experience with: Node.js, Go, Scala, Python or TypeScript
- Experience with system architecture and feature design
- Background shipping products from scratch
- Experience building out custom Restful APIs
- Bachelor’s in computer science or related field
So, the Education is in the Required section. Certifications aren't mentioned, so no need to include.
So in the Required Skills section, the programming languages (Node.js, Go, Scala, Python, TypeScript), system architecture, feature design, product shipping, RESTful API development. For Required Skills, perhaps list those in bullet points or as a list separated by commas.
But per the user's example output, they included Required Skills as a list, e.g., "Node.js, Go, Scala, Python, TypeScript. System architecture and feature design. Product shipping. RESTful API building."
So following that, perhaps structure each Required Skill as a separate line.
Also, the user's example uses bullet points with periods, so maybe follow that style