4PSA is expanding the technical support team for its flagship product, VoipNow. If you’re up for interesting challenges, this is your best shot at it.
The title is an intended pun, of course :). Still, it’s not that far from the truth, because as a Technical Support Expert, you are going to perform lots of investigations. Some complex scenarios may take hours or even days to complete. It’s not so much about the technical challenge, but mostly about making the customer happy.
There is no apparent connection between these two, but Moonshot is actually in the same trend, even though it uses Intel x86 (Atom). Many people advocate for ARM on servers, mainly because it is low-power, allowing a high CPU count per rack. But no one would mind I guess with a low-power CPU from Intel either.
Unfortunately, not many have a good overall picture on the cloud challenges, not to mention software engineering. And this is pretty complicated.
With a weather as sunny as this, who would stay indoors? Definitely not Johnny! 🙂
Check out this week’s problem to see what it’s all about. As always, keep in mind the rules and send us your solutions here by Tuesday, April 23rd, 10:00 AM GMT! Good luck! 🙂
Keep in mind that the competition is almost over! We will have only one more problem next week.
VoipNow is a complex team, with different skills, from product management to support experts and sales, constantly growing and looking for more teammates. This article is about a new opportunity in the Software Engineering Unit. When it comes to choosing our colleagues, we are very picky. But if you’re very good, you will win us over in no time. 🙂
VoipNow, 4PSA’s best known product (yet), has been designed with the goal to make people communicate faster, more efficiently, and at a lower cost, while enabling them to become more mobile.
Today’s post is about the team behind it.
We can’t kick off the weekend without a brain twister, can we? 😀 Here’s our third problem to keep you company by Tuesday, April 16th, 10:00 AM GMT! That’s the deadline to submit your awesome solutions. Do not forget about the rules and submit your results here.
Undoubtedly, you are familiar with cloud storage. Still, have you ever wondered how they are designed? To find out, you need to address some of the problems that are most frequently encountered while such a model is being shaped.
Security is a big issue for all developers when writing code. Any senior web engineer is familiar with common security problems like SQL injections, XSS vulnerabilies, LFI, Session poisoning, just to name a few.
We are not going to get into these right now since the web is already full of resources describing how much damage they can do and how to avoid the danger. We all know what they are made of and how they work.
It’s a commonly accepted fact that in order to succeed in something, you have to surround yourself with people and ideas that push you in the right direction. To that effect, I want to make it clear that, when you become a 4PSA Clouder, nothing can stop you from becoming the next rock star in software.
When I started writing code for a living, everything seemed freakishly complex. Why? Because there was no one around to guide me through the rough terrain of learning different APIs at once, to point out the mistakes in my design, and offer advice on how to code better and faster.
Spring’s here, and so is our second problem! Time to enjoy nature, play treasure hunt, and write an App about it. Or vice versa. 🙂
Either way, do not forget about the rules. The deadline to submit your solutions is Tuesday, April 9nd, 10:00 AM GMT. Results must be submitted here.
Johnny is out on a trip together with his friends. They want to have some fun by putting their smartphones to the test. Johnny is the tech oriented kind of person, so he is thinking of writing a phone App for him and his friends to play outdoors.
In a previous article, we described how to choose a HTTP method when implementing operations that affect resources. Today, we are going to explain how to implement services that manage concurrent operations on a resource and how clients should use such services.
Sometimes, Apps must handle concurrent updates on a resource. Just imagine an application that acts like a Wiki, where users read, write, and edit articles.
