And because we know technical excellence is hard, we offer unparalleled support for our employees.
Join us100% merit-based environment in a team of passionate professionals
that help and teach each other every step of the way
Access to any learning resource:
courses (Pluralsight, Coursera etc), books, conferences,
internal knowledge sharing sessions, you name it
Challenging projects with the newest technologies and technical freedom
to choose the best architecture and tools for the job
Unlimited home office
Flexible working hours
Excellent compensation
correlated 1-to-1 with performance
Open-door policy
Keyword soup:
Typescript Node Angular React HTML CSS SQL/NoSQL AWS HerokuKeyword soup:
.NET Core MVC WPF Windows Services HTML CSS SQL/NoSQL AzureWe try to keep it pretty simple, so we have 2-ish steps:
You can begin the process by applying below.
We're looking forward to hearing from you!
This is a ~15 minute call (phone, zoom, skype whatever) where we ask some (super) basic go/no-go technical questions. We also switch roles and the candidate can ask us similar questions (technical or otherwise). The goal of this call is to establish whether there's a basic fit and we should continue to the interview
The questions are pretty basic and also skewed towards computer science more than a specific technology, see above as to why.
This is a ~1-2h discussion, i.e. there's no code-writing involved, about various topics, in-depth, split in two big parts:
A. General questions. These are not related to a particular technology and will be similar to the ones listed here.
B. Technology-specific questions. These will be tailored to stuff you know For example if you know .NET and React, we'll ask you about the. If you don't know Typescript, we won't ask. Regardless of technology, the questions are mostly (99%) related to principles, mechanisms and design decisions. We have very few (almost none) API questions. Rather, we ask stuff like what is listed here.
99% of the questions are open-ended. We DO NOT ask API or "trivia" questions, those can be looked up. We ask about principles, mechanisms and generally how stuff works. We go into it as deep as we can.
The discussion is two-way: at any point the candidate can (and should) ask us questions, of any kind.
At the end of the technical discussion we always switch roles so the candidate can ask us about, well, anything.
We almost always give a "No" answer straight-away.
In case of a possible "Yes" we will get back with a complete written offer, including compensation, benefits and (often) a concrete learning plan with the gaps we identified during the interview. We'll schedule another meeting to discuss the offer. As with most things in life, most everything is negotiable, however we (as mentioned previously) try to be as fair as possible and our offer reflects it. In fact, many times, having known a candidate's expectations in advance, we presented a better offer as we felt the candidate was deserving of it, according to our company's reference system (that is to say, the compensation of our existing colleagues).
If you got this far, thank you!
I hope that by now most questions you might have had have been
cleared up and your interest is piqued. If you feel you resonate with our
values and culture and would like to apply please:
As a final note: we're ALWAYS looking for talented and passionate people to join us, regardless of whether we have work lined up or
not. So, the job postings on the website are almost perennial. Still, if you're in doubt about them, or feel you have a unique talent or
would simply like to talk to us, don't hesistate to write us, we're happy to chat.
My work, my passion. In God we trust all other we test!