id: MTAwMDAwMDAxNTUyMTUwMCA0MQ

reference: 1000000015521500

documentId: 1000000015521500

connectionPointId: 41

Názov práce:
Vývojári a analytici softvéru a aplikácií inde neuvedení

Popis práce:
Our team:
We’re quite a new team in Exponea, born out of the need to keep pace with our growing customer base. Our goal is to quickly react to incidents in our application. What is an incident? It is when a particular functionality is experiencing downtime, under-performing, or cannot be used properly. The goal is to quickly recognize such a situation, judge its severity and then take care of its resolution — either by ourselves or by asking for help from other engineering teams.

Competencies:
Incident engineer is a position suitable for people who either like having a wide area of knowledge or who haven’t yet decided on their specialization. As an incident engineer, you’ll deal with multiple product areas of Exponea from different perspectives – sometimes as a customer, sometimes as a developer, all while continuously learning about our stack, our marketing technologies and our customers.



Must have:
Capability to quickly recognize and triage a technical problem
Ability to read and understand Python code
Experience with SQL or NoSQL databases
Drive to keep things organized when working on multiple different tasks every day
Ability to communicate with both technical and non-technical people


Nice to have:
Python, Bash scripting
Knowledge of cloud architecture
Experience with Kubernetes or Docker

Our Daily challenges:

Downtime – Application Error in List of Imports:

A client contacted our Customer Support with a peculiar problem. Every attempt to display a list of imports into our app fails with an error. The support team finds that our back-end is returning a mysterious “KeyError” during the attempt to fetch the list of imports. They contact you as the second line of IT support and they are asking for help with pinpointing which import is causing the trouble.
You check the application logs to no avail, so you devise a short Python script which simulates front-end request for fetching the list of imports.
You catch the error, extract the import ID and look into the database to see its definition.
Here it is: The import definition dictionary is almost empty. Of course it was returning “KeyError”
You delete the invalid record, contact the client and tell them that you fixed the problem, and contact the dev guys responsible for this component so that they can investigate what happened.
Done. The client is happy.

Incident – Personalization is sometimes not working in email campaigns:

A client is trying to use personalization in an email campaign. It seems like it works everywhere except for the conditional part of the email campaign. In the application logs you find that the Jinja code is not evaluating properly.
You look into the back-end code, but you are not sure what is happening.
No worry, you contact one of our dev teams.
There is a guy (and a few girls) who specialize in this part of our system. It seems that the latest change introduced a bug. He will take care of it now.

Feedback to Devs and Product team:

Since the release 2 weeks ago, you’ve noticed that there are a few similar problems – API calls sometimes don’t respond as they should and there’s more errors reported than normally. Up until now, you’ve handled these on a case-by-case basis. But now it’s time to resolve this more systematically.
You write down common aspects of these similar cases and then it hits you – it seems to be a Kafka issue.
So you decide to focus on this particular problem for the whole afternoon – to gather data, set up metrics and maybe do a short load test. And there it is – there’s a particular problem with our Kafka setup that happens under load.
It’s not urgent, but it’s important. So you meet with the responsible dev team, discuss the problem – in the end, they plan to write the fix during the next week.

numberOfPosts: 2

jobCategoriesCodes_0: http://data.europa.eu/esco/isco/C2519

abstractJV_contact_0:
, , lenka.filova (at) exponea.com, lenka.filova (at) exponea.com Mgr. Lenka Fiľová

positionTypeCode: directhire

Meno zamestnanca: Exponea s.r.o.

employer_website: www.exponea.com

source: ISSZ