How we interview developers

Captain's log, stardate d182.y38/AB

Every week, we're approached by ten or fifteen different companies who need to hire developers.

After having serviced dozens of different companies, ranging from big corporates to one-man startups, we can share a bit of our secret sauce. In this blog, we will talk about how we interview them.

My tips for public speaking for tech people

Captain's log, stardate d139.y38/AB

Wow! I am still exhausted about my panel last week at the second edition of the Startup Grind Barcelona annual conference. It's been a long time since I had last spoken in front of such a large audience.

We, tech people, aren't too inclined to speak publicly. We might speak at minor tech events, or even in some small tech conferences, but rarely ever in front of big audiences. Let me share my tips with you!

How to improve self-confidence when writing code

Captain's log, stardate d598.y37/AB

One of the most frightening parts of being a developer is the recurring feeling that the solution that you are building is not going to work as intended, it is going to scale poorly or some of your coworkers will dislike working on top of it.

To give the best of yourself as a developer, you need to learn how to move away from these toxic feelings.

The importance of a step back to find quick wins

Captain's log, stardate d576.y37/AB

This week, I want to highlight the importance of taking a step back to analyse the applications we develop for our clients.

Being a consultancy means that all of our projects are for third parties (clients) who hire us for our expertise in Ruby on Rails or because they need more manpower and thus need extra people to increase their development pace.

Our clients always tend to prioritise new features. They feel that advancing equals building new features, but we need to advise them to take other factors into consideration.

You're one step away from meeting your best partner in business.

Hire Us