#interview questions. learn java through examples

[sohlidarity]

Internship tips

Some tips for recruitment season for Computer science students based on my experience.

Note: This is mostly for 1st and 2nd year students. Here is what I did to get my first internship offer.

1. Focus on your resume.

Before you even start applying to jobs, make sure that your resume has the following:

uses a basic template that is easily readable by the ATS. example

includes a Projects section!! this one is very important. You can include projects that you did in your class, in any CS clubs or something that you did on your own.

(optional but good to have) any job experience even if it is not related to cs or engineering + any clubs you are part of or hold leadership positions in.

Note: Think of your resume as a questionnaire. The interviewers will interview you based on what you put on your resume. The more technical projects and experience you showcase, the more you can stand out.

2. Work on some side projects if you don’t have any yet. You can look up tutorials on YouTube on how to make a website (both front end + backend). I recommend code academy, udemy, coursera or edx courses. Learn flutter+dart to make a mobile app. Be able to use java, python and c++ (be confident in at least one language).

3. Start applying to jobs! Cover letters are mostly optional so don’t worry about them too much. 

attend your college career fair and talk to recruiters. Ask for their email so you can contact them and send them a thank you message + stay connected. Getting in touch with recruiters is key.

here is a github database of multiple internships to appy for.

reach out to recruiters and alumni on linkedin. try to get referrals.

Note: even if you don’t think you are qualified for an internship, APPLY ANYWAY.

Now you wait for the interviews. Getting an interview is the hardest part :( BUT YOU GOT THIS. Keep applying and networking.

4. Most internships don’t really ask for a technical interview if you are a 1st or 2nd year student. But leetcode is the best place to prepare for technical interviews. Here are some problems to get you started. But besides that make sure you can clearly explain the projects on your resume and maybe even walk the interviewer through your thought process and any issues you had!

5. Time for behavioral interview which is the last final step. Here are some commonly asked interview questions. In a word document try to come up with a situation where you faced the issues described in these questions and then write them down. Also write down how you solved the issues. This is how you will prepare for the interview. Try to memorize the scenarios but also make sure that you speak naturally during the interview lol. They don’t need to know you memorized it. Smile and be pleasant during the interview! Everyone loves happy people!! Always project yourself in a positive light. 

Example: Tell us about a time you missed a deadline.

Answer: taken from this website

situation/task -  I was once given a deadline to produce an article for a client on a short turnaround time. I believed I could handle the article in addition to the workload I already had, but I miscalculated how long it would take me to write it. The morning the article was due, I realized I would not make it in time and contacted my boss to explain the situation.

action -  I apologized, explained what happened and asked for an extension, which he granted. 

result - I learned that I need to be honest with myself about the workload I can handle each day. I also learned that when accepting assignments, I need to include a time buffer to ensure that even if unforeseen events arise, I am able to meet my deadlines.

Note: If they ask for a weakness, mention something that is not your job related. For example, you can say something about creativity being your weakness when you are applying for a technical role. Make sure that you also mention what you are doing in order to improve the skill you said you are weak in. In this case, it could be taking a creative writing class etc.

6. Always have questions to ask at the end of the interview. Ask about any doubts you may have regarding the work. Ask if there is any specific technology you need to learn in advance. Ask how the day to day work life would look like. Ask how the company has been dealing with COVID. Ask them to describe a successful intern etc.

7. Send a thank you email to the recruiter and the interviewers! Don’t forget this one!

Lastly, keep working hard and be open to constructive criticism. Have other people look over your resume. Do NOT compare yourself with others. You are competing with YOURSELF during the recruitment process. Believe in yourself and all the work you have put in so far. Accept the fact that the recruitment process is stressful and find healthy ways to cope with stress. Most importantly, be nice to others and do not put other people down during this time :) You got this!! I believe in you. It is never too late to apply. There are internships all year round so do not worry :)

[anth-seeing2019]

Art Education in Museums

Luke Kindle

