Cybersecurity Engineer
About the role
with paragraphs. - "About Dell Technologies — ISG Developer Experience": This is about company context. Could be part of About the role or separate? The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. Responsibilities: The bullet list under "What You'll Achieve" includes responsibilities. So we can put those underResponsibilities
with- .
Requirements: The "Essential Requirements" list. Could be Requirements heading.
Qualifications: The "Desirable Requirements" list could be Qualifications.
Skills: Not explicitly listed; maybe we can combine some skills from requirements? But we should only create Skills section if there is specific content. There's no separate skills list; we could omit Skills.
Benefits: There's a "Benefits And Perks Of Working At Dell Technologies" paragraph referencing MyWellatDell.com. That's benefits content. So we can include Benefits section with that paragraph.
Pay: There's compensation range: $196,000 to $269,500. So Pay section with that.
Schedule: Not mentioned. So omit Schedule.
Also need to include maybe "About the role" includes the initial "Why This Role" and maybe some of the Dell description. We'll keep substantive info.
We must not repeat job title. Must not include metadata like location (Hopkinton MA) maybe? It's part of posting but not a heading; we can include as a short paragraph maybe under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is minor metadata; we can include as a short p. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc. Remove that. Also remove "Take the First Step Towards Your Dream Career" maybe? That's generic; but it's part of the posting but not boilerplate? It's a call to action; maybe considered application instructions? It says "Take the First Step Towards Your Dream Career". Could be considered fluff; but it's not a list. Might be okay to keep? The instruction: remove duplicated lines, application instructions. That phrase is not an instruction to apply; it's motivational. Might keep but could be considered boilerplate. Safer to drop it? It's not exactly application instruction. I'd keep it as part of About the role? But it's generic. I'd drop it to keep only substantive. Also remove "Join us and help build the future..." etc. That's also generic but maybe part of About the role. Might keep as it's substantive about mission. However it's somewhat fluff. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the descriptive paragraphs that convey role context. The "Join us and help build the future..." is generic but still part of posting; it's not boilerplate like EEO. I'd keep it. Now produce HTML. Structure:
About the role
Why This Role ... (the paragraph).
About Dell Technologies — ISG Developer Experience ... (the paragraph).
Maybe also include location short p:Location: Hopkinton, MA
but we decided to fold minor metadata into short p or drop. Could include as short p. Then Responsibilities:Responsibilities
- Develop and manage the agent lifecycle framework, including agent versioning, testing, validation, security review readiness, deployment processes, and release management within the enterprise agent registry
- Build and maintain shared services, reusable frameworks, developer tooling, and cross-platform integrations that accelerate adoption of AI agents while ensuring consistency, security, and compliance across product and engineering teams
- Partner closely with Product Security, Cybersecurity, Legal, Risk, Compliance, and Infrastructure teams to incorporate security requirements and controls into agentic development workflows and platforms
- Collaborate with cross-functional stakeholders to identify and address AI-specific security risks, including prompt injection, data exposure, agent permissions, secure tool usage, and external integrations
- Define, implement, and maintain standards for knowledge base content, metadata, structure, accessibility, and access controls to ensure trusted and secure inputs for agentic systems and workflows
- Drive engineering best practices across the agentic ecosystem, including automation, testing, observability, reliability, security-by-design principles, and continuous improvement of platform performance and developer experience
Requirements
- 10+ years in a software engineering, platform engineering, security engineering, or related technical leadership role
- Strong hands-on experience with AI-assisted software development, LLMs, agentic systems, AI development platforms, and modern software engineering practices
- Demonstrated experience working with Product Security, Cybersecurity, Risk, Compliance, or Governance teams to deliver secure enterprise software solutions and platforms
- Practical understanding of secure software development practices, threat modeling, identity and access management, application security, and software supply chain security
- Experience working cross-functionally with engineering, product, security, and infrastructure stakeholders
- Demonstrated ability to take ambiguous problems, structure them, and deliver concrete outputs including analyses, prototypes, specifications, or frameworks
- Strong written and verbal communication skills, with the ability to translate technical complexity into clear documentation for both technical and non-technical audiences
Qualifications
- Direct, hands-on experience with agentic development tools and platforms (e.g., Windsurf/Codeium, Claude Code, GitHub Copilot, Cursor, or equivalent)
- Experience evaluating, securing, or governing AI applications, copilots, agentic workflows, or enterprise AI platforms
- Familiarity with MCP ecosystems, AI security concepts, LLM token economics, and enterprise AI governance frameworks
- Experience in a large enterprise environment with compliance requirements, security review processes, and non-negotiable human oversight needs
- Background in developer experience, platform engineering, security engineering, or internal developer tooling.
- Experience building dashboards, measurement frameworks, security metrics, or data instrumentation for engineering productivity and risk visibility
- Comfort operating in ambiguity, defining structures and processes where few exist, and creating clarity without waiting for it
Benefits
Your life. Your health. Supported by your benefits. You can explore the overall benefits experience that awaits you as a Dell Technologies team member — right now at MyWellatDell.com
Pay:Pay
The salary range for this position is $196,000 to $269,500.
We should not include Schedule. Make sure no extra text. Output only HTML fragment. Check for any duplicated lines: none. Check for boilerplate removed: EEO etc removed. Check for minor metadata: we omitted location; maybe we should include location as short p under About the role. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So we could include location as short p. Let's add a short p:
Location: Hopkinton, MA
under About the role. Also maybe include "Join us to do the best work of your career and make a profound social impact as Senior Principal Software Security Engineer on our AI Development & Agent Ops team in Hopkinton MA." That's also part of the posting but repeats location and role. Since we already have location and role not repeated as heading, we could incorporate that sentence. But we must not repeat job title as a heading; we can include it in paragraph. However the sentence includes the job title again; but it's okay to include in prose as it's not a heading. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include it in paragraph. Let's incorporate that sentence into About the role paragraph. We have already a paragraph about Why This Role and About Dell Technologies. We could add another paragraph with that sentence. Let's craft About the role section:About the role
Why This Role: This is not a support role. Dell's AI Development & Agents Ops organization is operating at the frontier of what it means to build software with AI — and this individual will be in the engine room making it work. You will partner directly with a VP who is deeply engaged in the work, contribute to shaping how one of the world's largest technology companies builds software, and operate at a scale where your individual contributions have outsized organizational impact. You will also be joining at the right moment: early enough to shape the architecture of the transformation, with enough organizational commitment that the work has real resources and real stakes.
About Dell Technologies — ISG Developer Experience: Dell's Infrastructure Solutions Group is a global leader in Solutions, Storage, Compute, and Networking. The Developer Experience organization within ISG is responsible for developer productivity, tooling, observability, and platform engineering for approximately 9,000 engineers. Our current mandate spans agentic SDLC transformation, AI tooling governance, and the operating model changes required to make AI-assisted development the norm — not the exception. Infrastructure Solutions Group (ISG) builds the products that power infrastructure, solutions, and data management our customers need most. Our teams design and develop the hardware and software that connect infrastructure, accelerate computational workloads, integrate across the stack, protect data continuity, and deliver the platforms, applications, and diagnostics our customers rely on every day at enterprise scale. Some product builders follow the rules. Ours rewrite them. Within ISG, innovation isn't just about creating new technology- it's about challenging assumptions and reimagining how work gets done. Engineers define intent, author precise specifications, and orchestrate AI agents that execute at speed and scale. AI is embedded throughout our development process, helping us move faster, learn quicker, and deliver greater impact. Yet the most important contribution remains uniquely human: deciding what to build, designing how it should work, and applying the judgment needed to earn our customers' trust. When your products power critical infrastructure around the world, that responsibility matters. We move quickly toward the work that matters most. We reward experimentation, encourage bold thinking, and remove unnecessary barriers so great ideas can become reality faster. Our teams embrace a customer-first, first-to-market mindset, transforming rapid feedback into better products and better outcomes. We aren't looking for people who are content with the status quo- we look for builders who question it, improve it, and occasionally rewrite it. If you're energized by solving complex systems challenges, excited to work alongside AI to amplify your impact, and motivated by the opportunity to shape what's next instead of simply maintaining what's been done before, you'll find your place here.
Join us to do the best work of your career and make a profound social impact as Senior Principal Software Security Engineer on our AI Development & Agent Ops team in Hopkinton, MA.
Location: Hopkinton, MA
But note we repeated location twice; maybe we