Controls Technical Leader

We need to output HTML fragment with sections: About the role? The posting includes description about company and role. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have content: The posting includes a description about company and role (intro). Could be "About the role". Then responsibilities: "What You Will Do" list. Then qualifications/requirements: "Qualifications/Requirements" and "Desired Qualifications". Also "What You Will Bring" is responsibilities? Actually "What You Will Bring" seems like responsibilities/duties. So we can treat that as responsibilities. We have Pay Range: $100,000 - $130,000. So Pay section. We have Benefits: list of benefits. We have Work Requirements (Onsite): location, commute, shop floor, lift 40 lbs, travel 10-15%, citizenship. That could be Schedule? Actually schedule not given. Could be "Work Requirements" maybe not a standard heading. The allowed headings are limited to those list. We could put location etc under "About the role" or maybe "Responsibilities"? But we have no Schedule specifics. So we should not create Schedule section unless posting states schedule (like full-time, hours). It mentions Full-time (Regular) in benefits but not schedule details. Could treat "Work Requirements" as part of "About the role". Or we could create a "Schedule" section only if we have schedule info; we don't. So omit Schedule. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive info. We need to use

for section headings. Use

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

  for prose. We must not repeat job title as heading. Not include Job ID. We need to output only HTML fragment. Let's craft sections:

  About the role

  Quest Global delivers world-class end-to-end engineering solutions ... (the introductory paragraph up to "If you want to contribute to meaningful work and be part of an organization that truly believes when you win, we all win, and when you fail, we all learn, then we’re eager to hear from you.") That's a paragraph. But we need to preserve all substantive info; we can include that entire intro as a paragraph. Then responsibilities: combine "What You Will Do" and "What You Will Bring" maybe as a single responsibilities section with bullet list. We need to list each duty as

