31 tech jobs in India, August 29, 2026

T

Tekion

Viewed

The posting states no number of years. It describes the role as entry level and hands on, working on well defined tasks under senior guidance, so it is genuinely open to someone starting out. That is why we have published it at zero to one year rather than guessing a figure. What the job actually is, day to day: monitor, triage and investigate security alerts coming from SIEM, EDR, cloud, network and identity sources, and escalate anything suspicious or confirmed to senior engineers following an established procedure. Help cut false positives by spotting noisy alerts and documenting tuning recommendations. Assist in building and testing detection rules mapped to frameworks such as MITRE ATT&CK. Contribute to automation, including SOAR playbooks and AI agent driven workflows for alert enrichment, triage and response. Support SOC metrics tracking and reporting. The shift reality, stated plainly in the ad: this is a 24x7 SOC on a rotating shift schedule that includes night shifts, weekends and holidays. It is based at Tekion's Bangalore office. If you cannot do nights, this is not the role, and that is worth knowing before an interview rather than after. Who this is for: someone who wants into security operations and is willing to trade sociable hours for real alert handling experience early. Familiarity with SIEM or EDR tooling, an understanding of common attack techniques, and any scripting will help. The AI and SOAR automation work is a genuine differentiator, because a lot of first SOC jobs are pure alert clicking and this one explicitly includes building the automation. No interview process is published in the ad.

Z

ZoomInfo

Viewed

Stated requirement is 1 to 2 years of QA or testing experience with exposure to test automation. This is one of the few genuinely early career roles on the board today. Must have, as listed: one to two years in QA or testing with exposure to automation. Hands on experience or project exposure to Salesforce testing, ideally covering one or more of Sales Cloud, Salesforce CPQ, Revenue Cloud, Service Cloud or Commerce Cloud. Hands on Playwright automation using TypeScript or JavaScript. An understanding of automated testing concepts including test cases, test suites, locators, assertions and test execution. A basic understanding of Salesforce business processes and end to end application workflows. REST API testing with Playwright, Postman or similar. Working knowledge of JavaScript or TypeScript, with Java or Python a plus. Familiarity with CI/CD and exposure to Jenkins, GitHub Actions, Azure DevOps or GitLab CI/CD. Working knowledge of Git. Strong problem solving, troubleshooting and debugging. Good written and verbal communication, and the ability to work in an Agile cross functional team. Good to have: exposure to AI powered or AI assisted testing tools and Agentic AI, familiarity with Playwright AI capabilities or self healing automation, basic Salesforce Apex and Apex testing, performance testing with JMeter or LoadRunner, B2B SaaS experience, and a Salesforce certification or the willingness to work towards one. Location and working pattern: Chennai, and the posting carries a hybrid tag. Note that ZoomInfo has posted the same role separately in Bengaluru, so apply to the city you actually want. Who this is for: a QA engineer one or two years in who has some Playwright under their belt and is willing to specialise in enterprise Salesforce testing. The Salesforce angle is the thing to weigh. It is a genuinely marketable specialisation, but it is a narrower path than general product QA. No interview process is published in the ad.

Z

ZoomInfo

Viewed

Stated requirement is 1 to 2 years of QA or testing experience with exposure to test automation. Must have, as listed: one to two years in QA or testing with automation exposure. Hands on experience or project exposure to Salesforce testing across one or more of Sales Cloud, Salesforce CPQ, Revenue Cloud, Service Cloud and Commerce Cloud. Hands on Playwright automation in TypeScript or JavaScript. Understanding of automated testing concepts including test cases, test suites, locators, assertions and execution. Basic understanding of Salesforce business processes and end to end workflows. REST API testing using Playwright, Postman or a similar tool. Working knowledge of JavaScript or TypeScript, with Java or Python a plus. Familiarity with CI/CD concepts and tools such as Jenkins, GitHub Actions, Azure DevOps or GitLab CI/CD. Working knowledge of Git and version control. Strong debugging and troubleshooting. Good communication and the ability to work in an Agile cross functional team. Good to have: AI powered testing tools, AI assisted automation or Agentic AI exposure, Playwright AI capabilities and self healing automation concepts, basic Salesforce Apex and Apex testing, performance testing with JMeter or LoadRunner, B2B SaaS experience, and Salesforce certification or willingness to pursue one. Location and working pattern: Bengaluru, with a hybrid tag on the posting. The Chennai version of this role is a separate requisition and is also on this board. Who this is for: an early career QA engineer with Playwright experience who is willing to go deep on enterprise Salesforce testing. Weigh the specialisation honestly. It pays well and is in demand, but it is narrower than general product QA and it will shape the next few years of your CV. No interview process is published in the ad.

Z

Zscaler

Viewed

Stated requirement is 1 to 3 years of experience in a distributed, enterprise scale environment. That is a genuinely accessible band for systems level networking work, which normally starts higher. What you would do: develop and optimise network applications and protocols using C and C++. Design efficient data structures for network data processing and handle system level programming in Linux environments. Analyse network performance, identify issues and implement optimisations. Collaborate with other teams to define requirements, design architectures and integrate network solutions. Conduct code reviews, testing and debugging. Minimum qualifications as published: a foundational understanding of AI and ML technologies and experience using, securing or positioning AI driven solutions within your domain, alongside the one to three years in a distributed and enterprise scale environment. The ad also looks for strength in networking with a track record of proposing improvements to system reliability, scalability and network efficiency. Location and working pattern: this is stated as a hybrid role based in Bangalore, reporting to the Senior Manager, Engineering in the ZTNA department. The posting carries a hybrid tag and refers to in office perks, so do not read it as remote. Who this is for: someone one to three years in who genuinely wants systems and networking rather than application development, and is comfortable in C or C++ on Linux. If you have written packet handling code, worked on a proxy or a protocol stack, or done kernel adjacent work at university or in a first job, this is a strong opening at a company operating at very large scale. If your experience is web or backend service work, the datapath focus will be a hard change of direction rather than an adjacent step. No interview process is published in the ad.

O

Orca Security

Viewed

