Pruebas A/B
Las pruebas A/B son experimentos controlados realizados online para determinar cómo cada característica de un producto o webpage afecta el tráfico o disposición a pagar de potenciales clientes..
Empresas de software
Usted puede encontrar en este blog entradas referidas al mundo empresarial de las firmas de software, sus interrelaciones y panorama actual.
Marketing
Usted puede encontrar en este blog entradas referidas a Marketing en la red así como para empresas de software.
Seach Engine Optimization
Usted puede encontrar en este blog entradas referidas a como operan los SEO para optimizar su presencia en la red.
Internet
Usted puede encontrar en este blog entradas referidas a Marketing en la red así como para empresas de software.
viernes, 4 de octubre de 2013
Emprendores estonios crean aplicación que ayuda a la gestión
4:00
Juan MC Larrosa
No comments
The corporate world is almost entirely alien to me. I’ve never worked inside of a major company. It wasn’t, therefore, until I fleetingly tried my hand at startup life that I was introduced to the PPP system — Plans, Progress, Problems — for managing teams. In this instance, as CEO, I was the one being managed, tasked with filing PPP reports with my VC backers. I hated it, “why can’t I just pick up the phone?,” I’d say. But actually, those weekly emails worked pretty well.
In a much larger organisation, however, relying on a feed-back loop for teams that consists of emails, spreadsheets or more lengthy reports doesn’t scale very well from a manager’s point of view. Meanwhile, important and timely signals from team members can easily fall through the cracks.
Enter Weekdone, an Estonian startup backed by Ahti Heinla, founding engineer of Skype, and former investors and executives of leading Russian social network Odnoklassniki. The web and newly released iOS app taps into the PPP principle to enable managers to keep a pulse on their teams by streamlining the feedback loop and presenting the results in a highly visual and aggregated view.
Specifically, the problem Weekdone has set out to solve is that compared to the plethora of simple, visual apps that are available to help consumers get things done, the business world often still relies on lengthy documents, spreadsheets and emails to manage tasks and teams, or software that produces far too much unwieldily data that no one executive or manager can possibly hope to keep tabs on.
The Tallinn, Eastonia-based startup, and same team behind Talentag andUtopic, saw an opportunity to bring what it calls “actionable visual tools” to the area of team management. Thus, Weekdone was born with the aim of becoming the default tool for monitoring and managing teams by turning “big data into a thing of beauty”, says the company.
It’s certainly true the app looks the part — it recently won best Internet application at the Estonian Design Awards, for whatever that is worth — but it’s the simple (and, perhaps, realistic) work-flow that makes Weekdone appealing. Striking the balance between data input and the usefulness of what comes out at the other end is key to any type of productivity app, not least an app that is in part monitoring employee “happiness”.
At the start of each week, team members are asked to list their key plans and what they want to accomplish. “Usually these are the 5-7 big goals that have to be achieved whatever it takes,” says Weekdone co-founder Jüri Kaljundi. Then, as the week progresses, employees mark stuff done, automatically moving items from Plans to Progress.
In addition, Kaljundi says employees are required to rate their work happiness and answer any other questions posed by their manager, such as suggestions on how they can improve or what needs to get done.
“The progress can also be automatically imported from [task managers] Asana or Atlassian JIRA, and many other systems like Salesforce or Basecamp in the future, so there is no need for duplicate data entry,” he adds.
At the end of each week the app compiles an automatic visual dashboard and textual report of what’s been achieved since the last update, and what’s planned for the following week, which is sent to managers and team members via email, PDF or accessible on the web, mobile and tablet versions of Weekdone.
“The managers quickly see calculated indicators like team happiness, task completion ratio, overdue items count or problems, and can drill down into each section and person,” explains Kaljundi.
“They also quickly see which promises are not kept or are lagging behind for weeks, something that often gets lost in manual e-mails or task managers,” he says.
It’s from this overview of the app’s data that a manager can be prompted to give quick feedback to each team member or on specific items.
The ultimate goal, however, is to have Weekdone not only make the feed-back loop for teams and managers more efficient, thus improving productivity and employee happiness, but also to act as an early warning system when things go wrong.
To that end, Kaljundi says that Weekdone is putting a lot of its future development efforts into “automatic surfacing of potential problems and suggestions to save managers time and bring out what needs focus”.
At which point, of course, it may still be better to pick up the phone.
jueves, 3 de octubre de 2013
Android se apodera del mundo del smartphone
4:00
Juan MC Larrosa
No comments
The State Of Android — How It's Finally Solving Its Fragmentation And Monetization Problems And Conquering The Planet
Android really is taking over the world.
Business Insider
Android really is taking over the world.
Google's mobile operating system now runs on 60% of all computing devices in circulation (tablets, smartphones, and PCs combined). That's an amazing feat since it has only been around for six years.
In a new report from BI Intelligence, we take stock of Android-land. We look at the significant progress Android has made in reducing fragmentation and improving revenues for global Android developers, and review multiple sources of data on monetization to gauge the correct size of the revenue gap between iOS and Android, according to five different revenue metrics.
How did Android get where it is, and where is it headed?
- Android is the most popular computing software in the world, thanks to its dominance in the global tablet and smartphone markets. It's running on 76% of mobile devices and 80% of smartphones. In the same way that Windows software defined the PC era, Android now defines mobile computing.
- Android continues to gain market share overseas, but its growth has completely stalled in the U.S., at 52% of the smartphone operating system market.
- In the last year, Android has made huge strides in solving its interrelated fragmentation and monetization problems. Presently, a plurality of of Android devices, 45%, are running Jelly Bean, the latest and greatest version of Android software.
- When taking into account commerce, advertising, developer fees and app revenue, Android has nearly closed the monetization gap with Apple's iOS operating system. Android developers worldwide earn 90 cents for every 1$ earned by iOS developers, according to the latest data.
- Android apps deliver a massive global audience, and not surprisingly advertising has emerged as the dominant revenue source for Android developers. Google has also tried to give developers more tools to improve their revenue.
- Additionally, Google is solving Android's fragmentation problem (the fact that so many Android users run on old, outdated versions). Google has come up with a clever solution to cut through mobile industry layers by pushing updates directly to Android users through Google-owned apps and mobile services.
The report is full of full-size charts and Excel datasets that can be easily downloaded and put to use. Subscribers also gain access to our chart library of hundreds of charts and datasets on the mobile industry, and receive weekly in-depth reports and daily data-driven stories on the latest mobile trends.
Business Insider
martes, 1 de octubre de 2013
Innovación en la administración pública
4:00
Juan MC Larrosa
No comments
Agilidad y agilismo para la innovación pública
Los procesos de innovación, como los platos de la cocina moderna, precisan de tiempos de cocción cortos. El plazo, desde que se produce la chispa de la idea hasta que se pone en mercado -el llamado “time-to-market”-, debe acortarse radicalmente para evitar que el entorno cambie y convierta en obsoleto el producto, incluso antes de comercializarse.
Como el principal factor de obsolescencia es la presencia de competidores en el mercado, parecería que estas prisas no son de aplicación a la Administración pública. En general, soy partidario de no transportar directamente las soluciones de la empresa privada a la lógica de lo público. Ahora bien, la Administración pública posee sus propias razones para acelerar los tiempos en sus proyectos.
- El primer motivo apunta a la propia naturaleza de la innovación, que procede en ciclos iterativos de experimentación y evaluación. Cuando los productos incorporan un componente experimental, necesitan exponerse al contacto con sus usuarios lo antes posible, para poder perfeccionarse a partir de la experiencia de uso. En otro caso, nos encontraremos con proyectos faraónicos que, sin embargo, no consiguen ser adoptados. Recordemos que la tasa de conversión es el indicador clave.
- El segundo motivo tiene que ver con la motivación de las personas y los equipos que llevan a cabo los proyectos. Es imposible mantener el entusiasmo cuando un proyecto dura dos años y no se liberan productos intermedios operativos. Llega un punto en que el plazo de entrega se antoja aleatorio, no existe sentido de urgencia -o, al contrario, todo es urgente- y al final se acaba entregando algo que nadie sabe si responde a lo que desearíamos.
- El tercer motivo es económico. Los proyectos faraónicos son, eso, faraónicos y tienden a incrementar sus costes por encima de lo razonable. Mi consejo es que cualquier proyecto tecnológico que tienda a crecer se descomponga en módulos menores, controlables, de duración corta. Una duración ideal es la que abarca un trimestre. Cuidado con los proyectos plurianuales.
Preveo algunos bufidos al llegar a este punto: “claro, a todos nos gusta que los proyectos acaben lo antes posible, pero cada uno tiene la duración que tiene, y es imposible reducirla radicalmente”.
Pues no. Existen formas de conseguir que los proyectos entreguen productos operativos en plazo corto, con costes menores y con mayor satisfacción de los usuarios. Yo mismo he participado en alguno de ellos.
Agilismo: metodología para proyectos de innovación
Se conoce a la familia de metodologías que producen proyectos ágiles como “agilismo”. Originalmente, la expresión se refiere a métodos restringidos al desarrollo ágil de software. Hoy en día, hay que entender el agilismo como un movimiento social que trata de favorecer un cambio de mentalidad que pone en el centro la colaboración y la adaptación.
La Wikipedia lo explica así:
“El desarrollo ágil de software son métodos basados en el desarrollo iterativo e incremental, donde los requerimientos y soluciones evolucionan mediante la colaboración de grupos auto organizados y multidisciplinarios. Existen muchos métodos de desarrollo ágil; la mayoría minimiza riesgos desarrollando software en lapsos cortos.
El software desarrollado en una unidad de tiempo es llamado una iteración, la cual debe durar de una a cuatro semanas. Cada iteración del ciclo de vida incluye: planificación, análisis de requerimientos, diseño, codificación, revisión y documentación. Una iteración no debe agregar demasiada funcionalidad para justificar el lanzamiento del producto al mercado, sino que la meta es tener una «demo» (sin errores) al final de cada iteración. Al final de cada iteración el equipo vuelve a evaluar las prioridades del proyecto.”
La mejor manera de acercarse al agilismo es a través del “manifiesto ágil”:
“Estamos descubriendo formas mejores de desarrollar software tanto por nuestra propia experiencia como ayudando a terceros. A través de este trabajo hemos aprendido a valorar:
- Individuos e interacciones sobre procesos y herramientas
- Software funcionando sobre documentación extensiva
- Colaboración con el cliente sobre negociación contractual
- Respuesta ante el cambio sobre seguir un plan
Esto es, aunque valoramos los elementos de la derecha, valoramos más los de la izquierda.”
Si cambiamos software por cualquier otro objeto de un proyecto de innovación, seguiría siendo válido.
Bien, ¿y qué empresas utilizan metodologías ágiles? ¿Grupúsculos anarquistas de hackers? Citaré algunos ejemplos: Sony/Ericsson, Telefonica I+D, Adobe, IBM, Intel, Microsoft, Novell, Amazon, Google, mySpace, Yahoo, SAP, Bank of America, Merrill Lynch, Boeing, 3M, Bose… El agilismo es uno de los escasos elementos que comparten Microsoft y Google con el Bank of América.
Y, la Administración pública, ¿qué metodología de proyectos está usando? En general, lo más habitual son los modelos “llave en mano”, con esta secuencia:
- Una definición pretendidamente exhaustiva de requisitos
- Subcontratación a una empresa que se compromete a cumplir los requisitos
- Largo período de desarrollo que no produce prototipos operativos hasta el final
- Entrega del proyecto al cliente
- Comprobación de que cumple los requisitos
- Melancólica comprobación de que, aunque cumple requisitos, no es lo que deseamos
- Lanzamiento del proyecto de versión 2, por la misma empresa que hizo la versión 1
- Se repite el ciclo.
Por lo tanto, estamos usando una metodología con un marco de incentivos favorable al fracaso. Para el contratista, es favorable producir una versión 1 que cumple requisitos pero no se adapta a los deseos del cliente, porque así recibe automáticamente el encargo de realizar la versión 2.
Las metodologías ágiles, en cambio, proceden en ciclos cortos (máximo, 3 semanas) de producción y evaluación. Al final de cada sprint, se redefinen las necesidades, acercando cada vez las soluciones a los deseos del cliente, los cuales nunca pueden estar bien definidos al inicio.
¿En qué casos funciona mejor el “agilismo” que los métodos clásicos? En todos, pero especialmente cuanto mayor sea el tamaño y la complejidad, porque consiguen hacer manejables los proyectos complejos.
Agile en la Administración pública
¿Qué Administraciones públicas han desarrollado proyectos mediante metodologías ágiles? No muchas, la verdad. Vamos con retraso. Voy a poner un ejemplo reciente. El Ayuntamiento de Vitoria-Gasteiz ha publicado recientemente un anuncio de licitación para “la contratación de rediseño de la web municipal usando diseño adaptativo”. En el pliego de prescripciones técnicas se especifica que la metodología a emplear es SCRUM, seguramente la más popular de las metodologías ágiles de desarrollo de software.
El equipo de tecnología de Vitoria-Gasteiz siempre ha ido por delante de la mayoría. Felicidades. Espero que otras Administraciones se acerquen a preguntar y que tomen buena nota. El pliego es de lectura obligatoria
Recomiendo a quien tenga curiosidad que consulte la respuesta que en el Parlamento Vasco dio Idoia Mendia, en nombre del Gobierno Vasco, a una pregunta formulada por el parlamentario Álex Etxeberría, acerca del “Manifiesto Ágil”. ¡En 2010! Allí se nombran tres proyectos de éxito elaborados con esta metodología. ¿Soy yo el único que se emociona al ver que nuestros parlamentarios se interesan por materias como esta?
Para acabar, quiero recordar que el enfoque ágil, que enfatiza la colaboración, la adaptación y el minimalismo en la gestión, puede ser tomado como inspiración para la gestión pública más general. En este sentido, recomiendo vivamente la lectura de “Agile Management”, el último libro de Ángel Medinilla -uno de mis gurús de cabecera. Inspirador.
lunes, 30 de septiembre de 2013
Empresas donde la entrevista laboral es demoledora
4:00
Juan MC Larrosa
No comments
25 Companies Where The Interview Process Is Brutal
Read more: http://www.businessinsider.com/most-difficult-companies-to-interview-for-2013-8?op=1#ixzz2bVtZr53b
For the third year in a row, consulting firm McKinsey & Company has been rated as having the most difficult interviewing process by employees.
Glassdoor's ranking placed McKinsey at a 3.9 difficulty rating out of 5.0, beating out tech giants like Google and Facebook, which were also in the top 25.
The average interview difficulty rating on Glassdoor is 2.8.
Newcomers to this year's list include BlackRock, Microsoft Citrix, HubSpot, and Vistaprint.
Some companies still ask crazy brainteasers, despite Google's claims that they have nothing to do with success, while others stand out for running candidates through lengthy tests and round after round of interviews.
25. Rackspace
Interview difficulty rating: 3.3
Tough interview question: “If your day was 20% performing job duties and 80% strategizing then give us examples of what you would be doing with that 80%?” - Rackspace Acquisitions Representative III Interview (San Antonio, TX)
Recent job candidate commentary: “Hour three [of the interview] involved meeting the prospective actual team lead & manager to see how the fit might be. Questions like "Do you get enjoyment out of completing 50 tasks in a shift or do you prefer to tackle very difficult projects that take many hours?" Resume was scrutinized, and questions about if hired, where I wanted to be within the company in 5 years type questions.” – Rackspace Window Systems Administrator II Interview (Austin, TX)
Source: Glassdoor
24. Caterpillar
Interview difficulty rating: 3.3
Tough interview question: "Tell me of a situation when you had to work on safety incident, what was the incident and what was your involvement in providing solution and how it turned out." —Caterpillar Supply Chain Planning Engineer ( SAP IM WM ) Interview (East Peoria, IL)
Recent job candidate commentary: "The interviewer was the hiring manager who is from technical background, so all the questions are purely technical, which were very different from the job description. You gotta be very knowledgeable to go to the next round." –Caterpillar Senior Engineer (Gearbox Analyst) Interview (location, n/a)
Source: Glassdoor
23. Guidewire
Interview difficulty rating: 3.3
Tough interview question: "What is the difference between optimistic and pessimistic concurrency?" —Guidewire Senior Implementation Consultant Interview (Toronto, ON)
Recent job candidate commentary: "Overall it was a great experience and has undoubtedly developed my technical interview skills as well as understanding of some more obscure areas of Java." —Guidewire Solutions Consultant Interview (Dublin, Ireland)
Source: Glassdoor
22. Facebook
Interview difficulty rating: 3.3
Tough interview question: “Where do you see the future of Facebook?” – Facebook Product Manager Interview (Menlo Park, CA)
Recent job candidate commentary: "The second phone interview … I told her about my future plans for Facebook she said it wasn't much different from what they have now. (It is, but she was apparently expecting more than my already unconventional ideas)." – Facebook Product Manager Interview (Menlo Park, CA)
Source: Glassdoor
21. Informatica
Interview difficulty rating: 3.4
Tough interview question: “Describe yourself in 3 words.” —Informatica Senior QA Interview (Bangalore, India)
Recent job candidate commentary: "Most of the interview questions are related to algorithm, problem solving and critical thinking. Interviewers are very friendly and do make one feel comfortable. They focus less on coding and more on general design skills." – Informatica Principal Software Engineer Interview (Redwood City, CA)
Source: Glassdoor
20. Nvidia
Interview difficulty rating: 3.4
Tough interview question: Name as many uses for a brick as you can in one minute." – NVIDIA Campaign Manager Interview (location, n/a)
Recent job candidate commentary: "Even though you answer all questions over phone and get shortlisted for an onsite interview, you will not get a fulltime offer unless you have an internal reference." – NVIDIA Compiler Verification Engineer Interview (Austin, TX)
Source: Glassdoor
19. Citrix Systems
Interview difficulty rating: 3.4
Tough interview question: "What is the role of PDC emulator?" — Citrix Systems Technical Support Engineer Interview (location, n/a)
Recent job candidate commentary: "We discussed approaches to specific challenges, when asked for examples of providing solutions to a business group, I targeted both my tactical and strategic examples to demonstrate my range." — Citrix Systems Mobility Program Manager Interview (San Jose, CA)
Source: Glassdoor
18. Sapient
Interview difficulty rating: 3.4
Tough interview question: Write pseudo-code for a method and then create a full database schema for the proposed scenario." – Sapient Associate Consultant Interview (Arlington, VA)
Recent job candidate commentary: "They will send you an interview package email before the 1:1 interview, so make sure you read all the links in there. There are some Harvard and Yale Business Cases I found in there and they were very helpful." – Sapient Senior Associate Interview (Boston, MA)
Source: Glassdoor
17. BlackRock
REUTERS/Eric Thayer
Interview difficulty rating: 3.4
Tough interview question: “How would you invest $N in, say, (insert tech giant like Google/Facebook/Apple/Yahoo/Microsoft) ? What options would you take - stocks, bonds, etc.” – Blackrock Analyst Interview(New York, NY)
Recent job candidate commentary: "Pretty robust, though I expect it varies depending on the team. Failed an interview the first time I applied, passed the second time. As a person with a non-finance and non-programming background, I had questions ranging from general knowledge to puzzles to project management to my extra-curricular interests in coding." — BlackRock Analyst Interview (New York, NY)
Source: Glassdoor
16. Microsoft
Interview difficulty rating: 3.4
Tough interview question: "What do you do when there is no answer" — Microsoft Software Development Engineer In Test (SDET) Interview (Redmond, WA)
Recent job candidate commentary: "Process was driven very professionally by HR who took an active role thru out... Good balance of discussion between my experience, skills and my current and future interests." — Microsoft Engagement Manager Interview (location, n/a)
Source: Glassdoor
15. Avaya
Interview difficulty rating: 3.4
Tough interview question: "What kind of car do you drive and why?" Follow up question, "There are a lot of very affordable, high quality used cars, so why would you drive something that expensive?" — Avaya Territory Account Manager Interview (Denver, CO)
Recent job candidate commentary: "The on-site interview lasted 6 hours and was interviewed by 8 different people throughout that time. The people seemed 'normal' for the most part but there were areas with the nerdy and quiet stereotypes." — Avaya Systems Engineer III Interview Interview (Westminster, CO)
Source: Glassdoor
14. Procter & Gamble
Interview difficulty rating: 3.4
Tough interview question: “Describe a time when you had to do something you didn't want to do.” — Procter & Gamble Brand Manager Interview (location, n/a)
Recent job candidate commentary: "Really it's a company with strong values and they are looking for people with good personalities and character. So their interview process is all about filtering people through to see who can drive results, who can have fun, and who is competent enough to compete within." — Procter & Gamble Process Engineer Interview (Iowa City, IA)
Source: Glassdoor
13. Teach For America
Interview difficulty rating: 3.4
Tough interview question: "How do you measure success?" — Teach for America Corps Member Interview (location, n/a)
Recent job candidate commentary: "Long, tedious process … All of the interview questions fall into three categories: 2 questions on why TFA, why teaching etc., then half on whatever leadership position you wrote about in your app, and half about how you overcame challenges and difficulties." — Teach for America Teacher Interview (location, n/a)
Source: Glassdoor
12. Vistaprint
Interview difficulty rating: 3.5
Tough interview question: "How [would you] find the index and value of a missing element of an array of 5000 numbers?" — VistaPrint Software Manager Interview (Lexington, MA)
Recent job candidate commentary: I was interview[ed] by 7 people for the job. A very lengthy interview process where one was technical interview, the other are normal HR and behavioral and another on QA process etc... Process was lengthy but wait time was short for a decision." — VistaPrint QA Test Lead Engineer-sap Interview (Lexington, MA)
Source: Glassdoor
11. Paycom
Interview difficulty rating: 3.5
Tough interview question: "How do we know you're not going to give up when it gets tough?" — Paycom Sales Representative Interview (location, n/a)
Recent job candidate commentary: Interview process is tough. It’s a five step interview process and you need to be at your best every step of the way." — Paycom Sales Representative Interview (Denver, CO)
Source: Glassdoor
10. HubSpot
Interview difficulty rating: 3.5
Tough interview question: "Teach me something." — Hubspot Inbound Marketing Consultant Interview (location, n/a)
Recent job candidate commentary: "Initial phone screen with HR, phone screen with Sales Recruiter, followed by a VERY LENGTHY (took me two hours) test which included six parts (personality, vocabulary, situational questions, analogies, math and word problems), followed by a phone screen with the Sales Manager." –Hubspot Account Manager Interview
Source: Glassdoor
9. Stryker
Interview difficulty rating: 3.5
Tough interview question: "What kind of people do you dislike the most?" — Stryker Sales Representative Interview (Orlando, FL)
Recent job candidate commentary: "The interview process was intense, but it makes sense why the company is incredible successful and an industry leader. Be prepared to meet with several people and have your resume / background torn apart for accuracy." — Stryker Marketing Associate Interview (San Jose, CA)
Source: Glassdoor
8. Google
Interview difficulty rating: 3.6
Tough interview question: "Tell him how many people watch YouTube in my country last 1 hour?" — Google Search Quality Analyst Interview (Singapore)
Recent job candidate commentary:"The process and interviews were difficult and unusual but clear, informative and logical. It included a sales mock up pitch via the phone which is the hardest stage. You do need to understand the industry and local market and be up to date with related technologies." — Google Inside Sales Manager Interview (location, n/a)
Source: Glassdoor
7. ZS Associates
Interview difficulty rating: 3.6
Tough interview question: "What is the total surface area of a Boeing 747?"— ZS Associates Business Operations Associate Interview (Pune, India)
Recent job candidate commentary: "The interview process consists of 1 written round, 1 GD round, 1 case study and multiple rounds of interviews. The interview process is one of the most rigorous that I have heard of." — ZS Associates Business Operations Associate Interview (Location n/a)
Source: Glassdoor
6. Rolls Royce
Interview difficulty rating: 3.6
Tough interview question: "How would you build an engine from scratch?" — Rolls-Royce Manufacturing Engineer Interview (location, n/a)
Recent job candidate commentary: "It is VITAL that you know your stuff about the company; I was quizzed heavily about some very specific aspects of the business. The day was completed with the group exercise." — Rolls-Royce Graduate Scheme (Leadership) Interview (Derby, England)
Source: Glassdoor
5. Bain & Company
Interview difficulty rating: 3.7
Tough interview question: "Try to estimate the revenue from the sale of tickets at the Olympics in 2012." —Bain & Company Business Analyst Interview (Gurgaon, Haryana (India))
Recent job candidate commentary: "3 rounds with progressively higher level managers, 2 interviews each round. One case each interview. They were tough but fair." —Bain & Company Associate Consultant Interview (New York, NY)
Source: Glassdoor
4. Gartner
Interview difficulty rating: 3.7
Tough interview question: "You have 30 seconds; list as many uses for a baseball bat as you can think of..." — Gartner Client Partner Interview (Fort Myers, FL)
Recent job candidate commentary: "Very intensive interview process. They get very personal and spend a lot of time trying to understand your 'sense of purpose.' Essentially what they are getting at is, do you have something that drives you to make a lot of money" — Gartner Account Manager Interview (Fort Myers, FL)
Source: Glassdoor
3. Boston Consulting Group
Interview difficulty rating: 3.8
Tough interview question: "If I took your resume and removed the name at the top, what line on your resume would make your friends read it and recognize you?" — Boston Consulting Group Consultant Interview (Philadelphia, PA)
Recent job candidate commentary: "Overall relaxed, though it was tough to get a good read on the interviewer. Definitely brush up on basic math, especially multiplication and division and practice in front of someone as it simulates the pressure you'll have. It seems like even a simple math error can doom you, so practice." —Boston Consulting Group Consultant Interview (Boston, MA)
Source: Glassdoor
2. Thoughtworks
Interview difficulty rating: 3.9
Tough interview question: Tell us a story which the title is Green Hat." — ThoughtWorks Software Engineer Interview (Chicago, IL)
Recent job candidate commentary: "The hiring process is really thorough at ThoughtWorks. Even for an operational role I had 7 interviews. While this is exhausting it's also really helpful because I got to meet lots of people I would be working with, and ask questions - and get really honest answers. It seems to be as much about whether you want to work there, as whether they want you." — ThoughtWorks Marketing Interview (location, n/a)
Source: Glassdoor
1. McKinsey
Interview difficulty rating: 3.9
Tough interview question: "How would you calculate the annual carbon emissions from electric versus gas vehicles in the EU?" — McKinsey Business Analyst Interview (Boston, MA)
Recent job candidate commentary: "All the way, I met very interesting and capable people, the process itself was grueling - training for case studies in parallel to a full time executive job is not easy - but also very motivating." – McKinsey & Company Management Consultant Associate Interview (Chicago, IL)
Source: Glassdoor
Read more: http://www.businessinsider.com/most-difficult-companies-to-interview-for-2013-8?op=1#ixzz2bVtZr53b