Lead Software Engineer

Lead Software Engineer

7+ years' of experience working as a software developer. Strong proficiency in Java. Strong experience in building applications that interact with relational databases using SQL. Some experience of Enterprise Java (J2EE / JavaEE / Spring) application architectures. History of delivering high-cadence modern applications with applied Agile methodologies, test-first development approaches, adopting CI/CD pipelines and using Git version control.

Working knowledge of microservices architectures and Domain-Driven Design approaches. Some experience and knowledge of Python. Some experience and knowledge of JavaScript/Node.js. Some experience and knowledge of ORMs like Hibernate or JPA.

Be open to adopting new technologies and approaches on projects as they evolve, especially those relating to GenAI advancements. Stay at the forefront of the industry by staying abreast of the latest GenAI advancements and leveraging cutting-edge developments to fulfill migration projects. Participates as a software developer on small Agile teams, delivering software-based solutions for migrating and modernizing customer legacy applications to MongoDB. Follow existing best practice migration playbooks where applicable and be prepared to innovate to fill in gaps with creative solutions to solve challenges on each specific project. Actively participate in sprint grooming, planning, and showcases with ideas and suggestions. Take direction from the technical lead and project manager on projects, raising identified challenges and potential solutions to the team when applicable. Study the current state of each legacy application and the desired target state outlined by the customer and contribute to the planning, design, and solution from getting from source state to target state on each project. Be prepared to change project direction if customer or account team priorities change.

Please reply with your updated resume and required details: Full Name: LinkedIn ID (Must To have as per exp) Best number to reach you: Work authorization/Visa Status: Current Location: Current Compensation: Expected Compensation: Best time to call you: Waiting for your earliest response

Modernization Factory: Developer Candidate Challenge

Migrate a specific legacy JBoss Java application to a more modern platform according to the following directives:

• The application for you to migrate is the'kitchensink ' JBoss application available in the Red Hat JBoss EAP Quickstarts GitHub repository (no need to migrate any of the other applications listed there). Please use git clone when pulling this from the command line.
• The migrated application runtime you must target is the latest stable version of Spring Boot or Quarkus (your choice) based on Java 21 (you can host the running application on your laptop, in the cloud, or wherever - you don't need to target OpenShift as the host environment necessarily, which the application's README discusses in places).
• Create a new personal public GitHub project and host the source code for your new migrated application there (for just 'kitchensink' only). Include a new README where you outline the steps a developer would need to take to build and run your migrated application.
• Try to approach this migration process in the way you might do if the legacy application codebase was far larger, in terms of how you break up the problem into more management tasks, addressing the sort of infrastructure, scaffolding, and software engineering principles you would need to apply to help mitigate risk in the migration work and ensure the quality of what is migrated (during the subsequent playback session, you will be asked questions on the approach you took).
• OPTIONAL STRETCH GOAL: Modify the application to work against a MongoDB database rather than the existing relational target database.

1.5-hour presentation on Zoom to a few MongoDB staff where you will:

• Deliver a live demo of the running migrated application.
• Show what you did under the covers to perform the migration with examples of components you changed to highlight the processes you took.
• Outline any interesting aspects you learned from this process that would inform your approach to a future migration project.
• Answer questions from the interviewers on what you achieved in the migration, how you went about it, and other insights you've learned.
• Toward the end of the session, respond to any other more general interview questions you are asked.

Thanks & Regards ====== Salman Shaikh View phone number on click.appcast.io (Cell) Boston, MA View email address on click.appcast.io