Designer, Lighting
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 (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
- About Us: paragraph about AlfaTech culture, etc.
- Job Summary: description of role.
- Core Responsibilities: list of bullet points (starting with "Partner with senior designers..." etc.)
- Ideal Candidate: list of bullet points (minimum 3 years experience, Bachelor's degree, proficiency in software, etc.)
- Essential Requirements: bullet points (Experience with sustainable and energy-efficient lighting practices; Experience using Revit and AGi32 required.)
- Salary Range: paragraph about hybrid role, office location, salary range $38.46 - $40.85/Hour, final offer dependent on factors, ATCE multi-state employer note.
We need to decide sections: About Us could be "About the role"? Actually "About Us" is about company. The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can adapt: maybe "About the role" for Job Summary? Or "About Us" could be considered "About the role"? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to these headings where appropriate.
We have:
- About Us: could be "About the role"? Actually "About the role" is more like job summary. But we have both About Us and Job Summary. Could combine? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid having an About Us heading. But they gave examples of headings; we can use those or similar. Probably we should use headings that match content: "About the company" maybe not in list but okay. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings if applicable; but we can also use other headings if needed? The examples are just examples; we can use those headings. Likely they expect us to use those headings for sections we have.
Thus we could have:
- About the role
containing Job Summary (maybe also About Us? but About Us is about company, not role). Could also have About AlfaTech
but not in list. Might be okay but they said "e.g." not exclusive. Safer to include About Us as a heading maybe "About AlfaTech". But they said include a section ONLY when posting has real, specific content for it. About Us has content, so we should include it. Use About AlfaTech
.
- Responsibilities: list of core responsibilities.
- Requirements: could combine Ideal Candidate and Essential Requirements? Or separate Qualifications and Skills? The instruction includes Requirements, Qualifications, Skills. We have Ideal Candidate (experience, education, skills, traits) and Essential Requirements (specific software, sustainability). We could map:
- Qualifications: education and experience (Bachelor's degree, 3 years experience).
- Skills: software proficiency, collaboration, visual awareness, communication, etc.
- Requirements: maybe essential requirements (sustainable lighting practices, Revit and AGi32 required). Or we could combine.
We need to avoid thin sections; prefer few substantive sections. Could combine into one "Requirements" section that includes all bullet points from Ideal Candidate and Essential Requirements. But we need to preserve all info; we can list them as bullet points under one section.
Alternatively we could have two sections: "Qualifications" and "Skills". But that may be thin. However we have enough content for each.
Let's decide:
- About AlfaTech
with paragraph from About Us.
- Job Summary
with paragraph from Job Summary.
- Responsibilities
with ul list of core responsibilities.
- Qualifications
with ul list: Minimum of 3 years experience, Bachelor's degree in Lighting Design, Architecture, Interior Design, Electrical or related field.
- Skills
with ul list: Proficiency in lighting design software such as AGi32, Autodesk Revit, Rhinoceros, ALFA, Bluebeam, Photoshop, Climate Studio, Grasshopper, Bluebeam, Photoshop, and InDesign. (Note duplicate Bluebeam, Photoshop; we should preserve as given but could deduplicate? Instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines? They said remove duplicated lines. So we should deduplicate repeated items. So we list each unique software once.
Also: Familiarity with project management tools: InDesign, Excel.
- Strong collaborator.
- Excellent visual and spatial awareness.
- Strong communication and interpersonal skills.
- Eagerness to learn and adapt to new technologies and design trends.
- Familiarity with building codes, regulations related to lighting design, and basic knowledge of electrical systems.
- Requirements
with ul list: Experience with sustainable and energy-efficient lighting practices. Experience using Revit and AGi32 required.
- Pay
with paragraph: Salary range $38.46 - $40.85/Hour, hybrid role, expected office days in Monrovia, CA, final offer dependent on factors, ATCE multi-state employer note.
We should not include Schedule unless specified; not present.
We should not include Benefits unless specified; not present.
We need to remove boilerplate: "Other reasonable tasks as assigned. This is meant to summarize the role’s responsibilities and provide some information and structure. At AlfaTech we encourage our staff to think outside the box and explore opportunities beyond the confines of one’s stated responsibilities to bring new thoughts, ideas, and innovations to our company." This is part of Responsibilities? It's a generic statement; maybe we should keep as it's substantive? It's somewhat boilerplate but it's part of the posting. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those; it's about responsibilities. Might keep.
But we can incorporate into responsibilities as a bullet? It's a sentence summarizing role's responsibilities. Could be a paragraph after list.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep that sentence.
Similarly, "Ideal Candidate" heading is not a standard heading but we can treat as Qualifications/Skills.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now produce HTML fragment.
We'll need to wrap each section in and then content.
For lists: - ...
For prose:
...
We must not include or .
Let's craft.
First, About AlfaTech paragraph:
"At AlfaTech we believe in more than just engineering solutions; we believe in promoting a culture of agility, collaboration, and inclusion. As a leading consulting engineering firm, we provide thoughtful engineering design that is technologically forward thinking, innovative, and environmentally conscious, ensuring that our contribution to our built environment is flexible, sustainable, and lasting across all the market segments we serve."
Second, Job Summary paragraph:
"As a valued member of our Lighting Designer team, you will play a crucial role in proactively considering and planning for engineering aspects in your lighting design, and anticipating the requirements and constraints the engineer will need to address for lighting designs across a wide spectrum of projects, including large commercial spaces, multifamily developments, high-end residential properties, healthcare facilities, hospitality, higher education institutions, as well as museums and galleries."
Third, Responsibilities list:
- Partner with senior designers and principals to develop creative lighting concepts and designs for a range of projects.
- Build detailed lighting plans, layouts, and specifications tailored to project requirements.
- Apply valuable insights by staying updated on advancements in lighting technologies, products, and design trends.
- Illustrate your passion for your role by harnessing both graphic and spoken media to create interest and excitement in your designs through story telling.
- Collaborate with the wider design teams to seamlessly integrate lighting concepts into overall project plans.
- Liaise seamlessly with all disciplines interfacing with the design team such as architecture, interior design, structural, mechanical, electrical, and plumbing requirements.
- Engage with our clients to refine lighting concepts and develop solutions which exceed their expectations.
- Work with the construction and field teams to facilitate the execution of the lighting concepts, thereby ensuring the successful realization of the design.
- Be an active participant of construction site walkthroughs and project team meetings.
- Actively participate in relevant industry events such as product exhibitions, educational seminars, design awards, and other professional gatherings that support continued learning and industry engagement.
- Other reasonable tasks as assigned. This is meant to summarize the role’s responsibilities and provide some information and structure. At AlfaTech we encourage our staff to think outside the box and explore opportunities beyond the confines of one’s stated responsibilities to bring new thoughts, ideas, and innovations to our company.
Note the last bullet includes two sentences; we can keep as one - containing both sentences.
Fourth, Qualifications list:
- Minimum of 3 years of experience in lighting design, with a proven portfolio in diverse project environments.
- Bachelor’s degree in Lighting Design, Architecture, Interior Design, Electrical or a related field.
Fifth, Skills list:
- Proficiency in lighting design software such as AGi32, Autodesk Revit, Rhinoceros, ALFA, Bluebeam, Photoshop, Climate Studio, Grasshopper, InDesign.
- Familiarity with project management tools: InDesign, Excel.
- Strong collaborator.
- Excellent visual and spatial awareness.
- Strong communication and interpersonal skills.
- Eagerness to learn and adapt to new technologies and design trends.
- Familiarity with building codes, regulations related to lighting design, and basic knowledge of electrical systems.
Note: We removed duplicate Bluebeam, Photoshop.
Sixth, Requirements list:
- Experience with sustainable and energy-efficient lighting practices.
- Experience using Revit and AGi32 required.
Seventh, Pay paragraph:
"This is a hybrid role. It is anticipated that the working days in the office will be done at our Monrovia, CA office. The expected salary range for candidates who will work in Monrovia, CA is $38.46 - $40.85/Hour. The final offer to our new team member will be dependent on several factors that may include but are not limited to the length, breadth, and depth of experience within the job and the industry, education, etc. ATCE is a multi-state employer, and this salary range may not reflect positions that work in other states."
We should not include any extra fluff.
Now output HTML.
Check for
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Us: paragraph about AlfaTech culture, etc. - Job Summary: description of role. - Core Responsibilities: list of bullet points (starting with "Partner with senior designers..." etc.) - Ideal Candidate: list of bullet points (minimum 3 years experience, Bachelor's degree, proficiency in software, etc.) - Essential Requirements: bullet points (Experience with sustainable and energy-efficient lighting practices; Experience using Revit and AGi32 required.) - Salary Range: paragraph about hybrid role, office location, salary range $38.46 - $40.85/Hour, final offer dependent on factors, ATCE multi-state employer note. We need to decide sections: About Us could be "About the role"? Actually "About Us" is about company. The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can adapt: maybe "About the role" for Job Summary? Or "About Us" could be considered "About the role"? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to these headings where appropriate. We have: - About Us: could be "About the role"? Actually "About the role" is more like job summary. But we have both About Us and Job Summary. Could combine? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid having an About Us heading. But they gave examples of headings; we can use those or similar. Probably we should use headings that match content: "About the company" maybe not in list but okay. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings if applicable; but we can also use other headings if needed? The examples are just examples; we can use those headings. Likely they expect us to use those headings for sections we have.
Thus we could have:
- About the role
containing Job Summary (maybe also About Us? but About Us is about company, not role). Could also have About AlfaTech
but not in list. Might be okay but they said "e.g." not exclusive. Safer to include About Us as a heading maybe "About AlfaTech". But they said include a section ONLY when posting has real, specific content for it. About Us has content, so we should include it. Use About AlfaTech
.
- Responsibilities: list of core responsibilities.
- Requirements: could combine Ideal Candidate and Essential Requirements? Or separate Qualifications and Skills? The instruction includes Requirements, Qualifications, Skills. We have Ideal Candidate (experience, education, skills, traits) and Essential Requirements (specific software, sustainability). We could map:
- Qualifications: education and experience (Bachelor's degree, 3 years experience).
- Skills: software proficiency, collaboration, visual awareness, communication, etc.
- Requirements: maybe essential requirements (sustainable lighting practices, Revit and AGi32 required). Or we could combine.
We need to avoid thin sections; prefer few substantive sections. Could combine into one "Requirements" section that includes all bullet points from Ideal Candidate and Essential Requirements. But we need to preserve all info; we can list them as bullet points under one section.
Alternatively we could have two sections: "Qualifications" and "Skills". But that may be thin. However we have enough content for each.
Let's decide:
- About AlfaTech
with paragraph from About Us.
- Job Summary
with paragraph from Job Summary.
- Responsibilities
with ul list of core responsibilities.
- Qualifications
with ul list: Minimum of 3 years experience, Bachelor's degree in Lighting Design, Architecture, Interior Design, Electrical or related field.
- Skills
with ul list: Proficiency in lighting design software such as AGi32, Autodesk Revit, Rhinoceros, ALFA, Bluebeam, Photoshop, Climate Studio, Grasshopper, Bluebeam, Photoshop, and InDesign. (Note duplicate Bluebeam, Photoshop; we should preserve as given but could deduplicate? Instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines? They said remove duplicated lines. So we should deduplicate repeated items. So we list each unique software once.
Also: Familiarity with project management tools: InDesign, Excel.
- Strong collaborator.
- Excellent visual and spatial awareness.
- Strong communication and interpersonal skills.
- Eagerness to learn and adapt to new technologies and design trends.
- Familiarity with building codes, regulations related to lighting design, and basic knowledge of electrical systems.
- Requirements
with ul list: Experience with sustainable and energy-efficient lighting practices. Experience using Revit and AGi32 required.
- Pay
with paragraph: Salary range $38.46 - $40.85/Hour, hybrid role, expected office days in Monrovia, CA, final offer dependent on factors, ATCE multi-state employer note.
We should not include Schedule unless specified; not present.
We should not include Benefits unless specified; not present.
We need to remove boilerplate: "Other reasonable tasks as assigned. This is meant to summarize the role’s responsibilities and provide some information and structure. At AlfaTech we encourage our staff to think outside the box and explore opportunities beyond the confines of one’s stated responsibilities to bring new thoughts, ideas, and innovations to our company." This is part of Responsibilities? It's a generic statement; maybe we should keep as it's substantive? It's somewhat boilerplate but it's part of the posting. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those; it's about responsibilities. Might keep.
But we can incorporate into responsibilities as a bullet? It's a sentence summarizing role's responsibilities. Could be a paragraph after list.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep that sentence.
Similarly, "Ideal Candidate" heading is not a standard heading but we can treat as Qualifications/Skills.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now produce HTML fragment.
We'll need to wrap each section in and then content.
For lists: - ...
For prose:
- ...
...
We must not include or . Let's craft. First, About AlfaTech paragraph: "At AlfaTech we believe in more than just engineering solutions; we believe in promoting a culture of agility, collaboration, and inclusion. As a leading consulting engineering firm, we provide thoughtful engineering design that is technologically forward thinking, innovative, and environmentally conscious, ensuring that our contribution to our built environment is flexible, sustainable, and lasting across all the market segments we serve." Second, Job Summary paragraph: "As a valued member of our Lighting Designer team, you will play a crucial role in proactively considering and planning for engineering aspects in your lighting design, and anticipating the requirements and constraints the engineer will need to address for lighting designs across a wide spectrum of projects, including large commercial spaces, multifamily developments, high-end residential properties, healthcare facilities, hospitality, higher education institutions, as well as museums and galleries." Third, Responsibilities list: - Partner with senior designers and principals to develop creative lighting concepts and designs for a range of projects. - Build detailed lighting plans, layouts, and specifications tailored to project requirements. - Apply valuable insights by staying updated on advancements in lighting technologies, products, and design trends. - Illustrate your passion for your role by harnessing both graphic and spoken media to create interest and excitement in your designs through story telling. - Collaborate with the wider design teams to seamlessly integrate lighting concepts into overall project plans. - Liaise seamlessly with all disciplines interfacing with the design team such as architecture, interior design, structural, mechanical, electrical, and plumbing requirements. - Engage with our clients to refine lighting concepts and develop solutions which exceed their expectations. - Work with the construction and field teams to facilitate the execution of the lighting concepts, thereby ensuring the successful realization of the design. - Be an active participant of construction site walkthroughs and project team meetings. - Actively participate in relevant industry events such as product exhibitions, educational seminars, design awards, and other professional gatherings that support continued learning and industry engagement. - Other reasonable tasks as assigned. This is meant to summarize the role’s responsibilities and provide some information and structure. At AlfaTech we encourage our staff to think outside the box and explore opportunities beyond the confines of one’s stated responsibilities to bring new thoughts, ideas, and innovations to our company. Note the last bullet includes two sentences; we can keep as one