Stated requirement is 1 to 3 years of experience in a customer facing technical role. The posting names the kinds of background it will accept: Technical Support Engineer, Support or Solutions Engineer, Implementation Engineer, junior DevOps or Security Engineer, or similar. Worth knowing before you apply: the board title says Customer Success Engineer, but the description itself is for an Associate Customer Success Engineer and calls the job a great next step for someone early in a customer facing technical career. The associate framing is in the body, not the title, so the seniority is lower than the title alone suggests. That is the opposite of the usual trap and it works in a junior applicant's favour here. The work: supporting Orca customers day to day alongside senior Customer Success Engineers and Customer Success Managers, helping them get value from the platform, and growing into cloud security and customer success engineering as a career. The ad frames this explicitly as a growth seat rather than a role that expects a finished cloud security specialist. Location and working pattern: the posting states India, Delhi, remote. We checked this against the text rather than trusting a tag, and it is a genuine remote listing. Remote roles have been the single most requested thing from readers of this list, and this is one of only three today that survive that check. Who this is for: someone one to three years into support, implementation or junior DevOps or security work who wants a route into cloud security without already having the cloud security title. Being comfortable talking to customers matters as much as the technical depth here. If you are a strong engineer who does not want customer contact, this will not suit you, and the ad is honest about that. No interview process is published in the ad.

K

Kaseya

Viewed

Stated requirement is 2 years of experience with C Sharp and the .NET ecosystem. Note the mismatch worth knowing about: the title says Software Engineer I, which normally signals a first job, but the requirement is two years. The roman numeral is not a reliable guide to seniority, and today's edition has several examples of that in both directions. Required qualifications, as listed: two years of experience with C Sharp and the .NET ecosystem. Willingness to learn and develop with functional programming using F Sharp. Good knowledge of Win32 APIs. Basic familiarity with networking protocols such as HTTP and TLS. The ability to write clean and testable code. A general understanding of how distributed systems work. What the job actually is: design, develop, test and maintain software features for enterprise SaaS platforms. Build reliable and scalable services, APIs, platform components, integrations and customer facing capabilities. Take part in technical design, code reviews, troubleshooting and production support. Work with product management, QA, UX and operations to deliver roadmap commitments. Contribute to improvements in performance, reliability, security, maintainability, automation and observability. Follow and help improve agile development, CI/CD, automated testing and DevOps practice. Communicate progress, risks and technical trade offs clearly. Nice to have, from the ad: cloud infrastructure experience, contributions to open source software, and experience performing peer code reviews. Location and working pattern: the posting states this is a hybrid role requiring onsite presence at the Pune office three days per week. That is specific and it is in the ad, so plan for it. Who this is for: a Microsoft stack developer roughly two years in who wants enterprise product work rather than services or consulting. The F Sharp and Win32 elements are unusual and genuinely interesting if low level Windows work appeals. If your background is Java or Python, expect the C Sharp requirement to be taken literally. No interview process is published in the ad.

H

HighRadius

Viewed

Stated requirement is 2 to 3 years of QA experience across manual and automation testing, with a B.Tech or BE in Computer Science, IT or an equivalent. Requirements as listed: 2 to 3 years of QA experience in manual plus automation testing. Experience with Selenium WebDriver and API testing tools including Postman and REST Assured. Good SQL skills for data validation. Familiarity with Agile and Scrum workflows. An understanding of the defect lifecycle and QA metrics. Good communication, problem solving and collaboration skills. What the job actually is: design, execute and maintain manual and automated test cases across web, API and database layers. Perform API testing using Postman or automation frameworks such as REST Assured. Maintain UI automation using Selenium WebDriver in Java or Python. Validate backend data using SQL queries. Manage defects through Jira and work with development to get them resolved. Take part in Agile ceremonies, QA sign offs and release readiness reviews. Integrate automated tests into CI/CD pipelines using Jenkins or GitHub Actions. Perform cross browser and responsive testing. Contribute to QA process improvements and expand automation coverage. Location: Hyderabad. Note that other HighRadius engineering postings in this same edition state five days a week in the office, and this ad does not state a working pattern either way, so it is worth asking. Who this is for: a QA engineer two to three years in who already writes Selenium and API tests and wants breadth across UI, API and database validation rather than a single narrow lane. The SQL requirement is real here, not decorative, because a good part of the job is checking that the data behind the screen is correct. No interview process is published in the ad.

C

Coinbase

Viewed

Stated requirement is at least 3 or more years of experience in software engineering, plus a track record of having designed, built, scaled and maintained production services and an understanding of service oriented architecture. What you would do: architect and develop the platform for the security platform engineering organisation. Provide technical structure to teams and work with management and stakeholders on strategic roadmaps. Build new services in Go or Java to meet product and business needs. Design scalable systems using modern cloud technology. Manage your own project priorities, deadlines and deliverables. Mentor and train other team members on design technique and coding standards. Articulate a long term vision for maintaining and scaling backend systems. Write high quality, well tested code. Debug genuinely difficult technical problems and make systems easier to deploy, operate and diagnose. Review feature designs within your product area and across the company for cross cutting projects, taking ownership of security, safety, scale, operational integrity and architectural clarity. The functional areas the team covers, named in the ad: secrets and key management, identity and access management, onchain security, policy and risk management, and vulnerability management, serving product, compliance, security and services teams. Location and working pattern: the listing states Remote in India and carries a remote tag, and we confirmed that against the body rather than the tag alone. Read one caveat in the ad before you treat it as fully distributed: Coinbase describes itself as remote first but not remote only, and says to expect quarterly in person working sessions it calls surges. The ad is also blunt about culture, describing a high bar and an intense environment. Who this is for: a backend engineer three or more years in who wants security platform work rather than product features, and is comfortable in Go or Java. Prior security experience is not stated as mandatory, so a strong distributed systems engineer who wants to move into security has a real opening here. No interview process is published in the ad.

F

Fivetran

Viewed

Stated requirement is 3 or more years building production software, including senior level ownership of projects that ran for months and involved several people. Before anything else, two things the ad tells you that change the picture. First, Fivetran and dbt Labs are merging, and the posting says so directly, warning that both names appear during recruiting. The role itself is on dbt surfaces. Second, do not read this as a remote job. The posting carries a hybrid tag, and the only mention of remote working is in the bonus skills list, where having worked asynchronously in a fully remote distributed team is listed as a nice to have. That is a description of a candidate's past, not an offer about this job. What you would do: own end to end delivery across dbt Studio in the browser, the dbt VS Code extension, and the CLI workspace runtime that powers both. Own parts of that runtime, including migrating users off the legacy IDE and enabling asynchronous background agent runs. Help build the AI native developer experience, including agent workflows, diff review, streaming tool calls, charts and rich outputs for conversational analytics, and MCP apps that bring dbt projects into tools such as Claude and Codex. Technologies named: Python, TypeScript, React and Kubernetes. The ad is explicit that this is genuinely full stack and that you are expected to carry a feature from schema and service design through to the finished interface without a handoff. Bonus skills listed: having shipped LLM or agent powered features to production with real opinions on evaluation, latency, cost and where models fall down, and having worked asynchronously in a fully remote distributed team. Location and working pattern: Bengaluru, with the posting also tagged APAC, and a hybrid tag on the listing. Who this is for: a product minded full stack engineer three or more years in who is comfortable moving between Python services and a React front end, and who wants to build developer tooling rather than end user features. If you already use dbt, that context is worth a lot here. No interview process is published in the ad.

