Associate Project Manager Closure RMA and Warranty
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. 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. We need to decide which sections to include: The posting includes "What We Do At Terabase Energy" (company description). Could be "About the role"? Actually "About the role" is a heading suggestion. But we have "The Role" section describing the role. Could map to "About the role". Also we have "Responsibilities" (with subpoints). Also "Requirements" and "Qualifications". The posting has "Requirements Qualifications" combined? Actually after responsibilities, there is a line "Requirements Qualifications" then bullet list of qualifications. Then "Preferred Qualifications". Then "Benefits Compensation And Benefits". So we have Benefits section. Pay? Not specific numbers, just statement about salary ranges determined by role, level, location. That is somewhat generic but still mentions compensation. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation and benefits, so we can include Benefits section. Pay? It mentions salary ranges but not specific numbers; still it's about compensation. Should we include a Pay section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation, but not explicit pay numbers. However "Compensation And Benefits" heading is present. So we could include a Benefits section (maybe combine compensation and benefits). The instruction says prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly also Preferred Qualifications could be merged into Qualifications? But we should preserve all substantive information; we could keep Qualifications (required) and Preferred Qualifications as subpoints under Qualifications? But we need to use
- for any list of duties/requirements/benefits. So we can have separate sections for Requirements and Qualifications (maybe combined). The posting lumps "Requirements Qualifications" then bullet list. Then "Preferred Qualifications" separate bullet list. We could have a section "Requirements" with required qualifications, and another section "Preferred Qualifications". That seems fine.
We need to strip boilerplate: EEO statement, agency candidate note, contact recruiting team, etc. Also remove duplicated lines. Also remove "What We Do At Terabase Energy" maybe we can incorporate into About the role? Actually "About the role" heading is for role description, not company overview. But we could include a short paragraph about the company under About the role? The instruction: 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. The "What We Do At Terabase Energy" is company overview, not role. Could be considered "About the role"? Not exactly. But we could treat it as a brief intro before responsibilities. Since we need to preserve all substantive information, we should include it somewhere. Perhaps as a
before the first heading. The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having a paragraph before headings. So we can start with a
containing the company description. Then
About the role
with the role description paragraph (the "The Role" paragraph). ThenResponsibilities
with- for each bullet under Responsibilities (the many bullet points). Then
Requirements
with- for required qualifications. Then
Preferred Qualifications
with- for preferred qualifications. Then
Benefits
with- for benefits list.
We must not include Pay or Schedule sections because not explicitly stated (though compensation mentioned under Benefits). The Benefits section includes compensation and benefits; we can include that.
We need to remove boilerplate: EEO statement, agency candidate note, contact recruiting team, "Principles only." etc. Also remove duplicated lines (maybe none). Also remove "Terabase is an equal opportunity employer..." etc.
We need to preserve all substantive information: company description, role description, responsibilities bullet points, required qualifications bullet points, preferred qualifications bullet points, benefits bullet points.
We need to ensure we don't invent or summarize away detail. Keep the exact phrasing? We should preserve substance but can we trim minor words? Probably keep as is but ensure no extra fluff.
Let's extract sections.
Company description:
"What We Do At Terabase Energy, we believe digitalization and automation will drive the next wave of innovation and cost reduction in utility-scale solar. Terabase is developing an interconnected software and construction automation platform supporting the design, optimization, construction, and operation of large solar projects around the world. Our team includes solar-industry veterans and newcomers, engineers, software developers, product managers, project managers, and commercial professionals. We are headquartered in Northern California, with offices and employees across the United States and around the world."
That's one paragraph.
Role description (The Role):
"Terabase's SCADA solutions enable accurate data acquisition and effective management of utility-scale solar power plants. We are seeking an Associate Project Manager to support the Closure, RMA and Warranty services function within our Project Delivery team. Reporting to the Director of Project Delivery, you will coordinate project closeout documentation, action tracking, RMA and warranty cases, spares records, customer and vendor follow-up, and routine reporting for deployed SCADA and controls projects. The ideal candidate is organized, responsive, and detail-oriented, with the discipline to keep records current and follow actions through completion. Success in this role requires clear communication, strong coordination skills, comfort working across several concurrent projects, and an interest in developing technical knowledge of SCADA and industrial controls. This position is based in Berkeley, California, but the right candidate may be able to work remotely from another location."
That's a paragraph.
Responsibilities: There's a heading "Responsibilities" then subheadings: Project Closure, Closure Coordination, Documentation Management, Action Tracking, Stakeholder Support, System and Data Administration, Transition Support, Closure Reporting, Compliance and Records, RMA and Warranty Case Coordination, Process and Policy Administration, Customer and Vendor Follow-up, Spares Support, Financial Data Support, Quality Coordination, Product Feedback Support, Data and Reporting, Risk and Escalation Support. Under each subheading there are bullet points (starting with a bold phrase). We need to flatten into a list of duties. The instruction: Use
- for any list of duties/requirements/benefits. So we can create a single
- with each duty as
- . We need to preserve all substantive information; we can combine the subheading text with the bullet. For example: "Project Closure Closure Coordination: Maintain project closure plans, action logs, milestone dates, dependencies, and acceptance requirements under the direction of the Project Manager". Actually the bullet under Project Closure includes multiple sub-bullets? Let's parse: Under Responsibilities: Project Closure - Closure Coordination: Maintain project closure plans, action logs, milestone dates, dependencies, and acceptance requirements under the direction of the Project Manager - Documentation Management: Collect, organize, and quality-check closeout documents, including final reports, as-built deliverables, acceptance records, manuals, and lessons learned - Action Tracking: Track outstanding technical, commercial, and documentation items; follow up with assigned owners and escalate overdue or blocked actions - Stakeholder Support: Prepare meeting notes, status updates, customer correspondence, and internal follow-ups for review by the Project Manager - System and Data Administration: Keep project, ERP, inventory, and document-management records accurate and current, including dates, status, ownership, and supporting files - Transition Support: Coordinate knowledge-transfer meetings and support the handoff of open service items, equipment, and records to their post-project owners - Closure Reporting: Prepare routine closure dashboards and reports summarizing progress, open items, risks, and documentation status - Compliance and Records: Follow approved closure procedures and maintain complete, traceable records for customer commitments, internal reviews, and audits RMA and Warranty Case Coordination: - Log RMA and warranty requests, validate required information, coordinate assignments, track aging and due dates, and maintain complete case records - Process and Policy Administration: Apply approved RMA and warranty processes and policies, document exceptions, and recommend practical refinements based on recurring workflow issues - Customer and Vendor Follow-up: Coordinate routine communication with customers, vendors, suppliers, and service providers regarding status, shipment, repair, replacement, credit, and documentation - Spares Support: Maintain spares demand, inventory, rotation, replenishment, shipment, and consumption records and coordinate follow-up with Supply Chain and Operations - Financial Data Support: Collect and validate purchase orders, invoices, credits, freight, labor, and material costs to support warranty and spares budgets, forecasts, reserves, and cost allocations - Quality Coordination: Gather evidence for failure reviews and audits and coordinate follow-up actions with the Quality, Product, and Engineering teams - Product Feedback Support: Compile common failures, reliability issues, field data, and operator feedback and route the information to the Project Manager and responsible Product, Quality, and Engineering owners - Data and Reporting: Maintain dashboards and prepare routine metrics on case aging, turnaround time, resolution rate, costs, inventory status, recurring issues, and customer outcomes - Risk and Escalation Support: Identify missing information, overdue actions, cost concerns, and customer-impacting risks and escalate them promptly to the Project Manager Thus each bullet is a duty. We'll create
- for each. Requirements: The bullet list after "Requirements Qualifications": - Bachelor's degree in project management, business administration, engineering, supply chain, or a related field, or equivalent relevant experience - One to three years of experience in project coordination, project management, customer support, operations, warranty, procurement, or a related function - Strong organization and follow-through, with the ability to manage multiple action lists, records, deadlines, and priorities - Clear written and verbal communication skills and the ability to work effectively with customers and cross-functional teams - Proficiency with Microsoft Office and familiarity with project-management, ERP, inventory, reporting, or document-management tools - Ability to review data and documents for accuracy, identify missing information, and escalate issues promptly - Willingness to learn technical concepts related to SCADA, industrial controls, electrical systems, and utility-scale solar projects Preferred Qualifications bullet list: - Experience supporting SCADA, industrial controls, renewable-energy, construction, or electrical projects - Experience with RMA, warranty, field service, procurement, inventory, logistics, or project closeout activities - Familiarity with customer issue tracking, reporting dashboards, document control, or enterprise resource planning systems - CAPM certification or active pursuit of a project-management certification Benefits: Under "Benefits Compensation And Benefits" paragraph: "Terabase offers competitive compensation along with a comprehensive benefits package including: Generous time off and holiday policy Remote
- for any list of duties/requirements/benefits. So we can create a single
- for benefits list.
We must not include Pay or Schedule sections because not explicitly stated (though compensation mentioned under Benefits). The Benefits section includes compensation and benefits; we can include that.
We need to remove boilerplate: EEO statement, agency candidate note, contact recruiting team, "Principles only." etc. Also remove duplicated lines (maybe none). Also remove "Terabase is an equal opportunity employer..." etc.
We need to preserve all substantive information: company description, role description, responsibilities bullet points, required qualifications bullet points, preferred qualifications bullet points, benefits bullet points.
We need to ensure we don't invent or summarize away detail. Keep the exact phrasing? We should preserve substance but can we trim minor words? Probably keep as is but ensure no extra fluff.
Let's extract sections.
Company description:
"What We Do At Terabase Energy, we believe digitalization and automation will drive the next wave of innovation and cost reduction in utility-scale solar. Terabase is developing an interconnected software and construction automation platform supporting the design, optimization, construction, and operation of large solar projects around the world. Our team includes solar-industry veterans and newcomers, engineers, software developers, product managers, project managers, and commercial professionals. We are headquartered in Northern California, with offices and employees across the United States and around the world."
That's one paragraph.
Role description (The Role):
"Terabase's SCADA solutions enable accurate data acquisition and effective management of utility-scale solar power plants. We are seeking an Associate Project Manager to support the Closure, RMA and Warranty services function within our Project Delivery team. Reporting to the Director of Project Delivery, you will coordinate project closeout documentation, action tracking, RMA and warranty cases, spares records, customer and vendor follow-up, and routine reporting for deployed SCADA and controls projects. The ideal candidate is organized, responsive, and detail-oriented, with the discipline to keep records current and follow actions through completion. Success in this role requires clear communication, strong coordination skills, comfort working across several concurrent projects, and an interest in developing technical knowledge of SCADA and industrial controls. This position is based in Berkeley, California, but the right candidate may be able to work remotely from another location."
That's a paragraph.
Responsibilities: There's a heading "Responsibilities" then subheadings: Project Closure, Closure Coordination, Documentation Management, Action Tracking, Stakeholder Support, System and Data Administration, Transition Support, Closure Reporting, Compliance and Records, RMA and Warranty Case Coordination, Process and Policy Administration, Customer and Vendor Follow-up, Spares Support, Financial Data Support, Quality Coordination, Product Feedback Support, Data and Reporting, Risk and Escalation Support. Under each subheading there are bullet points (starting with a bold phrase). We need to flatten into a list of duties. The instruction: Use
- for preferred qualifications. Then
- for required qualifications. Then
- for each bullet under Responsibilities (the many bullet points). Then