1. Ask the definition
There are often some vaguely pointed words in the narration of the passers-by, and these words are often encountered in the daily work of the passers-by, and they think the judges know them, but the judges do not understand them for the first time. In particular, some words with relatively broad meanings have different meanings in different contexts, such as the word "architecture", which is defined differently by different people at different times and in different scenarios. Therefore, the judges will ask questions when there are some ambiguous words in the expressions of the advanced candidates, or when there are unclear/ambiguous meanings.
For example, in our promotion, we often say: the service performance has been optimized, and the interface speed is much faster.
Here the judges may ask:
What is the service here?
What does performance mean here?
What does optimization do
How much faster? From how much to how much? How is it quantified?
Words such as service and performance are relatively general. For example, performance may refer to query performance or write performance, and the corresponding optimization schemes for different performances are completely different. Some are optimization of technical points, and some may be of the entire architecture. Adjustment.
Tips for promotion: use precise words to reduce ambiguity
2. Ask the process
A thing can only have a good result if it has a good process, and a good result without a good process cannot be repeated.
Questions about the process are mainly to understand and confirm the role played by the promoted students in the project, the specific work, the role played, and the degree of mastery of the project.
Especially for some students who did not explain clearly some information during the PPT or presentation time, the judges need to complete the project information by asking questions at this time. Questions are often asked along the following dimensions:
2.1 Background reason
Why do you want to do this scheme/system? what is the thinking behind
What is the core pain point to be solved by this project?
Why are you doing this?
What is your role in the project?
How is your personal value reflected during project execution?
2.2 Technical details
How is a certain technical point realized? Tell me about the details?
Why is the XXX module designed this way? Is there a better solution?
Why use XXX cache here? Why use such a cache design? Can it be done without caching?
Why is the business area divided in this way? What was your thinking at that time?
Why use the XXX protocol here? What happens if you switch to the YYY agreement?
2.3 Program Risks
Did you refer to the industry's plans when making the plan? What are the plans, and what are the advantages and disadvantages of the plans?
Why choose the current program?
When evaluating a solution, what dimensions are considered, and why are these dimensions? How are the dimensions weighted?
Is there a comprehensive risk analysis of the current situation? What is the result of the analysis?
If the analyzed risk occurs, how to deal with it?
2.4 Data indicators
Why use XXX indicators? What is the logic behind it?
What is the quantifiable effect data generated by this project? What was the original expectation? How is it achieved?
The goal set at the beginning of the project was 3 times, why here is 3 times instead of 5 times and 10 times, what is the basis?
How are these figures derived?
Why is the boost here 30%? Can it reach 50%? If you want to reach 50%, what do you need to do? Why didn't you do it then?
Tips for promotion: scientific decision-making plan, quantifiable data, repeatable process
3. Ask Difficulty
Different levels have different requirements for difficulty, and the difficulty item can distinguish to a certain extent whether the requirements of a certain level are met.
During the defense process, the judges may ask some difficult questions for the corresponding level. The difficulty here is not limited to a certain technical difficulty, but may be the latest developments in some industries, or a classic strategy/scheme/architecture, or The latest architectures/languages/paradigms etc., such as:
What do you think is the most difficult point in the project? Why is this the hardest?
Can you talk about your views on XXX, which is more popular in the industry now?
What do you think of the hottest XXX in the business right now? Why is it not used in your project?
Tips for promotion: Only when there is difficulty can there be distinction
4. Ask the bigger picture
At a higher level, the overall view of things is a more important item.
The big picture here refers to looking at problems from a macro perspective, analyzing problems, solving problems from a larger perspective, and realizing the overall maximization of technological value, not just limited to one-acre three-point land. Frequently asked questions are as follows:
What are the upstream and downstream of your project? How is the whole link connected?
Did you influence product managers on this project? Which ones, if any? How?
What was your biggest impact/change on the project? How did you think at that time?
Tips for promotion: The overall situation determines the height, and it is under control
5. Ask about methodology
思考和总结是高阶一些的级别需要特别体现的内容，一般会落地成方法论，表示这个项目我这次能做成，下一次还能做成，有自己做事的节奏和方法。比如你讲某个地方的优化使用了缓存，此时需要对于缓存使用有自己的方法论，对于缓存其适用场景，优劣势，原理都尽在掌握，下次遇到类似的问题还可以解决，而且可能还是不同的方案，但是做事的方法和逻辑一样。
从这个项目你学到了什么？你最大的收获是什么？
如果还有 XXX 项目，你会怎样做？
你做 XXX 决定的逻辑框架是什么？
XXX 背后的思考是什么？
晋级提示: 持续的成功才是能力
6. 问业务价值
技术最终还是服务于业务产生价值，而在晋级中如何把在做的东西的业务价值体现出来，也是要着重思考的。
如果你在讲述过程中没有提起或者提得不那么明显或清晰，那么评委可能会就此提问，可能的问题如下：
这个项目的用户是哪些人？他为用户带来了什么？
如何衡量你这个项目的价值？项目价值衡量的维度是否合理？
从公司层面（部门/某个大一些的组织）看，你认为这个项目贡献情况如何？
你当前组织的业务目标是什么？你这个项目是如何服务于这个业务目标的？如果没有这个项目业务目标会怎么样？
晋级提示: 将技术与业务价值和公司（部门）目标关联上
7. 问学习成长
你在 PPT 上有讲架构能力有所欠缺，你打算如何提升这方面的能力？
你有提到持续学习，你将如何持续学习，学习什么，有什么计划，预计会有什么样的收益？
想象一下，一年后的你是怎样的？三年呢？五年呢？
晋级提示: 学习能力是必备能力之一
8. 技术晋级常见问题
以下是两个常见的问题集
8.1 性能优化
做了 XXX 优化，性能提升了很多
为什么要做这个优化？做这个优化的出发点是什么？
这里的性能是指什么？
提升了很多是多少？从多少提升到多少？如何量化的？
性能提升后对用户有什么影响？有什么业务价值？
在系统中还有类似的性能问题吗？有没有系统思考过产生这个问题的原因？
从研发流程或研发制度上有没有可以优化的点来规避这些性能问题？
8.2 信息系统
做了一个系统
为什么要做这个系统？做这个系统的初心是什么？
能解决什么问题，能带来什么效果
能给公司带来什么价值？如何衡量这个价值？
带来的这些价值如何服务于公司级的业务目标？
系统的架构是怎样的？
系统设计的时候有没有参考业界的方案？
当时做方案选型的时候是如何评估的，重点是考察了哪些点？为什么要考察这些点，当时的思考是什么？
你在这个系统过程中扮演的是什么角色？
系统的优势和不足在哪里？
这个系统下一步如何发展
9. 后记
晋级对于我们来说意味着「升职加薪」，意味着我们的能力、知识、技能等得到某种官方的认可。
同时也意味着将来要承担更多的责任，也会被更多的期待。
晋级并不是结束，而是下一个开始。