AI Product Design Engineer, Interface & Experience
Information Security Media Group (ISMG) · New York, NY · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes: About Us (company description) but not "About the role". There's "The Opportunity" describing role. Could map to "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content.
We have:
- About Us (company description) could be considered "About the role"? Not exactly. But we could treat "About Us" as "About the role"? Might be better to create a section "About the role" with content from "The Opportunity" and maybe "About Us"? However "About Us" is company overview, not role. The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID etc. It doesn't forbid using About Us as a section heading if we map to "About the role". Probably we should include a section "About the role" containing the description of the opportunity and what you'll do? Actually "What You'll Do" is responsibilities. So "About the role" could be a brief summary: The Opportunity paragraph. We'll include that.
Responsibilities: "What You'll Do" bullet points (though they are paragraphs). We'll extract each sentence as list items.
Requirements: maybe "What You Bring To The Table" includes experience, skills, etc. Could split into Requirements and Qualifications and Skills. But we need to avoid thin sections. Could combine into one "Requirements" section with list.
Qualifications: maybe not separate.
Skills: could be separate but we might just have one section "Requirements" covering experience, technical skills, etc.
Benefits, Pay, Schedule: not provided. So we omit those sections.
We must not include boilerplate like "Apply now" etc. Remove navigation, EEO, etc. The posting ends with "👉 Ready to be part of something bigger? Apply now or visit ISMG.io to learn more!" That's application instruction, should be removed.
Also remove emojis? Probably keep text but emojis may be considered noise; we can strip them.
We need to preserve all substantive information. So we need to include company description, opportunity, responsibilities, qualifications/skills.
Let's parse content:
About Us:
"ISMG is a global intelligence firm and media powerhouse, leading the way in cybersecurity, enterprise IT, and digital transformation. With 10+ brands, 38 digital media properties, and over 400 premier events annually—ISMG connects a network of over 2M executives, decision-makers, and innovators with the insights and opportunities they need to stay ahead. Apollo is the proprietary creation of ISMG's AI & Innovation team. It's an internal hub of AI-powered applications and workflows, custom-built for our various business units (Editorial, Marketing, Events, Sales, HR, etc.). It streamlines operations with intelligent automation and data-driven insights, and transforms how teams access critical cybersecurity insights by exclusively leveraging ISMG-verified sources—so teams move faster with confidence."
The Opportunity:
"ISMG is building a portfolio of AI-native intelligence products — audience analytics reporting, an AI-generated daily cybersecurity newscast, and a sourced Q&A system built on our conference archive. Every one of them is currently limited by the same thing: the interface. We have the pipelines, the data warehouse, and the models. What we do not have is anyone who owns what a CISO actually sees. You would be that person. This is a founding design-engineering role on a small team, with unusual latitude and unusual visibility. What you ship goes in front of security executives, ISMG’s editorial organization, and enterprise clients."
What You'll Do (list):
- Own the front-end and interaction design for the team’s AI products end to end — from stakeholder conversation to deployed application.
- Conduct lightweight user research, prototype workflows, and validate designs with clients and internal users before and after release.
- Translate complex AI and reporting workflows into clear information architecture and task-oriented experiences.
- Solve the interaction problems specific to AI output: how confidence is communicated, how citations surface, how a reviewer approves or rejects a machine-generated draft, and how uncertainty reads without eroding trust.
- Build quickly with AI-assisted development tooling, then rehome that output into ISMG’s Azure environment — Microsoft Entra ID authentication, App Service or Static Web Apps, and Azure DevOps pipelines.
- Establish the design system this team does not currently have: components, states, data visualization patterns, and an accessibility baseline.
- Build and maintain Figma libraries, design tokens, and a practical design-to-code handoff process.
- Design for enterprise realities: role-based access, dense data, audit trails, exports, responsive behavior, and accessible interaction patterns.
- Instrument everything through Application Insights and bring adoption and usage data back into the roadmap.
- Partner directly with the AI Innovation Manager on API contracts and data access, and with business units across editorial, marketing, and sales on what they actually need.
What You Bring To The Table:
- 2 to 5 years of experience in a UI/UX role building production web interfaces, or a relevant level of skills displayed through a personal project portfolio.
- Enterprise Applications Design: Experience designing B2B applications with complex permissions, data-heavy workflows, and high expectations around trust, clarity, and reliability.
- UI/UX: Strong understanding of user flows, interaction patterns, responsive UX, and intuitive interface design.
- User-Centered Discovery: Experience interviewing users, testing prototypes, synthesizing feedback, and changing direction when evidence warrants it.
- Frontend: Advanced proficiency in Next.js, React, TypeScript, and semantic HTML/CSS.
- Design Systems: Strong expertise in Tailwind CSS, design tokens, themes, and dark mode.
- Design Judgment: Can articulate why a layout works, not simply reproduce one you have seen.
- AI Workflow: Experience using Claude for prototyping and Claude Code with VS Code/Cursor to turn UI/UX requirements into production-ready frontend code.
- Azure Deployment: Prior work experience or clear evidence in the ability to quickly learn. Microsoft Entra ID and MSAL authentication is a meaningful plus.
- Data Visualization: Report building capability using Recharts, D3, Plotly, or similar.
- Accessibility & Performance: Strong knowledge of WCAG, ARIA, and Core Web Vitals.
- Attention to Detail: Strong eye for spacing, typography, motion, responsiveness, and visual issues AI-generated code may miss.
Nice to Have (we could include as part of Skills or separate but it's optional; we could include as part of Skills but it's "Nice to Have". Might be okay to include as part of Skills but we could omit as it's not required. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Nice to Have is specific content, we could include under Skills or a separate "Nice to Have" but not in the list of allowed headings. The allowed headings are limited to those eight. So we should incorporate Nice to Have into Skills or Requirements. Probably incorporate into Skills.
Thus we will have sections:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content.
We have:
- About Us (company description) could be considered "About the role"? Not exactly. But we could treat "About Us" as "About the role"? Might be better to create a section "About the role" with content from "The Opportunity" and maybe "About Us"? However "About Us" is company overview, not role. The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID etc. It doesn't forbid using About Us as a section heading if we map to "About the role". Probably we should include a section "About the role" containing the description of the opportunity and what you'll do? Actually "What You'll Do" is responsibilities. So "About the role" could be a brief summary: The Opportunity paragraph. We'll include that.
Responsibilities: "What You'll Do" bullet points (though they are paragraphs). We'll extract each sentence as list items.
Requirements: maybe "What You Bring To The Table" includes experience, skills, etc. Could split into Requirements and Qualifications and Skills. But we need to avoid thin sections. Could combine into one "Requirements" section with list.
Qualifications: maybe not separate.
Skills: could be separate but we might just have one section "Requirements" covering experience, technical skills, etc.
Benefits, Pay, Schedule: not provided. So we omit those sections.
We must not include boilerplate like "Apply now" etc. Remove navigation, EEO, etc. The posting ends with "👉 Ready to be part of something bigger? Apply now or visit ISMG.io to learn more!" That's application instruction, should be removed.
Also remove emojis? Probably keep text but emojis may be considered noise; we can strip them.
We need to preserve all substantive information. So we need to include company description, opportunity, responsibilities, qualifications/skills.
Let's parse content:
About Us:
"ISMG is a global intelligence firm and media powerhouse, leading the way in cybersecurity, enterprise IT, and digital transformation. With 10+ brands, 38 digital media properties, and over 400 premier events annually—ISMG connects a network of over 2M executives, decision-makers, and innovators with the insights and opportunities they need to stay ahead. Apollo is the proprietary creation of ISMG's AI & Innovation team. It's an internal hub of AI-powered applications and workflows, custom-built for our various business units (Editorial, Marketing, Events, Sales, HR, etc.). It streamlines operations with intelligent automation and data-driven insights, and transforms how teams access critical cybersecurity insights by exclusively leveraging ISMG-verified sources—so teams move faster with confidence."
The Opportunity:
"ISMG is building a portfolio of AI-native intelligence products — audience analytics reporting, an AI-generated daily cybersecurity newscast, and a sourced Q&A system built on our conference archive. Every one of them is currently limited by the same thing: the interface. We have the pipelines, the data warehouse, and the models. What we do not have is anyone who owns what a CISO actually sees. You would be that person. This is a founding design-engineering role on a small team, with unusual latitude and unusual visibility. What you ship goes in front of security executives, ISMG’s editorial organization, and enterprise clients."
What You'll Do (list):
- Own the front-end and interaction design for the team’s AI products end to end — from stakeholder conversation to deployed application.
- Conduct lightweight user research, prototype workflows, and validate designs with clients and internal users before and after release.
- Translate complex AI and reporting workflows into clear information architecture and task-oriented experiences.
- Solve the interaction problems specific to AI output: how confidence is communicated, how citations surface, how a reviewer approves or rejects a machine-generated draft, and how uncertainty reads without eroding trust.
- Build quickly with AI-assisted development tooling, then rehome that output into ISMG’s Azure environment — Microsoft Entra ID authentication, App Service or Static Web Apps, and Azure DevOps pipelines.
- Establish the design system this team does not currently have: components, states, data visualization patterns, and an accessibility baseline.
- Build and maintain Figma libraries, design tokens, and a practical design-to-code handoff process.
- Design for enterprise realities: role-based access, dense data, audit trails, exports, responsive behavior, and accessible interaction patterns.
- Instrument everything through Application Insights and bring adoption and usage data back into the roadmap.
- Partner directly with the AI Innovation Manager on API contracts and data access, and with business units across editorial, marketing, and sales on what they actually need.
What You Bring To The Table:
- 2 to 5 years of experience in a UI/UX role building production web interfaces, or a relevant level of skills displayed through a personal project portfolio.
- Enterprise Applications Design: Experience designing B2B applications with complex permissions, data-heavy workflows, and high expectations around trust, clarity, and reliability.
- UI/UX: Strong understanding of user flows, interaction patterns, responsive UX, and intuitive interface design.
- User-Centered Discovery: Experience interviewing users, testing prototypes, synthesizing feedback, and changing direction when evidence warrants it.
- Frontend: Advanced proficiency in Next.js, React, TypeScript, and semantic HTML/CSS.
- Design Systems: Strong expertise in Tailwind CSS, design tokens, themes, and dark mode.
- Design Judgment: Can articulate why a layout works, not simply reproduce one you have seen.
- AI Workflow: Experience using Claude for prototyping and Claude Code with VS Code/Cursor to turn UI/UX requirements into production-ready frontend code.
- Azure Deployment: Prior work experience or clear evidence in the ability to quickly learn. Microsoft Entra ID and MSAL authentication is a meaningful plus.
- Data Visualization: Report building capability using Recharts, D3, Plotly, or similar.
- Accessibility & Performance: Strong knowledge of WCAG, ARIA, and Core Web Vitals.
- Attention to Detail: Strong eye for spacing, typography, motion, responsiveness, and visual issues AI-generated code may miss.
Nice to Have (we could include as part of Skills or separate but it's optional; we could include as part of Skills but it's "Nice to Have". Might be okay to include as part of Skills but we could omit as it's not required. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Nice to Have is specific content, we could include under Skills or a separate "Nice to Have" but not in the list of allowed headings. The allowed headings are limited to those eight. So we should incorporate Nice to Have into Skills or Requirements. Probably incorporate into Skills.
Thus we will have sections:
About the role
with content from The Opportunity (maybe also About Us? but we can include company description as part of About the role? Might be better to have a separate "About the company" but not allowed. So we incorporate company description into About the role? The instruction says About the role heading for e.g. About the role. We'll put the opportunity description there.
Responsibilities
with ul list of the What You'll Do items.
Requirements
with ul list of What You Bring To The Table items (including nice to have). Could also split into Skills but we can keep as Requirements.
We should not include Benefits, Pay, Schedule.
We need to output only HTML fragment, no extra text.
Let's craft.
We need to ensure we preserve all substantive information: include company description? If we only put opportunity, we lose About Us description. That is substantive. Should we include it somewhere? Could we put it in About the role as a preamble? The About the role section could contain both company overview and opportunity. That would preserve it.
Thus About the role
containing both ISMG description and opportunity paragraph. Let's write:
About the role
ISMG is a global intelligence firm and media powerhouse, leading the way in cybersecurity, enterprise IT, and digital transformation. With 10+ brands, 38 digital media properties, and over 400 premier events annually—ISMG connects a network of over 2M executives, decision-makers, and innovators with the insights and opportunities they need to stay ahead. Apollo is the proprietary creation of ISMG's AI & Innovation team. It's an internal hub of AI-powered applications and workflows, custom-built for our various business units (Editorial, Marketing, Events, Sales, HR, etc.). It streamlines operations with intelligent automation and data-driven insights, and transforms how teams access critical cybersecurity insights by exclusively leveraging ISMG-verified sources—so teams move faster with confidence. ISMG is building a portfolio of AI-native intelligence products — audience analytics reporting, an AI-generated daily cybersecurity newscast, and a sourced Q&A system built on our conference archive. Every one of them is currently limited by the same thing: the interface. We have the pipelines, the data warehouse, and the models. What we do not have is anyone who owns what a CISO actually sees. You would be that person. This is a founding design-engineering role on a small team, with unusual latitude and unusual visibility. What you ship goes in front of security executives, ISMG’s editorial organization, and enterprise clients.
Then Responsibilities- ... each bullet. We need to convert each sentence into list items. Let's list them: 1. Own the front-end and interaction design for the team’s AI products end to end — from stakeholder conversation to deployed application. 2. Conduct lightweight user research, prototype workflows, and validate designs with clients and internal users before and after release. 3. Translate complex AI and reporting workflows into clear information architecture and task-oriented experiences. 4. Solve the interaction problems specific to AI output: how confidence is communicated, how citations surface, how a reviewer approves or rejects a machine-generated draft, and how uncertainty reads without eroding trust. 5. Build quickly with AI-assisted development tooling, then rehome that output into ISMG’s Azure environment — Microsoft Entra ID authentication, App Service or Static Web Apps, and Azure DevOps pipelines. 6. Establish the design system this team does not currently have: components, states, data visualization patterns, and an accessibility baseline. 7. Build and maintain Figma libraries, design tokens, and a practical design-to-code handoff process. 8. Design for enterprise realities: role-based access, dense data, audit trails, exports, responsive behavior, and accessible interaction patterns. 9. Instrument everything through Application Insights and bring adoption and usage data back into the roadmap. 10. Partner directly with the AI Innovation Manager on API contracts and data access, and with business units across editorial, marketing, and sales on what they actually need. Now Requirements: list items from What You Bring To The Table plus Nice to Have. Let's list each bullet: - 2 to 5 years of experience in a UI/UX role building production web interfaces, or a relevant level of skills displayed through a personal project portfolio. - Enterprise Applications Design: Experience designing B2B applications with complex permissions, data-heavy workflows, and high expectations around trust, clarity, and reliability. - UI/UX: Strong understanding of user flows, interaction patterns, responsive UX, and intuitive interface design. - User-Centered Discovery: Experience interviewing users, testing prototypes, synthesizing feedback, and changing direction when evidence warrants it. - Frontend: Advanced proficiency in Next.js, React, TypeScript, and semantic HTML/CSS. - Design Systems: Strong expertise in