Senior Hardware Systems Inegration Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About Volley (company description) maybe not needed as a heading? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. We have "About Volley" description: mission, etc. Could go under "About the role"? Actually "About the role" is typical heading for role description. The posting includes "The Role" section describing role. So we can put that under "About the role". Also there is "Why this is worth your time" and "Why Volley?" maybe could be part of About the role or separate? But we should follow headings. We have "What You Will Own" bullet list of responsibilities. That fits under Responsibilities. We have "Required Qualifications" list. That's Requirements or Qualifications? There's both Requirements and Qualifications headings. Usually Requirements = required qualifications. Qualifications = maybe preferred? But we have both Required and Preferred Qualifications. So we can put Required Qualifications under Requirements (or Qualifications). Preferred Qualifications under Qualifications? Or we could combine. The instruction: prefer few substantive sections over many thin ones. So we could have Requirements (including required) and Qualifications (including preferred). Or we could have Requirements (required) and Qualifications (preferred). Let's do that. Skills: maybe we can extract from required/preferred: experience with CAD, configuration management, Linux/Python, industrial communications, safety, etc. Could be a Skills section. Benefits: we have description of benefits: medical/dental/vision, 401k matching, PTO, holidays, life & disability, equity stake. Pay: base salary range $155k-$210k, equity stake. Schedule: willingness to be in Denver office five days a week, not hybrid/remote. We must not include boilerplate like EEO, legal, etc. Also must not include "Applicant must provide proof of his or her eligibility to work in the United States if selected for hire." That's maybe minor metadata; could be folded into a short p or dropped. Probably drop. Also must not include "We are not accepting resumes from third-party vendors..." etc. Drop. Now produce HTML. Structure:

About the role

... (company mission and role description)

Responsibilities

• ... each bullet from "What You Will Own"

Requirements

• ... required qualifications bullets

Qualifications

• ... preferred qualifications bullets

Skills

• ... maybe list of technical skills: CAD tools, configuration management, Linux/Python, Modbus, OPC UA, CAN, TCP/IP, PLCs, servo drives, safety-rated I/O, sensing, ROS/ROS2, C++, Python, AGV/AMR fleet integration, VDA5050, vertical transport standards, EV charging, OCPP, NFPA 70 Article 625, building codes, model-based systems engineering, automotive integration, problem resolution processes.

But we need to ensure we don't invent. Must preserve all substantive info; we can list skills derived from required/preferred. That's okay as it's not inventing, just extracting. Benefits:

Benefits

• Medical, Dental and Vision coverage covered up to 90% for employee and 75% for dependents.
• 401(k) plan with matching contributions, enrollment starts immediately.
• Generous paid time off and paid holidays.
• Life & Disability coverage.
• Equity stake in Volley (size determined within first months of hire, scales with level and experience).

Pay:

Pay

Base salary range: $155,000 to $210,000, determined by experience and skills.

Schedule:

Schedule

In‑person role requiring presence in the Denver office five days a week (not hybrid or remote).

