在线咨询
eetop公众号 创芯大讲堂 创芯人才网
切换到宽版

EETOP 创芯网论坛 (原名:电子顶级开发网)

手机号码,快捷登录

手机号码,快捷登录

找回密码

  登录   注册  

快捷导航
搜帖子
查看: 883|回复: 0

[招聘] 【AMD社招】Silicon Evaluation Lead (SEL)

[复制链接]
发表于 2017-2-10 16:35:47 | 显示全部楼层 |阅读模式

马上注册,结交更多好友,享用更多功能,让你轻松玩转社区。

您需要 登录 才可以下载或查看,没有账号?注册

x
AMD超威半导体招聘Silicon Evaluation Lead (SEL)请有意向者将简历发送到 Maggie1.Zhang@amd.com 以及 Cherry.Zhang@amd.com

Job Location: Austin, TX

Candidate requirements:
The candidate must have a BS or MSEE degree and a minimum of 10 years of

relevant working experience in new product

dvelopment from a design, platform and/
or product engineering discipline. The candidate should have experience both

as a technical lead as well as a project manager. The candidate must also have
a strong understanding of the general silicon engineering process (preferably
CPU or GPU), from concept to tape-out to production. Furthermore the candidate
should have experience with driving a multi-site and multi-disciplined engine
ering program.

The candidate should be a proven leader, be able create and maintain a working
cross functional team and manage in a matrixed environment. A successful cand
idate must have exceptional verbal, as well as written, communication skills.
In addition, the role requires outstanding people management skills to lead, m
otivate, and guide world class engineers.

Additional requirements:
- Solid understanding of financial and management accounting
- Strong analytical skills
- Ability to structure and execute complex analysis, draw insights, and commun
icate summary findings/recommendations to senior management as well as AMD cus
tomers
- Ability to network, build relationships, and drive effective decision-making
across multiple functions and levels within the organization
- Highly organized, able to prioritize, and juggle multiple work streams to ti
ght deadlines

Responsibilities:
- Primary technical interface for SCBU customers
- Execution of product specific hardware Emulation
- Driving the Collaborative Test Approach (CTA)from start through handover-to-
sustaining
- Development of the CTA plans
- Driving preparedness for execution of CTA testing prior to silicon
- Driving execution of CTA testing post silicon to enable product introduction
- Member of the Chief Engineering Council and will inherit Design Director Tea
m representation if design-director rolls-off CEC
- Driving cross-functional (platform, PEO, design, software) engineering coord
ination
- Defining effective forums
- Communication and escalation process
- Supporting Platform-level issue resolution as the CPU/APU expert
- Technical Issue Descriptions (w/SIG) for customer and executive communicatio
ns
- CPU/APU RTM recommendations to CEC and resulting CPU/APU quality and cost

Key deliverables:
- Pre Silicon Emulation execution management
- CTA execution management
- Post A0 tape-out content and timing recommendations
- Technical Issue Description and Resolution
- gate for all customer technical communication


SDL Job Description
General Overview of Role
Pre-silicon:
-        CTA (collaborative test approach) lead – primary design interface for platf
orm validation team/product engineering team and IP design team. Enable knowle
dge transfer of new or changed designs from IP team to platform validation/pro
duct engineering team. This knowledge transfer will be used by the platform va
lidation/product engineering teams to create test plans.
Post-silicon:
-        The silicon debug lead (SDL) directs the debug efforts of design-centric iss
ues observed in silicon.
-        The SDL is the primary contact for such efforts.  His/her focus is on one si
ngle program.
-        Key responsibilities:
o        Work with the AMD silicon debug/validation teams, IP owners, and SOC archite
ct to drive issues to closure.
o        As needed, work with the customer teams and the customer’s SDL counterpart
to drive issues to closure.
o        Draft documentation (as needed) and present that internally, as well as to t
he customer.  For example, detailed results collected in the lab, a proposal f
or a bug workaround, summary of new bug observation, etc.
o        Attend re-occurring customer meetings.  Some are general sync-ups, some are
issue-specific.  These could happen in parallel.  Ideally, the SDL should be h
osting debug sync-up meetings with the customer.

Work Flow & Team Dynamics
-        The silicon evaluation lead (SEL) directs the debug efforts across the full
SOC.  He/she relies on the leads in the different domains (design, platform, p
rocess, etc.) in order to drive SOC silicon activities to closure.
-        The SEL is our front-line interface to the customer and is also focused on o
ne program.
-        The SDL works in tandem with the SEL.  Collaboration model should be worked
out.
-        General work flow:
o        The SDL works closely with the SEL to triage debug efforts and coordinate cu
stomer communication.
o        When a new observation is reported by the customer, the SEL may allocate tha
t to the SDL.
o        When a new observation is reported internally, the SDL will likely be pulled
in by one of the domain leads (e.g. the platform validation lead may ask the
SDL directly to drive a new issue, or at least provide guidance).
o        The SDL will then do whatever necessary to determine root cause and close the issue completely,

or at least from a designerspective (e.g. what looked like a design issue turned out to be a software issue; can hand off to software
lead, but SDL may still need to close with the customer).

Organizational
-        Issues are tracked in JIRA.  Anyone can file the entry, doesn’t have to be
the SDL.  When applicable, a particular issue may also be tracked in the custo
mer database.  Note: not every issue is customer visible.  Certain AMD personn
el (including the SDL) will have access to the customer database.
-        Permissions.  The SDL requires access to the following areas:
o        JIRA
o        IP P4 depots (programming guides, SOC arch spec, fuse matrix, etc.)
o        Customer’s network: bug tracker database (e.g TFS) and shared folder for up
loading docs (e.g. Nermal)
-        Internal Meetings.
o        SECT (silicon evaluation core team).  This is a series of meetings where all
domain leads gather for status review.  Depending on the collaboration model
defined between the SEL and SDL, either one may drive these.
o        PECT (platform evaluation core team).  Sync-ups specifically for platform is
sues.  The SDL attends as needed.
o        Other sync-ups.  Other domain leads will have their own re-occurring sync-ups.  The SDL attends as needed.
o        Issue-specific.  The SDL should schedule meetings as needed to close items
in a timely fashion.
-        Customer Meetings.  The customer will typically drive re-occurring sync-ups.
  In addition, issue-specific sync-ups may be necessary for high priority items.  

These may be driven by AMD or the customer as needed.

Customer Communication
-        Coordinate this with the SEL.  The SEL should always be aware of what’s bei
ng shared with the customer, and typically vets that information beforehand.
-        Not every issue is customer visible.  Care should be taken with what is shar
ed with the customer and when.
-        Legal scanning.  Documentation that will be delivered to the customer (e.g.
IP specifications) should go through the legal scan procedure.  One person is
usually appointed to do this task for the program.
Presentation documentation.  Newly prepared slides should use the AMD slide te
mplates.
您需要登录后才可以回帖 登录 | 注册

本版积分规则

关闭

站长推荐 上一条 /1 下一条

小黑屋| 手机版| 关于我们| 联系我们| 隐私声明| EETOP 创芯网
( 京ICP备:10050787号 京公网安备:11010502037710 )

GMT+8, 2025-7-18 05:43 , Processed in 0.417083 second(s), 8 queries , Gzip On, MemCached On.

eetop公众号 创芯大讲堂 创芯人才网
快速回复 返回顶部 返回列表