Talent Acquisition Specialist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Title: Linde Advanced Material Technologies Inc. Talent Acquisition Specialist Indianapolis, IN, United States | req33334
We should not repeat job title as heading.
We need sections:
- About the role: maybe the first paragraph after title: "What you will enjoy doing* In this role, you will support recruitment by assisting with pre-hire onboarding and managing a requisition loadYou will screen resumes, interview candidates, schedule manager interviews, and prepare and extend offer lettersFurther, you will maintain systems by dispositioning candidates and tracking recruitment and onboarding activityYou will walk candidates through the pre-hire process and track the completion of background verifications, drug screens and physicalsYou may assist recruiters with proactive sourcing supportAlso, you will establish and maintain relationships with hiring leaders across the organization"
That's responsibilities.
- Requirements/Qualifications: "What Makes You Great A high school diploma or GED is required but a degree is strongly preferredYou must have one to three (1-3) years of prior talent acquisition experienceIn this role, you must have previous experience working in position that requires attention to detail Strong verbal and written communication skills are required"
- Benefits: "What we offer you! At Linde, the sky is not the limit... Linde offers competitive compensation and an outstanding benefits package. Enjoy access to health, dental, disability, and life insurance, paid holidays and vacation, 401(k) matching, pension benefits, an employee discount program, and opportunities for educational and professional growth. Additional compensation may vary depending on the position and organizational level."
- Pay: Not specific numbers, just "competitive compensation" and "Additional compensation may vary". That's vague; we should not create Pay section unless posting actually states them. It says "competitive compensation" but no specific numbers. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specific list, so we can include Benefits. Pay: we have only vague "competitive compensation" and "Additional compensation may vary". That's not specific; we should not create Pay section.
- Schedule: Not mentioned.
- Skills: Could be derived from requirements: attention to detail, verbal/written communication. Could be a Skills section. But we already have Requirements/Qualifications. Could combine. The instruction: prefer a few substantive sections over many thin ones. So maybe we have sections: Responsibilities, Requirements, Benefits. Possibly also About the role (maybe same as Responsibilities). The heading "About the role" could be used for a brief description. But we already have responsibilities detailed. Could do About the role (summary) and Responsibilities (list). However we need to avoid thin sections. Let's see: The posting includes "What you will enjoy doing*" which is essentially responsibilities. Could treat that as About the role (description) and then list responsibilities as bullet list. But we need to use - for any list of duties/requirements/benefits. So we can make a Responsibilities section with
- . For Requirements we can also list bullet points.
Benefits we can list bullet points.
Thus sections: Responsibilities, Requirements, Benefits.
We should not include About the role separately if it's thin. But we could include a short
for overview before the list. However the instruction: Use
for prose. So we can have a
for overview then
- for list.
Thus structure:
Responsibilities
In this role, you will support recruitment by assisting with pre-hire onboarding and managing a requisition load...
- Screen resumes
- Interview candidates
- Schedule manager interviews
- Prepare and extend offer letters
- Maintain systems by dispositioning candidates and tracking recruitment and onboarding activity
- Walk candidates through the pre-hire process and track the completion of background verifications, drug screens and physicals
- Assist recruiters with proactive sourcing support
- Establish and maintain relationships with hiring leaders across the organization
Similarly Requirements:
Requirements
A high school diploma or GED is required but a degree is strongly preferred. One to three (1-3) years of prior talent acquisition experience. Previous experience working in a position that requires attention to detail. Strong verbal and written communication skills are required.
- High school diploma or GED (degree preferred)
- 1-3 years of talent acquisition experience
- Attention to detail
- Strong verbal and written communication skills
Benefits:
Benefits
Linde offers competitive compensation and an outstanding benefits package.
- Health, dental, disability, and life insurance
- Paid holidays and vacation
- 401(k) matching
- Pension benefits
- Employee discount program
- Opportunities for educational and professional growth
We should not include Pay or Schedule.
We need to ensure we preserve all substantive information. Did we miss anything? The posting also includes "What Makes You Great" heading but we turned into Requirements. Also includes "Why you will love working with us" description about Linde; we could include an About the company section? Not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why you will love working with us" is more about company culture; could be considered About the role or maybe we could add a short under Responsibilities? But we already have responsibilities overview. Could add a separate section "About the company" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those. The "Why you will love working with us" is descriptive of company; could be considered About the role? Might be okay to include as a
under Responsibilities or as a separate
before responsibilities. But we must not invent sections. We could add a brief
after the responsibilities heading describing the company. However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings; we could also use About the role for a brief description. Let's consider adding an About the role section with a short paragraph summarizing the role and company. Then Responsibilities as list. That would avoid thin sections.
But we already have responsibilities list; we could put overview in About the role, then Responsibilities list. However the posting's "What you will enjoy doing*" is essentially responsibilities; we could treat that as About the role (description) and then list duties as bullet list under Responsibilities. That seems reasonable.
Thus:
About the role
In this role, you will support recruitment by assisting with pre-hire onboarding and managing a requisition load. You will screen resumes, interview candidates, schedule manager interviews, and prepare and extend offer letters. You will maintain systems by dispositioning candidates and tracking recruitment and onboarding activity. You will walk candidates through the pre-hire process and track the completion of background verifications, drug screens and physicals. You may assist recruiters with proactive sourcing support. Also, you will establish and maintain relationships with hiring leaders across the organization.
Then Responsibilities could be a list? But that would duplicate. Better to keep About the role as prose and then Responsibilities as list of duties (maybe more concise). However the instruction: Use - for any list of duties/requirements/benefits. So we need to list duties somewhere. We could put the list under Responsibilities. Then About the role could be a short summary of the role's purpose (maybe from "Why you will love working with us"?). But we risk duplication.
Given the instruction to prefer few substantive sections over many thin ones, maybe we just have Responsibilities (with prose overview + list) and Requirements (with prose + list) and Benefits (with prose + list). That's three sections.
Thus we keep Responsibilities section with an overview paragraph then list.
We already drafted that.
Now ensure we didn't miss any substantive info: The posting also includes "Linde Advanced Material Technologies Inc. Talent Acquisition Specialist Indianapolis, IN, United States | req33334" - we dropped job ID and location? The location is Indianapolis, IN, United States. Should we preserve location? It's substantive. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is not minor metadata; it's location of job. Should we include it? Possibly as a short
under About the role or at top. Since we are not using a heading for job metadata, we can include a short paragraph with location. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is not job ID; it's location. Could be included as a short
. Let's add a
at the very start: "Location: Indianapolis, IN, United States." Or incorporate into About the role.
We'll add a
before sections: "
Location: Indianapolis, IN, United States.
" That preserves location.
Now check for any other substantive info: The posting includes "Linde Advanced Material Technologies, formerly Praxair Surface Technologies, is a company that revolutionizes industries through innovative materials and surface coatings..." That's company description; we could include in About the role paragraph or maybe a separate about company. But we already have overview paragraph in Responsibilities; we could incorporate company description there. However that may be too much for Responsibilities. Perhaps better to have an About the role section that includes company description and location, then Responsibilities list, Requirements list, Benefits list. That would be four sections, but maybe still okay. The instruction: prefer a few substantive sections over many thin ones. Four sections each substantive is okay.
Let's design:
-
Location: Indianapolis, IN, United States.
- About the role
Linde Advanced Material Technologies, formerly Praxair Surface Technologies, is a company that revolutionizes industries through innovative materials and surface coatings. We are leaders in advanced materials and offer metal powders, sputtering targets, and surface coatings that enhance performance across various sectors. Our strong focus on innovation is evident in our superior technologies for the aerospace, energy, semiconductor, automotive, and industrial industries. Linde employees learn and abide the Linde Code of Ethics and Code of Conduct by demonstrating honesty, integrity, professionalism in all communications, actions, and decisions.
In this role, you will support recruitment by assisting with pre-hire onboarding and managing a requisition load. You will screen resumes, interview candidates, schedule manager interviews, and prepare and extend offer letters. You will maintain systems by dispositioning candidates and tracking recruitment and onboarding activity. You will walk candidates through the pre-hire process and track the completion of background verifications, drug screens and physicals. You may assist recruiters with proactive sourcing support. Also, you will establish and maintain relationships with hiring leaders across the organization.
But that mixes company description and role duties. Might be okay.
Then Responsibilities: maybe we can keep just a list? But we already listed duties in About the role. To avoid duplication, we could make
- . For Requirements we can also list bullet points.
Benefits we can list bullet points.
Thus sections: Responsibilities, Requirements, Benefits.
We should not include About the role separately if it's thin. But we could include a short
for overview before the list. However the instruction: Use
for prose. So we can have a
for overview then
- for list.
Thus structure:
Responsibilities
In this role, you will support recruitment by assisting with pre-hire onboarding and managing a requisition load...
- Screen resumes
- Interview candidates
- Schedule manager interviews
- Prepare and extend offer letters
- Maintain systems by dispositioning candidates and tracking recruitment and onboarding activity
- Walk candidates through the pre-hire process and track the completion of background verifications, drug screens and physicals
- Assist recruiters with proactive sourcing support
- Establish and maintain relationships with hiring leaders across the organization
Requirements
A high school diploma or GED is required but a degree is strongly preferred. One to three (1-3) years of prior talent acquisition experience. Previous experience working in a position that requires attention to detail. Strong verbal and written communication skills are required.
- High school diploma or GED (degree preferred)
- 1-3 years of talent acquisition experience
- Attention to detail
- Strong verbal and written communication skills
Benefits
Linde offers competitive compensation and an outstanding benefits package.
- Health, dental, disability, and life insurance
- Paid holidays and vacation
- 401(k) matching
- Pension benefits
- Employee discount program
- Opportunities for educational and professional growth
under Responsibilities? But we already have responsibilities overview. Could add a separate section "About the company" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those. The "Why you will love working with us" is descriptive of company; could be considered About the role? Might be okay to include as a
under Responsibilities or as a separate
before responsibilities. But we must not invent sections. We could add a brief
after the responsibilities heading describing the company. However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings; we could also use About the role for a brief description. Let's consider adding an About the role section with a short paragraph summarizing the role and company. Then Responsibilities as list. That would avoid thin sections. But we already have responsibilities list; we could put overview in About the role, then Responsibilities list. However the posting's "What you will enjoy doing*" is essentially responsibilities; we could treat that as About the role (description) and then list duties as bullet list under Responsibilities. That seems reasonable. Thus:
About the role
In this role, you will support recruitment by assisting with pre-hire onboarding and managing a requisition load. You will screen resumes, interview candidates, schedule manager interviews, and prepare and extend offer letters. You will maintain systems by dispositioning candidates and tracking recruitment and onboarding activity. You will walk candidates through the pre-hire process and track the completion of background verifications, drug screens and physicals. You may assist recruiters with proactive sourcing support. Also, you will establish and maintain relationships with hiring leaders across the organization.
Then Responsibilities could be a list? But that would duplicate. Better to keep About the role as prose and then Responsibilities as list of duties (maybe more concise). However the instruction: Use- for any list of duties/requirements/benefits. So we need to list duties somewhere. We could put the list under Responsibilities. Then About the role could be a short summary of the role's purpose (maybe from "Why you will love working with us"?). But we risk duplication.
Given the instruction to prefer few substantive sections over many thin ones, maybe we just have Responsibilities (with prose overview + list) and Requirements (with prose + list) and Benefits (with prose + list). That's three sections.
Thus we keep Responsibilities section with an overview paragraph then list.
We already drafted that.
Now ensure we didn't miss any substantive info: The posting also includes "Linde Advanced Material Technologies Inc. Talent Acquisition Specialist Indianapolis, IN, United States | req33334" - we dropped job ID and location? The location is Indianapolis, IN, United States. Should we preserve location? It's substantive. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is not minor metadata; it's location of job. Should we include it? Possibly as a short
under About the role or at top. Since we are not using a heading for job metadata, we can include a short paragraph with location. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is not job ID; it's location. Could be included as a short
. Let's add a
at the very start: "Location: Indianapolis, IN, United States." Or incorporate into About the role. We'll add a
before sections: "
Location: Indianapolis, IN, United States.
" That preserves location. Now check for any other substantive info: The posting includes "Linde Advanced Material Technologies, formerly Praxair Surface Technologies, is a company that revolutionizes industries through innovative materials and surface coatings..." That's company description; we could include in About the role paragraph or maybe a separateabout company. But we already have overview paragraph in Responsibilities; we could incorporate company description there. However that may be too much for Responsibilities. Perhaps better to have an About the role section that includes company description and location, then Responsibilities list, Requirements list, Benefits list. That would be four sections, but maybe still okay. The instruction: prefer a few substantive sections over many thin ones. Four sections each substantive is okay. Let's design: -
Location: Indianapolis, IN, United States.
-About the role
Linde Advanced Material Technologies, formerly Praxair Surface Technologies, is a company that revolutionizes industries through innovative materials and surface coatings. We are leaders in advanced materials and offer metal powders, sputtering targets, and surface coatings that enhance performance across various sectors. Our strong focus on innovation is evident in our superior technologies for the aerospace, energy, semiconductor, automotive, and industrial industries. Linde employees learn and abide the Linde Code of Ethics and Code of Conduct by demonstrating honesty, integrity, professionalism in all communications, actions, and decisions.
In this role, you will support recruitment by assisting with pre-hire onboarding and managing a requisition load. You will screen resumes, interview candidates, schedule manager interviews, and prepare and extend offer letters. You will maintain systems by dispositioning candidates and tracking recruitment and onboarding activity. You will walk candidates through the pre-hire process and track the completion of background verifications, drug screens and physicals. You may assist recruiters with proactive sourcing support. Also, you will establish and maintain relationships with hiring leaders across the organization.
But that mixes company description and role duties. Might be okay. Then Responsibilities: maybe we can keep just a list? But we already listed duties in About the role. To avoid duplication, we could make
- for list.
Thus structure: