Infrastructure Security Analyst – macOS Endpoint Security
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting has:
- Overview section (about State Farm)
- Responsibilities section (What You'll Do)
- Qualifications section (What We're Looking For, Experience That Would Set You Apart, What Will Help You Succeed)
- Why Join Our Team? section
- Benefits section (Our Benefits) with detailed benefits and pay information
I need to structure this into appropriate sections. The job title is "Infrastructure Security Analyst" (mentioned in the responsibilities section). I should not repeat it as a heading.
Sections I'll create:
1. About the role (from Overview)
2. Responsibilities (from What You'll Do)
3. Qualifications (from What We're Looking For, Experience That Would Set You Apart, What Will Help You Succeed)
4. Benefits (from Our Benefits, including pay info)
The pay information is detailed: "Potential starting salary range: $100,000 - $142,000" etc. So I should include a Pay section or include it in Benefits. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay and benefits, so I can include them. I'll include Pay as a subsection of Benefits or separate. Since the rules mention Pay as a possible heading, I'll create a Pay section.
Also, there's schedule info: "compensation is based on our standard 38:45-hour work week" - that's schedule info. So I could include a Schedule section.
But the rules say "Prefer a few substantive sections over many thin ones." I'll combine pay and schedule into Benefits or have separate sections. I think I'll create a Benefits section that includes pay and schedule details.
Let me structure:
About the role
...overview text...
Responsibilities
- ...each bullet from What You'll Do...
Qualifications
...intro text...
- ...qualifications and experience bullets...
Experience that would set you apart:
- ...those bullets...
What will help you succeed:
- ...those bullets...
Benefits
...why join our team text...
...benefits overview...
Pay
(but rules say use h3 for section headings, not h4. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Pay and Schedule are also h3 level. But they are subsections of Benefits? The example list includes them as separate headings. I'll make them separate h3 sections.
But the posting has "Our Benefits" section that includes pay details. I could make "Benefits" and "Pay" separate h3 sections. However, the pay info is part of the benefits section. I'll create a Benefits section with the benefits list, and a Pay section with the salary details. Also a Schedule section for the work week info.
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states all three. So I'll create three sections: Benefits, Pay, Schedule.
But the benefits section includes a lot of prose and lists. I'll structure accordingly.
Let me extract the content.
First, Overview: "Being good neighbors – helping people, investing in our communities, and making the world a better place – is who we are at State Farm. It is at the core of how we operate and the reason for our success. We're moving with urgency to become a Next Gen Good Neighbor, with technology that strengthens human connections and enhances the customer experience. As an employee, you'll spend less time navigating systems and more time applying judgment, empathy, and expertise in the moments that matter most."
That's About the role.
Responsibilities: "At State Farm, we believe strong security and a great employee experience should go hand in hand. We're looking for a motivated, curious, and technically skilled Infrastructure Security Analyst to join our macOS Security team. You'll help protect and modernize our growing enterprise Mac environment, strengthen endpoint security, and develop innovative solutions that make technology safer, simpler, and more reliable for the people who depend on it. We're looking for someone who enjoys solving challenging technical problems, learning new technologies, collaborating across teams, and turning great ideas into practical solutions.
What You'll Do
- Engineer and strengthen endpoint security. Implement, configure, maintain, and troubleshoot security controls that protect enterprise macOS devices.
- Modernize device management. Support and improve solutions using Jamf Pro, Microsoft Intune, Microsoft Entra ID, and related Apple management technologies.
- Protect against emerging threats. Support Microsoft Defender for Endpoint, investigate vulnerabilities, implement remediation, and verify security effectiveness.
- Automate and innovate. Develop scripts and automated solutions that improve efficiency, eliminate repetitive work, and strengthen operational consistency.
- Solve complex technical challenges. Investigate issues involving macOS, security applications, network connectivity, authentication, and device configuration.
- Advance identity and access security. Collaborate on certificate-based authentication, privileged access management, and secure access solutions.
- Deliver an exceptional Mac experience. Balance strong security protections with usability, reliability, and minimal disruption for employees.
- Collaborate across the enterprise. Partner with engineering, infrastructure, security, and technology teams to implement sustainable solutions.
- Embrace emerging technology. Explore opportunities to leverage AI, automation, and modern engineering practices to improve how we work."
I'll make each bullet a list item.
Qualifications: "What We're Looking For
We're seeking a hands-on technical professional with experience in infrastructure engineering, endpoint security, or enterprise device management. Qualifications and experience:
- Hands-on experience configuring, administering, securing, or troubleshooting macOS or other enterprise operating systems.
- Experience implementing or supporting endpoint security controls, endpoint management platforms, vulnerability remediation, or endpoint detection and response solutions.
- Experience with scripting or automation using Bash, Python, PowerShell, or similar technologies.
- Strong troubleshooting and analytical skills, including the ability to identify root causes and implement effective solutions.
- Understanding of security fundamentals, including system hardening, access management, endpoint protection, and compliance.
- Ability to work collaboratively across technical teams and clearly communicate problems, solutions, and outcomes.
Experience That Would Set You Apart
- Hands-on experience with Jamf Pro, Jamf Protect, Microsoft Defender for Endpoint, or Microsoft Intune, particularly in macOS environments.
- Familiarity with Apple device management, macOS security frameworks, configuration profiles, or enterprise deployments.
- Experience with Microsoft Entra ID, Conditional Access, certificate-based authentication, or privileged access management.
- Experience using Git, APIs, CI/CD pipelines, and configuration management tools.
- Experience troubleshooting network security, VPN connectivity, endpoint compliance, or security application performance.
- Experience designing, deploying, or improving automated security solutions at enterprise scale.
- Familiarity with AI-assisted engineering or other emerging security technologies.
What Will Help You Succeed
Beyond technical knowledge, we're looking for someone who brings energy, ownership, creativity, and a desire to continuously improve. You'll thrive on our team if you:
- Are naturally curious and enjoy learning how things work.
- Take initiative and follow through, even when challenges are unfamiliar.
- Enjoy solving problems rather than simply identifying them.
- Look for opportunities to simplify processes and automate repetitive work.
- Build strong relationships and believe collaboration leads to better outcomes.
- Understand that security solutions must work for both the organization and its employees.
- Bring fresh perspectives, challenge assumptions constructively, and help others succeed.
- Are motivated to grow your expertise and contribute to a collaborative, high-performing team.
You don't need to know every technology listed. We value strong technical fundamentals, demonstrated problem-solving ability, learning agility, and a willingness to take on new challenges."
I'll structure Qualifications with subsections: Required Qualifications, Preferred Qualifications, Success Factors (or similar). But the rules say use h3 for section headings, not subsections. I could keep it as one Qualifications section with multiple lists and prose.
Why Join Our Team?: "You'll be part of a team helping shape the future of enterprise macOS security at State Farm. Our work spans endpoint protection, device management modernization, vulnerability remediation, identity and access security, and automation. We believe in supporting one another, sharing knowledge, embracing new ideas, and creating an environment where people can continuously learn and grow. Our focus is simple: Simplify. Strengthen. Sustain. We want to simplify how security works, strengthen our protection of the enterprise, and build sustainable solutions that support State Farm's evolving technology needs. If you're passionate about cybersecurity, enjoy solving technical challenges, and want to make a meaningful difference, we'd love to hear from you. Serving more customers, securely, forever."
This could be part of About the role or a separate section. I'll include it in About the role or as a separate "Why join our team" section. The rules don't list that as a standard heading, but I can use h3 for it. However, "Prefer a few substantive sections over many thin ones." I'll merge it into About the role or Benefits.
Benefits: "Our Benefits
Because work-life balance is a priority at State Farm, compensation is based on our standard 38:45-hour work week!
Potential starting salary range: $100,000 - $142,000
Starting salary will be based on skills, background, and experience
High end of the range limited to applicants with significant relevant experience
Potential yearly incentive pay up to 15% of base salary
At State Farm, we offer more than just a paycheck. Check out our suite of benefits designed to give you the flexibility you need to take care of you and your family!
Get Paid! On top of our competitive pay, you are eligible for an annual raise and bonus.
Stay Well! Focus on you and your family’s health with our robust health and wellbeing programs. State Farm pays most of your healthcare premium, and we offer multiple healthcare plan options, including a high deductible plan. All medical plans provide 100% coverage for in-network preventative care, AND you and your family have access to vision, dental, telemedicine, 24/7 mental health professionals, and much more!
Develop and Grow! Take advantage of educational benefits like industry leading training programs, top-notch tuition assistance programs, employee resource groups, and mentoring.
Plan Ahead! Plan for those big moments in life with benefits like fertility/IVF/adoption assistance, college coaching, national discount programs, interactive monthly financial workshops, free financial coaching, and more. You can also start a savings account or consider financing through our State Farm Federal Credit Union!
Take a Little “You” Time! You
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Overview section (about State Farm) - Responsibilities section (What You'll Do) - Qualifications section (What We're Looking For, Experience That Would Set You Apart, What Will Help You Succeed) - Why Join Our Team? section - Benefits section (Our Benefits) with detailed benefits and pay information I need to structure this into appropriate sections. The job title is "Infrastructure Security Analyst" (mentioned in the responsibilities section). I should not repeat it as a heading. Sections I'll create: 1. About the role (from Overview) 2. Responsibilities (from What You'll Do) 3. Qualifications (from What We're Looking For, Experience That Would Set You Apart, What Will Help You Succeed) 4. Benefits (from Our Benefits, including pay info) The pay information is detailed: "Potential starting salary range: $100,000 - $142,000" etc. So I should include a Pay section or include it in Benefits. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay and benefits, so I can include them. I'll include Pay as a subsection of Benefits or separate. Since the rules mention Pay as a possible heading, I'll create a Pay section. Also, there's schedule info: "compensation is based on our standard 38:45-hour work week" - that's schedule info. So I could include a Schedule section. But the rules say "Prefer a few substantive sections over many thin ones." I'll combine pay and schedule into Benefits or have separate sections. I think I'll create a Benefits section that includes pay and schedule details. Let me structure:
About the role
...overview text...
Responsibilities
- ...each bullet from What You'll Do...
Qualifications
...intro text...
- ...qualifications and experience bullets...
Experience that would set you apart:
- ...those bullets...
What will help you succeed:
- ...those bullets...
Benefits
...why join our team text...
...benefits overview...