Quality Engineer
About the role
withcontent. - Responsibilities: The bullet list under "Accountability & Authorities:" and sub-bullets. Those are responsibilities. We'll create a
- list.
- Requirements: The "Requirements" heading appears later: "Requirements Competencies & Skills". Actually there is a line: "Requirements Competencies & Skills". Then bullet list of competencies and skills. Then "Mandatory:" list. Then "Desirable:" list. So we need to separate Requirements (maybe mandatory) and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have:
- Competencies & Skills (list of soft skills, technical). That could go under Skills.
- Mandatory: Bachelor's degree etc. That's qualifications.
- Desirable: Master's degree etc. Could be additional qualifications or preferred qualifications.
We also have "Performance measurements:" list - maybe could be under Responsibilities? But it's more like metrics; could be part of Responsibilities or maybe a separate section but not required heading. We'll keep as part of Responsibilities maybe.
We have "Benefits Compensation And Benefits" section with bullet list of benefits. So we will have Benefits heading.
Pay: The posting mentions "Our salary ranges are determined by role, level, and location. Within each posted range, individual pay is determined (and may be greater or higher), dependent on work location and additional factors, including job-related skills, experience, and relevant education or training." That's pay info but not specific numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info (salary ranges determined by role etc). That's still pay info, albeit not specific numbers. Should we include Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation info, albeit generic. So we can include a Pay section with that paragraph.
Schedule: No mention of schedule (e.g., full-time, remote flexibility). There's "Remote flexibility" under benefits, but schedule not explicit. So we should not create Schedule section.
We also need to include maybe a short paragraph for metadata like location? The posting mentions headquarters in Northern California, offices across US and world. Could be included in About the role? But we should not invent headings. Could add a
under About the role that includes that info? The About the role section currently has description; we could incorporate location info there if it's present. The posting includes: "We are headquartered in Northern California, with offices and employees across the United States and around the world." That's under "What We Do". That's not about the role but company description. Might be considered boilerplate? It's not navigation/legal; it's substantive about company. Should we keep? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that company description somewhere. Where to put? Could be a preceding paragraph before About the role? But we cannot add arbitrary headings not requested. We could include it as a
before the first heading? The instruction says output ONLY the HTML fragment; we can include
elements not under headings? It didn't forbid. It said use
for section headings,
- for any list,
for prose. So we can have
elements anywhere. So we can include a
with company overview. Thus structure:
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.
ThenAbout the role
with paragraph(s) from "About The Role". That paragraph: "The Quality Engineer ensures quality is built in—not inspected out—across the full lifecycle of mechanical, electrical, and electromechanical products, from new product introduction and incoming material through build, release, and field performance. The Quality Engineer implements and sustains quality engineering controls that ensure Terabase products meet specifications, customer requirements, traceability standards, and ISO 9001 compliance. The Quality Engineer implements and sustains the quality controls, inspection criteria, and procedures defined in the Terabase Quality Management System. Quality coordinates and provides oversight; Engineering, Manufacturing, and Supply Chain own execution of design, process, and supplier actions." We could keep as one. Then Responsibilities: we need to extract bullet points from "Accountability & Authorities:" and subpoints. Let's list them: - Quality Planning & NPI - Provide quality input in design and process reviews (manufacturability, inspectability, CTQs, lessons learned) - Develop and maintain inspection plans, control plans, checklists, and acceptance criteria; execute First Article Inspections (FAI) - Assess quality impact of engineering changes (ECOs in PLM) and verify effective implementation - Incoming & Supplier Quality - Inspect supplier-delivered materials against drawings, specifications, COCs, MTRs, and test certificates; verify part ID, serial, and lot traceability - Quarantine nonconforming material (physical and ERP hold) and raise NCRs in the QMS - Partner with the Supplier Quality Engineer on recurring supplier issues, SCARs, and supplier FAI submissions - In-Process & Build Quality - Conduct staged inspections at key assembly points (fit-up, torque, alignment, wiring and terminations, cable routing and labeling) mechanical and electrical build quality through dimensional, continuity, insulation resistance, and functional checks per approved test procedures - Monitor First Pass Yield (FPY), track defects through visual factory and daily walkdowns, and escalate repeat workmanship issues to CAPA - Confirm latest approved SOPs, drawings, and checklists are in use, and build records are fully traceable - Release Gates & Final Dispatch - Support FAT and SAT for assemblies and integrated systems - Authorize handover to FAT only when assembly is complete, no NCRs or inspections are open, BOM/revision and hardware/software versions are verified, and build records are uploaded - Release products for dispatch after verifying labeling, packaging, customer requirements, FAT approvals, and NCR closure; maintain the dispatch record in the QMS - Field & Customer Quality - Support investigation of field failures, installation issues, customer complaints, and warranty returns; feed findings back into design, process, and supplier controls - Support customer and owner's engineer audits and site inspections - NCR, CAPA & Risk Management - Log NCRs with full evidence and traceability, coordinate MRB dispositions, and track quarantines - Lead root cause analysis (5-Why, Ishikawa, 8D) and verify CAPA effectiveness before closure - Maintain PFMEAs and process risk assessments; recommend preventive actions from data trends without owning full preventive strategy - Support cost of quality reporting (scrap, rework, warranty) - QMS Compliance & Continuous Improvement - Keep quality records current in the QMS, ERP, and PLM (inspections, NCRs, CAPAs, FAT documentation, approvals) and maintain QMS dashboards for FPY, NCR trends, and CAPA aging - Conduct internal process and product audits and support ISO 9001, customer, and supplier audits; maintain calibration control of inspection equipment - Drive Lean/Kaizen activities (5S, poka-yoke, standardization) and capture lessons learned for future builds and designs - Performance measurements: (list) - Product Quality Performance (FPY, defect rates, escaped defects) - NCR & CAPA Effectiveness (cycle time, recurrence, on-time closure) - Build Control, Release Gate & Process Discipline - Field & Customer Quality (complaints, warranty returns) - Audit Performance & QMS Compliance - Continuous Improvement Performance - QMS / ERP / PLM Data Integrity We could treat Performance measurements as part of Responsibilities as well (maybe separate but not required). We'll include them as
- under Responsibilities.
Now Requirements: we have "Requirements Competencies & Skills" then list of competencies & skills (soft). Then "Mandatory:" list. Then "Desirable:" list.
We need to map to headings: Requirements, Qualifications, Skills.
We could put:
-
Skills
for the Competencies & Skills list (leadership, influence, analytical, etc.) -Requirements
for Mandatory list (Bachelor's degree, familiarity with standards, fluent English, min 5 years experience, etc.) -Qualifications
for Desirable list (Master's degree, ASQ CQE, etc.) Or we could swap. Usually Qualifications are mandatory; but we follow instruction: we have both headings available. We'll assign Mandatory to Requirements, Desirable to Qualifications. Now Benefits: we have bullet list under "Benefits Compensation And Benefits". We'll createBenefits
with- list.
Pay: we have paragraph about salary ranges. We'll create
Pay
withcontaining that paragraph. Schedule: none, so omit. Now we need to ensure we don't include boilerplate like EEO, equal opportunity, scam warning, application instructions, etc. At the end there is EEO statement and "Principles only. This role is not open to receiving agency candidates..." etc. That's boilerplate; we must remove. Also remove "Terabase is an equal opportunity employer..." etc. Also remove "Please contact our Recruiting team at careers@terabase.energy with any staffing-related inquiries." That's application instruction; remove. Now we need to preserve all substantive info. Let's verify we didn't lose any. From the posting: - "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." Keep as opening paragraph. - About the role paragraph(s): we captured. - Responsibilities: we captured all bullet points under Accountability & Authorities and subpoints, plus Performance measurements. Check if any responsibilities missing: The section "Quality coordinates and provides oversight; Engineering, Manufacturing, and Supply Chain own execution of design, process, and supplier actions." That's part of About the role paragraph; we included. Now "Performance measurements:" list we included. Now "Requirements Competencies & Skills": we captured as Skills. Now Mandatory list: we captured. Now Desirable list: we captured as Qualifications. Now Benefits: we captured bullet list. Now Pay: we captured paragraph about salary ranges. Now ensure we didn't inadvertently include any boilerplate like "Terabase is an
- list.
Pay: we have paragraph about salary ranges. We'll create
- for any list,