A

Abnormal AI

Viewed

Stated requirement is 3 or more years of professional software engineering experience, including building and operating production web applications. What you would do: own and develop data rich, consumer grade user interfaces and APIs that surface what Abnormal knows about a user's normal patterns and what might indicate something abnormal. Build the interface that lets customers and internal agents debug particular attacks. Build a framework and specification for quickly adding new data sources. Work directly with customers on feedback and iterate quickly, for example resolving false positive and false negative or integration issues. Work with distributed systems, cloud infrastructure and event driven or messaging based architectures. Collaborate with product managers, designers and partner engineering teams to define interfaces and make trade offs. Write maintainable code, automated tests, documentation and operational runbooks, and take part in code reviews and design discussions. Take part in on call and production support, investigate issues and improve reliability and observability. Use AI assisted development tools thoughtfully while keeping technical judgement and code quality. What the team owns: the identity graph and the data capturing relationships between people, groups, tenants and apps, plus platform capabilities used as intelligence by detection engine decisions, customer facing identity insights and cross product APIs. Location and working pattern: the posting states India, hybrid, and the listing itself is headed Hybrid, Bangalore. Treat the hybrid expectation as real. Who this is for: a full stack engineer three or more years in who genuinely enjoys frontend work but does not want to give up backend and distributed systems. The ad is clear that the frontend weighting is meaningful, so a backend only engineer would be stretching. On call is named explicitly, so factor that in. No interview process is published in the ad.

S

SolarWinds

Viewed

Stated requirement is 3 or more years of experience in Solution Engineering, Sales Engineering, Solutions Consulting, IT Operations, IT Service Management, or a related technical customer facing role. What the job actually is: partner with sales teams through the customer lifecycle to support new business, expansion and renewal opportunities. Conduct discovery sessions to understand customer business objectives, operational challenges, technical requirements and success criteria. Deliver product demonstrations of SolarWinds Service Desk and Web Help Desk tailored to what the customer said in discovery. Act as a technical advisor to prospective and existing customers evaluating and adopting the ITSM products. Work with Account Executives, Customer Success, Product Management and other teams to support customer success and feed market signals back into the product. What the role is not: this is a presales technical role, not a quota carrying sales job. It sits alongside sales and supports revenue, and the ad says so, but the responsibilities listed are discovery, demonstration and solution design rather than closing. We separate those deliberately, and we left another company's Solutions Engineer posting out of today's edition because its first stated objective was to exceed sales targets. This one reads differently. Location: Bangalore. The posting does not state a working pattern, so ask. Who this is for: someone with a few years in ITSM, IT operations, support or presales who is good in front of a customer and enjoys the puzzle of mapping a product onto somebody else's messy environment. Knowledge of service desk tooling and IT asset management is directly relevant. If you want to write code all day this is the wrong role, and if you want to sell without the technical depth it is equally wrong. No interview process is published in the ad.

S

Showpad

Viewed

Stated requirement is 3 to 6 years of professional software engineering experience. Read the title carefully before you skip or apply. The posting is listed as L2 Engineer, Coach, which reads like tier two product support. The body is headed L2 Engineer, GenAI Focused and opens by saying the team is seeking a mid level AI engineer. Coach is the Showpad product this sits on, not a support tier. The actual job is backend and applied AI engineering. Required qualifications as listed: 3 to 6 years of professional software engineering experience. Strong expertise in TypeScript and JavaScript. Hands on experience with AWS serverless services including API Gateway, Lambda, DynamoDB and VPC networking. Experience designing and building distributed backend systems. Strong understanding of REST APIs, microservices and event driven architectures. Experience with WebSockets and real time communication systems. Strong experience with unit testing and integration testing. Experience building and supporting production grade generative AI applications. Experience working with LLMs such as OpenAI, Anthropic, Gemini and open source models. Experience with prompt engineering and prompt optimisation. What you would do: design, develop and maintain scalable backend services in TypeScript and JavaScript. Build and operate cloud native applications on AWS serverless. Design and implement REST APIs and event driven architectures. Build and deploy production grade generative AI applications. Develop RAG based solutions using vector databases, embeddings and modern LLM frameworks. Engineer prompts and AI workflows. Conduct LLM evaluations, benchmarking and performance analysis. Implement AI observability, monitoring and quality evaluation. Build automated testing frameworks, maintain CI/CD pipelines, and contribute to architecture decisions. Location: Pune. The posting does not state a working pattern. Who this is for: a backend engineer three to six years in who has actually shipped an LLM feature to production, not just experimented. The serverless and TypeScript requirements are specific, so a Java or Python backend engineer without AWS serverless depth would be stretching. No interview process is published in the ad.

S

Skyflow

Viewed

Stated requirement is 4 or more years of experience in platform engineering, infrastructure engineering, DevOps or SRE roles, with real ownership of production cloud infrastructure. The timezone is in the job title and it matters. This is the operations seat on a PST timezone, which from India means working United States Pacific hours. That is a night shift. It is disclosed openly in the title rather than buried, but it is the single biggest thing to weigh before applying. What you have, as listed: 4 or more years in platform, infrastructure, DevOps or SRE roles with genuine ownership of production cloud infrastructure. Strong software engineering skills in Go or Python, writing tested maintainable code and treating infrastructure automation as software rather than scripting. Deep hands on Kubernetes in production covering workload scheduling, networking, autoscaling and upgrades. Infrastructure as code tooling such as Terraform, Pulumi or OpenTofu. Solid experience with at least one major public cloud, with AWS, GCP and Azure all named and experience across all three called a strong plus given the multi cloud footprint. A track record of building tools or platforms other engineers use, such as internal CLIs, provisioning frameworks, self service portals or automation pipelines. What the job actually is: build and run the infrastructure behind a multi tenant, security sensitive B2B cloud product used by enterprise customers worldwide. The platform spans multi tenant environments and single tenant bring your own cloud deployments into customer accounts, so every environment has to be provisioned, upgraded, monitored and recovered the same way at scale with minimal manual work. You would also carry deep operational ownership including on call, incident response and root cause analysis on the systems you build. Location: listed as India. Benefits named include a work from home expense, flexible hours, generous PTO and equity, though the posting does not state the role as remote in so many words. Who this is for: an infrastructure engineer who writes real code and wants platform building rather than ticket handling, and who can genuinely work Pacific hours. If the night shift does not work for your life, skip it, because the ad is not hiding it. No interview process is published in the ad.

