Senior Digital Buildings Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "Company Overview", "Job Description", "Key Responsibilities", "Qualifications Skills and Experience". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. We need sections only if posting has real specific content. We have: - Company Overview: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "Job Description" which includes description of role. Could map to "About the role". Or we could use "Job Description" but the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should use those exact headings. So we need to decide which sections to include. We have content for: - About the role: could be the Job Description paragraph(s) describing role. - Responsibilities: the "Key Responsibilities" list. - Qualifications: the "Qualifications Skills and Experience" section includes essential and desirable. - Skills: maybe we could separate Skills from Qualifications? But we have both technical skills and soft skills within qualifications. Could put them under Skills heading. However we also have Qualifications heading for education/experience. The instruction says we can use headings like Qualifications, Skills. So we could have both. We need to avoid filler sections like Benefits, Pay, Schedule if not present. The posting does not mention benefits, pay, schedule. So we omit those. We need to output only HTML fragment, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO etc. Not present. We need to ensure we don't repeat job title as heading. We need to not put Job ID/requisition numbers as headings. We need to preserve all details. Let's extract content. Company Overview paragraph: "FPC Global are the world's leading digital building experts, we offer full-service integrated technology consultancy and professional services to the built environment. We partner with global clients to improve asset performance, operational efficiency, sustainability outcomes, and digital maturity across complex portfolios." Job Description paragraph(s): "The Senior Digital Buildings Engineer contributes to integrating various BMS, IoT devices, and facility management systems into a cloud platform, working across different vendors and ecosystems. This platform-agnostic role enables secure, seamless data flow for analytics, remote monitoring, and operational efficiency. The engineer collaborates with global teams across IT, security, and infrastructure, engaging with multiple cloud environments (AWS, Azure, Google Cloud) and diverse technologies. The role requires strong technical adaptability, quick decision-making, and effective communication to support smart, data-driven building operations. In addition to client-facing roles and responsibilities, Senior DB engineer is expected to be an active member of the Digital Buildings Engineering team, to make a positive contribution to the development of the team and wider FPC business, working effectively with all FPC colleagues to successfully deliver projects and support FPC’s business objectives." Key Responsibilities bullet list (many). We need to preserve each bullet as

