Field Service Technician II
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: About the role? Could be "Company Overview". Use heading "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. Use "About the role" for company overview and job description? Might be better to have "About the role" for company overview and job description summary. Then "Responsibilities" for essential duties. Then "Requirements" or "Qualifications" for qualifications. Then "Skills" maybe for skill list? Could combine. Then "Benefits" for benefits package. "Physical Demands" and "Work Environment" maybe not in list but we can include as separate sections if they have content. The instruction says prefer a few substantive sections over many thin ones. But we must include sections only when posting has real specific content. We have content for Physical Demands and Work Environment; they are substantive. Should we include them? Possibly yes, but they are not in the example list; but we can still use h3 with those headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we should stick to those headings; but we can also add others if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. So we should map content to those headings only. So we need to fit Physical Demands and Work Environment into maybe "Responsibilities" or "Requirements"? Not ideal. But maybe we can omit them? However instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit Physical Demands and Work Environment, we lose info. But we could incorporate them into "Responsibilities" or "Requirements" as prose. That would preserve info while using allowed headings. Let's do that: include Physical Demands and Work Environment details within Responsibilities or Requirements as paragraphs.
We also have "Other" section: "Other duties as may be assigned." That's generic; could be omitted as boilerplate? It's not specific; maybe we can drop as filler. Also "Each employee’s primary objective..." that's generic; maybe drop.
We need to include Benefits: "competitive wages, a generous benefits package and a friendly, dynamic working environment." That's substantive.
We need to include Pay? Not explicit. So skip Pay section.
Schedule? Not explicit. Skip.
Now structure:
About the role
Company overview: FUJIFILM Dimatix Inc. ... (the paragraph about printheads, locations, etc.)
Job Description SKILL ... (the skill bullet? Actually there is a "SKILL" heading with subpoints: Applies acquired job skills... etc. That's a list of skill statements. We'll treat as list under Skills maybe. But we have Skills section separate. Let's parse.
The posting includes:
Job Description
SKILL Applies acquired job skills and company policies and procedures to complete assigned tasks.
JOB COMPLEXITY Works on assignments that are semi-routine in nature but recognizes the need for occasional deviation from accepted practice.
SUPERVISION Normally follows established procedures on routine work, requires instructions only on new assignments.
Experience Typically requires a minimum of 1 - 2 years of related experience.
Then "Essential Duties & Responsibilities" with many bullet-like sentences.
Then "Supervisory Responsibilities None"
Then "Qualifications" with required and desired.
Then "Physical Demands"
Then "Work Environment"
Then "Other"
Then benefits line.
Thus we can map:
About the role: Company Overview + Job Description (skill, complexity, supervision, experience) maybe.
Responsibilities: Essential Duties & Responsibilities (list).
Requirements: Qualifications (required) plus maybe desired? Could be separate Skills? But we have Skills section; we could put skill list from Job Description SKILL etc under Skills.
Benefits: benefits line.
We need to avoid filler like "commensurate with experience". Not present.
Let's craft.
First, About the role: combine company overview paragraph and the Job Description skill/complexity/supervision/experience.
We'll output:
About the role
At FUJIFILM Dimatix Inc., printing and material deposition devices are only as good as their printheads. We are a recognized leader in the manufacturing and design of durable and productive drop-on-demand inkjet printheads that power cutting-edge systems, as well as integrated inkjet solutions that add digital inkjet capabilities to other equipment. These are part of the digitization and transformation of many applications such as commercial printing, graphics, label & packaging, additive manufacturing, ceramic tiles, textiles, electronics and life science research. We’re looking for forward-thinkers eager to spark innovation in inkjet technology. Bring your talents to a team built on collaboration, creativity, and a passion for excellence. At FUJIFILM Dimatix, every product we make begins with the extraordinary people behind it. Join us for groundbreaking work in a flexible, engaging environment. We’re based in two incredible locations: Lebanon, New Hampshire, surrounded by picturesque New England landscapes, and Santa Clara, California, a dynamic hub in Silicon Valley with a mix of innovation, diversity, and sunshine. Fujifilm is globally headquartered in Tokyo with over 70,000 employees across four key business segments of healthcare, electronics, business innovation, and imaging. We are guided and united by our Group Purpose of “giving our world more smiles.” Visit: https://www.fujifilm.com/us/en/about/region/careers
Skill: Applies acquired job skills and company policies and procedures to complete assigned tasks.
Job Complexity: Works on assignments that are semi-routine in nature but recognizes the need for occasional deviation from accepted practice.
Supervision: Normally follows established procedures on routine work, requires instructions only on new assignments.
Experience: Typically requires a minimum of 1 - 2 years of related experience.
But we need to use - for any list of duties/requirements/benefits. The above are not lists; they are prose. Could be
. That's fine.
Now Responsibilities: list of essential duties.
We'll extract each sentence as
- .
List:
- Provide service and customer support during field visits and onsite print trials.
- Travel to customer sites to perform equipment installation, repair, maintenance and testing.
- Diagnose technical issues, determine and implement proper solutions.
- Provide pre-sales samples for future business opportunities.
- Create and modify graphics appropriate for the best images for customer samples.
- Performs basic experiments and tests on varied electromechanical systems in a laboratory environment.
- Performs basic set up of equipment in a laboratory environment.
- Correlates and reports results and observations of testing and experiments to engineering using databases and spreadsheet computer programs.
- Produce timely and detailed service reports.
- Works from written/verbal instructions, specifications, technical manuals and engineering sketches.
- Uses a variety of imaging equipment and software associated with image manipulation.
- Basic repairs to test equipment and components, if applicable.
- Performs testing of customized inkjet systems.
- Assembles, disassembles, modifies, reworks, refurbishes, repairs, reassembles and tests units as required, using: Blueprints, sketches, engineering specifications and standard testing equipment, applying knowledge of mechanical, electrical and optical interrelations.
- Compiles and records test results.
- Usage of computer skills such as Excel, Word and database applications.
- Works closely with customers, engineers and senior technicians.
- Travel domestically and abroad – Extensive travel may be required.
We should keep the exact wording. Some sentences start with verb forms; keep as is.
Now Requirements: we have Qualifications required and desired. Could combine.
Required:
- High school degree or equivalent and 1-2 years of related experience.
- Working knowledge of the Microsoft Office product suite (Word, Excel, PowerPoint, etc.)
- Knowledge of basic wiring, mechanical workings and electronics.
- Strong attention to detail.
- Effective written and verbal communication skills.
- Ability and desire to contribute both independently and as part of a team.
- Ability to work flexible shifts and to adapt to changing work schedules.
- Ability to remain calm and professional in high pressure situations and work effectively to resolve the issues.
- Ability to follow prescribed safety rules and regulations.
- Ability to work with minimal supervision.
- Ability to read, analyze and interpret formal and informal oral and written instructions, technical procedures and procedure manuals.
- Ability to effectively present information and respond to questions from customers, engineers, peers and management.
- Ability to create / manipulate graphic imaging in various formats and programs.
- Ability to understand the various graphic formats required by FIS printers to create graphics for printing.
- Familiar with Adobe Photoshop and Adobe Illustrator.
- Basic knowledge of color and color science; screening and halftone techniques.
- Ability to work from a foreign site with limited infrastructure or oversight.
- Ability to travel domestic and abroad, either alone or as a part of a team.
Desired:
- Two-year technical degree
We could put desired under Requirements as well, maybe as a separate list labeled "Desired". But we only have one heading Requirements; we could include both required and desired as lists, maybe with a note.
We'll output:
Requirements
Required
...
Desired
...
But we are only allowed to use for section headings; using might be okay as subheading? The instruction didn't forbid other headings, but said use for section headings (e.g...). It didn't say we cannot use other headings. Safer to stick to only. Could combine required and desired into one list with note? Might lose nuance. Could make two under same and precede with
indicating required vs desired. That's okay.
We'll do:
Requirements
Required:
...
Desired:
...
Now Skills: we could put the skill list from Job Description SKILL etc. But we already used those in About the role. Maybe we should move them to Skills section and keep About the role just company overview. Let's reconsider.
We have a "SKILL" heading with a statement. Also there are skill-like abilities in Qualifications (like ability to create/manipulate graphic imaging, familiarity with Photoshop/Illustrator, basic knowledge of color, etc). Those could go under Skills.
Thus we can have:
About the role
Company
for prose. We need to decide sections: About the role? Could be "Company Overview". Use heading "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. Use "About the role" for company overview and job description? Might be better to have "About the role" for company overview and job description summary. Then "Responsibilities" for essential duties. Then "Requirements" or "Qualifications" for qualifications. Then "Skills" maybe for skill list? Could combine. Then "Benefits" for benefits package. "Physical Demands" and "Work Environment" maybe not in list but we can include as separate sections if they have content. The instruction says prefer a few substantive sections over many thin ones. But we must include sections only when posting has real specific content. We have content for Physical Demands and Work Environment; they are substantive. Should we include them? Possibly yes, but they are not in the example list; but we can still use h3 with those headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we should stick to those headings; but we can also add others if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. So we should map content to those headings only. So we need to fit Physical Demands and Work Environment into maybe "Responsibilities" or "Requirements"? Not ideal. But maybe we can omit them? However instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit Physical Demands and Work Environment, we lose info. But we could incorporate them into "Responsibilities" or "Requirements" as prose. That would preserve info while using allowed headings. Let's do that: include Physical Demands and Work Environment details within Responsibilities or Requirements as paragraphs.
We also have "Other" section: "Other duties as may be assigned." That's generic; could be omitted as boilerplate? It's not specific; maybe we can drop as filler. Also "Each employee’s primary objective..." that's generic; maybe drop.
We need to include Benefits: "competitive wages, a generous benefits package and a friendly, dynamic working environment." That's substantive.
We need to include Pay? Not explicit. So skip Pay section.
Schedule? Not explicit. Skip.
Now structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. So we should map content to those headings only. So we need to fit Physical Demands and Work Environment into maybe "Responsibilities" or "Requirements"? Not ideal. But maybe we can omit them? However instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit Physical Demands and Work Environment, we lose info. But we could incorporate them into "Responsibilities" or "Requirements" as prose. That would preserve info while using allowed headings. Let's do that: include Physical Demands and Work Environment details within Responsibilities or Requirements as paragraphs.
We also have "Other" section: "Other duties as may be assigned." That's generic; could be omitted as boilerplate? It's not specific; maybe we can drop as filler. Also "Each employee’s primary objective..." that's generic; maybe drop.
We need to include Benefits: "competitive wages, a generous benefits package and a friendly, dynamic working environment." That's substantive.
We need to include Pay? Not explicit. So skip Pay section.
Schedule? Not explicit. Skip.
Now structure:
About the role
Company overview: FUJIFILM Dimatix Inc. ... (the paragraph about printheads, locations, etc.)
Job Description SKILL ... (the skill bullet? Actually there is a "SKILL" heading with subpoints: Applies acquired job skills... etc. That's a list of skill statements. We'll treat as list under Skills maybe. But we have Skills section separate. Let's parse. The posting includes: Job Description SKILL Applies acquired job skills and company policies and procedures to complete assigned tasks. JOB COMPLEXITY Works on assignments that are semi-routine in nature but recognizes the need for occasional deviation from accepted practice. SUPERVISION Normally follows established procedures on routine work, requires instructions only on new assignments. Experience Typically requires a minimum of 1 - 2 years of related experience. Then "Essential Duties & Responsibilities" with many bullet-like sentences. Then "Supervisory Responsibilities None" Then "Qualifications" with required and desired. Then "Physical Demands" Then "Work Environment" Then "Other" Then benefits line. Thus we can map: About the role: Company Overview + Job Description (skill, complexity, supervision, experience) maybe. Responsibilities: Essential Duties & Responsibilities (list). Requirements: Qualifications (required) plus maybe desired? Could be separate Skills? But we have Skills section; we could put skill list from Job Description SKILL etc under Skills. Benefits: benefits line. We need to avoid filler like "commensurate with experience". Not present. Let's craft. First, About the role: combine company overview paragraph and the Job Description skill/complexity/supervision/experience. We'll output:
About the role
At FUJIFILM Dimatix Inc., printing and material deposition devices are only as good as their printheads. We are a recognized leader in the manufacturing and design of durable and productive drop-on-demand inkjet printheads that power cutting-edge systems, as well as integrated inkjet solutions that add digital inkjet capabilities to other equipment. These are part of the digitization and transformation of many applications such as commercial printing, graphics, label & packaging, additive manufacturing, ceramic tiles, textiles, electronics and life science research. We’re looking for forward-thinkers eager to spark innovation in inkjet technology. Bring your talents to a team built on collaboration, creativity, and a passion for excellence. At FUJIFILM Dimatix, every product we make begins with the extraordinary people behind it. Join us for groundbreaking work in a flexible, engaging environment. We’re based in two incredible locations: Lebanon, New Hampshire, surrounded by picturesque New England landscapes, and Santa Clara, California, a dynamic hub in Silicon Valley with a mix of innovation, diversity, and sunshine. Fujifilm is globally headquartered in Tokyo with over 70,000 employees across four key business segments of healthcare, electronics, business innovation, and imaging. We are guided and united by our Group Purpose of “giving our world more smiles.” Visit: https://www.fujifilm.com/us/en/about/region/careers
Skill: Applies acquired job skills and company policies and procedures to complete assigned tasks.
Job Complexity: Works on assignments that are semi-routine in nature but recognizes the need for occasional deviation from accepted practice.
Supervision: Normally follows established procedures on routine work, requires instructions only on new assignments.
Experience: Typically requires a minimum of 1 - 2 years of related experience.
But we need to use- for any list of duties/requirements/benefits. The above are not lists; they are prose. Could be
. That's fine. Now Responsibilities: list of essential duties. We'll extract each sentence as
- .
List:
- Provide service and customer support during field visits and onsite print trials.
- Travel to customer sites to perform equipment installation, repair, maintenance and testing.
- Diagnose technical issues, determine and implement proper solutions.
- Provide pre-sales samples for future business opportunities.
- Create and modify graphics appropriate for the best images for customer samples.
- Performs basic experiments and tests on varied electromechanical systems in a laboratory environment.
- Performs basic set up of equipment in a laboratory environment.
- Correlates and reports results and observations of testing and experiments to engineering using databases and spreadsheet computer programs.
- Produce timely and detailed service reports.
- Works from written/verbal instructions, specifications, technical manuals and engineering sketches.
- Uses a variety of imaging equipment and software associated with image manipulation.
- Basic repairs to test equipment and components, if applicable.
- Performs testing of customized inkjet systems.
- Assembles, disassembles, modifies, reworks, refurbishes, repairs, reassembles and tests units as required, using: Blueprints, sketches, engineering specifications and standard testing equipment, applying knowledge of mechanical, electrical and optical interrelations.
- Compiles and records test results.
- Usage of computer skills such as Excel, Word and database applications.
- Works closely with customers, engineers and senior technicians.
- Travel domestically and abroad – Extensive travel may be required.
We should keep the exact wording. Some sentences start with verb forms; keep as is.
Now Requirements: we have Qualifications required and desired. Could combine.
Required:
- High school degree or equivalent and 1-2 years of related experience.
- Working knowledge of the Microsoft Office product suite (Word, Excel, PowerPoint, etc.)
- Knowledge of basic wiring, mechanical workings and electronics.
- Strong attention to detail.
- Effective written and verbal communication skills.
- Ability and desire to contribute both independently and as part of a team.
- Ability to work flexible shifts and to adapt to changing work schedules.
- Ability to remain calm and professional in high pressure situations and work effectively to resolve the issues.
- Ability to follow prescribed safety rules and regulations.
- Ability to work with minimal supervision.
- Ability to read, analyze and interpret formal and informal oral and written instructions, technical procedures and procedure manuals.
- Ability to effectively present information and respond to questions from customers, engineers, peers and management.
- Ability to create / manipulate graphic imaging in various formats and programs.
- Ability to understand the various graphic formats required by FIS printers to create graphics for printing.
- Familiar with Adobe Photoshop and Adobe Illustrator.
- Basic knowledge of color and color science; screening and halftone techniques.
- Ability to work from a foreign site with limited infrastructure or oversight.
- Ability to travel domestic and abroad, either alone or as a part of a team.
Desired:
- Two-year technical degree
We could put desired under Requirements as well, maybe as a separate list labeled "Desired". But we only have one heading Requirements; we could include both required and desired as lists, maybe with a note.
We'll output:
Requirements
Required
- ...
Desired
- ...
for section headings; using
might be okay as subheading? The instruction didn't forbid other headings, but said use
for section headings (e.g...). It didn't say we cannot use other headings. Safer to stick to
only. Could combine required and desired into one list with note? Might lose nuance. Could make two
- under same
and precede with
indicating required vs desired. That's okay. We'll do:
Requirements
Required:
- ...
Desired:
- ...
About the role
Company