Domain Expert, Semiconductors & Infrastructure Palo Alto

Domain Expert, Semiconductors & Infrastructure

Bring deep semiconductors and infrastructure expertise into the room where enterprise agents get designed, and turn it into specifications engineers can build the same week.

Sycamore is building the trusted agent operating system for the enterprise. Our platform helps companies build, deploy, and orchestrate AI agents that take on real operational work, with the security and control large organizations need.

We are a small, engineering-led team working directly with Fortune 500 enterprises. We have raised $65M from Coatue and Lightspeed, along with other investors and industry leaders.

The hardest part of deploying an agent into an enterprise workflow is almost never the model. It is knowing what the workflow actually is: who decides what, under whose authority, against which rules, with what evidence, and what happens when the answer is wrong.

That knowledge lives in people who have done the work. You are one of them.

You will pair directly with our Applied AI engineers on customer deployments. They build; you supply the substance that makes what they build correct. Your output is not advice or a slide. It is a specification precise enough to become a workflow definition, a rule set, a review screen, and a set of thresholds. You will then judge whether what came back is actually right, which is a different question from whether it runs.

Our platform is built around this shape of work. It extracts structured facts from documents with citations back to the source, applies deterministic rules where rules exist, routes the ambiguous middle to a human with the right permissions and authority limit, and keeps a tamper-evident record of every decision. Each of those pieces needs someone who knows what correct looks like.

You will also be in front of customers throughout: discovery sessions, requirements work, design review, and the conversations where a skeptical operator decides whether we understand their job. Credibility with those people is a large part of the role.

Chipmakers, equipment and materials vendors, and data-center, energy, and industrial infrastructure operators run some of the most technically demanding operational work in any industry. Engineering change and design review. Supplier qualification and component compliance. Export-control and trade screening. Incident, 8D, and corrective-action workflows. Capacity and capital change management. Specification and datasheet questions grounded in internal documents.

There is also a strong fit with internal AI governance itself. These organizations are standing up architecture and technical review boards for their own AI programs, and that intake, risk assessment, and approval process is something Sycamore Govern addresses directly as a first-party product.

The constraints are unusually strict. Process and design data is among the most sensitive intellectual property these companies hold, export controls limit where systems and data can live, and qualification cycles are long. To be clear about scope: fab-floor systems are not something our platform touches today.

In one month, you might:

• Define the review-board taxonomy for a change or approval process: which tracks exist, who sits on each, and what evidence each track requires before it can sign off.
• Assemble the export-control and trade-compliance rules a workflow must screen against, and specify which determinations must always be made by a licensed human.
• Specify the IP-sensitivity classification for the documents in a workflow, and what that implies for where data may live and which roles may see it.
• Write down what this company's internal audit function means by auditable, and what evidence would satisfy it.
• Sit through a discovery session and leave with the process written down properly: decision points, authority limits, service levels, exception paths, and what happens on breach.
• Work with an engineer to decide which parts of a workflow should be deterministic rules and which genuinely require judgment, and be honest about which is which.
• Specify the review screen: what a reviewer must see to decide in thirty seconds, and which fields are the ones people actually get wrong.
• Set the thresholds for what is handled automatically, what is routed to a person, and what is refused outright, along with the relative cost of a false positive and a false negative.
• Review what an agent produced across a batch of real cases and tell the team where it is wrong, not just where it failed.
• Identify which system of record a workflow depends on and what integrating with it honestly requires, including what will still be manual.

• Serve as the domain authority on customer deployments in your industry, from discovery through production.
• Translate real operational processes into specifications precise enough to build from: decision points, roles and authority, rules, thresholds,…