Senior Systems Engineer
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes "About Grassi" description, job summary, responsibilities, technical responsibilities, qualifications, why Grassi (benefits), compensation info. Need to map to sections.
We need to decide which sections to include based on presence of content.
- About the role: Could be the "Job Summary" paragraph: "We are currently seeking a Senior Systems Engineer to join our team in either our Park Ridge, NJ or Jericho, NY office location. This is a fully onsite position, five days per week in the office. This role offers an exciting opportunity to be part of a dynamic and growing firm." That's about the role. Also maybe include "About Grassi" but that's company description; not required but could be part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with job summary.
- Responsibilities: list of duties from "Responsibilities include, but are not limited to:" bullet list. Also technical responsibilities could be part of responsibilities? Might be separate but we can combine under Responsibilities.
- Requirements: maybe "Qualifications Required" is requirements. Also "Preferred" could be qualifications/skills. The instruction: Use Requirements heading for required qualifications? Could separate Requirements and Qualifications? They list both. We could treat "Qualifications Required" as Requirements, and "Preferred" as Qualifications or Skills. But we have both Qualifications and Skills headings available. Could put required under Requirements, preferred under Qualifications, and maybe Skills separate if we have skill list (like certifications). However we can combine.
- Benefits: from "Why Grassi?" includes benefits package description. Also "Benefits Package:" bullet list.
- Pay: compensation ranges for NY and NJ.
- Schedule: mention "fully onsite position, five days per week in the office." Also maybe after-hours maintenance. So schedule info.
We must not create sections with filler like "commensurate with experience". We have actual content.
We must not include boilerplate like EEO etc. Not present.
We need to output only HTML fragment, no /. Use
headings,
,
- . Ensure we preserve all substantive info.
Let's extract content.
About Grassi description: Could be considered company overview, but not required. Might be omitted as not part of sections? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the About Grassi paragraph somewhere. Where to put? Could be part of About the role? But About the role heading is for role description, not company. However we could include a separate section like "About the Company" but not in allowed headings. The allowed headings list is examples; we could still add other headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should likely stick to those. It also says "include a section ONLY when the posting has real, specific content for it". So we can include any of those headings if we have content. We might not need to include About Grassi if not fitting those headings. But we must preserve all substantive information; if we omit About Grassi, we lose info. Could we incorporate About Grassi into About the role? Possibly as a preamble: "About Grassi" could be considered part of About the role? Not ideal but maybe acceptable. However we could add a heading "About Grassi" as an h3 even though not in list; but instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use h3 for section headings (e.g...). It might be okay to add other headings as long as they are h3. But to be safe, we could incorporate About Grassi into a paragraph under About the role heading, maybe as a brief intro: "About Grassi: ..." That preserves info.
Let's craft:
About the role
About Grassi: After more than 40 years of business growth... (the whole About Grassi paragraph). Then job summary paragraph: "We are currently seeking a Senior Systems Engineer to join our team in either our Park Ridge, NJ or Jericho, NY office location. This is a fully onsite position, five days per week in the office. This role offers an exciting opportunity to be part of a dynamic and growing firm."
That preserves both.
Now Responsibilities: combine the bullet list from "Responsibilities include, but are not limited to:" plus the technical responsibilities subheadings? Could treat technical responsibilities as part of responsibilities. We'll create a
with each responsibility line.
List items:
- Serve as the final service desk escalation point for complex incidents involving Microsoft 365, identity services, secure remote access, endpoint protection, virtual desktop platforms, profile management, printers, security alerts, and firm applications.
- Lead root cause analysis for recurring, high-impact, or deadline-sensitive issues and implement durable corrective actions.
- Support technical delivery for endpoint, application, Microsoft 365, secure access, identity, infrastructure, security improvement, and modernization initiatives.
- Create and maintain configuration standards, operational runbooks, recovery procedures, troubleshooting guides, and knowledge articles.
- Mentor Level 1 and Level 2 personnel, improve escalation quality, and provide practical knowledge transfer.
- Coordinate with vendors, consultants, application owners, security resources, business stakeholders, and IT leadership.
- Identify technical debt, availability risks, capacity constraints, configuration weaknesses, and opportunities for automation or standardization.
- Participate in after-hours maintenance and critical incident response when business needs require it.
Then technical responsibilities could be separate bullet list under same responsibilities or maybe under a subheading but we don't have subheading allowed. Could incorporate as additional list items.
Technical responsibilities list:
- Administer and troubleshoot cloud services, including virtual machines, storage, networking, remote connectivity, monitoring, logging, backup, disaster recovery, and related services.
- Provide advanced support for virtual desktop environments and user profiles, including access, application delivery, printing, performance, capacity, and user experience.
- Administer Microsoft 365, including Exchange Online, Teams, Teams Phone, SharePoint Online, OneDrive, Outlook, Microsoft 365 Apps, Copilot, licensing, mailboxes, groups, and permissions.
- Support identity and access management, including users, groups, enterprise applications, access policies, sign-in issues, and access troubleshooting.
- Assess technical dependencies and business risk before changes and develop implementation, validation, and rollback plans.
- Support secure remote access, DNS, network connectivity, and secure-access platforms.
- Troubleshoot TCP/IP, DNS, DHCP, VPN, Wi-Fi, latency, endpoint connectivity, application access, and other network-related issues.
- Provide advanced support for Windows devices, endpoint performance, imaging, deployment, printers, scanners, application delivery, endpoint management, and remote-support tools.
- Support email security, endpoint protection, managed detection and response, identity security, password management, phishing investigations, suspicious sign-ins, malware alerts, and potential account compromise.
- Use PowerShell and approved automation tools for diagnostics, troubleshooting, and process improvement.
- Apply least-privilege principles, verify identity before sensitive access changes, and protect confidential client, tax, employee, and firm information.
- Maintain awareness of applicable security and compliance requirements, including IRS Publication 4557, the FTC Safeguards Rule, GLBA, SOC 2, GDPR, CCPA/CPRA, and HIPAA when applicable.
- Support security assessments, audit requests, remediation activities, recovery exercises, and technical control documentation.
- Support integrations, secure access, application availability and performance, upgrades, and vendor escalations across the firm’s application environment.
- Maintain technical knowledge of applications supporting accounting, tax, audit, advisory, document management, workflow, portals, payroll, practice management, electronic signature, PDF, scanning, printing, and remote-work processes.
- Support applications including CCH Axcess, CCH Engagement, CCH Workstream, CCH Workflow, Wolters Kluwer applications, Thomson Reuters applications, Inflo, SafeSend, K-1x, SurePrep, QuickBooks, QuickBooks Online, ShareFile, Adobe Acrobat, Adobe Sign, Star Practice Management, CFS Payroll, and related tools and dependencies.
- Understand the urgency of tax and audit deadlines, partner and client-impacting issues, secure access, engagement file availability, and business continuity.
- Coordinate technical and vendor resources while keeping stakeholders informed.
That's a lot but we need to preserve all substantive info. So include them.
Now Requirements: from "Qualifications Required" bullet list.
List:
- 5+ years of progressive experience across service desk support, advanced endpoint support, Microsoft 365 administration, secure remote access, business application support, and user-facing technical escalation.
- Demonstrated ability and willingness to handle Level 1 and Level 2 calls and tickets while owning Level 3 escalations, root cause analysis, platform support, documentation, and mentorship.
- Recent hands-on experience with cloud services, virtual desktop platforms, profile management, Microsoft 365, identity services, secure remote access, DNS, Wi-Fi, and production network-dependent support issues.
- Experience performing advanced incident troubleshooting, implementation planning, vendor escalation, documentation, and technical communication in a deadline-driven professional services environment.
Now Qualifications: from "Preferred" bullet list.
List:
- Bachelor’s degree in Information Technology, Computer Science, Cybersecurity, or a related field, or equivalent hands-on technical experience, military technical training, trade school, certifications, or comparable professional experience.
- Experience with endpoint management, service management, email security, endpoint protection, managed detection and response, password management, automation, security assessments, technical audits, remediation programs, business continuity, and disaster recovery.
- Experience supporting accounting, tax, audit, advisory, financial services, or another regulated and deadline-driven environment.
- Relevant Microsoft Azure, Microsoft 365, Microsoft Security, Cisco, CompTIA Security+, CISSP, CISM, ITIL, or comparable certifications are preferred.
Now Skills: maybe we could extract any skill-specific items not covered. Could include "PowerShell and approved automation tools" etc but those are in responsibilities. Could leave Skills empty or omit. Better to omit if no specific content.
Benefits: from "Why Grassi?" and "Benefits Package:" plus other benefits.
We need to capture:
- Flexibility: work-life balance initiatives include generous paid time off, flexible “Dress for Your Day” dress code, telecommuting options, flex-time policies, and summer hours, enhanced by our Floating Summer Friday’s program, which allows team members three extra Fridays off during the summer months in addition to their PTO.
- Company Culture: dedicated to creating an environment for our team members that is positive, productive, and aligns with our company’s high standards of inclusivity, diversity, and equity. Work with DEI Council and Grassi Women’s Council to organize events... Through charitable initiative, Grassi Gives Back, we support organizations such as Ronald McDonald House, Toys for Tots, Autism Speaks, Long Island Cares, and many of our nonprofit clients.
- Benefits Package: Competitive base compensation with eligibility for a raise and bonus each June or December based on performance metrics and level. Medical, Dental, and Vision Insurance, employer contribution to life insurance, 401(k) plan, ESOP, and client and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes "About Grassi" description, job summary, responsibilities, technical responsibilities, qualifications, why Grassi (benefits), compensation info. Need to map to sections. We need to decide which sections to include based on presence of content. - About the role: Could be the "Job Summary" paragraph: "We are currently seeking a Senior Systems Engineer to join our team in either our Park Ridge, NJ or Jericho, NY office location. This is a fully onsite position, five days per week in the office. This role offers an exciting opportunity to be part of a dynamic and growing firm." That's about the role. Also maybe include "About Grassi" but that's company description; not required but could be part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with job summary. - Responsibilities: list of duties from "Responsibilities include, but are not limited to:" bullet list. Also technical responsibilities could be part of responsibilities? Might be separate but we can combine under Responsibilities. - Requirements: maybe "Qualifications Required" is requirements. Also "Preferred" could be qualifications/skills. The instruction: Use Requirements heading for required qualifications? Could separate Requirements and Qualifications? They list both. We could treat "Qualifications Required" as Requirements, and "Preferred" as Qualifications or Skills. But we have both Qualifications and Skills headings available. Could put required under Requirements, preferred under Qualifications, and maybe Skills separate if we have skill list (like certifications). However we can combine. - Benefits: from "Why Grassi?" includes benefits package description. Also "Benefits Package:" bullet list. - Pay: compensation ranges for NY and NJ. - Schedule: mention "fully onsite position, five days per week in the office." Also maybe after-hours maintenance. So schedule info. We must not create sections with filler like "commensurate with experience". We have actual content. We must not include boilerplate like EEO etc. Not present. We need to output only HTML fragment, no /. Use
headings,
,
- . Ensure we preserve all substantive info.
Let's extract content.
About Grassi description: Could be considered company overview, but not required. Might be omitted as not part of sections? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the About Grassi paragraph somewhere. Where to put? Could be part of About the role? But About the role heading is for role description, not company. However we could include a separate section like "About the Company" but not in allowed headings. The allowed headings list is examples; we could still add other headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should likely stick to those. It also says "include a section ONLY when the posting has real, specific content for it". So we can include any of those headings if we have content. We might not need to include About Grassi if not fitting those headings. But we must preserve all substantive information; if we omit About Grassi, we lose info. Could we incorporate About Grassi into About the role? Possibly as a preamble: "About Grassi" could be considered part of About the role? Not ideal but maybe acceptable. However we could add a heading "About Grassi" as an h3 even though not in list; but instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use h3 for section headings (e.g...). It might be okay to add other headings as long as they are h3. But to be safe, we could incorporate About Grassi into a paragraph under About the role heading, maybe as a brief intro: "About Grassi: ..." That preserves info. Let's craft:
About the role
About Grassi: After more than 40 years of business growth... (the whole About Grassi paragraph). Then job summary paragraph: "We are currently seeking a Senior Systems Engineer to join our team in either our Park Ridge, NJ or Jericho, NY office location. This is a fully onsite position, five days per week in the office. This role offers an exciting opportunity to be part of a dynamic and growing firm." That preserves both. Now Responsibilities: combine the bullet list from "Responsibilities include, but are not limited to:" plus the technical responsibilities subheadings? Could treat technical responsibilities as part of responsibilities. We'll create a
- with each responsibility line.
List items:
- Serve as the final service desk escalation point for complex incidents involving Microsoft 365, identity services, secure remote access, endpoint protection, virtual desktop platforms, profile management, printers, security alerts, and firm applications.
- Lead root cause analysis for recurring, high-impact, or deadline-sensitive issues and implement durable corrective actions.
- Support technical delivery for endpoint, application, Microsoft 365, secure access, identity, infrastructure, security improvement, and modernization initiatives.
- Create and maintain configuration standards, operational runbooks, recovery procedures, troubleshooting guides, and knowledge articles.
- Mentor Level 1 and Level 2 personnel, improve escalation quality, and provide practical knowledge transfer.
- Coordinate with vendors, consultants, application owners, security resources, business stakeholders, and IT leadership.
- Identify technical debt, availability risks, capacity constraints, configuration weaknesses, and opportunities for automation or standardization.
- Participate in after-hours maintenance and critical incident response when business needs require it.
Then technical responsibilities could be separate bullet list under same responsibilities or maybe under a subheading but we don't have subheading allowed. Could incorporate as additional list items.
Technical responsibilities list:
- Administer and troubleshoot cloud services, including virtual machines, storage, networking, remote connectivity, monitoring, logging, backup, disaster recovery, and related services.
- Provide advanced support for virtual desktop environments and user profiles, including access, application delivery, printing, performance, capacity, and user experience.
- Administer Microsoft 365, including Exchange Online, Teams, Teams Phone, SharePoint Online, OneDrive, Outlook, Microsoft 365 Apps, Copilot, licensing, mailboxes, groups, and permissions.
- Support identity and access management, including users, groups, enterprise applications, access policies, sign-in issues, and access troubleshooting.
- Assess technical dependencies and business risk before changes and develop implementation, validation, and rollback plans.
- Support secure remote access, DNS, network connectivity, and secure-access platforms.
- Troubleshoot TCP/IP, DNS, DHCP, VPN, Wi-Fi, latency, endpoint connectivity, application access, and other network-related issues.
- Provide advanced support for Windows devices, endpoint performance, imaging, deployment, printers, scanners, application delivery, endpoint management, and remote-support tools.
- Support email security, endpoint protection, managed detection and response, identity security, password management, phishing investigations, suspicious sign-ins, malware alerts, and potential account compromise.
- Use PowerShell and approved automation tools for diagnostics, troubleshooting, and process improvement.
- Apply least-privilege principles, verify identity before sensitive access changes, and protect confidential client, tax, employee, and firm information.
- Maintain awareness of applicable security and compliance requirements, including IRS Publication 4557, the FTC Safeguards Rule, GLBA, SOC 2, GDPR, CCPA/CPRA, and HIPAA when applicable.
- Support security assessments, audit requests, remediation activities, recovery exercises, and technical control documentation.
- Support integrations, secure access, application availability and performance, upgrades, and vendor escalations across the firm’s application environment.
- Maintain technical knowledge of applications supporting accounting, tax, audit, advisory, document management, workflow, portals, payroll, practice management, electronic signature, PDF, scanning, printing, and remote-work processes.
- Support applications including CCH Axcess, CCH Engagement, CCH Workstream, CCH Workflow, Wolters Kluwer applications, Thomson Reuters applications, Inflo, SafeSend, K-1x, SurePrep, QuickBooks, QuickBooks Online, ShareFile, Adobe Acrobat, Adobe Sign, Star Practice Management, CFS Payroll, and related tools and dependencies.
- Understand the urgency of tax and audit deadlines, partner and client-impacting issues, secure access, engagement file availability, and business continuity.
- Coordinate technical and vendor resources while keeping stakeholders informed.
That's a lot but we need to preserve all substantive info. So include them.
Now Requirements: from "Qualifications Required" bullet list.
List:
- 5+ years of progressive experience across service desk support, advanced endpoint support, Microsoft 365 administration, secure remote access, business application support, and user-facing technical escalation.
- Demonstrated ability and willingness to handle Level 1 and Level 2 calls and tickets while owning Level 3 escalations, root cause analysis, platform support, documentation, and mentorship.
- Recent hands-on experience with cloud services, virtual desktop platforms, profile management, Microsoft 365, identity services, secure remote access, DNS, Wi-Fi, and production network-dependent support issues.
- Experience performing advanced incident troubleshooting, implementation planning, vendor escalation, documentation, and technical communication in a deadline-driven professional services environment.
Now Qualifications: from "Preferred" bullet list.
List:
- Bachelor’s degree in Information Technology, Computer Science, Cybersecurity, or a related field, or equivalent hands-on technical experience, military technical training, trade school, certifications, or comparable professional experience.
- Experience with endpoint management, service management, email security, endpoint protection, managed detection and response, password management, automation, security assessments, technical audits, remediation programs, business continuity, and disaster recovery.
- Experience supporting accounting, tax, audit, advisory, financial services, or another regulated and deadline-driven environment.
- Relevant Microsoft Azure, Microsoft 365, Microsoft Security, Cisco, CompTIA Security+, CISSP, CISM, ITIL, or comparable certifications are preferred.
Now Skills: maybe we could extract any skill-specific items not covered. Could include "PowerShell and approved automation tools" etc but those are in responsibilities. Could leave Skills empty or omit. Better to omit if no specific content.
Benefits: from "Why Grassi?" and "Benefits Package:" plus other benefits.
We need to capture:
- Flexibility: work-life balance initiatives include generous paid time off, flexible “Dress for Your Day” dress code, telecommuting options, flex-time policies, and summer hours, enhanced by our Floating Summer Friday’s program, which allows team members three extra Fridays off during the summer months in addition to their PTO.
- Company Culture: dedicated to creating an environment for our team members that is positive, productive, and aligns with our company’s high standards of inclusivity, diversity, and equity. Work with DEI Council and Grassi Women’s Council to organize events... Through charitable initiative, Grassi Gives Back, we support organizations such as Ronald McDonald House, Toys for Tots, Autism Speaks, Long Island Cares, and many of our nonprofit clients.
- Benefits Package: Competitive base compensation with eligibility for a raise and bonus each June or December based on performance metrics and level. Medical, Dental, and Vision Insurance, employer contribution to life insurance, 401(k) plan, ESOP, and client and