T

Tekion

Viewed

Stated requirement is 4 to 6 years of experience in security operations, security engineering, incident response or related roles, with equivalent experience considered. The shift pattern is explicit and non negotiable in the ad: this is a 24x7 SOC on a rotating shift schedule including night shifts, weekends and holidays. The posting also lists willingness and ability to work that roster as a requirement in its own right, not a footnote. What you would do: work in the 24x7 SOC providing continuous alert monitoring and response coverage. Triage, investigate and respond to security alerts from SIEM, EDR, cloud, network and identity sources, escalating confirmed incidents per procedure. Continuously tune detections and alert logic to reduce false positives and improve the signal to noise ratio across the alert pipeline. Build, test and maintain detection rules and use cases aligned to frameworks such as MITRE ATT&CK, based on emerging threats. Track and report SOC metrics. Automate response workflows using SOAR platforms and AI agents. Partner with IT, Engineering and Security Operations to identify risks, remediate vulnerabilities and strengthen security posture. How it differs from the Engineer I seat, in the ad's own framing: the Engineer II works on moderately complex projects with minimal supervision, while the Engineer I works on well defined tasks under senior guidance. Both are on the same roster and both are at Tekion's Bangalore office. If you are choosing between them, the years requirement is the clearer signal: this one asks four to six, the other asks none and says entry level. Hands on experience with alert triage is named in the requirements alongside the years. Who this is for: a SOC analyst or security engineer four to six years in who wants to move from consuming detections to writing and tuning them, and who is willing to keep working shifts to do it. The SOAR and AI agent automation work is the part that builds transferable skill fastest. No interview process is published in the ad.

H

HighRadius

Viewed

Stated requirement is a minimum of 5 or more years of experience in backend technology using Java, Spring Boot, low level design, data structures and algorithms, multithreading and AWS. The working pattern is stated in the ad and it is worth reading twice: five days working from office, in Hyderabad. That is a full return to office, not hybrid, and HighRadius states the same on another engineering role in today's edition. What the job actually is: HighRadius runs an internal new products initiative described as an entrepreneurship programme, with products built in a startup ecosystem inside the company. You would join one of those and be responsible for designing and building the product in stealth mode. Responsibilities named include building the foundational elements of the product, taking responsibility for timely delivery as a senior engineer in a small team, providing scalable solutions for EI and payment products covering both backend processing and UI representation, contributing to technical design and implementation with engineering leaders, high quality development at speed, code reviews, and filling gaps in the product by building development processes and tools where needed. Requirements as listed: strong hands on knowledge of core Java, Spring, Hibernate and SQL, with the five or more years covering Java, Spring Boot, low level design, DSA, multithreading and AWS. Knowledge of front end development alongside the backend technologies. One line to weigh: the ad says you would manage and groom junior developers for a high performance culture. We read this as senior engineer mentoring rather than people management, because no direct reports, hiring or performance responsibilities are named and every technical requirement is hands on. If you want a pure individual contributor seat with no mentoring expectation, ask about it. Who this is for: a Java backend engineer five or more years in who wants greenfield product building and can genuinely commit to five days a week in a Hyderabad office. The zero to one framing is the appeal here, and the office requirement is the cost. No interview process is published in the ad.

C

Cockroach Labs

Viewed

Stated requirement is 5 or more years of experience as a software engineer, with strong general purpose coding skills and Go or Python preferred. One caution about the years. The description also mentions someone with 16 or more years of experience across Microsoft, Oracle and companies such as Freshworks. That sentence is a biography of an engineering leader in the team section, not a requirement, and an automated parser reading the highest or lowest number in this posting would get it wrong in both directions. The requirement is five or more. What the role is now, in the ad's own words: it has shifted from a traditional DevOps or developer infrastructure profile to one centred on general software engineering and applied AI. Most of the time goes on building and hardening AI powered developer tools such as automated code review, CI failure triage and agentic automation, rather than managing build systems or CI infrastructure in isolation. Working knowledge of CI/CD and developer workflows is still needed, but the emphasis is shipping product quality software whose customers happen to be engineers. Examples of the team's actual work, named in the posting: building the AI code review pipeline and migrating the major repositories including cockroach, pebble and cockroach cloud off third party review tools such as BugBot, GitHub Copilot and Claude Code Action onto an in house AI driven pull request review system, and adding observability to AI review so findings can be surfaced and measured. What the team values, as stated: providing high quality support to engineering teams, engaging with engineers to understand developer pain points, minimising and automating away toil including the toil of using AI safely, shipping incrementally, measuring quality with real data, and being honest about where AI tooling still needs a human in the loop. Location: Bangalore. The posting does not state a working pattern. Who this is for: an engineer five or more years in who wants to build internal developer tooling and is genuinely interested in putting AI agents into engineering workflows safely. If you were hoping for distributed database internals, note that this role is deliberately not that. No interview process is published in the ad.

O

Okta

Viewed

Stated requirement is 5 or more years of professional experience in a data engineering or full stack role. What you would be doing, as listed: design and develop scalable data platforms using AWS, Snowflake, dbt and Databricks. Use Terraform to manage infrastructure as code so environments are consistent and reproducible. Develop and maintain CI/CD pipelines for data platform applications using GitHub and GitLab. Engineer robust data pipelines to support AI and ML infrastructure. Collaborate with data engineers, analysts, scientists and other engineers to ensure data availability, integrity and security. Build stable data layers and partner with analytics engineers to power AI and ML systems. Where the team sits: the Data Engineering team is part of the Technology Data and Intelligence organisation, and the platforms it builds are used across sales, marketing, engineering, finance, product and operations. The ad describes detailed technical design, development and implementation of applications on current technology stacks. Nice to have, named in the posting: experience with recent AI technologies, experience coaching and developing individuals for increased effectiveness, familiarity with cloud cost optimisation or FinOps, and a background in SaaS, security or identity. Location: Bengaluru. The posting does not state a working pattern in the text we can see, so ask. Who this is for: a data engineer five or more years in who has built pipelines on a modern warehouse stack and wants platform ownership rather than dashboard work. Snowflake and dbt experience is close to essential given how specifically they are named. Data engineering has been one of the two most requested categories from readers of this list, alongside backend, and this is a straightforward example of it at a large company. No interview process is published in the ad.

