CGI Coordinator
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Content:
- Intro: "Marks, part of the Propelis Group, Marks is a consumer experience agency ..." This is about the company. Could be "About the role"? Actually "Position Summary" then "Provide data governance, workflow management and support the Production team." That's a summary.
- Essential Responsibilities, Accountabilities & Results: list bullet points.
- Plus Skills: list.
- Competency Requirements: list.
- Physical Requirements: list.
- Qualifications Experience Required: list (duplicate of competency?).
- About Propelis: description.
- EEO etc: boilerplate to remove.
- Compensation: "Our compensation reflects the cost of labor across several U.S. geographic markets, and we pay differently based on those defined markets. The U.S. pay range for this position is $22.00 - $24.00 USD hourly." That's Pay.
- Benefits: "Group benefits currently include a selection of health care plans with prescription drug coverage, dental plan, vision plan, basic and supplemental life insurance, a flexible spending account for medical and dependent care expenses or a health savings account based on plan selection, short/long term disability and 401(k) Savings Plan."
- Schedule: "This is a remote position in the US. We are open to candidates in various states, with the exception of those residing in the following: AK, DC, DE, ME, NH, NM, OK, HI, MS, MT, NV, NE, ND, SD, VT, WY, and WV." That's location restrictions, not schedule. No explicit schedule like full-time/part-time. So we should not create Schedule section unless posting actually states them. It doesn't state schedule, so omit.
- Pay: we have pay range.
- Benefits: we have benefits.
- About the role: maybe we can combine Position Summary and About Propelis? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- About the role: could be Position Summary + maybe company description? The posting includes "Position SummaryProvide data governance, workflow management and support the Production team." That's a short summary. Also there is "About Propelis:" description. Could be considered "About the role" or "About the company". The instruction says "About the role" as example heading. We'll include a section with heading About the role
and include the Position Summary and maybe a brief about the company? But we must preserve ALL substantive information; we cannot invent or summarize away detail. So we need to include the Position Summary text exactly. Also we could include the About Propelis description under maybe "About the company" but not a prescribed heading. Since only allowed headings are those examples, we could put About Propelis under "About the role" as well, but that might be mixing. However we must not invent headings not in list. We could create a section About the role
containing the Position Summary paragraph. Then we could also include a separate About Propelis
? Not allowed per examples but maybe we can still use for any section heading; the examples are just examples, not exclusive list? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can use other headings as long as they are . Safer to use headings that match content: About the role, Responsibilities, Skills, Competency Requirements (maybe Requirements), Qualifications, Benefits, Pay. Physical Requirements maybe could be under Requirements? But we have a separate Physical Requirements section; we could include under Requirements heading.
We must not repeat the job title as a heading. Not needed.
We must remove boilerplate: EEO, legal, etc.
We must not include duplicated lines.
We need to preserve all substantive information.
Let's extract substantive content:
Company intro: "Marks, part of the Propelis Group, Marks is a consumer experience agency creating engaging moments across the entire brand spectrum—from brand design and packaging, to content and consumer connections. We are a collaborative global network of 1,900+ team members across 25+ studios and 20+ countries, partnering with some of the world’s most recognized brands to solve complex business challenges through design, strategy, and craft."
Position Summary: "Provide data governance, workflow management and support the Production team."
Essential Responsibilities, Accountabilities & Results (list):
- Maintain the workflow of the CGI Production process
- Manage task assignments and priorities for the artists
- Provide artists with support to enable them to complete assigned tasks
- Responsible for data governance to ensure accuracy
- Publish client notes within project management system
- Manage incoming data, products and tasking
Plus Skills:
- Shotgun/Shotgrid/Flow experience
- Experience working in a CGI environment
Competency Requirements (list):
- Excellent administrative, organizational, and interpersonal skills
- General understanding of Microsoft Excel or equivalent experience
- Strong analytical skills
- Self-starter and strong initiative
- Able to work well under pressure
- Able to multi-task, troubleshoot and prioritize
- Able to work effectively with a wide variety of personalities
- Able to adapt quickly to ever-evolving tech and workflow adaptations
- Able to communicate succinctly and professionally with staff and clients
Physical Requirements (list):
- Regularly required to sit; use hands to finger, handle, or feel and talk or hear
- Frequently required to stand; walk and reach with hands and arms
- Occasionally lift and/or move up to 10 pounds
- Vision, color vision and ability to adjust focus
Qualifications Experience Required (list) - appears duplicate of competency requirements but we must preserve; it's same list as competency requirements. We'll include maybe under Qualifications.
About Propelis:
- "Propelis is a portfolio of global marketing services and technology companies with a combined legacy of 150+ years, 2,000+ clients, 9,000 employees, and operations across 30 countries. Propelis provides the scale and support of a global organization while preserving the unique culture and identity of each company in its portfolio.For more information visit: www.MakeMarks.com"
Pay:
- "Our compensation reflects the cost of labor across several U.S. geographic markets, and we pay differently based on those defined markets. The U.S. pay range for this position is $22.00 - $24.00 USD hourly. Ultimately, in determining pay, we will consider the successful candidate’s location, experience, and other job-related factors."
Benefits:
- "Group benefits currently include a selection of health care plans with prescription drug coverage, dental plan, vision plan, basic and supplemental life insurance, a flexible spending account for medical and dependent care expenses or a health savings account based on plan selection, short/long term disability and 401(k) Savings Plan."
Schedule/Location: Not schedule but location restrictions. Could be under "Location" but not in examples. Might omit as not schedule. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state location restrictions but not schedule. So we could omit schedule section. However location info is substantive; we could include under a heading like "Location" but not in examples. 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 "e.g." So we could add a Location heading. Safer to include location info under maybe "About the role" or "About Propelis"? Not ideal. Could add a Location
section. Since it's not prohibited, I'll include it.
But we must not create Schedule section unless posting actually states them. It doesn't state schedule, so we won't.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
About the role
and include the Position Summary and maybe a brief about the company? But we must preserve ALL substantive information; we cannot invent or summarize away detail. So we need to include the Position Summary text exactly. Also we could include the About Propelis description under maybe "About the company" but not a prescribed heading. Since only allowed headings are those examples, we could put About Propelis under "About the role" as well, but that might be mixing. However we must not invent headings not in list. We could create a sectionAbout the role
containing the Position Summary paragraph. Then we could also include a separateAbout Propelis
? Not allowed per examples but maybe we can still use for any section heading; the examples are just examples, not exclusive list? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can use other headings as long as they are . Safer to use headings that match content: About the role, Responsibilities, Skills, Competency Requirements (maybe Requirements), Qualifications, Benefits, Pay. Physical Requirements maybe could be under Requirements? But we have a separate Physical Requirements section; we could include under Requirements heading.
We must not repeat the job title as a heading. Not needed.
We must remove boilerplate: EEO, legal, etc.
We must not include duplicated lines.
We need to preserve all substantive information.
Let's extract substantive content:
Company intro: "Marks, part of the Propelis Group, Marks is a consumer experience agency creating engaging moments across the entire brand spectrum—from brand design and packaging, to content and consumer connections. We are a collaborative global network of 1,900+ team members across 25+ studios and 20+ countries, partnering with some of the world’s most recognized brands to solve complex business challenges through design, strategy, and craft."
Position Summary: "Provide data governance, workflow management and support the Production team."
Essential Responsibilities, Accountabilities & Results (list):
- Maintain the workflow of the CGI Production process
- Manage task assignments and priorities for the artists
- Provide artists with support to enable them to complete assigned tasks
- Responsible for data governance to ensure accuracy
- Publish client notes within project management system
- Manage incoming data, products and tasking
Plus Skills:
- Shotgun/Shotgrid/Flow experience
- Experience working in a CGI environment
Competency Requirements (list):
- Excellent administrative, organizational, and interpersonal skills
- General understanding of Microsoft Excel or equivalent experience
- Strong analytical skills
- Self-starter and strong initiative
- Able to work well under pressure
- Able to multi-task, troubleshoot and prioritize
- Able to work effectively with a wide variety of personalities
- Able to adapt quickly to ever-evolving tech and workflow adaptations
- Able to communicate succinctly and professionally with staff and clients
Physical Requirements (list):
- Regularly required to sit; use hands to finger, handle, or feel and talk or hear
- Frequently required to stand; walk and reach with hands and arms
- Occasionally lift and/or move up to 10 pounds
- Vision, color vision and ability to adjust focus
Qualifications Experience Required (list) - appears duplicate of competency requirements but we must preserve; it's same list as competency requirements. We'll include maybe under Qualifications.
About Propelis:
- "Propelis is a portfolio of global marketing services and technology companies with a combined legacy of 150+ years, 2,000+ clients, 9,000 employees, and operations across 30 countries. Propelis provides the scale and support of a global organization while preserving the unique culture and identity of each company in its portfolio.For more information visit: www.MakeMarks.com"
Pay:
- "Our compensation reflects the cost of labor across several U.S. geographic markets, and we pay differently based on those defined markets. The U.S. pay range for this position is $22.00 - $24.00 USD hourly. Ultimately, in determining pay, we will consider the successful candidate’s location, experience, and other job-related factors."
Benefits:
- "Group benefits currently include a selection of health care plans with prescription drug coverage, dental plan, vision plan, basic and supplemental life insurance, a flexible spending account for medical and dependent care expenses or a health savings account based on plan selection, short/long term disability and 401(k) Savings Plan."
Schedule/Location: Not schedule but location restrictions. Could be under "Location" but not in examples. Might omit as not schedule. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state location restrictions but not schedule. So we could omit schedule section. However location info is substantive; we could include under a heading like "Location" but not in examples. 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 "e.g." So we could add a Location heading. Safer to include location info under maybe "About the role" or "About Propelis"? Not ideal. Could add a Location
section. Since it's not prohibited, I'll include it.
But we must not create Schedule section unless posting actually states them. It doesn't state schedule, so we won't.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
. Safer to use headings that match content: About the role, Responsibilities, Skills, Competency Requirements (maybe Requirements), Qualifications, Benefits, Pay. Physical Requirements maybe could be under Requirements? But we have a separate Physical Requirements section; we could include under Requirements heading.
We must not repeat the job title as a heading. Not needed.
We must remove boilerplate: EEO, legal, etc.
We must not include duplicated lines.
We need to preserve all substantive information.
Let's extract substantive content:
Company intro: "Marks, part of the Propelis Group, Marks is a consumer experience agency creating engaging moments across the entire brand spectrum—from brand design and packaging, to content and consumer connections. We are a collaborative global network of 1,900+ team members across 25+ studios and 20+ countries, partnering with some of the world’s most recognized brands to solve complex business challenges through design, strategy, and craft."
Position Summary: "Provide data governance, workflow management and support the Production team."
Essential Responsibilities, Accountabilities & Results (list):
- Maintain the workflow of the CGI Production process
- Manage task assignments and priorities for the artists
- Provide artists with support to enable them to complete assigned tasks
- Responsible for data governance to ensure accuracy
- Publish client notes within project management system
- Manage incoming data, products and tasking
Plus Skills:
- Shotgun/Shotgrid/Flow experience
- Experience working in a CGI environment
Competency Requirements (list):
- Excellent administrative, organizational, and interpersonal skills
- General understanding of Microsoft Excel or equivalent experience
- Strong analytical skills
- Self-starter and strong initiative
- Able to work well under pressure
- Able to multi-task, troubleshoot and prioritize
- Able to work effectively with a wide variety of personalities
- Able to adapt quickly to ever-evolving tech and workflow adaptations
- Able to communicate succinctly and professionally with staff and clients
Physical Requirements (list):
- Regularly required to sit; use hands to finger, handle, or feel and talk or hear
- Frequently required to stand; walk and reach with hands and arms
- Occasionally lift and/or move up to 10 pounds
- Vision, color vision and ability to adjust focus
Qualifications Experience Required (list) - appears duplicate of competency requirements but we must preserve; it's same list as competency requirements. We'll include maybe under Qualifications.
About Propelis:
- "Propelis is a portfolio of global marketing services and technology companies with a combined legacy of 150+ years, 2,000+ clients, 9,000 employees, and operations across 30 countries. Propelis provides the scale and support of a global organization while preserving the unique culture and identity of each company in its portfolio.For more information visit: www.MakeMarks.com"
Pay:
- "Our compensation reflects the cost of labor across several U.S. geographic markets, and we pay differently based on those defined markets. The U.S. pay range for this position is $22.00 - $24.00 USD hourly. Ultimately, in determining pay, we will consider the successful candidate’s location, experience, and other job-related factors."
Benefits:
- "Group benefits currently include a selection of health care plans with prescription drug coverage, dental plan, vision plan, basic and supplemental life insurance, a flexible spending account for medical and dependent care expenses or a health savings account based on plan selection, short/long term disability and 401(k) Savings Plan."
Schedule/Location: Not schedule but location restrictions. Could be under "Location" but not in examples. Might omit as not schedule. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state location restrictions but not schedule. So we could omit schedule section. However location info is substantive; we could include under a heading like "Location" but not in examples. 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 "e.g." So we could add a Location heading. Safer to include location info under maybe "About the role" or "About Propelis"? Not ideal. Could add a Location
section. Since it's not prohibited, I'll include it.
But we must not create Schedule section unless posting actually states them. It doesn't state schedule, so we won't.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll structure:
About the role
Location
section. Since it's not prohibited, I'll include it. But we must not create Schedule section unless posting actually states them. It doesn't state schedule, so we won't. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:About the role
Marks, part of the Propelis Group, Marks is a consumer experience agency creating engaging moments across the entire brand spectrum—from brand design and packaging, to content and consumer connections. We are a collaborative global network of 1,900+ team members across 25+ studios and 20+ countries, partnering with some of the world’s most recognized brands to solve complex business challenges through design, strategy, and craft.
Position Summary: Provide data governance, workflow management and support the Production team.
Responsibilities
- Maintain the workflow of the CGI Production process
- Manage task assignments and priorities for the artists
- Provide artists with support to enable them to complete assigned tasks
- Responsible for data governance to ensure accuracy
- Publish client notes within project management system
- Manage incoming data, products and tasking
Skills
- Shotgun/Shotgrid/Flow experience
- Experience working in a CGI environment
Requirements
Physical Requirements:
- Regularly required to sit; use hands to finger, handle, or feel and talk or hear
- Frequently required to stand; walk and reach with hands and arms
- Occasionally lift and/or move up to 10 pounds
- Vision, color vision and ability to adjust focus
Qualifications
- Excellent administrative, organizational, and interpersonal skills
- General understanding of Microsoft Excel or equivalent experience
- Strong analytical skills
- Self-starter and strong initiative
- Able to work well under pressure
- Able to multi-task, troubleshoot and prioritize
- Able to work effectively with a wide variety of personalities
- Able to adapt quickly to ever-evolving tech and workflow adaptations
- Able to communicate succinctly and professionally with staff and clients
About Propelis
Propelis is a portfolio of global marketing services and technology companies with a combined legacy of 150+ years, 2,000+ clients, 9,000 employees, and operations across 30 countries. Propelis provides the scale and support of a global organization while preserving the unique culture and identity of each company in its portfolio. For more information visit: www.MakeMarks.com
Pay
Our compensation reflects the cost of labor across several U.S. geographic markets, and we pay differently based on those defined markets. The U.S. pay range for this position is $22.00 - $24.00 USD hourly. Ultimately, in determining pay, we will consider the successful candidate’s location, experience, and other job-related factors.
Benefits
Group benefits currently include a selection of health care plans with prescription drug coverage, dental plan, vision plan, basic and supplemental life insurance, a flexible spending account for medical and dependent care expenses or a health savings account based on plan selection, short/long term disability and 401(k) Savings Plan.
Location
This is a remote position in the US. We are open to candidates