Consulting quiz

Do you have what it takes to become a Softhouse consultant? Go through our quiz to see if it's a match!

Press Start Quiz to start...

Embrace the confusion

You start your new assignment and everything is new and unknown - new technologies, new people, and new ways of doing things. What do you do?

Embrace the confusion. You know your fellow Softhousers will help you onboard and you’ll get it eventually.

Panic. You go out of your way to get up to speed but still feel insufficient and like you’re not the right person for the assignment.

Not applicable to you, since you refuse to take on new assignments where you feel you can’t fully deliver from day one.

Assist your customer in making the correct decisions

You’re at a crossroads when it comes to picking the right solution for your task. There are different paths and you have to choose one - how do you proceed?

Make a decision based on what you believe is best for the customer. Since the customer is busy, you present your decision at the next sprint demo and be prepared to re-evaluate your decision.

List the pros and cons of different alternatives and present them to your customer. Let the customer decide which way to go.

Make a decision based on your own experience and preferences, how you’d like to work, and what you think is the most fun.

Never? Talk about the customers with customers.

You are attending a meeting with your customer, discussing challenges and problems. You have had similar experiences in previous assignments and want to share your experience on how to solve the problem. What happens next?

You talk openly about your previous assignments and experience. Describe what problems the customer had and what they did to mitigate them.

You sit quiet at the meeting, worried about the previous NDA (nondisclosure agreement).

You anonymize the previous customer and share your experience more generically. This shows you can be trusted and they can speak openly about their problems.

Respect the legacy

You are about to make some minor changes to the source code to support new requirements, but the simple change requires major refactoring due to how related features are implemented. You get frustrated and stressed. What happens next?

You complain loudly and ask your colleagues why the code is so crappy. You explain to your customer that due to the poor quality of the code base, the requested changes will take time.

You try to understand why the code and solution are implemented the way it is - time restrictions, changes in requirements, or different people working in the code base? You respect the work and effort that has been put into the code.

Follow the path of the pioneers before you

A new feature is being implemented due to new requirements. From previous assignments you know of a good and cost-effective way of implementing the feature. What is the next step?

You start development directly according to your plans and solve the requirements on time and with sufficient quality.

You dig into the source code, try to find out how similar features have been implemented, and ask other developers in the organization what they think. You implement the feature according to existing patterns in the code even though your initial plans were "better".

Your target audience is often average Joe

You work in a highly efficient and skilled team. The team velocity is high and your deliveries always exceed expectations. What’s your approach when working on a feature?

Knowing that your team is highly skilled, you try to make elegant and advanced solutions to impress them. You create solutions you are proud of due to their elegance.

Knowing that people outside of your team will probably maintain your code in the future, you try to make a simpler solution. You avoid using advanced language constructs, features, and algorithms knowing that even less experienced developers will understand your work.

The commit log is your legacy

A bug is found in the system, you have found the cause and implemented a solution to it. You are about to commit the code, how do you proceed?

Knowing that your commit message is your legacy and will never change, you try to describe your commit in the best way possible. You describe why you are making the change and how you’re fixing it. You know that future developers will read your commit message when trying to understand the context of a code change.

Since no one will care about your commit message, you write a short note about fixing a bug. You don't waste any time trying to explain further.

If it isn't tested, it doesen't exist

You are developing some new views in a front-end GUI. Everything has been manually tested during development and you know that the GUI is working as expected. Are you done with your task?

Since both you and your teammates have manually clicked through the GUI and everything is working, you proceed to your next task.

Knowing that any future change will probably break your code you spend time writing automated tests for your changes. You know that these tests will help in the future when changes are being made and the GUI evolves. You know that your tests enable refactoring.

Use your body to strengthen your mind!

A bug is driving you crazy, and you’re banging your head against the keyboard trying to figure out what is wrong. Hour after hour passes without any solution in sight. What is your next step?

You lock your screen and take a break knowing that physical activity will boost your mind and help you find the solution to the problem.

You continue to bang your head against the keyboard. You get frustrated with a growing headache and drink more coffee to keep your focus. Eventually, you find the solution and fix the problem.

You are in the drivers seat of your professional development

You feel stuck in your professional development for some time now. What is your first reflex to remedy the situation?

You google around for a new job

You talk to your closest leader about how you feel. Together you revisit your development goals and look at possible solutions.

You stay put and do nothing, you are lucky you have a job to go to.

Name

Email

Phone

Consulting quiz

Do you have what it takes to become a Softhouse consultant? Go through our quiz to see if it's a match!

hello@softhouse.se

+46 40 664 39 00