Platform Software Engineer III

We need to output HTML fragment with sections: About the role (maybe from Elevator Pitch), Responsibilities (What You'll Do), Requirements, Benefits, Pay (Compensation and Transparency Statement), Schedule (maybe location and remote? Not explicit schedule; maybe not include schedule if not stated). The posting includes location and remote expectation; schedule not explicit. So we may omit Schedule unless there is explicit schedule info. There's no explicit schedule like full-time, but we can infer full-time but not explicit. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: base salary range. Benefits is stated. Schedule: not explicitly stated (no mention of hours, shift, etc). So we omit Schedule. We need headings:

for each section. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not include Job ID etc. Remove boilerplate like EEO, etc. Also remove application instructions (none). Remove duplicated lines. We need to preserve all substantive information. So we need to capture: - Elevator Pitch: description about role meaning, purpose, team, etc. Could be placed under About the role. - Success in the Role: Performance Outcomes (30 days, 90 days, 12 months). Could be part of Responsibilities or separate? Probably under Responsibilities. - What You'll Do: bullet list of duties (Linux C++ Development..., Enterprise-Level Software Development..., Electronics Integration & Prototyping..., Cross Functional Collaboration..., Leadership, Team Structure & Culture...). Actually those are subheadings within What You'll Do. We need to turn them into list items? The instruction: Use

  • for any list of duties/requirements/benefits. So we can treat each bullet as list item. However there are sub-sections with paragraphs. We could flatten: each major duty as list item, with maybe nested description? But we can't have nested HTML beyond
  • containing

    maybe. Simpler: create

    with each duty as
    • containing the description (maybe multiple sentences). That satisfies. - Requirements: list of requirements (10+ years..., Deep hands-on..., Strong Linux kernel..., Working knowledge..., Proficiency..., Solid digital..., Direct experience..., Experience..., Comfortable...). Use
      • . - Benefits: list of benefits (Equity..., Medical..., Flexible..., A 401(k)..., Unlimited vacation..., Quarterly stipend..., Tuition reimbursement..., Subscription to Calm...). Also maybe mention "We are passionate..." but that's more prose. We'll keep list. - Pay: base salary range $114,000 - $184,000 plus mention of target bonus, equity, comprehensive benefits package. Also mention compensation transparency statement. We'll put in

        . - Location: "Where is the role located? Our headquarters (and this role) is located in Waltham, Massachusetts. As a member of the Engineering team we expect you to come into the office daily, but we understand that things come up—you can work remotely from time to time for one-off needs." This could be placed under About the role or maybe a separate section? Not required heading. Could be a

        under About the role. - Culture description: "Leadership, Team Structure & Culture" paragraph about team, values. Could be part of About the role or Responsibilities. We'll include in About the role maybe. We must not create sections with filler. So we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Now craft HTML. We need to ensure no markdown fences, just raw HTML. Let's draft:

        About the role

        Evolv's R&D team is looking for an experienced and innovative Platform Software Engineer to provide technical leadership, improve software engineering practices, and be hands‑on with a team of SW engineers specializing in embedded, real‑time, and computer vision. In a fast‑paced development environment, the team continuously innovates new features and integrates complementary technologies into products. You will own the platform from the ground up — bringing up a custom Yocto‑based Linux distribution, writing and debugging kernel drivers, and building the secure boot and provisioning pipeline that ships with the hardware. You'll work directly with Electrical Engineering hardware engineers to translate schematics into working device drivers and device‑tree configurations, and partner closely with senior IC engineers on peripheral architecture and automated validation. The role is based in Waltham, Massachusetts; the expectation is to work in the office daily with occasional remote work for one‑off needs. The firm values a culture of trust, respectful challenge, continuous growth, and fun, guided by the principles: Do the Right Thing, Always; Put People First; Win Together; Own It; Be Bold, Stay Curious.

        Responsibilities

        • Linux C++ Development for Embedded Systems with strong focus on BSP and Kernel: maintain ownership of the OS layer build process, constructing and optimizing custom Yocto recipes, layers, and configurations; write, modify, and optimize Linux kernel device trees to map custom hardware peripherals and ensure clean boot routines; debug low‑level Linux kernel issues (boot failures, driver crashes, interrupt/DMA issues) using JTAG, serial console, kernel logs, ftrace/perf; own the secure boot and provisioning pipeline end‑to‑end — signed images, secure key storage/injection, fused security state — from design through production readiness; diagnose hardware‑software interface boundaries, including real‑time timing constraints, power profiles, and thermal behavior; design and implement real‑time systems interfacing with Linux on an SoC, meeting deterministic, low‑latency requirements.
        • Enterprise‑Level Software Development: design reusable, enterprise‑grade C++ software — modular component reuse and clean API abstraction, built for longevity across multiple product lines; manage component versioning, dependency trees, and decoupling strategies in resource‑constrained environments; write production‑quality C/C++17 for both user‑space applications and kernel‑adjacent components; apply advanced design patterns and object‑oriented principles to keep core libraries scalable and maintainable; build multithreaded applications using modern C++ concurrency primitives, thread synchronization, and lock‑free techniques; write clean, well‑documented, testable code; maintain quality through peer review and unit/functional testing; thoroughly document requirements, design intent, and validation data; use AI coding assistants (e.g., Claude) to accelerate development, testing, and documentation across the software lifecycle.
        • Electronics Integration & Prototyping: build and maintain Hardware‑in‑the‑Loop (HIL) test rigs and automated validation strategies to catch regressions at the hardware layer; bring up raw prototype boards in the lab, using bench instrumentation (oscilloscope, logic analyzer, multimeter) to root‑cause signal‑level issues; build Python‑based scripting frameworks to automate test execution, parse hardware logs, and orchestrate system‑level test behavior.
        • Cross Functional Collaboration: partner with EE/hardware teams throughout the product lifecycle — schematic review, component selection, and physical layout constraints; work with manufacturing to scale the provisioning process into production; support build automation, CI/CD pipelines, and SQA.
        • Leadership, Team Structure & Culture: join the Firmware Engineering team and work closely with the C++ Software Development Team; report to the Principal Firmware Engineer alongside a team of software, systems and hardware engineers; foster a culture of continuous improvement, innovation, and psychological safety; lead at least one internal technical workshop or knowledge‑sharing session; improve cross‑functional workflows around testing, deployment, and system reliability; help define and enforce coding standards and best practices across the team; weigh in on long‑term architectural decisions and product roadmap planning.

        Requirements

        • 10+ years of professional embedded/firmware software development experience.
        • Deep hands‑on experience building embedded Linux systems with Yocto (bitbake, layers, recipes, image customization) — ideally including a from‑scratch board bring‑up.
        • Strong Linux kernel driver development and debugging experience (character/platform drivers, interrupt handling, DMA).
        • Working knowledge of Device Tree syntax, bindings, and Yocto‑based DT configuration/overlay workflows.
        • Proficiency in C and C++17 for embedded/Linux development.
        • Solid digital hardware fundamentals — comfortable reading schematics, using a scope/logic analyzer, and reasoning about I2C/SPI bus timing and electrical behavior.
        • Direct experience with I2C and SPI Linux driver development on an SoC.
        • Experience with secure boot, image signing, or device provisioning on embedded Linux platforms.
        • Comfortable working cross‑functionally with EE teams to turn hardware requirements into software.

        Benefits

        • Equity as part of your total compensation package
        • Medical, dental, and vision insurance
        • Flexible Spending Accounts (FSA)
        • A 401(k) plan (and 2% company match)
        • Unlimited vacation policy
        • Quarterly stipend for perks and benefits that matter most to you
        • Tuition reimbursement to support ongoing learning and development
        • Subscription to Calm

        Pay

        The base salary range for this full‑time position is $114,000 – $184,000. In addition to base salary, the role offers a competitive target bonus, equity, and a comprehensive benefits package. This range reflects Evolv’s commitment to pay transparency and equity, in alignment with applicable state laws.

        Check for any boilerplate removed: we removed EEO, equal opportunity, scam warning, etc. We kept the compensation transparency statement but not the long list of states; we summarized. That's okay as we preserved substantive info (the range and that they disclose). We removed the detailed list of states; is that substantive? It's part of the transparency statement but maybe considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The list of states is part of legal compliance; could be considered boilerplate. Safer to remove it. We kept a short sentence about commitment to pay transparency and equity. That's fine. We also removed the "Compensation and Transparency Statement" heading; we used Pay section. We removed the "If you need a reasonable accommodation..." etc. That's EEO/accommodation boilerplate; remove. We removed the "Evolv participates in E-verify..." etc. Remove. We removed the "We are passionate, knowing that what we do..." paragraph under Benefits? Actually that was part of Benefits section but we kept benefits list; we removed the motivational prose. That's okay as it's not substantive benefit detail. We kept the "Where is the role located?" paragraph integrated into About the role. We kept the "Success in the Role: Performance Outcomes" content? We didn't explicitly include the 30/90/12 month outcomes. That's substantive; we missed it. Need to include that somewhere, likely under Responsibilities or a separate section. Since we have Responsibilities section, we can incorporate those outcomes as list items or as part of responsibilities. Let's add a subsection under Responsibilities maybe as list items: "Performance Outcomes: In the first 30 days... Within 90 days... Within 12 months..." We'll add as list items. Thus adjust Responsibilities
        to include those as list items. We'll add three list items for the outcomes. Let's rewrite Responsibilities
        with items: - Performance Outcomes: In the first 30 days, you will: Demonstrate technical depth and earn the respect of senior developers. Learn the product's hardware architecture. Review existing code and software architecture. Get hands‑on