Jobs · Nebraska

Engineering Team Lead

Thermo Systems · Omaha, NE · 1 mo ago
HybridFull-time
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. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Also remove "Visit us at ..."? That's maybe not boilerplate but could be considered promotional; but it's substantive? It's a link to learn more; maybe we can keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Visit us at ..." is not those; it's promotional but maybe keep? It's not required but could be considered part of "What You'll Get"? Actually it's separate line after benefits. Might be considered extra but not boilerplate. We could keep as a

maybe under Benefits? But better to keep as a separate paragraph maybe under a generic section? There's no heading for that. Could just include as a

after benefits. We need to parse the posting. Sections: - Who We Are: description of company. Could be "About the role"? Actually "Who We Are" is about company, not role. Could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for the role summary and maybe company description? The "Job Summary" is about role. "Who We Are" could be considered "About the role"? Might be better to treat "Who We Are" as "About the role" or maybe we could omit because not exactly role but still relevant. The instruction says prefer a few substantive sections over many thin ones. We could combine Who We Are and Job Summary under "About the role". Provide content. - Job Summary: description of role. - Education And Experience: could be "Qualifications" or "Requirements". We have Education And Experience and also Required Skills And Abilities. Also Supervisory Responsibilities etc. We need sections: Responsibilities (duties), Requirements (maybe education/experience), Qualifications (maybe similar), Skills, Benefits, Pay, Schedule. We have Duties And Responsibilities (with subcategories Technical Responsibilities, Customer Service, Project Responsibilities, Supervisory Responsibilities). That's definitely Responsibilities. We have Education And Experience: Bachelor of Science; etc. Typically 7+ years total experience. Proven Track Record: 3+ years as Control Systems Project Engineer I or equivalent. That's qualifications/requirements. We have Required Skills And Abilities: list of soft skills etc. We have Travel Required, On Call, Work Authorization/Other Requirements: these could be under Requirements or maybe separate but we don't have headings for those; we could incorporate into Requirements or Qualifications. We have Culture Model: description of core values; maybe could be under About the role or maybe omitted as boilerplate? It's not EEO but it's culture description; could be considered part of "About the role". Might keep. We have What You'll Get: Competitive salary, annual bonuses, 401(k) with company match, business travel reimbursement; Benefits: healthcare packages; Casual Dress; Training; Tuition Reimbursement; Vacation/Sick Time; Culture & Extras: free lunches, team bonding, swag. This is Benefits section. No explicit Pay or Schedule specifics besides "Competitive salary, annual bonuses". That's Pay info (salary). So we can create Pay section with that content. Schedule: not mentioned except maybe travel up to 50% overnight, on-call rotation. That's not schedule but could be considered Schedule? The instruction: only create Pay/Schedule/Benefits sections if posting actually states them. We have travel and on-call; not exactly schedule of hours. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section unless we have specific schedule info. We have "Travel Required Overnight travel may be required up to 50%" and "On Call On call rotation participation may be required based on location and client needs." That's not schedule but could be considered under Requirements or maybe a separate section like "Travel & On-Call". But we only allowed headings from list; we could put under Requirements or maybe under Responsibilities? Probably better to include under Requirements as additional requirements. Thus sections: - About the role (combining Who We Are and Job Summary) - Responsibilities (Duties And Responsibilities) - Requirements (Education And Experience + Work Authorization/Other Requirements + Travel Required + On Call) - Qualifications (maybe same as Requirements? But we need to avoid duplication. Could combine Education/Experience and Required Skills And Abilities into Skills? Actually Required Skills And Abilities is skills. So we can have Skills section for that. Qualifications could be education/experience. Let's decide: We have Education And Experience (qualifications). Required Skills And Abilities (skills). So we can have: - Qualifications (Education And Experience) - Skills (Required Skills And Abilities) - Responsibilities (Duties And Responsibilities) - Benefits (What You'll Get) - Pay (Competitive salary, annual bonuses, 401(k) with company match, business travel reimbursement) - (Optionally) Travel & On-Call could be under Requirements or maybe a separate section but not in list; we could add to Requirements. We must not create Pay/Schedule/Benefits unless posting actually states them. We have Pay info (competitive salary etc). Benefits info present. So we include Benefits and Pay. We must not include Schedule because no explicit schedule. Now we need to output HTML fragment with

headings and appropriate
  • for lists,

    for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details like specifics of duties etc. We need to be careful to not duplicate lines. Let's extract content. Who Are: "Thermo Systems is a global, full-service control systems integration partner, delivering world-class automation solutions in the District Energy, Life Sciences, and Mission Critical markets. Our diverse leadership and dedicated engineering team are committed to excellence and consistent growth. Our unique company culture, known as 'The Thermo Way,' strengthens our team by fostering an environment where all members perform their best. Our commitment to being unified, dynamic, and delivering excellence is evident in how we build trusting relationships through connection and camaraderie, ability to adapt, and focus on integrity and success. These values guide our daily operations and interactions, setting the standard for our team's behavior. As we continue to grow and evolve, 'The Thermo Way' supports our goals of becoming a world-class organization, ensuring employee success, customer success, and financial strength." Job Summary: "Works on a variety of control system projects. Capable of leading several project related tasks and/or large projects in their entirety. Provides engineering support on projects led by others. Assumes ultimate responsibility for the assigned projects/tasks. Leads and develops a team. Takes direction and seeks guidance from the assigned project leads, the supervisors, and company leadership." Combine under About the role. Now Responsibilities: Duties And Responsibilities with subcategories. We need to list each duty as

  • maybe grouped under headings? But we only have

    for section headings; inside we can have

    or

    • . The duties are many; we can make a
        with each duty as
      • . However there are subheadings like Technical Responsibilities, Customer Service, Project Responsibilities, Supervisory Responsibilities. We could either keep them as

        headings inside the section (maybe ) but not required. To preserve detail, we could keep them as

        headings then

          . But the instruction only says use

          for section headings; doesn't forbid other headings inside. We can use

          for prose and

          • for lists. For subheadings we could use

            Technical Responsibilities:

            then list. We must preserve all duties. Let's list them: Technical Responsibilities: - Lead, train, and mentor co-workers during start-up and commissioning of systems. - Expert in reading and interpreting piping & instrumentation diagrams and wiring diagrams. - Able to provide feedback regarding field conditions versus drawings. - Experienced with creating and editing Human-Machine Interface (HMI) and Programmable Logic Controller (PLC) applications. - Expert in understanding, practicing, and guiding others in the company’s Quality Management System (QMS). - Firm understanding of complex control system design. - Provide instrumentation specifications for complex control systems. - Value engineer specifications to provide the most cost-effective solutions. - Leads detailed design of Information Technology (IT) systems, network infrastructure, and computer system designs, as it relates to control system integration. Customer Service: - Communicate in an effective, positive, and proactive manner with customers. - Follow customer specific site standards and procedures. - Always conduct business in professional manner. - Provide excellent customer care and support. - Be patient, attentive, and responsive to customers in solving their problems. - Always follow up and honor commitments with customers. Project Responsibilities: - Complete assigned tasks accurately, on schedule, and under budget. - Lead individual project related tasks and/or small to mid-sized projects in their entirety. - Assume the ultimate responsibility for the successful completion of those projects or tasks on schedule and under budget. - Take on the role of the customer’s main contact on those projects that the employee is assigned to lead. - Identify changes in scope to overall projects and/or tasks. - Provide support on other projects or tasks that are scheduled to be led by others. - Manage and delegate assigned tasks accurately, on schedule, and under budget. - Understands and anticipates customer needs. - Accurately estimates the duration and difficulty of tasks. - Ensures the team adheres to a realistic schedule and budget. - Understands project invoicing and projection procedures. Supervisory Responsibilities: - Directly responsible for team members training and development. - Provides constructive feedback to team members. - Manages team members compensation and time off. - Ensure team members are effectively assigned to project tasks. - Manages performance and retention of team members. - Resolves conflicts within team. Now Requirements: Education And Experience + Work Authorization/Other Requirements + Travel Required + On Call. Education And Experience: - Bachelor of Science; Electrical Engineering, Mechanical Engineering, Computer Science, or other pertinent curriculum combined with relevant technical experience. - Typically, 7+ years total experience. - Proven Track Record: 3+ years as Control Systems Project Engineer I or equivalent. Work Authorization/Other Requirements: - Proof of eligibility to work in the country where the position is located is required. - Maintain a valid driver's license. - Fit for Duty at all times. Travel Required: - Overnight travel may be required up to 50%. On Call: - On call rotation participation may be required based on location and client needs. We could combine these into a
              list. Now Qualifications: maybe we already used Education/Experience as Qualifications. But we also have Required Skills And Abilities as Skills. Thus Qualifications section: Education And Experience (maybe we could rename to Qualifications). We'll put the same content. Skills section: Required Skills And Abilities list: - Viewed by others as trustworthy. - Listens well. - Understands needs and desires of others. - Continually provides the big picture of a project or task. - Committed to further developing managerial and leadership skills. Now Benefits: What You'll Get includes: - Competitive salary, annual bonuses, 401(k) with company match, and business travel reimbursement: We appreciate our employees, and we make sure they know it. - Benefits: We offer full-time employees multiple healthcare packages, including low-cost options. - Casual Dress: Every day is "Casual Friday"; we want you to be comfortable when you come to work. - Training

Similar jobs

Engineering Team Lead

VizientEdina, MN· 2 mo ago
Engineering$118k–$206k/yrapply on careers.vizientinc.com

Engineering Team Lead

M&T BankBuffalo, NY· 2 mo ago
Engineering$146k–$156k/yrapply on mtb.wd5.myworkdayjobs.com