Director, Connected Lifecycle Engineering

About Us

Shark Ninjais a global product design and technology company, with a diversified portfolio of 5-star rated lifestyle solutions that positivelyimpactpeople’s lives in homes around the world. Powered by two trusted, global brands, Shark and Ninja, the company has a proven track recordof bringing disruptive innovation to market and developing one consumer product after another has allowed

Shark

Ninjato enter multiple product categories, driving significant growth and market share gains. Headquartered in Needham, Massachusetts with more than4,100associates, the company’s products are sold at key retailers, online and offline, and through distributors around the world.

At Shark Ninja, we’re building an AI-native culture. We’re not waiting for the future; we’re creating it. Our people are expected to experiment boldly, adopt new tools, and continuously raise what’s possible to create meaningful impact for our consumers. If you believe the best way to do your job hasn’t been invented yet, you’ll fit right in.

Needham, MA

Every connected Shark Ninja product — the wireless link, the on-device display, the companion app experience — runs on firmware this leader owns. You will set the architecture that every connected program in the portfolio is built and gated against, and own the delivery of that firmware globally, whether it's written by your team or by an ODM/JDM partner.

This is a dual-mandate role: architect and delivery owner.

Architecture. You define the connectivity stack standards, pairing and provisioning protocols, display and embedded UI frameworks, and the app- and cloud-integration interfaces that gate every connected firmware program.

Delivery. You own global connected-device firmware — wireless connectivity, connected-device security, over-the-air updating, on-device displays, and the differentiated connected experiences that set our products apart.

You’ll operate as a peer to the Embedded Firmware director (who owns non-connected embedded architecture and delivery), and partner with the Embedded Firmware director in Asia on connected features executed from that region.

• Architecture, interface definitions, and integration standards for wireless connectivity, display/UI, and companion app and cloud integration — all product categories, globally.
• Architectural standards for Bluetooth/BLE, Wi‑Fi, Zigbee, Thread, and Matter stacks, and for display and embedded graphics/UI frameworks.
• Portfolio‑wide device provisioning, pairing, and companion‑app integration protocols: BLE GATT profiles, Wi‑Fi onboarding, cloud device registration and authentication.
• Technical decisions on wireless silicon, display hardware, and connectivity modules, in partnership with Hardware Engineering.
• A reuse‑first strategy — proven connectivity and UI components, vendor SDKs, and reference designs — reserving in‑house development for differentiated experiences, security, and IP.
• Connected architecture intent translated into requirements clear enough that development partners execute without interpretation.

• Engineering standards for connectivity and display/UI subsystems, applied equally to internal developers and third‑party suppliers.
• The technical requirements embedded in supplier agreements for connected subsystems — including the pre‑MP reproducibility deliverable: source, toolchain, and signed build manifest sufficient to independently rebuild shipping binaries.
• Design review and gating checkpoints that connectivity, display, and app‑integration deliverables clear before integration.
• Connected product behavior defined at design time with Systems Engineering…