- Company Name
- Cirrus Logic
- Job Title
- Summer Intern, Signal Processing Embedded Software Engineer
- Job Description
-
<think>
Okay, let me start by understanding what the user is asking for. They need a concise job profile for an internship position in Signal Processing Embedded Software Engineer. The key here is to normalize the job description into a structured summary without any fluff.
First, I need to extract the job title. That's straightforward: "Summer Intern, Signal Processing Embedded Software Engineer." I'll keep that as the title.
Next, the role summary. The original job description mentions working on signal processing algorithm development, areas like audio and battery power systems, and the intern will be mentored. I should condense this into a brief summary that highlights the main objective: supporting signal processing algorithm development with experimentation, data analysis, and collaboration in embedded systems. Also mention the potential areas (audio, battery) and the need for creativity and communication skills.
Then, expectations. The description lists independent or team work, part-time availability, creativity, and part-time during school. I need to present these as expectations clearly. The user wants to know what the company expects from the intern.
Key responsibilities should list the main tasks: conducting experiments in specific labs, testing batteries, documenting methods, writing MATLAB code, presenting findings. I'll make sure each responsibility is a bullet point without extra details.
Required skills: They need an MS in electrical engineering with signal processing, Matlab fluency, communication, attention to detail. I'll list these without the company's preferred requirements, but maybe mention the preferred ones if they are critical. Wait, no—the user said to exclude fluff and focus on required. The preferred skills are separate, so maybe list required and preferred under separate headings. But in the example, they combined them into "Required Skills." Wait, the user specified "Required Skills, Required Education & Certifications." So maybe required and preferred are separate? Wait, looking back at the user's instructions: "Required Skills, Required Education & Certifications." So maybe required skills include both, but the user might have wanted required vs preferred. But according to their example, the user lists Required Skills and then Required Education & Certifications. The original job description lists Required and Preferred Knowledge. So maybe I should structure as:
Required Skills: Matlab fluency, comm/organizational skills, attention to detail.
Preferred Skills: PhD, Python, C, lab experience, etc. But the user's output example in their instructions does not have a separate section for preferred. Wait, looking at the example they provided in the initial prompt, the output includes Required Skills and Required Education & Certifications. The original job description has a section for Required Knowledge and Preferred. Since the user says "Exclude fluff", but also to provide "Required Skills" and "Required Education & Certifications", I think that the required vs. preferred should be part of Required Skills if the job posting differentiates. Wait, the user instructions say "Required Skills, Required Education & Certifications. Keep it factual..." So perhaps I should list required first, then perhaps in parentheses mention preferred if needed. But the example they provided in their output (the one they want) doesn't have a separate preferred section. Wait, in their provided output example, it's:
Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. So perhaps the required skills include both required and preferred as separate bullet points. Let me check the original job description to see what's required and what's preferred. The Required includes MS in Signal Processing, Matlab, communication, etc. Preferred includes PhD, Python, C, etc. The user instructions say to include Required Skills, so the required ones, but the user might want Preferred as part of the required if necessary? But the user's own example output seems to have required skills without the preferred ones. For example, in the output example provided by the user, they have "Required Skills" as a bullet list. So perhaps in this case, the answer should only include required and not preferred, but the user's instructions mention to exclude fluff but include required. The original job description under Required Knowledge lists some as Required and others as Preferred. So in the answer, I should only include the Required ones. However, the user might consider that some of the preferred are important enough to include. Wait, but the user says "Exclude company details, location, benefits, or fluff." So maybe the preferred are fluff unless they are explicitly required. However, in the original job description, the preferred includes "Ph.D. candidate" which could be considered part of the required education. Wait, the required education is "M.S. candidate", and preferred is "Ph.D. candidate". So perhaps in Education & Certifications, the required is M.S., and preferred is PhD.
So, Required Education & Certifications: M.S. in Signal Processing (Electrical Engineering). Preferred: Ph.D. in same field.
But according to the user's output example, the Required Education & Certifications would be listed there. So maybe in the answer, separate required and preferred under each category if needed.
The user instructions also specify to keep it ATS-friendly, which is used in hiring technology, so keywords are important. So including terms like "Matlab", "Python", "C programming", "Signal processing", "Battery systems", etc.
Also, the user wants to make sure to exclude company details, location, benefits, or fluff. So I need to remove parts like "Cirrus Logic follows a 2+ day in-office..." and "Export control..." etc.
So the main sections would be:
Job Title: ...
Role Summary: Supporting signal processing algorithm development for embedded systems in audio and battery power systems, conducting experiments, data collection/analysis, and collaboration with mentorship.
Expectations: Part-time during school, in-office up to 5 days/week, based in a commutable distance.
Key Responsibilities: Conduct experiments in specific labs, data collection, testing batteries, document methods, write MATLAB code, present findings.
Required Skills: MATLAB, communication skills, organization, attention to detail.
Required Education & Certifications: M.S. in Electrical Engineering (Signal processing).
Preferred Skills: Ph.D., Python, C, lab experience, pro audio equipment, power systems familiarity.
But the user's instructions say to output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. So no need to separate preferred skills from required skills unless specified. Since the user says to exclude fluff, perhaps only include required, but the original job description has both required and preferred, so maybe list required as bullet points and preferred in another section. But user's example output combines everything under Required Skills.
Wait, looking back, the user says: "Exclude fluff" but "keep it factual, concise, ATS-friendly". Therefore, maybe include both required and preferred, but mark them as required or preferred? However, the user's output example doesn't have a preferred section. Let me check their example:
In the example they provided, the output has "Required Skills" and "Required Education & Certifications". So perhaps the answer should include both required and preferred under the appropriate sections. For example, Required Skills could list the mandatory and preferred as separate points, but maybe that's allowed. Alternatively, maybe the answer should only include required, as the user may consider preferred as optional. But the problem is that in some cases, ATS systems might penalize if they don't see certain required keywords. The user's original job description has both required and preferred, and since the user wants to make it ATS-friendly, including both might help in matching. But the user's instruction says to exclude fluff. The fluff includes company culture, benefits, etc. But required and preferred skills are part of the job requirements.
Since the user's example output includes both required and preferred under the same sections (like in the example provided in the problem, but looking at the example output isn't available yet because I need to create it), but the user's own example instruction says:
"Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications."
So perhaps in the answer, Required Skills includes both required and preferred, as ATS systems look for keywords. For example, in the original job description, the Required Skills are:
Matlab fluency
Excellent organizational and communication skills
Attention to detail and organization
Preferred:
Ph.D. candidate
Python fluency
C programming
Lab experience
Audio equipment familiarity
Battery cycler familiarity
So, maybe in the answer, Required Skills includes the required ones, and under Required Skills, perhaps include preferred in parentheses or as separate bullet points? But the user's example output shows that the required skills are listed first. However, given the constraint of max 500 words and being concise, maybe include required first, and then mention preferred, but perhaps not. Since the user wants to make it ATS-friendly, and the preferred are not required but often considered, maybe include the preferred skills in the Required Skills section, but label them as preferred.
But the user's instructions say to exclude fluff. The fluff is company details, locations, benefits. Required and preferred are job requirements, which are needed for matching. So perhaps include both required and preferred under Required Skills and Required Education & Certifications, maybe using phrases like "Preferred: ...".
But the user's initial instruction says: "Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications." So maybe list all required and preferred under those headings, with clear separation.
However, the user's instruction says to exclude fluff and keep it concise. Including preferred skills might not be considered fluff. In ATS systems, both required and preferred are useful for matching, especially if those preferred skills are common in the field. Therefore, it's better to include them for better matching, even if they are preferred.
So in this case, the answer should have under Required Skills both the required and preferred, perhaps