- Company Name
- indie.inc
- Job Title
- Embedded Software Test Engineer
- 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 any fluff. They also specified the output should be in English and only include certain sections: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, and Required Education & Certifications. The user emphasized being factual, concise, ATS-friendly, and globally neutral.
First, I need to read through the provided job description carefully. The job title is Embedded Software Test Engineer. The company's mission and culture are mentioned, but since those are part of the fluff, I can ignore them. The role summary should encapsulate the essence of the job, which is verifying automotive radar software with compliance to certain standards.
For Key Responsibilities, the job description lists several tasks. I need to condense those into bullet points, focusing on actions like defining test specs, automation scripts, verifying software layers, etc. I should make sure to use active verbs and remove any redundant information.
Required Skills should highlight the necessary qualifications: degrees, experience, knowledge of protocols, programming languages, tools like Vector toolchain, debugging skills, etc. Preferred qualifications are optional, so maybe some of those can be moved to the Required Skills if they're important. Wait, the user said to exclude fluff, but in the required skills, they want the hard requirements. Let me check the original instructions again. The user said to exclude company details, location, benefits, or fluff, so preferred qualifications can be omitted unless they're part of the required skills. Hmm. The user hasn't specified if preferred is required here. The job description's Required Qualifications are the essentials, so those should go into Required Skills. The preferred ones can be left out unless the user wants them. Let me check the example response. In the example, Preferred Qualifications were not included in the final output. So, I should stick to the Required Qualifications.
Education and certifications: the job requires a Bachelor's or Master's in related fields. The ISTQB certification is listed under preferred, but since the user wants Required Education & Certifications, maybe ISTQB isn't required here. The user's instruction says "exclude... fluff"—if ISTQB is under preferred, it's not mandatory, so maybe it's better to leave it out unless specified as required. However, in the example given, ISTQB is included in Required Education & Certifications. Wait, in the example, the ISTQB is listed as "Preferred Qualifications" but in the final output under Required Education & Certifications, it's excluded. Wait, no—the final output example from the user includes ISTQB under Required Skills? Let me check. The user's example response (in the thinking process) shows the final output. Let me recheck the original user's message.
The user's instruction says: "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications."
In the job description's Required Qualifications, ISTQB is under "Preferred Qualifications". The user said not to include preferred qualifications unless they are required. Wait, the user says "Required Education & Certifications", so if ISTQB is in the required section, include it. But in the job description, ISTQB is listed under "Preferred Qualifications". So, unless the user wants both required and preferred to be included in Required Education & Certifications, which is unlikely, I should only include the ones that are mandatory.
So, the required education is the Bachelor's or Master's. Required certifications are ISTQB if it's required, but since it's in the preferred, maybe it's not. Wait, in the original job description, ISTQB is listed under "Preferred Qualifications", not required. So should it be excluded? The final answer example might have included it, but let me check the user's sample output in their query. Wait, the user provided their own example output in the query? Let me see.
Wait, the user hasn't provided a sample output. They are asking me to generate it. So, based on the instructions, Required Education & Certifications should only include the ones that are required. The job description's Required Qualifications don't list ISTQB as required, but under Preferred. Therefore, in the final output, ISTQB isn't required here. Unless the user considers that ISTQB is part of the required skills. But according to the job description given, ISTQB is under "Preferred Qualifications", so in the Required section, it's not needed.
Wait, in the "Required Qualifications" section of the job description, it's under "Required Qualifications"? Let me check again. The job description's Required Qualifications are under "Required Qualifications" and "Preferred Qualifications". The Required Qualifications list the Bachelor's or Master's, 2+ years experience, etc. The Preferred Qualifications include ISTQB. So ISTQB is not a required certification.
So, in the final output, Required Education & Certifications would be Bachelor's or Master's in Electrical, Computer Engineering. The ISTQB is optional (Preferred) and not required, so it's excluded.
Now, the Key Responsibilities: The original job description lists several, but we need to condense them. The main points are defining and developing test specs, automation scripts, verifying AUTOSAR layers, performance testing, integrating automation into CI/CD, compliance with ISO 26262, test coverage, using Vector tools, debugging, analyzing datasheets.
For Required Skills, the user wants to list the necessary skills. Required skills from the job description are: solid understanding of microcontrollers, embedded C, RTOS; strong knowledge of communication protocols (CAN, SPI, I2C, UART, Ethernet); proficiency in C, Python, CAPL; skilled in debugging tools; solid English skills.
Wait, the user said to exclude fluff. Any redundant or repeated points should be condensed.
The final output should be in ATS-friendly language, meaning keywords that applicant tracking systems can pick up. Terms like ISO 26262, Automotive SPICE, AUTOSAR, etc., should be included.
Also, the Expectations section is a bit confusing. The user instruction says to include "Expactations"—probably a typo for "Expectations". So I'll need to include that. The expectation here is what the job expects from the candidate, like compliance with ISO standards, collaboration with engineering teams, etc. Maybe combine that with the role summary.
Wait, the user's instruction lists the sections as: Role Summary, Expactations, Key Responsibilities... perhaps "Expactations" is a typo for "Expectations". So in the output, I should write Expectations. The role summary is a concise overview of the position. The expectations would be what is expected from the candidate, possibly the key responsibilities or the compliance standards.
Actually, perhaps "Expectations" is meant to outline what the job requires in terms of experience, skills, etc. But looking back, the user's example in their instruction might not clarify. However, the user says to include "Expactations" (probably Expectations). So in the context of the job profile, Expectations might refer to the required experience or qualifications. But the user also has "Key Responsibilities" and "Required Skills". So perhaps "Expectations" is redundant. Wait, the user's instruction says to output the following sections: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications.
This seems a bit off. Normally, a job profile would have Role Summary, Key Responsibilities, Required Skills, Required Education. The "Expectations" section might be overlapping. Perhaps "Expectations" is a section where the job expects certain qualifications or standards. However, given the user's instruction, I need to follow it as written. So "Expectations" might be the experience and compliance standards. Let me check the original job description. Under Key Responsibilities, compliance with ISO 26262 is mentioned. So maybe Expectations refers to the compliance standards the candidate is expected to work with. Alternatively, maybe the user intended to have Expectations as what the job expects from the candidate, such as years of experience, etc. But the user's instruction is to keep it factual and ATS-friendly. Let me structure it as per the user's instruction.
So Role Summary is a brief overview of the role. Expectations would be what is required in terms of experience or standards compliance. Key Responsibilities are the main tasks. Required Skills are the hard skills. Required Education & Certifications are obvious.
But maybe the user made a typo and Expectations is supposed to be another section. Alternatively, maybe "Expactations" is a typo for "Requirements". But since the user wrote "Expactations", I should proceed with that as the title. So "Expactations" probably is a typo for "Expectations". Given that, I'll use "Expectations" as the section title.
So, putting it all together:
Job Title: Embedded Software Test Engineer
Role Summary: Develop and execute test specifications for automotive radar software, ensuring compliance with ISO 26262 ASIL B and Automotive SPICE 4.0 CL2 standards. Collaborate with engineering teams to verify safety and functional requirements using embedded systems and automate test processes.
Expectations: 2+ years of experience in embedded software verification, compliance with ISO 26262, Automotive SPICE, and AUTOSAR standards for embedded systems verification.
Key Responsibilities: - Define, develop, and execute embedded hardware test specifications. - Design automation scripts (C, Python, CAPL) and integrate into CI/CD. - Verify AUTOSAR MCAL, CDD, BSW layers (Quad SPI