🎁 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 Fortiro Fortiro is a fintech whose AI-powered platform helps leading banks and financial services customers in Australia, New Zealand, and globally detect financial crime and automate verification in lending and insurance. Role Mission Fortiro’s platform underpins fraud detection for major banks and financial services customers operating to 24/7 SLAs. The Technical Support Engineer is the first line of response on our platform support team: owning the alert queue, investigating in CloudWatch and OpenSearch, resolving what the runbook covers, and escalating cleanly when it doesn’t. Key Responsibilities Own the alert queue during rostered windows: acknowledge, triage, and drive each alert to resolution or escalation within SLA. Investigate directly in AWS CloudWatch and OpenSearch, using knowledge of the platform architecture including but limited to ECS, Step Functions, Lambda, SQS/SNS, RDS, and S3 to know where to look first. Execute runbooks precisely; log every action for audit and post-incident review. Escalate with a clean handover: symptoms, evidence, actions taken, business impact. Cover a rotating shift pattern including evenings, weekends, and public holidays to protect enterprise SLA commitments. Coordinate incidents through to mitigation and contribute to post-incident reviews. Partner with the Cloud Observability Engineer to flag noisy alerts, missing signals, and candidates for automation. Maintain and grow the runbook library, escalation matrix, and known-issues log. What you’ll bring to the role Experience in a technical support, NOC, SRE-adjacent, or platform operations role in a SaaS or cloud environment. Hands-on with AWS CloudWatch (metrics, alarms, Log Insights) and OpenSearch / Elasticsearch (queries, tenant/request filtering, cross-service correlation). Ability to hold a mental model of a distributed system and reason from symptoms to likely source before opening a runbook. Working familiarity with AWS core services: ECS, Lambda, Step Functions, SQS/SNS, RDS, S3. Strong triage instincts and disciplined runbook execution; clear, calm written communication under pressure. Basic scripting (Bash, Python, or similar) for repetitive investigation steps. Availability to work rotating evenings, weekends, and public holidays. Bonus: exposure to financial services, fraud detection, or regulated SaaS. Why Fortiro Impact: Support the platforms that protect major banks from financial crime. Growth: Clear path into SRE, observability, or platform engineering as the business scales. Culture: Inclusive, flexible, hybrid working with a long-term investment in our people. No recruitment agencies please. We have this covered and will reach out if we need support.
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.
