Skip to main content

Leaving CSB Engage :(

What a journey it has been!

Whether it be developing SIG using the Facebook and Instagram APIs or managing huge data sets (close to 1 billion). CSB Engage has been a wonderful place to work. It had flexibility and a great culture. The best thing would probably be the Monday lunches. This is where one person from the team would bring lunch from home and we would eat together. I'm proud that I've seen CSB Engage grow from Endless Rewards, to its merger with OnitMedia and I've been there every step of the way.

Why did I choose to leave? Well, I wasn't 'actively' looking to leave. I really was enjoying my time. But I felt I needed to be in an environment where my desire to learn would be aided and the opportunity that was given to me was exactly what I needed.

I generally learn when I'm around a group of smart individuals whom themselves like learning, so when I saw that Readify had an advertisement on LinkedIn. I decided to give it a shot. The recruitment process at Readify was four-stages. So it wasn't easy, nevertheless it was fun.

The first stage was developing a SOAP application (something I haven't done for a while) and deploying it. The application had a few puzzles which I had to solve. I knew one of my solutions to one of the puzzles was taking too long. So I had to do a bit of Googling to make it quicker. Readify says that this test takes 2 hours however it took a lot longer than that for me! There were two reasons for this. 1. because I haven't done WCF for a while, so I had difficulty using the classes and then deploying it to my AWS server and 2. taking me a while to realise that there are more efficient ways to do the problems and making my application quicker (Readify will fail you on speed). The details are here if you want to give it a shot:

The second stage was a technical interview with a live debugging session. To be honest, I didn't think I did too well here. And it was quite difficult at the time, but looking back it wasn't too bad. Nevertheless I made it through this stage as well :)

The third stage interview was a cultural fit one. I had a chat with one of the managers at Readify and she asked me a series of behavioural as well as cultural questions.

The final stage was with the state manager. It was similar to the third interview but with a broader view of the organisation.

None of the above stages are a surprise and Readify lists them on their website.

So I made it through the recruitment at Readify. And I'm feeling excited to be starting on Monday. I'm not sure what challenges would be thrown my way, but I hope I'm ready!!

As for CSB Engage. I will miss it. People have been great. I want to especially thank the leadership team for all their support!


Popular posts from this blog

from zero to production in eighty days

When I mean zero, I literally mean zero. A brand new project, a PO that's new to IT, no existing processes in place and a small team of four including myself and the PO.

The departmental organisation we were working for doesn't have any developers, scrum masters, product owners working for them. Everything they did was either done by another department or outsourced completely.

This is a story how we went from zero to production in eighty days.

My first time speaking at a conference

Since time immemorial we humans have valued the art of public speaking. Today, I want to share with you my experiences in speaking at conferences for the first time. Recently, I spoke at both DDD Melbourne and DDD Perth. Both of which were positive experiences that I learnt a lot in.

Have You Ever Produced Negative Value in a System!?

As developers we encourage our product owners to order the priority of their backlog in order of value. However, every time a new feature is implemented by a development team, there is a certain degree of risk associated with the introduction of that new code. Namely, risk of breaking another part of the product and maintenance cost. When a development team pulls in a new feature to implement there is a certain acceptance of this risk. In many cases, the risks that arise due to additional code complexity doesn't justify the value added by the new feature itself, so the development team can start implementing it.

Are there scenarios where the value added to a software product can be negative though?