S

Sarvam

Viewed

Stated requirement is 5 to 6 or more years in backend engineering, with meaningful time spent operating high throughput production systems you were on call for. What we are looking for, as listed: deep proficiency in Go or Python and the judgement to know which belongs where. Strong distributed systems design covering queues, workflow orchestration, idempotency, backpressure, retry and timeout semantics, consistency trade offs and graceful degradation. Production experience with Temporal or an equivalent durable execution engine on workflows that mattered. Kubernetes in production including autoscaling, resource management, rollouts and debugging under load, with GPU workload scheduling a strong plus. Demonstrable experience serving ML or LLM inference in production covering batching, caching, model versioning, A/B rollout and latency budgeting. Rigour about observability and reliability, including having designed SLOs, run incidents and shipped the fixes. Hard won cost intuition, having made a system materially cheaper without giving up quality. Bonus points: direct experience with OCR, intelligent document processing or document AI systems such as Textract, Document AI or Azure DI. GPU inference stacks including vLLM, TensorRT-LLM, Triton, SGLang or Ray Serve. Evaluation infrastructure for ML systems such as golden sets, regression gates and human in the loop review. Experience with BFSI, healthcare or public sector compliance and data residency constraints. On premise or air gapped deployment experience. What you would own: the architecture of the serving harness for Sarvam's vision models, including the accuracy work (multi pass extraction, ensembling, cross verification, schema constrained decoding, confidence calibration) and the hard trade off surface of accuracy against latency against rupees per page. Multi pass inference, model routing and cascades, self consistency and verification passes, confidence driven escalation, batching and caching strategy and GPU utilisation are named as the levers you would pull. You would also set the reliability bar for pipelines processing KYC, loan underwriting, claims and contracts. Stack named: Go, Python, Temporal, REST, Kubernetes, PostgreSQL, Redis, object storage and OpenTelemetry based observability. Location is Bengaluru. Who this is for: a backend or platform engineer who has run inference in production and cares about cost and latency as much as correctness. The ad closes by saying it wants people who can own the outcomes rather than people who match a checklist, which is a fair signal to apply if you are close but not exact.

H

HighRadius

Viewed

Stated experience level is 5 to 8 years, written in the ad as a labelled field rather than buried in prose. The working pattern is stated just as plainly: five days working from office, in Hyderabad. HighRadius says the same on another engineering role in today's edition, so read it as a company policy rather than a one off. One oddity worth knowing: the published posting still contains an unfilled template placeholder where the cloud provider should be, listing the requirement as experience with AWS, Azure or GCP written inside square brackets in two separate places. The employer has shipped the template without choosing. In practice that means the specific cloud is probably negotiable, but it is worth asking which one the team actually runs on before you prepare. Key responsibilities as listed: architect and maintain complex infrastructure modules using Terraform for consistent environments across development, staging and production. Design and deploy scalable, highly available and fault tolerant systems on a major cloud. Build and optimise automated deployment pipelines using Jenkins, GitLab CI or GitHub Actions for containerised applications. Manage and orchestrate containerised workloads with Docker and Kubernetes on EKS, AKS or GKE. Use Ansible or Packer to automate server configuration and image creation. Implement security as code by integrating automated vulnerability scanning and IAM policy enforcement into the infrastructure as code workflow. Work with development teams to containerise applications and give them self service infrastructure. Required technical skills: expert level Terraform including state management, workspaces and reusable module development. Strong hands on cloud services covering VPC, IAM, compute, RDS and S3. Proficiency in Kubernetes and Docker including writing Dockerfiles and managing manifests or Helm charts. Advanced scripting in Python, Bash or Go. Expert Git knowledge including branching strategies and GitOps workflows. Experience with build tools such as Maven or Gradle for Java, Node or Python environments. Who this is for: an infrastructure engineer five to eight years in whose strength is Terraform and who wants a platform building role rather than a support rota, and who can commit to a full time office return in Hyderabad. If hybrid or remote matters to you, this is a clear no.

6

6sense

Viewed

Stated requirement is 6 or more years of industry experience building and deploying machine learning systems in production, with clear end to end ownership. What we are looking for, as listed: a strong foundation in machine learning and applied statistics, with hands on depth in NLP, transformers, embeddings and retrieval based systems. Practical experience with modern generative AI tooling such as LangGraph, LangChain or Amazon Bedrock. Strong Python skills and experience building distributed ML pipelines on cloud infrastructure such as AWS or Databricks. A solid grasp of feature engineering, model evaluation and MLOps practice. A product mindset, wanting to build AI products customers use and measuring yourself on customer impact. Excellent communication, including explaining complex technical work clearly and holding your own with product and business partners. Comfort with ambiguity and the judgement to drive execution independently. Nice to have: experience with RAG architectures, vector databases and prompt engineering. Hands on work with PyTorch or TensorFlow. A background in B2B SaaS, enterprise AI products or forward deployed engineering, especially where you worked directly with complex customer data and delivered quickly. What you would own: machine learning problems end to end, from data exploration and modelling through deployment, monitoring and iteration in production. Building NLP, LLM and agentic systems at enterprise scale including retrieval based architectures and multi agent workflows. Developing ranking, recommendation, prediction and optimisation models that are explainable rather than black box. Partnering with product and go to market teams to turn ambiguous business problems into shipped capabilities. Improving performance, scalability and reliability of production ML systems and helping shape AI platform architecture. Location: Bengaluru. The team is distributed across the United States and India, though the posting does not state the role as remote. Who this is for: an ML engineer six or more years in who ships to production and wants the explainability problem specifically. The ad says plainly this is not a research role, so if you want to publish rather than deploy, look elsewhere.

Z

Zeta

Viewed

