🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Java Application Support Engineer (L2/L3) Insurance Domain Experience: 24 Years Location: Jaipur (Onsite) Employment Type: Full-time Notice Period: 30 Days We are seeking a Java Application Support Engineer (L2/L3) who will support and enhance a business-critical application for a client in the Insurance domain. This role requires a strong backend Java developer mindset combined with hands-on experience in production support, incident management, bug fixing, and minor feature enhancements. You will work closely with business users, QA, and senior engineers to ensure system stability and continuous improvement. Key Responsibilities Provide L2/L3 application support for Java-based enterprise applicationsInvestigate, debug, and resolve production incidents, defects, and performance issuesPerform root cause analysis (RCA) and implement permanent fixesHandle incident tickets, change requests, and service requests within defined SLAsImplement bug fixes and small-to-medium feature enhancementsSupport business users and client stakeholders with technical clarificationsWork on REST APIs, backend logic, and database-level issuesAssist in deployments, patch releases, and hotfix roll outsMaintain technical documentation and support run booksTake ownership of assigned modules and ensure production stability Requirements Required Technical Skills Strong experience in Java (Core Java, OOP)Hands-on experience with:Spring Framework / Spring BootRESTful Web ServicesHibernate / JPAExperience supporting JSP-based applications and Spring Web FlowStrong working knowledge of RDBMS:MSSQL (preferred)MySQLPostgreSQLAbility to analyse logs, stack traces, and database issuesBasic understanding of HTML, CSS, JavaScript (for UI-level issue analysis) Cloud & DevOps (Good to Have) Exposure to AWS services:S3, SQSCodePipeline, CodeCommit, CodeBuildFamiliarity with CI/CD and deployment pipelinesExperience working in production environments Domain Knowledge (Good to Have Strong Advantage) Prior experience in the Insurance domainUnderstanding of concepts such as:Policies, Coverages, PremiumsUnderwriting, Claims, EndorsementsPolicy lifecycle and renewals (Candidates with insurance domain exposure will be given preference.) Soft Skills & Expectations Strong problem-solving and analytical skillsClear and confident communication with business users and clientsHigh sense of ownership, accountability, and responsibilityAbility to work under pressure in production support scenarios BenefitsWhy Join CipherCru Innovation Exposure to enterprise insurance systemsHands-on ownership of real production applicationsBalance of support + development, not just ticket handlingOpportunity to grow into senior support or backend engineering roles .
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.