Engineering Manager, Wireless and Digital Design

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract from posting. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, ITAR? Actually ITAR is requirement? It says ITAR REQUIREMENTS: must be US citizen etc. That is a requirement, so we can include under Requirements or Qualifications. But we should not include EEO boilerplate. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. We need to preserve all substantive information. Use

for section headings. Use

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

  for prose. We need to decide sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (basic qualifications), Qualifications (maybe strongly desired?), Skills (maybe list of technical skills), Benefits (list), Pay (salary range), Schedule (maybe not present; no schedule info). So we omit Schedule. We need to avoid filler like "commensurate with experience" in Pay section? The instruction: 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. For Pay, we have salary range: $169,000-$266,000 (commensurate with experience). The phrase "commensurate with experience" is filler? It's part of the description but maybe considered filler. The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include that phrase inside the content; just that we shouldn't have a heading with only filler. So we can include Pay section with the range and maybe note commensurate with experience as part of text. We need to include Benefits: they listed many items: Comprehensive Benefits – Health, Dental, Vision, & HSA options; Unlimited PTO; Commuter Benefits (if working from HQ); Learning & Development Allowance; Health & Wellness Stipend; Sabbatical Program; Cutting-Edge Space Tech – Work on state-of-the-art satellite system. Also relocation benefits mentioned earlier: relocation benefits available for those who qualify. So include those. Now we need to structure. We'll produce:

  About the role

  ... paragraph describing role, location, etc.

  Responsibilities

  • ... list items

  Requirements

  • ... basic qualifications

  Qualifications

  • ... strongly desired items

  Skills

  • ... maybe technical skills list? Could combine with Requirements/Qualifications but we need to follow instruction: prefer few substantive sections over many thin ones. Could merge Skills into Requirements/Qualifications? But we have separate headings for Skills. We could decide to not include Skills if content overlaps; but we need to include all substantive info. Could put technical skills under Requirements or Qualifications. However the instruction says use headings only when posting has real specific content for it. It doesn't forbid having overlapping content; but we should avoid thin sections. Maybe we can combine Skills into Requirements (since they are technical skills). But we already have Requirements for basic qualifications (education, years). Skills could be separate: list of specific technical proficiencies (Matlab, Python, C/C++, simulation tools, packet decoders, localization algorithms, RTL design, FPGA synthesis, memory interfaces, etc). Those are substantive. So we keep Skills section. Benefits section. Pay section. We must not include Schedule. Now we need to extract content. Let's parse the posting. Intro: "Hubble Network was founded with the intention of delivering on the promise of what Internet-of-Things (IoT) was supposed to be. We're building a global Bluetooth® network dedicated to machine-to-machine connectivity. We differentiate ourselves as the first modem-less and gateway-less, direct-to-satellite network from off-the-shelf Bluetooth® Low Energy chips. Hubble is ideal for applications in logistics, AgTech, and maritime where economies of scale for volume consumer and enterprise asset tracking is a priority. Our goal is to be the first billion-endpoint-connected network in the world. Hubble is an early-stage, venture-backed startup supported by some of the best investors in the world. In their previous lives, the founding team has been successful in raising $100s of millions in venture funding, developing the Amazon Sidewalk network, launching billions of dollars of space assets, and leading their teams to successful exits, both through acquisition and IPO. We are now looking to bring on talented team members who are the best at what they do to help us make Hubble a reality for the world. This role is based in Seattle, WA (relocation benefits available for those who qualify) We're looking for an Engineering Manager, Wireless & Digital Design to lead the design of Hubble's wireless communication and localization systems and own their implementation in HDL on our satellite FPGAs. This is a player-coach role: you'll bring senior-level wireless systems expertise — modeling, algorithm design, and system architecture for direct-to-satellite Bluetooth connectivity and geolocation — while managing and growing the team of digital design engineers who turn those designs into flight-ready FPGA implementations. You'll own the full path from wireless system design to silicon: defining the algorithms and protocols that connect terrestrial Bluetooth devices to satellites and determine their position from orbit, and directing the digital design team responsible for the RTL codebase that performs localization and decodes packets from ground-based BLE transmissions. You'll work closely with leaders across hardware, firmware, software, and customer success to translate strategic goals into clear product plans and deliverables. This is a hands-on role for a builder — someone who can move between technical detail, customer insight, and company strategy without losing momentum." That's About the role. Now Responsibilities: likely the bullet points after "You'll own the full path..." etc. Let's extract: - Lead the design of Hubble's wireless communication and localization systems and own their implementation in HDL on satellite FPGAs. - Bring senior-level wireless systems expertise — modeling, algorithm design, and system architecture for direct-to-satellite Bluetooth connectivity and geolocation. - Manage and grow the team of digital design engineers who turn those designs into flight-ready FPGA implementations. - Own the full path from wireless system design to silicon: defining the algorithms and protocols that connect terrestrial Bluetooth devices to satellites and determine their position from orbit. - Direct the digital design team responsible for the RTL codebase that performs localization and decodes packets from ground-based BLE transmissions. - Work closely with leaders across hardware, firmware, software, and customer success to translate strategic goals into clear product plans and deliverables. - Move between technical detail, customer insight, and company strategy without losing momentum (hands-on builder). We can phrase as list. Now Requirements (basic qualifications): list from "BASIC QUALIFICATIONS" section. Let's extract each line: - Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, or a related field - 10+ years of experience across wireless systems and/or FPGA-based digital design, including 3+ years leading or managing engineering teams - Strong understanding of communication theory and digital signal processing (DSP) — filtering, correlation, decimation, channel estimation, beamforming, timing recovery, coding/error correction, and fixed-point arithmetic - Experience with Matlab or Python and/or C/C++ for algorithm development, modeling, and simulation, plus simulation/verification tools (e.g., ModelSim, Questa, Vivado) and scripting (Python, Tcl) - Experience developing packet decoders for wireless communication protocols (e.g., BLE, ZigBee, LoRa, or custom PHYs) - Experience designing localization or geolocation algorithms (e.g., Doppler-based positioning, TDOA/FDOA, angle-of-arrival, or Kalman/particle filtering for position estimation) - Proven expertise overseeing RTL design (Verilog/SystemVerilog) for high-throughput, low-latency digital receivers - Skilled in FPGA synthesis, timing closure, and resource optimization on Xilinx or Intel/Altera platforms - Familiarity with high-speed memory interfaces (DDR/DDR3/DDR4) and high-speed serial interfaces (LVDS, SPI, I2C, UART, SERDES-based links such as JESD204, PCIe, Ethernet) - Demonstrated ability to lead technical teams: setting direction, mentoring engineers, running design reviews, and delivering against evolving requirements - Ability to work closely with RF engineers, firmware developers, and systems engineers to integrate and validate end-to-end communication chains - Strong interpersonal, verbal, and written communication skills - Ability and willingness to thrive in a fast-paced, rapidly changing work environment Also ITAR requirement: must be US citizen or lawful permanent resident. That is a requirement; we can add under Requirements. Now Qualifications (STRONGLY DESIRED): list: - +15 years of directly relevant experience - Prior experience managing digital design or FPGA teams - Experience with satellite-based geolocation or positioning systems (e.g., Doppler geolocation from LEO) - Experience designing distributed digital signal processing systems across multiple FPGAs or compute nodes - Familiarity with soft-core or hard-core processor integration (e.g., ARM) and peripheral interfacing (SPI, I2C, AXI); embedded Linux (Petalinux) experience - Familiarity with synchronization techniques (preamble detection, symbol timing recovery, frequency offset correction) - Multi-radio coexistence management — relevant given the BLE + satellite link environment. - Experience with lab tools such as oscilloscopes, logic analyzers, and RF test equipment for bring-up and debugging - Knowledge of low-power design techniques for space-based or resource-constrained systems Now Skills: maybe we can treat the technical skills as part of Requirements/Qualifications, but we already have those. However we could create a Skills section that consolidates the technical proficiencies: e.g., wireless systems, DSP, Matlab/Python/C/C++, simulation tools, packet decoders, localization algorithms, RTL design, FPGA synthesis, memory interfaces, serial interfaces, etc. But that would duplicate. To avoid duplication, maybe we omit Skills section and incorporate those into Requirements and Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Skills into Requirements (or Qualifications). But we already have Requirements and Qualifications separate; they are substantive. Adding Skills might be thin. So we can omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: list from "COMPENSATION & BENEFITS" and earlier relocation benefits. - Relocation benefits available for those who qualify - Comprehensive Benefits – Health, Dental, Vision, & HSA options - Unlimited PTO - Commuter Benefits (if working from HQ) - Learning & Development Allowance - Health & Wellness Stipend - Sabbatical Program – Recharge and explore new ideas - Cutting-Edge Space Tech – Work on state-of-the-art satellite system Now Pay: Salary range: $169,000-$266,000 (commensurate with experience). Also later line: "Seattle Washington Washington Pay $169,600—$266,000 USD". Slight discrepancy; we should preserve both? The posting includes both lines; we should preserve all substantive info. Might combine: Salary range $169,000-$266,000 (commensurate with experience) and also note Seattle Washington Pay $169,600—$266,000 USD. Could just include the range as given; but we have two slightly different numbers. To preserve all, we could mention both: "