R&D Process Technician - Swing Shift
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Prefer a few substantive sections over many thin ones.
We need to include sections only when posting has real specific content. So we can include About the role (maybe from "A day in the life" description). Responsibilities (maybe from duties). Requirements (maybe from "You might be a good fit if you..."). Qualifications (maybe from "A strong candidate might bring one or more of the following…"). Skills (maybe overlapping). But we should avoid duplication. Perhaps combine some.
We need to preserve all substantive info. So we need to include all info from posting, but organized under these headings.
Let's extract content:
About the company: description of mission, technology, etc. This could go under About the role? Actually "About the role" is about the job, not company. But we have no explicit "About the role" heading content. However we could put company description under About the role? Might be okay but better to put under About the role? The instruction says use headings e.g. About the role, Responsibilities, etc. It doesn't forbid using About the role for company overview? Usually About the role is about the job. But we have "A day in the life" which describes role. So we can put that under About the role (or Responsibilities). Let's decide:
- About the role: could include "A day in the life As an R&D Process Technician at Swift on Swift's swing shift, you will be a core member of the device research and development team, conducting studies to help make more efficient and reliable solar cells. You will also help keep the lab running smoothly. Working at an early-stage startup, you will have the opportunity to get involved in many aspects of the company’s technical development and internal operations. In a typical day, you will run thin-film deposition and characterization systems to carry out experiments designed by Swift’s R&D scientists with your input. Taking organized notes and communicating your work effectively are key parts of the job, as is managing your time to run many experiments as efficiently as possible. You will also help build and maintain lab equipment and facilities. In our early-stage startup environment, you will help craft Swift’s culture and technical direction. As our team grows, we’ll expect you to help hire, mentor, and set an example for new team members. You will find many opportunities to grow your own skills and capabilities, and we encourage you to take full advantage of them."
That's a prose description of role.
- Responsibilities: could be a list of duties: run thin-film deposition and characterization systems, take organized notes, communicate work, manage time, help build/maintain lab equipment, help craft culture, help hire/mentor, etc. But many of those are already in the prose. To avoid duplication, we could keep responsibilities as a list derived from that prose. However we must preserve all substantive info; we can either keep prose under About the role and list responsibilities separately, but that would duplicate. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine: Use About the role for prose description, and Responsibilities for a bullet list of specific duties (maybe extracted). But that may be thin. Could instead put responsibilities under About the role and not have a separate Responsibilities section. But we need to include sections only when posting has real specific content. If we don't have distinct responsibilities beyond the prose, we could omit Responsibilities section. However we have a list of duties: "run thin-film deposition and characterization systems", "take organized notes", "communicate work", "manage time", "help build and maintain lab equipment", "help craft culture", "help hire, mentor, set example". Those are specific. Could be a Responsibilities section.
- Requirements: from "You might be a good fit if you..." bullet list (though it's not formatted as bullet but sentences). We can turn into list.
- Qualifications: from "A strong candidate might bring one or more of the following…" list.
- Skills: maybe overlapping with qualifications; but we could treat qualifications as skills. To avoid thin sections, we could combine Requirements and Qualifications into one section? But headings are prescribed; we can still include both if they have content. However we should prefer few substantive sections over many thin ones. If we have both Requirements and Qualifications with similar content, maybe we can merge them into one section called Requirements (or Qualifications). But we need to follow instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must use all; we can omit those lacking content. So we can choose to include only those with substantive distinct content.
We have:
- About the role: prose description (day in the life). Good.
- Responsibilities: bullet list of duties (maybe from same prose). Could be considered substantive.
- Requirements: list of "You might be a good fit if you..." (experience, abilities). Good.
- Qualifications: list of "A strong candidate might bring one or more of the following…" (specific technical experience). Good.
- Skills: maybe we could treat qualifications as skills; but we already have Qualifications. Could omit Skills.
- Benefits: we have benefits description.
- Pay: we have compensation details.
- Schedule: we have swing shift timing.
Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We must not include filler like "commensurate with experience". Not present.
Now we need to format:
About the role
then ... prose ...
. For lists: - ...
.
We must preserve all substantive information. Let's extract each piece precisely.
About the company description: Should we include that? It's not under any heading but it's substantive info about company. The instruction says preserve ALL substantive information. So we need to include company description somewhere. Where? Could be under About the role? But that is about the role, not company. However we could add a section "About the company" but not in allowed headings list. The allowed headings are only those listed; we cannot add other headings. So we must fit company description into one of the allowed headings. Perhaps we can put it under About the role as introductory paragraph before the day-in-life description. That would preserve it. The heading "About the role" could include both company overview and role description. That seems acceptable.
Thus About the role section will contain: company mission description + day-in-life prose.
Let's copy company description exactly:
"About the company At Swift Solar, our mission is to unlock the full potential of solar energy. We believe solar can provide affordable, reliable, resilient, clean energy to virtually anyone, anywhere. But while today’s solar technology is good, it’s not good enough. Swift Solar’s breakthrough perovskite-silicon tandem technology will drive solar power to commanding new heights. Our tandem cells stack a perovskite layer on top of a heterojunction (HJT) silicon cell, delivering dramatically higher efficiency than traditional silicon alone. In 2026, we acquired Meyer Burger’s HJT intellectual property and manufacturing assets, giving us the world’s most extensive HJT patent portfolio and a clear path to gigawatt-scale domestic production. This vertically integrated approach means we can design, manufacture, and scale next-generation solar solutions entirely in the United States—from silicon foundations to perovskite innovations. Our technology enables applications ranging from space solar to utility-scale power generation, creating American-made solutions for a world facing growing energy challenges. Swift Solar is on a journey to bring revolutionary clean-energy technology to market. We’re in it for the long haul, with support from world-class investors. Join our extraordinary team building the cutting-edge solar technology that will power the future."
Now day-in-life paragraph: "A day in the life As an R&D Process Technician at Swift on Swift's swing shift, you will be a core member of the device research and development team, conducting studies to help make more efficient and reliable solar cells. You will also help keep the lab running smoothly. Working at an early-stage startup, you will have the opportunity to get involved in many aspects of the company’s technical development and internal operations. In a typical day, you will run thin-film deposition and characterization systems to carry out experiments designed by Swift’s R&D scientists with your input. Taking organized notes and communicating your work effectively are key parts of the job, as is managing your time to run many experiments as efficiently as possible. You will also help build and maintain lab equipment and facilities. In our early-stage startup environment, you will help craft Swift’s culture and technical direction. As our team grows, we’ll expect you to help hire, mentor, and set an example for new team members. You will find many opportunities to grow your own skills and capabilities, and we encourage you to take full advantage of them."
We need to combine them into a single maybe with line breaks? Could be multiple
tags but instruction says use
for prose. Could have multiple
paragraphs. That's fine.
Now Responsibilities: list of duties. Let's extract from day-in-life: run thin-film deposition and characterization systems; take organized notes; communicate work effectively; manage time to run many experiments efficiently; help build and maintain lab equipment and facilities; help craft Swift’s culture and technical direction; help hire, mentor, and set an example for new team members; find opportunities to grow skills (maybe not a duty). Also "conducting studies to help make more efficient and reliable solar cells". Also "help keep the lab running smoothly". We'll list them.
We'll produce
- Conduct studies to improve solar cell efficiency and reliability.
- Run thin-film deposition and characterization systems for experiments designed by R&D scientists.
- Take organized notes and communicate work effectively.
- Manage time to run experiments efficiently.
- Help build and maintain lab equipment and facilities.
- Help craft company culture and technical direction.
- Assist in hiring, mentoring, and setting an example for new team members.
- Help keep the lab running smoothly.
But note some overlap; we can keep.
Now Requirements: from "You might be a good fit if you..." sentences:
- Have 2+ years of hands-on experience working as a technician in a technical field
for prose. Do NOT repeat the job title as a heading. Prefer a few substantive sections over many thin ones. We need to include sections only when posting has real specific content. So we can include About the role (maybe from "A day in the life" description). Responsibilities (maybe from duties). Requirements (maybe from "You might be a good fit if you..."). Qualifications (maybe from "A strong candidate might bring one or more of the following…"). Skills (maybe overlapping). But we should avoid duplication. Perhaps combine some. We need to preserve all substantive info. So we need to include all info from posting, but organized under these headings. Let's extract content: About the company: description of mission, technology, etc. This could go under About the role? Actually "About the role" is about the job, not company. But we have no explicit "About the role" heading content. However we could put company description under About the role? Might be okay but better to put under About the role? The instruction says use headings e.g. About the role, Responsibilities, etc. It doesn't forbid using About the role for company overview? Usually About the role is about the job. But we have "A day in the life" which describes role. So we can put that under About the role (or Responsibilities). Let's decide: - About the role: could include "A day in the life As an R&D Process Technician at Swift on Swift's swing shift, you will be a core member of the device research and development team, conducting studies to help make more efficient and reliable solar cells. You will also help keep the lab running smoothly. Working at an early-stage startup, you will have the opportunity to get involved in many aspects of the company’s technical development and internal operations. In a typical day, you will run thin-film deposition and characterization systems to carry out experiments designed by Swift’s R&D scientists with your input. Taking organized notes and communicating your work effectively are key parts of the job, as is managing your time to run many experiments as efficiently as possible. You will also help build and maintain lab equipment and facilities. In our early-stage startup environment, you will help craft Swift’s culture and technical direction. As our team grows, we’ll expect you to help hire, mentor, and set an example for new team members. You will find many opportunities to grow your own skills and capabilities, and we encourage you to take full advantage of them." That's a prose description of role. - Responsibilities: could be a list of duties: run thin-film deposition and characterization systems, take organized notes, communicate work, manage time, help build/maintain lab equipment, help craft culture, help hire/mentor, etc. But many of those are already in the prose. To avoid duplication, we could keep responsibilities as a list derived from that prose. However we must preserve all substantive info; we can either keep prose under About the role and list responsibilities separately, but that would duplicate. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine: Use About the role for prose description, and Responsibilities for a bullet list of specific duties (maybe extracted). But that may be thin. Could instead put responsibilities under About the role and not have a separate Responsibilities section. But we need to include sections only when posting has real specific content. If we don't have distinct responsibilities beyond the prose, we could omit Responsibilities section. However we have a list of duties: "run thin-film deposition and characterization systems", "take organized notes", "communicate work", "manage time", "help build and maintain lab equipment", "help craft culture", "help hire, mentor, set example". Those are specific. Could be a Responsibilities section. - Requirements: from "You might be a good fit if you..." bullet list (though it's not formatted as bullet but sentences). We can turn into list. - Qualifications: from "A strong candidate might bring one or more of the following…" list. - Skills: maybe overlapping with qualifications; but we could treat qualifications as skills. To avoid thin sections, we could combine Requirements and Qualifications into one section? But headings are prescribed; we can still include both if they have content. However we should prefer few substantive sections over many thin ones. If we have both Requirements and Qualifications with similar content, maybe we can merge them into one section called Requirements (or Qualifications). But we need to follow instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must use all; we can omit those lacking content. So we can choose to include only those with substantive distinct content. We have: - About the role: prose description (day in the life). Good. - Responsibilities: bullet list of duties (maybe from same prose). Could be considered substantive. - Requirements: list of "You might be a good fit if you..." (experience, abilities). Good. - Qualifications: list of "A strong candidate might bring one or more of the following…" (specific technical experience). Good. - Skills: maybe we could treat qualifications as skills; but we already have Qualifications. Could omit Skills. - Benefits: we have benefits description. - Pay: we have compensation details. - Schedule: we have swing shift timing. Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include filler like "commensurate with experience". Not present. Now we need to format:
About the role
then... prose ...
. For lists:- ...
maybe with line breaks? Could be multiple
tags but instruction says use
for prose. Could have multiple
paragraphs. That's fine. Now Responsibilities: list of duties. Let's extract from day-in-life: run thin-film deposition and characterization systems; take organized notes; communicate work effectively; manage time to run many experiments efficiently; help build and maintain lab equipment and facilities; help craft Swift’s culture and technical direction; help hire, mentor, and set an example for new team members; find opportunities to grow skills (maybe not a duty). Also "conducting studies to help make more efficient and reliable solar cells". Also "help keep the lab running smoothly". We'll list them. We'll produce
- Conduct studies to improve solar cell efficiency and reliability.
- Run thin-film deposition and characterization systems for experiments designed by R&D scientists.
- Take organized notes and communicate work effectively.
- Manage time to run experiments efficiently.
- Help build and maintain lab equipment and facilities.
- Help craft company culture and technical direction.
- Assist in hiring, mentoring, and setting an example for new team members.
- Help keep the lab running smoothly.