Stated requirement is 6 to 10 years of experience in distributed systems, storage systems or databases, algorithms and data structures, or Unix and Linux systems internals such as filesystems and system calls, and administration. A Bachelor's or Master's degree in engineering, specifically computer science or information systems, is also listed. What makes this different from a general DevOps posting: the requirement is written around systems fundamentals rather than a tool list. Filesystems and system calls are named directly, as are algorithms and data structures. If your reliability experience is mostly pipeline and dashboard work, the interview will likely go somewhere you are not expecting. If you have debugged a kernel level or storage level problem in production, this is aimed at you. Also listed: excellent communication skills and a sense of ownership, with a systematic problem solving approach. Context on the platforms you would be keeping up, from the ad: Tachyon, the cloud native banking stack built for population scale systems. Cipher, a unified authentication platform for secure high volume banking environments. Digital Credit as a Service, letting banks launch credit lines on UPI. Elena, a conversational AI platform for banking. Pixel, described as India's first digital native credit card, launched with HDFC Bank, for whom Zeta also rebuilt the PayZapp app. Sparrow, a card experience for non prime cardholders in the United States. Location: Hyderabad. The posting does not state a working pattern. Who this is for: an SRE or systems engineer six to ten years in who wants financial infrastructure where failures are expensive and visible. Banking and payments work carries real compliance weight and real out of hours pressure, and the upside is depth you cannot easily get elsewhere. Note the title says Lead, but the requirements are all hands on engineering rather than people management.

M

MongoDB

Viewed

Stated requirement is 6 or more years of professional software engineering experience. The ideal candidate, as listed: deep experience with at least one modern programming language, with Python, Go and Rust named as examples. Strong technical judgement and the ability to independently solve complex engineering problems. Excellent communication and comfort collaborating across teams and disciplines. Comfortable with modern infrastructure and delivery systems including containerised applications, Kubernetes and CI/CD tooling, with Drone.io named as an example. Collaborative, detail oriented and interested in building reliable, usable software. A bonus is experience building and maintaining full stack applications from front end interfaces through to backend APIs. Position expectations: own the implementation and long term maintenance of internal tools and platforms. Lead technical design discussions and contribute to architectural decisions. Write high quality maintainable code and set a strong engineering example for the team. Identify and proactively address technical debt, reliability risks and scalability concerns. Collaborate with engineers, product partners and other stakeholders to prioritise and deliver high impact work. The success measures published in the ad, which are worth noting because most postings do not commit to any: within three months, demonstrate strong ownership of one or more internal systems and contribute significantly to ongoing initiatives, and independently deliver meaningful improvements that reduce manual effort or operational friction. Within six months, have driven technical improvements or new tooling that measurably improves internal engineering efficiency, reliability or velocity. Location and working pattern: the posting says MongoDB is looking to speak to candidates based in Gurugram for its hybrid working model, so this is a hybrid role tied to that city. Who this is for: an engineer six or more years in who is happy that their users are colleagues rather than customers, and who wants the latitude of a team being built rather than one already running. Internal tooling work is often undervalued on a CV but the ownership here is broad and the success measures are unusually concrete.

N

Netradyne

Viewed

Stated requirement is 6 to 8 years of technical support experience, preferably with SaaS or cloud based platforms. Two things to weigh, both stated in the ad rather than inferred. First, the title says Lead and the requirement is six to eight years, but the job summary describes the role as a key first level liaison between the company and its customers. First level at six to eight years is an unusual combination, so it is worth asking in interview what the Lead in the title actually confers. Second, this is a 24x7x365 operations centre and the posting states that candidates must be flexible to work any shift based on business needs, including Saturday or Sunday. Must have skills as listed: 6 to 8 years of technical support experience, preferably SaaS or cloud. Basic SQL knowledge and working experience with one or more databases such as Postgres or MySQL. Familiarity with ITSM tools such as ServiceNow, Jira or Salesforce. Good hands on experience with REST APIs and webhooks. Experience analysing, investigating and identifying the root cause of complex customer issues and communicating findings to the right group. Strong problem solving and communication skills. The ability to work in shifts and under pressure. A proven ability to collaborate in a fast paced team. The ad also asks for strong English communication, excellent customer relationship skills, and prior experience supporting international customers, with United States or United Kingdom experience preferred. Key responsibilities: troubleshoot and resolve customer reported issues by phone, chat and remote tools. Perform root cause analysis and recommend corrective actions. Collaborate with engineering, QA and product teams. Work support rotations including incident escalation handling. Maintain case documentation and follow up with customers. Escalate unresolved or critical issues with supporting technical detail. One clarification on the word remote in this posting: it refers to remote troubleshooting tools used to reach customer devices, not to remote working. The role is based in Bengaluru. Who this is for: an experienced support engineer who wants hardware plus software problems rather than pure SaaS tickets, and who can work a rotating international roster.

D

Databricks

Viewed

Stated requirement is 7 or more years of professional experience in software development, with a Bachelor's or Master's degree in Computer Science, Electrical Engineering or a related field. Qualifications as listed: a deep understanding of JVM internals including garbage collection, JIT compilation, class loading and the memory model. Proficiency in at least one JVM language with extensive experience of its runtime environment. Strong programming skills in Scala, Java, Rust or other systems level languages. Extensive experience with operating system concepts including processes, threads, concurrency, scheduling and I/O. A proven track record of building and optimising high performance, scalable and reliable systems. Experience with distributed systems concepts and technologies. Excellent problem solving, analytical and debugging skills. Strong communication and collaboration. Experience with performance profiling and tuning tools. Contributions to open source projects related to the JVM or systems software. Experience with RPC frameworks. What you would do: design, implement and maintain core system infrastructure and low level software components. Optimise system performance, reliability and scalability. Work with JVM internals, memory management, concurrency and distributed systems. Collaborate with senior engineers and architects to define technical strategy and roadmaps. Mentor junior engineers. Take part in code reviews, design discussions and architectural decisions. Troubleshoot complex system issues. The ad is explicit about scope, and it is worth quoting the shape of it: this is not a full stack role, and the expertise is meant to be focused on the intricate details of system internals, performance and efficiency. Applying with a general backend CV and hoping to learn JVM internals on the job is unlikely to work here. Location: Bengaluru. The posting does not state a working pattern. Who this is for: a systems engineer seven or more years in who has genuinely tuned a JVM in anger, profiled garbage collection pauses, or written performance critical Scala, Java or Rust. If that describes you, this is one of the more technically serious postings in today's edition.

