🎁 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 →
About us :At FIS, our technology and our people are moving forward. We advance the way the world pays, banks and invests. We believe in building inclusive, diverse teams. Together, we innovate to help our colleagues, clients and communities succeed. If youre ready to grow your career and make an impact in fintech, we have one question: Are you FIS About the RoleWe are looking for an experienced Non-Functional Engineer to join a team developing backend payment-processing software for large international banks. Our technology landscape includes legacy applications deployed on IBM WebSphere, modernized Java applications running on Open Liberty, and cloud-native applications deployed on Kubernetes. Our payment solutions are standardized around SWIFT messaging and must meet demanding requirements for performance, scalability, resilience, availability, and operational stability. The Non-Functional Engineer will be responsible for designing, implementing, maintaining, and automating tests that validate the non-functional requirements of our software. You will work closely with architects, developers, DevOps engineers, and other stakeholders to identify bottlenecks, investigate failures, and improve the overall reliability and performance of the platform. You will also support the analysis and resolution of non-functional issues reported by customers in production environments. What You Will Be Doing- - Define test approaches and test scenarios for non-functional requirements, including: - Transaction throughput - Network bandwidth and data volume - Response times and latency - Scalability - Resilience and fault tolerance - High availability and recovery - Resource consumption - Stability under sustained load - Behaviour during infrastructure or dependency failures - Create, maintain, and execute automated non-functional test suites for: - Legacy Java applications running on IBM WebSphere - Java applications deployed on Open Liberty - Cloud-native applications running on Kubernetes - Translate architectural and business requirements into measurable non-functional acceptance criteria. - Develop realistic workload models that represent payment-processing patterns used by large banks. - Validate application behaviour under normal, peak, stress, endurance, and failure conditions. - Automate the provisioning, execution, monitoring, and reporting of non-functional tests. - Integrate non-functional testing into Maven and Jenkins-based CI/CD pipelines. - Analyse application, infrastructure, JVM, network, and container-level metrics to identify bottlenecks and abnormal behaviour. - Use logs, metrics, traces, and test results to perform root-cause analysis. - Work with architects and developers to diagnose and resolve issues identified during non-functional testing. - Reproduce and investigate performance, capacity, resilience, and stability issues reported by customers. - Provide clear test reports containing: - Test objectives and assumptions - Environment and configuration details - Workload characteristics - Results and observations - Identified bottlenecks - Risks and limitations - Recommended corrective actions - Establish performance baselines and detect regressions between software versions. - Contribute to standards, reusable test components, automation frameworks, and engineering best practices for non-functional validation. - Support capacity planning and provide evidence-based recommendations for application and infrastructure sizing. Required Qualifications - Strong experience with non-functional, performance, load, stress, scalability, or resilience testing. - Experience designing automated tests for high-volume backend or distributed systems. - Robust knowledge of Java applications and the Java Virtual Machine, including: - JVM memory management - Garbage collection - Threading and concurrency - Connection pools - Heap and thread dump analysis - CPU and memory profiling - Experience testing applications deployed on one or more Java application servers, preferably: - IBM WebSphere Application Server - Open Liberty - Good understanding of cloud-native and containerized application architectures. - Practical experience with Kubernetes, preferably standard or vanilla Kubernetes distributions. - Experience with CI/CD and build automation tools, particularly: - Jenkins - Maven - Experience using observability and analysis platforms such as: - Grafana - Kibana - Elasticsearch - Ability to analyse application logs, infrastructure metrics, JVM statistics, and distributed-system behaviour. - Good scripting or programming skills for test and workflow automation. - Good understanding of networking concepts relevant to non-functional testing, including: - Bandwidth - Latency - TCP connections - Load balancing - Timeouts - Retries - Network saturation - Experience working with relational databases, messaging systems, REST APIs, or other backend integrations. - Strong analytical and .
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.