KASHII UPDATEZ Everyday Student Requirements & Python Coding Tutorials by Python Kashi
S #2604
Applications open Full-Time Job

Analyst II - SIEM/SecOps

Zeta

  • Hyderabad, India
  • Not disclosed
  • 3–5 Years
  • Posted Yesterday
HR
Recruiter contact
Recruiter / hiring contact
No public email in this post. Use a source-linked contact instead.

About the role

About us

Build the future of banking.

Zeta is a next-generation banking technology company providing cloud-native, fully stackable processing and core banking platforms for issuers. With a focus on scalability, compliance, and innovation, Zeta empowers financial institutions to modernize their technology infrastructure and deliver secure, seamless digital banking experiences.

Our impact runs at real-world scale. Today, over 25 million cards are live on Zeta-powered platforms across 7 countries, supported by a passionate team of 1,700+ Zetanauts across India, the US, EMEA, and Asia. Backed by SoftBank Vision Fund, Mastercard, and other reputed strategic investors, we reached a valuation of $2 billion in 2025.

Our focus is on establishing product lines that focus on key outcomes by addressing real customer pain points, modernizing legacy systems, and strengthening core fundamentals. As a result, our systems and platforms support a wide range of banking and payments capabilities, including:

  • Tachyon, our cloud-native banking stack built for population-scale systems
  • Cipher, our unified authentication platform for secure, high-volume banking environments
  • Digital Credit as a Service, enabling banks to launch credit lines on UPI
  • Elena, our intelligent and conversational AI platform for banking
  • Pixel, India’s first digital-native credit card, launched in partnership with HDFC Bank, for whom we also revamped their PayZapp mobile app: Winner of the Celent Model Bank Award for Payments Innovation 2024
  • Sparrow, the leading card experience for non-prime cardholders in the US

…and more across cards, payments, lending, and core banking.

We are an engineering-first organization that values ownership, bias for action, and long-term thinking. Together, we solve some of the hardest problems in banking tech. Our culture is built around trust, collaboration, and creating the conditions for you to drive impact proportionate to your potential.

Reinforcing our commitment to creating an inclusive and supportive workplace, we have been consistently recognized as a Great Place to Work.

If you want to build cutting-edge banking tech that enables banks to serve millions reliably, securely, and at a population scale, Zeta is your playground.

If you would like to learn more about how we have grown and evolved over the years, watch our journey here. You can also explore our website and follow us on LinkedIn, Instagram, YouTube, and X.

About the Role

Zeta is building out its Security Operations Centre function, running on AWS OpenSearch as our core SIEM. We are looking for a SOC L2 Analyst with a strong investigative mindset and hands-on comfort operating without a traditional GUI-driven workflow — this role requires fluency in query languages to search, correlate, and triage data directly.

You'll be one of the early analysts shaping detection and response practices across a modern, cloud-native, hybrid environment spanning Kubernetes microservices, multi-cloud infrastructure, and traditional corporate IT.

You will be investigating and monitoring across:

Cloud & Infrastructure: AWS (primary hosting for all workloads/resources), Azure (logs), Kubernetes microservices

Edge/CDN & Network Security: Cloudflare

Endpoint: Microsoft Defender (corporate IT), macOS endpoints

Primary OS for incidents: Linux (majority of incident volume), with Windows/macOS corporate IT coverage

SIEM: AWS OpenSearch (query-language driven — no dedicated analysis GUI)