E

Elastic

Viewed

Stated requirement is 7 or more years of experience in technical support, system administration or a related customer facing role, with a technical background in systems administration, network engineering or software engineering. What you bring, as listed: strong verbal and written communication in English. A customer oriented focus. A good understanding of cloud native and container based technologies, including cloud platforms such as AWS, GCP and Azure and frameworks such as Kubernetes and Docker. An understanding of the product lifecycle and future direction for the supported products. A strong understanding of cloud native and container based distributed systems such as Kubernetes. Advanced hands on generalist experience across Java including the JVM and its components, operating systems including Linux and Windows, and networks including LDAP, load balancers, proxies and SSL. Experience with APIs and REST calls. Experience with web and application servers such as Tomcat, Apache, IIS, NGINX and JBoss. Advanced troubleshooting in web technology systems including HTML, CSS and JavaScript. Experience with SSO, SAML and Active Directory. Bonus points: knowledge of databases or search software technologies, experience with SaaS or distributed systems, being a team player able to work in a fast paced environment, a proven strong technical understanding of software products, and collaboration with developer teams on escalation issues. The ad also says curiosity is key and suggests researching and downloading the products before applying, which is a reasonable hint about how the interview will go. What you would be doing: ensuring technical customer issues are serviced within contractual service level agreements and managed to resolution. Maintaining strong customer relationships for the delivery of technical support. Resolving customer problems by telephone, email, chat or remote access. Continuously improving support process efficiency and customer satisfaction. Working across multicultural and geographically distributed teams. Contributing to product documentation, the customer knowledge base and best practice guides. Location: Bangalore. The team is described as spread across 12 time zones and 15 countries working as one unit. Who this is for: an experienced support engineer who wants genuinely deep technical work and direct contact with product engineers, rather than a tiered script. The Java and Linux depth asked for here is closer to an engineering requirement than a typical support one.

A

Adyen

Viewed

Stated requirement is a minimum of 5 years of experience writing Kotlin and a minimum of 8 years of experience building software for the Android platform. Two separate minimums sit in the same must have list, and the higher one is the real gate. We have published 8 years for that reason. A parser taking the first or lowest number here would advertise this as a five year job, and a five year Android developer would be rejected on the second line. Must haves, as listed: minimum 5 years writing code in Kotlin. Minimum 8 years building software for the Android platform. Experience developing enterprise level SDKs. Expert level knowledge of Kotlin, the Android SDK, Jetpack Compose, Coroutines, Gradle and dependency injection. Taking ownership of features from design and implementation through deployment and maintenance. A high level of personal accountability with strong technical skills, creative problem solving and a collaborative spirit. Experience writing and maintaining a comprehensive suite of automated unit and integration tests. The ability and desire to mentor and grow other engineers through code reviews, design reviews and over the shoulder debugging. Excellent verbal and written communication in English. Good to haves: Kotlin Multiplatform for cross platform development. Additional programming experience in C, C++ or Python. Card payment knowledge covering EMV and ISO8583. Experience building libraries used by other engineers. Knowledge of security best practices and standards. Experience in the payments industry. What you would do: work on solutions for Adyen's payment terminals covering card payments, Apple Pay and Google Pay on mobile phones, and QR code payments, and communication with the Adyen backend. Develop the main business logic in Kotlin, deployed on both Android based terminals and mobile phones. Own features end to end from design and implementation through testing and monitoring. Location and working pattern: Bengaluru, and the ad states directly that Adyen is an office first company that values in person collaboration and does not offer remote only roles. That is unambiguous, so do not apply hoping to negotiate it. One line to weigh: the role description mentions driving technical strategy and building a high performing team. Every listed requirement is hands on engineering and no reports, hiring or performance duties are named, so we read this as senior individual contributor scope with mentoring attached. Who this is for: an Android engineer with eight or more years who wants low level payments and SDK work rather than app features.

A

Agoda

Viewed

Stated requirement is 8 or more years of experience in software engineering, with a strong record of technical leadership and end to end ownership. What you would do: lead full stack architecture and system design for features used by millions of customers across web and cross platform environments. Own complex end to end systems, taking responsibility for building, integrating and maintaining both frontend and backend components including the backend for frontend layer, which the ad calls out as critical. Mentor and guide high performing teams, providing technical leadership and supporting the growth of peers. Drive technical decisions and influence architecture and best practice across multiple squads. Collaborate with product and design to deliver features and experiments that affect business outcomes. How the company frames the level: the ad describes Staff Engineer as a key role working with individual contributors and senior leadership, says its lead engineers are heavily involved in hiring and mentoring, and expects the person to push Agoda forward technically by adopting new technologies and setting higher standards. Involvement in hiring here reads as interviewing and technical assessment rather than people management, since no reports or performance responsibilities are named and the role is described as designing and implementing systems. About the team: the Full Stack Engineering department has several front end focused teams covering accommodations, flights, payments, marketing and post booking. Teams work across the stack and build end to end systems including user interfaces, APIs, backend systems and database systems, with a high degree of automation, CI/CD and a modular approach, and products under continuous experimentation. Location and working pattern: the title itself specifies Gurugram based, so treat the location as fixed rather than flexible. The posting does not state office days. Who this is for: a senior engineer eight or more years in who wants architecture scope across both halves of a large consumer product, and is comfortable that the weighting is backend. If you want to specialise narrowly in one layer, the breadth expected here works against that. If you want influence across squads without moving into management, it fits well.

Z

Zscaler

Viewed

