> Markdown version of [/jobs/ext/3590603-applications-engineering-sr-engineer](https://www.wearedevelopers.com/jobs/ext/3590603-applications-engineering-sr-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Applications Engineering, Sr Engineer

- **Company:** Synopsys
- **Location:** Mountain View, CA, United States
- **Experience:** Expert
- **Contract:** Internship / Graduate position
- **Skills:** Very-Large-Scale Integration, Computer Engineering, Software Debugging, Linux System Administration, Tcl (Programming Language)
- **Published:** October 5, 2026
- **Apply:** https://www.juju.com/job/21_01a0ef04-3a74-764c-80b8-e65c339481b3

## About the Role

* Bachelor's degree in Electrical Engineering, Computer Engineering, or related field, plus 2 years in semiconductor EDA, IC design, or applications/support; or Master's degree with relevant coursework or internship experience
 * Working understanding of RTL power concepts including switching power, internal power, leakage power, and clock gating fundamentals
 * Hands-on experience with Linux environments and Tcl scripting for automation or tool interaction
 * Ability to follow established technical flows, reproduce results, and document findings clearly for both technical and non-technical audiences
 * Strong written and verbal communication skills, you can explain what went wrong and what you tried without burying the key detail
 * Exposure to VCS, Verdi, low-power VLSI coursework, or basic SDC/UPF familiarity is a plus
 * Experience with synthesis tools, waveform debugging, or customer-facing technical support is a plus

## Description

* Execute Prime Power RTL 2.0 logical flows for customer evaluations and internal projects, including library setup, RTL ingestion, SDC/FSDB correlation, synthesis, compute_power runs, and clock gating efficiency reporting
 * Support customers with routine flow setup, installation troubleshooting, and licensing questions, documenting results and issues for team review and escalation
 * Run RTL power lint checks, summarize findings, and contribute testcase documentation, FAQ entries, and internal knowledge base updates
 * Reproduce customer-reported issues, diagnose routine problems, and escalate complex cases to senior AEs with clear context and supporting data
 * Prepare evaluation collateral and technical summaries using established templates, ensuring accuracy and clarity for both internal teams and customer-facing deliverables
 * Collaborate with sales, field support, and senior applications engineers on assigned accounts, contributing to support cases and evaluation timelines
 * Build working knowledge of Synopsys low-power design tools, RTL power estimation methodologies, and clock gating optimization techniques through hands-on customer and internal work

The Impact You Will Have

 * Enable faster customer evaluations by executing reliable PPRTL flows and delivering clear, accurate technical collateral
 * Reduce escalation time by reproducing and documenting issues with enough detail that senior engineers and R&D can act immediately
 * Improve team efficiency by contributing to internal documentation, FAQs, and knowledge base entries that make recurring problems easier to solve
 * Support customer adoption of Prime Power RTL 2.0 by helping them get flows running correctly the first time, reducing friction during critical evaluation windows
 * Strengthen customer relationships by responding to routine questions quickly and thoroughly, building trust during the early stages of tool engagement
 * Contribute to product quality by surfacing real-world flow issues and testcases that inform R&D priorities and future releases
 * Help grow the team's collective expertise by capturing what you learn in ways that make the next person more effective, * You can take a 200-line Tcl script, run it, hit an error, and figure out whether it is a setup issue, a data issue, or something that needs to escalate, without spinning for hours
 * You write documentation that someone else can actually use, not just notes that make sense to you in the moment
 * You are comfortable saying "I do not know, but I will find out" and then actually finding out, whether that means reading the user guide, asking a senior engineer, or reproducing the issue three different ways
 * You can sit in a customer call, take notes while a design lead describes a power problem, and walk away with enough clarity to start working the issue without needing a second meeting
 * You stay organized when you are juggling three evaluations, two support cases, and a documentation update, and nothing falls through the cracks
 * You care about getting it right, not just getting it done, because you know that a sloppy power estimate can send a design team in the wrong direction for weeks