Control Systems Engineer
Caterpillar Inc. · Mossville, IL · 1 mo ago
Engineering$98k–$146k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes "Summary Pay Range: $97,530.00 - $146,290.00". Also "This position requires working onsite five days a week." That's schedule. Benefits listed. So we need sections: About the role (maybe "About IPSD" or "About the role"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We have "About IPSD" describing division. Could be "About the role" includes the description of role and what you will do. Also "Responsibilities" could list the bullet points under "What You Will Do". "Requirements" could include degree requirement. "Qualifications" maybe the list of skills/knowledge (Analytical Thinking, Communicating Complex Concepts, etc). "Skills" maybe the embedded systems etc. But we need to avoid duplication. Let's parse content:
- Intro paragraph about Caterpillar.
- About IPSD description.
- Role Definition: seeking Controls System Engineer to design, develop, improve electro-mechanical systems...
- What You Will Do: list of designing advanced electrical control systems..., designing and implementing software..., designing and prototyping mechatronic devices..., identify and address areas of product weakness...
- Degree Requirement: requires a degree from accredited engineering program in mechanical, electrical, or related field.
- What You Will Have: list of competencies with sub-bullets (Analytical Thinking, Communicating Complex Concepts, Problem Solving, Embedded Systems, Technical Troubleshooting). Each has "Level Working Knowledge:" and bullet points.
- Additional Information: Relocation assistance available, Sponsorship available, ISE assignment not available.
- Then company description.
- Summary Pay Range: $97,530.00 - $146,290.00
- Benefits list.
- This position requires working onsite five days a week.
- Visa sponsorship is available for eligible applicants.
- Posting dates etc (boilerplate to remove).
- Drug screen, EEO etc (remove).
We need to output only HTML fragment, no markdown fences.
We need to decide sections:
- About the role: could combine the introductory paragraph about Caterpillar and IPSD description and role definition. But we must not repeat job title. Use prose
.
- Responsibilities: list of "What You Will Do" items.
- Requirements: degree requirement.
- Qualifications/Skills: maybe combine the "What You Will Have" competencies. Could be "Skills" section listing those competencies. Or "Qualifications". The instruction says use headings like Qualifications, Skills. We can have both if content distinct. But we have a list of competencies each with subpoints. Could treat as "Skills" section with subheadings? But we only allowed
for section headings, not nested headings. Could use - for each competency and inside
- for subpoints? Might be okay to nest lists. But we need to preserve all substantive info. Could flatten: each competency as a list item with its description (including subpoints). Could use
inside
- for subpoints? Might be messy.
Simplify: create a "Skills" section with
- each competency title and its description (including Level Working Knowledge and bullet points). Use
inside
- for the description? Might be okay but not specified. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for a list of skills, we should use
- . Inside each
- we can have prose (
) if needed. That seems acceptable.
Similarly for Responsibilities: list of duties.
For Requirements: maybe just a
(single requirement) or
- if multiple (only degree). Could be
.
For Benefits: list of benefits.
For Pay: we have pay range. Could be a
under Pay heading.
For Schedule: we have "This position requires working onsite five days a week." Could be a
under Schedule heading.
We also have relocation assistance, sponsorship available, visa sponsorship. Those could be under Additional Information but not a standard heading. Could maybe include under "Benefits" or "Additional Information". But instruction says only include sections when posting has real, specific content for it. We could add a section "Additional Information" but not in the list of allowed headings? The list includes examples but not exhaustive. Could add "Additional Information" as
. Might be okay. But we might incorporate those details into Benefits or other sections. Relocation assistance and sponsorship are benefits-ish. Could add to Benefits list. Visa sponsorship also similar.
Thus Benefits list can include: Medical, dental, vision; Paid time off; 401(k); HSA; FSAs; Health Lifestyle Programs; Employee Assistance; Voluntary Benefits and Employee Discounts; Career Development; Incentive bonus; Disability benefits; Life Insurance; Parental leave; Adoption benefits; Tuition Reimbursement; Relocation assistance; Sponsorship available; Visa sponsorship for eligible applicants. Also note "These benefits also apply to part-time employees". Could add as note.
We must not include boilerplate like "Posting Dates", "Any offer of employment is conditioned upon...", EEO, etc.
Now construct HTML.
Start with About the role
then
containing the introductory paragraphs: "Your Work Shapes the World at Caterpillar Inc...." plus IPSD description plus Role Definition. Combine into prose.
Then
Responsibilities
then - each duty.
Duties from "What You Will Do:":
- Designing advanced electrical control systems and integrating electrical and mechanical systems.
- Designing and implementing software and procedures to control and enhance electro-mechanical systems and mechatronic devices performance in collaboration with scientists.
- Designing and prototyping mechatronic devices with motors, solenoids, gears, sensors, and springs.
- Identify and address areas of product weakness in finished products.
Make each as
- .
Then
Requirements
then Degree requirement: "Requires a degree from an accredited engineering program in mechanical engineering, electrical engineering, or a related field."
Then
Skills
then - each competency with its description.
We need to include the competency title and its description (Level Working Knowledge and bullet points). Could format as:
-
Analytical Thinking: Knowledge of techniques and tools that support effective analysis, with the ability to identify the root cause of organizational problems and develop alternative solutions to resolve them. Level Working Knowledge: Approaches a situation or problem by defining the problem or issue and determining its significance. Makes a systematic comparison of two or more alternative solutions. Uses flow charts, Pareto charts, fish diagrams, etc. to disclose meaningful data patterns. Identifies the major forces, events and people impacting and impacted by the situation at hand. Uses logic and intuition to make inferences about the meaning of the data and arrive at conclusions.
Similarly for others.
We need to preserve all bullet points inside each competency. Let's extract each:
Analytical Thinking:
- Knowledge of techniques and tools that support effective analysis, with the ability to identify the root cause of organizational problems and develop alternative solutions to resolve them.
Level Working Knowledge:
- Approaches a situation or problem by defining the problem or issue and determining its significance.
- Makes a systematic comparison of two or more alternative solutions.
- Uses flow charts, Pareto charts, fish diagrams, etc. to disclose meaningful data patterns.
- Identifies the major forces, events and people impacting and impacted by the situation at hand.
- Uses logic and intuition to make inferences about the meaning of the data and arrive at conclusions.
Communicating Complex Concepts:
- Knowledge of effective presentation tools and techniques to ensure clear understanding; ability to use summarization and simplification techniques to explain complex technical concepts in simple, clear language appropriate to the audience.
Level Working Knowledge:
- Uses comparisons to familiar ideas when introducing a technical or novel feature.
- Separates fundamental concepts from supporting details in explaining a product or service.
- Explains products and services with little or no use of technical jargon or advanced vocabulary.
- Emphasizes the most important facts or features of a product or service.
- Perceives lack of audience comprehension; further simplifies explanation when needed.
Problem Solving:
- Knowledge of approaches, tools, techniques for recognizing, anticipating, and resolving organizational, operational or process problems; ability to apply knowledge of problem solving appropriately to diverse situations.
Level Working Knowledge:
- Identifies and documents specific problems and resolution alternatives.
- Examines a specific problem and understands the perspective of each involved stakeholder.
- Develops alternative techniques for assessing accuracy and relevance of information.
- Helps to analyze risks and benefits of alternative approaches and obtain decision on resolution.
- Uses fact-finding techniques and diagnostic tools to identify problems.
Embedded Systems:
- Knowledge of embedded systems and their applications; ability to develop embedded systems with varying levels of complexity to control the operations of the machine it is embedded within.
Level Working Knowledge:
- Describes the basic structure and functioning of an embedded system.
- Explains the commonly found errors in an embedded system.
- Identifies the application and difference between microprocessor and microcontroller.
- Researches and documents upgrades for existing embedded systems.
- Understands and works with embedded programming languages.
Technical Troubleshooting:
- Knowledge of technical troubleshooting approaches, tools and techniques; ability to anticipate, recognize, and resolve technical issues on hardware, software, application or operation.
Level Basic Understanding:
- Describes problem identification, reporting and escalation procedures.
- Explains the underlying concept of using a systematic approach to solve technical problems.
- Identifies available resources and support systems for troubleshooting.
- Describes common hardware, software and communication problems; finds ways to resolve issues.
Note: For Technical Troubleshooting, level is "Basic Understanding". We'll keep that.
Now Benefits section: list as - . Include all benefits mentioned.
Benefits list from text:
- Medical, dental, and vision benefits*
- Paid time off plan (Vacation, Holidays, Volunteer, etc.)*
- 401(k) savings plans*
- Health Savings Account (HSA)*
- Flexible Spending Accounts (FSAs)*
- Health Lifestyle Programs*
- Employee Assistance Program*
- Voluntary Benefits and Employee Discounts*
- Career Development*
- Incentive bonus*
- Disability benefits
- Life Insurance
- Parental leave
- Adoption benefits
- Tuition Reimbursement
- These benefits also apply to part-time employees
- Relocation assistance is available for this position
- Sponsorship is available for this position
- Visa sponsorship is available for eligible applicants.
We should keep the asterisks? They are just footnotes; we can keep them as part of text.
Now Pay section:
Pay
Pay Range: $97,530.00 - $146,290.00
Schedule section: Schedule
This position requires working onsite five days a week.
We might also add a note about visa sponsorship under Benefits or Schedule? Already in Benefits
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes "Summary Pay Range: $97,530.00 - $146,290.00". Also "This position requires working onsite five days a week." That's schedule. Benefits listed. So we need sections: About the role (maybe "About IPSD" or "About the role"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We have "About IPSD" describing division. Could be "About the role" includes the description of role and what you will do. Also "Responsibilities" could list the bullet points under "What You Will Do". "Requirements" could include degree requirement. "Qualifications" maybe the list of skills/knowledge (Analytical Thinking, Communicating Complex Concepts, etc). "Skills" maybe the embedded systems etc. But we need to avoid duplication. Let's parse content: - Intro paragraph about Caterpillar. - About IPSD description. - Role Definition: seeking Controls System Engineer to design, develop, improve electro-mechanical systems... - What You Will Do: list of designing advanced electrical control systems..., designing and implementing software..., designing and prototyping mechatronic devices..., identify and address areas of product weakness... - Degree Requirement: requires a degree from accredited engineering program in mechanical, electrical, or related field. - What You Will Have: list of competencies with sub-bullets (Analytical Thinking, Communicating Complex Concepts, Problem Solving, Embedded Systems, Technical Troubleshooting). Each has "Level Working Knowledge:" and bullet points. - Additional Information: Relocation assistance available, Sponsorship available, ISE assignment not available. - Then company description. - Summary Pay Range: $97,530.00 - $146,290.00 - Benefits list. - This position requires working onsite five days a week. - Visa sponsorship is available for eligible applicants. - Posting dates etc (boilerplate to remove). - Drug screen, EEO etc (remove). We need to output only HTML fragment, no markdown fences. We need to decide sections: - About the role: could combine the introductory paragraph about Caterpillar and IPSD description and role definition. But we must not repeat job title. Use prose
. - Responsibilities: list of "What You Will Do" items. - Requirements: degree requirement. - Qualifications/Skills: maybe combine the "What You Will Have" competencies. Could be "Skills" section listing those competencies. Or "Qualifications". The instruction says use headings like Qualifications, Skills. We can have both if content distinct. But we have a list of competencies each with subpoints. Could treat as "Skills" section with subheadings? But we only allowed
for section headings, not nested headings. Could use - for each competency and inside
- for subpoints? Might be okay to nest lists. But we need to preserve all substantive info. Could flatten: each competency as a list item with its description (including subpoints). Could use
inside
- for subpoints? Might be messy.
Simplify: create a "Skills" section with
- each competency title and its description (including Level Working Knowledge and bullet points). Use
inside
- for the description? Might be okay but not specified. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for a list of skills, we should use
- . Inside each
- we can have prose (
) if needed. That seems acceptable.
Similarly for Responsibilities: list of duties.
For Requirements: maybe just a
(single requirement) or
- if multiple (only degree). Could be
.
For Benefits: list of benefits.
For Pay: we have pay range. Could be a
under Pay heading.
For Schedule: we have "This position requires working onsite five days a week." Could be a
under Schedule heading.
We also have relocation assistance, sponsorship available, visa sponsorship. Those could be under Additional Information but not a standard heading. Could maybe include under "Benefits" or "Additional Information". But instruction says only include sections when posting has real, specific content for it. We could add a section "Additional Information" but not in the list of allowed headings? The list includes examples but not exhaustive. Could add "Additional Information" as
. Might be okay. But we might incorporate those details into Benefits or other sections. Relocation assistance and sponsorship are benefits-ish. Could add to Benefits list. Visa sponsorship also similar.
Thus Benefits list can include: Medical, dental, vision; Paid time off; 401(k); HSA; FSAs; Health Lifestyle Programs; Employee Assistance; Voluntary Benefits and Employee Discounts; Career Development; Incentive bonus; Disability benefits; Life Insurance; Parental leave; Adoption benefits; Tuition Reimbursement; Relocation assistance; Sponsorship available; Visa sponsorship for eligible applicants. Also note "These benefits also apply to part-time employees". Could add as note.
We must not include boilerplate like "Posting Dates", "Any offer of employment is conditioned upon...", EEO, etc.
Now construct HTML.
Start with About the role
then
containing the introductory paragraphs: "Your Work Shapes the World at Caterpillar Inc...." plus IPSD description plus Role Definition. Combine into prose.
Then
Responsibilities
then - each duty.
Duties from "What You Will Do:":
- Designing advanced electrical control systems and integrating electrical and mechanical systems.
- Designing and implementing software and procedures to control and enhance electro-mechanical systems and mechatronic devices performance in collaboration with scientists.
- Designing and prototyping mechatronic devices with motors, solenoids, gears, sensors, and springs.
- Identify and address areas of product weakness in finished products.
Make each as
- .
Then
Requirements
then Degree requirement: "Requires a degree from an accredited engineering program in mechanical engineering, electrical engineering, or a related field."
Then
Skills
then - each competency with its description.
We need to include the competency title and its description (Level Working Knowledge and bullet points). Could format as:
-
Analytical Thinking: Knowledge of techniques and tools that support effective analysis, with the ability to identify the root cause of organizational problems and develop alternative solutions to resolve them. Level Working Knowledge: Approaches a situation or problem by defining the problem or issue and determining its significance. Makes a systematic comparison of two or more alternative solutions. Uses flow charts, Pareto charts, fish diagrams, etc. to disclose meaningful data patterns. Identifies the major forces, events and people impacting and impacted by the situation at hand. Uses logic and intuition to make inferences about the meaning of the data and arrive at conclusions.
Similarly for others.
We need to preserve all bullet points inside each competency. Let's extract each:
Analytical Thinking:
- Knowledge of techniques and tools that support effective analysis, with the ability to identify the root cause of organizational problems and develop alternative solutions to resolve them.
Level Working Knowledge:
- Approaches a situation or problem by defining the problem or issue and determining its significance.
- Makes a systematic comparison of two or more alternative solutions.
- Uses flow charts, Pareto charts, fish diagrams, etc. to disclose meaningful data patterns.
- Identifies the major forces, events and people impacting and impacted by the situation at hand.
- Uses logic and intuition to make inferences about the meaning of the data and arrive at conclusions.
Communicating Complex Concepts:
- Knowledge of effective presentation tools and techniques to ensure clear understanding; ability to use summarization and simplification techniques to explain complex technical concepts in simple, clear language appropriate to the audience.
Level Working Knowledge:
- Uses comparisons to familiar ideas when introducing a technical or novel feature.
- Separates fundamental concepts from supporting details in explaining a product or service.
- Explains products and services with little or no use of technical jargon or advanced vocabulary.
- Emphasizes the most important facts or features of a product or service.
- Perceives lack of audience comprehension; further simplifies explanation when needed.
Problem Solving:
- Knowledge of approaches, tools, techniques for recognizing, anticipating, and resolving organizational, operational or process problems; ability to apply knowledge of problem solving appropriately to diverse situations.
Level Working Knowledge:
- Identifies and documents specific problems and resolution alternatives.
- Examines a specific problem and understands the perspective of each involved stakeholder.
- Develops alternative techniques for assessing accuracy and relevance of information.
- Helps to analyze risks and benefits of alternative approaches and obtain decision on resolution.
- Uses fact-finding techniques and diagnostic tools to identify problems.
Embedded Systems:
- Knowledge of embedded systems and their applications; ability to develop embedded systems with varying levels of complexity to control the operations of the machine it is embedded within.
Level Working Knowledge:
- Describes the basic structure and functioning of an embedded system.
- Explains the commonly found errors in an embedded system.
- Identifies the application and difference between microprocessor and microcontroller.
- Researches and documents upgrades for existing embedded systems.
- Understands and works with embedded programming languages.
Technical Troubleshooting:
- Knowledge of technical troubleshooting approaches, tools and techniques; ability to anticipate, recognize, and resolve technical issues on hardware, software, application or operation.
Level Basic Understanding:
- Describes problem identification, reporting and escalation procedures.
- Explains the underlying concept of using a systematic approach to solve technical problems.
- Identifies available resources and support systems for troubleshooting.
- Describes common hardware, software and communication problems; finds ways to resolve issues.
Note: For Technical Troubleshooting, level is "Basic Understanding". We'll keep that.
Now Benefits section: list as - . Include all benefits mentioned.
Benefits list from text:
- Medical, dental, and vision benefits*
- Paid time off plan (Vacation, Holidays, Volunteer, etc.)*
- 401(k) savings plans*
- Health Savings Account (HSA)*
- Flexible Spending Accounts (FSAs)*
- Health Lifestyle Programs*
- Employee Assistance Program*
- Voluntary Benefits and Employee Discounts*
- Career Development*
- Incentive bonus*
- Disability benefits
- Life Insurance
- Parental leave
- Adoption benefits
- Tuition Reimbursement
- These benefits also apply to part-time employees
- Relocation assistance is available for this position
- Sponsorship is available for this position
- Visa sponsorship is available for eligible applicants.
We should keep the asterisks? They are just footnotes; we can keep them as part of text.
Now Pay section:
Pay
Pay Range: $97,530.00 - $146,290.00
Schedule section: Schedule
This position requires working onsite five days a week.
We might also add a note about visa sponsorship under Benefits or Schedule? Already in Benefits
- for subpoints? Might be okay to nest lists. But we need to preserve all substantive info. Could flatten: each competency as a list item with its description (including subpoints). Could use
inside
- for subpoints? Might be messy.
Simplify: create a "Skills" section with
- each competency title and its description (including Level Working Knowledge and bullet points). Use
inside
- for the description? Might be okay but not specified. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for a list of skills, we should use
- . Inside each
- we can have prose (
) if needed. That seems acceptable. Similarly for Responsibilities: list of duties. For Requirements: maybe just a
(single requirement) or
- if multiple (only degree). Could be
. For Benefits: list of benefits. For Pay: we have pay range. Could be a
under Pay heading. For Schedule: we have "This position requires working onsite five days a week." Could be a
under Schedule heading. We also have relocation assistance, sponsorship available, visa sponsorship. Those could be under Additional Information but not a standard heading. Could maybe include under "Benefits" or "Additional Information". But instruction says only include sections when posting has real, specific content for it. We could add a section "Additional Information" but not in the list of allowed headings? The list includes examples but not exhaustive. Could add "Additional Information" as
. Might be okay. But we might incorporate those details into Benefits or other sections. Relocation assistance and sponsorship are benefits-ish. Could add to Benefits list. Visa sponsorship also similar. Thus Benefits list can include: Medical, dental, vision; Paid time off; 401(k); HSA; FSAs; Health Lifestyle Programs; Employee Assistance; Voluntary Benefits and Employee Discounts; Career Development; Incentive bonus; Disability benefits; Life Insurance; Parental leave; Adoption benefits; Tuition Reimbursement; Relocation assistance; Sponsorship available; Visa sponsorship for eligible applicants. Also note "These benefits also apply to part-time employees". Could add as note. We must not include boilerplate like "Posting Dates", "Any offer of employment is conditioned upon...", EEO, etc. Now construct HTML. Start with
About the role
thencontaining the introductory paragraphs: "Your Work Shapes the World at Caterpillar Inc...." plus IPSD description plus Role Definition. Combine into prose. Then
Responsibilities
then- each duty. Duties from "What You Will Do:": - Designing advanced electrical control systems and integrating electrical and mechanical systems. - Designing and implementing software and procedures to control and enhance electro-mechanical systems and mechatronic devices performance in collaboration with scientists. - Designing and prototyping mechatronic devices with motors, solenoids, gears, sensors, and springs. - Identify and address areas of product weakness in finished products. Make each as
- .
Then
Requirements
thenDegree requirement: "Requires a degree from an accredited engineering program in mechanical engineering, electrical engineering, or a related field." Then
Skills
then- each competency with its description. We need to include the competency title and its description (Level Working Knowledge and bullet points). Could format as:
- Analytical Thinking: Knowledge of techniques and tools that support effective analysis, with the ability to identify the root cause of organizational problems and develop alternative solutions to resolve them. Level Working Knowledge: Approaches a situation or problem by defining the problem or issue and determining its significance. Makes a systematic comparison of two or more alternative solutions. Uses flow charts, Pareto charts, fish diagrams, etc. to disclose meaningful data patterns. Identifies the major forces, events and people impacting and impacted by the situation at hand. Uses logic and intuition to make inferences about the meaning of the data and arrive at conclusions. Similarly for others. We need to preserve all bullet points inside each competency. Let's extract each: Analytical Thinking: - Knowledge of techniques and tools that support effective analysis, with the ability to identify the root cause of organizational problems and develop alternative solutions to resolve them. Level Working Knowledge: - Approaches a situation or problem by defining the problem or issue and determining its significance. - Makes a systematic comparison of two or more alternative solutions. - Uses flow charts, Pareto charts, fish diagrams, etc. to disclose meaningful data patterns. - Identifies the major forces, events and people impacting and impacted by the situation at hand. - Uses logic and intuition to make inferences about the meaning of the data and arrive at conclusions. Communicating Complex Concepts: - Knowledge of effective presentation tools and techniques to ensure clear understanding; ability to use summarization and simplification techniques to explain complex technical concepts in simple, clear language appropriate to the audience. Level Working Knowledge: - Uses comparisons to familiar ideas when introducing a technical or novel feature. - Separates fundamental concepts from supporting details in explaining a product or service. - Explains products and services with little or no use of technical jargon or advanced vocabulary. - Emphasizes the most important facts or features of a product or service. - Perceives lack of audience comprehension; further simplifies explanation when needed. Problem Solving: - Knowledge of approaches, tools, techniques for recognizing, anticipating, and resolving organizational, operational or process problems; ability to apply knowledge of problem solving appropriately to diverse situations. Level Working Knowledge: - Identifies and documents specific problems and resolution alternatives. - Examines a specific problem and understands the perspective of each involved stakeholder. - Develops alternative techniques for assessing accuracy and relevance of information. - Helps to analyze risks and benefits of alternative approaches and obtain decision on resolution. - Uses fact-finding techniques and diagnostic tools to identify problems. Embedded Systems: - Knowledge of embedded systems and their applications; ability to develop embedded systems with varying levels of complexity to control the operations of the machine it is embedded within. Level Working Knowledge: - Describes the basic structure and functioning of an embedded system. - Explains the commonly found errors in an embedded system. - Identifies the application and difference between microprocessor and microcontroller. - Researches and documents upgrades for existing embedded systems. - Understands and works with embedded programming languages. Technical Troubleshooting: - Knowledge of technical troubleshooting approaches, tools and techniques; ability to anticipate, recognize, and resolve technical issues on hardware, software, application or operation. Level Basic Understanding: - Describes problem identification, reporting and escalation procedures. - Explains the underlying concept of using a systematic approach to solve technical problems. - Identifies available resources and support systems for troubleshooting. - Describes common hardware, software and communication problems; finds ways to resolve issues. Note: For Technical Troubleshooting, level is "Basic Understanding". We'll keep that. Now Benefits section: list as
- . Include all benefits mentioned.
Benefits list from text:
- Medical, dental, and vision benefits*
- Paid time off plan (Vacation, Holidays, Volunteer, etc.)*
- 401(k) savings plans*
- Health Savings Account (HSA)*
- Flexible Spending Accounts (FSAs)*
- Health Lifestyle Programs*
- Employee Assistance Program*
- Voluntary Benefits and Employee Discounts*
- Career Development*
- Incentive bonus*
- Disability benefits
- Life Insurance
- Parental leave
- Adoption benefits
- Tuition Reimbursement
- These benefits also apply to part-time employees
- Relocation assistance is available for this position
- Sponsorship is available for this position
- Visa sponsorship is available for eligible applicants.
We should keep the asterisks? They are just footnotes; we can keep them as part of text.
Now Pay section:
Pay
Pay Range: $97,530.00 - $146,290.00
Schedule section:Schedule
This position requires working onsite five days a week.
We might also add a note about visa sponsorship under Benefits or Schedule? Already in Benefits
- if multiple (only degree). Could be
- for any list of duties/requirements/benefits, and
- each competency title and its description (including Level Working Knowledge and bullet points). Use