Share Today, a college student internship surface through, combined with my own experience summed up some of the views and learning methods, hoping to be helpful to everyone.
Let me talk about my own situation, I am a senior this year, a double non-school computer-related professional, college freshman to join the entrepreneurial team of Android developers groups.
Shortly after the start of the Chinese New Year last year, resume, before and after the vote Tencent, Ali, the US group, CVTE these companies, get an internship offer Tencent, Ali and CVTE, and ultimately chose Tencent, can be considered for their first job of brigade draw a satisfactory conclusion.
In March this year from internships into full-time employees.
This article was last year summed up after ten gold nine silver, mainly to share my own for the preparation of the interview season done as well as some experience and thinking in the interview process, because September and October interview quarter of this year has already begun, so Share out, hoping to find some partners practice some help.
First, there are plans to review the system
Major Internet company Golden nine silver ten season interview time about 9 to 10 months, if it is pushed through in the way, then, even in August will begin a telephone interview, which means if you want to get a satisfactory offer, you must before August to do all the work of the review.
I plan to talk about before the next, in order to prepare for this spring trick, I began to prepare in advance for six months review, the review stage is divided into three parts:
-
Learning "they know they will not" knowledge
-
A full range of learning, build their own "knowledge"
- Learning "did not know that he will not" knowledge
1.1 learning "I know they will not" knowledge
In fact, in the development process, there is always something they want to learn but because the project pressure or other reasons, then put his own plan later learned, also known as "do not know their own" knowledge.
E.g:
-
Some of the more common frameworks, such as the client's network request, image loading frame
-
Some common source categories and collections such as ArrayList, LinkedList, HashMap (the interview will be asked)
- The concept clearly feel they can not speak out, such as "memory leaks", "Java Concurrency"
This stage is a stage on their current knowledge of the leak filled, you have to do is to put their things will not be a complete list, and then one by one break.
This stage is best in the form of a blog, learned his "own language" to express, if you can use their understanding of clear and complete say it, and even allow others to understand what you say, that no basic problem.
But if your own mind can not form a clear idea, then, we can only prove that you were not enough understanding of this knowledge.
And now a lot of companies will "write a blog" as a plus point, in fact, a resume does not reflect many things, but if you have a long-term maintenance of the blog, then your blog by the interviewer can more clearly understand you, and insists that in itself is not an easy thing, to be able to adhere to the interviewer who write blog will be more favorable impression.
1.2 full range of learning, build their own "knowledge"
In fact, many people in peacetime learning techniques and daily development process, learn a lot of things, but few people would go to a systematic review in order to build their knowledge, resulting in a lot of knowledge he learned in no way better have contact, and may lead to learn some knowledge did not take long to forget.
That's how we build "knowledge" mean?
Android inside the so-called "knowledge" , I think that mainly includes several parts:
- Java and Anroid basis
- computer network
- operating system
- Design Patterns
- Data Structures and Algorithms
That we need to break these sections gradually, slowly improve our knowledge, this stage is the most time and effort, but stick with it, let us become a more solid foundation, but also to maximize the building our knowledge.
Here I recommend a copy of my own collected data: Android learn, interview documents, organize large video collection
1.3 learning "did not know that he will not" knowledge
This title may make you a bit puzzled, even do not know how the knowledge that he will not learn?
This time the role of face questions came out, "face questions facing the program" is actually a leak filled, a very good way to enhance their own programming foundation.
在做 面试题的时候，你会遇到很多奇奇怪怪的问题，很多都是你「之前没有接触过」或者「有接触过却没有往那方面想」的问题。
刚开始遇到这些面试题确实很让人很不舒服，但是这些面试题也确实能够最大限度地提升我们对知识之间联系的理解以及引发我们对一些具体使用场景的思考。
当然更重要的是我们可以通过刷往年各大互联网公司的面试题，让我们对于公司面试题有一个大致的认识而且也能提前了解到面试官面试时候的一些套路和做法。
二、面试的一些建议和套路
首先，要强调一点，想拿到自己满意的 offer，最重要的就是提升自己的编程能力，特别是计算机方面的基础，这是每轮技术面试都必问的。没有足够的实力，再高的面试技巧也是没用的。
不过，在面试中确实也有很多需要注意的地方，甚至存在一些通用的经验和套路。
掌握一些必要的面试技巧才能在面试官面前最大程度的展示我们自己真正的水平，甚至超常发挥，从而拿到满意的offer。
2.1 寻找自己的兴趣点，并将其培养成自己的瑞士jun刀
在学 Android 的过程中，其实每个人都有着自己跟别人不一样的兴趣点，例如我自己对 「Android 网络」、「图片加载」这两方面的知识就有很大的兴趣。
如果想要在 Android 面试中脱颖而出，拿到让自己满意的 offer，拥有某个「能超过绝大部分人」的技能是非常必要的，也就是所谓的你最出彩的地方。
在这次阿里技术二面的时候，面试官一上来就说：“上一轮的面试官已经问了很多关于项目的东 西了，你给我讲一下你觉得自己在 Android 中学的最好的东西吧。”
当时听到这个问题我心中一阵窃喜，因为之前花了很多的时间和精力在学习「Android 网络」和「图片加载」这两方面，对 于这两方面我还是很有把握的，最终也顺利通过了阿里的技术面试。
上面举的例子就是为了说明拥有某些技术特长的重要性，在面试中很多时候面试官关心的是你会什么，而不是纠结你不会什么。
而且技术的深度也比广度要重要的多，如果你在某方面研究的比 较深，很有自己的心得和体会，甚至连面试官在这方面都没办法问倒你的话，通过这次面试的成功率就会大大增加。
2.2 将所有的知识点写成对应的逐字稿
在日常的 Android 开发和学习过程中，相信很多人会觉得我们学过的东西自己都已经明白了，但是真正在面试官面前，被面试官问到问题的时候却不知道怎么「完整」、「清晰」地表达出来。
针对这个问题，我自己的解决方法是将我们在面试中可能会遇到的所有的知识点「全部」都写成 对应的逐字稿。
这里的逐字稿有三个要点：
- 必须是自己的总结和体会
- 结合你自己的开发和项目经历
- 能够流畅的朗读出来
写逐字稿的目的是让我们在面试官面前能够「完整」、「清晰」地表达出我们对知识的把握和理解，所以必须用「自己的语言」将自己的总结和体会写出来，只有这样我们才能记得更牢。
在写完逐字稿之后，我们可以试着朗读一下，看看能不能流畅的朗读出来，如果中间有一些拗口或别扭的句子，就把它逐渐改进。
在这里，我用「讲讲你对进程和线程的理解」这个问题来详细讲一下，如果我们在事先没有准备好相应的逐字稿的话，我们可能就会直接讲：
线程是 CPU 调度的最小单元，同时线程也是一种有限的资源。而进程相当于线程的“容器”，在PC 和移动设备上指一个程序或者一个应用。一个进程可以包含多个线程。
然后就这么完了，完了，了。20 秒解决问题，接着面试官估计也会回你一句，今天就这么结束吧。
在这里分享一下我自己对于「进程与线程」的部分逐字稿，大家可以参考一下。
进程与线程
按照操作系统中的描述。线程是 CPU 调度的最小单元，同时线程也是一种有限的资源。而进程相当于线程的“容器”，在 PC 和移动设备上指一个程序或者一个应用。一个进程可以包含多个线程。
进程
当一个程序第一次启动的时候，Android 会启动一个 Linux 进程和一个主线程。
默认情况下， 同一应用的所有组件均在相同的进程中运行。如果我们需要控制某个组件所属的进程，则可在 AndroidManifest 文件中执行此操作。
组件运行在哪个进程中，是在 AndroidManifest 文件中进行设置的，activity、service、 receiver 和 provider 均支持 android:process 属性，此属性可以指定该组件应在哪个进程运行。我们可以设置此属性，使每个组件均在各自的进程中运行。
进程的优先级
Android 系统将尽量长时间地保持应用进程，但为了新建进程或运行更重要的进程，最终需要移除旧进程来回收内存。为了确定保留或终止哪些进程，系统会根据进程中正在运行的组件以 及这些组件的状态，将每个进程放入 “重要性层次结构” 中。必要时，系统会首先消除重要性最低的进程，然后是重要性相对较高的进程，以此类推，以回收进程。
重要性层次结构一共有 5 级
1、前台进程 — Foreground process
2、可见进程 — Visible process
3、服务进程 — Service process
4、后台进程 — Background process
5、空进程 — Empty process
线程
线程在 Android 中是一个很重要的概念，从用途上来说，线程分为主线程和子线程，主线程的 作用是「运行四大组件以及处理它们和用户的交互」，而子线程的作用则是「执行耗时任务， 比如网络请求、I/O 操作等」，由于 Android 的特性，如果在主线程中执行耗时操作那么就会 导致程序无法及时地响应。因此耗时操作必须放在子线程中执行。
Android 中的线程形态
除了 Thread 本身以外，在 Android 中可以扮演线程角色的还有很多，比如 AsyncTask 和 IntentService，同时 HandlerThread 也是一种特殊的线程。
尽管 AsyncTask、IntentService 以及 HandlerThread 的「表现形式」都有别于传统的线程，但是它们的本质仍然是传统的线程。
我相信，如果你能像我上面的逐字稿这样，结合 Android 里面的知识点清晰地表达出你对进程和线程的理解的话，面试官肯定会很满意的。
这里附上我自己的逐字稿目录，大家也可以按照这样的分类，来对自己的「知识体系」建立不同的逐字稿。
2.3 遇到不懂的面试题直接回答不懂，但最好能将面试官的思路往我们会的东西带
在面试的时候，切勿不懂装懂。
我们面试的是技术岗位，有几斤几两，面试官问几个问题就知道 了，如果面试官问到的某个知识点，你只是有点印象或者没多少了解的话，直接回答这个知识不是很熟就行了。不然被面试官针对这个知识点追加几个问题的话，分分钟打你脸。
当然，在说对这个知识不是很熟之后，可以试着将面试官的面试思路往我们会的东西带，例如我 在阿里二面的时候，面试官问我有没有用过 B 树，因为我对 B 树不是很熟，所以我当时是这么讲 的：“对于 B 树不是很熟悉，但之前在看 HashMap 源码的时候，有研究过红黑树，对红黑树比较熟。” 然后成功地将面试官的问题转向了我熟悉的红黑树和 HashMap 的源码上面。
2.4 有意识地锻炼自己的沟通和表达能力
If you want to get a satisfactory offer, in addition to its excellent technical strength, with good communication and presentation skills it is also very important.
Even if the strength again strong, well you can not express it in words, but also in vain. Communication and presentation skills take a long time "deliberate practice", and no shortcuts.
In fact, freshman year, my communication and presentation skills are also quite poor, but then he started to slowly understand the importance of this ability, so in many cases. "Deliberate practice" this skill.
And himself later became head of the team, there are many occasions I need to make speeches or conduct some internal share, because of his own and later enjoyed playing "werewolf kill" ability to express it in the past two years has been greatly improved.
2.5 Each interview should be carried out completely re-set, a detailed record of the interview to ask the subject
After each round of interviews, do not rush to relax or rest, to come up with a memo will interview the interviewer asked the question, "all" are documented in detail. And find a quiet place slowly recalled during the interview that they have no links which performance was not very good, or is in need of improvement.
Every interview is a very valuable experience and wealth, in interview after interview must be re-set to find out where our performance is not good enough in the interview, and then targeted for improvements, and collected in the interview process we can not answer the interview questions, have carried out for review, Zhibuding on the next round of interviews is that you do not ask questions round of interviews, but this possibility is quite large, because between the interviewer will also communicate, your interview performance will spread to the hands of the next interviewer.
Third, the summary
Want to get a satisfactory offer, "insisted" it is the most important, put aside the hard work and persistence, all other methodologies are useless.
Any one industry is not easy, the only ongoing "active" efforts to go further. The above is some of my experience and understanding to move the spring interview, hoping to be helpful to everyone.
The end of the sentence
Interview: If you do not interview well-prepared, complete waste of time, it is not responsible for their own!
Quickly went for his interview done enough to prepare it!
Finally, no matter what, no matter what the size of the interview, the interviewer order not to be a child not to do, and only maxed face questions questions do thorough preparation, of course, in addition to the need to own a solid base hit in peacetime so no matter how the interviewer a kind of knowledge in Kill chisel, you can cope with such flow ah ~