No roles match that combination.
Added September 4, 2026
Who this is for: a test or quality engineer who wants to work on data correctness and on evaluating an AI agent, rather than on user interface regression suites. What the posting describes: building confidence in the quality, reliability and correctness of data across an enterprise data platform. Working closely with data engineering, product management, analytics and AI teams to define robust validation strategies. Automating testing so data products meet quality standards. As the AI powered Analytics Agent expands, validating user intents, defining evaluation frameworks, and working on the accuracy and consistency of what the agent returns. An honest caveat about this listing: it is one of the thinner advertisements in today's edition. Tekion describes the team and the mission clearly but does not publish a years figure, a named tool list, or an office days policy on this requisition. If the specifics matter to you, and for a testing role they usually do, treat the first recruiter call as the place to establish them. What the title suggests: the two in Software Development Test Engineer II is Tekion's second rung. Across today's Tekion advertisements the same company uses five to seven years for Senior, eight or more for Staff and nine or more for its Staff platform roles, so the two here sits below all of those. That is an inference from the sibling postings, not a figure this advertisement states. Location: listed as Bangalore HQ, which is Tekion's own shorthand for its Bengaluru office. The company does not publish office days on this listing. Experience: not stated anywhere in the posting, so this listing appears in no years band on our filter.
Who this is for: a Java backend engineer with five or more years who has built microservices at scale and wants enterprise domain work. What the posting asks for: a Bachelor's or Master's in computer science or a relevant field. Five or more years of relevant software engineering experience. Excellent Java and object oriented development skills. Experience building and scaling microservices. Strong problem solving, technical troubleshooting and diagnosis. Strong knowledge of both relational and NoSQL databases. Experience developing backends for enterprise systems, with ecommerce, manufacturing and supply chain named as examples. Excellent understanding of debugging, performance and optimisation. Hands on experience with Java, MongoDB, MySQL, AWS, the ELK stack, Spring Boot and Kafka. Experience with large scale cloud native applications. A strong understanding of large language model fundamentals. On the mentoring line: the advertisement says you are expected to be a role model for young engineers with a strong sense of code quality, and to enforce code quality within the team. We read that as senior individual contributor scope. There is no mention of direct reports, hiring or performance reviews anywhere in the posting, which is the line we use to separate an engineering role from a management one. The day to day: backend service work on a platform where the domain is genuinely complicated, and where correctness across dealership operations matters more than novelty. Location: Bangalore HQ, Tekion's Bengaluru office. No office days policy is published on this listing. Experience: five or more years, stated in the qualifications.
Who this is for: a Staff level engineer with nine or more years who has built platform infrastructure, and who has real depth in large language model systems rather than in consuming them. What the posting asks for: a Bachelor's or Master's in computer science or a relevant field. Nine or more years of relevant software engineering experience. A strong sense of ownership and technical leadership. Excellent Java and object oriented development skills. Deep experience building and scaling microservices. Experience developing backends for enterprise systems such as ecommerce, manufacturing or supply chain. Excellent understanding of debugging, performance and optimisation. Experience with Java, MongoDB, MySQL, AWS, the ELK stack, Spring Boot and Kafka. Deep experience in cloud technologies and large scale distributed systems. Deep expertise in large language model systems, including model selection and evaluation. What you would actually own: the technical vision and architecture for the AI native platform layer that other Tekion products build on. Architecting the AI gateway as a highly available, multi provider abstraction over language model vendors. Leading the design of Tekion's Model Context Protocol ecosystem. On leadership: the advertisement asks you to be a role model for engineers, enforce code quality and drive engineering excellence. As with the other Tekion listings, there is no mention of direct reports, hiring or performance management, so we read it as individual contributor scope with architectural authority. Location: Bangalore HQ, Tekion's Bengaluru office. No office days policy is published. Experience: nine or more years, stated in the qualifications.
Who this is for: a kernel or systems engineer who already works in Linux storage or networking subsystems. This is not a role you move into from application development. What the posting asks for: proven expertise in Linux and Unix kernel development and in writing robust device drivers, specifically within storage or networking subsystems. Deep technical command of storage protocols such as NVMe over TCP, RoCE and Fibre Channel, or SCSI including FCP and iSCSI, including experience designing and implementing significant components of those stacks. Demonstrated ability to lead complex engineering projects from conception to delivery while mentoring peers. Expert level debugging of complex system and kernel issues, and a track record of using performance analysis tools to find and remove storage bottlenecks. The office question, and it is a real one: the advertisement says Everpure is primarily an in office environment and that you will be expected to work from a named office, but the name is missing. The sentence contains an unfilled template variable where the location should be. The listing is placed in Bangalore, so that is the reasonable assumption, but the advertisement itself does not say it. Three Everpure listings in today's sourcing carry the same unfilled placeholder. Ask which office and how many days before you go far into the process. Also worth knowing: Everpure renamed itself from Pure Storage and its own advertisements have not fully caught up, so the same posting refers to both names and the recruiting contact address is still the old domain. That is a rename in progress, not a different employer. Experience: no years figure is stated anywhere in this posting, so it appears in no years band on our filter. The nature of the work implies real seniority.
Who this is for: a backend engineer with seven or more years, ideally in Go, who wants distributed systems and infrastructure rather than product features. What the posting asks for: a BS in computer science. Seven or more years designing, developing and testing enterprise products, with Go preferred. A good understanding of microservice architectures and cloud native platforms. Experience designing and owning microservices that operate and scale in a distributed architecture reaching thousands of nodes. Expert debugging skills and the ability to work through ambiguous problems at scale in public and private cloud environments. Experience working with multiple stakeholders, from product management through to customer beta partners, in designing highly scalable production quality software. Proven design sensibility and willingness to work in a collaborative team environment. A solid computer science background in data structures, algorithms and software design. On the title: it reads Member of Technical Staff, Backend Engineering Lead. Everpure uses Member of Technical Staff as its actual engineering level and appends a descriptor, and across its eleven live advertisements that same title spans three to eight years. Nothing in this requirement list involves managing people, so read Lead as technical ownership of a component. The office reality: the advertisement states plainly that you must be willing and able to work in an open office environment. Everpure describes itself as primarily an in office employer. The listing is placed in Bangalore. Experience: seven or more years, stated in the requirements.
Who this is for: an experienced support or escalation engineer who is genuinely technical and is comfortable being the person a large angry customer is escalated to. It is a named reader request on this board, so it is worth saying clearly that this is a customer facing role, not a product engineering one. What the posting asks for: end to end technical troubleshooting and root cause analysis across multi vendor environments, covering Linux and Windows administration, cloud architecture on AWS, REST API services, virtualisation with VMware and Hyper V, and enterprise storage protocols including NFS, S3 and SMB. An in depth understanding of enterprise networking and systems architecture with hands on proficiency in DNS, HTTP, SSL and TCP over IP, and the ability to diagnose complex networking, replication, performance and capacity problems. Exceptional customer crisis management, including leading multi stakeholder technical calls, de escalating high pressure situations and turning complex engineering concepts into concise communication. A commitment to peer mentorship and to creating knowledge base content. What the job is really like: escalation work is reactive by nature and the pressure is real. The upside is unusually deep exposure to how enterprise systems fail, which is why people who have done it well tend to move into reliability or solutions architecture afterwards. Location: Bangalore. Everpure describes itself as primarily an in office employer, though this particular listing does not state a number of days. Experience: no years figure is stated anywhere in this posting, so it appears in no years band on our filter.
Who this is for: a detection engineer or threat researcher who already owns a domain and wants formal accountability for it, rather than working through someone else's backlog. What the posting asks for: deep detection experience in at least one of endpoint and managed detection, cloud and SaaS, identity, email or SIEM, plus the judgement to own that area. A track record of owning technical work end to end and being answerable for its quality without much oversight. A strong grasp of how attackers actually operate, and fluent use of MITRE ATT&CK to decide where coverage belongs. Detection as code as your existing way of working, meaning version control, code review and controlled deployment through Git and CI and CD. A foundational understanding of AI and machine learning technologies and experience using or securing AI driven solutions in your domain, which Zscaler now puts in the minimum qualifications on most of its advertisements. Preferred rather than required: experience using AI driven automation, large language models or machine learning to speed up detection engineering and threat analysis, and programming or scripting in Python, Go or Ruby. The day to day: taking complete accountability for a coverage domain's health, backlog and performance, being the point of contact for its efficacy, and personally solving the hardest detection problems so the rest of the team has patterns to follow. Location and working pattern: this is a hybrid role in Pune, stated in the advertisement, reporting into the Threat Hunting department. Zscaler publishes a hybrid working model and benefits page but does not put the number of office days on this particular listing. Experience: no years figure is stated anywhere, so this appears in no years band on our filter.
Who this is for: someone from a customer facing technical consultancy or success background in cybersecurity who wants strategic enterprise accounts rather than a ticket queue. This is a directly requested category on this board. What the posting asks for: experience in a customer facing technical consultancy or success role within cybersecurity. A proven track record of executive stakeholder management, strategic customer engagements, and conveying complex technical concepts clearly. Hands on experience analysing technical environments, working across functions and troubleshooting critical customer escalations. A background in data modelling methodologies, SQL or ETL within technical or security domains. A Bachelor's degree in computer science, engineering or a related technical field. Demonstrated curiosity about AI tools and a history of integrating new technology into daily workflows. Preferred rather than required: deep domain expertise in vulnerability management programmes, enterprise risk scoring and security operations. On the job title, because it matters: Manager here refers to managing an account relationship. The posting reports into a Manager of Technical Success Management, and contains no direct reports, no hiring and no performance management. We publish roles like this because readers asked for them, and we exclude genuine people management roles, so the distinction is worth being explicit about. What it is not: this is a post sales technical role. It is not a quota carrying sales job, and the advertisement contains none of the sales target language that gets other listings excluded from this board. Location and working pattern: Bangalore, stated as hybrid. The number of office days is not published on the listing. Experience: no years figure appears anywhere in this posting, so it sits in no years band on our filter.
Who this is for: a cloud or infrastructure security engineer with five to seven years who works across all three major clouds and is comfortable owning identity and secrets infrastructure. What the posting asks for: five to seven years of experience, stated plainly. Hands on experience with Terraform and Ansible. A strong understanding of identity protocols including SAML, OAuth2, OIDC, LDAP and Kerberos. Experience with Azure AD and Entra ID, AWS IAM and GCP IAM. Expertise in HashiCorp Vault, Azure Key Vault and AWS KMS. Proficiency in Kubernetes RBAC, secrets management and workload identity management. A solid understanding of PKI, TLS certificates and cryptographic primitives. Strong Linux administration on RHEL, CentOS or Rocky Linux. Familiarity with firewall technologies, Fortigate in particular, covering firewall, NAT, VPN, IPS and URL filtering, and cloud security controls across Azure, AWS and GCP. Desirable rather than required: certifications in Azure Security Engineer, AWS Security or GCP Security, a network security certification such as Fortinet NSE4 or above, and the AWS Security Speciality. What to expect on working pattern: HighRadius is unusually direct about office attendance across its advertisements, and a sibling listing in today's edition puts five days a week in the office in bold. This particular advertisement does not repeat it, so confirm it for this specific requisition rather than assuming either way. Location: Hyderabad, Telangana. Experience: five to seven years, stated in the required skills section.
Who this is for: a DevOps or platform engineer with five to eight years who genuinely enjoys infrastructure as code, and who can work five days a week from an office in Hyderabad. What the posting asks for: expert level Terraform including HCL, state management, workspaces and reusable module development. Strong hands on experience with AWS, Azure or GCP covering VPC, IAM, compute, RDS and S3. Proficiency in Kubernetes and Docker, including writing Dockerfiles and managing manifests and Helm charts. Advanced scripting in Python, Bash or Go for automation. Expert knowledge of Git including branching strategies and GitOps workflows. Experience with build tools such as Maven or Gradle for Java, Node and Python environments. The ability to debug complex networking or deployment problems in a distributed system. The scope boundary, in the ad's own words: this role focuses strictly on provisioning, configuration management and CI and CD pipelines. If you want a role that also carries product reliability and incident ownership, this specific listing is narrower than that, which may be exactly what you want or exactly what you do not. The office policy: the advertisement states the work mode as five days working from office, and puts it in bold in its own text. Very few employers on this board publish attendance at all, so we surface it rather than leaving you to find out at offer stage. Location: Hyderabad, Telangana. Experience: five to eight years, stated as the experience level in the posting body.
Who this is for: a backend or platform engineer who works in Go or Rust and wants event driven, security sensitive infrastructure rather than product feature work. What the posting asks for: strong backend engineering in Go or Rust, with the advertisement stating directly that the team is moving away from Java heavy backgrounds for new platform work. Experience building event driven systems with Kafka, event sourcing patterns and at least once delivery guarantees. Familiarity with Temporal or another durable workflow engine. Experience with identity and access management systems covering OAuth 2.0, OIDC, token lifecycle management and fine grained authorisation models. A solid understanding of encryption patterns including envelope encryption, key hierarchy design and KMS integration. Comfort operating in multi tenant regulated environments where correctness and audit evidence are not negotiable. Strong observability instincts covering structured logging, distributed tracing and metrics. Preferred rather than required: experience with Zitadel, Keycloak or similar identity providers, and with ClickHouse or another columnar append only store. Why the Java sentence is worth taking seriously: most advertisements list preferred languages and quietly accept adjacent ones. This one states a direction of travel. Read it as a genuine filter rather than a preference, and if you are a Java engineer moving toward Go, say so explicitly in your application rather than hoping it is not noticed. Location: Pune. No office days policy is published on this listing. Experience: Kaseya publishes no years figure on this advertisement, so it appears in no years band on our filter. The Staff title and the scope of the surface imply real seniority.
Who this is for: a systems engineer who works close to the operating system and has built or operated isolation infrastructure. The pool of people who match this honestly is small, which is worth knowing in both directions. What the posting asks for: deep Linux systems experience across iptables and netfilter, process namespaces, cgroups, socket options and Unix domain sockets. Experience with at least one sandboxing or isolation technology, naming gVisor, Firecracker micro virtual machines, WebAssembly runtimes or equivalent. Strong networking fundamentals including the TCP and IP stack, transparent proxying, and TLS termination and origination. A language agnostic mindset, since you would design platforms other languages run on rather than systems tied to one runtime. Comfort working close to the operating system with memory management, process lifecycle and privilege separation. Go or Rust strongly preferred, with C and C plus plus experience relevant. Familiarity with SPIFFE or SPIRE or similar workload identity frameworks is called a strong plus. Preferred rather than required: experience building or operating multi tenant container or virtual machine isolation infrastructure, and prior work in security tooling, endpoint detection and response, or zero trust networking. On the title: Kaseya calls this Staff Systems Engineer, while the body calls the role an Intelligence Systems Engineer. The body is the more specific description of the work, and the two do not conflict about the level. Location: Pune. No office days policy is published on this listing. Experience: no years figure is stated anywhere, so it appears in no years band on our filter.
Who this is for: a DevOps, SRE or platform engineer with eight to twelve years whose Linux administration is genuinely deep, not just enough to use the tooling. What the posting asks for: eight to twelve years in DevOps, platform engineering, Linux administration or site reliability engineering. Strong Linux system administration expertise covering performance tuning, kernel parameters, storage and filesystem management, process management, system troubleshooting and networking fundamentals. Hands on experience managing Kubernetes clusters in production. Strong knowledge of infrastructure as code using Terraform or Pulumi. Experience designing and maintaining CI and CD pipelines with GitHub Actions, Jenkins, ArgoCD or equivalent. Experience with monitoring and observability using Prometheus, Grafana, Datadog or ELK. Strong scripting in Shell, Python or Go. Experience managing production incidents, on call support, alert tuning and operational excellence. A strong understanding of DNS, load balancers and firewalls. What the domain adds: backup and disaster recovery is a workload where storage behaviour and filesystem performance are the whole game, which is why the Linux requirement here is written more specifically than the usual DevOps list. If your background is Kubernetes and pipelines but thin on the operating system underneath, this listing will find that out. On call: the posting names production incident management and on call support as part of the role. Ask what the rotation looks like before offer stage. Location: Pune. No office days policy is published on this listing. Experience: eight to twelve years, stated in the required skills.
Who this is for: a test automation engineer roughly two to four years into their career. This is the lowest experience bar in today's edition, and we want to be straight about what that means: it asks for two or more years of relevant experience, so it is an early career role rather than a first job. Nothing in today's sourcing asked for under two years. What the posting asks for: a Bachelor's degree in a related field or equivalent business experience, and two or more years of relevant experience. Strong proficiency in Python or Ruby, with experience writing and maintaining automated tests using behaviour driven development frameworks such as Behave. Solid experience with Git version control including branching strategies, pull request workflows and managing Git submodules. Hands on experience integrating, executing and troubleshooting automated test suites within pipelines, specifically Jenkins or GitLab Runners. Practical experience interacting with, configuring or managing virtualised environments, particularly VMware ESXi. Solid knowledge of Linux, Windows and macOS including basic system administration and command line usage. Working knowledge of IP networking including TCP and IP, routing and subnets, and an understanding of basic firewall configuration. The ability to work independently on projects. What makes it a good early career role: the technologies named are ones you can learn and demonstrate on your own, and the mix of automation, virtualisation and networking is unusually broad for a role at this level. That breadth is worth more than the title. Location and working pattern: Pune, with the working condition stated as hybrid in the advertisement. Experience: two or more years, stated in the experience recommendations.
Who this is for: an engineer with eight or more years who is comfortable joining on the strength of the level and the company rather than a detailed technical brief. What the posting asks for: a Bachelor's degree in a related field or equivalent business experience, and eight or more years of relevant experience. The ability to manage projects and processes independently with limited supervision. Advanced knowledge of the applicable work area. The ability to adapt to new technology and processes as business requirements change. Knowledge of a variety of the field's concepts, practices and procedures. The ability to work constructively and independently under pressure in a fast paced, multitasking environment. The ability to manage competing priorities while producing high quality work. Strong verbal and written communication. Strong organisation and time management. Strong knowledge of programming languages and software basics, and of relevant development tools including version control. Our honest read: this is a thin advertisement for a principal level role. The technology names appear in the surrounding text rather than in the requirements, so we have listed them as context, not as a specification. There is nothing wrong with the role, but you will learn more in twenty minutes with the hiring manager than the posting tells you. What we can say concretely: ConnectWise serves roughly 45,000 partner businesses, so the systems are multi tenant and operate at real scale, and the Pune office runs engineering rather than only support. Location and working pattern: Pune. The sibling ConnectWise listing in today's edition states hybrid working conditions. Experience: eight or more years, stated in the experience recommendations.
Who this is for: an integration or enterprise applications engineer with eight or more years who understands finance systems and is comfortable working inside an audited environment. What the posting asks for: eight or more years in software engineering, integrations or enterprise applications. A strong finance systems background with hands on experience supporting and modernising finance business processes. Deep expertise in APIs, middleware, event driven architectures and enterprise integration patterns. Proven experience delivering AI, automation or intelligent process transformation. A solid understanding of SOX, audit, cybersecurity awareness and internal controls in an enterprise environment. A foundational understanding of AI and machine learning technologies and experience using or securing AI driven solutions, which now appears in the minimum qualifications on most Zscaler advertisements. Preferred rather than required: hands on experience with NetSuite, Workday, FloQast and Workiva. Being honest about what this is: enterprise systems engineering has a reputation problem among product engineers, and some of it is deserved. The compensating advantages are that the domain is genuinely intricate, the systems are business critical so quality is taken seriously, and the skills transfer across every large company. If the phrase internal controls makes you switch off, this is not your listing. Location and working pattern: Bangalore. Zscaler operates a hybrid model and links to its policy from the advertisement, but does not state the number of office days on this listing. Experience: eight or more years, stated in the minimum qualifications.
Who this is for: an engineer with five or more years who wants deep database and distributed systems work in a customer facing shape. This is one of the technical support and customer success roles readers of this list asked for by name. What the posting asks for: five or more years of proven experience, with the advertisement adding that MongoDB considers all candidates and looks particularly for people who are self taught and curious. The ability to work alongside the company's largest customers, resolving questions on architecture, performance, recovery and security. Expertise, or the ability to build it, in best practices for running MongoDB at scale. Comfort operating across Linux, the major clouds, containers, and the application languages customers build in. What the ramp actually looks like, because MongoDB publishes it: the advertisement sets out success measures. At three months you are expected to have a deep understanding of MongoDB and its ecosystem and to have completed new hire training. At six months you should be comfortable working directly with customers and to have completed the MongoDB Certified DBA Associate exam. At twelve months you would be working toward expertise within a technical specialism. Very few employers publish a ramp this explicitly, and it is a fair signal that the onboarding is real. One clarification: the six and twelve month figures above are onboarding milestones, not experience requirements. The requirement is five or more years. Location and working pattern: MongoDB states it is looking to speak to candidates based in Gurugram for its hybrid working model, so this is a location specific hybrid role rather than an all India one. Experience: five or more years, stated in the requirements.
Who this is for: an SAP developer with six or more years who wants to work where SAP meets a modern data platform, rather than in a traditional ERP consultancy. What the posting asks for: six or more years of SAP development experience with hands on delivery of at least one end to end SAP solution, an S4HANA extension named as an example. Domain knowledge in finance, procurement or supply chain that speeds up requirements understanding. Experience extending or customising Joule agents through SAP Build or Joule Studio, or building agents on SAP AI Foundation. Experience building applications on modern data platforms such as Databricks that extend or sit alongside SAP. Cloud native experience including containerisation and Kubernetes through Kyma, observability and scalability patterns. SAP certification in ABAP, SAP BTP or SAP Build, and prior work in a high growth technology company. What you would actually build: side by side extensions on SAP BTP, event driven integrations into the Lakehouse using OData and REST, IDoc, Cloud Integration and Event Mesh across a hybrid landscape, and AI assisted workflows over finance processes. Why the combination is worth noticing: SAP roles and modern data platform roles usually sit in different companies and different career tracks. This one is inside a data platform vendor, so the ERP work is expected to integrate with a Lakehouse rather than stay in its own world. If you have been trying to move an SAP background toward data engineering, this is an unusually direct route. Location: Bengaluru. No office days policy is published on this listing. Experience: six or more years, stated in the qualifications.
Who this is for: a backend or infrastructure engineer with seven or more years who wants to work on telemetry, metrics and diagnostic systems at large scale. What the posting asks for: seven or more years of production level experience in at least one of Python, Java, Scala, C plus plus or a similar language. The advertisement leads with the production qualifier, which matters: this is a role about systems that are already carrying load, not about building something new in isolation. What observability work involves in practice: building and running the systems that collect, store and query metrics, logs and traces for a platform that thousands of organisations depend on. The engineering difficulty is usually volume and cardinality rather than logic, and the constraint is that your systems have to stay up precisely when the platform is having its worst day. If you have run into the limits of an off the shelf monitoring stack and enjoyed the problem, this is the job shape that follows. About the employer: Databricks states that more than 20,000 organisations rely on its Data and AI platform, including around 70 percent of the Fortune 500. Scale is genuinely part of the role rather than a recruiting line. Being honest about the advertisement: it is lighter on named tooling than most listings in today's edition. The experience requirement is unambiguous, but the specific stack is worth asking about in the first conversation. Location: Bengaluru. No office days policy is published on this listing. Experience: seven or more years, stated in the requirements.
Who this is for: a full stack engineer with eight or more years whose centre of gravity is the front end, and who wants a product where the interface is the operational tool rather than a marketing surface. What the posting asks for: eight or more years of full stack software development experience. Expertise in JavaScript. Experience with HTML5 and CSS3 and modern component frameworks. Experience developing reusable user interface components in React, Angular 16 or later, JavaScript and HTML5 with CSS3. The ability to work in the web interface backend to support application service features, so this is not a purely client side role. Responsibility for making sure the interface works seamlessly across browsers, and for keeping up with web technologies the product might adopt. A levelling note worth knowing about this employer: Netskope states on several of its advertisements that the team hires across all levels and that candidates are individually assessed and appropriately levelled. That has appeared consistently on its postings over several months. It means the eight year figure on this listing is the stated floor for this title rather than a hard wall, and that a strong candidate slightly under it is usually levelled rather than rejected outright. We still publish the stated figure, because that is what the advertisement says. About the odd title: the listing carries a name in brackets, which is an internal hiring manager reference that Netskope has left in the public title. It is not part of the role. Location: listed as India, without a city. Netskope does not state a remote policy on this advertisement, so confirm the working location before assuming it is flexible. Experience: eight or more years, stated in the required skills.
Who this is for: a principal or architect level engineer with fifteen or more years who has owned the architecture of a high throughput data plane. What the posting asks for: fifteen or more years of overall experience, including eight or more years in the relevant specialism. The ability to set and drive overall architectural design and strategic technical direction for the Secure Web Gateway team. Experience understanding requirement specifications and designing and implementing high quality features with reliability, sustainability, scalability and observability for a data plane. Experience building sophisticated key management algorithms. The ability to work with product management to understand customer requirements and provide architectural guidance, and to provide technical leadership to other engineers. What data plane work means here: a secure web gateway sits in the path of customer traffic, so latency, throughput and failure behaviour are not quality attributes bolted on afterwards, they are the product. Engineers who have worked on proxies, network middleboxes or high performance traffic processing will recognise the shape immediately. On the levelling caveat: Netskope states across its advertisements that its teams hire across all levels and that candidates are individually assessed and appropriately levelled. We publish the fifteen year figure because the advertisement states it, but that standing sentence is a real signal that the number is a floor for the title rather than an absolute cut off. On management: despite the technical leadership language, this posting contains no direct reports, no hiring and no performance management. We exclude genuine people management from this board, and this listing does not cross that line. Location: listed as India, without a city, and no remote policy is stated. Confirm the working location. Experience: fifteen or more years, stated in the required skills.
Who this is for: a developer with three or more years in C sharp who wants systems level work, and who is comfortable that this is infrastructure software rather than web or application development. What the posting asks for: three or more years of software development experience. Proficiency in C sharp as the primary language, with good knowledge of C plus plus. Strong fundamentals in data structures, algorithms and object oriented design. Experience designing, developing, testing and maintaining software in C sharp and .NET. The ability to build efficient, scalable and reliable solutions. Experience with multithreaded and concurrent applications. The ability to debug complex software issues. Why the language pairing matters: C sharp with C plus plus underneath is a specific combination, common in enterprise infrastructure products where a managed layer sits over performance sensitive native code. If you have only ever worked in web focused .NET, the C plus plus expectation is the part to prepare for. A detail Commvault includes that almost nobody else does: the company opens its advertisements with a recruitment fraud warning. It states that scammers impersonate its recruiters and leadership by email and text, that it never conducts interviews solely by email or text message, and that it never asks for banking details before your first day. That is good advice for any application you make anywhere, and it is worth repeating: no legitimate employer needs your bank details to make you an offer. Location: listed across Bangalore, Hyderabad and Pune. The advertisement does not state office days. Experience: three or more years, stated in the requirements.
Who this is for: a systems engineer with six or more years in Rust, Go or another performance oriented language who wants database internals and open source work. What the posting asks for: six or more years of software engineering experience with strong systems level skills. A strong programming background in Rust, Go, C plus plus or similar performance oriented languages. Experience designing or maintaining SDKs, libraries, connectors, or compute and data integration codebases. Exposure to data warehouses, query engines, Arrow and columnar ecosystems, or execution runtimes. A desire to build foundational platform components other teams and community members depend on. Comfort working in public code review loops, asynchronous first communication and collaborative RFC processes. A mindset grounded in debuggability, reliability and ownership in ambiguous problems. It separately mentions two or more years working in open source, SDK, runtime or low level integration environments, which is a narrower sub requirement and not the overall bar. Why we publish six rather than two: an automated reader taking the smallest figure in this advertisement returns two years. The qualifications line says six or more years of software engineering with strong systems level skills. We publish six, read by hand. An edge rather than a requirement: contributions to or interaction with Arrow, ADBC, DuckDB, Presto, DataFusion, Spark or ClickHouse, experience shaping adapter or plugin standards and driver contracts, and familiarity with the Rust async ecosystem. One thing to know about the employer: the advertisement says you may see references to both Fivetran and dbt Labs during recruiting, because the teams and systems are being integrated. That is expected, not a red flag. Location: Bengaluru, Karnataka. The listing carries an internal remote tag, but no remote policy sentence appears in the text, so treat the location as the office and confirm. Experience: six or more years.
Who this is for: an engineer who wants MLOps and platform work rather than model research, and who can work hybrid in Bangalore. What the posting describes: designing and overseeing the strategy and architecture of scalable AI and machine learning operations platforms and pipelines. Packaging and deploying models to production so they are reproducible and interpretable. Designing automated CI and CD pipelines to speed up model deployment. Provisioning and optimising infrastructure for training and serving using Docker, Kubernetes or serverless platforms. Implementing post deployment monitoring for model performance, data drift and latency, with Monte Carlo named as preferable. Automating retraining and data pipeline workflows. Managing the deployment of foundation models, fine tuning workflows and retrieval augmented generation stacks including vector databases and knowledge graphs, with AWS Bedrock preferred. Managing GPU and CPU utilisation to minimise cloud cost while keeping inference latency low. Versioning data, code and models with tools such as MLflow. Implementing data security measures and data governance compliance. The location contradiction, and why we are flagging it: the advertisement carries the internal tag LI-Remote, while the job title itself says Hybrid in Bangalore. Two other Smartsheet listings in today's sourcing carry the same remote tag, and one of those also says Hybrid in its own title. The tag and the title cannot both be right. We have published this as hybrid in Bangalore, because the title is the more specific statement and because it is the one that would actually govern your working week. If remote is what makes a job possible for you, confirm it in writing before you invest in the process. Experience: Smartsheet publishes no experience requirement anywhere in this advertisement. The only years figure in the text is the company saying it has been going for over twenty years, which is not a requirement. So this listing appears in no years band on our filter, and the II in the title is the only level signal given.
Who this is for: a platform or site reliability engineer with eight or more years who writes real code and wants to build tooling other engineers use, rather than to service requests. What the posting asks for: eight or more years in platform engineering, infrastructure engineering, DevOps or SRE roles, with real ownership of production cloud infrastructure. Strong software engineering skills in Go or Python, with the advertisement stating you should write tested, maintainable code and treat infrastructure automation as software rather than scripting. Deep hands on Kubernetes experience 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 experience across AWS, GCP and Azure called a strong plus given the multi cloud footprint. A track record of building tools or platforms other engineers use, naming internal CLIs, provisioning frameworks, self service portals and automation pipelines, and stating explicitly that maintaining existing infrastructure is not the same thing. On mentoring versus managing: the posting mentions leading, mentoring and technically guiding a team of junior and early career platform engineers. There are no direct reports, no hiring and no performance management anywhere in the advertisement, so we read this as senior individual contributor scope with technical guidance attached. The operational reality: it names deep operational ownership including being on call and root causing incidents, and describes a bias toward automating recurring problems away rather than repeatedly firefighting them. Location: listed as India without a city. Skyflow mentions a work from home expense in its benefits but states no remote working policy anywhere in the advertisement, so we have not described this as a remote role. If that is what you need, confirm it explicitly. Experience: eight or more years, stated in the requirements.
Who this is for: a mobile or desktop engineer with nine or more years who has shipped production applications and wants to work on the client layer of AI products under real Indian network conditions. What the posting asks for: nine or more years building production mobile or desktop applications that real users depend on, with strong ownership of what you shipped. Deep Kotlin expertise in production including coroutines, flows and modern Android architecture, plus comfort with Swift on iOS and at least one desktop platform among Windows, Linux and macOS. Hands on Kotlin Multiplatform experience on a shipped or in production product, specifically designing shared modules, managing expect and actual boundaries, and dealing with the real friction of sharing code across mobile and desktop. A strong command of native audio and streaming pipelines covering audio capture, playback, buffering, voice activity detection, codec handling and low latency streaming to and from model endpoints. Experience shipping applications that work in constrained environments, described as offline first, low bandwidth and low memory, and the advertisement adds pointedly that working on a flagship device over fibre is not the same thing. What you would own: the client application layer across mobile and desktop for Sarvam's consumer and enterprise products, named in the advertisement as Indus and Kivi and whatever follows them, with Kotlin Multiplatform as the unifying approach. The posting also asks you to mentor engineers across the client team on platform native depth and Kotlin Multiplatform discipline, which is technical mentorship rather than management. Why the constraint is the interesting part: most mobile listings describe features. This one describes an environment, and building for the bottom of India's hardware and network range is a genuinely harder engineering problem than building for the top of it. Location: Bengaluru. No office days policy is published on this listing. Experience: nine or more years, stated in the requirements.
Who this is for: an experienced test engineer who wants infrastructure and cloud platform testing, and who already uses AI tooling as part of how they work. The requirement worth reading first: Druva lists, under must have skills, that the engineer must demonstrate proficiency in using AI for routine tasks, including generating functional test cases from specifications or precise prompts and then automating those test cases using AI. That is not a bonus line on this advertisement, it sits in the must have section. Several employers in today's edition have moved AI tooling from the nice to have list into the requirements, and this is the most explicit example. What else the posting asks for: knowledge of Docker, Linux and Windows. A good grasp of networking and cloud architecture fundamentals, preferably with exposure to AWS or Azure networking, storage and compute. Proficiency in Python or Java, with Python preferred, and strong shell scripting. Hands on experience with SQL databases. Strong experience in REST API testing and backend automation. Experience in user interface automation, with Selenium or Playwright preferred. Proficiency with Git, Jira, XRay and Jenkins. Strong analytical and debugging skills. Exposure to load and performance testing. The day to day: independently creating comprehensive feature test plans aligned with development milestones, leveraging and extending automation frameworks, owning the complete test execution cycle for user stories, performing a mix of automated, manual, white box and black box testing, creating and documenting testbed setups, and reporting and tracking issues. Location: Pune, Maharashtra. No office days policy is published on this listing. Experience: Druva states no years figure anywhere in this advertisement, so it appears in no years band on our filter. The Senior Staff title is the only level signal given, and at most employers that sits well above mid level.
Who this is for: a backend engineer with seven or more years who wants senior individual contributor work on large scale systems. What the posting asks for: seven or more years of experience. Strong experience with high level and low level design for large scale systems. Proficiency in Java, Python or C plus plus. Expertise in data structures, algorithms and design patterns. Hands on experience with microservices architecture, RESTful APIs and cloud platforms across AWS, Azure or GCP. Knowledge of SQL and NoSQL databases and caching mechanisms. A Bachelor's or Master's degree in computer science or a related field. Preferred rather than required: experience with distributed systems, event driven architecture and messaging queues, exposure to CI and CD pipelines, Docker and Kubernetes. The duplicate requisition: HighRadius has this same description live under the title Software Development Engineer IV as well, and the two bodies are identical. We publish one of them. If you find the other one yourself, applying to both gets you nothing extra, and it is worth asking the recruiter which requisition is actually open and funded. On mentoring: the advertisement asks you to mentor and guide junior engineers on design and coding standards. There are no direct reports, no hiring and no performance management in the posting, so this is senior individual contributor scope. Working pattern: HighRadius advertisements in today's edition state five days from the office on at least one sibling role. This listing does not state its own policy, so confirm it directly. Location: Hyderabad, Telangana. Experience: seven or more years, stated in the required skills.
Who this is for: a backend or platform engineer with seven or more years who wants to work on machine learning systems without necessarily having held a machine learning job title. What the posting asks for: seven or more years of industry experience in backend or platform engineering or equivalent, with a BE or BTech preferably in computer science or an equivalent qualification. Experience in applied machine learning is stated as a plus, not a requirement, which is the detail worth noticing. Strong programming in Python, Java or equivalent, with data structures and algorithms and solid data engineering foundations. An understanding of machine learning best practices, with the advertisement naming training and serving skew minimisation, A and B testing, feature engineering and model and feature selection. Why that framing matters: most machine learning adjacent listings demand machine learning experience outright, which shuts out backend engineers who have built the systems around models without owning the models. This one inverts it, asking for backend and platform depth first and treating applied machine learning as an advantage. If you have built feature pipelines, serving infrastructure or experimentation systems, read this listing properly rather than filtering it out on the AI and ML in the title. What the domain involves: trust and safety work means detection systems where false positives harm legitimate users and false negatives cause real damage. Engineers who like problems with genuine consequences and measurable trade offs tend to find it more interesting than growth work. One caution about this employer: Airbnb has appeared on this board before with roles that were withdrawn and re opened under new requisition identifiers inside a week. This listing was verified live today, but apply promptly rather than sitting on it. Location: Bangalore, India. This is an India based listing, not one of Airbnb's United States remote roles. Experience: seven or more years, stated in the expertise section.
Who this is for: a test automation engineer with five or more years who has tested Salesforce specifically, and who works in Playwright rather than only Selenium. What the posting asks for: five or more years of quality assurance automation experience. Strong hands on Salesforce testing across Sales Cloud, Salesforce CPQ, Revenue Cloud and Service Cloud, with Commerce Cloud preferred. Strong experience with Playwright automation using TypeScript or JavaScript. Experience building and maintaining automation frameworks from scratch. A solid understanding of Salesforce business processes and end to end testing. Strong experience with REST API testing using Playwright or Postman. Proficiency in JavaScript or TypeScript and working knowledge of Java or Python. Experience with CI and CD tooling such as Jenkins, GitHub Actions, Azure DevOps or GitLab. Experience with Git and version control best practice. Strong analytical, troubleshooting and debugging skills. Good to have rather than required: experience with AI powered testing tools. A verification note, since this board promises every link is checked: ZoomInfo's careers site returns an automated blocking response to scripted requests, so the direct page could not be confirmed by our usual method. This posting was verified live through the underlying applicant tracking system interface instead, which returned the role as open with the title and the Bengaluru location intact. The apply link is the employer's own canonical one and will open normally in a browser. We would rather tell you how a listing was checked than quietly skip the check. Duplicate listing note: ZoomInfo has the identical job description live for Chennai as well as Bengaluru. They are the same role in two cities, so pick the one you can actually work from. Location: Bengaluru, Karnataka. Experience: five or more years, stated in the must have section.
Who this is for: a backend engineer who has already shipped and supported production services and wants remote work without leaving India. What the posting asks for: professional experience building and shipping production backend applications, with real fundamentals in programming, APIs, databases, testing, debugging and performance. Experience with Ruby on Rails or Go, though the advertisement says plainly that it values the ability to learn a language over mastery of one. The ability to take a feature from clarification through delivery and follow up, working independently and asking for input at the right moment. Sound judgement about security, reliability, performance, maintainability and operational risk, and an understanding of modular backend boundaries and what coupling costs you later. One requirement worth reading twice: GitLab lists AI fluency as a requirement, not a bonus. It asks for practical experience with AI coding tools including the ability to review and correct what they generate. Several employers now do this, and it has moved from the nice to have list into the requirements list over the last month. The day to day: working inside one product area, partnering with product management, frontend, infrastructure and security, and contributing to the quality of shared backend code rather than only your own corner. Location and working pattern: the advertisement says all GitLab roles are remote, and adds that some roles carry location based eligibility requirements, so confirm India eligibility with the recruiter. Communication is asynchronous and written, which suits some people and genuinely does not suit others. Experience: GitLab states no years figure anywhere in this posting, so this listing appears under no years band on our filter. Read the level word instead. Intermediate at GitLab sits above entry level and below senior.
Who this is for: a senior backend engineer who has designed systems rather than only built inside them, and who has genuinely shipped an agentic AI system into production rather than prototyped one. What the posting asks for: deep backend expertise across architecture, APIs, data systems and performance tuning in a complex product or service environment. Proficiency in modern backend languages and a deep understanding of systems programming, with the ad again saying it values adaptability over mastery of one language. Architectural judgement, specifically experience designing or evolving modular backend boundaries, bounded contexts and migration safe architectures. The ability to lead through influence and clear written communication rather than authority. The requirement most candidates will screen out on: proven experience building or operating agentic systems in production. The advertisement is unusually specific that prompt engineering does not count, and names architecting loops, tool use and error handling strategies that ensure reliability at scale. The day to day: working across product, frontend, infrastructure, data and security boundaries, making architectural trade offs, and helping define standards for a high scale global product. The ad frames it as moving beyond assigned work to actively improving reliability and performance. Location and working pattern: all GitLab roles are remote, with the caveat that some carry location based eligibility requirements. Asynchronous written communication is central to how the company operates, not an afterthought. Experience: no years figure is published anywhere in this posting, so it sits in no years band on our filter. The title is the only level signal GitLab gives you.
Who this is for: a release or DevOps engineer with seven or more years behind them who has run deployments for enterprise SaaS platforms, not only for a product codebase. What the posting asks for: a Bachelor's degree in computer science or information systems, or equivalent practical experience. Seven or more years in release engineering, DevOps or a related discipline. Experience with releases and deployments for enterprise SaaS applications such as Salesforce, Zuora or comparable business systems. Strong hands on experience designing and operating GitLab CI and CD pipelines, or a comparable system, in production. Proficiency in at least one scripting language, Python named specifically, with the ability to write maintainable automation and integrations. Experience with source control, branching and merging strategies, artifact management, automated testing, deployment orchestration and rollback. The mandatory AI clause: the advertisement states that hands on experience using AI assisted development and automation tools such as Claude, or comparable enterprise approved tools, is mandatory as part of day to day DevOps and release engineering work. It is listed among the requirements, not among the bonuses. If you have not used these tools in a working context, this specific listing will screen you out. The day to day: standardising how business critical enterprise platforms get released, building the tooling other engineering teams use to ship, and putting operational controls and governance around changes that touch revenue systems. Location and working pattern: all GitLab roles are remote, subject to location based eligibility that the recruiter can confirm. The company runs asynchronously and in writing. Experience: seven or more years, stated plainly in the posting, which makes this the rare GitLab advertisement that publishes a figure at all.
Who this is for: an engineer with five or more years who enjoys internal platform and integration work, and who is comfortable that this is enterprise automation rather than product engineering. What the posting asks for: five or more years in software engineering, enterprise automation, platform engineering, DevOps, integration engineering or a related field. Proven experience building production grade automation that removes manual operational or development work. Strong programming in Python, JavaScript or TypeScript, Node.js, Java or similar. Experience with REST APIs, webhooks, OAuth, event driven workflows, asynchronous processing and SaaS integrations. Experience with Git and GitHub, CI and CD pipelines, automated testing, release engineering and environment management. Experience with at least two enterprise platforms, preferably including Salesforce, NetSuite, AEM, Boomi or Okta. Hands on Salesforce work with Apex, SOQL and SOSL, Flows, the Salesforce CLI, metadata APIs and platform security. The title problem, stated plainly: the listing is titled Senior Software Engineer and the first line of the body says the company is looking for a Senior Automation Engineer. The requirements are automation and integration requirements throughout. This matters for levelling and for what your next role looks like, so raise it with the recruiter early. The day to day: reducing manual operational work across Okta's internal enterprise systems, building reusable integration patterns, and improving developer productivity for teams that are not your own. Location: Bengaluru. Okta does not publish an office days policy on this advertisement, so ask. Experience: five or more years, stated in the requirements.
Who this is for: a backend engineer with five or more years in Java or Go who wants identity and access work, and who is comfortable owning infrastructure alongside code. What the posting asks for: five or more years with Java, using Spring or Dropwizard, or with Go, and a deep understanding of multithreading and asynchronous processing. Experience building high performance RESTful APIs or gRPC services. Solid experience with relational databases, MySQL or PostgreSQL, and caching layers such as Redis, at scale. Hands on AWS experience across Fargate, EC2 and Lambda, and infrastructure as code with Terraform, with the advertisement stating you should be comfortable managing your own cloud resources. Strong proficiency with Docker and Kubernetes and with CI and CD automation using Jenkins, ArgoCD or GitHub Actions. Nice to have rather than required: an understanding of OAuth 2.0, OIDC and JWT tokens, particularly for service to service communication. Experience with Splunk, SignalFX or Datadog for monitoring and troubleshooting production issues. Familiarity with Kafka or SQS for cross service messaging. If you have the backend fundamentals but not the identity protocols, the protocols are the part the posting treats as learnable. The day to day: building and operating the services behind identity administration, which means real production ownership, monitoring and on call exposure alongside feature work. Location: Bengaluru. The advertisement does not state a number of office days, so confirm it with the recruiter. Experience: five or more years, stated in the required knowledge and skills section.
Who this is for: an SRE or infrastructure engineer with eight or more years who has led a real platform migration, not only maintained an existing cluster. What the posting asks for: eight or more years in SRE, DevOps or infrastructure engineering roles. Strong hands on experience architecting and operating cloud native distributed systems on AWS and GCP. Deep Kubernetes expertise on EKS and GKE covering design, provisioning, scaling and advanced production troubleshooting, with three to five years stated against the tool itself. Proven experience leading ECS to EKS or GKE migrations and driving microservice enablement at scale. Proficiency with infrastructure as code using Terraform across multiple providers, Ansible or CloudFormation. Solid coding and scripting in Python, Go or Shell aimed at automation and tooling. Advanced understanding of CI and CD pipelines using ArgoCD, GitLab CI or Spinnaker, plus Linux systems and networking fundamentals including Direct Connect and Interconnect, DNS, routing and load balancing. Experience managing cloud databases and caching systems such as RDS, Cloud SQL, Redis, Memorystore, PostgreSQL and MySQL. Why we flag the numbers: an automated reader that takes the smallest figure in this advertisement returns three years. The actual requirement line says eight or more. We publish eight, because that is what the experience sentence says, and the three to five figures are attached to specific tools. The day to day: operating production infrastructure, leading reliability and modernisation initiatives, and acting as the escalation point for Kubernetes and multi cloud problems. Location: Bengaluru. No office days policy is published on the advertisement. Experience: eight or more years.
Who this is for: an engineer with eight or more years who wants to work on authentication at consumer scale, where an outage is a login outage for everyone downstream. What the posting asks for: eight or more years of software development experience, stated in the section describing who is a good fit for the role. Depth in building and operating production services, an eye for detail and a bias toward user experience, since the product is a login flow that other developers embed. Comfort in a highly collaborative and remote friendly environment, in the ad's own words. Bonus points, explicitly not requirements: experience building APIs for mobile applications and SDKs, one or more years of identity and access management domain experience, experience with Go and Terraform, front end work in React or Vue, and a deep understanding of the Node.js event loop. Why we flag the numbers: read by a script that takes the smallest year figure in the text, this advertisement returns one year, because of the identity and access management bonus line. Read properly it is an eight year role. This is the single clearest example in today's edition of why the years on our listings are read by hand. The day to day: building and running the business to consumer authentication domain inside Auth0, working across Node.js and React on the front end with Java and Kotlin services behind, and caring about standards compliance because the product is an implementation of them. Location: Bengaluru, with the advertisement describing the environment as remote friendly. It does not state a remote policy or office days, so confirm before assuming. Experience: eight or more years.
Read this before you apply
- Nothing at one year or less today, and that is the real number. We read every one of the 193 genuinely new advertisements and not one asked for under two years. The lowest bar in this edition is the ConnectWise test engineering role at two years, then Commvault at three. The board itself is a different story: there are 22 roles live right now at one year or less, and you can open exactly that slice here: https://www.munotes.in/dailytechjobs?exp=0
- AI tooling has moved from the bonus list into the requirements list. GitLab's release engineering role states that hands on experience with AI assisted tools, naming Claude, is mandatory. Druva puts using AI to generate and automate test cases under must have skills. Tekion asks a Java backend role for large language model fundamentals. Zscaler now opens its minimum qualifications with AI understanding on most of its ads. Four employers, one edition.
- A remote tag that its own job title contradicts. Smartsheet tags three advertisements with an internal remote marker, and two of those say Hybrid in the job title itself. We published the AI and ML Ops role as hybrid in Bengaluru, because the title is the more specific statement. If remote is what makes a job possible for you, get it in writing before you invest in the process.
- Two roles where the smallest number in the ad is not the requirement. Okta's Auth0 role mentions one year of identity experience, but that sits under bonus points and the actual bar is eight years. Okta's Ecosystem site reliability role mentions three to five years against Kubernetes and cloud, while the requirement line says eight. Any tool that takes the lowest number in a posting gets both of these wrong, which is why we read them by hand.
- One employer publishes its office policy, and one forgot to fill in the office. HighRadius puts five days working from office in bold in its own DevOps advertisement, which is rare and useful. Everpure went the other way: three of its listings contain an unfilled template placeholder where the office name should be, so the ad never actually says which office you would be expected in.
- An advertisement whose title and body disagree about the job. Okta's Senior Software Engineer listing opens by saying the company is looking for a Senior Automation Engineer, and the whole requirement list is enterprise automation. Apply to the body rather than the title, and ask the recruiter which one the requisition is approved as.
- What we left out, and why. We rejected a Zscaler role advertised for Bangalore whose requirements include United States citizenship, which no candidate in India can satisfy. We also dropped 22 advertisements that were re posts of roles already on our board under fresh requisition ids, several roles that read as individual contributor jobs but ask for two or more years of managing engineers, and the usual sales framed engineer titles carrying quota language.
- Several roles from one employer. Okta accounts for four of today's list and GitLab, Tekion, Everpure, Zscaler, HighRadius and Kaseya three each, across 19 employers in total. They are separate teams and separate requisitions, not one job posted repeatedly. We say so rather than letting it look like padding.
We read every posting by hand before it goes on this page. The same write-up goes out to the daily email.