GLOBAL OPS · Englewood, NJ · 3 wk ago
On-siteManagement$62k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Qualifications, maybe Benefits? The posting includes compensation details (Unarmed: $62,400 annually; Armed: $76,700 annually). That's compensation, so we need a Pay section. Also schedule: Tuesday to Saturday (50 hours workweek in the field; with flexible coverage requirements). So Schedule section. Benefits? Not mentioned. So no Benefits. Also location is given but not a heading; we can embed location in a short p maybe. Also we need to not repeat job title as heading. The job title is "Field Operations Specialist". Not to repeat. So we will have sections: About the role, Responsibilities, Qualifications, Pay, Schedule. Possibly also "What Success Looks Like" could be considered part of responsibilities? But it's separate content; we could include as a separate section maybe "Performance Expectations". However instruction: Prefer a few substantive sections over many thin ones. Could combine "What Success Looks Like" into Responsibilities or a separate section? It's about success metrics; could be its own section "Performance Expectations". But we need to decide if it's substantive enough. It's a list of bullet-like statements. Could be its own section. However we already have Responsibilities; we could add a subsection? But we only allowed headings . Could add another h3 "Performance Expectations". That would be okay if we have content. Let's see if we have enough sections: About the role, Responsibilities, Qualifications, Pay, Schedule, Performance Expectations. That's six sections, maybe okay. But we could also merge Performance Expectations into Responsibilities as bullet points. However the instruction: Prefer a few substantive sections over many thin ones. Having six may be okay if each is substantive. But we could combine Performance Expectations into Responsibilities to reduce sections. Let's think: The responsibilities list already includes many bullet-like items. The "What Success Looks Like" is more about outcomes; could be considered part of responsibilities or a separate section. I'd lean to include as a separate section "Performance Expectations" because it's distinct. But we need to avoid thin sections; each should have substantive content. Performance Expectations has several bullet points: Reliable coverage stabilization, Clear, professional incident escalation, Strong site familiarity across region, Reduced operational disruption, Positive client and internal feedback, Demonstrated readiness for advancement into Field Management. That's substantive.
Thus sections: About the role (paragraph), Responsibilities (ul), Qualifications (ul), Pay (p or ul?), Schedule (p), Performance Expectations (ul). Also maybe include location metadata in a short p before sections.
We must not include boilerplate like EEO etc. Not present.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content:
Location: Westchester, North New Jersey & West Connecticut (back up to Manhattan)
Employment Type: Full-time - Salaried
Work Setting: Field-Based (Multi-Site)
Schedule: Tuesday to Saturday (50 hours workweek in the field; with flexible coverage requirements)
Compensation: Unarmed: $62,400 annually; Armed: $76,700 annually (must possess valid NYS Armed Guard License, NJ SORA, and Unrestricted Carry Permit)
About The Role: paragraph.
Key Responsibilities: list items (some are combined with no bullet but we can split). Need to parse:
- Regional Shift Coverage & Workforce Stabilization
Provide on-site coverage in response to call-outs, absences, and urgent staffing needs
Float between multiple client locations within assigned region
Maintain operational continuity during scheduling gaps
Support staffing stabilization efforts during peak operational periods
- Site Familiarization & Operational Readiness
Develop working knowledge of all assigned sites, including post orders and client expectations
Conduct regular site visits and walkthroughs
Perform perimeter checks and site checks
Identify operational inconsistencies and escalate appropriately
- Incident Response & Escalation Support
Respond to urgent field incidents in coordination with Company Management
Support proper incident documentation and reporting
Maintain composure and professionalism during high-pressure situations
Reinforce escalation protocols and operational standards
- Quality Assurance & Standards Enforcement
Reinforce company protocols and professional conduct standards
Support onboarding shadowing for new agents
Provide real-time feedback to Managers regarding operational trends
Model accountability, punctuality, and field professionalism
- Authority & Reporting Structure
Reports directly to the Manager of Field Operations
No direct reports
No hiring, termination, or disciplinary authority
No client contract ownership
This role supports field management.
We need to preserve all. We'll create ul with li for each bullet point; maybe group under headings? But we only allowed h3 for section headings, not subheadings. Could we include subheadings as strong? Not allowed? The instruction only says use h3 for section headings; we can still use other tags like inside li? Probably okay but safer to just list each responsibility as li without subheadings. However we might lose some grouping but still preserve all info. Could embed subheading as inside li. That's acceptable.
Qualifications: list:
- Minimum 5 years of private security or related operational experience
- Valid NYS Security Guard License (required)
- Valid NYS Armed Guard License (required for Armed role)
- Valid NJ SORA & Carry Permit (required for Armed role)
- Strong understanding of field security operations
- Ability to travel between multiple Westchester, North New Jersey & West Connecticut
- Professional communication skills (verbal and written)
- Ability to remain calm under pressure
- Strong situational awareness and decision-making ability
Physical & Work Requirements:
- Ability to stand and walk for extended periods
- Ability to travel between sites throughout Westchester, North New Jersey & West Connecticut
- Flexibility for evenings, weekends, and emergency coverage
- Ability to respond to urgent operational needs
We could combine Qualifications and Physical & Work Requirements into one Qualifications section (since both are requirements). That's fine.
Pay: we have two rates: Unarmed: $62,400 annually; Armed: $76,700 annually (must possess valid NYS Armed Guard License, NJ SORA, and Unrestricted Carry Permit). We'll put in a p.
Schedule: Tuesday to Saturday (50 hours workweek in the field; with flexible coverage requirements). We'll put in a p.
Performance Expectations: list:
- Reliable coverage stabilization
- Clear, professional incident escalation
- Strong site familiarity across region
- Reduced operational disruption
- Positive client and internal feedback
- Demonstrated readiness for advancement into Field Management
Also there is a career path diagram: Security Agent ↓ Field Operations Specialist ↓ Regional Security Operations Manager ↓ Director of Security Operations. That's also substantive; could be included in Performance Expectations or a separate section "Career Path". Might be better as its own section "Career Path". But we already have many sections. Could add as a p.
But instruction: Prefer a few substantive sections over many thin ones. Adding Career Path may be okay if we keep sections limited. Let's count: About the role, Responsibilities, Qualifications, Pay, Schedule, Performance Expectations, Career Path = 7 sections. Might be many. Could merge Career Path into Performance Expectations or About the role. Probably better to add as a p under Performance Expectations or About the role. Since it's about advancement, fits Performance Expectations.
Thus Performance Expectations list plus a sentence about career path.
Let's craft HTML.
We'll start with a p for location and employment type etc? The location and employment type could be a short p: "Location: Westchester, North New Jersey & West Connecticut (back up to Manhattan). Employment Type: Full-time - Salaried. Work Setting: Field-Based (Multi-Site)." But we already have Schedule and Pay sections; we could incorporate location and employment type into a brief p before sections.
We must not repeat job title. So no heading for it.
Thus output:
. Could add another h3 "Performance Expectations". That would be okay if we have content. Let's see if we have enough sections: About the role, Responsibilities, Qualifications, Pay, Schedule, Performance Expectations. That's six sections, maybe okay. But we could also merge Performance Expectations into Responsibilities as bullet points. However the instruction: Prefer a few substantive sections over many thin ones. Having six may be okay if each is substantive. But we could combine Performance Expectations into Responsibilities to reduce sections. Let's think: The responsibilities list already includes many bullet-like items. The "What Success Looks Like" is more about outcomes; could be considered part of responsibilities or a separate section. I'd lean to include as a separate section "Performance Expectations" because it's distinct. But we need to avoid thin sections; each should have substantive content. Performance Expectations has several bullet points: Reliable coverage stabilization, Clear, professional incident escalation, Strong site familiarity across region, Reduced operational disruption, Positive client and internal feedback, Demonstrated readiness for advancement into Field Management. That's substantive.
Thus sections: About the role (paragraph), Responsibilities (ul), Qualifications (ul), Pay (p or ul?), Schedule (p), Performance Expectations (ul). Also maybe include location metadata in a short p before sections.
We must not include boilerplate like EEO etc. Not present.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content:
Location: Westchester, North New Jersey & West Connecticut (back up to Manhattan)
Employment Type: Full-time - Salaried
Work Setting: Field-Based (Multi-Site)
Schedule: Tuesday to Saturday (50 hours workweek in the field; with flexible coverage requirements)
Compensation: Unarmed: $62,400 annually; Armed: $76,700 annually (must possess valid NYS Armed Guard License, NJ SORA, and Unrestricted Carry Permit)
About The Role: paragraph.
Key Responsibilities: list items (some are combined with no bullet but we can split). Need to parse:
- Regional Shift Coverage & Workforce Stabilization
Provide on-site coverage in response to call-outs, absences, and urgent staffing needs
Float between multiple client locations within assigned region
Maintain operational continuity during scheduling gaps
Support staffing stabilization efforts during peak operational periods
- Site Familiarization & Operational Readiness
Develop working knowledge of all assigned sites, including post orders and client expectations
Conduct regular site visits and walkthroughs
Perform perimeter checks and site checks
Identify operational inconsistencies and escalate appropriately
- Incident Response & Escalation Support
Respond to urgent field incidents in coordination with Company Management
Support proper incident documentation and reporting
Maintain composure and professionalism during high-pressure situations
Reinforce escalation protocols and operational standards
- Quality Assurance & Standards Enforcement
Reinforce company protocols and professional conduct standards
Support onboarding shadowing for new agents
Provide real-time feedback to Managers regarding operational trends
Model accountability, punctuality, and field professionalism
- Authority & Reporting Structure
Reports directly to the Manager of Field Operations
No direct reports
No hiring, termination, or disciplinary authority
No client contract ownership
This role supports field management.
We need to preserve all. We'll create ul with li for each bullet point; maybe group under headings? But we only allowed h3 for section headings, not subheadings. Could we include subheadings as strong? Not allowed? The instruction only says use h3 for section headings; we can still use other tags like inside li? Probably okay but safer to just list each responsibility as li without subheadings. However we might lose some grouping but still preserve all info. Could embed subheading as inside li. That's acceptable.
Qualifications: list:
- Minimum 5 years of private security or related operational experience
- Valid NYS Security Guard License (required)
- Valid NYS Armed Guard License (required for Armed role)
- Valid NJ SORA & Carry Permit (required for Armed role)
- Strong understanding of field security operations
- Ability to travel between multiple Westchester, North New Jersey & West Connecticut
- Professional communication skills (verbal and written)
- Ability to remain calm under pressure
- Strong situational awareness and decision-making ability
Physical & Work Requirements:
- Ability to stand and walk for extended periods
- Ability to travel between sites throughout Westchester, North New Jersey & West Connecticut
- Flexibility for evenings, weekends, and emergency coverage
- Ability to respond to urgent operational needs
We could combine Qualifications and Physical & Work Requirements into one Qualifications section (since both are requirements). That's fine.
Pay: we have two rates: Unarmed: $62,400 annually; Armed: $76,700 annually (must possess valid NYS Armed Guard License, NJ SORA, and Unrestricted Carry Permit). We'll put in a p.
Schedule: Tuesday to Saturday (50 hours workweek in the field; with flexible coverage requirements). We'll put in a p.
Performance Expectations: list:
- Reliable coverage stabilization
- Clear, professional incident escalation
- Strong site familiarity across region
- Reduced operational disruption
- Positive client and internal feedback
- Demonstrated readiness for advancement into Field Management
Also there is a career path diagram: Security Agent ↓ Field Operations Specialist ↓ Regional Security Operations Manager ↓ Director of Security Operations. That's also substantive; could be included in Performance Expectations or a separate section "Career Path". Might be better as its own section "Career Path". But we already have many sections. Could add as a p.
But instruction: Prefer a few substantive sections over many thin ones. Adding Career Path may be okay if we keep sections limited. Let's count: About the role, Responsibilities, Qualifications, Pay, Schedule, Performance Expectations, Career Path = 7 sections. Might be many. Could merge Career Path into Performance Expectations or About the role. Probably better to add as a p under Performance Expectations or About the role. Since it's about advancement, fits Performance Expectations.
Thus Performance Expectations list plus a sentence about career path.
Let's craft HTML.
We'll start with a p for location and employment type etc? The location and employment type could be a short p: "Location: Westchester, North New Jersey & West Connecticut (back up to Manhattan). Employment Type: Full-time - Salaried. Work Setting: Field-Based (Multi-Site)." But we already have Schedule and Pay sections; we could incorporate location and employment type into a brief p before sections.
We must not repeat job title. So no heading for it.
Thus output:
Similar jobs
Field Operations Specialist
Managementapply on pretiumenterpriseservices.wd1.myworkdayjobs.com
Field Operations Specialist
Managementapply on nodaintelligence.ai
Field Operations Specialist
Management
Field Operations Specialist
Managementapply on jobs.lever.co
Field Operations Specialist
Managementapply on job-boards.greenhouse.io
Field Operations Specialist
Managementapply on recruiting.paylocity.com