Now we need to ensure we didn't repeat job title. Not included. Now we need to ensure we didn't include any boilerplate like EEO etc. We removed. Check for any leftover boilerplate: The "Why Volley?" includes base salary range etc which we used. Also includes "Why this is worth your time" which we may have omitted; but we could incorporate some of that into About the role or maybe a separate section? But we can drop if not needed. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the "Why this is worth your time" and "Why Volley?" content. If we drop them, we lose substantive info. So we need to incorporate that content somewhere. We have "Why this is worth your time" paragraph: "Most systems integration roles are about defending an architecture someone else set a decade ago. This one is about setting it. Volley is early enough that the interfaces you define become the product, and far enough along that you will watch them get realized in a building and carry real cars for real customers a year from now." And "Why Volley?" includes base salary range, equity stake, benefits description (which we already captured). Also includes "We have written this at the Senior level..." etc. That's about level. Could be included in About the role or maybe a separate section? But we have no heading for "Level". Could fold into About the role or Requirements? Probably About the role. Thus we need to include those paragraphs in About the role section. Let's craft About the role paragraph: combine company mission, role description, why it's worth your time, why Volley (including level note). Ensure we don't repeat job title. We'll produce a few paragraphs. Now Responsibilities: from "What You Will Own" bullet list. Let's extract each bullet: - System architecture, interface control, and configuration management. - Define and maintain the interfaces between subsystems: mechanical envelopes and tolerance stack-ups, power and grounding, signal and network topology, command and state semantics, timing, and failure behavior. - Own the interface control documents and keep them true, because in this system those gaps can lead to failures with a lead time. - You will also own the configuration management of the HW system, both as built/deployed as well as under development evolution. - Requirements flow-down and traceability. - Translate customer commitments, site constraints, and building code obligations into verifiable requirements on each subsystem, and keep the thread from a customer's throughput number to a supplier's acceptance test intact. - Supplier technical ownership. - Be the technical counterpart to our AGV, vertical transport, charging, and controls suppliers, from specification and RFQ through design review, factory acceptance, and warranty. - Evaluate platforms on their merits, write specifications a vendor can actually build to, and say no when what shows up is not what was specified. - Integration and protocol conformance. - We drive supplier AGVs over VDA5050. Other subsystems speak Modbus, OPC UA, CAN, and vendor-specific APIs. You will own conformance to the interface spec and make sure vendor deviations stay documented and contained at the boundary rather than leaking into our architecture. - The acceptance standard. - Define what gets proven at the bench, at the supplier's factory, at our Denver test facility, and on site, and what evidence closes each requirement. You author the acceptance criteria and test plans that the field team executes against, and you are the one who judges whether the results clear the bar. - The interface to the building. - Automated parking lives inside civil and structural reality: slab flatness and levelness, clearances, structural deflection, power, ventilation, and fire protection. You will define what the building has to provide, and work with architects, general contractors, and code consultants when what was built diverges from what was drawn. - Technical leadership. - This is an individual contributor role and it stays one in the immediate future. Your leverage comes from your own judgment, your specifications, and the decisions you make, not from headcount. As the program grows you may have an engineer or two working under you, and you will set their technical direction and review their work, but the job is to build, not to manage. We need to keep each as list items. Now Requirements: Required Qualifications bullets: - BS in engineering (Mechanical, Electrical, or Computer Science), or equivalent experience - 8+ years developing and deploying complex electromechanical or robotic systems, including at least one you followed all the way into the field - Deep experience with CAD tools, drawing generation, and lifecycle management - Experience with configuration management best practices, processes, and/or systems - Willingness to be in our Denver office five days a week. This is not a hybrid or remote role. The prospect of joining an in person dynamic team is exciting to you. - Demonstrated ownership of system-level architecture: interface control documents, requirements flow-down, tolerance and error budgets, and the discipline to keep them current when the design moves - Real experience as the technical owner of an outside supplier: writing the specification, reviewing their design, defining acceptance, and holding the line on deviations or changes, and executing change management when it is required - The ability to troubleshoot across domains (mechanical, electrical, controls, software, and operations), and to take on the problems that sit between owners - A track record of raising the technical bar around you: mentoring less experienced engineers, reviewing others' designs or architecture decision, and getting a cross-functional group to converge on a decision without holding authority over anyone - Working fluency with industrial communications and controls: Modbus, OPC UA, CAN, TCP/IP, PLCs, servo and motor drives, safety-rated I/O, and sensing (depth, vision, position, temperature, current) - Enough Linux and Python to pull logs apart and test a hypothesis yourself. You do not need to be a software engineer, but you do need to be able to read one's work - Literacy in safety and agency certification: hazard analysis, risk assessment, creating functional safety concepts, and the practical realities of UL, IEC, ISO, and CE - A high tolerance for ambiguity, and the judgment to know when to resolve it with a decision versus a test - Writing that holds up: a specification a vendor can build to and a test report a reader can act on Now Qualifications: Preferred Qualifications bullets: - Experience with software development in ROS/ROS2, C++, and/or Python - AGV/AMR fleet integration generally and more applicable VDA5050 or comparable interface protocols - Vertical transport and material handling: VRCs, scissor lifts, and conveyors, and the standards that govern them (ASME B20.1, ISO 13849, and for automated parking specifically, EN 14010) - EV charging, including automated or robotic charging, OCPP, and NFPA 70 Article 625 - Work with building codes and authorities having jurisdiction: IBC, IMC, NFPA, permit review, alternative means and methods - Requirements and model-based systems engineering tooling, used because it helped rather than because it was mandated - Automotive or vehicle integration, debugging and troubleshooting experience - Having built the process, not just followed it and ideally in early-stage environments where the standard is whatever you wrote down and others adhere to it because its the right way to execute - Formal training or experience with problem resolution processes Now Skills: we could combine some of the technical skills from required/preferred but not duplicate. However we might avoid a separate Skills section if we think it's thin. But we have many