Midlevel Fullstack Java Developer

Role: Midlevel Fullstack Java Developer

Skills: Java, React/Angular, HTML5, CSS3, JavaScript

Location: Frankfurt Germany

Type: Permanent We are at Coforge hiring for Midlevel Fullstack Java Developer with Java, React/Angular, HTML5, CSS3, JavaScript Job Description: Seniority Level: Medium (Level 2) – This is a mid-level developer role requiring at least 4 years of experience in the software developer role. Level 2 developers have deep knowledge of the project’s technical and business requirements and are capable of independently executing development tasks, managing quality for their work, and solving complex problems within their scope. They can organize and prioritize their own activities (and assist others) to meet agreed tasks and deadlines.

Required Skills & Qualifications: Level 2 Software Developers are expected to fulfill the same core skill requirements listed above for Software Developers in this call-off (expertise in Java backend development, RESTful APIs, databases, front-end frameworks, DevOps practices, agile methods, automated testing, etc.). In the proposal evaluation, each proposed developer must meet at least 5 of these skill requirements, with additional skills beyond five providing a higher score. (Level 2 developers should meet these requirements at a solid intermediate level, whereas Level 3 developers exhibit advanced mastery and possibly additional breadth/depth of experience.) Key Responsibilities: Software Developers at Level 2 carry out hands-on development and testing tasks to build the required digital euro testing support tools.

Their responsibilities include: Software development and maintenance – Implement assigned features and components of the project’s software deliverables (the simulator backend, EAT test tools, and member portal) in accordance with the technical specifications. This involves coding in Java (and relevant frameworks), developing front-end functionalities for the web portal, and integrating databases and external services as needed. Level 2 developers focus on writing efficient, secure, and well-documented code for their modules.

Customization and testing – Customize and configure existing tools or frameworks for the CLIENT’s purposes (for example, tailoring market-standard testing tools for the EAT processes). Conduct unit and integration tests for the functionalities they develop, contribute to automated test development, and fix bugs or issues discovered during testing to ensure the deliverables meet quality standards. They collaborate with Level 3 developers to incorporate feedback from code reviews and improve the robustness and performance of the software. Collaboration and agility – Work as part of an agile delivery team (using Scrum/SAFe/Kanban practices), closely cooperating with colleagues and the CLIENT’s project team. Level 2 developers are expected to be 50% on-site in Frankfurt (with advance notice) and 50% remote, as needed. They participate in daily scrums, sprint planning, and progress meetings, providing updates on their tasks and ensuring alignment with project timelines. They also assist in knowledge transfer by maintaining technical documentation for their components.

Expected Deliverables/Outputs: Level 2 developers contribute to the same major project deliverables – the Digital Euro Simulator, EAT Testing Tools, and DESP Member Portal – working under the guidance of Level 3 developers to complete these on schedule (see timeline above). In addition, each Level 2 Software Developer is expected to produce: Functional software modules assigned to them, delivered as part of the overall solution (e.g. portions of the simulator backend, test tool configurations, or portal features) with all required source code and binaries.

Unit and integration test cases and results for their code, contributing to the project’s automated test suite and ensuring that their work meets the acceptance criteria and quality benchmarks. Technical documentation for their implementations (inline code documentation, design notes, user guides for components, etc.), so that the delivered software can be understood and maintained by CLIENT teams post-project.