Responsibilities

  • Monitoring & Escalation Handling
  • Perform full-time monitoring alongside L1, actively working the alert queue during high-volume periods, while also handling escalations from L1 analysts.
  • Act as the primary escalation point for all L1-escalated alerts and incidents; receive and validate escalated alerts/incidents, performing deeper investigation to confirm scope, impact, and root cause.
  • Perform detailed investigation, log correlation, and root-cause analysis across multiple data sources — AWS, Kubernetes, Cloudflare, Azure logs, Defender, and Linux/macOS endpoints.
  • Write and run OpenSearch Query DSL / Lucene queries directly against raw log data to pivot, correlate, and build full incident timelines (this is the primary analysis method — there is no GUI-driven investigation path).
  • Determine incident severity, scope, and business impact; validate true positive vs. false positive at a deeper level.
  • Escalate confirmed major/high-severity incidents to the L3/Incident Response team or CSIRT leadership per the incident response plan, including a full technical summary, supporting evidence, and recommended actions.
  • Coordinate with L3/Incident Response teams for complex or high-severity incidents.
  • Threat Analysis & Detection Support
  • Conduct threat hunting based on IOCs, IOAs, and threat intelligence feeds.
  • Support ideation and testing of new detection use cases, correlation rules, and dashboards, in coordination with the detection engineering/L3 team.
  • Identify and report logging/health issues (e.g., missing logs, parser errors, data source outages) for timely resolution.
  • Tune and recommend improvements to detection rules, correlation logic, and SIEM use cases based on false positives/negatives observed during investigations; develop tested tuning solutions and hand them to L3 analysts and build teams for deployment.
  • Create new detection use cases, tune existing correlation rules, build/modify dashboards, develop and refine UEBA rules, and map detections to the MITRE ATT&CK framework for coverage visibility.
  • Playbook, SOP & Knowledge Management
  • Develop and refine investigation steps for scenarios not covered by existing playbooks, and document these as new/updated runbooks for L1 use.
  • Update and improve SOPs, playbooks, and knowledge base articles based on incident learnings.
  • L1 Oversight & Mentoring
  • Mentor and provide technical guidance to L1 analysts, including alert triage decisions and use of investigation tools.
  • Own L1 shift handovers, and train/mentor L1 analysts on alert handling and escalation.
  • Review quality of L1 alert closures and escalations; provide feedback and coaching.
  • Support training and onboarding of L1 analysts on tools, triage procedures, and escalation criteria.
  • Ensure smooth shift handovers between L1 and L2, and across shifts.
  • Compliance & Audit Support
  • Assist with compliance and audit requests requiring deeper technical evidence or investigation summaries.
  • Continuous Learning & Feedback
  • Continuously expand knowledge of emerging threats, attack techniques, and best practices through ongoing training and self-study.
  • Stay current on emerging threats, TTPs, and vulnerabilities relevant to our environment, and translate this into actionable detection improvements.

Skills

  • Strong working knowledge of SIEM query languages — direct experience with OpenSearch Query DSL, Lucene syntax, KQL, SPL, or equivalent is essential (you must be comfortable querying raw data without relying on prebuilt dashboards)
  • Solid Linux investigation skills — process, network, and log-level analysis on Linux hosts is core to this role
  • Practical understanding of cloud security fundamentals, ideally AWS (IAM, CloudTrail, VPC Flow Logs, GuardDuty, etc.)
  • Exposure to Kubernetes/container security concepts (pod logs, k8s audit logs, common container attack patterns)
  • Familiarity with Cloudflare logs (WAF, DNS, edge traffic) or similar CDN/edge security tooling
  • Working knowledge of Microsoft Defender and basic Windows/macOS endpoint investigation
  • Strong analytical and investigative mindset — able to pivot from a single alert to a full incident narrative using raw log data
  • Understanding of the MITRE ATT&CK framework and common attack patterns (cloud, container, endpoint), including mapping detections for coverage visibility
  • Experience acting as an escalation point for L1 analysts — validating their triage, coaching on quality, and owning shift handovers
  • Ability to author and maintain runbooks, SOPs, and knowledge base articles from incident learnings
  • Clear, structured incident documentation and communication skills

Experience and Qualifications

  • 3–5 years of hands-on SOC experience, with at least 1–2 years in an L2 analyst capacity handling escalations independently
  • Bachelor of Technology (BE/B.Tech), M.Tech/ME in Computer Science or equivalent.
  • Prior SOC experience in a fintech, banking, or regulated industry environment
  • Exposure to Azure Sentinel/Azure logs in addition to AWS
  • Scripting ability (Python, Bash) for automation of repetitive investigation tasks
  • Certifications such as Security+, GCIH, GCIA, CySA+, or equivalent
  • Experience contributing to detection engineering (writing/tuning correlation rules, not just consuming them)
  • Familiarity with case management/ticketing tools (e.g., TheHive, Jira, ServiceNow)
  • Experience developing or tuning UEBA rules
  • Experience identifying and reporting log pipeline health issues (missing sources, parser errors, ingestion outages)

