Digital Asset Assistant (Part-Time)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Who We Are (company description) maybe "About the role"? Actually there is "Who We Are" repeated, then "Role Summary", then "Key Responsibilities", then "Skills And Qualifications", then "What One Will Gain Experience In", then "Physical Demands:", then "Beck’s Benefits". Also there is "Join our team..." repeated. No explicit Pay or Schedule. So we should not create Pay or Schedule sections. Benefits section exists: we have details about benefits. Should we include Benefits heading? Yes, there is specific content about benefits. Also maybe "Physical Demands" could be under Requirements? But we have no specific heading for Physical Demands; we could include under Requirements or Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate headings based on content. We have "Who We Are" (company overview) maybe map to "About the role"? Actually "About the role" is more about the role description; we have Role Summary. Could use "About the role" heading for Role Summary. Responsibilities heading for Key Responsibilities. Requirements/Qualifications/Skills: we have Skills And Qualifications and also What One Will Gain Experience In (maybe benefits? Actually that's what you'll gain). Could treat "Skills And Qualifications" as Skills heading. Requirements maybe not present; we could omit. Qualifications maybe also not separate. But we could combine Skills and Qualifications under Skills heading. The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role (Role Summary), Responsibilities, Skills, Benefits. Also maybe "What One Will Gain Experience In" could be under Benefits? Actually it's about experience gained, not benefits. Could be under "About the role" or separate "Learning Outcomes". But not in list of allowed headings; we could omit or incorporate into About the role. Probably better to include as part of About the role or as a separate section like "What You'll Gain". But not in allowed headings; we could still use for any heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate; but we could also use other headings? It says use for section headings (e.g. ...). Likely they expect only those headings. So we should map content to those headings. Let's map:
- About the role: combine Who We Are and Role Summary? Actually Who We Are is company description; Role Summary is role description. Could put both under About the role.
- Responsibilities: Key Responsibilities.
- Skills: Skills And Qualifications (also maybe What One Will Gain Experience In? but that's not skills). We'll put Skills And Qualifications under Skills.
- Benefits: Beck’s Benefits.
We should not include Requirements, Qualifications, Pay, Schedule as they lack specific content.
We must preserve all substantive information; not invent or summarize away detail. So we need to include all details from those sections.
We need to format lists with - . For prose use
. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's EEO statements repeated; we should remove them. Also duplicated "Who We Are" paragraph appears twice; we need to keep only one copy. Also repeated "Join our team and build your future with Beck." and EEO again; remove duplicates.
We need to preserve substantive info: company description, role summary, responsibilities list, skills/qualifications list, what one will gain experience list (maybe we need to include that somewhere; if we omit, we lose info. So we need to include that content. Where to put? Could be under About the role as a sub-section? But we cannot add new headings not in list; but we could include as a paragraph under About the role. That would preserve info. Similarly Physical Demands: we need to preserve that info; could be under Skills or maybe under About the role? Probably better to include as a paragraph under Skills? But Physical Demands is not skills. Could be under About the role as well. However we must not invent headings; we can just add
paragraphs under existing sections.
Thus structure:
About the role
Who We Are: ... (company description)
Role Summary: ... (the paragraph)
What One Will Gain Experience In: ... (list)
Physical Demands: ... (sentence)
But we need to keep the list for "What One Will Gain Experience In" as a list. The text: "Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing". It seems missing commas; but we can treat each as separate items. We'll split by capital letters? Better to keep as is? The original: "Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing". It seems missing spaces. We'll just keep as a single sentence? But we need to preserve info; we can make a list splitting by capital letters? Might be risky. Perhaps we keep as a paragraph as given.
Similarly Physical Demands: "Physical Demands: Frequently required to sit, stand, and move about the office; frequently operates a computer and other office productivity equipment; frequently lift and move up to ten pounds and occasionally lift and move up to fifty pounds; constantly communicates with HR team, Beck employees, and external vendors; ability to adhere to timely and consistent attendance." We'll keep as paragraph.
Now Responsibilities: need to parse the block: "Gather project photography, renderings and other visual assets from internal project folders and approved sources.Organize and rename digital files according to established Marketing standards.Upload project photography, renderings and graphics into OpenAsset.Tag and categorize assets using established project information, image types, keywords and metadata.Review existing OpenAsset records for missing, duplicate, outdated or incorrectly categorized assets.Assist with ongoing cleanup of the digital asset library.Review assigned projects to identify gaps in available imagery, such as:Missing completed project photographyProjects with renderings but no final photographyLow-resolution or outdated imageryMissing interior, exterior or key project viewsDuplicate or incorrectly filed assetsMaintain a tracking list of missing assets, outstanding requests and completed project reviews.Help locate higher-resolution, original or updated image files from approved internal sources.Flag missing imagery or asset needs for Marketing team members to follow up on with project teams or other contacts.Support priority projects and recently completed projects to help ensure they have complete and organized visual asset collections.Assist with other Marketing organization and digital content tasks as assigned."
We need to split into list items. Each sentence seems separated by period but no spaces after periods. We'll split by periods and then trim. We'll create - for each.
Skills And Qualifications: list items: "Current college student preferred.Strong organizational skills and attention to detail.Comfortable working with digital files, folders and cloud-based systems.Ability to follow established procedures, naming conventions and tagging standards.Basic familiarity with Microsoft Office and Microsoft 365.Comfortable learning new software and digital tools.Ability to work independently once tasks and expectations are established.Interest in marketing, architecture, construction, photography, communications or digital content is a plus.Previous experience with OpenAsset is not required. Training will be provided."
We'll split similarly.
Benefits: paragraph: "At Beck our team member experience goes beyond your day-to-day work activities – we also want to support the rest of your life goals, milestones and challenges. We strive for thrive – we want you to thrive in your wellbeing, finances, and community. In Addition To Robust Coverage For Medical, Dental, Vision, Life & Disability Benefits, Beck Is Pleased To Offer Its Team Members: 401k match and free SmartDollar program for financial wellnessFree dedicated financial coachPersonal health & fitness program for tracking activities & earning rewardsPaid family leaveHealth discounts on medical premiumsFree comprehensive health screeningsFree health coach program for weight-loss & hypertension managementFinancial & behavioral support for family forming journeys (ex. Fertility, adoption, pregnancy, and parenthood).Free Life CoachPet insurance discountOrganized projects and events to support our communities"
We need to split into list items after colon? The benefits list after colon seems missing spaces. We'll split by capital letters? Might be messy. Perhaps we keep as a paragraph preserving the text as is. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep as a paragraph, even if lacking formatting. That's acceptable.
Now we need to remove duplicated lines: The repeated "Who We Are" paragraph appears twice; we keep one. Also repeated EEO statements; we remove them. Also repeated "Join our team and build your future with Beck." appears multiple times; we can keep one maybe? But it's not substantive? It's a call to action; maybe considered boilerplate? It's not EEO but could be considered application instruction? It's a tagline; maybe we can keep one instance? The instruction: remove duplicated lines. So we should keep only one copy of that line. Where does it appear? At end of responsibilities? Actually after responsibilities there is "Join our team and build your future with Beck." Then later after benefits there is again "Join our team and build your future with Beck." plus EEO again. We'll keep one instance maybe under About the role or at end? But it's not a heading; we can keep as a paragraph under About the role? Might be considered boilerplate but not explicitly listed to remove; it's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It could be considered application instruction? It's a call to apply; maybe considered application instruction. Safer to remove it. The instruction: remove duplicated lines, and application instructions. So we should remove "Join our team and build your future with Beck." as it's likely an application instruction. So we will not include it.
Now produce HTML fragment.
Let's craft.
First, About the role section:
About the role
We're The Beck Group, the largest and most innovative integrated building firm in the country. We are focused on delivering design and construction excellence on a broad range of project types. Headquartered in downtown Dallas, with offices in Atlanta, Austin, Charlotte, Denver, Fort Lauderdale, Fort Worth, Mexico City, and Tampa, we believe a better process and outcome results from working together. At Beck, you will find yourself surrounded by passionate colleagues who have a collaborative mindset and care about each other. We are committed to hiring the best and brightest within our industry, and that's why we are seeking experienced professionals like you to help transform the industry and continue building Beck's respected reputation.
The Digital Asset Assistant is a part-time position supporting the Marketing team with the organization and maintenance of Beck’s project photography, renderings and other digital assets. This role is well suited for a college student interested in gaining professional experience in marketing, architecture, construction, photography, communications or digital content management. The position will provide hands-on experience working with project imagery and digital asset management while helping ensure Beck’s visual resources are organized, complete and easily accessible. The Digital Asset Assistant will work under the direction of the Marketing team to gather, organize, tag and upload assets into OpenAsset, as well as assist with identifying gaps and improving existing project records.
What One Will Gain Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing
Physical Demands: Frequently required to sit, stand, and move about the office; frequently
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate; but we could also use other headings? It says use for section headings (e.g. ...). Likely they expect only those headings. So we should map content to those headings. Let's map:
- About the role: combine Who We Are and Role Summary? Actually Who We Are is company description; Role Summary is role description. Could put both under About the role.
- Responsibilities: Key Responsibilities.
- Skills: Skills And Qualifications (also maybe What One Will Gain Experience In? but that's not skills). We'll put Skills And Qualifications under Skills.
- Benefits: Beck’s Benefits.
We should not include Requirements, Qualifications, Pay, Schedule as they lack specific content.
We must preserve all substantive information; not invent or summarize away detail. So we need to include all details from those sections.
We need to format lists with - . For prose use
. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's EEO statements repeated; we should remove them. Also duplicated "Who We Are" paragraph appears twice; we need to keep only one copy. Also repeated "Join our team and build your future with Beck." and EEO again; remove duplicates.
We need to preserve substantive info: company description, role summary, responsibilities list, skills/qualifications list, what one will gain experience list (maybe we need to include that somewhere; if we omit, we lose info. So we need to include that content. Where to put? Could be under About the role as a sub-section? But we cannot add new headings not in list; but we could include as a paragraph under About the role. That would preserve info. Similarly Physical Demands: we need to preserve that info; could be under Skills or maybe under About the role? Probably better to include as a paragraph under Skills? But Physical Demands is not skills. Could be under About the role as well. However we must not invent headings; we can just add
paragraphs under existing sections.
Thus structure:
About the role
Who We Are: ... (company description)
Role Summary: ... (the paragraph)
What One Will Gain Experience In: ... (list)
Physical Demands: ... (sentence)
But we need to keep the list for "What One Will Gain Experience In" as a list. The text: "Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing". It seems missing commas; but we can treat each as separate items. We'll split by capital letters? Better to keep as is? The original: "Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing". It seems missing spaces. We'll just keep as a single sentence? But we need to preserve info; we can make a list splitting by capital letters? Might be risky. Perhaps we keep as a paragraph as given.
Similarly Physical Demands: "Physical Demands: Frequently required to sit, stand, and move about the office; frequently operates a computer and other office productivity equipment; frequently lift and move up to ten pounds and occasionally lift and move up to fifty pounds; constantly communicates with HR team, Beck employees, and external vendors; ability to adhere to timely and consistent attendance." We'll keep as paragraph.
Now Responsibilities: need to parse the block: "Gather project photography, renderings and other visual assets from internal project folders and approved sources.Organize and rename digital files according to established Marketing standards.Upload project photography, renderings and graphics into OpenAsset.Tag and categorize assets using established project information, image types, keywords and metadata.Review existing OpenAsset records for missing, duplicate, outdated or incorrectly categorized assets.Assist with ongoing cleanup of the digital asset library.Review assigned projects to identify gaps in available imagery, such as:Missing completed project photographyProjects with renderings but no final photographyLow-resolution or outdated imageryMissing interior, exterior or key project viewsDuplicate or incorrectly filed assetsMaintain a tracking list of missing assets, outstanding requests and completed project reviews.Help locate higher-resolution, original or updated image files from approved internal sources.Flag missing imagery or asset needs for Marketing team members to follow up on with project teams or other contacts.Support priority projects and recently completed projects to help ensure they have complete and organized visual asset collections.Assist with other Marketing organization and digital content tasks as assigned."
We need to split into list items. Each sentence seems separated by period but no spaces after periods. We'll split by periods and then trim. We'll create - for each.
Skills And Qualifications: list items: "Current college student preferred.Strong organizational skills and attention to detail.Comfortable working with digital files, folders and cloud-based systems.Ability to follow established procedures, naming conventions and tagging standards.Basic familiarity with Microsoft Office and Microsoft 365.Comfortable learning new software and digital tools.Ability to work independently once tasks and expectations are established.Interest in marketing, architecture, construction, photography, communications or digital content is a plus.Previous experience with OpenAsset is not required. Training will be provided."
We'll split similarly.
Benefits: paragraph: "At Beck our team member experience goes beyond your day-to-day work activities – we also want to support the rest of your life goals, milestones and challenges. We strive for thrive – we want you to thrive in your wellbeing, finances, and community. In Addition To Robust Coverage For Medical, Dental, Vision, Life & Disability Benefits, Beck Is Pleased To Offer Its Team Members: 401k match and free SmartDollar program for financial wellnessFree dedicated financial coachPersonal health & fitness program for tracking activities & earning rewardsPaid family leaveHealth discounts on medical premiumsFree comprehensive health screeningsFree health coach program for weight-loss & hypertension managementFinancial & behavioral support for family forming journeys (ex. Fertility, adoption, pregnancy, and parenthood).Free Life CoachPet insurance discountOrganized projects and events to support our communities"
We need to split into list items after colon? The benefits list after colon seems missing spaces. We'll split by capital letters? Might be messy. Perhaps we keep as a paragraph preserving the text as is. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep as a paragraph, even if lacking formatting. That's acceptable.
Now we need to remove duplicated lines: The repeated "Who We Are" paragraph appears twice; we keep one. Also repeated EEO statements; we remove them. Also repeated "Join our team and build your future with Beck." appears multiple times; we can keep one maybe? But it's not substantive? It's a call to action; maybe considered boilerplate? It's not EEO but could be considered application instruction? It's a tagline; maybe we can keep one instance? The instruction: remove duplicated lines. So we should keep only one copy of that line. Where does it appear? At end of responsibilities? Actually after responsibilities there is "Join our team and build your future with Beck." Then later after benefits there is again "Join our team and build your future with Beck." plus EEO again. We'll keep one instance maybe under About the role or at end? But it's not a heading; we can keep as a paragraph under About the role? Might be considered boilerplate but not explicitly listed to remove; it's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It could be considered application instruction? It's a call to apply; maybe considered application instruction. Safer to remove it. The instruction: remove duplicated lines, and application instructions. So we should remove "Join our team and build your future with Beck." as it's likely an application instruction. So we will not include it.
Now produce HTML fragment.
Let's craft.
First, About the role section:
About the role
We're The Beck Group, the largest and most innovative integrated building firm in the country. We are focused on delivering design and construction excellence on a broad range of project types. Headquartered in downtown Dallas, with offices in Atlanta, Austin, Charlotte, Denver, Fort Lauderdale, Fort Worth, Mexico City, and Tampa, we believe a better process and outcome results from working together. At Beck, you will find yourself surrounded by passionate colleagues who have a collaborative mindset and care about each other. We are committed to hiring the best and brightest within our industry, and that's why we are seeking experienced professionals like you to help transform the industry and continue building Beck's respected reputation.
The Digital Asset Assistant is a part-time position supporting the Marketing team with the organization and maintenance of Beck’s project photography, renderings and other digital assets. This role is well suited for a college student interested in gaining professional experience in marketing, architecture, construction, photography, communications or digital content management. The position will provide hands-on experience working with project imagery and digital asset management while helping ensure Beck’s visual resources are organized, complete and easily accessible. The Digital Asset Assistant will work under the direction of the Marketing team to gather, organize, tag and upload assets into OpenAsset, as well as assist with identifying gaps and improving existing project records.
What One Will Gain Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing
Physical Demands: Frequently required to sit, stand, and move about the office; frequently
- . For prose use
. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's EEO statements repeated; we should remove them. Also duplicated "Who We Are" paragraph appears twice; we need to keep only one copy. Also repeated "Join our team and build your future with Beck." and EEO again; remove duplicates. We need to preserve substantive info: company description, role summary, responsibilities list, skills/qualifications list, what one will gain experience list (maybe we need to include that somewhere; if we omit, we lose info. So we need to include that content. Where to put? Could be under About the role as a sub-section? But we cannot add new headings not in list; but we could include as a paragraph under About the role. That would preserve info. Similarly Physical Demands: we need to preserve that info; could be under Skills or maybe under About the role? Probably better to include as a paragraph under Skills? But Physical Demands is not skills. Could be under About the role as well. However we must not invent headings; we can just add
paragraphs under existing sections. Thus structure:
About the role
Who We Are: ... (company description)
Role Summary: ... (the paragraph)
What One Will Gain Experience In: ... (list)
Physical Demands: ... (sentence)
But we need to keep the list for "What One Will Gain Experience In" as a list. The text: "Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing". It seems missing commas; but we can treat each as separate items. We'll split by capital letters? Better to keep as is? The original: "Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing". It seems missing spaces. We'll just keep as a single sentence? But we need to preserve info; we can make a list splitting by capital letters? Might be risky. Perhaps we keep as a paragraph as given. Similarly Physical Demands: "Physical Demands: Frequently required to sit, stand, and move about the office; frequently operates a computer and other office productivity equipment; frequently lift and move up to ten pounds and occasionally lift and move up to fifty pounds; constantly communicates with HR team, Beck employees, and external vendors; ability to adhere to timely and consistent attendance." We'll keep as paragraph. Now Responsibilities: need to parse the block: "Gather project photography, renderings and other visual assets from internal project folders and approved sources.Organize and rename digital files according to established Marketing standards.Upload project photography, renderings and graphics into OpenAsset.Tag and categorize assets using established project information, image types, keywords and metadata.Review existing OpenAsset records for missing, duplicate, outdated or incorrectly categorized assets.Assist with ongoing cleanup of the digital asset library.Review assigned projects to identify gaps in available imagery, such as:Missing completed project photographyProjects with renderings but no final photographyLow-resolution or outdated imageryMissing interior, exterior or key project viewsDuplicate or incorrectly filed assetsMaintain a tracking list of missing assets, outstanding requests and completed project reviews.Help locate higher-resolution, original or updated image files from approved internal sources.Flag missing imagery or asset needs for Marketing team members to follow up on with project teams or other contacts.Support priority projects and recently completed projects to help ensure they have complete and organized visual asset collections.Assist with other Marketing organization and digital content tasks as assigned." We need to split into list items. Each sentence seems separated by period but no spaces after periods. We'll split by periods and then trim. We'll create - for each.
Skills And Qualifications: list items: "Current college student preferred.Strong organizational skills and attention to detail.Comfortable working with digital files, folders and cloud-based systems.Ability to follow established procedures, naming conventions and tagging standards.Basic familiarity with Microsoft Office and Microsoft 365.Comfortable learning new software and digital tools.Ability to work independently once tasks and expectations are established.Interest in marketing, architecture, construction, photography, communications or digital content is a plus.Previous experience with OpenAsset is not required. Training will be provided."
We'll split similarly.
Benefits: paragraph: "At Beck our team member experience goes beyond your day-to-day work activities – we also want to support the rest of your life goals, milestones and challenges. We strive for thrive – we want you to thrive in your wellbeing, finances, and community. In Addition To Robust Coverage For Medical, Dental, Vision, Life & Disability Benefits, Beck Is Pleased To Offer Its Team Members: 401k match and free SmartDollar program for financial wellnessFree dedicated financial coachPersonal health & fitness program for tracking activities & earning rewardsPaid family leaveHealth discounts on medical premiumsFree comprehensive health screeningsFree health coach program for weight-loss & hypertension managementFinancial & behavioral support for family forming journeys (ex. Fertility, adoption, pregnancy, and parenthood).Free Life CoachPet insurance discountOrganized projects and events to support our communities"
We need to split into list items after colon? The benefits list after colon seems missing spaces. We'll split by capital letters? Might be messy. Perhaps we keep as a paragraph preserving the text as is. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep as a paragraph, even if lacking formatting. That's acceptable.
Now we need to remove duplicated lines: The repeated "Who We Are" paragraph appears twice; we keep one. Also repeated EEO statements; we remove them. Also repeated "Join our team and build your future with Beck." appears multiple times; we can keep one maybe? But it's not substantive? It's a call to action; maybe considered boilerplate? It's not EEO but could be considered application instruction? It's a tagline; maybe we can keep one instance? The instruction: remove duplicated lines. So we should keep only one copy of that line. Where does it appear? At end of responsibilities? Actually after responsibilities there is "Join our team and build your future with Beck." Then later after benefits there is again "Join our team and build your future with Beck." plus EEO again. We'll keep one instance maybe under About the role or at end? But it's not a heading; we can keep as a paragraph under About the role? Might be considered boilerplate but not explicitly listed to remove; it's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It could be considered application instruction? It's a call to apply; maybe considered application instruction. Safer to remove it. The instruction: remove duplicated lines, and application instructions. So we should remove "Join our team and build your future with Beck." as it's likely an application instruction. So we will not include it.
Now produce HTML fragment.
Let's craft.
First, About the role section:
About the role
We're The Beck Group, the largest and most innovative integrated building firm in the country. We are focused on delivering design and construction excellence on a broad range of project types. Headquartered in downtown Dallas, with offices in Atlanta, Austin, Charlotte, Denver, Fort Lauderdale, Fort Worth, Mexico City, and Tampa, we believe a better process and outcome results from working together. At Beck, you will find yourself surrounded by passionate colleagues who have a collaborative mindset and care about each other. We are committed to hiring the best and brightest within our industry, and that's why we are seeking experienced professionals like you to help transform the industry and continue building Beck's respected reputation.
The Digital Asset Assistant is a part-time position supporting the Marketing team with the organization and maintenance of Beck’s project photography, renderings and other digital assets. This role is well suited for a college student interested in gaining professional experience in marketing, architecture, construction, photography, communications or digital content management. The position will provide hands-on experience working with project imagery and digital asset management while helping ensure Beck’s visual resources are organized, complete and easily accessible. The Digital Asset Assistant will work under the direction of the Marketing team to gather, organize, tag and upload assets into OpenAsset, as well as assist with identifying gaps and improving existing project records.
What One Will Gain Experience In Digital asset managementMarketing operationsProject photography and visual contentFile organization and metadata managementProfessional marketing systems and workflowsArchitecture and construction industry marketing
Physical Demands: Frequently required to sit, stand, and move about the office; frequently