Jobs · Engineering · Indiana

CAE Engineer III, Pump Development

Franklin Electric · Fort Wayne, IN · 4 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. First, we need to extract sections. The posting includes: - Department: Engineering - Location: US - Indiana - Fort Wayne - Description: Primary responsibility ... (some prose) - Key Responsibilities (list) - Skills Knowledge and Expertise Skills and Abilities (list) - Education and Experience: (list) - Computer Skills: (list) - Then a paragraph about diversity, encouraging apply. - Then "Why Work at Franklin Electric?" with benefits description. We need to map to headings: About the role (maybe description), Responsibilities (key responsibilities), Requirements (maybe education/experience?), Qualifications (maybe skills?), Skills (maybe computer skills?), Benefits (why work at Franklin Electric?), Pay (none), Schedule (none). We should only include sections with real content. We need to preserve all substantive info, not invent. We must not repeat job title as heading (none given). No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a diversity encouragement paragraph and "Why Work at Franklin Electric?" which is benefits-ish. We'll keep that as Benefits. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. We need to decide which content goes where. Let's extract: About the role: The description paragraph(s) before Key Responsibilities: "Primary responsibility is to efficiently use computer-simulated models to analyze the behavior of fluids and fluid flow in rotodynamic pump applications. Additionally, the position will use CAE models to evaluate product structural mechanics of new designs in motor and pump applications. This position will use the principles of fluid and structural mechanics to simulate how air, water, and other liquids interact with physical barriers and analyze the results to come up with solutions to complex engineering problems. Adept at leveraging cutting edge technologies to develop innovative solutions for complex engineering projects." That's prose. We'll put in

    . Responsibilities: The bullet list under "Key Responsibilities". Let's extract each line: - Demonstrate thorough knowledge of fluid dynamics and heat transfer as required for hydraulic CFD analysis and optimization. - Establish design solutions to improve product performance and reliability from CFD/FEA simulation results. - Ability to think out of the box and be able to work in cross-functional team. - Including planning and executing simulation activity, developing design solutions to meet performance targets, collaborating with design engineering on their feasibility, and root cause resolution of issues discovered during validation testing. - Prepare and present technical presentations. - Develop computational models to simulate fluid flow, heat transfer, structural, vibration, or impact simulation. - Collaborates with other Global Engineering teams on various engineering projects. - Provides technical support in discussions of simulation tools, design reviews, DFMEA, and validation planning and execution. - Participates in a cross-functional and cross-cultural team environment. - Analyzes computational technology, resource needs, and market demand to plan and assess the feasibility of projects. - Establishes individual engineering priorities to support the test plan schedule. - Performs other related duties as required or assigned. We need to put each as

  • inside
      . Requirements: Possibly Education and Experience? The heading "Requirements" could be used for education/experience. But we also have "Qualifications". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide mapping. We have Education and Experience: Bachelor’s degree in engineering or a related technical field (required). Master’s degree in Hydraulic Design or related CAE field of study (preferred). Ten or more years of related experience (Master’s degree in a relevant field could substitute for years of experience.) That's qualifications/requirements. Could go under Requirements or Qualifications. Since we have both headings, we need to decide which content fits each. Usually Requirements = education/experience, Qualifications = skills/knowledge. But we also have a separate "Skills Knowledge and Expertise Skills and Abilities" section. That seems like skills. Then "Computer Skills" is also skills. Thus we could map: - Requirements: Education and Experience. - Qualifications: maybe the "Skills Knowledge and Expertise Skills and Abilities" (the list of skills/abilities). - Skills: Computer Skills (specific software). But we need to avoid duplication. The posting also includes "Skills Knowledge and Expertise Skills and Abilities" which is a long list of skills/abilities. Then "Computer Skills" separate. Thus we can have: Requirements: Education and Experience (as
        ). Qualifications: Skills Knowledge and Expertise Skills and Abilities (as
          ). Skills: Computer Skills (as
            ). Benefits: Why Work at Franklin Electric? paragraph. Pay: none -> omit. Schedule: none -> omit. We also have Department and Location info. Should we include that? It's metadata; we could fold into a short

            under About the role maybe. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

            or drop it." So we can include Department and Location in a short paragraph maybe under About the role or separate? Probably include as a short

            after About the role? But we need to preserve all substantive information. Department and Location are substantive. We'll include them as a short

            maybe before About the role? But we need a heading for About the role. We could have About the role heading, then a

            that includes the description plus department/location? Or we could have a separate

            for metadata. The instruction: "fold minor metadata into a short

            or drop it." So we can create a short

            for Department and Location. Thus structure:

            About the role

            Primary responsibility is to efficiently use computer-simulated models to analyze the behavior of fluids and fluid flow in rotodynamic pump applications. Additionally, the position will use CAE models to evaluate product structural mechanics of new designs in motor and pump applications. This position will use the principles of fluid and structural mechanics to simulate how air, water, and other liquids interact with physical barriers and analyze the results to come up with solutions to complex engineering problems. Adept at leveraging cutting edge technologies to develop innovative solutions for complex engineering projects.

            Department: Engineering. Location: US - Indiana - Fort Wayne.

            Then Responsibilities. Then Requirements (Education/Experience). Then Qualifications (Skills Knowledge and Expertise). Then Skills (Computer Skills). Then Benefits (Why Work at Franklin Electric?). We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract the lists precisely. Responsibilities list: we need to capture each bullet as given. Some lines start with verb, some are fragments. We'll keep as is. Let's copy them exactly: - Demonstrate thorough knowledge of fluid dynamics and heat transfer as required for hydraulic CFD analysis and optimization. - Establish design solutions to improve product performance and reliability from CFD/FEA simulation results. - Ability to think out of the box and be able to work in cross-functional team. - Including planning and executing simulation activity, developing design solutions to meet performance targets, collaborating with design engineering on their feasibility, and root cause resolution of issues discovered during validation testing. - Prepare and present technical presentations. - Develop computational models to simulate fluid flow, heat transfer, structural, vibration, or impact simulation. - Collaborates with other Global Engineering teams on various engineering projects. - Provides technical support in discussions of simulation tools, design reviews, DFMEA, and validation planning and execution. - Participates in a cross-functional and cross-cultural team environment. - Analyzes computational technology, resource needs, and market demand to plan and assess the feasibility of projects. - Establishes individual engineering priorities to support the test plan schedule. - Performs other related duties as required or assigned. Note: Some lines start with lowercase? We'll keep as is. Now Qualifications list: "Skills Knowledge and Expertise Skills and Abilities". The text after that heading: "New product development experience from concept to production. Experience in developing new or derivative designs of motors, pumps, or other turbomachinery. Assist in all stages of the Fluid-dynamic, Thermodynamic and Heat Transfer design analysis within the Franklin Electric Global Engineering Team. Extensive working knowledge of a CAD system (ProE/CREO preferred). High level of analytical ability for difficult / complex technical problems. Strong interpersonal skills and ability to work effectively with others. Manages large and complex development projects. Demonstrates a track record of successful projects. Analyzes information and evaluates results to choose the best solution and solve problems. Understands complex analytical tools such as finite element analysis, computational fluid dynamics analysis, parametric modeling, electric motor design and analysis, and complex mathematical analysis programs. Analyzes information and evaluates results to choose the best solution and solve problems. Maintains confidentiality and uses discretion with business information. Writes routine reports and correspondence. Deals with problems involving several known variables in situations of routine nature. Plans the time, method, manner, and/or performance sequence of own work; may also occasionally assist in planning work assignments performed by others within a limited area of operation." Note there is a duplicate line "Analyzes information and evaluates results to choose the best solution and solve problems." appears twice. We should keep both? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines are present in source; we should keep them as they are (though they are duplicated). We'll keep both. Now Computer Skills list: "Advanced: Pro-E (CREO) CAD software required ANSYS CFx and FLUENT experience required ANSYS Mechanical experience required" We need to format as list items. Now Benefits: "Why Work at Franklin Electric? Becoming a part of the Franklin Electric team not only provides outstanding benefits, it also opens doors to opportunities for future growth. Enjoy peace of mind with a world-class company. But more importantly, be satisfied in knowing you make a difference. Take a look at this video to see our Global Headquarters here in Fort Wayne, Indiana." We need to keep that as prose under Benefits heading. Now we need to ensure we don't include any boilerplate like diversity encouragement paragraph: "Don’t feel like you check all the boxes in the job description? Here at Franklin Electric, we are dedicated to building a diverse and inclusive culture which includes embracing candidates from a variety of different backgrounds and industries. We highly encourage you to apply so we can connect on this and future opportunities." That's application encouragement; we should remove as per instruction: remove application instructions. So we drop that paragraph. Also we should drop any duplicated lines? Already we kept duplicates as they are in source; but we might consider removing duplicate lines if they are exactly same? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It says remove duplicated lines. So we should remove duplicated lines. The duplicate line "Analyzes information and evaluates results to choose the best solution and solve problems." appears twice. We should remove one instance. We'll keep only one. Also there may be other duplicated lines? Not obvious. Thus we will deduplicate that line. Now we need to output only HTML fragment, no markdown fences. Let's craft. We'll start with

            About the role

            then

            description. Then

            Department: Engineering. Location: US - Indiana - Fort Wayne. Then

            Responsibilities

              with each
            • . Then

              Requirements

                for education/experience. Then

                Qualifications

                  for skills knowledge. Then

                  Skills

                    for computer skills. Then

                    Benefits

                    benefits text. Make sure no extra whitespace issues. Let's write

Similar jobs

Pump Engineer

Direct Energy BusinessHouston, TX· 3 mo ago
Engineeringapply on careers.nrgenergy.com

Fluids Design Engineer III

Blue OriginMerritt Island, FL· 1 mo ago
Information Technology$121k–$169k/yrapply on blueorigin.wd5.myworkdayjobs.com

Fluids Design Engineer III

Blue OriginGreater Seattle Area· 2 mo ago
Engineering$121k–$169k/yrapply on blueorigin.wd5.myworkdayjobs.com

Fluids Engineer III

Blue OriginDenver, CO· 3 mo ago
Engineering$111k–$155k/yrapply on blueorigin.wd5.myworkdayjobs.com