This is a piece for the team at Exsilio, our clients, and partners to know what our internal expectations are. Obviously, the title of this article is rather black and white, and it seemed to me of value to have a discussion on how Exsilio can be a challenging, yet very rewarding, place to work for reasons people may not immediately think of. I'm going to speak specifically about developers, but the general concepts apply to all categories of our team.
As a service based organization, people often believe that being successful in their job means having a specific technical skillset. For example, I'm a developer and I’m very good at programming in T-SQL and C#, so I should be successful. A strong technical skillset is a given, and honestly speaking, if your only asset is your technical knowledge then you're probably not going to succeed – at least not at Exsilio.
Let’s talk about what makes people succeed, get the level of appreciation they're looking for, and keep everyone else happy. So think about the real purpose of your job. Since I’m already using the example of a software developer, why do people want software developers, to write code obviously (this is the point where average developers begin to fail). But there are more fun ways to spend money, so why are they spending their money on this project? Fundamentally, at least in most cases at our company, it is to write code to create solutions which will make someone's life better or easier than it would have been otherwise. And it’s a solid understanding of this where you move from an average developer to a quality developer.
If you're a software developer and you're not thinking every day, with every task, about how your solution will enhance, benefit, and dare I say "amaze" the end-user, then you're in the wrong profession. You’re certainly working for the wrong company, if you work at Exsilio. It goes further than the code you write, it is the way people interact with the product you build, it is the way you present your product, and the way people receive it. The end product should practically glow with the pride and efforts of the person who is delivering it. This comes from the person building it affirmatively answering all of the following: Does this make sense? Do I know why I'm building this and understand the value it will be providing to people? Is this something I'd want to use every day? Am I proud of this product? Is this something that is commercially worthy?
I hear developers often say “I’m a developer not a creative designer.” I tend to translate this to, "It should be alright if I create something that looks like crap." Professionally, this may be correct; however, people know what looks good and what doesn't. While some make the excuse that it is subjective, most people would agree that Lamborghinis and Ferraris are truly stunning vehicles, they don’t need a creative designer had to tell them this. They know it based on basic senses. The same rule applies if you’re a developer without a creative person on your team; build something that you're incredibly impressed by. If you're incapable of doing this, then either you don't care about your project or you’re lacking in technical skills.
In the same regard as above, they often times say “I'm not a business analyst so I should just need a technical spec and not need to understand the business requirements”. To that I say something very similar. Simply put, if you're working on a project and you don't know the business rationale and use cases behind it, then 1. Your project is doomed from the start and 2. You probably should be working on it until you do.
At the end of the day, if the software you’ve written doesn’t make your users feel like they're being more successful and impressed both by function, feature, and general beauty, then the project was a failure. Average developers, developers who shouldn't be working at Exsilio, simply take what was delivered to them on a technical specifications document and deliver on that. Anyone who's been around me in meetings to review projects and status hopefully knows this.
While this piece was aimed at the developer, it conceptually crosses the boundaries for all of the delivery groups in our organization. It is really an honor that our customers have chosen to work with us on some truly amazing, incredibly high profile, and cutting-edge projects, but with that comes an awesome level of responsibly. With that level of responsibility come the intangibles that make people the best they can be. At times, these are the same things that can make Exsilio a tough place to work for reasons I think most wouldn't ever think of. Over the six years, I’ve thought it is worth it, and honestly I have to believe the people who’ve stood the test of time have thought so as well.