Senior Silicon Security Engineer
CyberJobs.Com · San Jose, CA · 1 mo ago
Information Technology$65k–$85k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each section heading. Use
for each section heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Company Description: first paragraph about Renesas. That's not a section heading but could be part of About the role? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include an About the role section containing company description and job description overview.
We need to include Responsibilities: list of duties.
Qualifications: includes Required Technical Skills and Preferred Qualifications and Education.
Skills: maybe separate? The posting includes "Required Technical Skills" and "Preferred Qualifications". Could combine into Requirements or Qualifications. The instruction says we can use sections like Requirements, Qualifications, Skills. We need to decide which sections to include based on content.
We have Pay: The posting includes "The expected annual base salary range for this position is $65,000 to $85,000." Also later "Compensation: USD 68000 - USD 85000 - yearly". So we have pay info. So we should include a Pay section.
Benefits: The posting mentions "We believe in rewarding our employees with a competitive benefits package alongside their salary. More information will be provided during the hiring process." That's vague, not specific benefits. According to rule: never create Benefits section unless posting actually states them. It mentions competitive benefits package but not specifics. That's likely too vague; we should not create Benefits section.
Schedule: Not mentioned. Remote Work Available: No. That's schedule? Not exactly. Could be considered work arrangement. But not explicit schedule like full-time, part-time. Might not create Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, diversity statement, export controls, etc.
We need to preserve all substantive information.
Thus sections:
- About the role: includes company description and job description overview (first paragraphs). Could combine company description and job description summary.
- Responsibilities: list bullet points from Responsibilities section.
- Qualifications: could include Required Technical Skills, Preferred Qualifications, Education. Could be a single Qualifications section with subpoints? But we need to use - for any list. Could have nested lists? Probably fine.
- Skills: maybe separate? But we already have qualifications covering skills. Could combine.
- Pay: include salary range.
We need to ensure we don't repeat job title as heading.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content.
Company Description:
"Renesas is an embedded semiconductor solution provider driven by its Purpose 'To Make Our Lives Easier.' As the industry’s leading expert in embedded processing with unmatched quality and system-level know-how, we have evolved to provide scalable and comprehensive semiconductor solutions for automotive, industrial, infrastructure, and IoT industries based on the broadest product portfolio, including High Performance Computing, Embedded Processing, Analog & Connectivity, and Power."
Job Description overview:
"We are seeking a motivated Cloud DevOps and AI Security Engineer to help support, secure, and scale our emerging AI infrastructure and development pipeline. This role is intended for a recent graduate, master’s graduate, or early-career professional with hands-on experience from coursework, internships, projects, or related work. In this role, you will work with developers and operations leads to implement secure cloud practices, maintain automated deployment pipelines, monitor security posture, document controls, and support the responsible use of AI-assisted engineering tools. This is an opportunity to build practical experience with Infrastructure as Code (IaC), continuous integration, DevSecOps practices, production web operations, cloud security, and secure AI-enabled development workflows."
That's substantive.
Responsibilities bullet points:
- AI Infrastructure and Pipeline Security: As we move to adopt a more AI / Agentic workflow you will help secure emerging AI infrastructure and AI-enabled development by supporting security checks, documenting controls, validating tool configurations, and escalating potential risks under guidance from senior team members.
- Security Monitoring: Review logs, alerts, system activity, and pipeline outputs to help identify, document, and escalate potential vulnerabilities or unusual behavior.
- Cloud Infrastructure Support: Assist in provisioning, configuring, and maintaining core AWS services such as VPC, EC2, S3, IAM, Lambda, Docker, and Kubernetes.
- Infrastructure as Code: Learn, update, and write basic Terraform, Serverless, or AWS CloudFormation templates under guidance from senior team members.
- Access Management: Help manage user permissions and access controls using AWS IAM and least-privilege principles.
- Team Collaboration: Work with developers, QA, and operations team members to troubleshoot issues, document findings, and support safe releases for customer-facing web platforms.
- Deployment Support: Help maintain and improve automated CI/CD pipelines to support safe, reliable, and repeatable software delivery.
- Documentation: Create and maintain clear technical documentation for architecture diagrams, deployment processes, access controls, and security protocols.
Qualifications:
Required Technical Skills:
- Cloud Fundamentals: Foundational understanding of AWS services, cloud computing concepts, networking basics, IAM, security groups, and common web infrastructure patterns.
- Cloud Security Fundamentals: Basic familiarity with least privilege, access controls, encryption, secrets management, logging, and secure configuration practices.
- Security Monitoring and Triage: Ability to review logs, alerts, system activity, and pipeline outputs, document findings clearly, and escalate potential risks.
- Automation Exposure: Basic experience with scripting languages such as Python or Bash to automate repetitive operational or security-related tasks.
- Version Control: Familiarity with Git workflows, Bitbucket pipelines, pull requests, branching strategies, and change tracking.
- AI-Assisted Engineering: Awareness of how AI coding assistants and automation tools can be used responsibly, including protecting sensitive information, validating tool outputs, documenting AI-assisted changes, and following approved safe-use practices.
Preferred Qualifications:
- Experience: 0–2 years of experience in IT support, systems administration, cloud operations, cybersecurity, software engineering, web operations, or a junior DevOps role.
- Certifications: Relevant entry-level certifications, such as AWS Cloud Practitioner, CompTIA Security+, or equivalent, are helpful but not required.
Education:
- Degree in Computer Science, Cybersecurity, Software Engineering, Information Systems, or a related field, or equivalent practical experience.
- Coursework, internships, graduate research, capstone projects, or hands-on work involving cloud security, DevSecOps, secure software development, application security, AI infrastructure, or responsible use of AI coding assistants are highly desirable.
Pay:
- The expected annual base salary range for this position is $65,000 to $85,000. This range does not include potential short-term or long-term incentive compensation. Actual compensation may vary based on relevant experience, skills, qualifications, geographic location, and other job-related factors.
- Also later: Compensation: USD 68000 - USD 85000 - yearly. Slight discrepancy but both convey range. We'll include the range as stated.
We should not duplicate. We'll include the first statement.
We need to avoid boilerplate: The repeated company description later, TAGIE culture, benefits vague, EEO, export controls, etc. Remove those.
Now construct HTML.
We'll have:
About the role
... company description + job description overview ...
Responsibilities
- ... each responsibility ...
Qualifications
We could split into Required Technical Skills, Preferred Qualifications, Education as subheadings? But only allowed headings are those listed; we could still use for sub-sections? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could keep only those headings. However we need to present the qualifications content. Could put all under Qualifications heading and use - for each bullet, maybe with nested
for sub-items? That's okay.
We'll do:
Qualifications
- Required Technical Skills:
- Cloud Fundamentals: Foundational understanding of AWS services, cloud computing concepts, networking basics, IAM, security groups, and common web infrastructure patterns.
- Cloud Security Fundamentals: Basic familiarity with least privilege, access controls, encryption, secrets management, logging, and secure configuration practices.
- Security Monitoring and Triage: Ability to review logs, alerts, system activity, and pipeline outputs, document findings clearly, and escalate potential risks.
- Automation Exposure: Basic experience with scripting languages such as Python or Bash to automate repetitive operational or security-related tasks.
- Version Control: Familiarity with Git workflows, Bitbucket pipelines, pull requests, branching strategies, and change tracking.
- AI-Assisted Engineering: Awareness of how AI coding assistants and automation tools can be used responsibly, including protecting sensitive information, validating tool outputs, documenting AI-assisted changes, and following approved safe-use practices.
- Preferred Qualifications:
- Experience: 0–2 years of experience in IT support, systems administration, cloud operations, cybersecurity, software engineering, web operations, or a junior DevOps role.
- Certifications: Relevant entry-level certifications, such as AWS Cloud Practitioner, CompTIA Security+, or equivalent, are helpful but not required.
- Education:
- Degree in Computer Science, Cybersecurity, Software Engineering, Information Systems, or a related field, or equivalent practical experience.
- Coursework, internships, graduate research, capstone projects, or hands-on work involving cloud security, DevSecOps, secure software development, application security, AI infrastructure, or responsible use of AI coding assistants are highly desirable.
That seems fine.
Pay section:
Pay
The expected annual base salary range for this position is $65,000 to $85,000. This range does not include potential short-term or long-term incentive compensation. Actual compensation may vary based on relevant experience, skills, qualifications, geographic location, and other job-related factors.
We could also mention the USD 68000 - USD 85000 yearly but it's redundant; we can include both? Might be considered duplication. Better to include just the first statement; it's substantive.
We should not include Benefits or Schedule sections.
Now ensure we removed boilerplate: The repeated company description later, TAGIE culture, benefits vague, EEO, export controls, Remote Work Available, Employment Type, etc.
Check for any duplicated lines: The company description appears twice; we used only once.
Now produce final HTML fragment.
Make sure to not include any markdown fences.
Let's craft
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Company Description: first paragraph about Renesas. That's not a section heading but could be part of About the role? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include an About the role section containing company description and job description overview.
We need to include Responsibilities: list of duties.
Qualifications: includes Required Technical Skills and Preferred Qualifications and Education.
Skills: maybe separate? The posting includes "Required Technical Skills" and "Preferred Qualifications". Could combine into Requirements or Qualifications. The instruction says we can use sections like Requirements, Qualifications, Skills. We need to decide which sections to include based on content.
We have Pay: The posting includes "The expected annual base salary range for this position is $65,000 to $85,000." Also later "Compensation: USD 68000 - USD 85000 - yearly". So we have pay info. So we should include a Pay section.
Benefits: The posting mentions "We believe in rewarding our employees with a competitive benefits package alongside their salary. More information will be provided during the hiring process." That's vague, not specific benefits. According to rule: never create Benefits section unless posting actually states them. It mentions competitive benefits package but not specifics. That's likely too vague; we should not create Benefits section.
Schedule: Not mentioned. Remote Work Available: No. That's schedule? Not exactly. Could be considered work arrangement. But not explicit schedule like full-time, part-time. Might not create Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, diversity statement, export controls, etc.
We need to preserve all substantive information.
Thus sections:
- About the role: includes company description and job description overview (first paragraphs). Could combine company description and job description summary.
- Responsibilities: list bullet points from Responsibilities section.
- Qualifications: could include Required Technical Skills, Preferred Qualifications, Education. Could be a single Qualifications section with subpoints? But we need to use - for any list. Could have nested lists? Probably fine.
- Skills: maybe separate? But we already have qualifications covering skills. Could combine.
- Pay: include salary range.
We need to ensure we don't repeat job title as heading.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content.
Company Description:
"Renesas is an embedded semiconductor solution provider driven by its Purpose 'To Make Our Lives Easier.' As the industry’s leading expert in embedded processing with unmatched quality and system-level know-how, we have evolved to provide scalable and comprehensive semiconductor solutions for automotive, industrial, infrastructure, and IoT industries based on the broadest product portfolio, including High Performance Computing, Embedded Processing, Analog & Connectivity, and Power."
Job Description overview:
"We are seeking a motivated Cloud DevOps and AI Security Engineer to help support, secure, and scale our emerging AI infrastructure and development pipeline. This role is intended for a recent graduate, master’s graduate, or early-career professional with hands-on experience from coursework, internships, projects, or related work. In this role, you will work with developers and operations leads to implement secure cloud practices, maintain automated deployment pipelines, monitor security posture, document controls, and support the responsible use of AI-assisted engineering tools. This is an opportunity to build practical experience with Infrastructure as Code (IaC), continuous integration, DevSecOps practices, production web operations, cloud security, and secure AI-enabled development workflows."
That's substantive.
Responsibilities bullet points:
- AI Infrastructure and Pipeline Security: As we move to adopt a more AI / Agentic workflow you will help secure emerging AI infrastructure and AI-enabled development by supporting security checks, documenting controls, validating tool configurations, and escalating potential risks under guidance from senior team members.
- Security Monitoring: Review logs, alerts, system activity, and pipeline outputs to help identify, document, and escalate potential vulnerabilities or unusual behavior.
- Cloud Infrastructure Support: Assist in provisioning, configuring, and maintaining core AWS services such as VPC, EC2, S3, IAM, Lambda, Docker, and Kubernetes.
- Infrastructure as Code: Learn, update, and write basic Terraform, Serverless, or AWS CloudFormation templates under guidance from senior team members.
- Access Management: Help manage user permissions and access controls using AWS IAM and least-privilege principles.
- Team Collaboration: Work with developers, QA, and operations team members to troubleshoot issues, document findings, and support safe releases for customer-facing web platforms.
- Deployment Support: Help maintain and improve automated CI/CD pipelines to support safe, reliable, and repeatable software delivery.
- Documentation: Create and maintain clear technical documentation for architecture diagrams, deployment processes, access controls, and security protocols.
Qualifications:
Required Technical Skills:
- Cloud Fundamentals: Foundational understanding of AWS services, cloud computing concepts, networking basics, IAM, security groups, and common web infrastructure patterns.
- Cloud Security Fundamentals: Basic familiarity with least privilege, access controls, encryption, secrets management, logging, and secure configuration practices.
- Security Monitoring and Triage: Ability to review logs, alerts, system activity, and pipeline outputs, document findings clearly, and escalate potential risks.
- Automation Exposure: Basic experience with scripting languages such as Python or Bash to automate repetitive operational or security-related tasks.
- Version Control: Familiarity with Git workflows, Bitbucket pipelines, pull requests, branching strategies, and change tracking.
- AI-Assisted Engineering: Awareness of how AI coding assistants and automation tools can be used responsibly, including protecting sensitive information, validating tool outputs, documenting AI-assisted changes, and following approved safe-use practices.
Preferred Qualifications:
- Experience: 0–2 years of experience in IT support, systems administration, cloud operations, cybersecurity, software engineering, web operations, or a junior DevOps role.
- Certifications: Relevant entry-level certifications, such as AWS Cloud Practitioner, CompTIA Security+, or equivalent, are helpful but not required.
Education:
- Degree in Computer Science, Cybersecurity, Software Engineering, Information Systems, or a related field, or equivalent practical experience.
- Coursework, internships, graduate research, capstone projects, or hands-on work involving cloud security, DevSecOps, secure software development, application security, AI infrastructure, or responsible use of AI coding assistants are highly desirable.
Pay:
- The expected annual base salary range for this position is $65,000 to $85,000. This range does not include potential short-term or long-term incentive compensation. Actual compensation may vary based on relevant experience, skills, qualifications, geographic location, and other job-related factors.
- Also later: Compensation: USD 68000 - USD 85000 - yearly. Slight discrepancy but both convey range. We'll include the range as stated.
We should not duplicate. We'll include the first statement.
We need to avoid boilerplate: The repeated company description later, TAGIE culture, benefits vague, EEO, export controls, etc. Remove those.
Now construct HTML.
We'll have:
About the role
... company description + job description overview ...
Responsibilities
- ... each responsibility ...
Qualifications
We could split into Required Technical Skills, Preferred Qualifications, Education as subheadings? But only allowed headings are those listed; we could still use for sub-sections? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could keep only those headings. However we need to present the qualifications content. Could put all under Qualifications heading and use - for each bullet, maybe with nested
for sub-items? That's okay.
We'll do:
Qualifications
- Required Technical Skills:
- Cloud Fundamentals: Foundational understanding of AWS services, cloud computing concepts, networking basics, IAM, security groups, and common web infrastructure patterns.
- Cloud Security Fundamentals: Basic familiarity with least privilege, access controls, encryption, secrets management, logging, and secure configuration practices.
- Security Monitoring and Triage: Ability to review logs, alerts, system activity, and pipeline outputs, document findings clearly, and escalate potential risks.
- Automation Exposure: Basic experience with scripting languages such as Python or Bash to automate repetitive operational or security-related tasks.
- Version Control: Familiarity with Git workflows, Bitbucket pipelines, pull requests, branching strategies, and change tracking.
- AI-Assisted Engineering: Awareness of how AI coding assistants and automation tools can be used responsibly, including protecting sensitive information, validating tool outputs, documenting AI-assisted changes, and following approved safe-use practices.
- Preferred Qualifications:
- Experience: 0–2 years of experience in IT support, systems administration, cloud operations, cybersecurity, software engineering, web operations, or a junior DevOps role.
- Certifications: Relevant entry-level certifications, such as AWS Cloud Practitioner, CompTIA Security+, or equivalent, are helpful but not required.
- Education:
- Degree in Computer Science, Cybersecurity, Software Engineering, Information Systems, or a related field, or equivalent practical experience.
- Coursework, internships, graduate research, capstone projects, or hands-on work involving cloud security, DevSecOps, secure software development, application security, AI infrastructure, or responsible use of AI coding assistants are highly desirable.
That seems fine.
Pay section:
Pay
The expected annual base salary range for this position is $65,000 to $85,000. This range does not include potential short-term or long-term incentive compensation. Actual compensation may vary based on relevant experience, skills, qualifications, geographic location, and other job-related factors.
We could also mention the USD 68000 - USD 85000 yearly but it's redundant; we can include both? Might be considered duplication. Better to include just the first statement; it's substantive.
We should not include Benefits or Schedule sections.
Now ensure we removed boilerplate: The repeated company description later, TAGIE culture, benefits vague, EEO, export controls, Remote Work Available, Employment Type, etc.
Check for any duplicated lines: The company description appears twice; we used only once.
Now produce final HTML fragment.
Make sure to not include any markdown fences.
Let's craft
About the role
... company description + job description overview ...
Responsibilities
- ... each responsibility ...
Qualifications
We could split into Required Technical Skills, Preferred Qualifications, Education as subheadings? But only allowed headings are those listed; we could still use for sub-sections? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could keep only those headings. However we need to present the qualifications content. Could put all under Qualifications heading and use - for each bullet, maybe with nested
for sub-items? That's okay.
We'll do:
Qualifications
- Required Technical Skills:
- Cloud Fundamentals: Foundational understanding of AWS services, cloud computing concepts, networking basics, IAM, security groups, and common web infrastructure patterns.
- Cloud Security Fundamentals: Basic familiarity with least privilege, access controls, encryption, secrets management, logging, and secure configuration practices.
- Security Monitoring and Triage: Ability to review logs, alerts, system activity, and pipeline outputs, document findings clearly, and escalate potential risks.
- Automation Exposure: Basic experience with scripting languages such as Python or Bash to automate repetitive operational or security-related tasks.
- Version Control: Familiarity with Git workflows, Bitbucket pipelines, pull requests, branching strategies, and change tracking.
- AI-Assisted Engineering: Awareness of how AI coding assistants and automation tools can be used responsibly, including protecting sensitive information, validating tool outputs, documenting AI-assisted changes, and following approved safe-use practices.
- Preferred Qualifications:
- Experience: 0–2 years of experience in IT support, systems administration, cloud operations, cybersecurity, software engineering, web operations, or a junior DevOps role.
- Certifications: Relevant entry-level certifications, such as AWS Cloud Practitioner, CompTIA Security+, or equivalent, are helpful but not required.
- Education:
- Degree in Computer Science, Cybersecurity, Software Engineering, Information Systems, or a related field, or equivalent practical experience.
- Coursework, internships, graduate research, capstone projects, or hands-on work involving cloud security, DevSecOps, secure software development, application security, AI infrastructure, or responsible use of AI coding assistants are highly desirable.
That seems fine.
Pay section:
Pay
The expected annual base salary range for this position is $65,000 to $85,000. This range does not include potential short-term or long-term incentive compensation. Actual compensation may vary based on relevant experience, skills, qualifications, geographic location, and other job-related factors.
We could also mention the USD 68000 - USD 85000 yearly but it's redundant; we can include both? Might be considered duplication. Better to include just the first statement; it's substantive.
We should not include Benefits or Schedule sections.
Now ensure we removed boilerplate: The repeated company description later, TAGIE culture, benefits vague, EEO, export controls, Remote Work Available, Employment Type, etc.
Check for any duplicated lines: The company description appears twice; we used only once.
Now produce final HTML fragment.
Make sure to not include any markdown fences.
Let's craft
- for each bullet, maybe with nested
- for sub-items? That's okay.
We'll do:
- Required Technical Skills:
- Cloud Fundamentals: Foundational understanding of AWS services, cloud computing concepts, networking basics, IAM, security groups, and common web infrastructure patterns.
- Cloud Security Fundamentals: Basic familiarity with least privilege, access controls, encryption, secrets management, logging, and secure configuration practices.
- Security Monitoring and Triage: Ability to review logs, alerts, system activity, and pipeline outputs, document findings clearly, and escalate potential risks.
- Automation Exposure: Basic experience with scripting languages such as Python or Bash to automate repetitive operational or security-related tasks.
- Version Control: Familiarity with Git workflows, Bitbucket pipelines, pull requests, branching strategies, and change tracking.
- AI-Assisted Engineering: Awareness of how AI coding assistants and automation tools can be used responsibly, including protecting sensitive information, validating tool outputs, documenting AI-assisted changes, and following approved safe-use practices.
- Preferred Qualifications:
- Experience: 0–2 years of experience in IT support, systems administration, cloud operations, cybersecurity, software engineering, web operations, or a junior DevOps role.
- Certifications: Relevant entry-level certifications, such as AWS Cloud Practitioner, CompTIA Security+, or equivalent, are helpful but not required.
- Education:
- Degree in Computer Science, Cybersecurity, Software Engineering, Information Systems, or a related field, or equivalent practical experience.
- Coursework, internships, graduate research, capstone projects, or hands-on work involving cloud security, DevSecOps, secure software development, application security, AI infrastructure, or responsible use of AI coding assistants are highly desirable.
Qualifications
Pay
The expected annual base salary range for this position is $65,000 to $85,000. This range does not include potential short-term or long-term incentive compensation. Actual compensation may vary based on relevant experience, skills, qualifications, geographic location, and other job-related factors.
We could also mention the USD 68000 - USD 85000 yearly but it's redundant; we can include both? Might be considered duplication. Better to include just the first statement; it's substantive. We should not include Benefits or Schedule sections. Now ensure we removed boilerplate: The repeated company description later, TAGIE culture, benefits vague, EEO, export controls, Remote Work Available, Employment Type, etc. Check for any duplicated lines: The company description appears twice; we used only once. Now produce final HTML fragment. Make sure to not include any markdown fences. Let's craft - Required Technical Skills: