Staff Embedded Firmware & System Software Engineer — Platform Controller and SoC Stack

We need to output HTML fragment with sections: About the role, Responsibilities (What You’ll Do), Qualifications (Required Qualifications, Preferred Qualifications maybe combined?), Benefits? There's mention of equity, compensation range. Pay section: we have compensation range. Should we include Pay section? The posting includes compensation range and equity. So we can include Pay section with that info. Benefits? Not explicit benefits besides equity. Could include Benefits section maybe not needed. Schedule not mentioned. So we include About the role, Responsibilities, Qualifications (maybe split Required and Preferred?), Pay. Also maybe About TYLsemi, Inc. could be part of About the role? The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. We have About the role content (first paragraph). Responsibilities (What You’ll Do). Qualifications (Required Qualifications and Preferred Qualifications). Pay (compensation range and equity). Possibly Skills? Not separate. Benefits? Equity could be considered benefit but we already have Pay. Could include Benefits with equity? But instruction: only include section when posting has real specific content. Equity is mentioned under compensation. So Pay section can include both cash and equity. We'll not create Benefits separate. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Not present. We need to preserve all substantive info. So include all paragraphs. We'll structure:

About the role

... (the About The Role paragraph)

Responsibilities

• ... each bullet from What You’ll Do

We need to break the responsibilities into list items. The text includes multiple sentences; we can split by sentences or logical chunks. We'll create list items for each major duty. Then Qualifications: maybe two subsections? But we can combine Required and Preferred under Qualifications heading with subheadings? Not allowed to add extra headings beyond those listed? Could use

Required Qualifications

and

Preferred Qualifications

but those are not in the allowed list? The allowed list includes Qualifications (singular). It didn't forbid subheadings but we should follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and inside we can have paragraphs for Required and Preferred. Could also split into two headings if we treat them as separate sections but they'd be Qualifications and maybe Skills? Not ideal. Better to have one Qualifications section with two paragraphs: Required Qualifications and Preferred Qualifications as bold? But we cannot add extra headings; we can use inside

. That's okay. Thus:

Qualifications

Required Qualifications: ...

Preferred Qualifications: ...

Pay section:

Pay

The compensation range shown below represents total target cash compensation and includes both base salary and target bonus. Actual compensation will vary based on factors such as experience, skills, qualifications, job level, and work location. In addition to cash compensation, this position is eligible for equity in the form of stock options, giving you the opportunity to share in the Company’s long-term growth and success.

The Pay Range For This Role Is 180,000 - 216,000 USD per year (US)

We should not include duplicate lines. Ensure we preserve all substantive info from About TYLsemi, Inc. etc. That content is under "About TYLsemi, Inc." which is basically company description. Should we include that under About the role? It's separate but could be part of About the role? The instruction: About the role heading for section headings e.g. About the role. The initial "About The Role" paragraph is about the role. Then later there is "About TYLsemi, Inc." which is about the company. Could we include that under About the role as well? Might be better to add another section like "About the company" but not in allowed list. Could we incorporate it under About the role? Might be okay to add a paragraph after the initial About the role content. But the instruction says use headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid additional headings not listed, but says prefer a few substantive sections over many thin ones. Could we add a section "About the company" using

About the company

? Not in list but maybe acceptable. However to be safe, we could include that content under About the role as additional paragraphs, since it's still about the role/company context. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive. So we could add another heading like "About the company". But to avoid risk, we can keep it under About the role. Thus About the role section will have two paragraphs: first the role description, second the company description (About TYLsemi, Inc.) plus the rest of the motivational content (The Opportunity, Why Now, Culture & Team, The Ask, etc). That's a lot of content; we need to preserve all substantive info. So we will include all those paragraphs under About the role. Thus final HTML:

About the role

We are building the software stack that runs on next-generation silicon. Based on Zephyr-platform management controller responsible for secure boot, system software on the application processor — bootloader, kernel drivers, PCIe subsystem, and IOMMU configuration — that turns raw silicon into a platform an operating system can run on.

The Opportunity The AI infrastructure market is exploding. Every hyperscaler, every cloud provider, every AI company is building custom silicon. But they all face the same problem: how do you connect hundreds of chips, deliver clean power at scale, and move terabits of data without melting the package? That's what we solve. TYLsemi builds the chiplet infrastructure IP — the IO, power delivery, and interconnect building blocks — that makes AI/HPC systems actually work at scale. This isn't a nice-to-have. It's the critical path.

