No roles match that combination.
Added August 28, 2026
Experience: 1 to 3 years in security engineering, automation or DevOps, or in software engineering with a security or compliance lean. This is a genuine early career opening. What the posting asks for: the ability to write and ship automation code, comfort integrating tools over APIs, and working knowledge of identity, endpoint and compliance systems. The role expects you to stand up and use MCP servers so AI workflows can reach internal systems safely, which is a specific and current requirement worth preparing for. The day to day named in the ad: automating evidence collection, control checks and reporting for compliance frameworks; building integrations and lightweight pipelines connecting security, IT, identity and compliance tools; automating access reviews, provisioning and deprovisioning checks and posture validation alongside IT; maintaining internal security tooling and scripts; and building dashboards and alerting so control status and gaps are visible. Read this before applying: the ad rules out the work a lot of security candidates actually want. If you are aiming at detection, threat hunting or incident response, this is explicitly not that role and the posting says so in its own note. Location: Pune. Fit: strong if you can code and want security depth. Weak if you want to be a SOC analyst.
Experience: 1 to 3 years in a customer facing technical role. The posting frames this as a next step for someone early in their career rather than a senior hire, and states plainly that you will not be thrown into the deep end. Required background named in the posting: experience in a customer facing technical role, willingness to learn cloud security, and the communication skills to troubleshoot with customers directly. Cloud security expertise itself is what you are expected to build here, not arrive with. The real day to day: supporting Orca customers alongside senior CSEs and Customer Success Managers, answering technical questions, troubleshooting platform issues, and gradually taking on more complex accounts and conversations as you ramp. Location and working pattern: India, Bangalore, listed as Remote in the posting. This is one of only two genuinely remote employers on today's board, and remote has been the single most requested thing from readers of this list, so it is worth flagging clearly rather than burying. Fit: strong if you have a year or two of support, implementation or technical account work and want to move into cloud security. The title on the board says Customer Success Engineer, but the seat being filled is the Associate one.
Experience: 2 or more years of relevant work experience. A Bachelor's or Master's degree in computer science or an equivalent field is named. Required background: proficiency in at least one general purpose language, with Go, Java, C, C plus plus, Scala and Python all named. A strong grounding in distributed systems and cloud is what the team is actually buying. Listed as a plus rather than a requirement: AWS, Azure, GCP or other public cloud experience, and knowledge of Docker, containers, Kubernetes and microservice architectures. Worth noting, because a candidate who has these but only two years should not self reject. Also named: a solid understanding of the software development life cycle, design patterns and engineering principles, strong problem solving and attention to detail, and the ability to work independently or in a team on complex, time sensitive projects. The real day to day: building cloud native protection software, then designing, developing, testing, deploying and improving it, while managing your own project priorities and deadlines. Location: Bangalore. Fit: strong for a backend engineer with two to four years who wants distributed systems depth at a listed security company.
Experience: 2 or more years in an SDET role, stated plainly in the requirements. What the posting asks for: in depth understanding of automation principles and tools, the ability to design efficient and maintainable automation suites for varied scenarios, and to develop deterministic automation cycles that ensure real test coverage rather than nominal coverage. Test strategy: designing comprehensive strategies that reflect how users actually behave, and building test plans that cover every layer of the test pyramid, adapting the approach when issues demand it. Also named: expertise in quality assurance principles applied to complex problems, using data analysis to find root causes, using metrics to track progress and quality, and collaborating with senior stakeholders to align automation work with business goals. The seniority note worth reading: the ad describes an SME who performs work independently with minimal oversight and advises others. That is a higher bar of autonomy than the two year figure alone suggests, so expect to evidence ownership, not just tool familiarity. Location: Bengaluru. Fit: strong if you have two to four years of hands on automation and can talk about test design, not just test writing.
Experience: 2 to 4 years of relevant experience in security engineering, vulnerability management or a related technical field. Required background named in the posting: hands on experience deploying, managing and operating modern vulnerability management platforms. This is the core of the role and is stated first. Also named: enthusiasm for infrastructure as code, a track record of using automation to improve efficiency, and experience collaborating across teams to actually reduce software vulnerabilities rather than only report them. The real day to day: maintaining Samsara's vulnerability management infrastructure, working alongside technical product managers and engineers across the company, and de risking software vulnerabilities to protect customers. The posting notes your work feeds the wider security and compliance strategy. A cultural requirement the ad states directly: it values working backwards from a defined outcome, and expects you to define success and align cross functional stakeholders towards it. Expect that to appear in interviews. Location: Bengaluru (BLR1 office). Fit: strong for a security engineer with two to four years who has run a vulnerability management tool in anger and can script and automate around it.
Experience: 2 to 4 years in security engineering, software engineering or a related technical role. What the posting explicitly does NOT require, stated in its own words: deep specialist expertise in vulnerability management or offensive security. What it asks for instead is a solid information security foundation, strong engineering skills, and the judgement to make sound security tradeoffs. If you have been self rejecting from AppSec roles for lack of a security title, read this one properly. The real day to day: building automation and tooling for the application security programme, turning manual and hard to scale security work into reliable automated systems; integrating security into the development lifecycle with automated checks in CI/CD pipelines and reusable secure by default components; supporting and extending the security stack (SAST, DAST, SCA and secrets scanning) so findings reach the right engineering team quickly; and helping developers interpret and fix what those tools report. AI is named as part of the job, not a bonus: prototyping and productionising AI assisted workflows for triage and to scale security work. Growth stated in the ad: room to build security depth and take on broader product security responsibility over time. You work closely with Engineering and Product. Location: India. Fit: strong for an engineer who codes well and wants to move into application security.
Experience: 3 or more years of overall software engineering experience, plus at least 1 year designing complex distributed systems. Note the shape of this carefully. The one year figure is a sub requirement about distributed systems specifically, not the overall bar, and an automated parser reading only the smallest number in this ad would wrongly file it as a one year job. The real floor is three. Core stack named: Golang and Python, AWS, and Spark, with experience across storage and data pipelines. Listed as preferred, at a noticeably higher bar: 5 or more years with Golang, 5 or more years with Protobuf, and 5 or more years with Apache Spark, mainly PySpark. Exposure to Airflow, Elasticsearch, Kafka and Parquet is also named. So the preferred profile sits well above the required one, which is worth knowing before you judge your chances. The real day to day: building performant APIs that serve as sources of truth for many internal systems; building and maintaining high throughput, low latency systems processing hundreds of millions of events per day; establishing reliable data pipelines; developing backend integrations with external applications; owning delivery of complex features end to end; and owning SLAs and SLOs for your systems. Working pattern: listed as Hybrid, Bangalore. Process note the ad discloses: Abnormal uses AI assisted tools in its hiring process. Fit: strong for a backend engineer with three to five years in distributed data systems.
Experience: 3 or more years of developer level Linux platform experience, stated under minimum qualifications. This is the lowest experience bar of the three Everpure roles on today's list, and a genuine mid level entry point into systems work. Required background named in the posting: strong programming skills in C, C plus plus, Python, Java, Go or another language, with a solid understanding of object oriented design, plus a strong understanding of modern technology architecture. The interest areas the team names: distributed systems, algorithms, operating systems, Linux kernel, database internals, hypervisors, containers, compilers and hardware. The ad says explicitly "or at least some of those", so a partial match is expected rather than disqualifying. The real day to day: designing and implementing new algorithms and technologies for high performance, highly reliable systems, with the posting setting the reliability expectation at six nines; owning delivery end to end from concept to shipped product; solving hard problems through persistence; and working across product management, development, system validation and support. Context worth knowing: FlashBlade customers run AI workloads, modern backup, Splunk and Elastic log analytics, Kafka data pipelines and Spark cluster computing, so the team studies how those systems actually use storage. Location: Bangalore. Fit: strong for a systems engineer with three or more years who wants storage and kernel adjacent depth.
Experience: 3 or more years in a DevOps, Site Reliability Engineering or related role. The real day to day, as listed: designing, building and maintaining the team's CI/CD pipelines to automate build, test and deployment; provisioning and managing cloud infrastructure using infrastructure as code, with Terraform and CloudFormation named as examples; implementing monitoring, logging and alerting to keep applications healthy and observable; working with developers to containerise applications with Docker and manage orchestration with Kubernetes or ECS; and building security into the infrastructure and applications. What the team is for, which shapes the work: Professional Services R&D designs and builds reusable, scalable assets and tools that make customer engagements more efficient and cost effective for Okta's delivery teams and partners. You are building for internal and partner users, not external customers. Worth weighing before you apply: the posting describes a new, dynamic group and a chance to join a strategic team from the ground up. Expect to define practice rather than inherit it, and expect ambiguity that comes with a team still forming. Location: Bengaluru. Fit: strong for a DevOps or SRE engineer with three to six years who wants ownership of a platform from the start rather than a seat on a mature one.
Experience: 3 or more years building backend systems, primarily in Node. A strong background building core components for scalable, high availability web applications and services is named. ⚠️ Two commitments stated plainly in the posting, worth reading before you apply. First, the role requires participation in a 24/7 on call rotation for business continuity and incident response. Second, MongoDB is looking to speak to candidates based in Gurugram for its hybrid working model, so this is not a remote seat. The real day to day: working with research, product management, engineering and design to define the first version and future evolution of MongoDB's AI interfaces; designing, building and delivering well tested core pieces of the platform, including the MongoDB MCP Server, Agent Skills, the Intelligent Assistant Platform and purpose built agents; taking ownership of ambiguous problems and driving them to completion independently; and contributing to architecture. The kind of engineer named: product minded, thriving on autonomy, taking pride in shipping, able to integrate with fast moving and often unproven technologies and make pragmatic decisions as requirements change. Culture note from the ad: MongoDB says it values intellectual curiosity and honesty and prioritises collaboration over competition. Location: Gurugram, hybrid. Fit: strong for a backend engineer with three or more years in Node who wants to work at the agent and database boundary and can accept the on call commitment.
Experience: a minimum of 3 years of hands on experience in ServiceNow development and implementation, stated directly. Platform breadth named in the posting: forms, lists, UI Pages, UI Policies, Client Scripts, Business Rules, Script Includes, Workflows, Flow Designer, Catalog Items and Notifications. Scripting is expected on both sides, server side and client side, using JavaScript, the Glide API, GlideRecord and other ServiceNow scripting frameworks. The data work, which is a real part of this job: designing and executing data migration, transformation, validation, cleanup, reconciliation and maintenance, and querying and manipulating platform data efficiently at scale. Quality and support duties: unit, system and integration testing plus support for user acceptance testing; and ongoing production support, defect resolution, performance tuning and continuous improvement of existing implementations. If you want a pure greenfield build role, note that supporting what is already live is explicitly in scope. Also expected: technical documentation covering designs, configuration guides, support docs and deployment procedures, and full participation in Agile ceremonies including backlog refinement, sprint planning, estimation, stand ups, reviews and retrospectives. Location: Bengaluru. Fit: strong if ServiceNow is already your specialism. This is not a general backend role and a generalist without platform depth will struggle against the requirement list.
Experience: 3 to 5 years of hands on experience with React, TypeScript, Tailwind CSS and modern UI component libraries such as Shadcn UI. Frontend specifics named: modern client side state management and data fetching libraries, with TanStack Query, Zustand and Redux Toolkit given as the examples. This is a more precise stack requirement than most postings give, so match your experience against it honestly. Backend and data: building reliable API services with Node.js or Python (FastAPI), and modelling, querying and optimising relational data in PostgreSQL, plus designing and maintaining clean RESTful APIs and microservices. Engineering practice expected: SOLID principles, common design patterns and clean code, and comprehensive test suites using Jest, React Testing Library or backend frameworks such as PyTest, with the goal of high coverage and preventing regressions. The real day to day: owning scalable, user facing web applications end to end, collaborating with product managers, designers and system architects to take features from design to deployment, participating in Agile ceremonies, and mentoring junior engineers through code review and technical guidance. Location: Bangalore, full time. Fit: strong for a full stack engineer with three to five years who is genuinely comfortable on both sides and knows this specific modern React stack, not just React in general.
Experience: 3 to 5 years in software engineering, technical consulting or automation roles. ⚠️ A clarification about location, because the wording invites a wrong assumption. The posting repeats a Quartz award naming Workato the number one best company for remote workers. That is a company level accolade in the boilerplate, not a statement about this job. The role is listed in Hyderabad, India, and nothing in the posting offers remote working for it. Do not apply expecting a remote seat on the strength of that line. The real day to day: supporting the provisioning and management of cloud environments and demo infrastructure, and building automations that keep those systems reliable, secure and scalable, working under the guidance of senior engineers on the Demo Infrastructure team. What the seniority signal means: the ad describes working under senior guidance, so expect a supported role with mentorship available rather than one where you set direction alone. That is a positive if you are moving into infrastructure automation from adjacent work. Location: Hyderabad, India. Fit: strong for someone with three to five years in automation, cloud provisioning or technical consulting who wants infrastructure work at a well capitalised enterprise software company.
Experience: 3 to 6 years of UiPath experience, with strong proficiency in UiPath Studio, Robots, Orchestrator, Automation Hub and other UiPath products. ⚠️ Remote status, stated by the employer: "All of our roles are remote, however some roles may carry specific location based eligibility requirements." GitLab is all remote by design rather than as a concession, which is why it appears repeatedly on this list. The posting is tied to India, so check the eligibility line on the application itself. The real day to day: designing, developing and implementing enterprise level RPA solutions using UiPath to automate manual and repetitive processes; collaborating with business stakeholders to gather requirements, analyse processes and propose automation that fits company goals; ensuring timely delivery and quality of the automations; providing production support; and continuously improving and optimising what is already running. A cultural requirement worth taking seriously: GitLab states that all team members are expected to incorporate AI into their daily workflows to drive efficiency and impact, and describes AI as a core productivity multiplier. This appears in the company section of every GitLab posting on today's list. Location: Bangalore, India, remote. Fit: strong if UiPath is your actual specialism. A general automation or scripting background without UiPath platform depth will not match this requirement list.
Experience: 4 or more years of relevant experience. A Bachelor's degree in a related field or equivalent business experience is named. Stack named in the posting: Java, with MQ and Kafka called out. Listed as good to have rather than required: AWS, specifically DynamoDB, S3 and Lambda. The real day to day: designing, building and maintaining large scale production services, web applications, data pipelines and streaming systems; working on systems critical to the company's current and future operations; and debugging production issues across services. The posting also names supporting engineering teams with high attention to detail, and researching, analysing and documenting findings. Scope note: the ad says this role may influence others within the software engineering team by explaining facts, policies and practices. That is peer influence, not people management, so it remains an individual contributor seat. Working conditions, stated in the posting: hybrid, Pune location. Fit: strong for a Java backend engineer with four or more years who has run services in production and wants scale. If you have Kafka or MQ experience the match is closer still. Note that ConnectWise has a second, more senior engineering role on today's list at 5 to 8 years, so compare the two before choosing.
Experience: 4 to 6 years of relevant work experience, with a BTech in computer science or a related field named. Stack required: strong experience in Java, and strong knowledge of at least one database from a list the posting gives as MySQL, NoSQL, SQL Server, Oracle and PostgreSQL. The real day to day: solving complex problems and building experiences for users at scale; collaborating with other teams to develop and ship solutions; ensuring the solutions and processes built are high quality; and creating scalable solutions relevant to the company's overall growth. The ad frames the core challenge as building resilient systems that manage millions of orders daily with zero downtime. Team culture, as the posting describes it: self starters who work well in a team and take constructive feedback, regular one to ones, open communication and an emphasis on each member's continuous growth. It states a preference for speed over perfection. Location: Bangalore, Karnataka. Fit: strong for a Java backend engineer with four to six years who wants very high throughput consumer scale at an Indian product company. This is a hands on individual contributor role, not a lead seat, despite the III in the title.
Experience: 4 to 7 years of relevant work experience. A degree in computer science or a related technical discipline is stated as required, not preferred. ⭐ The priority skill, flagged by the employer itself as the key requirement: hands on experience planning and executing migrations from Jenkins to Harness. If you have done exactly this, you are the target candidate and should lead your application with it. If you have not, expect to be competing against people who have. Must haves also named: a track record of building and shipping large scale engineering products, and working knowledge of cloud infrastructure such as Azure or AWS (given as preferred); experience with Shell, Python or other scripting languages; experience managing Linux systems and working with build and release tools including Jenkins; and effective written and verbal communication. Good to have, in the big data domain: support experience in big data; architecting, implementing and maintaining big data solutions; and the Hadoop ecosystem, specifically HDFS, MapReduce, Oozie, Hive, Impala, Spark, Kerberos and Kafka. Containerisation with Docker and Kubernetes and configuration management systems are also listed. Named explicitly in the posting: experience with AI assisted coding tools, with Cursor, Windsurf, Claude and GitHub Copilot given as the examples. Working environment: the ad asks for comfort in a fast paced start up environment and collaboration with engineers, data scientists and product managers. Location: Bangalore. Fit: strongest if you have run this exact migration.
⭐ Read the experience line in full before applying, because the ad contains its own contradiction, in its own words: "Minimum 5 years of development experience, but expect that typically candidates would have 15+ years experience." We have published the stated minimum of 5, because that is the stated minimum, but you should apply understanding that the employer has told you where the real bar sits. This is unusually candid, and useful: most postings leave that gap for you to discover after the first call. Scope, also worth reading carefully: the role opens as "team lead for a group of engineers". The requirement list asks for experience leading other engineers technically and the ability to mentor more junior engineers and lead others across a project. There are no direct reports, hiring duties or performance responsibilities named, so we read this as a technical lead seat rather than a people management one, but go in expecting leadership scope. Required background: strong experience writing device drivers or kernel development for Linux and Unix, with storage or networking drivers preferred; designing and implementing significant components in storage protocol stacks and storage systems; software development in C and C plus plus along with Python; and demonstrated experience debugging difficult protocol, kernel and system issues. Protocols named: SCSI (FC SCSI or iSCSI, FCP) and NVMe fabrics (NVMe over RoCE, TCP or FC), plus TCP/IP network protocols. VMware experience with an understanding of their initiator stack is asked for. Also named: performance analysis and optimisation for storage systems, experience upstreaming Linux code (preferred), and test automation development. Location: Bangalore. Fit: genuinely senior systems engineers only.
Experience: 5 or more years of overall industry experience in a relevant technical role. ⭐ An unusually useful note from the employer, quoted from the posting: this team is hiring across all levels, and candidates are individually assessed and appropriately levelled based on their skills and experience. In practice that means the 5 year figure is a reference point rather than a hard filter, and a strong candidate above or below it is still in scope. Few postings say this out loud. Required background: proficiency in at least one scripting language, with Python preferred. Hands on exposure to modern cloud technologies is central to the role, with Docker, Kubernetes, networking and the AWS and GCP platforms all named. The real day to day: ensuring reliable operation of production environments for Netskope's data infrastructure and products, running at scale on large volume distributed cloud systems; maximising system reliability; automating routine tasks; improving production efficiency; and assisting with capacity management by tracking CPU, memory, storage and traffic volume to forecast and scale infrastructure. Location: listed as India. Fit: strong for a DevOps or SRE engineer with five or more years who wants data platform scale at a listed security company. Given the levelling note above, it is also worth a look if you are somewhat under five years but strong on Kubernetes and Python.
Experience: 5 or more years of professional software engineering experience with a focus on backend systems, plus 3 or more years of hands on experience developing production applications with Golang. Note that both figures are stated, so the Go specific requirement is the tighter of the two in practice. The real day to day: designing and building highly scalable backend services, distributed systems and API infrastructure as part of a growing engineering team. ⚠️ Location clarification, same as Workato's other role on this list. The company boilerplate quotes a Quartz award naming Workato the number one best company for remote workers. That is an accolade about the company, not an offer of remote work on this requisition, which is listed in Chennai, India. Apply on the basis of the location line, not the award. Context on the employer: Workato describes itself as a leader in Enterprise MCP with a cloud native architecture connecting applications, data sources and processes for real time orchestration, and cites recognition from Business Insider, the Forbes Cloud 100 and Deloitte Tech Fast 500. Fit: strong for a backend engineer with five or more years overall and at least three years writing production Go. If your Go is recent or side project only, the three year production requirement is the line to check first.
Experience: 5 or more years in a software engineering role, with strong hands on backend engineering and cloud infrastructure experience, listed under basic qualifications. A second requirement of 1 or more years appears elsewhere in the ad for a narrower skill; the overall floor is 5, and an automated filter reading the smaller number would misfile this role as junior. ⚠️ Travel, stated in the posting: expect regular travel to customer sites to support scoping, prototyping and go live phases of an engagement, including in person workshops and executive readouts. This is a customer facing engineering role, not a desk based one, and that commitment should factor into your decision. The blend of skills named: AI and data engineering, cloud and security architecture, and customer facing solutioning. You operate across the full engagement lifecycle. The real day to day: scoping a customer's environment and pain points the way a consultant would; prototyping working demos quickly, in real time with the customer; and hardening the strongest patterns into production deployments for enterprise and campus customers. Location: listed as India. Fit: strong for a backend or data engineer with five or more years who genuinely enjoys customer contact and can hold a room with enterprise stakeholders. Weak if you want heads down engineering, because the customer facing half is not optional here.
Experience: stated in the posting as 5 years to 8 years. The work location and type are given in the same line: Pune, hybrid. Languages named: Go, Java or Python, carried in the role title itself. The real day to day, as listed: system engineering, meaning designing, building and maintaining large scale production services, web applications, data pipelines and streaming systems; active participation in an Agile and Scrum framework including sprint planning, daily stand ups, retrospectives and demos; and operational excellence, including debugging production issues. What the level means here: the posting describes developing high quality, innovative and fully performing software in compliance with rigorous coding standards, working with cross functional teams so that designs, code and tests land on time and in line with organisational standards. This is a hands on engineering role rather than a lead or architect seat. A note on choosing between the two ConnectWise roles on this list: this cybersecurity seat asks 5 to 8 years and names Go, Java or Python. The Senior Software Engineer II role asks 4 or more years and is Java focused with Kafka and MQ. The numbering is not a reliable guide to seniority across the two, so read both requirement lines rather than assuming II outranks I. Location: Pune, hybrid. Fit: strong for a backend engineer with five or more years who wants security domain work.
Experience: 6 or more years of production level experience in one of Java, Scala, Python, C plus plus or a similar language. A BS or higher in computer science or a related field is named. The two concrete problem areas the posting describes, which are worth reading as a choice between very different jobs under one title: First, infrastructure platforms. Building foundational infrastructure that supports operation across numerous geographic regions and cloud providers, and implementing cloud agnostic infrastructure abstractions so Databricks engineers can manage and operate their services more efficiently. Second, engineering productivity. Developing tools and processes that improve the developer experience across programming languages, linters, static analysis, IDEs, remote development environments, automated release pipelines and test automation frameworks. The posting states the current focus is optimising the Rust development experience across the organisation. Note on Rust: it is named as a current focus area rather than a stated requirement, and the listed language requirement is Java, Scala, Python or C plus plus. If you have Rust it is clearly relevant, but the absence of it does not appear to be disqualifying on the requirement line. Location: Bengaluru. Fit: strong for a backend or infrastructure engineer with six or more years who wants platform work rather than product features. Databricks has a second, far more senior role on today's list at 15 or more years, so check which one matches you.
Experience: 6 or more years of experience in data engineering, stated under qualifications. The core of the role: designing and evolving a multi tenant, cloud scale data platform that serves thousands of dealerships and business users, while maintaining strong tenant isolation, governance and data quality standards. The posting is explicit that this goes beyond traditional data engineering and is about shaping the enterprise data foundation. The architectural work named, which is the most useful detail in the ad: driving the evolution from batch oriented data processing to near real time and real time data ingestion architectures. This is a stated modernisation programme rather than a maintenance seat, so expect to be building the new path rather than only running the existing one. What that foundation powers: analytical products, operational insights and emerging AI driven experiences across the platform, with faster decision making and new machine learning use cases named as the goal. Employer context: Tekion's platform spans Automotive Retail Cloud for retailers, Automotive Enterprise Cloud for manufacturers and large enterprises, and Automotive Partner Cloud for technology partners, using big data, machine learning and AI. Location: Bangalore HQ. Fit: strong for a data engineer with six or more years who has worked on multi tenant platforms and wants to own a batch to streaming migration. Weak if your experience is analytics or reporting rather than platform engineering.
Experience: 7 or more years of expansive programming experience in an object oriented language such as Java, especially in backend services. A separate requirement names 4 or more years working with MySQL or an equivalent relational database system. A Bachelor's degree in computer science or equivalent is listed. Note the two figures: the overall bar is 7 years, and the database figure of 4 years is a narrower sub requirement. The higher number is the real gate. What the team owns: common shared services including search, cache, configuration management, frameworks for async job management and the email pipeline. These are the foundations other Okta engineering teams build on, so the blast radius of the work is large. Engineering environment named in the posting: cloud native, with redundancy, multi tenancy, scale, resource optimisation and resiliency as first class citizens, and a weekly release cycle. The ad ties this to Okta's Always On operating mantra. Also named: technical depth in architecting, implementing, tuning and debugging some of the largest cloud deployments in the enterprise world. Location: Bengaluru. Fit: strong for a senior backend engineer with seven or more years in Java who wants infrastructure and platform work at large scale rather than product surface work. Okta has three roles on today's list at different levels, so compare the requirement lines before choosing.
Experience: 8 or more years of experience in designing, development and testing of enterprise products, with Golang preferred. A BS in computer science is named. ⚠️ Working pattern, quoted from the posting: "We are primarily an in-office environment and therefore, you will be expected to work from the Bangalore office in compliance with Everpure's policies, unless you are on PTO, or work travel, or other approved leave." This is unambiguous, so treat it as a five day in office expectation rather than a hybrid one. The real day to day: designing and developing cloud native microservices and integrating new features into the Portworx products; focusing on design, development, unit and functional testing, code reviews, documentation and continuous integration and deployment; debugging product and performance issues in large scale clusters using AI tooling; collaborating with peers and stakeholders to take solutions from initial design to production; taking full ownership of design and development while adapting to customer feedback and handling issues found in unit testing, system testing and customer deployments; and experimenting with new technologies. Product context: Portworx is Kubernetes native storage and data management, so container orchestration is the environment rather than a bonus skill. Location: Bangalore, in office. Fit: strong for a senior Go engineer with eight or more years in enterprise product development who is comfortable with an in office commitment.
Experience: 15 or more years of industry experience building and supporting large scale distributed systems. This is the highest experience bar on today's list and it is stated plainly, so treat it as real. The specialism the team is actually hiring for: engineers with experience in core database internals. The central technical challenge named is extracting data from OLTP systems while imposing minimal load on those production systems, using techniques such as incremental data capture and log parsing. The product context: Lakeflow Connect provides ready to use, point and click connectors for enterprise applications (Salesforce, Workday, ServiceNow, SharePoint are named), databases such as SQL Server, cloud storage, message queues and local files. The cross platform element: ingestion is a key platform capability, not a standalone product. Every Databricks surface, with dashboards, notebooks, SQL and AI named, needs ingestion, so the posting says the person in this role works closely with other product teams to embed Connect into those surfaces. The ad is explicit that it wants engineers who remain hands on at this level rather than moving away from the code, and who want large impact on a strategically important problem. Location: Bengaluru. Fit: only for genuinely senior engineers with database internals depth. If you are at eight or ten years this is a stretch that the posting itself does not invite, and Databricks has a second backend role on this list at 6 or more years that is a better match.
Experience: no years figure is published anywhere in this posting. The clearest signal available is the grade in the title, Intermediate, which at GitLab sits below Senior and above Junior. We have filed this under roles with no published years rather than guess a number. ⚠️ Remote status, quoted from GitLab: "All of our roles are remote, however some roles may carry specific location based eligibility requirements." GitLab is structurally all remote rather than remote as a concession, which is why three of its roles appear on today's list. Check the eligibility line on the application. Stack named: Ruby on Rails and PostgreSQL. The real day to day: helping build the software that makes database upgrades safe, fast and predictable for GitLab.com and for self managed customers, on the team that owns the database upgrade experience within the Database Excellence stage. What the posting offers, in its own framing: an all remote, asynchronous, highly team based environment with mentorship, where you grow skills in backend engineering, system design and reliability. For a reader earlier in their career who wants remote backend work, this is the most accessible of the three GitLab roles here. What it asks for beyond code: strong written communication and comfort working asynchronously in an all remote distributed team. On a remote first team that is a genuine requirement, not a soft skill footnote. Location: Bangalore, India, remote. Fit: good for a backend engineer who wants Rails and Postgres depth and remote working.
Experience: no years figure is published in this posting. The title carries Senior, and the ad asks for an experienced product engineer, but no number is given anywhere, so we have filed it under roles with no published years rather than invent one. ⚠️ Remote status, quoted from GitLab: "All of our roles are remote, however some roles may carry specific location based eligibility requirements." Stack named: Ruby on Rails, with full stack experience wanted and the current focus on backend. What makes this role different from a pure backend seat, and the thing to weigh before applying: the posting asks for someone who will spend as much time understanding what users need and shaping how features should work as actually building them. You work directly with the product manager and engage with users. If you want tightly specified tickets, this is not that job. If you have wanted more say in what gets built, it is unusually explicit about offering it. Product area: Plan, covering the planning side of GitLab, specifically Planning Views. A cultural requirement in every GitLab posting: all team members are expected to incorporate AI into their daily workflows, which GitLab describes as a core productivity multiplier. Location: Bangalore, India, remote. Fit: strong for an experienced Rails engineer who genuinely enjoys product thinking and remote, asynchronous work. This is the most product facing of GitLab's three backend roles on today's list.
Experience: no years figure is published in this posting. ⚠️ A title inconsistency inside the ad itself, worth knowing before you apply. The posting is titled "Staff Backend Engineer - Database Change Management", but the opening line of the role description reads "As a Senior Backend Engineer, Database Upgrades". Staff and Senior are different rungs at GitLab with different compensation bands, so this is worth clarifying with the recruiter on the first call rather than assuming. We publish the advertised title. ⚠️ Remote status, quoted from GitLab: "All of our roles are remote, however some roles may carry specific location based eligibility requirements." The technical problem, which is the reason to read this one: replacing GitLab's sequential database migration system with a dependency graph model, making upgrades faster and safer for GitLab.com and self managed customers. The posting says you lead the design and delivery of that migration system. Why it is a real engineering challenge: sequential migrations on a large production PostgreSQL estate serialise work that could run in parallel and make long upgrades risky. Modelling dependencies between migrations is a genuinely hard correctness problem, not a refactor. Stack: Ruby on Rails and PostgreSQL, consistent with the team's other roles. Location: Bangalore, India, remote. Fit: strong for a senior backend engineer with deep PostgreSQL and Rails experience who wants a well defined, difficult systems problem and remote working.
Experience: 3 or more years of experience in the cybersecurity industry in a client facing role, with account management, customer success and technical account management named as the kinds of background that count. Why this role is on the list: Technical Account Manager and Customer Success Manager roles were requested by name by a reader of this list. A Manager title here refers to managing accounts and customer outcomes, not managing people, so it belongs on a board built for individual contributors. Two of today's roles fit that request, this one and LogicMonitor's Customer Success Engineer. The domain requirement is real: this asks specifically for cybersecurity industry experience, not general SaaS account management. If your background is client facing but in another sector, that is the gap to address in your application. The real day to day named in the posting: owning client relationships and outcomes, maintaining accurate records of customer interactions and activities in CRM, sharing knowledge, conducting training sessions and writing internal articles. Product context you would be supporting: XVigil, which maps digital assets, identifies threats, enriches them with cyber intelligence and provides remediation and takedown workflows; BeVigil, which uses mobile, web, network and encryption scanners to map known and unknown assets; and SVigil, which identifies software supply chain risks across software, cloud services and third party dependencies. Location: Bengaluru. Fit: strong for a client facing technical professional with three or more years inside cybersecurity.
⭐ Read the experience requirements together, because the first number is not the real one. The posting says 2 or more years of experience in customer facing support roles, and then lists three further requirements each asking for 3 or more years: supporting or administering SaaS ITIM products, Linux, Windows or network administration, and cloud platforms such as AWS and Azure. We publish 3 years, because a candidate with exactly two years would fail three of the four requirements. An automated parser taking the lowest number in this ad would advertise it as a two year job. The technical depth expected: this is not a relationship only success role. Administering observability or IT infrastructure monitoring products, real systems administration on Linux or Windows or networks, and working knowledge of the major cloud platforms are all asked for. Also named: the ability to follow a structured process and enter information accurately, and comfort working in a fast paced environment during rapid growth. Location, stated plainly: this position is located in Pune. LogicMonitor describes its offices as Centers of Energy where teams coordinate their in person time, so expect an office based pattern rather than remote. Product context: hybrid observability across on premises, cloud and edge, aimed at anticipating issues before they cause outages and optimising resources in real time. Fit: strong for a support or infrastructure engineer with three or more years who wants a customer facing path. Weak at exactly two years, despite the headline figure.
⭐ The title and the requirement disagree, and the requirement wins. This is advertised as an Associate Solutions Engineer, a title that reads entry level in most companies. The required qualification is 4 or more years as a presales, solutions or sales engineer in identity and access management or security, with a proven track record of engaging and gaining trust with developer personas, software engineers and architects. If you are a genuine fresher, this is not the role the title suggests it is. Today's list carries two roles genuinely open at one year and they are Mindtickle's and Orca Security's. ⚠️ Timezone and territory, stated in the posting: you serve Australian commercial customers and businesses across the APJ timezone, mostly Australia and New Zealand, while based in Bengaluru. ANZ business hours run ahead of India, so expect early starts. This is the kind of commitment that is easier to accept knowingly than to discover later. The real day to day: partnering with sales teams as the identity authority, aligning Auth0 solutions to developer pain points through tailored product demonstrations; architecting and running hands on proofs of concept for complex use cases and owning the technical validation alongside engineering teams; and confidently answering in depth technical, application security and identity infrastructure questions from developers, architects and CTOs. Product context: Auth0 is Okta's developer focused identity product, so credibility with a developer audience is the core of the job. Location: Bengaluru. Fit: strong for a presales or solutions engineer with four or more years in identity or security.
Experience: 5 or more years of experience in customer facing roles with a blend of technical expertise and account management, along with demonstrated experience with product features. Note that Zscaler has a more senior version of this same role on its board asking 8 or more years, so check which one you are applying to. Also named: a foundational understanding of AI and machine learning technologies, and experience leveraging, securing or positioning AI driven solutions to optimise outcomes within your domain. Why a Manager title appears on a board built for individual contributors: this role manages customer accounts and technical outcomes, not people. Readers of this list asked for Technical Account Manager and Customer Success roles by name, and this is one of them. ⚠️ Region and working pattern, both stated in the posting: this is a hybrid role based in Bangalore, reporting to the Manager, Technical Success Management in the Customer Success department, and it serves AMS, the Americas. Supporting American customers from India usually carries a timezone commitment, so raise working hours on the first call. Product context: the Zero Trust Exchange securely connects users, devices and applications in any location, protecting against cyberattacks and data loss. Culture note from the ad: Zscaler says it seeks people who actively use AI to amplify their impact, and describes a culture of transparency and constructive debate with impact valued over activity. Fit: strong for a customer facing technical professional with five or more years in security or networking.
Experience: a minimum of 6 years working as a Support Engineer or Senior Support Engineer supporting cloud networking or web security products, with a further requirement of 5 or more years in a related area. The domain specificity matters here: general software support experience is not what this asks for. ⚠️ Location, stated in the posting: this is a hybrid role based in either Bangalore or Mohali, reporting to a Manager in the Customer Success department. Mohali openings are comparatively rare in this market, so this is worth noting if you are in the Chandigarh region and have been filtering only Bangalore, Hyderabad and Pune listings. Named in the requirements: demonstrated curiosity and active exploration of AI tools, with a proven history of integrating new technologies into daily workflows to improve problem solving. Zscaler states this as an expectation rather than a bonus, consistent across its postings. The real day to day: playing an integral part in solving critical technical challenges customers face on Zscaler's cloud platform, as the escalated technical tier rather than first line support. Product context: the Zero Trust Exchange, which securely connects users, devices and applications, backed by what Zscaler calls the world's largest security data lake. Fit: strong for a support engineer with six or more years whose background is specifically cloud networking, web proxy or web security. Weak if your support experience is in general enterprise software, because the domain requirement is stated twice.
⚠️ Working hours, stated at the very top of the posting and quoted here because it changes whether this job suits you at all: "NOTE: This role is working with North America customers (Eastern/Central Time)." From India that means a night shift. Eastern time runs roughly nine and a half to ten and a half hours behind IST, so plan accordingly rather than discovering it at offer stage. Experience: 5 to 8 years of experience supporting large enterprise customers. Technical requirements named: strong TCP/IP knowledge, and excellent knowledge and prior experience supporting network security products. This is a networking heavy support role, so the depth expected is genuine. The real day to day: being the primary point of contact for customer support and escalation cases; regularly communicating status updates to customers; troubleshooting issues and finding workarounds inventively; and working collaboratively with peers. The posting notes you deal with top class IT administrators at Fortune 500 companies, so the audience is technically demanding. Employer context: Netskope's platform secures cloud, data and AI traffic in real time, with its Zero Trust Engine and NewEdge network, and more than 30 of the Fortune 100 as customers. Location: listed as India. Fit: strong for a support or network engineer with five to eight years who has supported enterprise network security products and is genuinely willing to work North American hours. If night shifts are not workable for you, skip this one rather than absorbing the cost later.
Read this before you apply
- One employer published the gap between its stated minimum and its real bar, in writing. Everpure's Member of Technical Staff, Kernel role in Bangalore sets out its requirement as "Minimum 5 years of development experience, but expect that typically candidates would have 15+ years experience." We have published the stated minimum of 5, because that is what it says, but read that sentence before you spend an evening on the application. Most postings leave you to discover that gap on the first call.
- Two more ads where the title and the requirement disagree, in the same direction. Okta's Associate Solutions Engineer asks for 4 or more years in presales or solutions engineering, despite a title that reads entry level everywhere else. LogicMonitor's Customer Success Engineer opens with 2 or more years, then lists three separate requirements at 3 or more years each, so three is the honest floor. In both cases the headline number is the friendlier one and the real one is further down.
- A remote tag that is not a remote job. Workato's postings carry a line quoting a Quartz award naming it the number one best company for remote workers. That is a company accolade sitting in the boilerplate, not an offer of remote work: both Workato roles here are listed in Hyderabad and Chennai. We checked seven roles that mentioned remote today and only six are genuinely remote. Elastic and Commvault mean supporting customers remotely, Netskope's mention is a VPN technology, and Fivetran states two days a week in the office.
- GitLab's Staff Backend Engineer posting calls itself Senior in the body. The title is Staff Backend Engineer, Database Change Management, and the first line of the description reads "As a Senior Backend Engineer, Database Upgrades". Those are different rungs on different pay bands, so it is worth asking the recruiter which one is actually open before you interview.
- Six roles are genuinely remote, and five of them are backend. All four GitLab roles are all remote because the company is built that way rather than as a concession, and three of those four are backend engineering on Ruby on Rails and PostgreSQL. Orca Security's Customer Success Engineer states India, Bangalore, Remote in the posting itself. Remote backend work has been the most requested thing on this list, so it is worth saying plainly that today has real depth in it.
- Office days, shifts, travel and on call, all stated in the postings. Everpure says outright that its Portworx role is primarily in office and expects you in Bangalore. MongoDB's AI Builder role includes a 24/7 on call rotation and is hybrid in Gurugram. Netskope's Senior Cloud Support Engineer works with North American customers on Eastern or Central time, which is a night shift from India. Okta's Associate Solutions Engineer covers Australian customers in the APJ timezone. Coursera's Applied AI role expects regular travel to customer sites. Abnormal AI, Zscaler, LogicMonitor and ConnectWise all state hybrid or office based working.
- Entry level is genuinely thin again, and we are not going to dress it up. Exactly 2 roles on this list are open to someone with a year behind them: Mindtickle's Security and Automation Engineer in Pune and Orca Security's Customer Success Engineer, which is remote. We swept all 105 boards to find them. That matches what we measured on 12 August: only about 6 to 10 genuine entry level tech roles exist across these boards at any moment, and they do not refresh daily. The board as a whole carries 16 open roles at one year or less, which is more than a single day's edition can show, and you can see every one of them here: https://www.munotes.in/dailytechjobs?exp=0
- Where several roles come from one employer, they are separate teams. GitLab has four (three backend seats on different teams plus an RPA role), Everpure three (FlashBlade, Kernel and Portworx, three different products), Okta three (DevOps, core infrastructure and presales), and ConnectWise, Databricks, Netskope, Sigmoid, Workato, ZoomInfo and Zscaler two each. Twenty two employers in all.
We read every posting by hand before it goes on this page. The same write-up goes out to the daily email.