Stated requirement is 8 or more years of experience in customer facing technical roles, featuring 3 or more years driving value in Technical Account Management, Customer Success, Solutions Delivery or Sales Engineering, within cloud, web security, networking or infrastructure domains. We publish this as an eight year role. The three year figure is a subset requirement describing how much of the eight has to be in a specific discipline, and reading the smaller number as the entry bar would send a three year candidate into an application they cannot pass. Minimum qualifications as listed: the 8 or more years above. Strong technical acumen with the ability to align customer business challenges to the Zscaler portfolio for the security outcomes they want. A proven ability to analyse customer data to gain insights and develop tailored adoption strategies and risk mitigation plans. A foundational understanding of AI and ML technologies and experience using, securing or positioning AI driven solutions within your domain. A solid understanding of core networking protocols such as HTTP, DNS and SSL, and technologies including DLP, sandboxing, SD-WAN and CASB, with some ability to troubleshoot network issues using tools such as Ping, Traceroute and MTR. Preferred qualifications: experience using AI powered operational analytics or predictive health scoring dashboards to evaluate deployment health, uncover adoption blockages and mitigate customer risk, plus an in depth understanding of enterprise infrastructure and cloud security. Relevant industry certifications are named, including CISSP, CCNP, CCIE, Network Plus, AWS, Azure and Google Cloud. What you would do: serve as a strategic technical advisor, understanding customer goals and guiding them through their zero trust journey as the central post sales point of contact. Build and nurture deep relationships with key customer stakeholders. Provide proactive recommendations so customers adopt and get the most from the platform. Location and working pattern: the ad states this is a hybrid role based in Bangalore, reporting to the Manager, Technical Success within the Customer Success department. Despite Manager appearing in the job title, this is an individual contributor role managing customer accounts, not people. Who this is for: an experienced pre sales or post sales technical specialist in networking or security who wants ownership of customer outcomes. Readers of this list asked for technical account management and customer success roles by name, and this is a senior example of exactly that.

O

Observe.AI

Viewed

Stated requirement is 9 or more years of experience across software engineering, network security and AWS security. What you will bring, as listed: a proven track record as an experienced infrastructure security designer implementing secure cloud, networks and corporate IT infrastructure, and experience working at a SaaS product company. What you would be doing, grouped as the ad groups it. On strategy: develop and document comprehensive security policies, reference architectures, design patterns and the strategic roadmap for infrastructure security, and keep current with network and infrastructure security practice. Collaborate with engineering, AWS and architecture teams so proposed designs meet both business objectives and security requirements. On technical design and architecture: provide technical leadership to build security into all infrastructure and network designs across AWS cloud, SaaS applications and IT environments. Design and re architect the AWS infrastructure to implement network segmentation, deep packet inspection, firewalls, VPNs and VPC configurations. Design secure access and network solutions for production environments and own the overall access management framework. Act as the security point of contact for change management, reviewing new infrastructure designs. Own and implement security components including privileged access management, Access Analyzer, Identity Center and role based access control, GuardDuty and web application firewall. Design and architect integrations with security tools such as SIEM and cloud workload protection. On compliance and partnership: represent infrastructure security during regulatory and compliance audits including PCI, SOC, ISO and HITRUST. Work with corporate IT to implement and continuously improve network and security controls in the corporate environment. Work closely with security operations and incident response teams providing technical leadership, and mentor junior infrastructure security professionals. Location: Bengaluru. The posting does not state a working pattern. Who this is for: a senior cloud security engineer who wants design authority rather than alert handling, and is comfortable that the scope includes corporate IT and audit representation as well as production AWS. Reporting into the VP of Information Security means short lines and real influence, and it also means the gaps are yours to own.

A

Appian

Viewed

Stated requirement is 10 or more years of professional software engineering experience. Education, as listed: a Bachelor's or Master's degree in Computer Science, Information Technology or a related field, with an educational background from a highly selective premier engineering institution focused on Computer Science fundamentals stated as preferred. That preference is in the ad, and it is worth knowing it is there. Experience and skills as listed: a strong understanding of data structures, algorithms, design patterns, and both object oriented and functional programming. A proven track record of leading technical initiatives from conception to global production deployment. Deep expertise in Java and modern web technologies with mastery of data structures, algorithms and complex design patterns. Extensive experience building and scaling distributed systems in AWS cloud native environments, and modernising applications and platforms. Strong knowledge of enterprise application architecture. Experience managing large scale codebases where performance optimisation and bottleneck identification are critical. Experience integrating AI and ML, specifically implementing intelligent features such as RAG or agentic workflows into enterprise software, is preferred, as is experience using AI tools and models such as Amazon Q, Kiro and Claude. Expert level proficiency in Java or a similar major language. Hands on experience with Docker, Kubernetes and advanced CI/CD automation. Deep familiarity with performance monitoring and observability. Key responsibilities: work with product leadership to turn long term business goals into scalable technical milestones and define the technical direction. Lead the design of distributed, event driven and cloud native systems, making high level decisions on system boundaries, data consistency and integration patterns. Drive adoption of AI native engineering, using AI tools to improve developer productivity and implementing AI features into the platform. Set and enforce the standard for system design and code quality, keeping the codebase maintainable. Location: Chennai. The posting does not state a working pattern. Who this is for: an architect level engineer ten or more years in who wants technical authority without moving into people management. The ad describes the role as the technical anchor and the architect of the team's success, so expect influence to be the main currency.

G

GitLab

Viewed

The posting states no number of years anywhere, and we have published it with no experience figure rather than inventing one. The requirements are written as capabilities instead, and they are substantial, so this is not an entry level role despite the absence of a number. What you will bring, as listed: experience owning complex customer facing technical cases from initial contact through triage, reproduction, bug reporting, resolution and clear customer communication, including difficult or escalated interactions. Strong experience with Linux systems administration, scripting, Git, and continuous integration and delivery in production or customer environments, with the ability to investigate issues at both infrastructure and application levels. The ability to mentor teammates on complex troubleshooting and customer communication through pairing sessions, case reviews and cross team collaboration. Experience collaborating with product, engineering and sales teams to turn customer feedback into product fixes, feature improvements and roadmap priorities. Familiarity with DevOps practices and technologies such as Kubernetes and serverless computing, and an understanding of how different GitLab implementations affect customers. A demonstrated ability to learn, collaborate across teams and apply transferable skills from related technical support or engineering roles. What the job actually is: sitting at the intersection of support and engineering, helping customers running GitLab in demanding environments. Working in the Engineering department directly with customers as they hit edge cases. Digging into Linux systems, logs and the Ruby on Rails codebase to troubleshoot performance issues, reproduce bugs and contribute merge requests that fix problems at source. Improving documentation and refining support processes in the issue tracker. Location and working pattern: GitLab states that all of its roles are remote, though it notes some roles carry location based eligibility requirements. The listing is attached to Bangalore, India. We checked the remote claim against the posting text rather than a tag. The team is described as globally distributed across the Americas, Europe, the Middle East, Africa and Asia Pacific, working asynchronously, with shifts structured to support personal lives while meeting customer needs. Who this is for: a support engineer who can read and write Ruby and wants to fix bugs rather than route them, and who wants genuinely remote work. The transferable skills line means adjacent engineering backgrounds are welcome.