RTLS Senior Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Role Description (which is about the role), Key Responsibilities, Required Skills Experience (core technical skills, tools platforms). No explicit Benefits, Pay, Schedule. So we include About the role (maybe from first paragraph), Responsibilities, Requirements (maybe combine Required Skills Experience as Requirements), Skills (maybe separate? The instruction says we can have sections like Skills, Requirements, Qualifications. We need to decide what content goes where. The posting has "Required Skills Experience Core Technical Skills" and "Tools Platforms Preferred". That's skills. Could treat as Requirements (skills) and maybe Qualifications (experience). But we need to avoid thin sections. Could combine into one "Requirements" section covering skills and experience. Or we could have "Skills" and "Qualifications". Let's see: The posting includes "Required Skills Experience Core Technical Skills" and "Tools Platforms Preferred". That's both skills and experience. Could put under "Requirements". The instruction: "Prefer a few substantive sections over many thin ones." So maybe just three sections: About the role, Responsibilities, Requirements. No Benefits/Pay/Schedule. Use

for each heading. Use

• for lists. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. There's no boilerplate in given text besides maybe "Role Description". We'll keep content. We need to format:

  About the role

  We are seeking a Senior Engineer OT Enablement with deep expertise in RealTime Location Services RTLS and industrial location services for Oil Gas environments This SME role focuses on enabling personnel safety asset tracking operational visibility and regulatory compliance across refineries offshore platforms pipelines LNG terminals and depots The role requires handson experience deploying WiFi Bluetooth BLE and anchorbased positioning solutions in OT environments while ensuring high availability cybersecurity and compliance with Oil Gas standards

  But note there are no punctuation; we can keep as is but maybe add spaces for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. We can keep the text exactly as given, but we may need to add spaces where missing? The original text has missing spaces after periods? Actually the given text: "Role Description We are seeking a Senior Engineer OT Enablement with deep expertise in RealTime Location Services RTLS and industrial location services for Oil Gas environments This SME role focuses on enabling personnel safety asset tracking operational visibility and regulatory compliance across refineries offshore platforms pipelines LNG terminals and depots The role requires handson experience deploying WiFi Bluetooth BLE and anchorbased positioning solutions in OT environments while ensuring high availability cybersecurity and compliance with Oil Gas standards". There are missing spaces between sentences. We should preserve exactly? Probably we should keep as is, but we could add spaces to make readable? That would be altering content. Better to keep exactly as given, but we can wrap in

  and keep the string. However it's hard to read. But instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding spaces is not inventing detail, it's just formatting; but could be considered altering the original text. Safer to keep exactly as given. Similarly for responsibilities: list items. We need to parse responsibilities bullet points from the text: "Key Responsibilities RTLS Safety Enablement Design and deploy RTLS solutions for Personnel tracking and mandown musteringAsset and tool tracking in hazardous zones Enable geofencing restrictedzone s and emergency evacuation support Support realtime visibility for offshore platforms refineries and remote sites Network Infrastructure Optimize industrial WiFi and BLE networks for harsh environments Perform RF surveys heat mapping and accuracy tuning in Offshore platformsRefineries and tank farmsLNG and pipeline facilities Ensure redundancy resilience and high availability for safetycritical systems Select and validate intrinsically safe RTLS tags anchors and gateways Support audits HAZOP and safety reviews Operations Reliability Lead endtoend RTLS deployments Provide L3 support troubleshooting and root cause analysis Define SOPs runbooks and maintenance strategies" We need to split into list items. The text seems to have headings within: "RTLS Safety Enablement", "Network Infrastructure", "Operations Reliability". Each heading followed by sentences. We can treat each heading as a list item? Or we can make sub-items? The instruction: Use

  • for any list of duties/requirements/benefits. So we can create a list where each duty is a
  • . We need to extract duties. Let's parse: RTLS Safety Enablement: - Design and deploy RTLS solutions for Personnel tracking and mandown mustering - Asset and tool tracking in hazardous zones - Enable geofencing restrictedzone s and emergency evacuation support - Support realtime visibility for offshore platforms refineries and remote sites Network Infrastructure: - Optimize industrial WiFi and BLE networks for harsh environments - Perform RF surveys heat mapping and accuracy tuning in Offshore platformsRefineries and tank farmsLNG and pipeline facilities - Ensure redundancy resilience and high availability for safetycritical systems - Select and validate intrinsically safe RTLS tags anchors and gateways - Support audits HAZOP and safety reviews Operations Reliability: - Lead endtoend RTLS deployments - Provide L3 support troubleshooting and root cause analysis - Define SOPs runbooks and maintenance strategies We need to preserve the exact phrasing, but we can add line breaks and bullet points. The original text lacks spaces in some places: "mandown musteringAsset", "restrictedzone s", "Offshore platformsRefineries", "tank farmsLNG", "safetycritical systems", "endtoend". We should keep as is? Might be okay to add spaces for readability but that changes content. However the instruction says preserve ALL substantive information; adding spaces is not adding or removing substantive info, just formatting. Might be acceptable. Safer to keep exactly as given but we can insert spaces to separate words that are obviously concatenated due to missing spaces. But that could be considered altering. I'd lean to keep the original string but break into list items preserving the exact strings as they appear, even if they have missing spaces. That would be weird but faithful. Let's extract each duty as a substring from the responsibilities section. Original responsibilities string after "Key Responsibilities ": "RTLS Safety Enablement Design and deploy RTLS solutions for Personnel tracking and mandown musteringAsset and tool tracking in hazardous zones Enable geofencing restrictedzone s and emergency evacuation support Support realtime visibility for offshore platforms refineries and remote sites Network Infrastructure Optimize industrial WiFi and BLE networks for harsh environments Perform RF surveys heat mapping and accuracy tuning in Offshore platformsRefineries and tank farmsLNG and pipeline facilities Ensure redundancy resilience and high availability for safetycritical systems Select and validate intrinsically safe RTLS tags anchors and gateways Support audits HAZOP and safety reviews Operations Reliability Lead endtoend RTLS deployments Provide L3 support troubleshooting and root cause analysis Define SOPs runbooks and maintenance strategies" We need to split at each heading: "RTLS Safety Enablement", "Network Infrastructure", "Operations Reliability". Then after each heading, the duties until next heading or end. Let's manually split: After "RTLS Safety Enablement " we have: "Design and deploy RTLS solutions for Personnel tracking and mandown musteringAsset and tool tracking in hazardous zones Enable geofencing restrictedzone s and emergency evacuation support Support realtime visibility for offshore platforms refineries and remote sites " Then "Network Infrastructure " then: "Optimize industrial WiFi and BLE networks for harsh environments Perform RF surveys heat mapping and accuracy tuning in Offshore platformsRefineries and tank farmsLNG and pipeline facilities Ensure redundancy resilience and high availability for safetycritical systems Select and validate intrinsically safe RTLS tags anchors and gateways Support audits HAZOP and safety reviews " Then "Operations Reliability " then: "Lead endtoend RTLS deployments Provide L3 support troubleshooting and root cause analysis Define SOPs runbooks and maintenance strategies" Now we need to split each block into individual duties. The duties seem separated by verbs but no clear delimiters. We can infer each duty starts with a verb (Design, Asset, Enable, Support, Optimize, Perform, Ensure, Select, Support, Lead, Provide, Define). We can split before each capitalized verb that starts a new sentence? But there is no punctuation. This is messy. Given the instruction to preserve ALL substantive information, maybe we should not try to split into list items; we could keep the responsibilities as a paragraph (

    ) rather than list. But the instruction says use

    • for any list of duties/requirements/benefits. If we don't have clear list, we could still use

      . But the responsibilities are clearly a list of duties; we should attempt to make list items. We could treat each sentence as a duty, but we need to infer sentence boundaries. The original text likely had periods but they were removed inadvertently. We could insert periods before each capital letter that starts a new duty after a heading? For example after "RTLS Safety Enablement " we see "Design and deploy..." then "Asset and tool..." then "Enable geofencing..." then "Support realtime visibility..." then after that we see "Network Infrastructure". So we can split before each capitalized word that is not part of a proper noun? This is getting complex. Given the constraints, maybe it's acceptable to output responsibilities as a

      block, preserving the text exactly. The instruction says use

      • for any list of duties/requirements/benefits. If we don't format as list, we might violate. But we could still format as list with each duty as a line item, even if the delineation is approximate. I think we can produce list items based on the logical groupings we identified: each heading's bullet points. We can produce:
        • Design and deploy RTLS solutions for Personnel tracking and mandown musteringAsset and tool tracking in hazardous zones Enable geofencing restrictedzone s and emergency evacuation support Support realtime visibility for offshore platforms refineries and remote sites
        • Optimize industrial WiFi and BLE networks for harsh environments Perform RF surveys heat mapping and accuracy tuning in Offshore platformsRefineries and tank farmsLNG and pipeline facilities Ensure redundancy resilience and high availability for safetycritical systems Select and validate intrinsically safe RTLS tags anchors and gateways Support audits HAZOP and safety reviews
        • Lead endtoend RTLS deployments Provide L3 support troubleshooting and root cause analysis Define SOPs runbooks and maintenance strategies
        But that lumps multiple duties into each li, losing granularity. Better to split further. Let's attempt to split by noticing each duty starts with a verb and ends before next verb that starts a new duty (capitalized). We'll need to parse the string. I'll write a quick mental parse for first block: "Design and deploy RTLS solutions for Personnel tracking and mandown musteringAsset and tool tracking in hazardous zones Enable geofencing restrictedzone s and emergency evacuation support Support realtime visibility for offshore platforms refineries and remote sites" Verbs: Design, Asset (actually "Asset" is noun but phrase "Asset and tool tracking" starts with Asset), Enable, Support. So we can split before each of these words when they appear at start of a duty. Thus duties: 1. Design and deploy RTLS solutions for Personnel tracking and mandown mustering 2. Asset and tool tracking in hazardous zones 3. Enable geofencing restrictedzone s and emergency evacuation support 4. Support realtime visibility for offshore platforms refineries and remote sites But note the original text concatenated "musteringAsset" without space. If we split before "Asset", we need to ensure we keep the preceding text correct. The original had "...mandown musteringAsset and tool tracking..." So if we split before Asset, the first duty would end at "mustering". But the original lacks space; we could add a space before Asset to separate. That would be adding a space, but it's minor. Similarly for second block: "Optimize industrial