- Company Name
- QuoteWerks
- Job Title
- Software Developer
- Job Description
-
<think>
Okay, I need to help the user by turning the given job description into a concise mini-job profile for job matching. Let me start by understanding the requirements. The user wants the output to include the job title, role summary, expectations, key responsibilities, required skills, and required education/certifications, all in English. I have to exclude any fluff, company details, location, benefits, or other unnecessary information. Also, it needs to be ATS-friendly and globally neutral.
First, the job title is already provided as "Software Developer". Next, the role summary should be a brief overview. The original job description mentions building and maintaining web applications for SaaS users, working on full-stack development, and migrating functionality from desktop to web. I'll summarize that to capture the essence without extra details.
Expectations would outline what the company expects from the candidate. The key responsibilities here include full-stack work, API integration, legacy system maintenance, collaboration with stakeholders, and using modern tools. I need to phrase these concisely.
For required skills, the job mentions .NET (C#, VB.NET), JavaScript, full-stack tech like Web APIs, AngularJS, SQL, API design, source control like TFS. Also, Python is a plus. The skills should be listed clearly, maybe bullet points or in a paragraph. The user mentioned excluding any fluff, so I'll focus only on the technical skills and requirements.
Education and certifications aren't explicitly stated in the job description, but it's common to require a bachelor's degree in a related field. Since the original text doesn't specify, I might note that a bachelor's is required unless told otherwise. Certifications aren't mentioned, so maybe leave that blank or state none if needed. Wait, the user says to include education and certifications if present. The job description doesn't mention any education, but perhaps the typical for a software developer role is a bachelor's. I should infer that here.
Wait, the user said "required education & certifications", but the job description doesn't specify any. Should I include a typical one? The example might need a standard like "Bachelor's degree in Computer Science or related field" as that's common. But maybe the user wants only what's in the original job post. The original says next steps but no education or certs. Hmm, this is a bit tricky. The instructions say to exclude fluff but include required education and certifications. If they are not mentioned, perhaps just leave it as blank, but that might not be helpful. Maybe the user expects a standard one. Let me check the original job description again. The job says "Next Steps" but under "Skills You’ll Need", there's no mention of education or certs. So I should probably leave them out unless the job description specifies them. However, including a bachelor's degree is common in tech roles. But the user instructions say to exclude fluff. So maybe better to leave it out since it's not stated. Alternatively, maybe the user expects a standard. Hmm.
Wait, the user wants the output to be factual. Since the original job description does not mention education or certifications, I should not include them unless stated. Therefore, in the required education & certifications, maybe just omit if nothing is stated, but the user wants to include that section. The job description doesn't say anything about education or certifications. Therefore, perhaps in the required education write "Not specified" or just omit. Wait, looking at the sample the user provided, in the output, they included "Not required". Let me check the user's example. Wait, the user provided a sample input and output. Wait, the user didn't provide a sample output, but the user provided an example input and expects the output. Let me check the example given by the user. Let me look at the example that the user is using here. Wait, the user hasn't provided an example. Maybe I should just proceed with the information given.
In this case, the job description doesn't mention required education or certifications. However, for completeness, perhaps the role expects a bachelor's. But since it's not in the original description, including it would be adding information not present. Since the user instruction says to exclude fluff and keep it factual, I should not add it. Therefore, in Required Education & Certifications, leave it blank. However, the user's example in their problem might not show that. Wait, maybe they want a default. For example, maybe in some cases where it's standard, include a bachelor's degree. But without the job post specifying, that's an assumption. Hmm. I might have to mention that if the job description doesn't specify, but in the given job desc, it's not mentioned. Therefore, leave it as is.
Okay, proceeding with that. So the education section might be: Required Education & Certifications: None specified. But the user wants to output that section. Alternatively, if not specified, perhaps leave it blank. But the user instruction says to include Required Education & Certifications, so maybe write "Not specified" or omit. However, the user provided an example in their query where the output includes education (if they had provided it). Since they didn't specify, I'll have to infer based on the instructions. Since the user says "Exclude... fluff", but also wants a factual representation. So if the job doesn't mention education or certifications, maybe just leave that section empty. But looking back at the user's exact output instructions, they specify "Required Education & Certifications", so perhaps include that line even if no info. However, the job description does not mention any education or certifications. Therefore, perhaps write "Not specified" or "None". Let me check the original job description again. The job description under "What You’ll Do" lists responsibilities, and under "Skills You’ll Need" lists technical skills but no education. So the Required Education & Certifications would be: Not specified. But maybe the user expects that line to be included. So, in that case, write "Not specified" in Required Education & Certifications.
Alright, now let's structure the sections according to the user's instructions. Let me make sure I'm following:
- Job Title
- Role Summary: concise overview, excluding company details, location, benefits. The original says "build and maintain business-critical web applications used daily by customers." Also, "passionate about solving real problems for SaaS users." But maybe the role summary should focus on the main purpose. So something like "Develop and maintain business-critical web applications for SaaS users, focusing on full-stack solutions and system migration."
Expectations: What the role requires. Maybe not a separate section, but part of the responsibilities. Wait the user's output format includes Expectations as a separate line. Wait, the user's output example (from the input) says:
Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications.
So Expactations is a typo for Expectations. The user wrote "Expactations", probably a typo. Let me check the original instruction:
"Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications."
But that's probably a typo for "Expectations". However, the assistant should correct that? Wait, the user is providing the instruction with a typo. Should I treat "Expactations" as an error and proceed as "Expectations"? Since the instructions are in the user's query, and the assistant must follow exactly. However, maybe the user made a typo, and "Expactations" should be "Expectations". So perhaps in the output, list as "Expectations" as that's likely what was intended. But the user wrote it incorrectly. Hmm. Well, in the output, the user wants the line "Expactations", so I need to follow that. But that's a typo. However, since the user specified it, perhaps proceed as written, even with a typo. But the correct term is "Expectations", so maybe the user meant that, and the typo is in the instruction. To be safe, I'll use "Expectations" as it's the correct spelling. Because maybe the user just made a typo. Alternatively, follow exactly as written. Hmm. The user might have made a mistake. Let me check the user's instruction again. The user says: "Output only: Job title, Role Summary, Expactations, Key Responsibilities..." So, probably a typo. Given that, perhaps the user intended "Expectations". So proceed with that correction. Therefore, in the output, the section is "Expectations". Otherwise, if I type "Expactations", that's wrong. Since the user might have a typo, but in the output, we need to follow the correct term for ATS-friendliness. Therefore, correct the typo and use "Expectations". That makes sense.
In the original job description, the "What You’ll Do" section includes the responsibilities, and the "Skills You’ll Need" is the skill section. The "Expectations" might be part of the role summary. Wait, the user's output instructions include "Expactations" as separate from Role Summary. So the Role Summary is the high-level summary, Expectations are what the role expects from the candidate. But the user probably intended "Expectations" to be what the company expects in terms of qualifications, etc. However, in the given job description, the Expectations may not be clearly separated. Alternatively, maybe "Expectations" is a redundant section. But according to the user's instructions, it's required. So perhaps for Expectations, list things like experience level, required skills. Wait, maybe the user uses Expectations as the role requirements. For example, the job requires experience in full-stack development, .NET, JavaScript, etc. So perhaps in the Expectations, we can repeat the key expectations. But looking at