• . The responsibilities list is long; we need to capture each bullet point. Let's extract responsibilities from "What You Will Do": - Lead and mentor team responsible for Control and Monitoring, and DCS development associated plant cross- disciplinary and cross- systems simulation. - Focus on work planning, technical approach, design assurance, and execution excellence on new build and modernization projects. - This role supports our customer at GE Hitachi Nuclear Then "What You Will Bring" list items (many). We'll treat each sentence as a bullet. We need to be careful not to lose any detail. Let's copy the "What You Will Bring" text: Lead integrated approaches and solutions across the diverse plant disciplines or specialties of Control and Monitoring, DCS systems, and Instrumentation associated plant cross- disciplinary and cross- systems simulation Coordinate matrixed cross- disciplinary Engineering teams to assess work product or support requests, analyze plant system requirements, operations and maintenance goals, possible I&C and DCS architectures, equipment selection, phased implementations, develop list of clarifications and exceptions, prepare proposals with scope, conformance matrix and risk scorecard, work plans, cost estimates, and schedules Lead preparation of high thru low work planning, scheduling, and resource loading across lifecycle phases of Engineer-Procure-Construct or new product introduction using the applicable practices, guides, and tools Support project engineering or manager with understanding execution metric and status, issues, risks, mitigation or recovering plans, and be extremely proactive to identify changes in scope Drive compliance utilizing scope, work plan, budget, overall schedule, applicable design processes, and discipline specific practices and tools including design and technical reviews Lead “day-to-day” operations and follow-up to ensure deliverables are produced and commitments met on-spec., on-budget, and on-schedule Collaborate proactively and inclusively for overall team across other engineering disciplines to support integrated plant design objectives Collaborate with project management, project engineering, support functions, and others to drive project completion Identify, confirm, document, and lead resolution of technical, risk, other emergent issues Provide technical oversight and mentorship to ensure system designs and deliverables comply with requirements throughout design release to manufacturing or supplier including production, validation, installation, and commission tests Support strategy, plan, statement of work preparation, and implementation of resource loading and mobilization involving employees, staff augmentation contractors, suppliers and partners including other GEV entities Assist with hosting learning sessions, knowledge capture, and transfer initiatives Champion conformance with regulations and guides, standard review plans, branch technical positions, interim staff guidance, information notices and summaries, bulletins, orders, applicable nuclear guidance, and industry standards Use variety of tools for requirements, design, change, configuration, and document management Support simplification, continuous process improvement, and cost-out Champion nuclear safety culture; Ensure compliance with GEH policies, quality management system, and corrective action program Deliver work with integrity, safety, security, quality, and on-time output Now qualifications/requirements: we have "Qualifications/Requirements" block with bullet-like sentences. Also "Desired Qualifications". We'll combine into Requirements section maybe split into Required and Desired? But headings limited to Requirements, Qualifications, Skills. We could use Requirements for mandatory, Qualifications for desired, Skills for desired skills? However we need to avoid thin sections. Perhaps combine all into Requirements section with sub-bullets? But we must follow instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can have multiple of those headings if content exists. So we can have Requirements (mandatory), Qualifications (desired), Skills (maybe from desired qualifications). But we need to ensure we don't create thin sections with filler. We have plenty of content for each. Let's parse: Mandatory qualifications (under "Qualifications/Requirements"): - Bachelor of Science in Engineering, Physics, Chemistry, Computer Science, or Mathematics or equivalent 4-year technical degree - 10 years experience in heavy industrial, thermal power, or nuclear industry working in plant instrumentation application, control and monitoring system design, digital control system (DCS), networking, and data communications architecture definition including requisition engineering, implementation, test, installation, and commissioning - 10 years experience in application engineering, field installation, and test engineering of systems, equipment, and components including selection, sizing calculations, and equipment qualification to diverse industry standards - 7 years experience in the nuclear industry product family system design, plant engineering, maintenance, modifications, new plant design certification, and licensing - 7 years experience in combination of; requirements management, system design, application or requisition engineering, analysis, modeling and simulation, change, configuration, collaboration, and document management, and technical reviews related to nuclear or process instrumentation, data acquisition, monitoring, control, electrical distribution systems and equipment - 5 years experience performing independent, or preferably team based, system design or technical reviews including interfacing with requirements management, independent verification and validation, and systems and software quality assurance organizations - 5 years excellent knowledge, skill, and experience with PC and desktop engineering productivity software, computer aided design or analysis and modelling, and project collaboration tools Desired Qualifications (list): - Master of Science in Engineering, Physics, Chemistry, Computer Science, or Mathematics or equivalent 4-year technical degree - Professional Engineer - Experience with schedule, planning, and tracking activities with schedule tools (e.g., Microsoft Project, Oracle Primavera P6, JIRA, etc.) - Experience in nuclear analog and digital instrumentation, control, monitoring, electric power system and field engineering with working knowledge in safety-related, significant to safety, and non-safety-related systems, hardware, software, theory of operation, instrument set point and calibration methodologies, equipment environmental and seismic testing and qualification - Experience in US and international nuclear regulatory affairs, licensing, laws, rules, regulations, guidance, etc. applicable to power and test reactors - Competency in industry standards IEEE, IEC, and quality standards - Competency in industrial controls networking, data communications architectures, and protocols - Competency in modeling, simulation, and test data collection tools (e.g., WSC 3KEYMASTER, GE Mark*VIe virtual controller, Siemens SIMATIC S7 series, etc.) - Clear thinker, detail oriented, insightful, quantitative, balanced, and a results-oriented analyst and leader - Self-starter with energy, positive “Can-Do” attitude and inclusive style – Proven track record of delivering commitments on specification, on budget, and on schedule - Strong verbal communication, as well as, facilitation and presentation skills for technical and business audiences – Able to communicate openly, calmly, and crisply in stressful situations - Adaptive; able to quickly learn diverse and varying organizational interfaces with professional astuteness - Continuous improvement “mindset” with an ability to identify, influence, and implement better ways to do an activity or process - Solid PC, as well as, personal and team productivity software - Solid technical writing skills with focus on requirements and design documents - Working knowledge, expertise, and experience using LEAN/Agile, six sigma design for reliability, failure modes and effects analysis, and design to cost techniques and tools) We could treat these as Skills section. But we also have "Skills" heading allowed. So we could put the desired qualifications under Skills. However some are more like qualifications (education, certifications). But we can split: Requirements = mandatory qualifications; Qualifications = desired qualifications (education, certifications); Skills = desired skills (competencies, soft skills). That seems reasonable. Now Benefits: list includes Full-time (Regular) 401(k) 401(k) matching Dental insurance Health insurance Life insurance Paid time off Referral program Vision insurance Short/Long Term Disability We need to output as

  • each. Pay: we have Pay Range: $100,000 - $130,000 plus note about compensation decisions. We'll include that as

    maybe. Schedule: we have no explicit schedule (like hours). We have Work Requirements (Onsite) with location, commute, shop floor, lift 40 lbs, travel 10-15%, citizenship. This could be placed under About the role or maybe a separate section like "Work Requirements" but not allowed. Could incorporate into About the role paragraph. But we already have About the role paragraph with company description; we could add another paragraph about work requirements. However we must not create a Schedule section. So we can add a second

    under About the role covering location, commute, etc. Or we could create a separate section like "Work Requirements" but not allowed. So we will add to About the role. Thus About the role will have multiple paragraphs: first about company mission, second about work requirements (location, etc). That's fine. Now we need to ensure we don't repeat job title. Not present. Now produce HTML. Let's craft:

    About the role

    Quest Global delivers world-class end-to-end engineering solutions by leveraging our deep industry knowledge and digital expertise. By bringing together technologies and industries, alongside the contributions of diverse individuals and their areas of expertise, we are able to solve problems better, faster. This multi-dimensional approach enables us to solve the most critical and large-scale challenges across the aerospace & defense, automotive, energy, hi-tech, healthcare, medical devices, rail and semiconductor industries. We are looking for humble geniuses, who believe that engineering has the potential to make the impossible possible; innovators, who are not only inspired by technology and innovation,