Investigation Engineer

We’re currently expanding our Support Team and we’re looking for a new colleague to join as an Investigation Engineer, who excels in problem solving skills, can think critically and who enjoys analyzing clues from all possible angles. The salary starts at €1,800 with stock options and other benefits included, working in one of our Central Europe offices or from home on a full-time basis. Are you up for the challenge?

Tasks and responsibilities:

• Diagnose and investigate technical issues from a backend and platform infrastructure perspective, being on the second line of Support.
• Test, troubleshoot and debug application code base
• Work closely with Engagement platform specialists, Technical consultants, Business consultants by helping them to resolve technical issues and guide them through problem solving process
• Communicate the results of investigation back to internal and external clients

What we expect of the candidate:

• Capability to quickly recognize and triage a technical problem
• Understanding of programming (algorithms, conditions, cycles)
• Drive to keep things organized when working on multiple different tasks every day

• Ability to communicate with both technical and non-technical people
• Basic understanding of JS
• Experience with at least 1 programming language
• Understanding high level architecture of Software
• English language (advanced or native level)
• Broad understanding of internet technology (front-end, back-end, API, network requests)

Nice to have:

• Bash scripting
• Knowledge of cloud architecture
• Experience with Kubernetes or Docker
• Experience with SQL or NoSQL databases
• Experience with Python or Javascript
• Knowledge of ticketing systems (f.e. Jira or SalesForce) 

Our Daily challenges

Investigating issue - 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 a 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.

Escalation - 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 evaluated properly.

You look into the back-end code, but you are not sure what is happening.

Don't worry, you can 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.

They 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.

What you might like about this role:

Opportunity to learn and master new technologies (Google Cloud Platform Kubernetes, Google BigQuery) and get knowledge from various areas (data analysis, backend system integrations)

Cooperating closely with the developers in order to improve stability of platform, with a possible career path leading to Developer or Technical consultant

Regional benefits:

Monthly lunch entitlement by up to 110€ per month

Pension scheme or Health insurance depending on region