Jobs · Engineering · California

Digital - RTL Design Quality & Automation Engineer

Eliyan Corporation · San Francisco Bay Area · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role (already present), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role (we have a paragraph). Responsibilities: there is a list under "Key Responsibilities" with subheadings Design Quality & Signoff, Flow Automation and CIC, AI-Augmented Tooling. We need to extract responsibilities as list items. Probably combine them into a
  • list. Requirements: "What You'll Bring" includes bullet points: BS or MS..., 3+ years..., Working knowledge..., Proficiency..., Experience..., Practical experience..., Authorization..., On-site Monday through Friday... Also "Preferred Qualifications" list. We can combine required and preferred? The instruction: Use section headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. There's no explicit Pay or Benefits specifics besides "Comprehensive Benefits" mentioned at top, and "Equity Participation". So we have Benefits: "Comprehensive Benefits" and "Equity Participation". That's specific enough? It says "Comprehensive Benefits" and "Equity Participation". That's specific enough to include Benefits section. Pay: not specified. Schedule: "On-site Monday through Friday at our Bay Area, Vancouver, or Toronto office." That's schedule info (onsite M-F). So we can include Schedule section. Skills: maybe we can extract technical skills: Python, Tcl, shell scripting, Git, Linux, Makefiles, LLM APIs, etc. Could be a Skills section. Qualifications: maybe we can include education and experience as Qualifications. But we already have Requirements. The instruction: Prefer a few substantive sections over many thin ones. We need to decide which sections to include: About the role (given), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Schedule. Possibly also Qualifications if we separate required vs preferred. But we can combine required and preferred into Requirements. Let's see. We need to preserve all substantive information. So we need to include all details from the posting, except boilerplate. Let's parse. Posting text: "Lint / CDC / Synthesis Quality -- AI-Augmented Design Flows - CI/CD for RTL On-Site Monday-Friday - Bay Area, CA / Vancouver, BC / Toronto, ON Full-Time - Equity Participation - Comprehensive Benefits ABOUT THE ROLE Eliyan is the chiplet interconnect pioneer behind NuLink, the industry's most efficient chiplet-to-chiplet PHY technology. With Series C funding from leading hyperscalers and AI infrastructure providers, we are scaling our digital design organization to support multiple concurrent IP programs across advanced process nodes. Here is the honest version of this job. Our digital designers spend part of every week doing work a machine should be doing: re-running lint and CDC by hand, reading thousands of violations to find the twenty that matter, chasing down which synthesis run regressed QoR, and manually assembling the evidence that a branch is clean enough to promote to release. We are looking for an engineer who can own the intersection of design quality and design automation. In this role you will define and enforce signoff criteria for lint, CDC, and synthesis across all active programs, build the waiver management and tracking infrastructure, and develop AI-augmented tooling that turns thousands of tool violations into actionable, designer-ready reviews. You will report into the digital design team and work directly alongside RTL designers — this is not a pure DevOps or IT role. Key Responsibilities Design Quality & Signoff Define and maintain lint, CDC, and synthesis elaboration signoff criteria across all active design programs. Build and own the waiver management system — structured flow with owner attribution, justification, expiration, and audit trail. Analyze synthesis results for area, timing, and power regressions; trace QoR anomalies to specific RTL changes. Collaborate with project design leads to develop and maintain project-specific rule decks, synthesis constraints, and signoff checklists. Flow Automation and CIC Own the Jenkins-based CI pipeline for RTL quality: lint, CDC, RDC, elaboration, synthesis, and STA. Build the dev-to-release promotion pipeline with automated gating, clean-run qualification, and handoff evidence generation. Develop per-project dashboards for QoR tracking, regression visibility, and release readiness. AI-Augmented Tooling Develop LLM-based violation triage pipelines that classify lint and CDC output, suppress known-benign patterns, and surface real issues with context. Build automated pull requests with violations pre-filtered, grouped, and annotated for designer review. I mplement spec-to-RTL consistency checking and CI-integrated documentation generation using LLM-driven pipelines. Benchmark AI output quality, measure false-negative rates, and establish guardrails the design team can trust. What You'll Bring BS or MS in Electrical Engineering, Computer Engineering, Computer Science, or a related field. 3+ years in ASIC or SoC design automation, with hands-on experience running and analyzing lint, CDC, or synthesis tools. Working knowledge of SystemVerilog and the RTL front-end flow — able to read violations, assess severity, and disposition findings. Proficiency in Python, Tcl, shell scripting, Git, Linux, and Makefiles. Experience building and maintaining CI/CD pipelines (Jenkins, GitLab CI, or GitHub Actions). Practical experience with LLM APIs or agent frameworks (e.g., Anthropic Claude, OpenAI) applied in a production or team-facing context. Authorization to work in the United States or Canada; visa sponsorship may be considered for exceptional candidates. On-site Monday through Friday at our Bay Area, Vancouver, or Toronto office. Preferred Qualifications Experience with industry-standard EDA tools such as Synopsys SpyGlass, Design Compiler, PrimeTime; Cadence Genus, Conformal; or Siemens Questa. Experience building waiver management systems, violation databases, or design quality dashboards. Background in data engineering or ML systems: evaluation harnesses, retrieval pipelines, or production inference. Exposure to PHY, SerDes, die-to-die interconnect, or chiplet-based SoC design. Open-source contributions to design automation, hardware verification, or developer tooling. We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us." We need to remove boilerplate: the last paragraph about AI tools in hiring process, contact us, etc. Also maybe the "We may use artificial intelligence..." is boilerplate; remove. Also remove duplicated lines? Not seeing duplicates. Now we need to produce HTML fragment with sections. We'll have:

    About the role

    ... (the paragraph about Eliyan, etc.)

    Responsibilities

    • Define and maintain lint, CDC, and synthesis elaboration signoff criteria across all active design programs.
    • Build and own the waiver management system — structured flow with owner attribution, justification, expiration, and audit trail.
    • Analyze synthesis results for area, timing, and power regressions; trace QoR anomalies to specific RTL changes.
    • Collaborate with project design leads to develop and maintain project-specific rule decks, synthesis constraints, and signoff checklists.
    • Own the Jenkins-based CI pipeline for RTL quality: lint, CDC, RDC, elaboration, synthesis, and STA.
    • Build the dev-to-release promotion pipeline with automated gating, clean-run qualification, and handoff evidence generation.
    • Develop per-project dashboards for QoR tracking, regression visibility, and release readiness.
    • Develop LLM-based violation triage pipelines that classify lint and CDC output, suppress known-benign patterns, and surface real issues with context.
    • Build automated pull requests with violations pre-filtered, grouped, and annotated for designer review.
    • Implement spec-to-RTL consistency checking and CI-integrated documentation generation using LLM-driven pipelines.
    • Benchmark AI output quality, measure false-negative rates, and establish guardrails the design team can trust.
    Note: there is a typo "I mplement" should be "Implement". We'll correct? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Should we keep the typo? It's part of the posting. Probably we should keep as is, but we could keep the exact text: "I mplement spec-to-RTL consistency checking". However that seems like a formatting error. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The typo is not substantive? It's a mistake but it's part of the text. I'd keep it as is: "I mplement spec-to-RTL consistency checking". But we could keep the original phrase exactly. Let's keep as is. Now Requirements section: combine "What You'll Bring" bullet points. We need to decide if we call it Requirements or Qualifications. The posting has "What You'll Bring" (requirements) and "Preferred Qualifications". We could have Requirements (mandatory) and Qualifications (preferred). But instruction says prefer few substantive sections over many thin ones. Could combine both into Requirements section, but we might lose distinction. However we can include both as separate sub-sections? Not allowed; only headings allowed are the listed ones. We could have Requirements (mandatory) and Qualifications (preferred) as separate sections if both have content. That would be two sections, still okay. But we need to see if we have enough content for each. Mandatory: BS/MS, 3+ years, working knowledge SystemVerilog, proficiency Python/Tcl/shell/Git/Linux/Makefiles, experience building CI/CD pipelines, practical experience with LLM APIs, authorization to work US/Canada, on-site Monday-Friday. Preferred: experience with EDA tools, experience building waiver management systems, background in data engineering/ML systems, exposure to PHY/SerDes/die-to-die/chiplet SoC, open-source contributions. We could put mandatory in Requirements, preferred in Qualifications. That seems reasonable. Now Benefits: we have "Equity Participation" and "Comprehensive Benefits". Also maybe "Full-Time". But Benefits section should contain those specifics. Schedule: "On-site Monday through Friday at our Bay Area, Vancouver, or Toronto office." That's schedule. Pay: not specified, so omit. Now we need to ensure we don't include any boilerplate like "Full-Time" maybe part of schedule? Already schedule covers on-site M-F. Full-Time is implied but we could include in schedule? Not needed. Now produce HTML. Let's craft the About the role paragraph: combine the sentences from "ABOUT THE ROLE" up to before "Key Responsibilities". The paragraph: "Eliyan is the chiplet interconnect pioneer behind NuLink, the industry's most efficient chiplet-to-chiplet PHY technology. With Series C funding from leading hyperscalers and AI infrastructure providers, we are scaling our digital design organization to support multiple concurrent IP programs across advanced process nodes. Here is the honest version of this job. Our digital designers spend part of every week doing work a machine should be doing: re-running lint and CDC by hand, reading thousands of violations to find the twenty that matter, chasing down which synthesis run regressed QoR, and manually assembling the evidence that a branch is clean enough to promote to release. We are looking for an engineer who can own the intersection of design quality and design automation. In this role you will define and enforce signoff criteria for lint, CDC, and synthesis across all active programs, build the waiver management and tracking infrastructure, and develop AI-augmented tooling that turns thousands of tool violations into actionable, designer-ready reviews. You will report into the digital design team and work directly alongside RTL designers — this is not a pure DevOps or IT role." We'll put that in a

    . Now Responsibilities list as above. Now Requirements (mandatory) list: - BS or MS in Electrical Engineering

Similar jobs

Automation Engineer

Piper CompaniesCharlotte, NC· 1 mo ago
Information Technologyapply on careers.pipercompanies.com

Automation Engineer

SLAS (Society for Laboratory Automation and Screening)Fridley, MN· 3 mo ago
Engineering$112k–$130k/yrapply on careers.slas.org

Automation Engineer

Hamilton CompanyReno, NV· 3 mo ago
Engineeringapply on careers-hamiltoncompany.icims.com