You sense the interview is coming to an end, the questions are getting sparse, and it’s difficult to gauge your potential.
This dream job could come to fruition, but there is a weight on you. Sitting across the table in silence, your mind wanders to how all the moisture from your mouth found its way under your arms. At that moment, the silence is broken and your focus is redirected.
“What is your greatest strength?”
You’ve been there — sitting in a job interview as they roll through their list of questions trying to determine if you’re the candidate they seek.
In one way or another, they always question your strength. Sometimes, they outright ask you about it. Other times, it may be tucked under explaining how you overcame a difficult work situation or how your workflow sets you apart.
In response, it can be easy to default to your passion, reliability, consistency, or patience with others. You might be a self-starter or great at keeping yourself motivated. Or maybe you stay calm and composed during high-stress situations.
Those are all commendable traits, but the answer companies are looking for is efficiency.
Regardless of the position — barista, designer, cashier, mid-level management, sales — you need to be efficient. You see, efficiency is a strength that directly impacts the company. If you can master peak performance using minimal resources, you‘re bound to achieve the highest-level output. Or as business translates it, profit.
Now you’re thinking, “Sure, I’m good at my job and even clock in and out on time.” That’s not the efficiency that’s going to set you apart from John in accounting. You need to analyze your tasks, break them down, and reorganize them for optimal production, time, money, and resource usage without being asked.
Here’s an everyday example.You’re cooking a tasty, dependable dinner: spaghetti. Let’s say you start by putting garlic bread in the oven and placing your pasta in boiling water. You begin cooking down your tomato sauce. Then you realize you now have to brown your meat in a separate pan. By the end, your pasta is overcooked, your bread is burnt, and you’ve dirtied more dishes than necessary.
Now, what if we took that simple process, broke down each part, and rearranged it to make it more efficient? Typically, you start by browning the meat. Then add your diced tomatoes and spices to create your sauce. While that’s cooking down, boil your pasta and throw some garlic bread in the oven for the last eight minutes. Voilà, dinner is served. Hot, timely, and with minimal dishes.
Obviously, this is a natural trait for me. Yes, I’m the girl who loads the dishwasher and puts groceries on the checkout belt in a specific way. With that said, it’s a trait that can be learned and easily exercised in your day-to-day. How can you cook dinner faster, organize your fridge better, and get more housework done during your already busy schedule?
Now apply that same concept to your job. How can you design wireframes more effectively, make three lattes in the time it takes Sally to make one, or manage your team to exemplify their individual strengths?
When you prove your efficiency, you can win interviews, become an asset, and confidently ask for raises.
So next time you’re asked what your strength is, respond with efficiency — and show them why.
#self-improvement #startup #programming #business #work
In this article, I share what I think is one of the best tips when it comes to design interviews.
As a junior UX designer, I’ve been asked a few times by my peers: what is the most essential UX interview tip I have?
Well, to this question I have a very simple answer,** just be honest**… well, this might sound like a no brainer, but it seems to me that not many junior designers know about it or want to apply it.
I had the chance to speak with a few designers and I discovered that some tend towards being a little bit insincere when going through interviews for design positions. It’s normal to be intimidated when going through an interview process and you might want to act as if you have more experience than you have to secure the job.
Well, I’m here to suggest that that’s not the right approach. I fact, recruiters know in advance that as a junior designer you won’t have many years worth of experience so instead of being insincere it’s better to show up with an open mindset and being honest.
A mindset of learning and improving is always welcomed and valued in today’s world. Simple answers like “I might not know X because I’ve haven’t had the chance to get at it but I can learn it as I’m an avid Lerner” go a long way with recruiters.
Put yourself on your recruiter’s shoes, would you rather employ someone “that answers to 90% of the requirements’’ but doesn’t show a growth mindset, or would you employ someone “that answers to 70% of the requirements’’ but shows it’s the thirst for learning and improving?
That’s not to say that you’ll show up with no qualifications at all. You still have to have a certain level of expertise. “Don’t be the guy with 30hrs of experience using Sketch and 1hr of prototyping experience calling himself a UX designer”.
Some skills can be rapidly learned with just a little bit of discipline and will so don’t be afraid to answer with a no if you haven’t had experience with certain techniques due to lack of opportunity of doing so, for example. It’s always easier to learn something new than being perceived as untrustworthy because you said you were qualified to do something but you finally weren’t.
keep in mind that being sincere is always the way… not just during job interviews but in life. Anytime you’re being insincere to achieve something, most probably, the lie will end catching you back and having the opposite effect you wanted it to have.
Anyway, I’ll stop with my “life lessons” and I’ll wish you a very successful interview.
Hopefully, this little advice does help you.
#design-interview #job-interview #system-design-interview #job-interview-tips #ux-interview
Disclaimer: this reflects my personal opinions, not those of my employer.
Over the last few years, I have interviewed hundreds of candidates for positions in Software Engineering, Software Engineering Management, Product and Product Marketing Management, Technology Evangelism, and others. It has always bothered me how many people accidentally sabotage themselves, making entirely avoidable mistakes in the early stages of interviews and phone screens, preventing interviewers from getting to know those candidates better, forcing the premature end of the process for them.
I call these mistakes avoidable because not making them is entirely under the interviewee’s control, having nothing to do with aptitude, competence, interviewer having a bad day, or not being fit for a certain position. If you can avoid them (and you can!), then you are already standing out from the crowd, for being able to make your “elevator pitch” in a way that assures interviewers that you’ll be able to handle yourself in a loop with their peers and managers.
Without further ado, this is how you can do better in your job interview:
A short introduction is a short introduction!
Not an invitation for you to read through your resume. So when asked by the interviewer to give “a quick introduction so we can get started”, do just that. Time it to 90 seconds or less. This is about who you are, not (yet) about what you have done. Let’s mock it:
Interviewer: “My name is X, I have been at this company for 5 years, doing X, Y, Z, and prior to this I spent most of my career doing mobile development, now I’m managing this team and am the hiring manager for this position.”
You: “My name is Y, I started in 19xx, when I was born, then went to school, where I learned how to read (…) then I had the opportunity to learn Docker, which I think is the future with Kubernetes, AI, and the Blockchain.”
WRONG. This is what you have done, not who you are.
You: “My name is Y, I’m an Engineer/Marketer/Product person, I’ve graduated from X, been in this market for 5 years, most recently at company Y, and I love being at the intersection of product and engineering, and that’s why I applied for the position”.
Speaking of time
Don’t talk too much, or for too long. If you have been talking for 5-6 minutes without pause, your interviewer is probably already distracted and unable to piece your story together to a coherent whole. Keep answers short and to the point, make pauses, ask if the interviewer has questions, continuously check back to see if the person is still with you. If not, it’s probably time to stop talking.
A couple of extra tips here: if the company interviewing you requires that people take notes about your answers, you can pay attention to when the interviewer has stopped typing. It probably means you are adding nothing to your answer, so change gears. A second cue is that, for video interviews (or live, like in the good ole days), if the person you’re talking to has gone static, not reacting to anything you said, that’s a good sign that you should stop talking.
What’s your motivation?
“Why did you apply for this position?” is considered by many the easiest question in an interview. Well, I have news for you: it isn’t.
There are many ways to answer this question in a way that will immediately raise suspicion in a good interviewer that you don’t know what position you’re applying for, which may be a terminal mistake in a selection process.
Here are some bad answers:
Some good ones:
#interview #interview-tips #interviewing #job-search #tech-jobs #communication #recruiting #hr
As of this writing, the market is tough. We’ve been hit hard with a deadly
pandemic that left thousands of people unemployed. It’s layoffs everywhere and the companies are being conservative when it comes to
Companies are not willing to hire people with no experience or people who they’ve to train.
Your first job in tech is the toughest, you’re competing
with virtually every new college grad and anyone who completed a boot
camp. I know it can be hard to even land an interview, for someone to
give you a chance to talk and demonstrate you could be valuable
Now, the chance of you getting an interview totally depends on how your resume compares to the job description. The more relevant it is to the
skills required, the better your chances of getting an interview.
To build your resume, I’d recommend https://thetechresume.com. It’s a nice read to follow the principles when it comes to building a tech resume.
Over the past few months, I’ve been collecting resources like videos,
websites, and taking notes to prepare for coding interviews.
In that process, I made an 8 weeks study guide curated of important data
structure resources to prepare for tech interviews and honestly this
study guide was helpful to me to know what to study every day and in
following a routine for my job search.
If you’re serious about preparing for a tech interview then 8 weeks is the
minimum to be given to prepare thoroughly for a tech interview. I know
there are few who would cram up pools of content in a week or two. But, I
believe that is not a realistic or sensible approach.
Tech interviews can be intense and most companies expect you to solve problems or go through a data structure topic in detail.
Now, My study guide with resources will eat up the entire blog space. So,
Instead of straight-up dumping down the content all together, I racked
my brains on how to deliver the content in the most effective way
possible to ensure the habit of consistency and dedication stays intact
during the interview preparation process.
In this blog post, I would give you what to cover each week. If you’re
interested to know what resources to refer to when covering each topic then I’d recommend subscribing to the newsletter https://thedailycoding.com in which you’ll receive one email daily about the concept and the resources to practice.
If you believe you can find resources to relevant topics on your own then
here’s how you should plan to cover each topic every week.
#coding-interviews #software-development #job-interview #job-search #coding #latest-tech-stories #coding-interview-tips #coding-job-interview-advice
During my time as a Data Scientist, I had the chance to interview my fair share of candidates for data-related roles. While doing this, I started noticing a pattern: some kinds of (simple) mistakes were overwhelmingly frequent among candidates! In striking disagreement with a famous quote by Tolstoy, it seems to me, “most unhappy mistakes in case studies look alike”.
In my mind, I started picturing the kind of candidate that I would hire in a heartbeat. No, not a Rockstar/Guru/Evangelist with 12 years of professional experience managing Kubernetes clusters and working with Hadoop/Spark, while simultaneously contributing to TensorFlow’s development, obtaining 2 PhDs, and publishing at least 3 Deep Learning papers per year. Nope; I would just instantly be struck by a person who at least does not make the kind of mistakes I am about to describe… And I can imagine the same happening in other companies, with other interviewers.
Although this is a personal and quite opinionated list, I hope these few tips and tricks can be of some help to people at the start of their data science career! I am putting here only the more DS-related things that came to my mind, but of course writing Pythonic, readable, and expressive code is also something that will please immensely whomever is interviewing you!
#data-science #job-interview-tips #job-interview-preparation #job-interview
Android Interview Questions and Answers from Beginner to Advanced level
DataFlair is committed to provide you all the resources to make you an android professional. We started with android tutorials along with practicals, then we published Real-time android projects along with source code. Now, we come up with frequently asked android interview questions, which will help you in showing expertise in your next interview.
Android – one of the hottest technologies, which is having a bright future. Get ready to crack your next interview with the following android interview questions. These interview questions start with basic and cover deep concepts along with advanced topics.
1. What is Android?
Android is an open-source mobile operating system that is based on the modified versions of Linux kernel. Though it was mainly designed for smartphones, now it is being used for Tablets, Televisions, Smartwatches, and other Android wearables.
2. Who is the inventor of Android Technology?
The inventors of Android Technology are- Andry Rubin, Nick Sears, and Rich Miner.
3. What is the latest version of Android?
The latest version of Android is Android 10.0, known as Android Q. The upcoming major Android release is Android 11, which is the 18th version of Android. [Note: Keep checking the versions, it is as of June 2020.]
4. How many Android versions can you recall right now?
Till now, there are 17 versions of Android, which have their names in alphabetical order. The 18th version of Android is also going to come later this year. The versions of Android are here:
5. Explain the Android Architecture with its components.
This is a popular android developer interview question
Android Architecture consists of 5 components that are-
a. Linux Kernel: It is the foundation of the Android Architecture that resides at the lowest level. It provides the level of abstraction for hardware devices and upper layer components. Linux Kernel also provides various important hardware drivers that act as software interfaces for hardwares like camera, bluetooth, etc.
b. Native Libraries: These are the libraries for Android that are written in C/C++. These libraries are useful to build many core services like ART and HAL. It provides support for core features.
c. Android Runtime: It is an Android Runtime Environment. Android Operating System uses it during the execution of the app. It performs the translation of the application bytecode into the native instructions. The runtime environment of the device then executes these native instructions.
d. Application Framework: Application Framework provides many java classes and interfaces for app development. And it also provides various high-level services. This complete Application framework makes use of Java.
e. Applications: This is the topmost layer of Android Architecture. It provides applications for the end-user, so they can use the android device and compute the tasks.
6. What are the services that the Application framework provides?
The Android application framework has the following key services-
a. Activity Manager: It uses testing and debugging methods.
b. Content provider: It provides the data from application to other layers.
c. Resource Manager: This provides users access to resources.
d. Notification Manager: This gives notification to the users regarding actions taking place in the background.
e. View System: It is the base class for widgets, and it is also responsible for event handling.
7. What are the important features of Linux Kernel?
The important features of the Linux Kernel are as follows:
a. Power Management: Linux Kernel does power management to enhance and improve the battery life of the device.
b. Memory Management: It is useful for the maximum utilization of the available memory of the device.
c. Device Management: It includes managing all the hardware device drivers. It maximizes the utilization of the available resources.
d. Security: It ensures that no application has any such permission that it affects any other application in order to maintain security.
e. Multi-tasking: Multi-tasking provides the users the ease of doing multiple tasks at the same time.
8. What are the building blocks of an Android Application?
This is a popular android interview question for freshers.
The main components of any Android application are- Activity, Services, Content Provider, and Broadcast Receiver. You can understand them as follows:
a. Activity- It is a class that acts as the entry point representing a single screen to the user. It is like a window to show the user interface.
b. Services- Services are the longest-running component that runs in the background.
c. Content Provider- The content provider is an essential component that allows apps to share data between themselves.
d. Broadcast receivers- Broadcast receiver is another most crucial application component. It helps the apps to receive and respond to broadcast messages from the system or some other application.
9. What are the important components of Android Application?
The Components of Android application are listed below:
10. What are the widgets?
Widgets are the variations of Broadcast receivers. They are an important part of home screen customization. They often display some data and also allow users to perform actions on them. Mostly they display the app icon on the screen.
11. Can you name some types of widgets?
Mentioned below are the types of widgets-
a. Informative Widgets: These widgets show some important information. Like, the clock widget or a weather widget.
b. Collective Widgets: They are the collection of some types of elements. For example, a music widget that lets us change, skip, or forward the song.
c. Control Widgets: These widgets help us control the actions within the application through it. Like an email widget that helps check the recent mails.
d. Hybrid Widgets: Hybrid widgets are those that consist of at least two or more types of widgets.
12. What are Intents?
Intents are an important part of Android Applications. They enable communication between components of the same application as well as separate applications. The Intent signals the Android system about a certain event that has occurred.
13. Explain the types of intents briefly?
Intent is of three types that are-
a. Implicit Intents: Implicit intents are those in which there is no description of the component name but only the action.
b. Explicit Intents: In explicit intents, the target component is present by declaring the name of the component.
c. Pending Intents: These are those intents that act as a shield over the Intent objects. It covers the intent objects and grants permission to the external app components to access them.
14. What is a View?
A view is an important building block that helps in designing the user interface of the application. It can be a rectangular box or a circular shape, for example, Text View, Edit Text, Buttons, etc. Views occupy a certain area of the screen, and it is also responsible for event handling. A view is the superclass of all the graphical user interface components.
15. What do you understand by View Group?
It is the subclass of the ViewClass. It gives an invisible container to hold layouts or views. You can understand view groups as special views that are capable of holding other views, that are Child View.
16. What do you understand about Shared Preferences?
It is a simple mechanism for data storage in Android. In this, there is no need to create files, and using APIs, it stores the data in XML files. It stores the data in the pair of key-values. SharedPreferences class lets the user save the values and retrieve them when required. Using SharedPreferences we can save primitive data like- boolean, float, integer, string and long.
17. What is a Notification?
A notification is just like a message that shows up outside the Application UI to provide reminders to the users. They remind the user about a message received, or some other timely information from the app.
18. Give names of Notification types.
There are three types of notifications namely-
a. Toast Notification- This notification is the one that fades away sometime after it pops up.
b. Status Notification- This notification stays till the user takes some action on it.
c. Dialog Notification- This notification is the result of an Active Activity.
19. What are fragments?
A fragment is a part of the complete user interface. These are present in Activity, and an activity can have one or more fragments at the same time. We can reuse a fragment in multiple activities as well.
20. What are the types of fragments?
There are three types of fragments that are: Single Fragment, List Fragment, Fragment Transactions.
21. What are Layout XML files?
Layout XML files contain the structure for the user interface of the application. The XML file also contains various different layouts and views, and they also specify various GUI components that are there in Activity or fragments.
22. What are Resources in Android Application?
The resources in Android Apps defines images, texts, strings, colors, etc. Everything in resources directory is referenced in the source code of the app so that we can use them.
23. Can you develop Android Apps with languages other than Java? If so, name some.
Yes, there are many languages that we can work with, for the development of Android Applications. To name some, I would say Java, Python, C, C++, Kotlin, C#, Corona/LUA.
24. What are the states of the Activity Lifecycle?
Activity lifecycle has the following four stages-
a. Running State: As soon as the activity starts, it is the first state.
b. Paused State: When some other activity starts without closing the previous one, the running activity turns into the Paused state.
c. Resume State: When the activity opens again after being in pause state, it comes into the Resume State.
d. Stopped State: When the user closes the application or stops using it, the activity goes to the Stopped state.
25. What are some methods of Activity?
The methods of Activity are as follows:
26. How can you launch an activity in Android?
We launch an activity using Intents. For this we need to use intent as follows:
27. What is the service lifecycle?
There are two states of a service that are-
a. Started State: This is when the service starts its execution. A Services come in start state only through the startService() method.
b. Bounded State: A service is in the bounded state when it calls the method bindService().
28. What are some methods of Services?
The methods of service are as follows-
29. What are the types of Broadcast?
Broadcasts are of two types that are-
a. Ordered Broadcast: Ordered broadcasts are Synchronous and work in a proper order. It decides the order by using the priority assigned to the broadcasts.
b. Normal Broadcast: These are asynchronous and unordered. They are more efficient as they run unorderly and all at once. But, they lack full utilization of the results.
30. What are useful impotent folders in Android?
The impotent folders in an Android application are-
31. What are the important files for Android Application when working on Android Studio?
This is an important android studio interview question
There are following three files that we need to work on for an application to work-
a. The AndroidManifest.xml file: It has all the information about the application.
b. The MainActivity.java file: It is the app file that actually gets converted to the dalvik executable and runs the application. It is written in java.
c. The Activity_main.xml file: It is the layout file that is available in the res/layout directory. It is another mostly used file while developing the application.
32. Which database do you use for Android Application development?
The database that we use for Android Applications is SQLite. It is because SQLite is lightweight and specially developed for Android Apps. SQLite works the same way as SQL using the same commands.
33. Tell us some features of Android OS.
The best features of Android include-
34. Why did you learn Android development?
Learning Android Studio is a good idea because of the following-
35. What are the different ways of storage supported in Android?
The various storage ways supported in Android are as follows:
36. What are layouts?
Layout is nothing but arrangements of elements on the device screen. These elements can be images, tests, videos, anything. They basically define the structure of the Android user interface to make it user friendly.
37. How many layout types are there?
The type of layouts used in Android Apps are as follows:
38. What is an APK?
An APK stands for Android Package that is a file format of Android Applications. Android OS uses this package for the distribution and installation of the Android Application.
39. What is an Android Manifest file?
The manifest file describes all the essential information about the project application for build tools, Android operating system, and google play. This file is a must for every Android project that we develop, and it is present in the root of the project source set.
#android tutorials #android basic interview questions #android basic questions #android developer interview questions #android interview question and answer #android interview questions #android interview questions for experienced #android interview questions for fresher