Why Now The Market Window The semiconductor industry is going through its biggest architectural shift in 40 years: Moore's Law is dead. 2nm and beyond delivers marginal performance gains. The future is chiplets, not monolithic dies.Custom silicon is now mainstream. Google, Microsoft, Amazon, Meta, OpenAI — they're all designing their own ASICs. The $50B custom silicon market is growing 30% annually.IO and power are the bottleneck. Solve hard problems and provide something which is a category in itself.Translation: We're entering the market at exactly the moment when every major AI/HPC player needs what we're building, and their alternatives are disappearing.

Culture & Team: How We Work No Politics, No Bureaucracy There are no layers, no approval chains, no corporate theater. If you have an idea, we test it. If it works, we ship it.No endless meetings, no PowerPoint presentations to convince middle management. Remote-Friendly, Global Team US team: Bay Area preferred, but we hire the best people regardless of locationIndia team: Building a world-class design center in Bangalore Move Fast, Ship Real Products We're not a research project. We have paying customers, committed capital, and aggressive timelines. This is a company, not a lifestyle business. We're building to win. What We Value Ownership mindset. You're not here to execute someone else's roadmap. You're here to define it.Bias for action. We move fast. Analysis paralysis doesn't fly here.Deep technical expertise. This is hard engineering. We need people who've shipped real silicon and debugged real hardware.Low ego, high standards. We don't care about titles or politics. We care about results.

The Ask If you're reading this, you're probably comfortable. You have a good job at a stable company with all the benefits. We're asking you to walk away from that and bet on us. Here's Why You Should The market is real. AI infrastructure spending is $200B+ annually and growing 40% YoY. Every hyperscaler needs what we're building.The team has done this before. We've built and exited semiconductor companies at scale. This isn't our first rodeo.The traction is de-risked. We have LOIs, strategic investors, and a clear path to revenue.The work is consequential. You're not optimizing someone's ad click-through rate. You're building the silicon infrastructure that powers AI. This is the bet. Join us and build something that matters. Or stay comfortable. No judgment. But if you're the kind of person who wants to take the shot, we'd love to talk.

Then Responsibilities list. We need to extract bullet points from "What You’ll Do". Let's parse: - Firmware and platform control - Design, implement, and maintain Zephyr RTOS firmware for a platform management controllers, including device drivers, subsystem integration, and application-level services. - Write and upstream-quality-review drivers against Zephyr's driver model — devicetree bindings, Kconfig, init levels and priorities, struct device APIs. - System software and high-speed interconnect - Bring up and debug PCIe links on first silicon — LTSSM progression, link training failures, lane reversal and polarity, equalization, speed and width negotiation. - Implement and maintain PCIe host controller and endpoint drivers: enumeration, configuration space, BAR allocation, MSI/MSI-X interrupt routing, AER and error handling, ASPM and link power states. - Configure and validate IOMMU behavior — address translation, DMA remapping, device isolation domains, page-table management, fault reporting and recovery. - Develop system software across the boot and runtime path: bootloader, firmware-to-OS handoff, ACPI or device tree description, kernel drivers, and the DMA and memory-management interfaces they depend on. - Debug DMA correctness and coherency problems end to end, from device transaction through translation to system memory. - Silicon and process - Perform post-silicon bring-up: first-boot debug, clock and reset validation, bus enumeration, triage of RTL-versus-firmware ambiguity with design teams. - Debug hard problems using JTAG/SWD, ETM/ITM trace, protocol analyzers, and logic analyzers — including intermittent, timing-dependent, and multi-master failures. We'll create list items for each of these bullet points (maybe combine sub-bullets). We'll produce

• ...

with each distinct duty. Now Qualifications: Required Qualifications paragraph: "8–10 years of professional embedded firmware and/or system software development in C, with meaningful exposure to modern C++ or Rust. Deep, hands-on RTOS experience on 32-bit microcontrollers (Arm Cortex-M or RISCV) scheduling, priority assignment, ISR design, synchronization primitives, and the failure modes each one produces. Proven driver development experience against a formal driver model, including bus drivers and interrupt-driven peripherals. System software fundamentals: virtual memory and address translation, DMA and cache coherency, the kernel/users pace boundary, and how a platform gets from reset vector to a running OS. Working knowledge of PCIe architecture — enumeration, configuration space, BARs, MSI/MSI-X, and the transaction model — sufficient to debug why a device is not appearing or not moving data. Understanding of what an IOMMU is for and what it costs: translation, isolation, and the DMA failure modes that appear when it is misconfigured. Demonstrated ability to read a hardware specification or register map and translate it into correct, testable software without handholding. Applied AI/ML knowledge — Strong AI based coding