- Company Name
- 5V Tech | Certified B Corp™
- Job Title
- Back End Developer
- 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. They specified excluding company details, location, benefits, and fluff. The output should only include the job title, role summary, expectations, key responsibilities, required skills, and required education & certifications. Also, it needs to be in English, ATS-friendly, globally neutral, and under 500 words.
First, I need to read through the provided job description carefully. The job title here is "Back End Developer," which I should confirm. The original job title says "Backend Engineer – Embedded / Real-Time Systems," so maybe I should use that as the title instead? Wait, the user said to use the given job title, which is "Back End Developer." Hmm, but maybe the user wants the actual title from the job description. Let me check again.
Looking at the input: the user provided the job title as "Back End Developer," but the job description starts with "Backend Engineer – Embedded / Real-Time Systems." So is there a discrepancy here? The user's instruction says to normalize, which might mean using the actual title from the job description. But the user provided the job title as "Back End Developer." Maybe they want the exact title given, but perhaps the correct one is "Backend Engineer – Embedded / Real-Time Systems." This could be a mistake. Since the user provided the job title as "Back End Developer," I should use that unless instructed otherwise. But maybe I should check for consistency.
Next, the role summary needs to be a concise summary for job matching. The job is about backend software for real-time systems, embedded systems, etc. So the role summary should encapsulate designing and developing backend services for embedded products, real-time communication layers, integration with hardware, ensuring quality, and contributing to architecture.
Expectations would probably be the same as key responsibilities. Let me see. The job description lists duties like designing backend services, building real-time communication layers, collaborating with teams, ensuring quality via code reviews and CI/CD, contributing to architecture.
Required skills: the job requires experience as a backend developer with Node.js, TypeScript, NestJS. Real-time systems with WebSockets, event-driven architectures. Understanding of client/server synchronization, Linux environments.
Education and certifications aren't explicitly mentioned in the job description. It says "If you are interested," but no mention of required degrees or certifications. So maybe leave that section blank unless inferred. But the user wants it included. Maybe "Not specified" or omit? Wait, the user says to include Required Education & Certifications, but if the job description doesn't mention it, I should probably state that there are no specific requirements or note that it's not mentioned here. However, since the user wants the output to be factual, perhaps just leave it out if it's not provided. Alternatively, maybe the user expects placeholders. Hmm. In the example input, there is no education mentioned, but in the output, they have "Required Education & Certifications" which might be left blank. Let me check the example response.
In the example response, the user didn't mention education or certifications, so the output includes "Not required for this role." Wait, no, in the example given by the user in the problem prompt, when there's no education or certifications mentioned, they just leave it as "Required Education & Certifications: Not specified." But I need to check the original job description. The original job description says nothing about education or certifications, so perhaps just note that they are not specified. But the user's instruction says to include Required Education & Certifications. So I should include that section even if it's not present. Maybe write "Not specified."
Also, the user wants to exclude company details, location, benefits. The location is Paris, but they want that excluded. The required European Citizenship is part of the job requirements? Wait, the job description says "they require European Citizenship." That's an expectation, not a location. So the expectations would include that, but the user said to exclude location. Wait, no. The user says to exclude location. The location part is "Paris (South of Paris / Île-de-France)" which should be excluded. The European Citizenship is a requirement for the role. However, the user's instruction says to exclude fluff, but maybe that's a requirement. The job requires the candidate to be on-site 3 days/week and require European Citizenship. The user wants to exclude fluff, but the citizenship is a requirement. So that should be included in the expectations or key responsibilities? Wait, maybe in the expectations section. Let me check.
The user wants "Expectations" to be included, which is separate from key responsibilities. So the "require European Citizenship" is an expectation. Also, "need to be on-site 3 days per week." So those are expectations. But the user instructions say to exclude location. The location is in Paris but the user wants to exclude location. However, the on-site days and citizenship are not location, so they should be included in expectations.
So, putting it all together. Let's start constructing the sections.
Job Title: Backend Engineer – Embedded / Real-Time Systems. Wait, but the user provided the job title as "Back End Developer." There's some ambiguity here. The original job title in the description is "Backend Engineer – Embedded / Real-Time Systems," but the user provided the title as "Back End Developer." Should I correct it to the actual title from the job description or use the one the user provided? The user says "Normalize the following job description into a concise mini-job profile... Output only: Job title..." So if the job description has a different title, perhaps the user expects the actual title. But the user provided "Back End Developer" in the job title section. Wait, maybe that's a mistake. Let me look again.
Original input:
Job Title: Back End Developer
Job Description:
Backend Engineer – Embedded / Real-Time Systems
Paris (South of Paris / Île-de-France)
...
So the job title in the user's input is "Back End Developer," but the job description's first line starts with "Backend Engineer – ..." So is the user providing a title that's different from the job description? Probably a mistake. The correct title is "Backend Engineer – Embedded / Real-Time Systems." But since the user says to include the job title, maybe they actually want the one from the job description. However, the user's own input says the title is "Back End Developer." So this is conflicting. The user might have intended the job title as given. Perhaps I should use "Backend Engineer – Embedded / Real-Time Systems" as the job title. But the user provided "Back End Developer as the title. Hmm. Maybe it's a translation or typo issue. Let's see. "Back End Developer" is the same as "Backend Engineer," so perhaps using the given title is fine, but maybe the role is more of an engineer with embedded systems. Since the user wants the profile to be for job matching, using the correct title as per the job description is better. So maybe I should adjust the job title to match what's in the description. But the user's instruction says "Normalize the following job description," so perhaps the correct approach is to use the title as given by the user, even if the job description's actual title is different. This is a bit confusing. But given that the user provided the job title as "Back End Developer," but the job description calls it a "Backend Engineer – Embedded..." perhaps the user made an error. Since the user's instruction says to normalize the job description, which includes using the actual content of the job description, maybe the correct approach is to use "Backend Engineer – Embedded / Real-Time Systems" as the job title, even if the user provided a different one. Otherwise, the job title would be misleading. For example, if the job is for a backend developer working on embedded systems, but the title is "Back End Developer," but the actual role is more specialized. Therefore, using the correct title from the job description is better for job matching.
So I'll proceed with using the title from the job description: "Backend Engineer – Embedded / Real-Time Systems."
But the user might have given the title as "Back End Developer" for some reason. Maybe it's a test case. Hmm. Well, following the instruction to normalize the provided job description, the correct title is the one in the job description. I'll go with "Backend Engineer – Embedded / Real-Time Systems."
Next, the role summary should be a concise summary for job matching. The role involves backend software for embedded products, real-time systems, Linux-based environments, integration with hardware, etc. So the role summary would be something like: Develop backend services for embedded/real-time systems, focusing on high-performance, reliability, and real-time communication. Work on integrating backend logic with complex hardware products.
Expectations: The job requires 3 days on-site per week and European Citizenship. So expectations would mention being on-site and citizenship requirement.
Key Responsibilities: Designing and developing backend services, building real-time communication layers, collaborating with teams (embedded, frontend, system architects), ensuring software quality via code reviews, testing, CI/CD, contributing to architectural decisions.
Required Skills: Strong backend dev experience (Node.js, TypeScript, NestJS), real-time systems (WebSockets, event-driven), understanding client/server sync, Linux familiarity.
Education & Certifications: Not specified in the job description, so probably leave that as "Not specified."
Now, checking the user's example output. Wait, the user didn't provide an example output, but in their instruction, they wrote: "Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications."
So the expected structure is these six sections. Let's make sure to follow that.
Also, keep