Systems Analyst

About the role

Anza runs the mortgage-insurance platform that lenders, servicers, and our internal underwriting staff depend on end to end. When something breaks — a screen won't load, an API call returns an error, a partner's file didn't process, an order looks stuck — you're the first person to look at it. This is the front line of our support group. You'll work across a Java backend, a React web portal suite, and an AWS estate instrumented with Datadog.

Responsibilities

• Respond and Investigate: Take first response on production issues from customers (lenders, partners) and internal users, and own each ticket through to closure. Triage by impact and urgency, and route or escalate anything you can't resolve — with your findings attached, not just the customer's words.
• Investigate: Investigate before escalating: reproduce where you can, check the logs and dashboards, and use the runbooks. Work out whether it's a defect, a data problem, an environment issue, or the system working as intended.
• Communicate: Write the customer-facing response: clear, accurate, specific, with a next step or workaround. Adjust for a partner's technical integrator versus an internal underwriter. Keep customers and internal stakeholders updated on anything that stays open, without needing to be chased.
• Raise clean defect reports: steps to reproduce, environment, affected IDs, log links, expected versus actual. Flag recurring problems as patterns, with evidence, so engineering can fix the underlying cause instead of the symptom.
• Support incident response as the investigation and communication arm, and take part in post-incident reviews.

Qualifications

• Minimum Education: Bachelors Degree
• Minimum Skills: Technical support, service desk, QA, systems analyst, or similar role or equivalent hands-on experience in a technical environment where you diagnosed problems rather than just logged them.
• Basic SQL: You can write a SELECT with a JOIN and a date filter against a relational database, and you're comfortable learning more. We'll assess this at a practical level, not a trick-question level.
• Comfort reading logs and error messages: You've searched logs before - in any tool - and you can tell signal from noise.
• Working understanding of how web applications and APIs fit together: Browser, request, server, database. Status codes, JSON payloads, what a 401 versus a 500 means.
• Browser developer tools basics: network tab and console.
• Clear written English: You can explain a technical problem to a non-technical person succinctly, without confusing or patronising them. This is the single most important skill in the role.
• Methodical, evidence-led way of working: You check before you conclude, you're comfortable saying "I don't know yet, here's what I'm looking at," and you don't guess in front of a customer.
• Genuine curiosity and follow-through: You want to know why something failed, and you don't drop a ticket because it got awkward.
• Care and discretion with production and customer data: You'll have read access to real customer and loan data in a regulated environment.

Preferred Skills

• Using an API client like Postman or curl to reproduce a failing request.
• Supporting a B2B product with external technical customers, rather than only internal users or consumers.
• Login and access troubleshooting: SSO, OAuth/OIDC, JWTs, API keys, permission errors.
• Message queues or asynchronous processing: queues, retries, dead-letter queues, and explaining "it hasn't happened yet" to a customer who expected it instantly.
• File-based processing support: SFTP/S3 feeds, batch jobs, per-record rejections.
• Workflow or BPM engines: Camunda, Temporal, or similar - especially diagnosing stuck processes.
• Support tooling: Jira, Jira Service Management, Zendesk, Freshdesk, PagerDuty; SLAs, knowledge bases.
• Any scripting: Python, Bash, or SQL automation.
• Domain adjacency: Any regulated, transaction-heavy industry: financial services, payments, lending, insurance, healthcare, logistics.
• Mortgage or mortgage-insurance exposure is a nice bonus; we fully expect to teach the domain.
• Working in a regulated environment (SOC 2, NYDFS, PCI-DSS or similar) and understanding why the access controls exist.
• A degree in a technical field, or a support/IT certification; neither is required, and practical experience counts equally.