Software Engineer

The role of a Junior Developer is to produce quality technical solutions to problems outlined by the Engineering Manager and Product Owner. This person works within a team, as any other developers.

They write good quality test and production code with little supervision. They have the knowledge to use the right design pattern at the right time and follow best practices like SOLID and dry principals with minimal support.

A Junior Developer works on concrete topics as any other team members, but the delivery is slower than a Core Developer because of the lack of experience and expertise in some technologies and the lack of commercial awareness.

The primary differences between a Junior Developer and a Core Developer are both the expectations of velocity as well as the amount of effort required to produce a stand-alone solution.

Key Responsibilities

Building software applications

• Is responsible to build software applications by using relevant development languages and applying knowledge of systems, services and tools appropriate for the business area

• Is responsible to write readable and reusable code by applying standard patterns and using standard libraries

• Is responsible to refactor and simplify code by introducing design patterns when necessary

• Is responsible to ensure the quality of the application by following standard testing techniques and methods that adhere to the test strategy

• Is responsible to maintain data security, integrity and quality by effectively following company standards and best practices

End to End System Ownership

• Has sufficient knowledge to own a service end to end by actively monitoring application health and performance, setting and monitoring relevant metrics and act accordingly when violated

• Has sufficient knowledge to reduce business continuity risks and bus factor by applying state-of-the-art practices and tools, and writing the appropriate documentation such as runbooks and OpDocs

• Has sufficient knowledge to reduce risk and obtain customer feedback by using continuous delivery and experimentation frameworks

• Has sufficient knowledge to independently manage an application or service by working through deployment and operations in production

Technical Incident Management

• Is responsible to address and resolve live production issues by mitigating the customer impact within SLA

• Is responsible to improve the overall reliability of systems by producing long term solutions through root cause analysis

• Is responsible to keep track of incidents by contributing to postmortem processes and logging live issues

Architectural Guidance

• Has basic knowledge to advise product teams towards a technical solution that meets the functional, nonfunctional & architectural requirements by challenging the rationale for an application design and providing context in the wider architectural landscape

• Has basic knowledge to set a clear direction for a technical capability by evaluating and aligning the target architecture improvements, reframing architectural designs and decisions for varied stakeholder

Software Systems Design

… lees de volledige omschrijving bij Booking.com.