Technician, Power Delivery
Cobb, Fendley & Associates, Inc. · San Antonio, TX · 1 mo ago
ManagementFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We must parse the job posting.
First, there is a description about company, but not necessarily a section heading. We need to decide which sections to include.
We need to extract:
- About the role: maybe the description paragraph about CobbFendley and the role? The posting includes: "Since 1980, CobbFendley has been committed..." then "Are You Ready To Join Our Block And Advance Your Career?" then "At CobbFendley, People Are Our Most Valued Resource." Then bullet list of benefits etc. Then "CobbFendley is seeking an experienced Power Delivery Technician in our San Antonio, Texas office." That's about the role.
Thus we can put an
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We must parse the job posting.
First, there is a description about company, but not necessarily a section heading. We need to decide which sections to include.
We need to extract:
- About the role: maybe the description paragraph about CobbFendley and the role? The posting includes: "Since 1980, CobbFendley has been committed..." then "Are You Ready To Join Our Block And Advance Your Career?" then "At CobbFendley, People Are Our Most Valued Resource." Then bullet list of benefits etc. Then "CobbFendley is seeking an experienced Power Delivery Technician in our San Antonio, Texas office." That's about the role.
Thus we can put an About the role with paragraphs summarizing that.
- Responsibilities: there is a big block under "Responsibilities" with subheadings: Plan Production, Compliance + Quality, Communication + Collaboration, Training, Learning + Advancement, Client + Internal Satisfaction, Technical, etc. We need to output a - list of duties. Should we preserve subheadings? The instruction: Use
- for any list of duties/requirements/benefits. So we can flatten into list items, preserving content. Probably each bullet is a duty. Could group but okay.
- Requirements: there is a section "Requirements EXPERIENCE + KNOWLEDGE SKILLS ABILITY (KSA)" with subpoints: Emerging // Basic understanding..., Knowledge of standard drafting techniques..., Skills in using industry-standard engineering..., Ability to use spreadsheets... So we can list those as requirements.
- Qualifications: Not explicitly separate; maybe same as requirements? The posting doesn't have a separate Qualifications heading. So we should not create Qualifications section if no specific content.
- Skills: Could be extracted from responsibilities or requirements? There's a "Skills" maybe not separate. The posting includes "Skills in using industry-standard engineering and drafting software". That's under Requirements. So we could have a Skills section if we want, but we should only include if posting has real specific content for it. It does have skills content. However we already have Requirements covering knowledge, skills, ability. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into Requirements and Responsibilities only, plus Benefits, Pay, Schedule.
- Benefits: There's a block "Compensation + Benefits // Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-Term and Long-Term Disability Insurance; Employer Funded and Voluntary Life Insurance; Tuition Reimbursement; and Continuing Education Programs Paid Parental Leave // FMLA-eligible employees will receive fully paid leave in the amounts of eight (8) weeks for maternity cases and two (2) weeks for paternity or adoptions cases Winter Holiday // Extended office closure from December 25 through January 1 to relax and enjoy the holidays Community Engagement // CobbFendley Cares focuses on STEM Education, Hunger Relief, and Sustainable Solutions". So we have benefits details.
- Pay: Not explicitly stated; only "Competitive compensation package". No specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have content. Pay: we have only "Competitive compensation package" but no specific numbers. That's vague; is that considered stating pay? It says "Competitive compensation package". That's not a specific number or range. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive compensation package" is similar to vague. Likely we should not create Pay section because it's not specific.
- Schedule: There's "EXPECTED WORK HOURS This is a full-time position, generally 40 hours per week, however, hours may fluctuate depending on department needs including the use of overtime. CobbFendley’s standard operating hours are Monday through Friday, 7:30 AM to 4:30 PM CST. Generally, employees receive a 1-hour unpaid lunch break free of duty. Please note, operating hours and lunch hours may differ based on project workload, primarily for field staff." Also "WORK LOCATION FLEXIBILTY This position is eligible for a hybrid schedule once the training period is complete as established by the department." So we have schedule info. That's specific enough (hours, days). So we can include Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
We should not include Qualifications, Skills, Pay.
Now we need to output HTML fragment: use
for each section heading. Use
for prose. Use
- for lists.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the details from each section.
Let's extract About the role prose:
From description: "Since 1980, CobbFendley has been committed to providing innovative engineering and surveying solutions with the goal of bettering communities. Our multi-discipline approach allows for the efficient completion of projects through experienced staff who focus on client communication. We are always seeking talented and qualified professionals to enhance our ability to provide clients with exceptional service. Are You Ready To Join Our Block And Advance Your Career? At CobbFendley, People Are Our Most Valued Resource. We Offer A(n) New Hire Program // We understand changing jobs can be intimidating, CobbFendley has established a program geared specifically to the successful onboarding and integration of new hires into the firm Development Opportunities // Professional and personal growth through innovative in-house training and collaborative resources Compensation + Benefits // Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-Term and Long-Term Disability Insurance; Employer Funded and Voluntary Life Insurance; Tuition Reimbursement; and Continuing Education Programs Paid Parental Leave // FMLA-eligible employees will receive fully paid leave in the amounts of eight (8) weeks for maternity cases and two (2) weeks for paternity or adoptions cases Winter Holiday // Extended office closure from December 25 through January 1 to relax and enjoy the holidays Community Engagement // CobbFendley Cares focuses on STEM Education, Hunger Relief, and Sustainable Solutions CobbFendley is seeking an experienced Power Delivery Technician in our San Antonio, Texas office."
But note that the benefits part is duplicated later; we will move benefits to its own section. So for About the role we should include the company overview and the role seeking statement, but not the benefits list (since that will be in Benefits). However we need to preserve all substantive information; we can't duplicate. So we can include the company overview and the statement about seeking an experienced Power Delivery Technician in San Antonio, Texas office. Also maybe the "New Hire Program" and "Development Opportunities" are part of benefits? They are more like benefits/opportunities. Could be considered benefits. But they appear under "We Offer A(n) New Hire Program // ... Development Opportunities // ..." That's part of the benefits/offers. So we could move those to Benefits section as well. However the instruction: Benefits section only if posting actually states them. It does state New Hire Program and Development Opportunities. So we should include them in Benefits.
Thus About the role prose: "Since 1980, CobbFendley has been committed to providing innovative engineering and surveying solutions with the goal of bettering communities. Our multi-discipline approach allows for the efficient completion of projects through experienced staff who focus on client communication. We are always seeking talented and qualified professionals to enhance our ability to provide clients with exceptional service. Are You Ready To Join Our Block And Advance Your Career? At CobbFendley, People Are Our Most Valued Resource. CobbFendley is seeking an experienced Power Delivery Technician in our San Antonio, Texas office."
We could also include "We Offer A(n) New Hire Program // ..." but that's benefits.
Now Responsibilities: we need to extract list items.
Responsibilities block:
Plan Production // Support Project Managers, Project Engineers and Designers with technical design tasks for various projects.
Utilize engineering and drafting software to complete assignments, such as generating plan and profile drawings to include cross-sections, underground utilities, etc. from survey files and/or record drawings.
Develop rough sketches, drawings, specifications, and other data received into final construction drawings.
Complete simple redline markups and incorporate review comments with guidance.
Interpret survey notes, utility records, and civil plans to create accurate base drawings.
Perform basic calculations, including elevations, grades, utility dimensions, and material quantities.
Support collection of field data or utility record information when required.
Compliance + Quality // Observe and follow QA/QC processes under supervision.
Perform self-checks on drawings and data for accuracy, completeness and consistency.
Maintain organized project files, records, and documentation for team access.
Comply with company standards and safety requirements.
Communication + Collaboration // Work with supervisor, project managers, mentors, and various internal personnel to complete assignments.
Training, Learning + Advancement // Develop skills in interpreting survey data, utility records, and engineering plans.
Client + Internal Satisfaction // Work with internal clients daily and escalate concerns when needed.
Support internal project teams by delivering assigned work accurately and on schedule.
Technical // Apply the client’s standards, guidelines, specifications, practices, and procedures and/or appropriate industry standards in preparing layouts of overhead and/or underground electric distribution facilities.
Prepare manual or computer assisted design and construction drawings of a complex nature, cost estimates and bill of materials and any other required documents and reports for construction and maintenance projects.
Assist in the performance of load studies on distribution circuits and transformers; investigate circuit reliability and voltage issues to determine necessary corrective action.
Prepare and submit required reports and correspondence.
Utilize client and Company information systems to track and update design activities.
Acquire field data necessary to prepare the appropriate design.
Ability to handle contacts with clients and other agencies in connection with project design responsibilities.
Field verification of equipment and marking/staking new facilities.
Other job-related duties as assigned.
Independent research and adapt to changing priorities.
Work in a collaborative team environment and deliver accurate work product.
Adhere to CobbFendley’s safety standards to uphold a safe and efficient environment.
Maintain a professional attitude and fulfill responsibilities with integrity.
We need to turn each sentence into
- . Some sentences are long; we can keep them as is.
We should not include the section headings like "Plan Production //" as separate headings; just treat as part of the duty.
Thus we will create a
with many - items.
Now Requirements: block:
EXPERIENCE + KNOWLEDGE SKILLS ABILITY (KSA) Emerging // Basic understanding and minimal practical experience; requires guidance and supervision. No experience is required.
Knowledge of standard drafting techniques, technical standards, and established procedures used to support the design, construction, and maintenance of infrastructure projects.
Skills in using industry-standard engineering and drafting software (e.g., AutoCAD, Civil 3D, MicroStation, OpenRoads Designer, ArcGIS, Microsoft Office, etc.) to prepare technical drawings, document work, and communicate project information effectively.
Ability to use spreadsheets, word processing, and standard office software to compile data, support technical documentation, and assist with reporting and recordkeeping.
We need to output as list items.
Now Benefits: we need to capture all benefits mentioned:
From "Compensation + Benefits // Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-T
- list of duties. Should we preserve subheadings? The instruction: Use
- for any list of duties/requirements/benefits. So we can flatten into list items, preserving content. Probably each bullet is a duty. Could group but okay.
- Requirements: there is a section "Requirements EXPERIENCE + KNOWLEDGE SKILLS ABILITY (KSA)" with subpoints: Emerging // Basic understanding..., Knowledge of standard drafting techniques..., Skills in using industry-standard engineering..., Ability to use spreadsheets... So we can list those as requirements.
- Qualifications: Not explicitly separate; maybe same as requirements? The posting doesn't have a separate Qualifications heading. So we should not create Qualifications section if no specific content.
- Skills: Could be extracted from responsibilities or requirements? There's a "Skills" maybe not separate. The posting includes "Skills in using industry-standard engineering and drafting software". That's under Requirements. So we could have a Skills section if we want, but we should only include if posting has real specific content for it. It does have skills content. However we already have Requirements covering knowledge, skills, ability. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into Requirements and Responsibilities only, plus Benefits, Pay, Schedule.
- Benefits: There's a block "Compensation + Benefits // Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-Term and Long-Term Disability Insurance; Employer Funded and Voluntary Life Insurance; Tuition Reimbursement; and Continuing Education Programs Paid Parental Leave // FMLA-eligible employees will receive fully paid leave in the amounts of eight (8) weeks for maternity cases and two (2) weeks for paternity or adoptions cases Winter Holiday // Extended office closure from December 25 through January 1 to relax and enjoy the holidays Community Engagement // CobbFendley Cares focuses on STEM Education, Hunger Relief, and Sustainable Solutions". So we have benefits details.
- Pay: Not explicitly stated; only "Competitive compensation package". No specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have content. Pay: we have only "Competitive compensation package" but no specific numbers. That's vague; is that considered stating pay? It says "Competitive compensation package". That's not a specific number or range. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive compensation package" is similar to vague. Likely we should not create Pay section because it's not specific.
- Schedule: There's "EXPECTED WORK HOURS This is a full-time position, generally 40 hours per week, however, hours may fluctuate depending on department needs including the use of overtime. CobbFendley’s standard operating hours are Monday through Friday, 7:30 AM to 4:30 PM CST. Generally, employees receive a 1-hour unpaid lunch break free of duty. Please note, operating hours and lunch hours may differ based on project workload, primarily for field staff." Also "WORK LOCATION FLEXIBILTY This position is eligible for a hybrid schedule once the training period is complete as established by the department." So we have schedule info. That's specific enough (hours, days). So we can include Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
We should not include Qualifications, Skills, Pay.
Now we need to output HTML fragment: use
for each section heading. Use
for prose. Use
- for lists. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the details from each section. Let's extract About the role prose: From description: "Since 1980, CobbFendley has been committed to providing innovative engineering and surveying solutions with the goal of bettering communities. Our multi-discipline approach allows for the efficient completion of projects through experienced staff who focus on client communication. We are always seeking talented and qualified professionals to enhance our ability to provide clients with exceptional service. Are You Ready To Join Our Block And Advance Your Career? At CobbFendley, People Are Our Most Valued Resource. We Offer A(n) New Hire Program // We understand changing jobs can be intimidating, CobbFendley has established a program geared specifically to the successful onboarding and integration of new hires into the firm Development Opportunities // Professional and personal growth through innovative in-house training and collaborative resources Compensation + Benefits // Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-Term and Long-Term Disability Insurance; Employer Funded and Voluntary Life Insurance; Tuition Reimbursement; and Continuing Education Programs Paid Parental Leave // FMLA-eligible employees will receive fully paid leave in the amounts of eight (8) weeks for maternity cases and two (2) weeks for paternity or adoptions cases Winter Holiday // Extended office closure from December 25 through January 1 to relax and enjoy the holidays Community Engagement // CobbFendley Cares focuses on STEM Education, Hunger Relief, and Sustainable Solutions CobbFendley is seeking an experienced Power Delivery Technician in our San Antonio, Texas office." But note that the benefits part is duplicated later; we will move benefits to its own section. So for About the role we should include the company overview and the role seeking statement, but not the benefits list (since that will be in Benefits). However we need to preserve all substantive information; we can't duplicate. So we can include the company overview and the statement about seeking an experienced Power Delivery Technician in San Antonio, Texas office. Also maybe the "New Hire Program" and "Development Opportunities" are part of benefits? They are more like benefits/opportunities. Could be considered benefits. But they appear under "We Offer A(n) New Hire Program // ... Development Opportunities // ..." That's part of the benefits/offers. So we could move those to Benefits section as well. However the instruction: Benefits section only if posting actually states them. It does state New Hire Program and Development Opportunities. So we should include them in Benefits. Thus About the role prose: "Since 1980, CobbFendley has been committed to providing innovative engineering and surveying solutions with the goal of bettering communities. Our multi-discipline approach allows for the efficient completion of projects through experienced staff who focus on client communication. We are always seeking talented and qualified professionals to enhance our ability to provide clients with exceptional service. Are You Ready To Join Our Block And Advance Your Career? At CobbFendley, People Are Our Most Valued Resource. CobbFendley is seeking an experienced Power Delivery Technician in our San Antonio, Texas office." We could also include "We Offer A(n) New Hire Program // ..." but that's benefits. Now Responsibilities: we need to extract list items. Responsibilities block: Plan Production // Support Project Managers, Project Engineers and Designers with technical design tasks for various projects. Utilize engineering and drafting software to complete assignments, such as generating plan and profile drawings to include cross-sections, underground utilities, etc. from survey files and/or record drawings. Develop rough sketches, drawings, specifications, and other data received into final construction drawings. Complete simple redline markups and incorporate review comments with guidance. Interpret survey notes, utility records, and civil plans to create accurate base drawings. Perform basic calculations, including elevations, grades, utility dimensions, and material quantities. Support collection of field data or utility record information when required. Compliance + Quality // Observe and follow QA/QC processes under supervision. Perform self-checks on drawings and data for accuracy, completeness and consistency. Maintain organized project files, records, and documentation for team access. Comply with company standards and safety requirements. Communication + Collaboration // Work with supervisor, project managers, mentors, and various internal personnel to complete assignments. Training, Learning + Advancement // Develop skills in interpreting survey data, utility records, and engineering plans. Client + Internal Satisfaction // Work with internal clients daily and escalate concerns when needed. Support internal project teams by delivering assigned work accurately and on schedule. Technical // Apply the client’s standards, guidelines, specifications, practices, and procedures and/or appropriate industry standards in preparing layouts of overhead and/or underground electric distribution facilities. Prepare manual or computer assisted design and construction drawings of a complex nature, cost estimates and bill of materials and any other required documents and reports for construction and maintenance projects. Assist in the performance of load studies on distribution circuits and transformers; investigate circuit reliability and voltage issues to determine necessary corrective action. Prepare and submit required reports and correspondence. Utilize client and Company information systems to track and update design activities. Acquire field data necessary to prepare the appropriate design. Ability to handle contacts with clients and other agencies in connection with project design responsibilities. Field verification of equipment and marking/staking new facilities. Other job-related duties as assigned. Independent research and adapt to changing priorities. Work in a collaborative team environment and deliver accurate work product. Adhere to CobbFendley’s safety standards to uphold a safe and efficient environment. Maintain a professional attitude and fulfill responsibilities with integrity. We need to turn each sentence into
- . Some sentences are long; we can keep them as is.
We should not include the section headings like "Plan Production //" as separate headings; just treat as part of the duty.
Thus we will create a
- with many
- items. Now Requirements: block: EXPERIENCE + KNOWLEDGE SKILLS ABILITY (KSA) Emerging // Basic understanding and minimal practical experience; requires guidance and supervision. No experience is required. Knowledge of standard drafting techniques, technical standards, and established procedures used to support the design, construction, and maintenance of infrastructure projects. Skills in using industry-standard engineering and drafting software (e.g., AutoCAD, Civil 3D, MicroStation, OpenRoads Designer, ArcGIS, Microsoft Office, etc.) to prepare technical drawings, document work, and communicate project information effectively. Ability to use spreadsheets, word processing, and standard office software to compile data, support technical documentation, and assist with reporting and recordkeeping. We need to output as list items. Now Benefits: we need to capture all benefits mentioned: From "Compensation + Benefits // Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-T
- for any list of duties/requirements/benefits. So we can flatten into list items, preserving content. Probably each bullet is a duty. Could group but okay.
- Requirements: there is a section "Requirements EXPERIENCE + KNOWLEDGE SKILLS ABILITY (KSA)" with subpoints: Emerging // Basic understanding..., Knowledge of standard drafting techniques..., Skills in using industry-standard engineering..., Ability to use spreadsheets... So we can list those as requirements.
- Qualifications: Not explicitly separate; maybe same as requirements? The posting doesn't have a separate Qualifications heading. So we should not create Qualifications section if no specific content.
- Skills: Could be extracted from responsibilities or requirements? There's a "Skills" maybe not separate. The posting includes "Skills in using industry-standard engineering and drafting software". That's under Requirements. So we could have a Skills section if we want, but we should only include if posting has real specific content for it. It does have skills content. However we already have Requirements covering knowledge, skills, ability. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into Requirements and Responsibilities only, plus Benefits, Pay, Schedule.
- Benefits: There's a block "Compensation + Benefits // Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-Term and Long-Term Disability Insurance; Employer Funded and Voluntary Life Insurance; Tuition Reimbursement; and Continuing Education Programs Paid Parental Leave // FMLA-eligible employees will receive fully paid leave in the amounts of eight (8) weeks for maternity cases and two (2) weeks for paternity or adoptions cases Winter Holiday // Extended office closure from December 25 through January 1 to relax and enjoy the holidays Community Engagement // CobbFendley Cares focuses on STEM Education, Hunger Relief, and Sustainable Solutions". So we have benefits details.
- Pay: Not explicitly stated; only "Competitive compensation package". No specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have content. Pay: we have only "Competitive compensation package" but no specific numbers. That's vague; is that considered stating pay? It says "Competitive compensation package". That's not a specific number or range. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive compensation package" is similar to vague. Likely we should not create Pay section because it's not specific.
- Schedule: There's "EXPECTED WORK HOURS This is a full-time position, generally 40 hours per week, however, hours may fluctuate depending on department needs including the use of overtime. CobbFendley’s standard operating hours are Monday through Friday, 7:30 AM to 4:30 PM CST. Generally, employees receive a 1-hour unpaid lunch break free of duty. Please note, operating hours and lunch hours may differ based on project workload, primarily for field staff." Also "WORK LOCATION FLEXIBILTY This position is eligible for a hybrid schedule once the training period is complete as established by the department." So we have schedule info. That's specific enough (hours, days). So we can include Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
We should not include Qualifications, Skills, Pay.
Now we need to output HTML fragment: use