<div>Anthriq is a signal processing infrastructure company. We build the full acquisition and compute stack for human-aware technology — from custom analog front-end IP that captures biosignals at the source, to signal-first compute systems built for time-critical, deterministic workloads.</div><div>Our infrastructure is designed around one principle: the signal should never be the bottleneck. General-purpose processors — CPUs, GPUs, DSPs — were not built for this class of problems. They approximate determinism. We build it into the architecture.</div><div>Anthriq Silicon is our ground-up effort to build a new compute category.</div><div> </div><div>Read More About Anthriq Silicon Program here: <a href="https://dataroom.anthriq.com/xL2dwHtZS7" rel="noopener noreferrer" target="_blank">https://dataroom.anthriq.com/xL2dwHtZS7</a></div>

Anthriq

About Us
Anthriq is a signal processing infrastructure company. We build the full acquisition and compute stack for human-aware technology — from custom analog front-end IP that captures biosignals at the source, to signal-first compute systems.
Anthriq Silicon is our ground-up effort to build a new compute category. Read more about the Anthriq Silicon Program here: anthriq.com/silicon
About the Role
We are taking our first custom ASIC — a multi-core vector processor with a purpose-built instruction set — from architecture to qualified production silicon on an advanced process node.
A program like this has two kinds of gravity. Inside, several engineering tracks move at different speeds and depend on each other in ways that are rarely written down. Outside, a set of partners, IP providers, and manufacturing stakeholders all have their own schedules, and none of them are ours to control. Tapeout happens when both of those are held together by someone whose full-time job it is.
That is this role. You will own the master schedule, the dependency map across every internal and external commitment, design freeze and change control, the review cadence, and deliverable acceptance at each milestone.
What makes this worth doing: there is one silicon program at this company, and it is this one. You will not be one of nine TPMs reporting into a program office. You will work directly with the founders and the architecture team; you will be in the room where scope and schedule get decided rather than briefed afterward, and your read on what is real versus what is optimistic will move dates that matter.

Responsibilities
Own the integrated program plan
<ul>
<li>Maintain one master plan spanning the internal engineering tracks — RTL design, verification, firmware and pre-silicon software, IP integration, physical implementation and every external delivery the program depends on, through tapeout, NPI and qualification.</li>
<li>Track the critical path weekly and plan backwards from the dates that cannot move, not forwards from what teams would prefer.</li>
</ul>
Run the cadence and break cross-team blockers
<ul>
<li>Run the weekly program review and milestone reviews from a single source of truth.</li>
<li>Find the coupling points before they bite: a coverage-closure slip gating a design freeze, an incomplete register map stalling firmware, a late IP handover holding up integration, a constraints package that will not survive synthesis. Drive these across team leads rather than reporting them after the fact.</li>
<li>Hold every track to a shared definition of done, and keep interfaces between teams written down rather than assumed.</li>
</ul>
Own the dependency map
<ul>
<li>Track every commitment the program rests on with a date, an owner, and an acceptance bar: design deliverables, timing constraints and power intent, third-party IP delivery including licensing and documentation, emulation and virtual platform builds, package and test specifications, coverage and quality targets, register maps, and milestone approvals.</li>
<li>Chase every line, and flag slippage weeks ahead rather than at the review.</li>
</ul>
Run freeze and change control
<ul>
<li>Own the design freeze gates and the ECO log, keeping late change inside agreed limits.</li>
<li>Route every proposed change through a documented decision — cost, schedule impact, approval. Nothing enters a frozen baseline silently.</li>
</ul>
Manage external delivery
<ul>
<li>Be the program's point of contact for vendors, IP providers, EDA partners and manufacturing-side stakeholders whose timelines we depend on.</li>
<li>Track what was committed against what has arrived, and read technical status reporting critically rather than accepting the summary slide.</li>
<li>Know what evidence each milestone requires before it is accepted, and assemble it.</li>
</ul>
Manage risk and report it straight
<ul>
<li>Maintain a live risk register with real mitigations and named owners, and drive contingency planning on tapeout-critical paths.</li>
<li>Publish a weekly status — schedule, risks, decisions needed, dependencies missed — and escalate to CTO/CEO with a recommendation attached, not just a problem.</li>
<li>Flag where timelines are at risk from team bandwidth gaps, and feed that into resourcing and hiring conversations.</li>
</ul>
Requirements
<ul>
<li>8–12 years in semiconductor product development, including 3+ years in a technical program or project management role on SoC/ASIC programs.</li>
<li>At least one SoC taken from RTL to tapeout, ideally through silicon bring-up. Non-negotiable.</li>
<li>Working technical fluency across the ASIC lifecycle — design freeze, coverage closure, DFT insertion, synthesis, P&amp;R, STA, EM/IR, DRC/LVS, netlist drops and ECO classes. You will not be hands-on in any one discipline, but you will not be a relay either: you need to ask the next question and know when an estimate is soft.</li>
<li>Experience holding external partners — design services, foundry, OSAT, IP vendors — to your dates, not just attending their status calls.</li>
<li>Track record running multi-team programs with competing priorities and a hard external deadline.</li>
<li>Strong written communication. A large part of this job is a status note clear enough that engineering leads trust it and nobody rewrites it.</li>
<li>Comfortable with incomplete information, and willing to own the uncomfortable conversation: a slipped date, a thin report, bad news delivered early.</li>
<li>B.E./B.Tech in Electronics, Electrical, Computer Science or related field.</li>
</ul>
Preferred
<ul>
<li>Prior time at a fabless semiconductor company or chip startup, through a tapeout cycle.</li>
<li>Advanced-node exposure (7nm or below).</li>
<li>Third-party IP licensing and delivery coordination.</li>
<li>Familiarity with hardware emulation and virtual prototyping platforms.</li>
<li>Contract-linked delivery: SOWs, acceptance criteria tied to technical deliverables.</li>
<li>PMP/PgMP is a plus, but not a substitute for having run a real program.</li>
</ul>