My interest in this form of seeing, that of the art museum tour guide- not quite a historian, not quite a layman- came from a presentation given to an art history class of mine by a worker in the Learning and Interpretation Department of the Cincinnati Art Museum. As someone who studies art and art history academically, it was interesting to hear from someone whose career was centered around the accessibility of a public art collection to a larger audience, rather than in-depth research and paper-writing. The bulk of my observation for this project was done by attending the Cincinnati Art Museum’s Public Tours, which are held several times a month and are free to the public. The docents began the tours by introducing themselves and asking visitors about their background, their level of familiarity with the collection, and in the case of the tour of the CAM’s Cincinnati Wing, whether the visitor was a Cincinnati native. During the tours, the docents establish a narrative for the visitors that they string between different items in the collection, be they paintings, pieces of furniture, or everyday objects from times past. The docents ask open ended questions throughout- “what do we think this might have been used for?” or “what does this look like to you?” rather than “who was Claude Monet?” The questions and discussion seemed to be as much about forming an educational narrative as they were about establishing a personal connection to the art. Before or after the tours, I was able to speak briefly with the docents and ask a few questions about the (mostly volunteer) role. They came from a range of backgrounds, many having little to no academic training in art or art history; one docent I spoke to was a retiree who had worked in finance and later came to doing tours out of a personal interest in learning about art history. The docents, who all received similar training sessions at the CAM, described the job as one in which they often met visitors halfway and learned bits and pieces from visitors to incorporate into further tours.  After these short interviews, it seemed as though the museum docent was indeed at a position somewhat between having a expert or professional perspective in the galleries and having a more vernacular, commonplace one. They understand and categorize the museum’s collection through narratives they can explain to visitors. It occurred to me during some of these tours that Karen Strassler’s discussions of ethnography of photography in Java had some similarities to the way docents organized information. Just as the she described the history of the picture-taking practice in Java and considerations of genres, social functions, political functions, and of imagery, the tour guides explained similar aspects of art with their discussion of the pieces in the CAM’s collection. I later returned to the representative of the CAM’s Learning and Interpretation Department mentioned earlier and was able to ask more pointed questions about the discursive practices in education at the museum and reify my own observations from the tours. Her department, she explained, was concerned with the accessibility of the institution. Instead of large research or curatorial projects, their programs’ aim would be to try to make the collection appeal to the everyday person, young children, or to people with disabilities. 

To discuss my interview in relation to Charles Goodwin’s writing on professional vision, it might be useful to use another, perhaps more familiar, viewpoint as a foil- that of a museum curator and art historian. In terms of Goodwin’s coding schemes, the ways one might break down and classify information, historians and museum educators alike may categorize art based on region, style, or movement. They differ in terms of what they pull from these categorizations. For historians, a work has more or less one relevant set of information, consisting of date, materials, artist, historical provenance context, formal and iconographical aspects, etc., whereas the educator is interested in how the work can appeal to a given audience. Museum educators can separate the museum's collection into distinct narratives they can tell to their audience. Within coded schemes of information, Goodwin suggests that each type of professional vision has a method by which it separates out, highlights, relevant information. For educators, the museum's public tours are for precisely this- a way to point out parts of art that are narratively, iconographically, or materially significant to their audience. This differs, for example, from one form of information consolidation curators use- the museum catalog, in which all of the relevant data of the work is placed without comment or extrapolation. The third significant aspect of professional vision Goodwin discusses deals with is the material or graphical representations, or nonverbal ways information is communicated. For the museum educator, there are many parts of the institution that act in this way: museum maps, wall labels and diagrams, interactive installations- in one gallery there was a recreation of a work in puzzle format. These all suggest ways for their visitors to grow closer to the museum and its collection. It seems that the "professional" vision of a tour guide or museum educator is one that seeks out relatable and accessible details in works of art. This form of seeing is instrumental in their effort to, in essence, break down the discursive barrier between those who study, collect, and preserve works of art in an institution, and those who visit the institution. In closing out our conversation, the CAM Learning specialist I spoke to left me with this: When visitors are on their own in the museum, I often hear them trying to figure out the artwork by reading labels.  As an educator, of course the label is important, but it’s not the full story. Part of the story of a work of art is about how the viewer is able to interpret it without information.  That I think is a difference between how most people visit museums and how I personally visit museums; I don’t read the label until I’ve spent time looking and talking about the work of art.

[curiosityandcode]

I got interviewed for a entry level software dev job and i completely failed it. I’m so embarrassed and disappointed. Like i barely answered any of the technical questions correctly. I didnt even know what a delegate was. Idk how to get over this failure and get back on my feet. Cuz i feel like if i dont even know the basics, whats the point of applying.. i’m such an idiot

