What I Tell Myself On A Bad Day

Content Backend Software Develo... D-Orbit Lisboa, Portugal in Candidatura simplificada Salvar Qualifications and Requirements Strong experience in Python programming (at least 3 years): Knowledge of asynchronous programming: Strong knowledge about Pythons' unit testing frameworks (preferably pytest); Experience in the use of Cython library for generation of python extensions; Strong experience in Java programming (preferable experience in Kotlin): Experience in maintaining Java based web applications: Strong experience in C programming; Strong experience in the use and design of REST APIs; Strong experience on event-driven architectures (pubsub pattern); Strong familiarity with Git distributed version control system; Strong experience of the use of commandline of the Linux based operating systems; Strong experience in debugging distributed applications potentially running in remote environments: Experience in agile development methodologies (e.g.. Scrum, TDD); Experience with applications that handle large datasets: Experience in implementing caching mechanisms (i.e., using Redis); Experience in NoSQL databases such as Cassandra and Redis; Experience in relational databases, namely PostgreSQL: Experience using Kafka, MQTT and Redis as message brokers: Experience in cloud-based environments, namely AWS; Experience in the definition and use of Docker containers; Experience in orchestration of docker containerized microservices using Kubernetes; Some experience in working under DevOps oriented methodologies: Pipeline definition: Test execution automation; Some experience in web application development using the microservices architectural paradigm; Experience in designing web-based applications considering the need for scalability, reliability and security; Experience with Jira framework: Experience of bash shell scripting; Experience in JavaScriptTypescript: Experience in authentication and authorization mechanisms; Experience with event bus technologies (e.g., Kafka);

Content Fix the bug Delete the automated test that caught the bug

The modern developer's tactical retreat. When Slack notifications keep pinging while you're trying to hunt down that elusive race condition, sometimes you gotta go full spec ops and "accidentally" disconnect. Nothing says "I need four uninterrupted hours with this code" like the sweet silence of appearing offline. The digital equivalent of hiding in the server room with the lights off. Mission critical: fix bug. First objective: escape the meeting invites.

Content STOP Stop scrolling. I'm here to remind you about the bug vou have to fix

Nothing says "I love my job" quite like scrolling through OpenAI's entire ad tracking infrastructure at 2 AM. Every single class name screaming "ads.data" like a dystopian poetry collection. ApiAdTarget, BazaarContentWrapper, SearchAdsCarousel—it's like someone took the concept of targeted advertising and made it into a Java package naming convention. The forced smile says it all. You're not debugging critical infrastructure. You're not optimizing algorithms. You're knee-deep in ad tech for an AI company, trying to figure out why the BazaarContentWrapper isn't wrapping content from the correct bazaar. Your CS degree feels like it's watching you through the window, shaking its head in disappointment. But hey, the stock options are great, right? Right?

Finally, a candidate with the courage to list the skill we all depend on but pretend not to use. While the rest of us write "proficient in algorithm optimization" on our resumes, this legend just wrote "googling." The honesty is refreshing. I've been in this industry for 15 years and still spend half my day asking search engines to fix my broken code. At least this guy won't waste time pretending he memorized the entire documentation.