foreword
When interviewing programmers, I often hear the interviewer say some clichés, such as "Today's interview is over here, go back and wait for the notification", "Do you have any questions to ask me", "If this question does not Do it, then we can change one too."
Today we are going to talk about a sentence that most interviewers will say "Do you have any questions?"
This is an old-fashioned question. I have gone through many interviews before, and I have given many different answers to this question. Of course, I have also referred to some suggestions from other people. I have summarized several methods of answering here, just for your reference. .
1. No more
This sounds like an unbelievable answer, but it is actually feasible, because you have completed the necessary communication and communication during the interview process just now, and the interviewer has basically understood your situation, so out of politeness, I propose this Questions, giving you a chance to take the initiative to ask, is actually out of respect for the interviewer.
If you can understand this point, it is a good ending to end the interview by saying "no problem" directly and politely. After all, every interview is quite tiring, and it is a relief to end it.
2. Ask what you really want to ask
When I was participating in the intern interview, whenever the interviewer said this to me, I would really grab the interviewer and keep asking questions, because for me, it is really necessary to get to know me well What does the interviewing department do, what is the technology stack like, and I also need to know whether there is a possibility of becoming a full-time trainee.
Since the interviewer gives you a chance to ask questions, take this opportunity to clear up your doubts. This habit continued until I participated in campus recruitment.
Formal work is of course more important than internship work. I can’t wait to learn more about the department, technology stack, etc. from the interviewer, so as to better evaluate whether I am suitable for this department. I would like some information to help you in your career Development is also important.
When the interviewer hears you asking this kind of question, he will also answer you enthusiastically, and he will also be very satisfied with this thirst for knowledge. After all, you want to know his department, what he does, and want to join them , the interviewer can receive what you want to convey to him.
In addition, after knowing this information, you can learn more about the department’s information and learn some related technology stacks in advance. If you really want to join this company in the future, this will also be very helpful to you of.
3. Don’t ask for sensitive information
Asking what you really want to ask does not mean that you can ask questions without a bottom line. For interviewers, some questions are relatively taboo. Let's look at a few negative examples.
**Don’t ask about salary:** It’s not advisable to ask about salary directly. If you are participating in a technical interview, don’t ask about salary. People will think you are unprofessional and focus on money. If it is an HR interview, you can also ask more implicitly "what is your company's salary structure?"
**Do not ask about personal matters:**Some interviewers are more casual and want to get first-hand information directly from the interviewer, such as asking the interviewer "how much is a month's salary", "do you usually work overtime seriously", "do you think this company How is the company?" This is like a person you just met asking about your family affairs, which will make people very disgusted.
**Don’t ask about things that have nothing to do with the position:** Some interviewers may jump out of the interview position and start asking some unrealistic questions such as "what is the future company strategy?" How to" This kind of fake and empty questions should also be avoided. I believe that there should be fewer people who make this mistake, after all, we programmers are more practical.
Summarize:
The reason why the interviewer wants to give the interviewer a chance to ask questions is actually because the interviewer has the right to know the basic information of the department interviewing him, job information, technology he may use in the future, and the business he is responsible for.
Nowadays, it is not difficult for you to understand a company, but it is getting more and more difficult to understand a department, a business line, or even a group under the business line in the company, because there are too many departments in large companies Moreover, the information is not completely transparent. It is difficult for you to know where you will work in the future based on "Maimai" and the opinions of some communities.
Maybe when the interviewer is waiting for you to ask questions, this is your last chance to understand it.
Finally, I will share a copy of the latest 2023 Android intermediate and advanced interview questions, hoping to help you.
Due to the large content of the article and the limited space, the information has been organized into PDF documents. If you need to know the complete document for Android intermediate and advanced interviews, you can add WeChat to get it for free! (Promise: 100% free )
1. Android interview related
1.Activity
● Talk about the Activity life cycle
● What methods will be called when Activity A starts another Activity B? What if B is a transparent theme or a DialogActivity
● Tell me about the function of the onSaveInstanceState() method? When will it be called?
● Activity startup process
● onSaveInstanceState(), onRestoreInstanceState drop timing
● activity startup mode and usage scenarios
● Activity A jumps to Activity B, and then presses the return key, the order of life cycle execution
● Switch between horizontal and vertical screens, press the home button, press the back button, lock and unlock the screen, jump to the transparent Activity interface, start an Activity whose theme is Dialog, and the life cycle of the Activity when the Dialog pops up
● The difference between onStart and onResume, onPause and onStop
● Is there a limit to the size of Intent, the method of transferring data between activities? If the amount of data transferred is too large, what are the solutions?
● When will the Activity's onNewIntent() method be executed?
● Explicit start and implicit start
● scheme usage scenarios, protocol format, how to use
● Four scenarios of ANR
● The difference between onCreate and onRestoreInstance when restoring data
● The way to transfer data between activty
● Ways to start Activities across Apps, precautions
● What is the Activity task stack
● What are the flags commonly used by activities?
● How the data of the Activity is saved, and how to restore the saved data after the process is killed
2.Service
● The life cycle of service, the difference between the two startup methods
● What are the two ways to start the Service? where is the difference
● How to ensure that the Service is not killed?
● How to communicate between Service and Activity
● What is IntentService, the principle of IntentService, application scenarios and its difference from Service
● How many return values does the onStartCommand method of Service have? What do they mean?
● The mixed life cycle of bindService and startService and how to close it
● Which system services have you used?
● Do you know about ActivityManagerService? what role does it play
3.BroadcastReceiver
● Classification and usage scenarios of broadcasting
● The difference between the two registration methods of broadcasting
● The principle of broadcast sending and receiving
● The difference between local broadcast and global broadcast
4.ContentProvider
● What is ContentProvider and its use
● ContentProvider permission management
● The relationship between ContentProvider, ContentResolver, and ContentObserver
● Implementation Principle of ContentProvider
● Advantages of ContentProvider
● What are Uri?
5.Handler
● The implementation principle of Handler
● Can a new Handler be directly created in the sub-thread? Why can the main thread’s Looper call the loop method for the first time? When and which class
● Causes of memory leaks caused by Handler and their solutions
● A thread can have several Handlers, several Loopers, and several MessageQueue objects
● What are the differences between the methods of creating Message objects?
● How does Message.obtain() maintain the Handler of the message pool? What are the methods for sending messages?
● Differences and application scenarios between post and sendMessage of Handler
● What happens to the message queue after the handler postDealy, assuming postDelay 10s first, then postDelay 1s, how to deal with these two messages
● What is the data structure of MessageQueue
● How does the Handler make a thread correspond to a Looper, and how to ensure that there is only one MessageQueue ThreadLocal in the Handler mechanism?