•

Experience supporting compliance/audit evidence requests (PCI-DSS, SOC 2, RBI/regulatory — relevant to fintech)

Zeta is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees. We encourage applicants from all backgrounds, cultures, and communities to apply and believe that a diverse workforce is key to our success.

Eligibility & process

Who can apply

• 3–5 years of hands-on SOC experience, with at least 1–2 years in an L2 analyst capacity handling escalations independently • Bachelor of Technology (BE/B.Tech), M.Tech/ME in Computer Science or equivalent. • Prior SOC experience in a fintech, banking, or regulated industry environment • Exposure to Azure Sentinel/Azure logs in addition to AWS • Scripting ability (Python, Bash) for automation of repetitive investigation tasks • Certifications such as Security+, GCIH, GCIA, CySA+, or equivalent • Experience contributing to detection engineering (writing/tuning correlation rules, not just

Skills & stack

Python Next.js Microservices AWS Azure Kubernetes Linux JIRA

Selection process

  1. As described in the employer's job posting.

Prep kit

20 resources
Study material 4
Company-specific guides 4
Likely coding questions 4
Round-wise strategy 4
Round 1: Online Assessment (OA) Aptitude, Quantitative Logic & 2 Coding Problems Focus on accuracy and speed. Practice arrays, strings, and standard arithmetic puzzles.
Round 2: Technical Interview 1 Core Tech Stack (Python, Next.js, Microservices, AWS, Azure, Kubernetes, Linux, JIRA) & Live Code Tracing Explain your thought process aloud. Analyze time & space complexities before coding.
Round 3: System Design & Problem Solving Database Schemas, APIs & Architecture Basics Clarify edge cases, diagram schemas cleanly, and discuss scalability trade-offs.
Round 4: HR & Cultural Fit Discussion Zeta Core Values, Learning Agility & Offer Terms Demonstrate passion, strong communication, and readiness for full-time collaboration.
Technical questions 5
Explain OOP (Object-Oriented Programming) principles with real-world examples in Python. Answer
Model answer: 1. Encapsulation (data hiding via private fields/getters). 2. Abstraction (hiding implementation complexity). 3. Inheritance (code reusability). 4. Polymorphism (method overriding/overloading).
What is the time and space complexity of QuickSort vs MergeSort? Answer
Model answer: QuickSort: Average O(N log N) time, O(log N) space. Worst O(N^2). MergeSort: Guaranteed O(N log N) time, but requires O(N) auxiliary space.
Explain the difference between SQL Indexing (B-Tree vs Hash) and when not to use an index. Answer
Model answer: Indexes speed up SELECT queries via B-Trees. However, they slow down INSERT, UPDATE, and DELETE operations because indexes must be updated on disk. Avoid on low-cardinality columns (e.g., boolean flags).
What happens under the hood when you enter a URL in a browser? Answer
Model answer: 1. DNS lookup (resolves IP). 2. TCP 3-way handshake (SYN, SYN-ACK, ACK). 3. TLS negotiation for HTTPS. 4. HTTP GET request sent. 5. Server responds with HTML/CSS/JS. 6. Browser renders DOM & CSSOM tree.
What is the difference between REST and GraphQL APIs? Answer
Model answer: REST uses multiple fixed endpoints with possible over/under-fetching. GraphQL uses a single endpoint allowing clients to query exact fields in a single request.
Behavioural & HR questions 3
Why do you want to join Zeta as a Analyst II - SIEM/SecOps?
Highlight Zeta's market reputation, recent tech innovations, and how your skills in Python directly solve their team's objectives.
Describe a challenging bug or academic project roadblock and how you resolved it.
Use the STAR method: Situation (project context), Task (what needed solving), Action (specific tools/logic applied), Result (quantifiable positive outcome).
How do you handle strict deadlines or sudden scope changes?
Explain your prioritization strategy, proactive communication with mentors/peers, and agile mindset.
Zeta Not disclosed
Recruiter Resume Apply
Chat Chat with Kashii