Senior IT Systems & Network Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map sections to those headings. The posting doesn't have explicit "Responsibilities" but we have "What You'll Accomplish" which is responsibilities. "What We Need" is requirements/qualifications/skills. "Preferred, But Not Required" could be part of qualifications. "How You’ll Work" maybe about work style, could be omitted or maybe part of responsibilities? But we should only include sections when posting has real specific content. We have content for About Lyte (company description). Could be "About the role"? Actually "About Lyte" is about company, not role. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections: About the role (maybe combine About Lyte and Why This Role Exists?), Responsibilities (What You'll Accomplish), Requirements (What We Need), Qualifications (maybe Preferred?), Skills (maybe automation experience?), Benefits, Pay. Schedule: we have mention of office five days per week, occasional evening/weekend work. That's schedule info. So we can include Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must preserve all substantive information. So we need to include all details from the posting, but organized under headings.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not invent or summarize away detail. So we need to keep specifics like technologies, timeframes, etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
About Lyte Lyte builds perception systems for Physical AI operating in complex environments. The company combines custom silicon, integrated sensors, and software into a unified platform for robotics, mobility, and next-generation automation. Lyte is headquartered in Sunnyvale, California, with a global presence. For more information, visit www.lyte.ai If you’re excited about building impactful technology in a dynamic, hands-on environment, we’d love to hear from you! Why This Role Exists Lyte is building perception systems that combine custom silicon, sensors, and software for robotics, mobility, and next-generation automation. As the company grows, its internal technology environment must become more secure, reliable, scalable, and cost-effective without adding unnecessary complexity. This role will help turn a growing IT environment into a well-controlled, supportable operation. You will work directly across identity, endpoints, Linux systems, cloud infrastructure, networking, security, vendors, and compliance. This is a hands-on individual contributor role for someone who can identify a problem, make a sound technical decision, and carry the solution through implementation.
But we might split into two paragraphs? It's okay.
Next: Responsibilities (Responsibilities
) with list of accomplishments.
We need to list bullet points for each accomplishment: first 30 days, first 90 days, six months, etc. Use - .
We need to preserve all details: "In your first 30 days, you will complete knowledge transfer across Lyte’s core IT systems, operating practices, vendors, and active projects. You will begin independently resolving recurring issues and establish working relationships with Engineering and other key partners." etc.
We'll create list items.
Next: Requirements (
Requirements
) maybe combine What We Need and Preferred? But we have separate sections: Requirements (mandatory) and Qualifications (preferred). The instruction says use headings like Requirements, Qualifications, Skills. So we can have:
Requirements
with list of mandatory items from "What We Need". Use - .
Qualifications
with preferred items from "Preferred, But Not Required". Use - .
Skills
maybe we can include automation experience? But that's already in Requirements. Could also include scripting languages. But we might not need separate Skills if covered. However instruction says prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include all if they have content. We have content for Requirements (mandatory), Qualifications (preferred), Skills (maybe we can list scripting languages as skills). But the mandatory already includes automation experience with Bash, PowerShell, Python. That's a skill. Could still have Skills section listing those. But to avoid duplication, maybe we put scripting languages under Skills, and other mandatory under Requirements. However the mandatory list includes many items; we could split.
Better: Requirements: list of mandatory items (ownership of M365, Entra ID, Intune; Linux admin; networking; endpoint ownership; delivering projects). Qualifications: preferred items (AWS/Azure/GCP; SOC 2; SIEM; GitLab; AI-tool governance; GPU/AI/ML; EDA/EPDA; vendor negotiations). Skills: automation experience with Bash, PowerShell, Python, or comparable scripting language. That seems reasonable.
Next Benefits (Benefits
) list bullet points.
Pay (Pay
) maybe just a paragraph with pay range.
Schedule (Schedule
) paragraph about office five days per week, occasional evening/weekend work.
We must not include filler like "commensurate with experience". Not present.
Now ensure we don't repeat job title. Not needed.
Now produce HTML.
Check for any duplicated lines: The posting includes some repeated phrases like "Lyte builds perception systems..." appears twice? Actually first paragraph includes that, then later "Why This Role Exists" repeats similar. We need to preserve all substantive information, but we can avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must deduplicate. But we could keep both; duplication is okay as it's preserving. However we might want to avoid repeating same sentences exactly; but it's okay.
We'll include both.
Now craft HTML.
Let's write:
About the role
About Lyte Lyte builds perception systems for Physical AI operating in complex environments. The company combines custom silicon, integrated sensors, and software into a unified platform for robotics, mobility, and next-generation automation. Lyte is headquartered in Sunnyvale, California, with a global presence. For more information, visit www.lyte.ai If you’re excited about building impactful technology in a dynamic, hands-on environment, we’d love to hear from you! Why This Role Exists Lyte is building perception systems that combine custom silicon, sensors, and software for robotics, mobility, and next-generation automation. As the company grows, its internal technology environment must become more secure, reliable, scalable, and cost-effective without adding unnecessary complexity. This role will help turn a growing IT environment into a well-controlled, supportable operation. You will work directly across identity, endpoints, Linux systems, cloud infrastructure, networking, security, vendors, and compliance. This is a hands-on individual contributor role for someone who can identify a problem, make a sound technical decision, and carry the solution through implementation.
Responsibilities
- In your first 30 days, you will complete knowledge transfer across Lyte’s core IT systems, operating practices, vendors, and active projects. You will begin independently resolving recurring issues and establish working relationships with Engineering and other key partners.
- Within your first 90 days, you will take ownership of assigned systems and deliver a meaningful milestone on a priority initiative, such as the Jamf MDM rollout, identity and endpoint improvements, and infrastructure setup for new offices and sites.
- Within six months, you will strengthen the company’s identity and endpoint security by improving controls across Microsoft 365, Entra ID, Intune, Jamf, MFA, Conditional Access, RBAC, encryption, patching, EDR, and vulnerability remediation.
- You will improve infrastructure reliability and supportability across Linux systems, firewalls, office networks, VPN access, cloud services, storage, backups, and business-continuity capabilities. Improvements will be documented and measured against priorities agreed with the IT leadership team.
- You will reduce avoidable cost and manual work by improving visibility into cloud, SaaS, licensing, compute, and storage spend and by automating high-value IT and security workflows using Bash, PowerShell, Python, or similar tools.
- By the end of your first year, the systems you own should be more secure, better documented, easier to operate, and less dependent on individual knowledge. You will have helped reduce priority risks, improve audit readiness, and give the company a stronger foundation for continued growth.
Requirements
- Demonstrated ownership of Microsoft 365, Entra ID, and Intune environments, including identity lifecycle management, MFA, Conditional Access, RBAC, Exchange, SharePoint, or Teams
- Hands-on administration and troubleshooting of Linux systems, including hardening, patching, access controls, monitoring, and availability
- Experience configuring and supporting enterprise networking, firewalls, segmentation, switching, VPNs, and remote access
- Ownership of mixed macOS, Windows, or Linux endpoint environments using platforms such as Intune, Jamf, EDR, encryption, and vulnerability-management tools
- Evidence of independently delivering infrastructure or security projects from problem identification through implementation, documentation, and operational handoff
Qualifications
- Experience with AWS, Azure, or GCP
- SOC 2 or ISO 27001
- SIEM and logging platforms
- GitLab or CI/CD environments
- AI-tool governance
- GPU or AI/ML infrastructure
- EDA or EPDA environments
- Technology-vendor or licensing negotiations
Skills
- Working automation experience with Bash, PowerShell, Python, or a comparable scripting language
Benefits
- Competitive salary and equity
- Comprehensive medical, dental, and vision coverage
- 401(k) retirement plan
- Flexible vacation and time-off policy
- Collaborative, fast-paced, and inclusive work environment
- Opportunity to work on cutting-edge technologies with a highly cross-functional team
Pay
The Pay Range For This Role Is 150,000 - 230,000 USD per year (Bay Area, CA)
Schedule
This individual contributor role is based in Lyte’s Sunnyvale office five days per week and may occasionally require evening or weekend work for maintenance, deployments, or urgent incidents.
Check for any missing info: The "How
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections: About the role (maybe combine About Lyte and Why This Role Exists?), Responsibilities (What You'll Accomplish), Requirements (What We Need), Qualifications (maybe Preferred?), Skills (maybe automation experience?), Benefits, Pay. Schedule: we have mention of office five days per week, occasional evening/weekend work. That's schedule info. So we can include Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must preserve all substantive information. So we need to include all details from the posting, but organized under headings.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not invent or summarize away detail. So we need to keep specifics like technologies, timeframes, etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
About Lyte Lyte builds perception systems for Physical AI operating in complex environments. The company combines custom silicon, integrated sensors, and software into a unified platform for robotics, mobility, and next-generation automation. Lyte is headquartered in Sunnyvale, California, with a global presence. For more information, visit www.lyte.ai If you’re excited about building impactful technology in a dynamic, hands-on environment, we’d love to hear from you! Why This Role Exists Lyte is building perception systems that combine custom silicon, sensors, and software for robotics, mobility, and next-generation automation. As the company grows, its internal technology environment must become more secure, reliable, scalable, and cost-effective without adding unnecessary complexity. This role will help turn a growing IT environment into a well-controlled, supportable operation. You will work directly across identity, endpoints, Linux systems, cloud infrastructure, networking, security, vendors, and compliance. This is a hands-on individual contributor role for someone who can identify a problem, make a sound technical decision, and carry the solution through implementation.
But we might split into two paragraphs? It's okay.
Next: Responsibilities (Responsibilities
) with list of accomplishments.
We need to list bullet points for each accomplishment: first 30 days, first 90 days, six months, etc. Use - .
We need to preserve all details: "In your first 30 days, you will complete knowledge transfer across Lyte’s core IT systems, operating practices, vendors, and active projects. You will begin independently resolving recurring issues and establish working relationships with Engineering and other key partners." etc.
We'll create list items.
Next: Requirements (
Requirements
) maybe combine What We Need and Preferred? But we have separate sections: Requirements (mandatory) and Qualifications (preferred). The instruction says use headings like Requirements, Qualifications, Skills. So we can have:
Requirements
with list of mandatory items from "What We Need". Use - .
Qualifications
with preferred items from "Preferred, But Not Required". Use - .
Skills
maybe we can include automation experience? But that's already in Requirements. Could also include scripting languages. But we might not need separate Skills if covered. However instruction says prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include all if they have content. We have content for Requirements (mandatory), Qualifications (preferred), Skills (maybe we can list scripting languages as skills). But the mandatory already includes automation experience with Bash, PowerShell, Python. That's a skill. Could still have Skills section listing those. But to avoid duplication, maybe we put scripting languages under Skills, and other mandatory under Requirements. However the mandatory list includes many items; we could split.
Better: Requirements: list of mandatory items (ownership of M365, Entra ID, Intune; Linux admin; networking; endpoint ownership; delivering projects). Qualifications: preferred items (AWS/Azure/GCP; SOC 2; SIEM; GitLab; AI-tool governance; GPU/AI/ML; EDA/EPDA; vendor negotiations). Skills: automation experience with Bash, PowerShell, Python, or comparable scripting language. That seems reasonable.
Next Benefits (Benefits
) list bullet points.
Pay (Pay
) maybe just a paragraph with pay range.
Schedule (Schedule
) paragraph about office five days per week, occasional evening/weekend work.
We must not include filler like "commensurate with experience". Not present.
Now ensure we don't repeat job title. Not needed.
Now produce HTML.
Check for any duplicated lines: The posting includes some repeated phrases like "Lyte builds perception systems..." appears twice? Actually first paragraph includes that, then later "Why This Role Exists" repeats similar. We need to preserve all substantive information, but we can avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must deduplicate. But we could keep both; duplication is okay as it's preserving. However we might want to avoid repeating same sentences exactly; but it's okay.
We'll include both.
Now craft HTML.
Let's write:
About the role
About Lyte Lyte builds perception systems for Physical AI operating in complex environments. The company combines custom silicon, integrated sensors, and software into a unified platform for robotics, mobility, and next-generation automation. Lyte is headquartered in Sunnyvale, California, with a global presence. For more information, visit www.lyte.ai If you’re excited about building impactful technology in a dynamic, hands-on environment, we’d love to hear from you! Why This Role Exists Lyte is building perception systems that combine custom silicon, sensors, and software for robotics, mobility, and next-generation automation. As the company grows, its internal technology environment must become more secure, reliable, scalable, and cost-effective without adding unnecessary complexity. This role will help turn a growing IT environment into a well-controlled, supportable operation. You will work directly across identity, endpoints, Linux systems, cloud infrastructure, networking, security, vendors, and compliance. This is a hands-on individual contributor role for someone who can identify a problem, make a sound technical decision, and carry the solution through implementation.
Responsibilities
- In your first 30 days, you will complete knowledge transfer across Lyte’s core IT systems, operating practices, vendors, and active projects. You will begin independently resolving recurring issues and establish working relationships with Engineering and other key partners.
- Within your first 90 days, you will take ownership of assigned systems and deliver a meaningful milestone on a priority initiative, such as the Jamf MDM rollout, identity and endpoint improvements, and infrastructure setup for new offices and sites.
- Within six months, you will strengthen the company’s identity and endpoint security by improving controls across Microsoft 365, Entra ID, Intune, Jamf, MFA, Conditional Access, RBAC, encryption, patching, EDR, and vulnerability remediation.
- You will improve infrastructure reliability and supportability across Linux systems, firewalls, office networks, VPN access, cloud services, storage, backups, and business-continuity capabilities. Improvements will be documented and measured against priorities agreed with the IT leadership team.
- You will reduce avoidable cost and manual work by improving visibility into cloud, SaaS, licensing, compute, and storage spend and by automating high-value IT and security workflows using Bash, PowerShell, Python, or similar tools.
- By the end of your first year, the systems you own should be more secure, better documented, easier to operate, and less dependent on individual knowledge. You will have helped reduce priority risks, improve audit readiness, and give the company a stronger foundation for continued growth.
Requirements
- Demonstrated ownership of Microsoft 365, Entra ID, and Intune environments, including identity lifecycle management, MFA, Conditional Access, RBAC, Exchange, SharePoint, or Teams
- Hands-on administration and troubleshooting of Linux systems, including hardening, patching, access controls, monitoring, and availability
- Experience configuring and supporting enterprise networking, firewalls, segmentation, switching, VPNs, and remote access
- Ownership of mixed macOS, Windows, or Linux endpoint environments using platforms such as Intune, Jamf, EDR, encryption, and vulnerability-management tools
- Evidence of independently delivering infrastructure or security projects from problem identification through implementation, documentation, and operational handoff
Qualifications
- Experience with AWS, Azure, or GCP
- SOC 2 or ISO 27001
- SIEM and logging platforms
- GitLab or CI/CD environments
- AI-tool governance
- GPU or AI/ML infrastructure
- EDA or EPDA environments
- Technology-vendor or licensing negotiations
Skills
- Working automation experience with Bash, PowerShell, Python, or a comparable scripting language
Benefits
- Competitive salary and equity
- Comprehensive medical, dental, and vision coverage
- 401(k) retirement plan
- Flexible vacation and time-off policy
- Collaborative, fast-paced, and inclusive work environment
- Opportunity to work on cutting-edge technologies with a highly cross-functional team
Pay
The Pay Range For This Role Is 150,000 - 230,000 USD per year (Bay Area, CA)
Schedule
This individual contributor role is based in Lyte’s Sunnyvale office five days per week and may occasionally require evening or weekend work for maintenance, deployments, or urgent incidents.
Check for any missing info: The "How
for prose. We must not invent or summarize away detail. So we need to keep specifics like technologies, timeframes, etc. We need to output only HTML fragment, no /, no markdown fences. Let's structure:
About the role
About Lyte Lyte builds perception systems for Physical AI operating in complex environments. The company combines custom silicon, integrated sensors, and software into a unified platform for robotics, mobility, and next-generation automation. Lyte is headquartered in Sunnyvale, California, with a global presence. For more information, visit www.lyte.ai If you’re excited about building impactful technology in a dynamic, hands-on environment, we’d love to hear from you! Why This Role Exists Lyte is building perception systems that combine custom silicon, sensors, and software for robotics, mobility, and next-generation automation. As the company grows, its internal technology environment must become more secure, reliable, scalable, and cost-effective without adding unnecessary complexity. This role will help turn a growing IT environment into a well-controlled, supportable operation. You will work directly across identity, endpoints, Linux systems, cloud infrastructure, networking, security, vendors, and compliance. This is a hands-on individual contributor role for someone who can identify a problem, make a sound technical decision, and carry the solution through implementation.
But we might split into two paragraphs? It's okay. Next: Responsibilities (Responsibilities
) with list of accomplishments. We need to list bullet points for each accomplishment: first 30 days, first 90 days, six months, etc. Use- .
We need to preserve all details: "In your first 30 days, you will complete knowledge transfer across Lyte’s core IT systems, operating practices, vendors, and active projects. You will begin independently resolving recurring issues and establish working relationships with Engineering and other key partners." etc.
We'll create list items.
Next: Requirements (
Requirements
) maybe combine What We Need and Preferred? But we have separate sections: Requirements (mandatory) and Qualifications (preferred). The instruction says use headings like Requirements, Qualifications, Skills. So we can have:Requirements
with list of mandatory items from "What We Need". Use- .
Qualifications
with preferred items from "Preferred, But Not Required". Use- .
Skills
maybe we can include automation experience? But that's already in Requirements. Could also include scripting languages. But we might not need separate Skills if covered. However instruction says prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include all if they have content. We have content for Requirements (mandatory), Qualifications (preferred), Skills (maybe we can list scripting languages as skills). But the mandatory already includes automation experience with Bash, PowerShell, Python. That's a skill. Could still have Skills section listing those. But to avoid duplication, maybe we put scripting languages under Skills, and other mandatory under Requirements. However the mandatory list includes many items; we could split. Better: Requirements: list of mandatory items (ownership of M365, Entra ID, Intune; Linux admin; networking; endpoint ownership; delivering projects). Qualifications: preferred items (AWS/Azure/GCP; SOC 2; SIEM; GitLab; AI-tool governance; GPU/AI/ML; EDA/EPDA; vendor negotiations). Skills: automation experience with Bash, PowerShell, Python, or comparable scripting language. That seems reasonable. Next Benefits (Benefits
) list bullet points. Pay (Pay
) maybe just a paragraph with pay range. Schedule (Schedule
) paragraph about office five days per week, occasional evening/weekend work. We must not include filler like "commensurate with experience". Not present. Now ensure we don't repeat job title. Not needed. Now produce HTML. Check for any duplicated lines: The posting includes some repeated phrases like "Lyte builds perception systems..." appears twice? Actually first paragraph includes that, then later "Why This Role Exists" repeats similar. We need to preserve all substantive information, but we can avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must deduplicate. But we could keep both; duplication is okay as it's preserving. However we might want to avoid repeating same sentences exactly; but it's okay. We'll include both. Now craft HTML. Let's write:About the role
About Lyte Lyte builds perception systems for Physical AI operating in complex environments. The company combines custom silicon, integrated sensors, and software into a unified platform for robotics, mobility, and next-generation automation. Lyte is headquartered in Sunnyvale, California, with a global presence. For more information, visit www.lyte.ai If you’re excited about building impactful technology in a dynamic, hands-on environment, we’d love to hear from you! Why This Role Exists Lyte is building perception systems that combine custom silicon, sensors, and software for robotics, mobility, and next-generation automation. As the company grows, its internal technology environment must become more secure, reliable, scalable, and cost-effective without adding unnecessary complexity. This role will help turn a growing IT environment into a well-controlled, supportable operation. You will work directly across identity, endpoints, Linux systems, cloud infrastructure, networking, security, vendors, and compliance. This is a hands-on individual contributor role for someone who can identify a problem, make a sound technical decision, and carry the solution through implementation.
Responsibilities
- In your first 30 days, you will complete knowledge transfer across Lyte’s core IT systems, operating practices, vendors, and active projects. You will begin independently resolving recurring issues and establish working relationships with Engineering and other key partners.
- Within your first 90 days, you will take ownership of assigned systems and deliver a meaningful milestone on a priority initiative, such as the Jamf MDM rollout, identity and endpoint improvements, and infrastructure setup for new offices and sites.
- Within six months, you will strengthen the company’s identity and endpoint security by improving controls across Microsoft 365, Entra ID, Intune, Jamf, MFA, Conditional Access, RBAC, encryption, patching, EDR, and vulnerability remediation.
- You will improve infrastructure reliability and supportability across Linux systems, firewalls, office networks, VPN access, cloud services, storage, backups, and business-continuity capabilities. Improvements will be documented and measured against priorities agreed with the IT leadership team.
- You will reduce avoidable cost and manual work by improving visibility into cloud, SaaS, licensing, compute, and storage spend and by automating high-value IT and security workflows using Bash, PowerShell, Python, or similar tools.
- By the end of your first year, the systems you own should be more secure, better documented, easier to operate, and less dependent on individual knowledge. You will have helped reduce priority risks, improve audit readiness, and give the company a stronger foundation for continued growth.
Requirements
- Demonstrated ownership of Microsoft 365, Entra ID, and Intune environments, including identity lifecycle management, MFA, Conditional Access, RBAC, Exchange, SharePoint, or Teams
- Hands-on administration and troubleshooting of Linux systems, including hardening, patching, access controls, monitoring, and availability
- Experience configuring and supporting enterprise networking, firewalls, segmentation, switching, VPNs, and remote access
- Ownership of mixed macOS, Windows, or Linux endpoint environments using platforms such as Intune, Jamf, EDR, encryption, and vulnerability-management tools
- Evidence of independently delivering infrastructure or security projects from problem identification through implementation, documentation, and operational handoff
Qualifications
- Experience with AWS, Azure, or GCP
- SOC 2 or ISO 27001
- SIEM and logging platforms
- GitLab or CI/CD environments
- AI-tool governance
- GPU or AI/ML infrastructure
- EDA or EPDA environments
- Technology-vendor or licensing negotiations
Skills
- Working automation experience with Bash, PowerShell, Python, or a comparable scripting language
Benefits
- Competitive salary and equity
- Comprehensive medical, dental, and vision coverage
- 401(k) retirement plan
- Flexible vacation and time-off policy
- Collaborative, fast-paced, and inclusive work environment
- Opportunity to work on cutting-edge technologies with a highly cross-functional team
Pay
The Pay Range For This Role Is 150,000 - 230,000 USD per year (Bay Area, CA)
Schedule
This individual contributor role is based in Lyte’s Sunnyvale office five days per week and may occasionally require evening or weekend work for maintenance, deployments, or urgent incidents.
Check for any missing info: The "How
- .
- .