While searching for an internship last year, I went to multiple interviews. I had an impressive resume - side projects, volunteer work, high GPA, previous work experience. Basically any job I applied to, I got asked in for an interview. I also didn’t getting any offers for the first 3 months.

Does this make me stupid? Was my resume a lie? Was I a failure? It sure felt like it at the time. But the truth was I wasn’t good at interviewing. For example:

At my first white board interview I got a very simple anagram questions. I spent half an hour solving it because I kept doubting my self and my approach. I didn’t get the job. 

At another interview I had a take home assignment  and my solution didn’t compile without errors and was more complicated then it needed to be. I didn’t get the job. 

At another interview, I got asked questions about trees where the edge case had to be spoon fed to me cause I couldn’t think of it on my own. I was asked back for a second interview but still didn’t get the job. 

At another interview I struggled to answer the question and I got all the java questions wrong. But at this point, I was getting a bit better at interviews so I illustrated my thought process better and was honest about what facts I knew confidently and which I was a bit uncertain about. I was nervous the entire time since my interviewer never once smiled at me. I got a job offer but it was a month later (I’m pretty sure that I was not their first choice).

I was devastated. My friend had managed to get an job offer on her first interview and it was at one the companies that rejected me.  What good was my resume if I was a terrible at coding?

At this point, I applied for a position for a company that I didn’t find that interesting (it was fintech) but I decided to apply anyway. I went to the interview and I talked about my side projects a bit. My interviewers were nice and asked me some questions about what I was interested in. I answered, told some jokes, they laughed. I asked some questions, they answered. We laughed. I did an technical question - I made some mistakes but I explained my process. We talked some more, we laughed a bit. I left that interview thinking that the people who interviewed me were great but I had no expectations for an offer. That night I got an offer. The next day I got that other job offer I mentioned before. I took the fintech offer - I wanted to work with people who I could laugh with.

I’m 8 months into my internship. Remember how I wasn’t interested in the company? Well, everyday I love coming to work. I work with people who help me become a better coder. I get so many opportunities to work on projects vital to the business. I’ve met so many cool and interesting people. These are the things I’ll mention about on social media - not all the struggle that came before. (I also don’t post about my failures at work - like when I break something in production, or code reviews with a million changes.) People tend to only post their success - but don’t think that means they have never failed.

So, how did I get to the point where I could get 2 job offers? Well, I tried to improve after each interview by reflecting on what I did wrong and improving on these skills so I could do better next time.

For me, the big thing was that I stopped trying to get the right answer the first time.  Normally, I would sit silently and try to come up with the correct answer really fast. So I started practicing walking the interviewers through my thought process - I would point out things I knew were wrong or edge cases that I was going to ignore for a moment while I figured something else out. If I didn’t know something, I would say that but then also proceed to give my best educated guess.

Before each interview I also reviewed a list of my experiences and what I learned from them. That way, they were fresh in my mind and I could bring them up while answering questions about my skills, strengths, weaknesses etc.

I reviewed my data structure knowledge and did practice leet code questions so that I could get better at technical questions.

Basically, I built my skills to be better at technical interviews. It was hard work but at least I got a job in the end. And you know what? Even with these tips you can still fail at an interview. The point is that you have to pick yourself up and try to do better next time.

Anyway, the point of this terribly long answer is that “yes failure sucks but everyone fails. Don’t be too hard on yourself.”

(Oh, and that great resume I mentioned at the beginning? I got that through six years of learning to program which had its many failures along the way. Failures that I definitely didn’t put on the resume. )

[rminfotech-blog]

Hadoop Big data Training at RM Infotech Laxmi Nagar Delhi NCR

History:

In 2006, the hadoop project was founded by Doug Cutting, It is an open source implementations of internal systems which is now being used to manage and process massive data(s) volumes. In short,

With Hadoop , a large amount of data of all varieties is continually stored and added multiple processing and analytics frameworks rather than moving the data(s) because moving data is typical and very expensive.

What are the career prospects in Hadoop?

Do you know that in next 3 years more than half of the data in this world will move to Hadoop? No wonder McKinsey Global Institute estimates shortage of 1.7 million Big Data professionals over next 3 years.

Hadoop Market is expected to reach $99.31B by 2022 at a CAGR of 42.1% -Forbes

Average Salary of Big Data Hadoop Developers is $135k (Indeed.com salary data)

