Here’s a great website for anybody looking for a remote job. It provides a rather lengthy list of categorized careers, with explanations of what each one is all about, links to learning and training materials, as well as the links to the numerous websites where remote jobs are advertised.
There has been some noise in the mass media about the 996.ICU (official website) recently. That’s good, but I think we can do better. So, spread the word!
Here are a few bits to get you started:
The name
996.ICUrefers to “Work by ‘996’, sick in ICU”, an ironic saying among Chinese developers, which means that by following the “996” work schedule, you are risking yourself getting into the ICU (Intensive Care Unit).
What is 996?
A “996” work schedule refers to an unofficial work schedule (9 a.m.–9 p.m., 6 days per week) that has been gaining popularity. Serving a company that encourages the “996” work schedule usually means working for at least 60 hours per week. Visit 996 working hour system on Wikipedia for more details.
GitHub and Microsoft works support the 996.ICU initiative, as well as many other companies and teams.
Cyprus Tax Calculator is probably the best implementation of the tax calculator that I’ve seen around. It’s dead simple to use, and allows all kinds of calculations – monthly or annually, with or without 13th salary, and reporting overalls, income tax, social insurance deductions, as well as providing tax breakdowns.
Very handy tool for anyone in the job market. ;)
This week I’ve handed in my resignation letter, marking my last working day as February 28, 2019. After 4.5 years as a Chief Technology Officer at Qobo, I feel it’s time for a new adventure.
Looking back at the last 4.5 years, it feels like there is enough to fill several lifetimes – so much has been done, so much has changed, so many people met, so many ideas tried, and so many things accomplished!
Have a look at my annual posts summarizing just the most noticeable changes:
Or, if you feel like it, take a deeper dive into more blog posts, varying from Instagram pictures to some deep technical brainstorming and solutions.
Obviously, I can go on and on for hours, but here are a few high-level points just to keep things in context:
I have met and worked with some really amazing people and teams, true professionals, and inspiring individuals. I have learned a great deal over the years, and have grown both personally and professionally.
So, why am I leaving then? I feel it’s time. It’s time for a change both the company and for myself.
When I joined Qobo, it was a tiny startup, like many others, trying to find its identity, develop, and grasp some luck. It was also still trying to survive the catastrophic consequences of the “Cyprus haircut“, which killed many stronger, more mature businesses. Gladly, we managed to pull through all of that. It wasn’t easy by any means, but we’ve done that. The company has survived, grown, and matured.
It is now well on the way to success, with a clear vision, great products, strong client portfolio, good reputation, and an amazing team.
I think I have done enough to help Qobo to get here. There are now many new people, ideas, and approaches, which will take it forward in a smoother, faster, and more efficient way.
As for myself, it’s also been quite a ride. There has been countless nights and weekends of tight deadlines, non-stop work, lack of sleep, nervous breakdowns, alcohol abuse, emotional highs and lows, and so on. (All kind of expected in a startup.) But I need to step back and recover a bit. On top of that, over the last few month, my focus was mostly needed in non-technical areas. I want to get back to my routes for a bit, and dive into the hands-on technology – things that I like the most: writing code and administrating infrastructure.
Where am I going then? To tell you the truth, right this moment – I don’t know yet. The decision to step down as a CTO and to leave Qobo took quite a bit of thinking, consideration, and preparation. I haven’t looked at my new options or opportunities yet. But given the state of the IT industry in Cyprus and a growing deficit of developers, devops and system administrators, I’m sure I’ll find my next adventure soon enough. (If you have any suggestions or recommendations, please do ping me either here or via LinkedIn).
I would like to take this opportunity to say a huge thank to you to everyone I’ve met and worked with while my years in Qobo. I am truly humbled and honored to have had the opportunity to work with you and to learn from you! I’m sure our paths will cross again.
The Science of the Job Search, Part VII: You Only Need 50% of Job “Requirements” – is a nice article in the series, with a few interesting numbers. The one that stands out the most is:
You’re as likely to get a job interview meeting 50% of job requirements as meeting 90% of them.
This sounds about right. And it also explains how the recruiting is still around, with all those ridiculous requirements in every other vacancy.