Jobs · Engineering · Texas

Water Process Integration & Solutions Architect

Yokogawa · Sugar Land, TX · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: About The Team (maybe About the role?), DUTIES / RESULTS (Responsibilities), Education & Core Qualifications (Qualifications/Education), Technical Skills & Experience (Skills), ATTRIBUTES (maybe Skills or Qualities), TRAVEL (maybe Schedule? Actually travel is not schedule but could be part of schedule? The instruction says include Schedule only if posting actually states schedule; travel is not schedule. So we may not include Schedule. Benefits? Not mentioned. Pay? Not mentioned. So we will include sections: About the role (maybe "About The Team" qualifies as about the role?), Responsibilities (DUTIES / RESULTS), Qualifications (Education & Core Qualifications), Skills (Technical Skills & Experience + ATTRIBUTES maybe combine?), but we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. We need to map content accordingly. - About the role: could be the introductory paragraph about Yokogawa and the team. We'll include that. - Responsibilities: DUTIES / RESULTS list. - Requirements: maybe Education & Core Qualifications (minimum degree, experience). Could be considered Requirements. - Qualifications: maybe same as Requirements? But we need distinct sections; maybe we can put Education & Core Qualifications under Qualifications, and Requirements could be something else like "Experience" but we don't have separate. Could combine? But we must not create empty sections. We could put Requirements as the same as Qualifications? Might be duplication. Better to treat Education & Core Qualifications as Qualifications, and Requirements as maybe "Experience" but we don't have separate heading. However we could treat "Requirements" as the same as Qualifications but that would be duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So we could skip Requirements if not distinct. But we need to include sections only when posting has real specific content for it. So we can omit Requirements if we don't have distinct content. However we have Education & Core Qualifications which could be considered Qualifications. So we will have Qualifications section. - Skills: Technical Skills & Experience plus ATTRIBUTES (maybe combine). We'll put under Skills. - Benefits: none -> omit. - Pay: none -> omit. - Schedule: none -> omit (travel not schedule). Thus we will output sections: About the role, Responsibilities, Qualifications, Skills. We need to use

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

    for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from DUTIES/RESULTS, Education & Core Qualifications, Technical Skills & Experience, ATTRIBUTES, and maybe the introductory paragraphs. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip the EEO paragraphs at end, also the referral line, etc. We need to keep the travel? Travel is not a section we include; but maybe we could include it under Skills? No. Travel is not a duty/requirement/benefit; it's a condition. Could be considered part of Requirements? But we don't have a Requirements section. Could we include travel under Qualifications? Probably not. The instruction says we should not create sections unless posting has real specific content for it. Travel is specific content but we don't have a heading for it. Could we include it as a

    under Qualifications or Skills? It's not really a skill. Might be better to include a short paragraph under Qualifications? But that would be mixing. Perhaps we can include a separate section "Travel" but not in allowed headings list. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; maybe we can also use other headings if needed? 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, not exhaustive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create a heading for Travel if we want, but it's not in the examples. Safer to stick to the given headings. Travel could be considered part of Schedule? Not exactly. But we could treat travel as part of Schedule? The posting says "Ability to travel up to 50% of the time, including domestic and international business trips. A valid passport is required." That's more like a requirement. Could be placed under Requirements (if we had that section). Since we don't have Requirements, maybe we can put it under Qualifications as a bullet? But Qualifications is for education/degrees/experience. Travel is not a qualification. Could be under Skills? Not really. Maybe we should include a Requirements section after all, to capture education, experience, travel, etc. Then Qualifications could be for preferred qualifications? But the posting lumps Education & Core Qualifications (minimum is bachelor's, advanced degree preferred, 10+ years experience, etc.) That's both education and experience. That could be Requirements. Then Qualifications could be for preferred qualifications like advanced degree, participation in associations, etc. But the posting also has "Technical Skills & Experience" and "ATTRIBUTES". So we could map: - About the role: intro paragraphs. - Responsibilities: DUTIES / RESULTS. - Requirements: Education & Core Qualifications (minimum bachelor's, 10+ years experience, etc.) - Qualifications: maybe "Advanced degree preferred; active participation in relevant associations preferred; experience in priority markets preferred." But those are already in Education & Core Qualifications (they say advanced degree preferred; active participation preferred; experience in priority markets preferred). Actually those are within Education & Core Qualifications. So maybe we don't need separate Qualifications. - Skills: Technical Skills & Experience + ATTRIBUTES. Thus we have About the role, Responsibilities, Requirements, Skills. We need to ensure we include all substantive info: the introductory paragraphs about Yokogawa, award winner, mission, team, etc. Also the "About The Team" paragraph. We must not repeat the job title as a heading (the page already shows it). So we don't add a heading for job title. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: EEO paragraphs, referral line, etc. Let's extract content: Intro: "Not just a job, but a career Yokogawa, award winner for ‘Best Asset Monitoring Technology’ and ‘Best Digital Twin Technology’ at the HP Awards, is a leading provider of industrial automation, test and measurement, information systems and industrial services in several industries. Our aim is to shape a better future for our planet through supporting the energy transition, (bio)technology, artificial intelligence, industrial cybersecurity, etc. We are committed to the United Nations sustainable development goals by utilizing our ability to measure and connect. About The Team Our 18,000 employees work in over 60 countries with one corporate mission, to "co-innovate tomorrow". We are looking for dynamic colleagues who share our passion for technology and care for our planet. In return, we offer you great career opportunities to grow yourself in a truly global culture where respect, value creation, collaboration, integrity, and gratitude are highly valued and exhibited in everything we do." That's the about the role. DUTIES / RESULTS bullet list (each line starts with a verb). We need to preserve all. List: - Guide the company in the structuring of acquisitions, investments, partnerships to deliver on the strategic water vision. - Providing structured insights into sequencing of these activities to ensure that the process is economically sound and de-risked. - Develop clear value propositions and business cases that quantify customer outcomes, including water savings, energy reduction, operating efficiency, compliance improvement, asset reliability, production resilience, and resource recovery. - Support the company in the design, evaluate, and optimize complete treatment trains that may include biological treatment, membrane separation, desalination, water reuse, resource recovery, sludge processing, and brine management. - Provide clear economic insights into technology adoption and end user value to aide in market positioning and strategy development. - Translate customer production, water, energy, labor, reliability, and regulatory challenges into clear technical requirements and solution concepts. - Advise on the integration of process technologies with instrumentation, control systems, SCADA, DCS, advanced process control, digital twins, analytics, AI-enabled optimization, and asset performance solutions. - Provide technical leadership for customer discovery, workshops, concept development, feasibility studies, proposals, pilots, and proof-of-concept activities. - Support the assessment of emerging water technologies, strategic partners, and acquisition targets for technical fit, integration potential, scalability, operating risk, and commercial value. - Create repeatable solution architectures, application playbooks, and portfolio roadmaps that support commercialization and adoption across Yokogawa. - Collaborate with sales, engineering, R&D, digital, automation, services, and business leadership to advance qualified opportunities and deliver integrated solutions. - Build productive relationships with customers, engineering firms, universities, research institutes, technology providers, and industry associations. - Monitor regulatory developments, market needs, competitor behavior, and technology trends, and translate these insights into portfolio and business recommendations. - Support business planning, sales enablement, investment decisions, and executive communication. - Provide periodic reporting on activities, opportunities, risks, and outcomes while remaining fiscally responsible and compliant with company guidelines. Note some lines start with gerunds (Providing, Support, etc). We'll keep as is. Education & Core Qualifications: "Minimum is a bachelor’s degree in chemical, environmental, civil, mechanical, water resources, or a related engineering or scientific discipline. An advanced degree is preferred; equivalent demonstrated experience may be considered.10+ years of progressively responsible experience in water, wastewater, desalination, water reuse, resource recovery, or industrial water treatment.Demonstrated experience integrating multiple process technologies into complete customer solutions rather than focusing solely on a single product or unit process.Experience supporting complex municipal or industrial projects through concept development, design, commercialization, deployment, or operations.Ability to develop and communicate CAPEX, OPEX, total-cost-of-ownership, risk, and value tradeoffs.A strategic mindset with the ability to contribute to portfolio planning, partnerships, acquisitions, and business development.Active participation in relevant water, wastewater, industrial, or engineering associations is preferred." We need to preserve spacing; but we can format as paragraphs or list. Since it's a list of requirements, we can use
    • for each bullet. However the original is not bulletized but sentences. We could split into items. The instruction: Use
      • for any list of duties/requirements/benefits. So we should treat these as a list of requirements. We'll split each sentence into an
      • . Need to ensure we don't lose any detail. Sentences: 1. Minimum is a bachelor’s degree in chemical, environmental, civil, mechanical, water resources, or a related engineering or scientific discipline. 2. An advanced degree is preferred; equivalent demonstrated experience may be considered. 3. 10+ years of progressively responsible experience in water, wastewater, desalination, water reuse, resource recovery, or industrial water treatment. 4. Demonstrated experience integrating multiple process technologies into complete customer solutions rather than focusing solely on a single product or unit process. 5. Experience supporting complex municipal or industrial projects through concept development, design, commercialization, deployment, or operations. 6. Ability

Similar jobs