According to experts –  India alone will face a shortage of close to 2 Lac Data Scientists. Experts predict, a significant gap in job openings and professionals with expertise in big data skills. Thus, this is the right time for IT professionals to make the most of this opportunity by sharpening their big data skill set.

Who should take this course?

This course is designed for anyone who:-

wants to get into a career in Big Data

wants to analyse large amounts of unstructured data

wants to architect a big data project using Hadoop and its eco system components

Why from RM Infotech

100% Practical and Job Oriented

Experienced Training having 8+ yrs of Industry Expertise in Big Data.

Learn how to analyze large amounts of data to bring out insights

Relevant examples and cases make the learning more effective and easier

Gain hands-on knowledge through the problem solving based approach of the course along with working on a project at the end of the course

Placement Assistance

Training Certificate

Course Contents

Lectures 30 X 2 hrs. (60 hrs) Weekends. Video 13 Hours Skill level all level Languages English Includes Lifetime access Money back guarantee! Certificate of Completion * Hadoop Distributed File System * Hadoop Architecture * MapReduce & HDFS * Hadoop Eco Systems * Introduction to Pig * Introduction to Hive * Introduction to HBase * Other eco system Map * Hadoop Developer * Moving the Data into Hadoop * Moving The Data out from Hadoop * Reading and Writing the files in HDFS using java   * The Hadoop Java API for MapReduce o Mapper Class o Reducer Class o Driver Class * Writing Basic MapReduce Program In java * Understanding the MapReduce Internal Components * Hbase MapReduce Program * Hive Overview * Working with Hive * Pig Overview * Working with Pig * Sqoop Overview * Moving the Data from RDBMS to Hadoop * Moving the Data from RDBMS to Hbase * Moving the Data from RDBMS to Hive * Market Basket Algorithms * Big Data Overview * Flume Overview * Moving The Data from Web server Into Hadoop * Real Time Example in Hadoop * Apache Log viewer Analysis * Introduction In Hadoop and Hadoop Related Eco System. * Choosing Hardware For Hadoop Cluster nodes * Apache Hadoop Installation o Standalone Mode o Pseudo Distributed Mode o Fully Distributed Mode * Installing Hadoop Eco System and Integrate With Hadoop o Zookeeper Installation o Hbase Installation o Hive Installation o Pig Installation o Sqoop Installation o Installing Mahout * Horton Works Installation * Cloudera Installation * Hadoop Commands usage * Import the data in HDFS * Sample Hadoop Examples (Word count program and Population problem) * Monitoring The Hadoop Cluster o Monitoring Hadoop Cluster with Ganglia o Monitoring Hadoop Cluster with Nagios o Monitoring Hadoop Cluster with JMX * Hadoop Configuration management Tool * Hadoop Benchmarking 1. PDF Files + Hadoop e Books 2. Life time access to videos tutorials 3. Sample Resumes 4. Interview Questions 5. Complete Module & Frameworks Code

Hadoop Training Syllabus

Other materials provided along with the training

* 13 YEARS OF INDUSTRY EXPERIENCE * 9 YEARS OF EXPERIENCE IN ONLINE AND CLASSROOM TRAINING

ABOUT THE TRAINER

Duration of Training

Duration of Training will be 12 Weeks (Weekends) Saturday and Sunday 3 hrs.

Course Fee

Course Fee in 15,000/- (7,500/- X 2 installments) 2 Classes are Free as Demo. 100% Money back Guarantee if not satisfied with Training. Course Fee includes Study Materials, Videos, Software support, Lab, Tution Fee.

Batch Size

Maximum 5 candidates in a single batch.

Contact Us

To schedule Free Demo Kindly Contact :-

Parag Saxena.

RM Infotech Pvt Ltd,

332 A, Gali no - 6, West Guru Angad Nagar,

Laxmi Nagar, Delhi - 110092.

Mobile : [phone].

website : http://www.rminfotechsolutions.com/javamain/hadoop.html

[techandguru-blog]

Even #sharpest #programmers find it #tough. Can you solve it? Write your answer in the comment box

Below is an image which contains Java MCQ on access modifier with 4 choices. Choose the right answer and write in the comment box. Even #sharpest #programmers find it #tough.

Java MCQ

Related Items: Java Interview Preparations and Java Basic Concepts

Do you want to stay updated on new #technology changes? Please follow, like, share and #subscribe. Your help can help us grow and we will ensure your growth.