Regional Market Engineering Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Townsquare Media:" and "The Regional Market Engineering Manager Opportunity:" etc. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We need to extract content. We have: - About Townsquare Media: description of company. Could be "About the role"? Actually "About Townsquare Media" is about company, not role. But we can map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. If content matches, we use that heading. If not, we might need to adapt? Probably we should use those headings only if we have content for them. If we have content about the role, we can put under "About the role". The posting includes "The Regional Market Engineering Manager Opportunity:" which describes role. So we can put that under

About the role

. Responsibilities: The "Essential Functions" list includes duties. So we can put under

Responsibilities

with

• items. Requirements: Could be "Qualifications" section. The posting has "Qualifications:" with Required and Preferred. So we can put under

  Qualifications

  . Also maybe "Requirements" could be same as Qualifications. But we should not duplicate. Use Qualifications heading. Skills: Could be extracted from Qualifications (proficiency with Microsoft Windows etc). Could be separate but we can include under Qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Qualifications section. But we have separate headings list; we can choose to include Qualifications and maybe Skills if we have distinct content. However we have content like "Proficiency with Microsoft Windows, Microsoft Office, networking concepts, computer hardware, and wireless/handheld devices" etc. That's skills. Could be under Skills. But we also have "Required: Five or more years..." etc. That's qualifications/experience. Could split. But we should avoid thin sections. Maybe we combine into one Qualifications section that includes both experience and skills. That seems fine. Benefits: The posting has "Benefits:" with list. So we include

  Benefits

  with
  . Pay: Not mentioned (no salary). So we should NOT include Pay section. Schedule: Not mentioned (though hybrid, travel, after-hours, weekend work, on-call). That's schedule info. The posting mentions hybrid position involves travel, after-hours and weekend work, on-call availability. That's schedule details. So we could include Schedule section with that info. However the instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The schedule content is specific: hybrid, travel, after-hours, weekend work, on-call availability. So we can include Schedule. We also need to include maybe "About the role" section with description from "The Regional Market Engineering Manager Opportunity:" and maybe also "About Townsquare Media:"? The "About the role" heading expects description of role. We can put the opportunity description there. The "About Townsquare Media" could be considered company overview; maybe we could put under "About the role" as well, but it's about company. Could we add another heading like "About the company"? Not allowed headings list. So we could incorporate that into About the role or maybe omit. The instruction: do NOT repeat the job title as a heading. It's okay to include company description under About the role? Might be okay. But better to keep About the role focusing on role. Could we add a separate section like "About the company"? Not in allowed headings list, but we could still use

  About the company

  ? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g...). Likely they expect only those headings. So we should stick to those. So we can put company description under About the role as part of role description? Might be okay. Alternatively we could omit company description entirely? But we must preserve ALL substantive information. So we need to include it somewhere. We could put it under About the role as a preamble. Thus sections: - About the role: includes description of Townsquare Media and the opportunity. - Responsibilities: essential functions list. - Qualifications: required and preferred. - Benefits: list. - Schedule: hybrid, travel, after-hours, weekend, on-call. We should not include Pay. Now format: Use

  for each heading. Then content:

  for prose,

  • for lists. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "Five or more years of progressively responsible broadcast engineering experience, or an equivalent combination of education and experience", etc. We need to capture the list of essential functions: many bullet points. We'll turn each into
  • . We need to capture benefits list: "3 weeks of PTO (+ 9 paid holidays)", "Medical, Dental, and Vision Insurance", "401(k) Retirement Plan", "Casual, high-energy work environment", "Opportunity for upward mobility", "Company provided laptop", "Competitive salary + bonus program", "Company discounts", "Pet Insurance", "Time off for volunteering", "And much more…" The "And much more…" is vague; we should include as is? It's substantive? It's filler. Might be okay to include as a list item. We need to capture schedule/hybrid info: "This is a hybrid position that involves travel, after-hours and weekend work, and on-call availability as required." Also earlier: "*This is a hybrid position that involves travel, after-hours and weekend work, and on-call availability as required." Also later: "Travel and Emergency Response" section includes details about driving, responding to emergencies, on-call availability. So schedule section should include that. We need to ensure we don't include boilerplate like disclaimer, EEO, etc. Remove those. Now craft HTML. Let's draft:

    About the role

    Townsquare is a media, entertainment, and digital marketing solutions company dedicated to serving small and mid-sized markets across the U.S. We own and operate 354 radio stations and more than 400 local websites across 74 markets—including trusted Fort Collins, Grand Junction, Montrose, Casper, Cheyenne, and Laramie stations. We combine the power of local media with best-in-class digital solutions to help businesses grow—offering everything from broadcast and digital advertising to SEO, web design, and programmatic marketing. Townsquare Media is looking for a Market Engineering Manager to oversee our multi-station broadcast radio facility in the Fort Collins, Grand Junction, Montrose, Casper, Cheyenne, and Laramie markets. This position serves as the sole technical authority for market-level engineering operations and is responsible for the planning, analysis, and independent decision-making that governs broadcast continuity, FCC compliance, and infrastructure strategy across all assigned stations. The Market Engineering Manager exercises independent judgment on matters that directly affect station revenue, regulatory standing, and operational performance, and will personally perform technical work when operational circumstances require.

    Responsibilities

    • Exercise independent judgment to assess, prioritize, and resolve technical failures affecting station broadcast continuity, including real-time decisions during on-air emergencies where delays directly impact revenue and regulatory standing
    • Evaluate equipment performance and determine appropriate corrective action, including the authority to take systems offline, reroute signals, or authorize emergency repairs without prior approval when broadcast continuity is at risk
    • Ability and willingness to serve as Chief Operator under FCC rules, with independent authority to ensure station compliance with all applicable technical regulations
    • Conduct root cause analysis of equipment failures and develop technical solutions to prevent recurrence
    • Evaluate and optimize broadcast transmission infrastructure and technical systems to ensure operational continuity and regulatory compliance
    • Develop technical operating standards for market engineering operations
    • Develop and recommend capital expenditure plans for infrastructure upgrades, including vendor evaluation, budget proposals, and cost-benefit analysis for executive approval
    • Evaluate and select vendors and contractors for engineering projects and maintenance
    • Inspect, diagnose, repair, and maintain all broadcast radio station equipment, including transmitters, antennas, satellite downlinks, automation systems, studio equipment, remote equipment, generators, telephone systems, and related equipment
    • Install and maintain AoIP and automation systems (Zetta and Wheatstone experience preferred)
    • Maintain and troubleshoot AM directional antenna systems
    • Maintain EAS systems, logging compliance, and related equipment
    • Maintain personal computers, servers, printers, and software; perform updates as needed
    • Install and maintain LAN systems
    • Ensure compliance with all Company Engineering and Information Technology practices
    • Maintain a valid driver’s license and reliable transportation
    • Drive independently to multiple transmitter sites across assigned markets, including remote locations
    • Respond to emergency equipment failures on short notice, including after hours and weekends; this role requires on-call availability reflecting the position’s independent authority over broadcast operations
    • Travel between sites safely and efficiently, navigating to locations without assistance
    • Read and interpret technical documents, safety rules, operating and maintenance instructions, schematics, and procedure manuals
    • Follow detailed verbal and written instructions accurately and retain information necessary to complete tasks
    • Identify and differentiate between multiple transmitters, equipment components, and site locations
    • Diagnose equipment issues and make real-time decisions to restore broadcast operations
    • Write routine reports, technical documentation, and correspondence
    • Communicate effectively with programming staff, management, and other employees to achieve operational goals
    • Interface with the Senior Vice President of Engineering, Senior Vice President of Information Technology, and other Corporate Technical Staff to ensure current guidance and best practices are followed
    • Follow all safety protocols for working with high-voltage equipment and at tower sites
    • Maintain situational awareness to prevent falls and injuries
    • Climb ladders and work at heights
    • Work in varying weather conditions and outdoor environments
    • Frequently stand, walk, sit, use hands to handle or feel, reach with hands and arms, and talk or hear
    • Occasionally climb, balance, stoop, kneel, crouch, or crawl
    • Frequently lift and/or move up to 10 pounds; occasionally lift and/or move up to 50 pounds
    • Maintain close visual acuity to prepare and analyze data and figures, view a computer terminal, read extensively, inspect small defects and parts, operate machines, and use measurement devices

    Qualifications

    • Required: Five or more years of progressively responsible broadcast engineering experience, or an equivalent combination of education and experience
    • Required: Demonstrated ability to exercise independent technical judgment in high-pressure, time-sensitive environments
    • Required: Proficiency with Microsoft Windows, Microsoft Office, networking concepts, computer hardware, and wireless/handheld devices
    • Required: Ability to solve practical problems and deal with a variety of concrete variables in situations where only limited standardization exists
    • Required: Ability to interpret instructions furnished in written, oral, diagram, or schedule form
    • Preferred: SBE certification or computer-related certification