• . The bullet points are long sentences; we should keep them as is. Qualifications Skills and Experience: Essential: - Bachelor's degree Controls engineering or a related field. - Industry Expertise Typically 7-12 years of experience in design and configuration of building automation systems, cloud integration, or IT infrastructure roles. - Systems Integration related projects or related industries such as Architecture, MEP Engineering Design or Construction. - Strong understanding of MEP Engineering, cybersecurity best practices, energy performance analytics. - Knowledge of edge computing and data preprocessing methods for IoT systems. - Technical Skills Basic technical understanding in delivering digital / smart building and IoT technology projects, including some or all of the following: Digital Building Systems Integration design, development and implementation Digital Building Controls Systems Cybersecurity best practices IP Networking (IPV4, IPV6, Switching, Routing, DHCP, WiFi, Structured Cabling, etc.) System Audits & Site Surveys - Soft Skills Analytical Skills: Ability to interpret building performance data, identify trends, and develop actionable insights for continuous improvement. Client-Focused: Excellent client relationship management skills with the ability to communicate technical information effectively. Process Improvement: Proven experience in understanding and contributing to SOPs, MOPs, and RACIs, with a focus on process optimisation and standardisation. Problem Solving: Strong troubleshooting skills with a proactive approach to resolving technical issues remotely. Leadership and Mentorship: Proven ability to lead, mentor, and develop junior team members in incident management and operational best practices. Desirable: - Experience with BMS systems like Niagara, Delmatic, Delta, LoRaWAN. Certifications in any of these are beneficial . - Cloud platforms (AWS, Azure, or Google Cloud) and relevant cloud services (data storage, IoT hubs, etc.). Certification in any of the cloud platforms is beneficial. - Personal Attributes Highly professional, with unwavering honesty and integrity. Exceptional communicator and client-relationship builder. A continuous and agile learner. A systems thinker with attention to detail. A strategic thinker with the ability to translate vision into action. - Success Measures To be agreed with role specific assignments and career planning with the hiring manager. Additional Information paragraph about FPC community etc. This is more about company culture; could be included under "About the role" or maybe a separate section like "About the company". But we only have allowed headings; we could incorporate into About the role or maybe we could add a section "About the company"? Not allowed. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but we could use others? Safer to stick to those. We could put the Additional Information under About the role as prose. We need to avoid filler like "Success Measures To be agreed..." that is vague; but it's actual content. Should we include it? It's not filler like "commensurate with experience". It's a statement. We could include under Qualifications or maybe under a separate section "Requirements"? But we have no specific requirements besides qualifications. Could treat "Success Measures" as part of Qualifications? Might be okay. We need to preserve all substantive info; we can include it as a paragraph under Qualifications or maybe under a separate section "Requirements". Since we have a heading "Requirements" allowed, we could put success measures there. But we already have qualifications covering education/experience/skills. The success measures is about performance metrics; could be under Requirements. Let's decide sections: - About the role: combine Company Overview + Job Description paragraphs. - Responsibilities: list of responsibilities. - Qualifications: education, years experience, industry expertise, systems integration, understanding, knowledge, technical skills basics, soft skills. - Skills: maybe separate technical skills and soft skills? But we already included them under Qualifications. Could split: Qualifications for education/experience, Skills for technical and soft skills. However the instruction says we can use both headings. Let's do: - Qualifications: education, years experience, industry expertise, systems integration, understanding, knowledge. - Skills: technical skills (list) and soft skills (list) and desirable (BMS experience, cloud platforms, personal attributes). Also success measures maybe under Requirements? But we could put success measures under Qualifications as well. But we need to avoid duplication. Let's parse the qualifications section more clearly. Original "Qualifications Skills and Experience Essential:" list includes: - Bachelor's degree Controls engineering or a related field. - Industry Expertise Typically 7-12 years of experience in design and configuration of building automation systems, cloud integration, or IT infrastructure roles. - Systems Integration related projects or related industries such as Architecture, MEP Engineering Design or Construction. - Strong understanding of MEP Engineering, cybersecurity best practices, energy performance analytics. - Knowledge of edge computing and data preprocessing methods for IoT systems. - Technical Skills Basic technical understanding in delivering digital / smart building and IoT technology projects, including some or all of the following: Digital Building Systems Integration design, development and implementation Digital Building Controls Systems Cybersecurity best practices IP Networking (IPV4, IPV6, Switching, Routing, DHCP, WiFi, Structured Cabling, etc.) System Audits & Site Surveys - Soft Skills Analytical Skills: Ability to interpret building performance data, identify trends, and develop actionable insights for continuous improvement. Client-Focused: Excellent client relationship management skills with the ability to communicate technical information effectively. Process Improvement: Proven experience in understanding and contributing to SOPs, MOPs, and RACIs, with a focus on process optimisation and standardisation. Problem Solving: Strong troubleshooting skills with a proactive approach to resolving technical issues remotely. Leadership and Mentorship: Proven ability to lead, mentor, and develop junior team members in incident management and operational best practices. Desirable: - Experience with BMS systems like Niagara, Delmatic, Delta, LoRaWAN. Certifications in any of these are beneficial . - Cloud platforms (AWS, Azure, or Google Cloud) and relevant cloud services (data storage, IoT hubs, etc.). Certification in any of the cloud platforms is beneficial. - Personal Attributes Highly professional, with unwavering honesty and integrity. Exceptional communicator and client-relationship builder. A continuous and agile learner. A systems thinker with attention to detail. A strategic thinker with the ability to translate vision into action. - Success Measures To be agreed with role specific assignments and career planning with the hiring manager. Thus we could have: Section Qualifications (education/experience): Bachelor's degree, 7-12 years experience, Systems Integration related projects, Strong understanding..., Knowledge of edge computing... Section Skills: Technical Skills list, Soft Skills list, Desirable BMS experience, Cloud platforms, Personal Attributes, Success Measures. But we also have "Requirements" heading allowed; we could put the essential qualifications under Requirements, and desirable under Skills? However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have both Requirements and Qualifications. But we need to avoid redundancy. Perhaps we treat Requirements as the essential qualifications (education, experience, etc.) and Qualifications as the desirable? Or vice versa. Let's think: Usually Requirements = mandatory qualifications; Qualifications = preferred qualifications. But we have both essential and desirable. So we could map: - Requirements: Essential items (Bachelor's degree, 7-12 years experience, Systems Integration related projects, Strong understanding..., Knowledge of edge computing..., Technical Skills basic understanding, Soft Skills...). Actually technical and soft skills are also essential? They are listed under Essential as part of Technical Skills and Soft Skills. So they'd be essential. - Qualifications: Desirable items (BMS experience, Cloud platforms certifications, Personal Attributes, Success Measures). That seems logical. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications. We will not have Skills separate because we already covered technical and soft skills under Requirements (essential). But we could still have Skills section for technical and soft skills if we want. However we already used them under Requirements. To avoid duplication, we can keep them under Requirements. Now we need to format lists. For About the role: we have two paragraphs: Company Overview and Job Description. We'll combine into maybe two

  elements. For Responsibilities: we need to output

  • for each bullet. The bullet points are long sentences; we need to keep them exactly as in the posting, but we need to ensure we don