脸书Product design vs System design

HR让选product design 还是 system design，感觉pr

您好！
本帖隐藏的内容需要积分高于 188 才可浏览
您当前积分为 0。
使用VIP即刻解锁阅读权限或查看其他获取积分的方式

游客，您好！
本帖隐藏的内容需要积分高于 188 才可浏览
您当前积分为 0。
VIP即刻解锁阅读权限 或 查看其他获取积分的方式
Unlock interview details and practice with AI
Curated Interview Questions from Top Companies

一下两者的优劣吗？过几周就onsite了

我两年前product design 和 system design 都面过，product design 面你有没有product sense，like how to design the UI interface for a product, for both web page and mobile, how the API format looks like when interface needs different data, etc. System design 就是我们一般说的design interview, like tiny URL, how to design a WeChat, more backend thinkings.

马上面了，才意识到这个区别。

我仔细看了面试的要求。其实这个两个类别就是focus在两个不同的方向。比如app dev就是要理解产品UI和API的要求，不需要知道后端是如何存取的。而infr dev就必须了解底层特别是数据的存储优化，还有scalable。市面上的system design的材料，基本上覆盖了这些方面。比如设计API，设计data model，就是product design，设计一个KV store，top K，就是system design。其实两者也是有重合的部分，比如考虑scalability等等。

欢迎大牛补充。

设计twitter设计web crawler就是product design
system design是设计一个kv store之类的

cuiyang36 发表于 2020-5-2 13:20
我两年前product design 和 system design 都面过，product design 面你有没有product sense，like how to  ...

可以这样说吗 product design 和 OOD也有一些相似之处？ 比如parking lot

论坛匿名账号 发表于 2020/05/03 06:43:34
可以这样说吗 product design 和 OOD也有一些相似之处？ 比如parking lot

我觉得OOD是另一套....

cuiyang36 发表于 2020-5-3 07:03
我觉得OOD是另一套....

那复习资料呢？ Grokking the System Design Interview 算不算product design的一个好的复习资料

个人意见，既然是在职跳槽，选和自己之前做的比较接近，自己更熟悉的那个比较好

匿名者 发表于 2020-5-3 10:54
那复习资料呢？ Grokking the System Design Interview 算不算product design的一个好的复习资料

Grokking the System Design Interview肯定是system design的复习资料啊

同求，感觉product design简单一点？

这个HR发的System design和Product design的介绍。想问下如果主要用grokking那本书来准备，选哪个好？
The Systems Design Interview

You'll have a design aspect to your interview which will deal with building a

large-scale distributed system. You may be asked to build a feature for

Facebook. Our engineer will be focusing on your ability  to think through

the design of a complex system, especially with regards to trade-offs around

consistency, availability, and partition tolerance.



1. Possible question

topics Interviewers will focus on

your familiarity with complex products or systems and assess your ability to

arrive at answers in the face of unusual constraints.



You should be familiar with the areas

below—but we’re not looking for you to be an expert in all of them. You should

know enough to weigh design considerations (and understand when to consult an

expert) for:

• Concurrency (threads, deadlock,

starvation, consistency, coherence)

• Caching

• Database

partitioning, replication, sharding, CAP Theorem

• Networking (IPC,

TCP/IP)

• Real-world

performance (relative performance RAM, disk, your network, SSD)

• Availability and

reliability (types of failures, failure units, how failures may manifest,

mitigations, etc.)

• Data storage and data

aggregation

• QPS capacity /

machine estimation (back of the envelope estimates), byte size estimation



2. Example questions

We might ask you to:

• Architect a worldwide video distribution system

• Build Facebook chat

• Design a mobile image search client



The Product Design Interview

1. Possible Question

topics Interviewers will focus on

building a product or API at scale that supports an end user product or

service.

You should be familiar with the areas below—but we’re not looking for you to be an expert in all of

them.

You should know enough

to weigh design considerations (and understand when to consult an expert) for:

• Storage data models

• Scalability

• Design patterns

• Data ownership

• Protocols

• Data formats

• Client-server design

• Designing for long

term vs. complexity

• Accommodating

possible product changes



2. Example Questions

We might ask you to:

• Design a service or product API

• Design a chat service or a feed API

• Design an email server