Saturday, July 21, 2012

"Crack ThoughtWorks"

              




Hi, Yesterday i become glad by listening  that ThoughtWorks (DREAM COMPANY) going to visit in GNDU  for 2013 Batch. ThoughtWorks is the 1st company visiting for 2013 batch. so student have no experience how to crack the interview and what companies are looking for. Here is little effort from my side to help  juniors so they can start there career in reputed companies.
          So, every company have different requirement according to the position. some companies are looking for totally technical guys and dont deal with marks or any other stuff like no backlog, no gap and some do. TW is purely a technical company and have a group of great talented curious  person so they are looking for the same.
Main Thing is "FOOD IS NOT FREE". A company never pay you for free if they are paying such high packages(5.86LPA) then they expect much from you side too. Don't panic, Be confident you can do it. just need of will power  and curiosity and should be a technical guy.
 The hiring procedure of TW include 5 rounds.
 1) Written Test
 2) Pair Programming Round
 3) Technical Interview Round 1
 4) Technical Interview Round 2
 5) HR Round.
Written Test:  
Written Test will not a aptitude test. it wouldn't contain any quantitative or reasoning question. It will a flow chart round which would be difficult to crack. Appox. only around 10%  clear this round but again practice make the man perfect and The TRICK IS THAT JUST GOOGLE YOU WOULD GET SAME FULL TEST PAPER. But this is not enough, approximately all of you must have question paper in hands but still it will not easy to crack because you don't know the correct answers and even your answers are correct but you cant remember the answer and it would become difficult to solve the paper again in such strict time limit. Keep in mind that you are not alone who have paper everyone have paper in there hands prior So practice very hard.
Around 400 student participated but only 31 was able to crack this round so practice hard.
Pair Programming Round:
In this round they will give you 1 problem and you have to break down the logic and code that problem with the help of your programming partner(a person from the side of TW) in your favorite language. Main thing is that you have to take deep care of  coding scenario and naming conventions  and if your are coding in object oriented language then you have to follow all the rules of OOPS. AGAIN THERE IS A TRICK JUST GOOGLE FOR TW PROGRAMMING PROBLEMS AND YOU WILL GET ALL THE PROBLEM STATEMENTS. Practice 1 or 2 problem in prior.
Here is sample Code which was coded by me during last year TW drive.

Look at the naming convention adopted in this code. don't go for logic in deep and keep talking with your partner during this round  tell him each & everything what you are going to do. Your logic, the  Name conventions, why you adopted for particular programming language, everything share with him/her.
Only 8 students left after this round.

Technical Round 1: unfortunately i was out in this round reason are many. but main reason is OVER CONFIDENT. So don't make such a silly mistakes. i didn't revise anything. So  please be prepared. The interview is not like a other companies interview they will ask you simple question. Pattern is very much different.
This is 2-to-1 round, you will interviewed by 2 person. The interview will start with OPPS design  question in UML.
Like: Design Regulator of FAN
Design Chess Game.
Design Model for university.
And many more......
 for cracking this round read OOPS book by Rambaugh.
After reading this book practice your hand on live Problems.
After opps design question they might go for a puzzles. Don't panic if you found that problem is difficult. INTERVIEWER NEVER EXPECT RIGHT ANSWER THEY ALWAYS EXPECT A RIGHT APPROACH.
Your problem solving skills will play role. After puzzles you will face some Algorithm design question and some question on Data Structure.
find some Algorithmic question on this link and try to crack the logic.
ONLY 1 student left after this round.
Technical Round 2:  In this round they will ask you some new problem from the same domain like oops, DS, ADA. Keep in mind that keep talking with interviewer tell him/her everything.
Do brainstorming find logic and explain your logic like that  "I Think *WE* can solve this problem by this way". Have a deep look on last line, i told that "WE" not "I" try to involve interviewer in you problem work like a team, explain your approach, may be you will on right way and interview will give you some clue to solve problem or if you are on wrong path interview can guide you. so try to involve him.
some practice Books for this round: Crack the coding interview & Algorithm made easy.

HR Round: Not much sure about the HR cos is was out till this round So it would be general HR round.
Because they know well That "GEEKS ARE OFTEN WEEK IN ENGLISH". Ohhh sorry... i mean "WEAK". :)

BEST OF LUCK TO ALL.


