Role: Software Engineer Java/Kotlin Experience: 5+ Years Location: Singapore KEY FEATURES OF THE POSITION Functional / Technical Communicate highly technical issues to non-technical audience. Earn good reputation of being technically strong in the organization by help solving problems others struggle Development and delivery with Java/Kotlin, EJB, Spring Boot, MySQL, Oracle and IBM MQ. Understand business / system requirements and translate them into technical solutions that are scalable, stable and fit for purpose. Tackle very complex legacy defects that mediocre developers cannot analyse/solve. Ensure adherence to the bank standards (including code, security and performance). Passionate about technologies and building robust and scalable Java Systems. Analysis, design coding, and implementation of complex and custom-built applications. Work collaboratively with team to achieve goals. Experience working in Agile methodologies, such as Scrum, and/or Extreme programming. Investigate and resolve production issues to help maintain a stable production environment; remain cool and effective in crisis. Regulatory Responsibilities &/OR Risk Management Demonstration of appropriate values and behaviours including but not limited to standards on honesty and integrity, due care and diligence, fair dealing (treating customers fairly), management of conflicts of interest, competence and continuous development, adequate risk management, and compliance with applicable laws and regulations Take responsibility for ensuring that risks and issues are identified and managed closely and drive all stakeholders to deliver on time and to the required quality standards SKILLS REQUIREMENTS OF THE POSITION Professional and Technical Professional Well organized and ability to prioritise and carry out multiple tasks Able to influence and drive projects to meet key milestones and overcome challenges Able to translate functional requirements to efficient and fit-for-purpose technical solutions Preferably, have experience in finance/banking or public sector domain. Technical Must Have : Core Java / Kotlin and JUnit. Spring Boot Strong computer science knowledge (algorithms, data structures, object-oriented design) TDD. Able to write acceptance test. Basic Linux shell scripting commands Java Messaging Concepts. (JMS, MQ) Relational Database concepts, SQL, joins, index, triggers etc. Web Services Rest, SOAP. Spring core concepts. Experience in SQL queries optimisation Basic DevOps and AWS cloud experience (CI/CD, containerisation, common AWS services) Familiarity with Intellij, Git, SonarQube/SonarLint Desirable : JBOSS (or any other application server knowledge). Java Server Faces, JPA, EJB knowledge. Able to write/understand complex SQL queries. Kafka React JS Personal and Social Good communication skills Good work ethnics and punctuality Good problem-solving abilities Good team player
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.