[bssd] DIY EB1A NSC Concurrent PP 12天批准# Immigration - 落地生根
m*p
1 楼
准备去onsite, 收到HR的email, 讲的是onsite的大体流程，其中一段是Architecture:
Here is what you can expect during our onsite interview:
Coding (2)
...
Architecture (1)
There will be one interview that focuses on architecture. These interviews
focus on systems – think distributed systems and APIs – very focused on
building/implementing a structure/product. One example of a question: How
would you build a chat system that handles millions of concurrently
connected users? Be sure to be very thorough in your explanation, we are
generally looking for a boxes and arrows diagram on the whiteboard.
A couple of things to focus on in this interview:
---communication is key, you will be steering the conversation and it will
be up
to you to understand the problem and ask clarifying questions
---our engineers will be focusing on your familiarity with complex systems.
Some topics you should be familiar with:
---Concurrency (threads, deadlock, starvation, consistency, coherence)
---Networking (IPC, TCP/IP)
---Abstraction (understanding how OS, filesystem, and database works)
---Real---world performance (relative performance RAM, disk, your network,
SSD)
---Availability and Reliability (durability, understanding how things can
fail)
---Data storage (RAM vs. durable storage, compression, byte sizes)
---CAP Theorem
---byte math
Note that we're not looking for you to be an expert in ALL of these, but you
should know enough of them to weigh design considerations and know
when to consult an expert
For practice:
---work with a fellow engineer on mock design sessions
---dig into the implementation and performance of an open source system,
understand things like how the system stores data on disk and how it
compacts data
---be familiar with how databases and operating systems work
---practice on a whiteboard
Conversation/Coding (1)
...
Lunch
...
真要考这么难我秒跪了，我是不是应该延后几个月onsite？
Here is what you can expect during our onsite interview:
Coding (2)
...
Architecture (1)
There will be one interview that focuses on architecture. These interviews
focus on systems – think distributed systems and APIs – very focused on
building/implementing a structure/product. One example of a question: How
would you build a chat system that handles millions of concurrently
connected users? Be sure to be very thorough in your explanation, we are
generally looking for a boxes and arrows diagram on the whiteboard.
A couple of things to focus on in this interview:
---communication is key, you will be steering the conversation and it will
be up
to you to understand the problem and ask clarifying questions
---our engineers will be focusing on your familiarity with complex systems.
Some topics you should be familiar with:
---Concurrency (threads, deadlock, starvation, consistency, coherence)
---Networking (IPC, TCP/IP)
---Abstraction (understanding how OS, filesystem, and database works)
---Real---world performance (relative performance RAM, disk, your network,
SSD)
---Availability and Reliability (durability, understanding how things can
fail)
---Data storage (RAM vs. durable storage, compression, byte sizes)
---CAP Theorem
---byte math
Note that we're not looking for you to be an expert in ALL of these, but you
should know enough of them to weigh design considerations and know
when to consult an expert
For practice:
---work with a fellow engineer on mock design sessions
---dig into the implementation and performance of an open source system,
understand things like how the system stores data on disk and how it
compacts data
---be familiar with how databases and operating systems work
---practice on a whiteboard
Conversation/Coding (1)
...
Lunch
...
真要考这么难我秒跪了，我是不是应该延后几个月onsite？