9 comments:

  1. 1) Applied on their site. Within not much days got a call back from HR. Asked for a call interview to be scheduled.

    2) On call interview went about who I am, what I do at work and what do I do other than my work. Why I am looking for change and why thoughtworks. Any open source contributions I have done? What do I know about their company? It went all well and HR was satisfied. I was moved to next step and told to submit code solution they will be mailing.

    3) Got two problems, I answered one of my choice, spent a weekend to designing and decorating the solution with all my OOP strengths.

    4) The INTERVIEW – As I reached their office around 10:30 A.M. HR greeted and received me, took for a coffee. You could see all what you hear mostly no cubicles, sticky notes all around for various tasks.

    Code Refactoring Round (The Good Part) – In this round you will sit with senior developer and refactor the code which you submitted.
    It went quite smooth and was real fun, main reason being I really liked attitude of the guy and he was very interactive. The guy was courteous enough to get me a windows keyboard when I was struggling with his mac keyboard.

    1st Technical Interview (Not so good part) – Here two thought workers came to interview with 5 and 7 years of experience respectively. As they came senior guy asked me some questions straight ahead, like tell me about you. What do you do in spare time? Then junior interrupted and gave his introduction told what he does in the company and what all he works on.

    Then first question was “Why Thoughtworks, What are you expectations from Thoughtworks”, as I replied things being Agile, Test Drive Development and how lack of these practices have in my current company is has driven me on quest of such a company. Also I have heard its different experience with no cubicles etc.

    Then second question was “What you can contribute to Thoughtworks, what your vision is and what you bring to the table”. Not so good with self-praise, I could only get few items here. I told my vision of becoming a good architect and build good solutions.

    Then came “Give a OOP design of Library Management System”. I went ahead and approached the board and explained my thoughts on how would go about approaching the problem, starting with chalking down some requirements. As I was writing down requirements and things what I thought it should do, I was interrupted to tell that they need DESIGN and I can skip these things. In my head I was going with already such a vague statement such as “Library Management System” which can cover so many things, I didn’t have clue what they were expecting to hear or see. Anyways I continued to draw some UML of some interface and sure shot classes such as Book and put in some attributes. Then Also drew Library class and established has a relationship. Then as I was moving in the direction of getting more items under common interface like magazines, cd’s etc. I was stopped and told how you would search in this system.
    I was also told that LMS is large system I should focus on a part of it. Getting rid of such vagueness I felt relieved. Discussion went around from being how will be attributes stored to performance of this thing that trying to match each book would be performance intensive to not exposing internal attributes book to any outside class.

    Then we went onto some balance parenthesis question. I suggested all time famous stack then , I was told to do with recursion which I could. Other than that small discussion on how hibernate works and maps RDBMS tables took place.

    So in summary out of an 1.5 hour interview. Majority time (around an hour) went where I blabbered around LMS. I saw most of the time went NEGOTIATING requirements with them rather than focus on design. I don’t know if they were trained but they will give very little signs on if they agree with you or not leave alone the answer even on the Question.

    HR Guys: In all my experience the people who consistently I admired were HR Guys

    ReplyDelete
    Replies
    1. please help me to prepare for thought woks next month thought works is coming for recuirtment

      Delete
  2. The interview process can be very upsetting too.
    Here is a funny yet sad scene that has happened during a ThoughtWorks interview.

    Immaturity levels are quite high nowadays in the interviewing process:

    http://lovethoughtworks.blogspot.com/2014/06/a-hilarious-review-on-thoughtworks.html

    ReplyDelete
  3. hello,
    very good post thanks for the help.
    as you mentioned up there that we can find thoughtworks questions on the internet.
    i googled but was unable to find them.
    can you please help me with the same.

    ReplyDelete
  4. The Le_Meridian Funding Service went above and beyond their requirements to assist me with my loan which i used expand my pharmacy business,They were friendly, professional, and absolute gems to work with.I will recommend  anyone looking for loan to contact. Email..lfdsloans@lemeridianfds.com  Or lfdsloans@outlook.com.WhatsApp ... + 19893943740.

    ReplyDelete
  5. Wow! Keep writing stuff like this. Moreover, if you need an accounting software for managing your day to day task then go for QuickBooks software. It has many outstanding features that will help you out. Besides, get assistance to fix any issue at QuickBooks Payroll Tech Support Number 1-833-401-0204. Read more: https://www.mildaccounting.com/quickbooks-payroll-tech-support-number/

    ReplyDelete
  6. QuickBooks Enterprise Support Phone Number is successfully delivering the world class technical assistance for QuickBooks Enterprise at comfort of your home. We understand your growing business need and that is the reason we provide only the best.
    QuickBooks Enterprise Support Phone Number
    QuickBooks Enterprise Support Phone Number
    QuickBooks Enterprise Support Phone Number

    ReplyDelete