Job Description:
We are urgently seeking a highly skilled Full-Stack Developer with expertise in Java 11 and Angular 15, with extensive experience in API integrations, specifically with the Amadeus Quick Connect (AQC) API. This role requires a developer who can handle both backend and frontend tasks to resolve critical issues in our flight booking flow. Additionally, the developer must collaborate with a web design team to improve the existing UI based on a Figma project. The team should have strong experience in CSS and web design to ensure that the design enhancements are implemented effectively. The system is currently live in a production environment, and we need someone who can quickly identify and fix the problems to ensure smooth operation.
Project Overview:
Our flight booking system, built on a MongoDB database, is experiencing several critical issues. Please note that the implementation is already in place; however, we suspect that it has been done incorrectly and is not fully compliant with the integration documentation provided by Amadeus. The specific issues needing attention include:
- Invalid PNR Generation: The booking process is generating invalid Passenger Name Records (PNRs) in Amadeus AQC, preventing successful completion of reservations.
- Baggage Options Integration: There are issues in how baggage options are retrieved from the Amadeus AQC API and integrated into the front-end, which is developed in Angular 15. These options need to be correctly processed and stored securely in our MongoDB database.
- Checkout Flow Errors: The booking flow from pre-reservation with a timeout on the checkout page to final reservation post-payment (via Stripe) is not functioning correctly. Data errors during this process are leading to failed or invalid bookings.
- Offer Retrieval Time Improvement: The current time to retrieve offers fluctuates between 8 and 15 seconds, which is unstable and exceeds acceptable limits. You will need to identify and implement solutions to improve this retrieval time to a maximum of 5 seconds.
- Passenger Type Search Issues: There are problems when retrieving search results for different types of passengers (e.g., adult + infant = 0 results). This issue needs to be thoroughly investigated and resolved to ensure accurate search results.
In addition to resolving these issues, the developer will work closely with a web design team to implement improvements to the existing UI. The developer's team must have substantial experience in CSS and web design to ensure the frontend enhancements align with the design specifications provided in the Figma project.
Responsibilities:
- Analyze and debug the existing codebase, focusing on identifying any deviations from the official Amadeus AQC API integration guidelines.
- Correct any issues in the current implementation to ensure compliance with Amadeus's documentation and best practices.
- Ensure that baggage options retrieved from the Amadeus AQC API are correctly processed, stored securely in our MongoDB database, and seamlessly integrated into the Angular 15 front-end.
- Resolve the issues in the checkout flow to ensure that pre-reservation, payment processing, and final reservation steps work flawlessly together.
- Identify and implement solutions to improve the offer retrieval time to a maximum of 5 seconds, ensuring consistent and stable performance.
- Investigate and fix issues related to retrieving search results for different types of passengers (e.g., adult + infant).
- Collaborate with a web design team to implement UI improvements based on Figma specifications, ensuring high-quality design and responsiveness across devices.
- Ensure that the development team has strong experience in CSS and web design to effectively apply design enhancements.
Requirements:
- Extensive experience with Java 11 development.
- Proven expertise in integrating and troubleshooting the Amadeus Quick Connect (AQC) API.
- Strong experience with Angular 15 and the ability to handle complex front-end integrations.
- Solid experience with MongoDB, with a focus on secure data storage and retrieval.
- Experience optimizing API performance and reducing latency in offer retrieval.
- Ability to troubleshoot complex issues, particularly with passenger type searches.
- Strong understanding of both backend and frontend development, with the ability to work in a live production environment.
- Experience with payment gateways, particularly Stripe, is a plus.
- Strong experience in CSS and web design, with the ability to collaborate effectively with design teams.
- Ability to work under tight deadlines and deliver high-quality results quickly.
Deadline:
This project must be completed by September 1st. Please only apply if you are confident in your ability to meet this deadline.
How to Apply:
Please provide examples of previous work, particularly related to API integrations, performance optimization, and any specific experience with the Amadeus AQC API, Angular 15, MongoDB, CSS, and web design. Include a brief overview of how you plan to approach solving the issues mentioned above.
We look forward to collaborating with a talented developer who can swiftly resolve these critical issues and ensure our booking system runs smoothly.
Testing and Acceptance Criteria:
Testing will be conducted in collaboration with the developer via recorded videoconference sessions with screen sharing. During these sessions, the developer will demonstrate that the fixes for PNR generation, baggage options integration, offer retrieval time, and passenger type search issues are correctly implemented and functioning as per the Amadeus AQC API documentation. The results will be validated against expected outcomes, including successful booking completion and correct retrieval of offers within the targeted time of 5 seconds. The booking flow must be fully functional and stable across desktop, tablet, and mobile devices, with testing required across major browsers—Safari, Chrome, Mozilla, and Edge—to ensure consistent performance and responsiveness.
Security and Intellectual Property:
Access to the source code will be provided through security measures established by the client. The source code, both existing and newly written by the developer, remains the exclusive property of the client. The developer acknowledges that they have no rights to the source code and that it has always been, is, and will continue to be the property of the client.
Delivery and Payment Terms:
The project has a strict deadline of September 1st, with an additional 48 hours allotted for final acceptance testing (including testing and debugging). If the developer fails to meet the agreed deadline, a penalty of 3% per day of the total project cost will be applied until the work is completed and accepted by the client. The project will be managed under a formal contract and a Non-Disclosure Agreement (NDA). The client does not accept negotiation regarding the payment mechanism or the deadline. Payment will be made per project, divided into milestones, which will be agreed upon with the developer. Payment for each milestone will be made after the progress is uploaded and tested in the production environment.
Confidentiality and Non-Disclosure Agreement (NDA):
The developer agrees to adhere strictly to the terms of the Non-Disclosure Agreement (NDA) associated with this project. This includes, but is not limited to:
- Prohibiting any discussion or sharing of the project details with third parties.
- Ensuring that any technology, design, or code developed for this project is not reused, repurposed, or disclosed in any other projects without the express written permission of the client.
- All information and materials provided during the course of the project must be handled with the highest level of confidentiality and returned to the client upon completion or termination of the contract.
Final Note:
All deliverables must strictly adhere to the Figma project specifications. No new code will be written from scratch; the existing production page will be modified accordingly. This project is limited to the client's homepage, covering web, tablet, and mobile responsive views.