Data Engineer
Brno
Tracab – Engineering /
1. Full-Time /
On-site
We are looking for one Senior and one Junior/Mid Data Engineer to help us build our products driven by our customer’s expectations - reliability, effectiveness and robustness of code are key achievements.
A Data Engineer will be developing Python modules to extract, transform and load data provided by external data vendors. It is a person with a passion for clean code, reliable architecture, code readability and testing coverage, adopting a highly consistent working style, willing to identify, solve production issues, and learn from them.
If you have a solid background in system and software engineering and are familiar with the Python language, we’d like to meet you.
Must Haves
- System and software engineering experience (seniors) / education, or at least interest (juniors)
- (Seniors) ability to design secure and highly-available code
- Ability to understand and analyze existing data flows and processing and be able to migrate them from the legacy architecture
- Algorithmization and scripting ability (primarily Python, PowerShell, C#, Perl or any other programming language is a plus)
- Experience (seniors) / basics and willingness to learn (juniors) with industrial standard processes
- (Seniors) ability to perform root-cause analysis / (juniors) problem-solving attitude
Nice to Haves
- Development industry experience
- Cloud systems and processes experience - design procedures for troubleshooting, preparing run books, executing game days, running chaos monkeys, feature flagging, canary releases
- A fan of the post-mortem (lessons learned) culture
- Experience with large-scale or distributed systems, SOA
- Soft-skills - communication, project management skills
- Keep pace in a fast, constantly changing environment - old (systems, technologies, procedures) is discarded and new is implemented constantly, changes are implemented as we constantly grow and learn
Not to Haves
- The position is not suitable for a person who is in general not thinking in a long term:
- With not a systematic approach, e.g. unwilling to follow the process, make documentation, blind to repeating issues, preferring manual-repeated work over automation
- With “It works for me”, or “fixed, let’s forget about it” mindset
- Satisfied with doing tasks in a hacky - tech-debt introducing way, for example, finishing things until the state they “somehow works” and moving on without getting the technology under control
