Senior Front End Engineer

How we work:

Our entire engineering team works in 6 week cycles. Each developer is assigned to one or more projects during this cycle and aims to deliver the project together with other project team members from various other teams. In addition to working on projects, we also focus on other tasks - not limited to working on our backlog, providing an L3 support to our client facing colleagues or making improvements to our product through an initiative called “Happy consultants”.
In order to keep our high quality standards, each change in code we do gets reviewed and our automated pipeline builds these changes, runs a series of tests, runs the linter, packages the outputs and deploys them onto a development environment.
We are a team of diverse skill sets - you will need to share your experience and knowledge (during code reviews and ideally also beyond) with other colleagues and help them grow just like we all will help and support you from the minute you join us.

Challenges:

Here are some of the challenges that kept us busy in the past:

• Micro frontend research
• Our application is split up into modules but we are experimenting with the idea of loosening up the coupling even a bit more and splitting our large application into a collection of smaller ones run under a single container application.
• Identify the pros and cons of this approach and what problems will it solve effectively and what other problems it might bring.
• Take into account how this switch potentially affects not the architecture alone but also the execution, deployment and DX.
• Optimizing build performance
• The larger an application gets, the more complex the build becomes. Our application consists of hundreds of components, directives, services, pipes and other functions.
• Find a way to optimise the build in order to make the DX and the pipeline build performance better.
• Optimizing change detection
• Our application aims to deliver a swift interaction experience to its users without the feeling that something is lagging.
• Identify components that are underperforming.
• Analyze their bottlenecks using the profiler.
• Optimize the runtime performance of the problematic code parts.
• Data visualisation
• Our real-time analyses like trends, funnels, reports, and segmentations allow users to gain insights about their data from multiple perspectives. We integrate with external data sources spanning multiple relational databases and big data storage systems.
• Build an interface for users to query data from data sources located outside of the Engagement to build the basis for our analyses and visualizations.
• Create complex data visualizations using the Highcharts library or similar suitable tool.
• Be proactive in proposing solutions which will help users to better understand their data.
• Improve test quality and extend test coverage.
• Extend UI library
• We have created a mature UI library with the goal in mind to unify the look, behavior, and the API of our reusable components. This library already consists of a solid foundation of components but the innovation in the Engagement goes hand in hand with the need to create new components and enhance existing ones.
• Create new reusable components while focusing on clear API, stability, best possible UX and modern browser support.
• Test your component well. Use unit tests to cover all thinkable and unthinkable scenarios your component may go through to make it robust.
• Other than that…
• We work hard to have sustainable code, but we still have some code in our codebase, especially from the early startup era, that was written in haste to keep the business running - you will need to be able to get around in complex code and help us refactor it.
• Automated testing of our code is important to us. You will need to cover your code, help us improve existing test quality and extend overall test coverage - spanning from unit tests, through integration tests to automated e2e tests.

#LI-KP1