No roles match that combination.
Added August 4, 2026
Requirements. 3+ years of proven experience as a software developer or frontend developer, with a strong understanding of React, TypeScript and the general frontend ecosystem. Solid experience with HTML, CSS and object oriented JavaScript. Strong experience with GraphQL. Experience debugging problems across systems and repositories and designing solutions that span the whole stack. Experience with modern testing frameworks. Responsibilities. Design, develop and implement high quality applications. Work with cross functional teams to define, design and ship new features. Take part in code reviews. Troubleshoot and debug issues. Own and operate high scale cloud based systems and services. ⭐ Remote, and the restriction matters. The posting states: "This role will be remote, and based in India ". So it is genuinely remote, but only if you live in one of those five states. Twilio has used the same five state limit before. The IAM team itself is described as based in Bangalore, and the posting adds that as a remote first company you may be asked to attend in person on an ad hoc basis for team gatherings, off sites or customer meetings, plus occasional travel for project or team meetings. One process detail the posting discloses. Twilio says it uses AI to help make its hiring process efficient, while stating every hiring decision is made by a person. It also warns that it never makes job offers without a formal interview process and never interviews solely over text messaging apps, which is a scam warning worth reading. Who this is for. A frontend engineer with three or more years who wants remote work and does not want to leave a tier two city to get it. If you are outside the five named states, this one will not work and it is better to know before you apply. Identity is a good domain to grow in: the problems stay interesting because the threat model keeps moving, and IAM experience transfers everywhere.
Requirements. 4+ years of professional experience. Strong C and C++ with a systems background. Experience or strong interest in distributed systems, operating system internals, kernel integration and large scale data management. What you would do. Design and deliver high reliability storage features: own end to end development of new algorithms and software for a highly reliable (six nines) and high performance system, meeting demanding business SLAs. Innovate and solve complex systems challenges by analysing, troubleshooting and solving problems across distributed systems, OS internals, kernel integration and large scale data management. Contribute to platform expansion and cloud integration, developing features that extend FlashArray into the public cloud (for example CloudSnap and Cloud Block Store for AWS). Work cross functionally so features keep the platform's core simplicity and zero downtime upgrade promise. Office reality. Bangalore, in office. Everpure states across its postings that it is "primarily an in-office environment" and expects you at the Bangalore office except for PTO, work travel or approved leave. It is one of the few employers on this board that states its policy plainly. ⚠️ Everpure re-posts roles under fresh requisition ids. Two other Everpure postings this week turned out to be near identical re-posts of roles already on this board (similarity 0.99 against rows published on 1 and 3 August), and were left out for that reason. This one was checked the same way and is genuinely different work. Who this is for. A systems engineer with four or more years in C or C++ who wants storage internals. You do not need prior storage domain experience: the requirement is systems depth, and storage is learnable on the job. Note that Everpure uses the title "Member of Technical Staff" at every level from 4 years to 18, so the title tells you nothing about seniority here. Read the years.
Requirements. At least 4 to 7 years of in depth, hands-on professional experience in the DevOps or infrastructure engineering domain. What you would do. Create systems that serve as the brains of complex distributed products. Work on code modularity, scalability and reusability. Mentor younger engineers on the team. Contribute to team building within the engineering organisation. Scale context, from the posting. Meesho says 5 percent of Indian households shop with it, which makes resilient systems necessary to manage millions of orders every day, and states it has done this with zero downtime. Culture detail worth knowing. Meesho describes valuing speed over perfection and seeing failures as opportunities, and says it has worked to instil a "Founder's Mindset" across engineering teams. It also names regular one to ones and open communication as part of how the team runs. Take that as a signal about pace: this is a fast environment rather than a carefully staged one. Location and terms. Bangalore, marked on-site by Meesho, Full Time Employee, on the Infrastructure team inside Tech. Who this is for. A DevOps or infrastructure engineer with four or more years who wants to build platform systems rather than run tickets. The mentoring is stated as part of the role, so this suits someone ready to be a reference point for less experienced engineers, but there is no people management in it. If your experience is mostly managed services and dashboards rather than writing code, the emphasis on modularity and reusability will show in interview.
Requirements. 5+ years of cloud infrastructure administrator experience is required. Significant prior experience with at least one of the big three cloud providers (AWS, GCP or Azure) is required. Experience with Ansible, Terraform and Kubernetes is desirable. The posting also asks for proficiency with Microsoft Office applications, which is unusual to see stated on an infrastructure role. What you would do. Participate in the on call rotation as a member of the Cloud Managed Services team and respond to incidents that affect Neo4j cloud infrastructure availability, providing support for customer cases. Troubleshoot server and database technical issues. Reliably manage and monitor the customer's Neo4j database environment, taking a holistic view of environment health to maximise application and infrastructure uptime. Help ensure customers successfully deploy and manage Neo4j in their production environments. ⭐ Remote, and verified. The board lists this as Remote: India and nothing in the posting body imposes an office or hybrid requirement, which is why it is published as remote. Today's other two remote roles are Twilio's (restricted to five states) and Databricks' (with 20 percent customer travel); this one carries neither restriction in writing. ⚠️ On call is explicit. The first responsibility listed is the on call rotation. That is the job, not a footnote, so weigh it honestly if you have done pager duty before and know how you find it. Company context. Neo4j says it recently passed 200 million dollars in annual recurring revenue, doubling over three years. Who this is for. A cloud infrastructure engineer with five or more years who is comfortable talking to customers as well as fixing systems. The posting says plainly it suits someone with strong technical skills who enjoys solving problems as much as collaborating directly with customers, so if customer contact drains you, this is the wrong shape even though the technical work fits.
Requirements. 5+ years of experience as a software engineer, ideally with experience building SDKs, libraries or developer tooling. Responsibilities. Maintain and enhance existing FGA SDKs in Go, JavaScript, .NET, Python and Java using the SDK generator framework. Customise and refine SDK templates and wrappers so behaviour is consistent across languages, supporting configuration overrides such as store ID, authorisation model ID, headers and parallelisation limits. Implement and improve core SDK features including client credentials authentication flows, robust error mapping, retry logic with jitter, and rate limiting safeguards. Implement advanced capabilities such as BatchCheck, ListRelations and non transactional write operations. What makes this one different. The team's guiding principle is stated as "One developer experience, many deployment models", covering both the open source and SaaS versions of FGA. All development happens in the open as open source and community contributions are welcomed and reviewed. That means your commits and code reviews are publicly visible, which is a genuine plus if you want a portfolio and a genuine consideration if you would rather work privately. Location. Bengaluru. Okta operates a flexible model where the role allows, so confirm office days in the first call. ⚠️ Board metadata to ignore on Okta postings generally. Several Okta requisitions publish "Minimum Work Experience: 0.0" in their Greenhouse metadata, which as structured data reads like no experience is needed. It is an unfilled placeholder. Years here come from the requirement list in the body. Who this is for. An engineer with five or more years who genuinely enjoys building for other developers, and who is comfortable being polyglot: this is five SDK languages, so breadth matters more than depth in any one. Authorisation is a good domain to learn properly and hard to pick up casually.
Requirements. 5+ years of software engineering experience. The team and mission. Core Identity owns the authentication pipeline, identity protocols, user sessions and the fundamental elements underpinning the Auth0 product, and is also steward of the platform's technical health, performance and efficiency. Core Frontier is a new team within it. As a Senior Engineer on that team you operate at the intersection of deep product innovation and the global customer experience, ensuring features developed across Core Identity (the posting names Native to Web, Cross App Access and Custom Token Exchange) are hardened, scaled and seamlessly integrated into the Auth0 ecosystem. You act as the architectural bridge so complex internal logic becomes a polished, secure and high performance experience for developers. Being on a brand new team. The posting says plainly that this is a new team. That usually means more influence over how things are done and less established process to lean on, which suits some people and not others. Worth asking in the first call how many engineers the team will have and who else has joined. Location. Bengaluru, with Okta's flexible model where the role allows. ⚠️ Ignore the Okta board metadata that reports "Minimum Work Experience: 0.0" on several of its requisitions. It is an unfilled placeholder, not an experience figure. Who this is for. An engineer with five or more years who wants identity protocols and platform hardening rather than feature delivery. Auth0 is a developer facing product, so the definition of done includes other engineers' experience of your work. If you have OAuth, OIDC or SAML depth, this is squarely aimed at you, and that depth is portable to any security team afterwards.
Requirements. 5 to 7 years, stated in the job title itself. Proven experience in firmware development for embedded systems, preferably in consumer electronics or IoT devices. Experience with hardware and software integration, working closely with hardware teams to define firmware requirements. Experience with device drivers, low level hardware interfaces and firmware debugging techniques. Experience with SoC bring up and micro controllers. Responsibilities. Work with cross functional teams including hardware engineers, software developers and product managers to define firmware requirements and specifications for the smart speaker and associated devices. Design, develop and test firmware solutions for the smart speaker, ensuring performance, reliability and compatibility. Implement firmware features to support the smart speaker and other devices in the PhonePe ecosystem. The products, so you know what you would be working on. The PhonePe smart speaker is the device that announces payment confirmations aloud in shops, alongside DQR devices and printers. This is hardware that runs in ordinary retail environments, so reliability and cost constraints are real rather than theoretical. Location and terms. Bangalore, at the Salarpuria Softzone office. The requisition type is FTE Regular. Who this is for. An embedded or firmware engineer with five to seven years. This is a rare posting on a board that is otherwise dominated by cloud, backend and data roles, so if firmware is your field it is worth a look precisely because the competition from this list's usual readership will be thin. Consumer electronics or IoT background is preferred rather than required, so adjacent embedded experience should still get a hearing.
Requirements. 5+ years of relevant experience. Hands-on work across dbt, MetricFlow, Snowflake and Databricks. Experience building governed semantic layers and standardised metric definitions. What you would do. Design, build and maintain governed metric models: standardised, reusable definitions of business KPIs that dashboards, reports and AI agents all query from a single source of truth. Own the automation and maintenance of corporate scorecards and executive reporting, ensuring trusted, timely data with AI powered anomaly detection and alerting. Conduct deep dives on key KPIs and company goals, surfacing actionable insights and translating business priorities into data driven work. Lead enablement sessions on the analytics platforms. How the posting describes itself. "This is not a traditional reporting or data science role." The three strategic pillars are automating and governing corporate executive reporting, standardising metrics and reporting practices at scale, and enabling self serve and AI powered data solutions. The connecting thread is making Smartsheet's data trusted, consistent, accessible and ready for both human and AI consumption. ⛔ Ignore the remote tag. Like every Smartsheet India posting, this one carries an #LI-Remote tag while its own title says "Hybrid, Bangalore". Smartsheet's postings have contradicted themselves this way on every requisition we have checked, across two consecutive editions. The title and body agree with each other; the tag does not. Treat this as a Bangalore hybrid role. Who this is for. An analytics or BI engineer with five or more years who wants governance and semantic modelling rather than dashboard production. The AI angle is real work here (building agents over governed data), not a buzzword in the intro, which makes it a genuinely current skill to pick up.
Requirements. 7+ years of software engineering experience, with genuine full stack breadth across user interfaces, APIs and backend services. What you would do. Independently own end to end features and platform capabilities spanning intuitive user interfaces, REST and GraphQL APIs, high throughput asynchronous job engines and microservice backends. Drive technical strategy and make critical architectural decisions across the entire stack. Influence both your immediate team and cross functional initiatives. Solve challenges ranging from rich, responsive admin workflows to massive scale batch processing, real time synchronisation and identity resolution algorithms. Mentor engineers across the full stack. Partner with product management and UX on feature strategy. Balance short term delivery against long term platform health. Location. The posting states this is a hybrid position, based in Bengaluru. ⚠️ Okta board metadata to ignore. Several Okta requisitions publish "Minimum Work Experience: 0.0", which reads as structured data saying no experience is required. It is an unfilled placeholder. The 7 year figure is from the requirement list in the body. Who this is for. A staff level engineer with seven or more years who is genuinely full stack and wants architectural ownership of a platform rather than a feature area. Identity resolution and large scale batch processing are the distinctive technical problems here, and both are transferable: identity resolution in particular is the same problem shape as customer data platforms and deduplication work elsewhere. The mentoring and strategy responsibilities make this a senior IC seat rather than a management step, and nothing in the posting describes managing people.
Requirements. 8+ years of experience in an object oriented language, preferably Java. Experience developing and tuning highly scalable distributed systems. Experience with reliability engineering, specifically in data quality, data observability and incident management. Hands-on experience developing data integration applications for large scale (petabyte scale) environments, across both batch and online systems. What you would do. Work with engineers throughout the organisation to build foundational infrastructure that lets Okta scale for years. Design, build and deploy the systems that power the company's data analytics and machine learning. Design and own the building, deployment and optimisation of the streaming infrastructure. The stack, as listed. Kinesis, Flink, Elasticsearch and Snowflake sit at the centre of the analytics infrastructure. Why the team exists, stated in the posting. The project has a directive from engineering leadership to make Okta a leader in the use of data and machine learning to improve end user security, and to expand that competency across the rest of engineering. The posting says you would have a sizable impact on the direction, design and implementation of the solutions. Location. Bengaluru, under Okta's flexible model where the role allows. ⚠️ Okta publishes "Minimum Work Experience: 0.0" in the board metadata on several requisitions including this one. It is an unfilled placeholder, not a real figure. The 8 years is from the body. Who this is for. A data or backend engineer with eight or more years and real streaming experience, not just batch. The reliability engineering requirement (data quality, observability, incident management) is specific and worth taking seriously: this is a platform other teams depend on, so being on the hook for it is part of the job. Java is preferred rather than optional here.
Requirements. 8+ years of systems engineering experience focused on designing and optimising infrastructure for high performance, low latency applications. Hands-on experience with Software Defined Networking (SDN), cloud platforms such as AWS or Azure, and containerisation tools such as Docker or Kubernetes. Responsibilities. Participate in the design, development and optimisation of firewall and SWG platforms in cloud infrastructure. Execute the technical roadmap for firewalls and SWG in cloud infrastructure, keeping it aligned with business goals. Work closely with engineering teams to enhance platform support for virtualised environments. Drive professional development and growth initiatives for team members. ⚠️ One responsibility worth flagging honestly. The list includes "Drive professional development and growth initiatives for team members". There is no reporting line, hiring, or performance review language anywhere in the posting, so we have read this as senior mentorship rather than people management and published it as an individual contributor role. If becoming responsible for other people's development is not what you want, ask about it directly in the first call, because that sentence is doing some work. Location and terms. Bangalore, hybrid. Employment type is listed as Fulltime Employee, in the Engineering division. A note on Zscaler titles. Zscaler runs many concurrent requisitions with near identical titles across different teams, and has had five separate roles called "Staff Software Development Engineer" open at once. The team and stack distinguish them, not the title. This one is the firewall and SWG platform seat. Who this is for. A systems or networking engineer with eight or more years who wants core product work at a security company. If your background is application development rather than networking, the SDN and firewall requirements are a real barrier here.
Requirements. 8+ years of experience working on systems or distributed systems with a focus on networking, firewall technologies and cloud infrastructure. Experience with virtual environments including Docker, containers, Kubernetes and OVA. Responsibilities. Build robust frameworks and tools specifically designed to test complex products. Design and develop wide reaching tools that impact the entire engineering lifecycle. Write high quality code to automatically verify product quality and ensure seamless performance. How the posting frames the role, which is worth quoting because it is unusually direct. You will be "writing the frameworks and tools used to test our products, occupying a unique space that combines the 'building' mindset of software design with the 'breaking' mindset of software test engineering", and you will be "often writing more code than the developers themselves". That is a clear statement that this is an engineering job, not a QA job, and it is the reason it sits in the main list rather than being treated as a testing role. Location and terms. Bangalore, hybrid, Fulltime Employee. Who this is for. A senior engineer with eight or more years who enjoys tooling and has the networking and systems depth to test this particular product meaningfully. You cannot write good tests for a firewall datapath without understanding the datapath, which is why the requirement list is systems heavy rather than test heavy. If you are an SDET who has been wanting a role where the framework is the deliverable and the scope is the whole engineering org, this is the clearest example of that shape on the board today. Zscaler runs several similar sounding titles: this is the tooling one.
Requirements. 8+ years of industry experience. Deep AWS infrastructure experience across EKS, Lambda, ECS, VPC and IAM. Terraform and infrastructure as code practice including reusable modules, remote state management and environment based blueprints. CI/CD pipeline ownership, with GitLab named. Observability tooling, with Prometheus and Grafana named. Responsibilities. Design, build and maintain scalable, secure and highly available AWS infrastructure for AI and ML workloads using Terraform, following IaC best practice including reusable modules, remote state management and environment based blueprints. Own and continuously evolve GitLab CI/CD pipelines for AI platform services, automating build, test, security scanning and multi environment deployment so releases are fast, reliable and repeatable. Architect a centralised observability stack using Prometheus and Grafana. Drive infrastructure automation, observability and platform governance so AI and data engineering teams can deliver reliably and securely. Where it sits. The posting places this in the IT Data Strategy team. That is internal platform engineering serving the company's own AI and data teams, rather than customer facing product work. It is genuine infrastructure engineering rather than end user IT support, which is why it is in scope here. Location. Bangalore or Pune, both listed, which is worth noting since almost every role in this edition is Bangalore only. Zscaler operates a hybrid model. Who this is for. A platform or DevOps engineer with eight or more years who wants to specialise toward AI infrastructure. The AWS and Terraform requirements are the hard ones; the AI part is about supporting ML workloads rather than building models, so you do not need a machine learning background to be credible here. Pune as an option makes this accessible if Bangalore does not suit you.
Requirements. 8 to 12 years of backend engineering experience. Experience with NoSQL databases such as Cassandra, MongoDB or Aerospike. What you would do. Design and build scalable distributed systems and microservices. Lead development of complex features and technical initiatives end to end. Drive system design, API design and engineering best practice. Own scalability, performance, reliability and fault tolerance of services. Optimise high throughput, low latency systems. Contribute to cross team collaboration and system alignment. Stay hands-on with coding and system design 50 to 60 percent of the time. Mentor engineers and support team capability growth. Participate in technical decision making and architectural improvements. Handle production issues, root cause analysis and continuous improvement. ⭐ The 50 to 60 percent number is worth the price of admission. Very few staff level postings tell you how much of the job is still coding. Agoda does, in writing, which means you can hold them to it and you know what you are signing up for. The team and stack. High scale, fault tolerant distributed systems for a platform serving millions of users daily, owning inventory, pricing, booking, payments and customer and partner platforms. Systems run with high availability, low latency and zero downtime expectations using Scala, Go, Java and Kotlin with Kafka and Aerospike. The team ships dozens of releases a day. ⛔ Visa. Agoda records "Visa sponsored: False" on this requisition and the title says Gurugram based, so this is for candidates already able to work in India. Department is listed as IT Engineering. Who this is for. A backend engineer with eight or more years who wants scale and wants to keep writing code. JVM and Scala experience transfers most directly. Agoda also runs a Level 5 version at 11+ years in the same office, also in this edition, which adds architecture and cross team leadership.
Requirements. A Bachelor's degree and 8+ years of experience, or 10+ years of experience without the degree, which is a stated alternative route rather than an implied one. Extensive knowledge and practical experience across several of applied AI, machine learning, statistics, propensity modelling, churn prediction and recommender systems. What you would do. Partner with sales and customer success teams, understand their goals and find opportunities to draw relevant insights and drive tangible impact. Develop and implement machine learning based cross sell and upsell models, and product recommender models, to drive sales and monetisation. Build and deploy predictive models for customer churn and identify proactive churn risk signals to drive retention. Drive the full analytics lifecycle from understanding the business objective through analysing the data to developing automated reporting. Where it sits. You work primarily with go to market teams and are part of Smartsheet's Data Science and Business Intelligence team. This is a data science role serving commercial functions, so expect your stakeholders to be sales and customer success leaders rather than engineers. ⛔ Ignore the remote tag. Every Smartsheet India posting carries an #LI-Remote tag while the bodies and titles describe Bangalore hybrid or Bangalore office work. Two consecutive editions have found the same contradiction on every Smartsheet requisition checked. This is a Bangalore role. ⚠️ A years figure automated tools misread on Smartsheet postings. Every one opens "For over 20 years, Smartsheet has empowered teams", so a parser looking for a number followed by "years" finds 20 before it finds anything about the candidate. The real figure here is 8, from the requirement list. Who this is for. A data scientist with eight or more years who is comfortable being commercially useful. Propensity, churn and recommender experience is the core ask. If you want research or deep learning work, this is not that role.
Requirements. 8 to 12 years of strong software design and development experience building massively large scale distributed internet systems and products. Hands-on experience in advanced Java, Spring Boot, AWS, Node, agentic AI, LLM, RAG, Cursor and Copilot. Experience and knowledge of open source tools and frameworks and broader cutting edge server side technologies. Superior organisation, communication, interpersonal and leadership skills. Must be a self starter who works well with minimal guidance in a fluid environment. ⚠️ An unusual stated requirement. The posting says you "should be an active contributor to developer communities like Stack Overflow, Top coder, Git hub, Google Developer Groups". That is a real filter if you have kept your work private, and worth knowing before you apply: have your public profile ready, or be prepared to explain the absence. The role. As a Principal Engineer you help define the technical design and implementation roadmap across multiple solutions, and work with engineering leadership to ensure squads are resourced and equipped with the right expertise to deliver them. Nothing in the responsibilities describes managing people directly. Location and terms. Bengaluru, marked on-site by Paytm, on the Travel team inside Technology. Company scale, from the posting. Paytm cites 500 million plus registered users and 21 million plus merchants. Who this is for. A principal or staff level backend engineer with eight or more years who wants architecture scope across several product lines. The AI tooling requirements are stated as hands-on, so this is a good fit if you have already brought LLM and RAG work into production rather than read about it. Paytm is on-site in Bengaluru for this one, unlike most of its roles which are Noida based.
Requirements. 8+ years of professional experience, with depth in Azure cloud and infrastructure engineering, DevOps and platform work. Responsibilities. Explore the client's needs and drive the building of a technical roadmap and solution that supports their business goals. Help shape and build Thoughtworks' cloud and infrastructure practice through collaboration with business development, marketing and capability development teams. Ensure and build the controls and processes for continuous delivery and evolution of infrastructure and applications, driving automation through all stages. Take a leading role in monitoring and ensuring technical expectations of deliverables are consistently met on projects. Provide expertise and guidance in DevOps, cloud, platform and infrastructure. ⛔ Office policy, and it is the strictest on this board. Thoughtworks states across its India postings that you may be expected to work from a Thoughtworks office or at a client's office location for all five working days of the week, depending on business or client needs. Its Greenhouse metadata records "Remote Eligible: False". ⚠️ The posting also carries an #LI-Remote tag, which contradicts both. The body and the structured metadata agree with each other, so we publish this as Bengaluru, on-site. ⚠️ A years figure automated tools misread here. Thoughtworks postings open with "For 30+ years, our clients have trusted our autonomous teams", so a parser looking for a number followed by "years" finds 30 before it finds the real requirement. The figure above is from the requirement list. Who this is for. An infrastructure engineer with eight or more years and real Azure depth who wants consulting: different clients, different constraints, and a firm that will back strong engineering practice. The practice building responsibilities mean you would also help sell and shape the offering, which suits someone who wants influence beyond delivery. Do not apply if you need remote or hybrid.
Requirements. 8+ years of Android development experience, with at least 2 shipped production apps. Hands-on experience with the modern Jetpack stack: Hilt, Room, DataStore, WorkManager, Navigation and Paging. Experience with performance tooling: Macrobenchmark, Baseline Profiles, App Startup and R8 optimisation. Experience with modularisation at scale, Gradle build optimisation (KSP, configuration cache, build cache) and CI/CD pipelines. What you would do. Join the Android Platform team and focus primarily on building a roadmap for the Android platform. Lead and contribute to engineering efforts from planning and organisation through execution and delivery. Work closely with QA, other engineers, product managers and designers across the company to shape the future of the Android platform. Actively participate in external community activity. The constraint that defines the work. Meesho's Android team describes building an experience that works on everything from five thousand rupee entry level phones in small towns to flagship devices in metros, tracking stability metrics it says few others bother with, and handling millions of orders without downtime. Performance on cheap hardware is the actual engineering problem. Location and terms. Bangalore, marked on-site, Full Time Employee, on the Android Platform team. Who this is for. A senior Android engineer with eight or more years who wants platform and architecture ownership. The two shipped production apps requirement is concrete, and the performance tooling list is specific enough that it will be obvious in interview whether you have used it. Meesho also runs an SDE IV Android seat at 6+ years if this bar is a stretch, and a DevOps seat at 4 to 7 in this same edition.
Requirements. 11+ years of experience building and operating large scale backend systems in production environments. Recent and ongoing hands-on coding experience in production environments is required, stated explicitly. Experience with cloud native architectures on AWS or GCP. What you would do. Lead the architecture, design and development of complex distributed systems at scale. Own the technical direction, delivery and evolution of critical systems and platforms. Drive system design, API standards, software architecture and engineering best practice across teams. Lead complex technical initiatives involving multiple services, teams and stakeholders. Make key technical decisions, balancing business priorities against scalability, reliability and maintainability. Remain an active hands-on contributor. Influence engineering decisions beyond your immediate team, mentor engineers, shape development practices and help raise the organisation's technical bar. Is this a management role? No reporting line, hiring or performance review responsibility appears anywhere in the posting, and the hands-on coding requirement is stated as a requirement rather than a preference. We have published it as a senior individual contributor seat on that basis. The word "Lead" in the title is a level marker at Agoda (Level 5), not a people management signal. ⛔ Visa. Agoda records "Visa sponsored: False" and the title says Gurugram based. The team and stack. Mission critical domains across inventory, pricing, booking, payments and the customer and partner platforms, on Scala, Go, Java and Kotlin with Kafka and Aerospike, shipping dozens of releases a day. Who this is for. A backend engineer with eleven or more years who wants architectural ownership without leaving the code. If you want the same work one level down, Agoda's Level 4 Staff seat is in this same edition at 8 to 12 years.
Requirements. 14+ years of developer level Linux platform experience. Strong programming skills in C, C++, Python, Java, Go or other languages with a solid grounding in object oriented programming. Hands-on development experience in the storage domain and related technologies is preferred rather than required. What you would do. Design, collaborate on and implement creative new algorithms and technologies for high performance, highly reliable systems, which the posting describes as six nines. Own and deliver innovation end to end, from concept to shipped product. Analyse and solve challenging problems in the FlashBlade product area. The team, in its own words. FlashBlade is a scale out all flash file and object store designed for modern workloads. The team says it wants people who want to understand how modern applications like AI or Splunk work with data and how to make that better, who enjoy distributed systems, algorithms, operating systems, the Linux kernel, database internals, hypervisors, containers, compilers and hardware "or at least some of those", and who will dive into a complex problem and drive it to resolution. Office reality. Bangalore, in office. Everpure states plainly that it is primarily an in-office environment and expects attendance except for PTO, work travel or approved leave. Who this is for. A systems engineer with fourteen or more years and genuine Linux platform depth. Storage domain experience is preferred but not required, so strong systems people from databases, kernels or distributed infrastructure are in scope. Note Everpure uses "Member of Technical Staff" at every level from 4 years to 18 across its board, so the title carries no seniority information at all and you have to read the years, which is exactly why we publish them.
Requirements. 10+ years of hands-on technical experience across different areas of security, including infrastructure security, product security, system design and DevSecOps. What you would do. Lead AI security architecture: drive the technical roadmap and high level design to continuously prevent and detect security failures. Optimise the AI driven software development lifecycle by designing secure by default guardrails for both human developers and AI coding agents, with the mission of ensuring near zero vulnerabilities from application and data security failures reach production. Conduct advanced red teaming, using LLMs to improve the security posture. Architect defences for autonomous AI systems against prompt injection, data leakage and jailbreaking attacks. Mentor security engineers and provide architectural guidance across the organisation, partnering with ML, DevOps and platform teams to evangelise secure coding practice. ⭐ The posting states this is an individual contributor role, and it goes further: the mentoring happens "without direct reporting lines". That is unusually explicit and it is why an architect title at 10 years sits comfortably in an IC-only list. Location and terms. Bangalore, marked on-site, Full Time Employee, on the Infrastructure team. Who this is for. A security engineer or architect with ten or more years who wants the AI security frontier rather than another AppSec programme. The base requirements are conventional (infrastructure security, product security, DevSecOps), so you do not need existing AI security experience to apply, but you do need to want it: prompt injection defence and LLM red teaming are the distinctive half of the job. Meesho also runs a Security Engineer IV seat at 7+ years if this bar is a stretch.
⚠️ This posting states no years of experience anywhere. Rather than guess a number we have left the experience figure empty, which is the standing rule on this board. The consequence is that this row sits in no experience band on the page filter, so if you filter by years you will not see it. Read the requirements below and judge the level yourself: the scope (owning shared systems used by the whole engineering org) reads senior, and the title says Senior. The role. Join the Platform Ops team within Platform Engineering to enable developer productivity by building and improving developer tooling and environments, and by improving productivity tools around observability. The team builds the shared systems and workflows engineers rely on every day, internal developer environments and self serve tooling, so that the recommended way to ship changes is the easiest way. This is described as a platform tooling role focused on reusable capabilities and self service workflows adopted across teams. The AI part. You would help develop AI based workflows for productivity and efficiency, including automation that improves infrastructure operations, with faster triage, automated runbook steps and better self service for common issues given as examples. How work gets prioritised, which tells you something about the team. You prioritise the highest impact problems by looking at where time is being lost today: slow builds, flaky tests, manual release steps. ⚠️ Check the priority flag before you apply to any Fivetran role. Fivetran publishes an internal "Priority Status" field on some requisitions. Values seen include "P3 (Future Open)" and "P2 (Internal Resources)", and roles carrying them are not open to external applicants even though the apply page loads normally. This posting carries no such flag, which is why it is here; two other Fivetran roles were left out today for exactly that reason. Office. Fivetran's Bangalore roles run a hybrid model of two days in the office each week. Merger note. Fivetran and dbt Labs are combining, and the postings warn you will see both names during recruiting.
⚠️ This posting states no years of experience anywhere, so the experience figure is left empty rather than guessed, per the standing rule here. That means this row appears in no experience band on the page filter. Judge the level from the scope: the title says Staff and the work is architecting a new platform, so treat it as a senior seat. The role. Fivetran is building the next foundational layer of the analytics stack: an Enterprise Context Platform that captures, stores and exposes organisational decision memory. As a seasoned engineer on Context Platform Systems you would architect and build the durable memory substrate that powers agentic analytics workflows. The platform stores not just metadata but meaning: decisions, intent, rationale and history, made safely accessible to humans, agents and applications. The posting calls it a greenfield, high leverage role with company level impact. What you would do. Prototype technical solutions and find the best fit for the context engine. Architect and build the core Context Platform. Design schemas and primitives for Decision Memory and enterprise context. Own context storage systems across graph, vector and event or time based stores. Build read, write and query APIs used by agents, products and external applications. Design permission aware, auditable access. ⚠️ Fivetran priority flags. Fivetran publishes an internal "Priority Status" on some requisitions, and values like "P3 (Future Open)" and "P2 (Internal Resources)" mean the role is not open to external applicants even though the apply page loads normally and returns a healthy response. This posting carries no flag. Two Fivetran roles were excluded from today's edition because they did. Office and company. Bangalore, hybrid at two office days a week. Fivetran is merging with dbt Labs and warns you will see both brand names during recruiting. Who this is for. A senior engineer who is comfortable with ambiguity and has built storage or retrieval systems before. Graph, vector and temporal storage in one system is an unusual combination and a genuinely interesting design problem.
⚠️ This posting states no years of experience anywhere, so the figure is left empty rather than guessed. That means this row sits in no experience band on the page filter. The title says Senior and the scope is infrastructure ownership, so judge accordingly. Requirements as stated. Experience with infrastructure as code and related tooling such as Pulumi or Terraform. Prior experience developing for or operating Trino is described as a huge plus rather than a requirement, which matters: it means Trino specific knowledge is not a gate. The role. On the fully distributed Starburst Galaxy Reliability, Scalability and Efficiency team you own the reliability, scalability and efficiency (performance per dollar) of Starburst Galaxy IaaS and SaaS as it grows. You help design and build core infrastructure around Trino within the Galaxy product itself, and build the tooling used to operate the SaaS at scale, which the posting describes as "the machine that builds the machine". Daily work includes developing backend infrastructure for product features, building operational tooling, supporting the product in production, and driving collaboration with stakeholders on reliability, scalability and efficiency. On the Core Infrastructure side you own the APIs for provisioning and upgrading cloud infrastructure. Location. The posting lists India without naming a city, and describes the team as fully distributed, though no explicit remote statement appears in the body, so confirm the working arrangement in the first call rather than assuming. Who this is for. A backend or infrastructure engineer who wants data infrastructure at the query engine layer. Because Trino experience is explicitly a plus rather than a requirement, this is a realistic way into distributed query systems for someone with strong general infrastructure skills. The efficiency framing (performance per dollar) suggests cost engineering is a real part of the work.
⚠️ This posting states no years of experience anywhere. Composio's postings are known for this: an earlier one headed its list "Must haves" and then said "if you are very good, nothing is a must per-se". The experience figure is left empty rather than guessed, so this row appears in no experience band on the page filter. Judge it on the requirements, which are written as capabilities rather than years. Must haves, as the posting frames them. Automation and quality engineering: you build automation frameworks, quality platforms and developer tooling that engineers rely on. You write clean, maintainable automation and validation code and know how to apply the right quality strategy across API, integration, contract and end to end layers. You care about quality outcomes, CI/CD quality gates, release confidence and reducing flaky tests, not just test execution. Complex systems and integrations: you can reason about API behaviour, authentication, retries, idempotency, eventual consistency and distributed systems. You have tested, validated and debugged integration heavy systems involving multiple services and external dependencies. You use logs, traces, metrics and production signals to investigate failures and improve reliability. AI native: you actively use AI to accelerate testing, debugging, automation or engineering workflows. Location. Bangalore. Composio's board marks this posting `isRemote: false`, and nothing in the body contradicts that, so treat it as an in office or hybrid Bangalore role and confirm the days. Who this is for. A test engineer who thinks like a platform engineer. The emphasis on idempotency, eventual consistency and integration debugging means this suits someone who has tested distributed systems rather than user interfaces. Because no years figure is stated and the company writes its requirements as capabilities, a strong candidate with less conventional experience has a real chance here, which is rarer than it should be.
⚠️ This posting states no years of experience anywhere, so the figure is left empty rather than guessed, per the standing rule. That means this row sits in no experience band on the page filter. The title says Staff, and Zscaler uses Staff across a wide range on this board, so treat the level as genuinely unclear and ask in the first call. Requirements and stack. Strong Java for backend services and APIs. Experience with scalable, high performance service design. Testing discipline across unit, integration and performance tests. Comfort with Agile and Scrum ceremonies. Responsibilities. Lead the development of identity management products for Zscaler. Design and implement scalable, high performance backend services and APIs using Java. Ensure code quality by writing and maintaining unit, integration and performance tests while monitoring, debugging and optimising system performance. Collaborate with cross functional teams to deliver integrated solutions and contribute to Agile and Scrum processes such as sprint planning and retrospectives. Participate in an on call rotation to support a highly available engineering platform and ensure compliance with federal guidelines. Context. The posting frames the work as helping manage digital risk by applying security through identity integration and controls, building workflows and application integrations coordinated with the larger IAM team, product management and business teams. ⚠️ Two things to weigh. There is an on call rotation, stated plainly. And compliance with federal guidelines is named, which usually means process overhead around changes and access. Location and terms. Bangalore, hybrid, Fulltime Employee. Who this is for. A Java backend engineer who wants identity and access management. Zscaler runs many similarly titled requisitions across different teams, so read the responsibilities rather than the title: this is the identity platform one, distinct from the firewall datapath and test tooling seats also in today's edition.
⚠️ This posting states no clear years requirement, so the figure is left empty rather than guessed and this row appears in no experience band on the page filter. Note that a parser scanning for a number before the word "years" finds Smartsheet's standard opening line, "For over 20 years, Smartsheet has empowered teams", which is the company's age and nothing to do with the candidate. That is exactly the kind of trap that makes reading by hand necessary. Smartsheet's separate Senior MLOps requisition asks 5+, 7+ and 4+ years across three bullets, so this family of roles sits in that region. Requirements. Hands-on experience with at least one major cloud provider (AWS, Azure or GCP). Experience building and maintaining AI and ML Ops platform systems for scalability, reliability, efficiency and security. In depth experience in system design and AI/ML frameworks and tools involving petabytes of data within the Databricks Lakehouse ecosystem. Experience with Monte Carlo is preferable. Experience with AWS Bedrock is preferable. What you would do. Design, develop and oversee the strategy and architecture of scalable and reliable AI/ML Ops platforms and pipelines. Package and deploy AI/ML services to production, ensuring they are reproducible and interpretable. Design and implement automated CI/CD pipelines to accelerate model deployment. Provision and optimise infrastructure for training and serving using Docker, Kubernetes or serverless platforms. Implement post deployment monitoring for model performance, data drift and latency. Automate retraining and data pipeline workflows so models stay accurate. Manage the deployment of foundation models. ⛔ Ignore the remote tag. The title says "Hybrid in Bangalore" and the posting carries an #LI-Remote tag anyway. Every Smartsheet India requisition checked across two editions has the same contradiction. The title is right. Who this is for. An ML platform engineer who wants ownership of architecture rather than model building. Databricks Lakehouse depth is the distinguishing requirement.
Requirements. 5 to 8 years of engineering experience required. Engineering experience in AI and agentic development. Experience developing and deploying software within enterprise environments. Experience with LLMs, agent frameworks, or deploying AI systems in production. Prior experience in an FDE or similar forward deployed engineering role. Willingness and ability to travel up to 30 percent to customer sites for on site engagements, technical reviews and presentations. Responsibilities, in the posting's own three groupings. Customer success: serve as the primary technical owner for customer engagements from initial discovery through production rollout. Understand each customer's architecture, constraints and definition of success and drive toward that outcome. Manage expectations, communicate risks clearly and help customers navigate technical decisions. Technical integration: build the connectors, pipelines and supporting tooling needed to make the platform work inside real enterprise environments. Write production quality code, troubleshoot issues and implement fixes directly in active workstreams. Work effectively within customer environments that have different stacks and integration constraints. Product feedback loop: capture product feedback precisely, including logs, reproduction steps and a proposed path forward, and use engagements to identify product gaps. ⭐ Level is explicit. MongoDB records "Job Level: Professional - IC" in the requisition metadata, so this is unambiguously an individual contributor role despite being customer facing and senior. ⚠️ Two practical points. Travel is up to 30 percent to customer sites. And the posting says MongoDB is "looking to speak to candidates who are based in Gurugram for our hybrid working model", so this is a Gurugram hybrid role, not remote. Who this is for. An engineer with five to eight years who wants customer facing delivery work while still writing production code. If you have done consulting or solutions engineering and want to stay technical, this is that shape. MongoDB runs a Staff version at 9+ years in this same edition.
Requirements. 9+ years of relevant engineering experience, including hands-on work in production systems and complex customer or enterprise environments. Experience with LLMs, agent frameworks, retrieval systems, evaluation frameworks, or deploying AI systems in production enterprise environments. Prior experience in a forward deployed engineering role or a similarly hybrid role spanning customer environments, product influence and hands-on engineering execution. Willingness and ability to travel up to 30 percent to customer sites for on site engagements, technical reviews and executive or customer presentations. Responsibilities. Customer and business impact: own the most complex customer engagements and technical workstreams, especially where the problem, solution or path to production is ambiguous. Build deep understanding of customer architecture, business goals, constraints and definition of success, and use it to shape the technical approach rather than only execute within a predefined one. Act as a trusted technical counterpart to customers' engineering leaders, internal product and engineering leaders, and executive stakeholders when navigating complex tradeoffs, risks and priorities. Technical leadership and execution: lead architectural design for customer facing solutions and platform capabilities within the FDE domain, balancing hands-on implementation with technical decision making across multiple teams. Take ambiguous, high level problems and turn them into clear technical direction, implementation plans and milestones. ⭐ Level is explicit. MongoDB records "Job Level: Professional - IC" in the requisition metadata, so despite the seniority and executive exposure this is an individual contributor role. ⚠️ Practical points. Up to 30 percent travel to customer sites, and MongoDB says it is looking for candidates based in Gurugram for its hybrid working model, so this is not remote. Who this is for. A senior engineer with nine or more years who is comfortable in front of customer executives and still wants to build. The senior version at 5 to 8 years is also in this edition.
Requirements. 8+ years of experience in data engineering, data platforms and analytics, or software engineering. Deep experience with distributed computing using Apache Spark and knowledge of Spark runtime internals. Experience with technical project delivery: managing scope, timelines and measurable outcomes, and translating complex concepts into actionable solutions. What you would do. Work with customers to build and productionise solutions to their data and AI challenges on the Databricks platform. Own the architecture, lead design decisions and implement end to end systems spanning data engineering, AI and application development. Work cross functionally to shape long term strategic priorities alongside engineering, product and developer relations. Deliver with customer empathy, integrating with client systems, training and other technical needs so customers get the most value from their data. Build skills in new technical areas that support the deployment and integration of Databricks based solutions. ⭐ Remote, with a stated cost. The board lists this as Remote, India and nothing in the body imposes an office requirement. The posting does state "Travel to customers 20% of the time", so this is remote with regular customer visits rather than remote and stationary. That is disclosed here because remote is the most requested thing on this board and the detail changes whether it works for you. How the posting describes itself, worth reading before applying. "This is a hands-on, customer-facing role for builders who thrive at the intersection of technology and business impact", and "FDEs are billable and know how to complete projects according to" scope. Billable delivery work has a different rhythm from product engineering: timelines are committed to customers. Who this is for. A data or platform engineer with eight or more years and genuine Spark depth, who wants customer facing delivery and can travel a fifth of the time. Spark runtime internals is the distinguishing requirement and it is not something you can pick up in the interview loop.
Added August 3, 2026
Requirements as the posting states them. Educational qualification BE, B.Tech, MCA or M.Tech, which is a hard filter here. 2 to 6 years of experience in manual testing (functional, regression, sanity, integration) and automation (Selenium, Appium, API). Within that, 2+ years of relevant experience in automation and manual testing, and 2+ years specifically in automation with Selenium and Java. Experience with a BDD framework such as Cucumber, and with Rest Assured. Analysing requirements and PRDs and writing test cases from them. Web, mobile web and mobile app testing. API and web services testing. Writing SQL queries with exposure to MySQL. Defect life cycle with hands-on Jira. Working experience in Linux. Agile methodology. Selenium WebDriver and Appium. Programming in Java preferred. Open source tooling: Eclipse, JUnit, Maven. Scripting in shell, Python, Perl or Ruby. Nice to have: Jenkins exposure. Candidates from the e-commerce domain are explicitly preferred. Day to day and location. Noida, and Paytm marks this posting on-site with an employment type of Full-time Employment. The team is Insurance, inside the Technology department. Who this is for. A tester who already does both halves of the job, manual and automation, and wants a fintech scale problem. The BE, B.Tech, MCA or M.Tech line is the one requirement with no give in it, so if your degree is outside that list this is not the application to spend your time on. If you have 2 years and solid Selenium plus Java, you are inside the stated band rather than stretching for it, which is rare on this board right now.
Requirements. 3+ years of strong experience in performance testing and engineering. Proficiency in JMeter, LoadRunner, Gatling or an equivalent load generation tool. Experience with monitoring tools including Grafana, InfluxDB, JVM tools and MAT (Memory Analyzer Tool). Knowledge of API testing via Postman or SOAP UI, including WebSocket testing. A solid understanding of system architecture, scalability and distributed systems. Experience analysing performance metrics and identifying bottlenecks. Familiarity with NFRs, SLAs and KPIs. Strong analytical, problem solving and communication skills, and the ability to work across cross functional teams. The actual day to day, from the responsibilities list. Develop performance test strategies and plans tied to system requirements and project timelines. Understand the application architecture and pick the critical business transactions worth validating. Design realistic workload models. Create, maintain and execute the test scripts. Run baseline, load, stress and scalability tests. Monitor the system while it runs. Analyse results to find bottlenecks and system limits. Work with development and infrastructure teams to fix what you find. Recommend optimisations. Write detailed reports with metrics, findings and recommendations. Gather and validate NFRs, SLAs and KPIs with stakeholders. Location and terms. Noida, marked on-site, Full-time Employment, on the Telco team inside Technology. Who this is for. Someone who has owned performance testing end to end and can talk to a business stakeholder about what a p99 means for them. The posting asks you to communicate findings to non-technical stakeholders as an explicit requirement, so this suits a tester who writes well. Three years is a real floor here, not a formality, but there is no upper bound stated.
Minimum qualifications. A Bachelor's degree in Computer Science, a related technical field, or equivalent practical experience. 4+ years of professional experience designing, building and deploying production grade product components in Go, Java or C++. A proven background in microservices architecture, cloud deployments and distributed systems design. Strong core computer science fundamentals including algorithms, data structures and maintainable software engineering principles. Team oriented communication, with the posting explicitly naming cross functional and open office working. Preferred technical qualifications. Hands-on Kubernetes and containers, with prior Kubernetes control plane development called out as a plus. Implementing authentication (SSO, LDAP) and authorisation (RBAC, OAuth) frameworks. A background in e-commerce marketplace integration, or automating SaaS billing and usage reporting. Building telemetry reporting systems for production services, or developing public facing SDKs. What you would actually do. Develop, test and integrate high performance microservices into the Portworx suite with high availability in distributed systems. Lead the software lifecycle: architectural design, code reviews, unit and functional testing, documentation, CI/CD. Work with product managers, engineering peers and early adopter customers. Own feature stability, folding in customer feedback and fixing what testing and deployment surface. Research emerging cloud infrastructure tooling. Office reality. Bangalore, and the posting is tagged #LI-ONSITE. Everpure states across its postings that it is "primarily an in-office environment" and that you are expected to work from the Bangalore office except for PTO, work travel or approved leave. It also asks you to be willing to work in an open plan office. Treat this as an in-office job, not a hybrid one. Who this is for. A backend engineer with four or more years in a compiled language who wants Kubernetes storage and SaaS platform work. You do not need storage domain experience: the preferred list is about control planes, auth and billing integration, not flash media. If you need to work from home most of the week, this is the wrong role, and the posting is unusually honest about that.
Requirements. 4+ years as a backend developer with a strong focus on services development. Strong backend skills, Node.js preferred, with Python, Java or similar accepted. Real experience designing, building and maintaining distributed microservices architectures in production. A strong operational ownership mindset covering monitoring, troubleshooting and service reliability. Experience supporting high traffic, high throughput systems with strict availability and performance requirements. Hands-on GCP or another cloud. Experience using AI tools to drive and optimise development. Event driven and asynchronous architectures. Messaging and streaming with Kafka. A strong grasp of scalability, resilience, fault tolerance and performance optimisation. Experience with Angular or React on the front end. Ability to work independently to short timelines, to pick up existing systems quickly, and strong debugging and communication skills. Preferred. Monitoring, logging, alerting and observability. Handling millions of daily events, requests or messages. Infrastructure as code and CI/CD pipelines. Optimising cloud cost and performance. Designing highly available systems across regions. Kubernetes including deployment, scaling, observability and production operations. Day to day. Design, develop and maintain services and UIs. Contribute to services architecture. Build RESTful APIs and integrate external services. Work across SQL and NoSQL to design data models and access patterns. Find and fix performance bottlenecks. Use AI tooling (the posting names Claude) to build, test and maintain systems. Write unit and integration tests, review code, and investigate production issues. Shift and location, both published. Bengaluru, tagged #LI-Hybrid. ZoomInfo states a Work Shift of "General Shift" with start times of 09:00, 10:00 or 11:00 and finishes of 18:00, 19:00 or 20:00. That is a normal India day, which is worth knowing because several customer facing roles on this board run US or EMEA hours. Who this is for. A backend engineer four or more years in who wants scale and is comfortable being on the hook for what they ship. ZoomInfo's careers site returns 403 to automated checks, so this listing was confirmed live through the Greenhouse jobs API rather than the public page. The apply link is the employer's own and works normally in a browser.
Requirements. 4 to 8 years of experience in big data technologies. Strong hands-on Hadoop, MapReduce, Hive, Spark and PySpark. Excellent programming and debugging in Python, Java or Scala. Experience with a scripting language such as Python or Bash. Hands-on programming with multithreaded applications. The posting also asks for a strong product design sense and specialisation in Hadoop and Spark specifically. Good to have. NoSQL databases such as HBase or Cassandra. Databases, SQL and messaging queues like Kafka. Streaming applications using Spark Streaming, Flink or Storm. AWS and cloud technologies such as S3. Caching architectures such as Redis. The work itself. Grow the analytics capability with faster and more reliable tooling, handling petabytes of data every day. Build platforms that make data available to cluster users with low latency and horizontal scalability. Diagnose problems across the whole technical stack. Design and develop a real time events pipeline for data ingestion feeding real time dashboards. Write complex transformation functions turning raw sources into reliable data lake components. Design and implement new components across the Hadoop ecosystem. Title contradiction, worth knowing before you apply. The job board title is "Data Engineering, Senior / Lead Engineer" and the first line of the description is "Data Engineering, Technical Lead". Nothing in the responsibilities or requirements describes managing people, so we have published it at the stated 4 to 8 year band as an individual contributor role. If the level matters to you, ask in the first call which of the two the requisition actually is. Location and terms. Noida, marked on-site, Full-time Employment, on the Insurance team. Who this is for. A data engineer with four or more years on the Hadoop and Spark side who wants volume. If your background is warehouse and SQL rather than distributed processing, the mandatory list here is squarely the latter.
Requirements. 5+ years of professional full stack software development. Deep front end expertise in React or a similar modern JavaScript framework. Strong backend development in Java and the Spring ecosystem or similar. Solid experience designing and implementing scalable RESTful APIs and microservices. Proven ability to design and work with relational and NoSQL databases. Experience with cloud platforms such as AWS or GCP and with containerisation via Docker and Kubernetes. Designed and implemented relational database schemas in PostgreSQL and optimised complex SQL queries for high traffic features. Excellent problem solving, and a commitment to clean, maintainable, testable code. Familiarity with AI concepts or experience using AI assisted tools in the development workflow. Extra credit. Strong AWS knowledge including serverless services and infrastructure as code with Terraform. Cloud infrastructure on AWS or Google Cloud Platform. Packaging and distributing containerised applications with Docker and Kubernetes. Day to day. Design, develop and deploy scalable web applications with React and Java. Lead backend services and API development for performance, stability and scalability. Drive features within Compass. Work with product managers, UX designers and other engineers to turn requirements into technical specifications. Contribute to technical direction and best practices. Take part in code reviews, design discussions and operational support. Location. Bengaluru. The posting carries an internal #Hybrid_Bengaluru tag, and Okta states elsewhere that it enables a flexible approach where roles allow, so expect hybrid rather than fully remote or fully in office. Confirm the exact days in your first call. Who this is for. A full stack engineer with five or more years who wants an internal platform job with real users rather than a customer facing product surface. Because Compass is internal tooling, the feedback loop is short and you will meet the people using what you ship. One caution: Okta's job board publishes a "Minimum Work Experience: 0.0" field on several of its postings, including some in this edition. That is an unfilled placeholder, not a real zero. The years above come from the requirement list in the body.
Requirements. 5+ years of software development experience, with at least 3+ years working on large scale data systems. Strong SQL for data manipulation and Python for pipeline development. Hands-on experience building and operating data pipelines in a cloud environment, AWS preferred. Hands-on experience with the modern data stack, named specifically as Snowflake for warehousing, dbt for transformation and Terraform for infrastructure as code. Experience with data ingestion, streaming and event driven architecture such as Kafka, CDC and Snowpipe. Knowledge of data security and data privacy best practices. A strong understanding of data modelling principles. Extra credit. Experience with Snowpark. Day to day. Own and operate the critical data pipelines and infrastructure, and take part in the team's support rotation for availability and business continuity. Lead troubleshooting on complex pipeline or infrastructure issues, including going beyond the team's direct scope to get to a resolution. Manage the data onboarding lifecycle, working with stakeholders to integrate new internal and external sources. Develop and deploy data solutions with Snowflake, dbt, Airflow and Terraform. Advocate for modern tooling and better practice. You report to the manager of the Data Engineering Pipeline team. ⚠️ A years trap on this one. The requirement reads "5+ years of software development experience, with at least 3+ years working on large-scale data systems". Any tool that takes the smallest number in the sentence reads this as a 3 year job. It is a 5 year job with a 3 year specialisation inside it, and that is how we have listed it. Also note Okta publishes "Minimum Work Experience: 0.0" and "Maximum Work Experience: 0.0" in this posting's board metadata. That is a placeholder left unfilled, not a real experience figure. Location. Bengaluru. Okta operates a flexible model where the role allows; confirm office days in the first call. Who this is for. A data engineer with five or more years who wants ingestion and platform ownership, including the on call side of it, rather than analytics work. If your Snowflake and dbt are real rather than adjacent, you are in scope.
Requirements. 5+ years of experience in the software industry with a passion for solving complex software engineering problems. A software engineering foundation, specifically experience designing and developing reusable libraries and experimentation platforms for backend and frontend from scratch using industry best practices. Experience working with distributed systems. Demonstrated ability to write high quality code. Technologies you would use, as listed. Java 17 and JUnit 5. Docker and Kubernetes. AWS, GCP and Azure. SQL and BigQuery. Bazel and BuildKite. Day to day. Design and implement features and performance improvements for highly scalable distributed data pipelines on the cloud. Develop, maintain and test code. Conduct design and code reviews. Work with peers, product managers and customer support to ship with quality, performance and scalability. Understand and fix performance and scalability problems. Participate periodically in the on call rotation. Participate in the hiring process. Mentor junior developers. Office reality, stated in writing. "This is a full-time position based out of our Bangalore office." The hybrid model is defined as two days in the office each week. That is more specific than most postings manage and worth taking at face value. The merger. Fivetran and dbt Labs are combining, and the posting warns you will see references to both companies through the recruiting process as teams, systems and career sites integrate. Not a problem, just expect it. Who this is for. A backend engineer with five or more years who wants data infrastructure rather than application work. Mentoring and hiring are in the responsibilities, so this is a senior seat in practice as well as title, but there is no people management in it. ⚠️ One note on Fivetran postings generally. Its board publishes an internal "Priority Status" field on some requisitions, and values like "P3 (Future Open)" and "P2 (Internal Resources)" appear on roles that are not open to external applicants right now. This posting carries no such flag, which is why it is here and two other Fivetran roles are not.
Requirements. 5+ years of experience post BE or B.Tech. Experience with React, TypeScript and CSS, and the team uses TailwindCSS. A track record of leading UI features end to end. What you would do. Build new interfaces for lawyers and organisations to collaborate with AI. Lead end to end UI features across Assistant, Vault, Workflows, the Word and Outlook add-ins and future Harvey products, covering scoping, design reviews, implementation and launch. Lead frontend engineering on new products being built at Harvey. ⛔ The location, because the job board is wrong about it. Harvey's own board flags this posting, and every other India posting it has, as remote. It is not. The bodies of Harvey's India postings state they are based in Bengaluru, and one Harvey posting listed under Bengaluru says in its own body that it is based in San Francisco. We publish the location from the body, never the flag, so treat this as a Bengaluru role. If remote matters to you, ask before you invest in the process. Eligibility. Harvey states on its India postings that you must be authorised to work in India and that visa sponsorship is not available. Who this is for. A frontend engineer with five or more years who wants ownership rather than tickets: the posting talks about leading features and leading frontend on new products, not implementing designs handed down. The bar on craft is explicitly high and the team says so up front, which is useful information either way. If you have been doing React and TypeScript for five years and want a product with real complexity behind the interface, this is a strong fit, and it is a rare chance to get into a company at this stage without a decade of experience.
Requirements. 5+ years of experience troubleshooting Unix and Linux. Experience with algorithms, data structures, complexity analysis and software design. Experience in one or more of Java, Python or Go. Experience in a large scale web operations role. Hands-on experience with Ansible, Kubernetes, SQL and NoSQL datastores, and CI/CD. What the team does. Engineering Stack Support (ESS) is a team of software engineers focused on improving availability, latency, performance, efficiency, change management, monitoring, emergency response and capacity planning of the engineering stacks. It creates a bridge between service owners and platform engineering by applying a software engineering mindset to application debugging and system administration. ⭐ Levelling, stated in the posting. "Please note, this team is hiring across all levels and candidates are individually assessed and appropriately leveled based upon their skills and experience." Netskope has said the same on other postings we have carried. In practice that means the 5 year figure is the stated floor and the actual level is decided after assessment, so it is worth applying if you are close rather than exactly on it. Location. Bengaluru. Who this is for. An SRE or infrastructure engineer with five or more years who wants internal platform reliability work at a security company, and who is comfortable that the job mixes writing software with system administration rather than being purely one or the other. If you want customer facing incident work, note this team supports engineering stacks, not customers.
Requirements. 5+ years of experience in Java, React and AWS, with strong development proficiency and a solid foundation in object oriented programming. The job grade is Senior Consultant. Responsibilities as written. Learn and adopt practices like writing clean and reusable code using TDD, pair programming and design patterns. Use and advocate for continuous delivery practices to deliver high quality software and value early. Work in collaborative, value driven teams building customer experiences for clients. Create large scale distributed systems out of microservices. Collaborate with a variety of teammates to build features, design concepts and interactive prototypes, keeping best practices and UX specifications embedded along the way. Apply technology thinking from the Thoughtworks Technology Radar to client problems. Use DevSecOps tools and practices, shifting security left in development. Take part in the whole cycle of software consulting and delivery from ideation to deployment. Act as a mentor for more junior consultants. ⛔ Office policy, and it is the strictest in this edition. "You may be expected to work out of our Thoughtworks office or at our client's office location for all five working days of the week, depending on business or clients' needs." The Greenhouse metadata also carries "Remote Eligible: False". Note that the posting separately carries an #LI-Remote tag, which contradicts both of those: the body and the metadata agree with each other, so we have published it as Pune, on-site, five days. Who this is for. An engineer with five or more years who wants consulting: different clients, different domains, strong opinions about how software should be built, and a company that will back you on TDD and pair programming rather than treat them as overhead. It is also a good fit if you want to move into a mentoring track without becoming a manager. Do not apply if you need remote or hybrid, because the posting tells you five days in writing.
Requirements. 5 to 8 years of experience in Software Development in Test (SDET) or systems engineering, with a BS or MS in Computer Science or a related field. Hands-on experience with Linux, shell scripting, Git, and architecting scalable CI/CD pipelines. The team, in its own words. The Database QA team owns the end to end quality of YugabyteDB, validating everything from core storage and the language layers (YSQL and YCQL) through to high impact features such as Change Data Capture. It blends performance engineering with system level stress testing so the database holds up in unpredictable production environments. The team describes itself as the champions of correctness in a distributed world. Company context worth having. YugabyteDB is a PostgreSQL compatible distributed database built for cloud native workloads, deployed in over 100 countries and powering more than 5 million clusters. Named customers include Shopify, Paramount+, GM, Kroger, Fiserv and NPCI. Yugabyte's staff are spread across 12 or more countries and multiple time zones. Location. The posting lists India without naming a city. Who this is for. A test engineer with five to eight years who wants depth in distributed systems. The degree line is stated (BS or MS in Computer Science or related), so it is a real filter. If your background is functional or manual QA, this is a stretch: the work assumes you can reason about storage engines, consistency and failure modes. If you have been writing stress and performance harnesses against backend systems, it is a natural next step and one of the more technically interesting QA seats on the board.
Requirements. 6+ years of experience in advanced data modelling using Data Vault (DV 2.0). Proven experience building analytics systems with data transformation, dependency and workload management, with the toolset named as Data Vault, AutomateDV, dbt core, Airflow, Snowflake, GitLab and SQL. Proven experience building and maintaining business analytics layers and semantic layers that let non-technical users self serve. What you would do. Lead the implementation of efficient and scalable systems that optimise data transformations from the Snowflake data lake into clean, documented data products. Contribute to design standards and architectural principles. Build and maintain a governed, robust, reliable and scalable analytics system (DW/DV). Work with BI analysts and data scientists on data accessibility guidelines. Drive data democratisation by activating data on platforms including the Smartsheet platform itself, Amplitude, Thoughtspot and Gainsight. Create frameworks that improve data quality and observability so issues are found faster. Create and implement data testing plans covering data validation, data quality assessment and regression testing to catch anomalies. Reporting line and location, both stated. "This full-time position reports to the Director of Analytics Engineering and is based in Smartsheet's corporate offices in Bengaluru, India." The job title itself says Hybrid, Bangalore. ⛔ A remote tag to ignore. This posting carries an #LI-Remote tag while its own title says "Hybrid, Bangalore" and its body says it is based in the Bengaluru offices. Every Smartsheet India posting in this edition carries that same contradiction. The body wins: this is a Bengaluru hybrid job. Who this is for. An analytics engineer with six or more years who has actually built with Data Vault, because that is the first requirement and it is specific enough that adjacent modelling experience will show. If you know dbt and Snowflake but have never done DV 2.0, expect that to come up early.
Requirements. 6+ years building scalable Android apps with real user impact. Experience with Retrofit, Room, Coroutines, Jetpack and RxJava. Experience with shared libraries, modularisation and build optimisations. What you would own. Architect and build scalable, high quality components and systems used across the Meesho Android app. Own and improve core app performance metrics including page latency, cold start time, memory usage and App Vitals. Design reusable frameworks, SDKs and libraries that power consistent experiences across multiple feature teams. Be the go-to expert for Android best practice, from Jetpack and Compose through modularisation and Gradle optimisation. Mentor and support engineers across the org. The team's framing, which tells you the constraint. Meesho's Android team describes building an experience that works on everything from five thousand rupee entry level phones in small towns to flagship devices in metros, calling it a challenge of scale, stability and empathy. They track stability metrics they say few others bother with, and handle millions of orders without downtime. Level. The posting states plainly that this is "a critical individual contributor role focused on elevating the foundation of Meesho's Android experience", so the mentoring in the responsibilities is technical influence rather than people management. Location and terms. Bangalore, marked on-site by Meesho, Full Time Employee, on the Demand team inside Tech. Who this is for. A senior Android engineer with six or more years who wants platform work: frameworks, performance and build systems used by other engineers, rather than shipping user facing features. If your experience is feature delivery and you have never profiled a cold start or fought Gradle, the gap will show. If low end device performance is a thing you have genuinely optimised for, there are few Indian products where it matters more.
Requirements. A B.Tech in Computer Science, Machine Learning or a related field, with at least 6+ years of experience in AI/ML research. Experience in auction theory, predictive modelling, causal inference and reinforcement learning. Expertise in PyTorch or TensorFlow, and proficiency in Python as well as big data technologies. A history of mentoring junior data scientists and comfort driving multiple problem statements at once. What you would do. Design and develop bidding, budget pacing and related algorithms that optimise ad spend and return. Create frameworks and experimental designs to measure ad effectiveness and ROI. Work with product and engineering to turn business requirements into ML solutions. Communicate the long term roadmap, insights and recommendations to technical and business leadership. Mentor junior data scientists and provide technical guidance. Lead research initiatives in machine learning, auction theory and advertising technology. Team context. Meesho's data science group works across fraud detection, inventory optimisation and platform vernacularisation, so the AdTech team sits inside a broader group solving commerce problems for a mostly non metro user base. Location and terms. Bangalore, marked on-site, Full Time Employee, on the Data Science team. Who this is for. A data scientist with six or more years whose work has been in ranking, auctions, bidding or another domain where a model's output is money. The auction theory and causal inference requirements are specific: general ML experience without exposure to either will be a stretch. The mentoring line is stated as a requirement rather than a responsibility, so bring examples. Note the title says Principal but the stated bar is 6 years, which is lower than most Principal titles on this board and is why it sits in the 6 year group rather than the senior one.
Requirements. 6 to 10 years of experience in DevOps engineering. Strong practical knowledge of managing AWS infrastructure, specifically EC2, load balancers, CloudFront, ElastiCache, EBS, S3, IAM, CloudWatch, Auto Scaling and Lambda. An understanding of open source server software such as Tomcat, HBase, Kafka, MySQL, Redis and Elasticsearch. Strong experience in infrastructure automation with Ansible, Terraform, CloudFormation or similar. Hands-on Kubernetes, EKS, Docker and ECS. Hands-on automation in shell, Python or PowerShell. Strong experience with Jenkins, Maven or Gradle. Experience with DevOps and CI/CD pipelines using Jira, Confluence, Jenkins, Git, Maven, Nexus and Docker. Hands-on CI/CD automation for EC2, ASG, EKS and ECS using Helm and Jenkins. Big plus. Hands-on experience with any of the big data stack: Hadoop, Kafka, EMR, Ranger, Spark, Hive, Starburst, Looker, TigerGraph or Neo4j. This is what makes it a data DevOps seat rather than a general one. Scale, in the team's own words. Paytm describes itself as cloud first on AWS, working with petabytes of data, millions of requests per minute and a few thousand microservices across a few hundred thousand cores. It names three things it built in house: one of the world's largest CI platforms, its own AWS cost management platform, and EBS autoscaling that downscales with no outage. Its observability system processes tens of millions of events per second. Location and terms. Noida, marked on-site, on the Lending team inside Technology, with an employment type of On-roll (Paytm's term for a permanent employee rather than a contractor). Who this is for. A DevOps or platform engineer with six or more years who wants the data infrastructure side and real AWS scale. Despite the "Lead" in the title, nothing in the requirement or responsibility list describes managing people; it reads as a senior individual contributor seat.
Minimum requirements. 7+ years of progressive software development experience with a proven track record of designing and building scalable, high performance server-side features using Java and Spring. Deep experience in fast paced agile environments with a strong understanding of CI/CD and automated testing. Experience in cloud security, identity or authentication protocols. Experience with UI technologies such as ReactJS. A Bachelor's degree in Computer Science or equivalent experience. Responsibilities. Partner with product management, engineering directors and principal architects to turn business objectives into scalable technical roadmaps. Drive cross functional collaboration with product, design and QA. Lead the design and implementation of new features and services in the core Java platform, owning them from conception to deployment. Define engineering best practice and contribute to technical designs, proposals and long term architectural decisions. Act as a force multiplier across teams, mentoring Staff and Senior engineers and guiding design reviews. Develop maintainable software with comprehensive test coverage and improve testing and CI/CD strategy. Maintain technical documentation. Champion AI native engineering practice in the product development lifecycle using AI coding assistants, while keeping security and code quality standards. Identify emerging trends such as advanced device security and prototype solutions. ⚠️ The finding worth knowing before you apply. Okta is running this identical job description under two different seniority titles at the same time. This posting is "Staff Software Engineer, Backend" and a second requisition, "Principal Software Engineer, Backend", carries a body that is 99.7 percent identical: same Device Identity and Access team, same 7+ years, same Java and Spring requirements, same hybrid tag. The only real differences are the requisition id and one heading line. We have published the Staff one. If you are offered either, the level is worth a direct question, because the written requirements do not distinguish them at all. Location. Bengaluru, tagged #LI-Hybrid. Who this is for. A backend engineer with seven or more years in Java and Spring who wants scope beyond a single team. Identity and authentication experience is listed as a requirement rather than a bonus, so some exposure to the domain matters.
Requirements. 7+ years of software development experience using Python. Proven experience with distributed systems software design. Good knowledge of RESTful API standards. Proven experience in distributed microservices development. Experience with cloud based infrastructure on AWS or GCP. Knowledge of industry best practice for package management and release cycles (CI/CD). Experience with NoSQL (MongoDB or Elasticsearch) and SQL. High personal and leadership skills. Strong communication skills in English. What you would do. Design, build and deploy complex distributed systems. Build third party integrations with major conference providers using their SDKs. Shift and location, both published. Bengaluru, tagged #LI-Hybrid. ZoomInfo states a Work Shift of "General Shift" with start times of 09:00, 10:00 or 11:00 and corresponding finishes of 18:00, 19:00 or 20:00, so this is an India hours role. One process detail the posting discloses. ZoomInfo says it may use a software based assessment as part of recruitment, and publishes the results of that tool's most recent bias audit. Expect an automated stage. Who this is for. A Python engineer with seven or more years who is comfortable owning integrations and distributed services. The posting is unusually thin on responsibilities, which cuts both ways: there is room to shape the role, and there is less to judge it by before you talk to the team. Worth asking in the first call which product surface the conference provider integrations feed, because that determines how much of the job is integration maintenance versus new system design. Note ZoomInfo's careers site returns 403 to automated link checks, so this posting was confirmed live through the Greenhouse jobs API rather than the public page. The apply link works normally in a browser.
Requirements. 7+ years of experience in product security with a focus on application security and DevSecOps. Proven experience leading architectural changes or cross team efforts to mitigate security vulnerabilities. Hands-on experience with manual source code reviews and securing production code. Experience with Git, Jenkins, Artifactory or similar. Experience with Docker and containerisation is highly desirable. What you would do. Lead and manage all aspects of the Secure Software Development Lifecycle. Implement and manage security tools within the CI/CD pipeline (DevSecOps). Conduct and oversee VAPT for web applications, APIs, iOS and Android apps. Perform threat modelling, design and architecture reviews. Execute manual source code reviews and improve security in production. Manage and optimise a self managed bug bounty programme. Provide security architectural guidance to engineering and IT teams. Manage issues found through penetration tests and the bug bounty. Lead security training and awareness across the organisation. Manage Web Application Firewalls. Take part in the Security Champions programme. Help create and maintain security risk models for new and existing systems. Location and terms. Bangalore, marked on-site, Full Time Employee, on the Infrastructure team inside Tech. Who this is for. An AppSec engineer with seven or more years who wants to own the programme rather than execute a piece of it. Note the mix: this is not a pure pentest role and it is not a pure tooling role, it is both plus architecture review and internal advocacy. If you want to spend all day testing, the training, awareness and Security Champions responsibilities will not suit. The "lead and manage" language here is about the security programme and its findings, not about managing engineers.
Requirements. 5+ years of experience creating, deploying and scaling machine learning solutions in a cloud environment. 7+ years of programming experience in languages used in AI/ML such as Python or Scala. 4+ years of experience developing deep learning and traditional ML models using common frameworks such as PyTorch, TensorFlow, HuggingFace or scikit-learn. Hands-on experience with at least one major cloud provider (AWS, Azure or GCP). Legally eligible to work in India on an ongoing basis. ⚠️ Three different year figures. The requirement list carries 5+, 7+ and 4+ years across three separate bullets, all mandatory. We publish the highest mandatory figure, 7, because that is the bar you have to clear on the programming requirement. Any tool taking the smallest number would list this as a 4 year job, which would be wrong. What you would do. Automate deployment and retraining of ML models from training through production inference by building and managing complete CI/CD/CT pipelines. Build, fine tune or use pre-trained LLMs, deep learning models or traditional ML models. Evaluate and recommend AI or ML solutions using vendor products, custom models or both. Implement model versioning, lineage tracking and auditing for compliance with security and ethical standards. Continuously monitor production model health, identifying and correcting drift, staleness and degradation. Incorporate user feedback and manage retraining cycles. Act as the connection between data scientists and software engineers. Partner with engineers, product managers and business functions to integrate ML across Smartsheet. Provision and manage scalable cloud infrastructure using infrastructure as code. Provide architectural guidance and mentorship to ML engineers, data scientists and analytics engineers. Write clear technical documentation. Reporting line and location. You report to the Director, Analytics Engineering and Data Governance, and the posting says you "work from our Bangalore, India office". ⛔ Ignore the remote tag. Like every Smartsheet India posting in this edition, this one carries an #LI-Remote tag while the body states a Bangalore office. The body wins. Who this is for. An ML engineer with seven or more years who wants the platform and operations side. The mentorship line is architectural guidance, not people management.
Requirements. 8+ years of systems engineering experience focused on designing and optimising infrastructure for high performance, low latency applications. Hands-on experience with Software Defined Networking (SDN), cloud platforms such as AWS or Azure, and containerisation tools such as Docker or Kubernetes. Responsibilities. Design and optimise system infrastructure and datapaths for high performance networking and low latency security applications. Implement and optimise core networking protocols including NAT, DNS, DHCP and policy enforcement for enterprise grade performance. Use AI coding assistants and LLMs to optimise code for performance and memory safety and to streamline the development lifecycle through automated testing. Resolve complex system issues using deep expertise in the Linux kernel, networking features and filesystems. Write detailed technical specifications and rigorous unit tests. Location and terms. "This is a hybrid role based in Bangalore", reporting to the Director, Software Engineering in the Software Engineering department. Employment type is listed as Fulltime Employee. Tagged #LI-Hybrid. A note on Zscaler titles. Zscaler runs several concurrent requisitions with near identical titles across different teams, and has had five separate roles called "Staff Software Development Engineer" open at once. The team and the stack are what distinguish them, not the title, so read the responsibilities rather than assuming a level from the words Senior or Staff. This one is the networking datapath seat. Who this is for. A systems or networking engineer with eight or more years who wants kernel adjacent performance work rather than application development. If your background is web services, the NAT, DNS, DHCP and Linux kernel requirements are a genuine barrier here rather than nice to haves. If you have done datapath or packet processing work, this is squarely aimed at you.
Minimum qualifications. 8+ years of industry experience with demonstrated curiosity and active exploration of AI tools, and a proven history of integrating new technologies to enhance daily workflows and augment problem solving. Strong hands-on software engineering experience with FastAPI, Next.js and Postgres, including building application stacks end to end. A Bachelor's degree in Computer Science or a related technical field. Responsibilities. Build and scale the agentic layer of the AI Native Product Operations Platform by designing production grade AI systems and supporting platform capabilities. Develop hands-on across FastAPI, Next.js and Postgres while applying practical knowledge of RAG architectures, embeddings and vector retrieval. Implement standards, patterns and guardrails so AI development on the platform stays scalable, reliable and cohesive. Work with product and other stakeholders to translate business needs into technical solutions optimised for cost and throughput. Contribute in a high velocity delivery environment with frequent releases and end to end execution. Location. Bangalore or Mohali, both listed. Zscaler operates a hybrid working model. Employment type is Fulltime Employee, in the Products division. ⚠️ A years figure that automated tools miss. This posting writes the requirement as "8 +yrs", with a space before the unit and an abbreviation instead of the word "years". Standard parsers match "8+ years" and would read this posting as stating no experience requirement at all. Read by hand it is 8. Who this is for. A senior engineer with eight or more years who has moved into AI application work and wants to own a platform layer rather than a feature. The stack requirement is specific (FastAPI, Next.js, Postgres), so Python plus React experience transfers but is not identical. The role is practical AI engineering, so if your interest is model training or research this is not that job. Mohali as an option is worth noting if north India suits you better than Bangalore.
Requirements. A BS in Computer Science. 8+ years of experience designing, developing and testing enterprise products, with Golang preferred. A good understanding of microservice architectures and cloud native platforms. Experience designing and owning microservices that operate and scale in a distributed system architecture reaching thousands of nodes. Expert debugging skills and the ability to navigate ambiguous problems at scale in public and private cloud environments. Experience working with multiple internal and external stakeholders, from product management through to customers. Responsibilities. Design and develop cloud native microservices and integrate new features into Portworx products. Focus on design, development, unit and functional testing, code review, documentation and CI/CD. Debug product and performance issues in large scale clusters using AI tooling. Work with peers and stakeholders to take solutions from initial design to production. Take full ownership of design and development, adapting to customer feedback and handling issues found in unit testing, system testing and customer deployments. Experiment with new technologies. Office reality. Bangalore. The posting states directly: "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." Everpure is one of the few employers on this board that states its office policy plainly, and it means it. Who this is for. A backend or distributed systems engineer with eight or more years, ideally in Go, who wants storage and Kubernetes depth. The debugging emphasis is real: much of the job is working out why something behaves oddly on a large customer cluster, which suits people who enjoy diagnosis. Everpure runs several Member of Technical Staff requisitions on different teams at very different bars, from 4 years up to 18, so check which one you are reading.
Requirements. 8+ years of experience in a relevant field, and the posting adds a hard qualifier: "from only product based companies". Strong experience with microservice architecture. Experience leading technical architecture discussions and helping drive technical decisions within the team. Experience partnering with the product management team. Experience developing products that handle large data sets. Good to have. Experience in the integration domain. Experience working on SaaS solutions. Technical foundation, as listed. Data structures and algorithms. Design principles. Software design, both high level and low level. Performance and scalability. Hands-on with the stack: Node.js (or expertise in another language, which the posting says is acceptable), MongoDB, Python, Amazon AWS and Apache Kafka. ⛔ The eligibility filter to read first. "8+ years of experience in a relevant field (from only product based companies)" is stated in the requirements. If your background is services, consulting or an IT outsourcing firm, this posting is telling you in advance that it will screen you out, regardless of the quality of the work. Celigo carried the same requirement on its previous listing, so it is a standing policy rather than a slip. Better to know now than after three rounds. On the language. The posting says "We are looking for someone that absolutely loves to write code. Experience with Node JS is an added advantage, but if there are any really talented developers out there looking to try something new, we would love to hear from you too." So Node.js is preferred rather than mandatory. Location. Hyderabad, with the posting describing a flexible hybrid work culture and modern offices. Who this is for. A backend engineer with eight or more years from a product company who wants architecture influence alongside hands-on coding. The posting does use "lead teams" and "drive a small set of technically strong individuals" language, so expect technical leadership responsibilities, though nothing in it describes people management, hiring or performance reviews.
Must haves. 8+ years of professional software development experience with a proven track record in a Lead or Staff capacity. Proficiency in React (preferred) or Angular, with a focus on state management, performance optimisation and data visualisation. Expert level knowledge of Java or Python, with comfort in multi-threading and concurrency patterns. API design and integration: experience designing, building and consuming secure, performant RESTful APIs or GraphQL. Experience with front end technologies including HTML, JavaScript and CSS. Experience with Go or other high concurrency languages. What you would do. Architect and execute: lead the design of end to end features, from high performance React interfaces to scalable Java and Python microservices. AI innovation: drive the integration of LLMs and AI agents into the New Relic ecosystem, including building and maintaining MCP (Model Context Protocol) servers to bridge New Relic data with AI models. Scale heavily: build and maintain highly available, multi-threaded backend services handling massive throughput and concurrency. Technical leadership: lead system architecture discussions, conduct deep dive code reviews and set engineering standards. Collaborate with product and design to turn complex data visualisations into performant user experiences. Mentor: guide junior and senior engineers through complex technical hurdles. Scale context, from the posting. You would build and support a core set of services that all of New Relic's agents connect to every hour of every day, processing millions of messages per second and handling petabytes of data, as part of a distributed team. Location. Bangalore. New Relic's metadata lists the Work Arrangement as Hybrid, and the company states elsewhere that its model spans fully office based, fully remote and hybrid depending on the role, so confirm which applies here in the first call. Who this is for. A full stack engineer with eight or more years who wants observability scale and the MCP and LLM integration work, which is unusually current. Despite the "Lead" title, the mentoring is technical guidance rather than line management.
Requirements. 8+ years of experience in software quality engineering with a strong automation focus. Hands-on experience with Playwright for end to end browser automation including multi-tab, auth flows and visual testing. What you would own. Design and own the overall test automation framework and strategy across both the Voice AI and Monitoring and Analytics platforms. Define test pyramid principles (unit, integration, contract, end to end) and enforce them across repositories. Lead architecture decisions for automation tooling, CI/CD test pipelines and observability of test health. Establish standards for test data management, environment parity and flakiness elimination. Own the performance testing practice covering load, stress, soak and spike testing for backend services and APIs. Define performance baselines, SLOs and regression gates integrated into CI/CD. Instrument test runs with profiling and APM tooling to find throughput bottlenecks and latency regressions. Build scalable performance test harnesses using Locust, k6 or equivalent. Collaboration. Act as a technical lead and quality champion, influencing engineering culture, coding standards and test coverage expectations. Mentor mid-level and senior engineers on automation patterns, code quality and testing strategy. Partner with product managers to define acceptance criteria and quality gates. Reporting line and location. You report to the Director, NOC Delivery and Automation. Bangalore, Karnataka. Who this is for. A quality engineer with eight or more years who wants strategy and system ownership. Playwright is named specifically rather than "a browser automation tool", so hands-on experience with it matters. The performance testing half is as large as the functional half here, so this suits someone who has done both rather than one. ChargePoint runs several similar NOC automation requisitions; this one is the Voice AI and monitoring platform seat, and its description differs substantially from the others.
Requirements. 8 to 12 years of backend engineering experience. Experience with NoSQL databases such as Cassandra, MongoDB or Aerospike. The posting states that recent and ongoing hands-on coding experience in production environments is required, which is worth noting at this level. The team and stack. Agoda's backend engineering team builds high scale, fault tolerant distributed systems for a global travel platform serving millions of users daily, owning mission critical domains across inventory, pricing, booking, payments and the customer and partner platforms. Systems run with high availability, low latency and zero downtime expectations, using Scala, Go, Java and Kotlin with Kafka and Aerospike, plus CI/CD, automation and observability. The team ships dozens of releases a day and designs for resilience and self healing. What you would do. Drive the design and development of scalable distributed systems, working on high impact backend services, combining hands-on coding, system design and technical leadership, contributing to complex systems and influencing engineering practice. ⛔ Visa and location. The posting title says "Gurugram based" and Agoda's metadata records "Visa sponsored: False", so this role is for candidates already able to work in India. The department is listed as IT Engineering. Who this is for. A backend engineer with eight or more years who wants scale and is still writing code, since the posting makes ongoing hands-on coding an explicit requirement rather than an assumption. JVM and Scala experience transfers most directly. Agoda also runs a separate Level 5 "Backend Lead Software Engineer" requisition at 11+ years in the same office if you are further along; that one adds mentoring and cross team influence on top of the same technical base.
Requirements. 10+ years of data engineering experience, with at least 5 years focused on architecting data platforms for data products, analytics or AI driven products. Expert level understanding of data pipeline and orchestration tooling, with dbt, Airflow, Fivetran and Terraform named specifically. Experience with high compliance and high security regulated environments is listed as a plus. The remit. Okta describes this as the technical visionary role for its internal data platform supporting internal AI use cases with AI ready data. You are responsible for turning the data product vision into a secure, scalable and elegant technical reality, owning the technical strategy, implementation and scalability that brings the AI and data product roadmap to life. You own the technical standards for engineering excellence, security and governance so the core data platform is trusted and ready to power AI powered products and decision making across Okta. The posting frames it as balancing today's execution against building a durable foundation. Reporting line. The Senior Manager of Enterprise Data Platform. Location. Bengaluru, and the city is in the job title itself. ⚠️ Board metadata to ignore. Several Okta postings, including some in this edition, publish "Minimum Work Experience: 0.0" and "Maximum Work Experience: 0.0" in their Greenhouse metadata. Read as structured data that would say no experience is needed; it is an unfilled placeholder. The 10 year figure above is from the requirement list in the posting body, which is the only source we trust for years. Who this is for. A principal or staff level data engineer with a decade in, at least half of it architecting platforms rather than building pipelines on someone else's. The governance and security emphasis is heavy, which suits someone who has worked under real compliance constraints. If you want to lead a team, note this is framed as technical ownership: the leadership is over standards and architecture, not headcount.
Requirements. 10+ years of experience in infrastructure engineering or platform engineering in a production environment. Experience with observability tools including Datadog and Sentry, and incident response practices including PagerDuty. What you would do. Design and build new infrastructure systems while scaling and strengthening existing infrastructure. Architect and optimise distributed systems for reliability, including load balancing, quota management and failover mechanisms. Build distributed rate limiting and quota management systems using Redis backed algorithms to handle bursty traffic patterns without degrading user experience. Work in an environment balanced between building new systems and operational excellence, keeping Harvey resilient and efficient as it scales across products, regions, customers and usage. Your work affects the reliability, scalability and security of the platform serving leading law firms and professional service providers. Scale, as stated. Harvey's infrastructure processes billions of prompt tokens and millions of daily requests across its global legal AI platform. ⛔ Location, because the job board is wrong. This posting is flagged remote on Harvey's own board, and its body says "This role is based in Bengaluru, India". Every Harvey India posting carries the same false remote flag, and one Harvey posting listed under Bengaluru states in its body that it is based in San Francisco. We take the location from the body every time. This is a Bengaluru role. Eligibility. Harvey states on its India postings that you must be authorised to work in India and that visa sponsorship is not available. Who this is for. An infrastructure or platform engineer with ten or more years who wants high throughput AI serving problems. Rate limiting, quota management and failover at this scale are specific skills; if you have built them, the posting is describing your work directly. The company is explicit about pace and intensity in its culture section, which is worth reading honestly before applying.
Requirements. 12+ years of industry experience. 4+ years of experience building large scale distributed systems. Experience with large scale messaging systems such as Kafka, RabbitMQ or commercial equivalents. ⚠️ A years trap on this one. The requirement list carries both "12+ years of industry experience" and "4+ years of experience building large scale distributed systems". Any tool that takes the smallest figure in a posting would list this as a 4 year job. It is a 12 year job with a 4 year distributed systems specialisation inside it, and that is how it is listed here. The impact, as the posting frames it. Design and run the Databricks metrics store, letting all business units and engineering teams bring detailed metrics into a common platform for sharing and aggregation with high quality, introspection and query performance. Design and run the cross company Data Intelligence Platform containing every business and product metric used to run Databricks, balancing data protection against shareability as the company transitions to being public. Develop tooling and infrastructure to manage and run Databricks on Databricks at scale across multiple clouds, geographies and deployments. You would build a variety of tools spanning logging, orchestration, data transformation, metric store, governance platforms and data consumption layers, working with Databricks product teams, data science and applied AI. A useful detail. The team functions as a large, production, in-house customer that dogfoods Databricks and guides the future direction of the product, so platform gaps you find turn into product work. Location. Bengaluru, India, with the hiring entity listed as Databricks India Private Limited. Who this is for. A staff level data or backend engineer with over a decade of experience who wants internal platform scale and influence on a commercial product at the same time. Note Databricks uses the same titles at very different bars: it has run "Staff Software Engineer" at 10 to 12 years and "Senior Staff Software Engineer" at 15, so the title tells you less than the years do.
Requirements. 14+ years of developer level Linux platform experience. Strong programming skills in C, C++, Python, Java, Go or other languages, with a solid understanding of object oriented programming. Hands-on development experience in the storage domain and related technologies is listed as preferred rather than required. What you would do. Design, collaborate on and implement creative new algorithms and technologies for high performance, highly reliable systems, which the posting describes as six nines. Own and deliver innovation end to end, from concept to shipped product. Analyse and solve challenging problems in the FlashBlade product area. The team, in its own words. This is described as an opportunity to be one of the seed members of a growing product team in the FlashBlade business unit, one of the fastest growing at the company. FlashBlade is a scale out all flash file and object store designed for modern workloads. The team says it is deeply immersed in how customers work with data: AI, modern backup, log analytics with Splunk and Elastic, data pipelines with Kafka and cluster computing with Spark. It asks for people who enjoy distributed systems, algorithms, operating systems, the Linux kernel, database internals, hypervisors, containers, compilers and hardware, "or at least some of those". Office reality. Bangalore, in office. Everpure states across its postings that it is primarily an in-office environment and expects you at the Bangalore office except for PTO, work travel or approved leave. Who this is for. A systems engineer with fourteen or more years and real Linux platform depth. This is one of the highest bars in this edition and it is not padding: the work is algorithm design for storage systems at six nines reliability. Storage domain experience is preferred but not required, so strong systems people from adjacent fields (databases, kernels, distributed infrastructure) are in scope. Everpure runs Member of Technical Staff requisitions from 4 years to 18, so the title carries no level information at all here.
Requirements. 15+ years of backend engineering experience building and operating production web applications or SaaS products. Strong programming skills in Python and experience with a modern web framework. Hands-on experience with relational databases. What you would do. Work closely with product to prioritise customer focused work and deliver reliable features quickly in a fast moving environment. Design and own backend services and APIs that power Harvey's web applications, workflows and integrations. Model and manage data. Build secure, multi-tenant services. Orchestrate interactions with LLMs and agentic tools. Help define the backend architecture powering Harvey's rapidly expanding product surface. The posting says the work has immediate business and customer impact as you ship the foundational systems behind the next generation of Harvey's AI products. ⛔ Location, because the board is wrong about it. Harvey flags all of its India postings as remote on its own job board. They are not. Harvey's India postings state Bengaluru in their bodies, and one posting listed on the board under Bengaluru says in its body that the role is based in San Francisco. We publish the location from the body every time. This is a Bengaluru role. Eligibility. Harvey states that you must be authorised to work in India and that visa sponsorship is not available. Company context. Harvey builds agentic AI for legal and professional services, combining an enterprise platform with domain expertise. It describes itself as scaling fast with strong product market fit, and is direct about the culture: it names decisiveness and intensity, and says the bar is high. Take that as information rather than marketing when you weigh the role. Who this is for. A backend engineer with fifteen or more years who wants to be close to the product rather than deep in infrastructure. Python and multi-tenant SaaS are the core requirements. If you want the infrastructure side instead, Harvey has a separate core infrastructure seat at 10+ years, also in this edition.
Requirements. 18+ years of experience developing and implementing high performance networking products, coupled with a Bachelor's degree or higher in Computer Science or Computer Engineering. Significant domain knowledge of the networking stack with hands-on systems development including IPv4 and IPv6, API design and distributed systems. Hardware and kernel proficiency: hands-on experience with the Broadcom SDK, familiarity with modern switch silicon features such as ECMP and QoS, and direct experience with Linux kernel or device driver development. What you would do. Manage the full software development lifecycle, from initial architecture and invention through development, release and ongoing maintenance. Drive technical strategy by influencing system design, architecture and best practice, contributing specifically to the evolution of the FlashBlade networking product area. Invent and optimise algorithms to orchestrate multi-array and multi-cloud storage systems. Architect, implement and optimise core services spanning on-premises arrays and cloud deployments. Team context. The FlashBlade team builds a portfolio designed for demanding mission critical applications. Although the product is a hardware storage array, the posting notes that over 90 percent of the engineering staff are software engineers. Customers value simplicity of management, continuous upgrades and never taking downtime. Office reality. Bangalore, in office. Everpure states it is primarily an in-office environment and expects attendance at the Bangalore office except for PTO, work travel or approved leave. Who this is for. A networking architect with eighteen or more years and genuine silicon and kernel level exposure. This is the narrowest role in this edition: the Broadcom SDK and switch silicon requirements mean general network engineering will not clear the bar. If you have built switching or routing products, this is aimed squarely at you and roles at this depth are rare in India. The degree requirement is explicit.
Requirements. 2 to 5 years of experience in software engineering, forward deployed engineering, or a client facing technical delivery role in a B2B SaaS or AI product company. Prior experience with conversational AI platforms, contact centre technology or LLM based applications is highly preferred rather than required. What you would do. Own end to end client onboarding, from requirement gathering and solution design through platform configuration, UAT and production go-live. Conduct technical discovery sessions to map client needs. Design custom conversation flows and integration logic for clients. Develop proofs of concept and prototypes. Troubleshoot and resolve production issues across the stack. Build technical solutions to bridge gaps between the platform and client systems. The team, in its own words. The FDE team describes itself as the technical backbone of every client relationship, responsible for taking clients from signed contract to successful production deployment and beyond, when enterprises are trusting the voicebot to handle thousands of live customer conversations daily. The team works closely with Product, Infra, Business and Platform Engineering so field learnings shape the roadmap. Honest framing. This is a customer facing engineering role, not a pure backend seat. You will spend real time in discovery sessions and on client calls as well as writing code. The posting says directly that no two days look the same. If you want to be heads down in a codebase, this is not it. If you want to see your work land in a customer's operation, it is a good version of the job. Location and terms. Bangalore, marked on-site by Meesho, Full Time Employee, on the AI Services team inside Tech. Who this is for. An engineer two to five years in who is comfortable talking to enterprise clients and wants ownership early. This is one of only two roles in this edition with a floor below 3 years, so if you are early career and technically solid, it is a genuine opening rather than a stretch.
Requirements. 5+ years of experience in a client facing or technology focused role where business experience and technical acumen were combined. Experience managing and executing technical projects with a customer first attitude and a strong sense of empathy. Excellent project management and communication skills. Proven ability to quickly learn new technologies and understand complex systems, with SQL, databases, APIs and reporting tools named. Strong troubleshooting and problem solving skills with a continuous desire to improve your technical depth. Ability to collaborate cross functionally. Ability to work under pressure and to deadlines. What you would do. As a critical member of the Customer Success team, be responsible for the retention and expansion of the largest customers. Work with Sales on strategy for increasing adoption within large organisations. Deliver timely and organised onboarding through effective project management, make sure customers see full value in the products, and advise on technical best practice. Provide proactive technical guidance across all products. Work with Customer Support, Engineering and other teams on technical escalations. Surface use cases and problems to Engineering to push the product forward. ⭐ Remote, and verified. The board lists this as Remote (India) and nothing in the posting body imposes an office or hybrid requirement, which is why it is published as remote. That matters: it is the only genuinely remote role in this edition, and several employers today flagged roles as remote that turned out not to be. ⚠️ One oddity in the posting. It carries a United States E-Verify statement about verifying eligibility to work in the U.S. That is boilerplate inherited from Hightouch's US postings and sits oddly on a role explicitly described as the first Technical Account Manager hire in India covering APJ. Worth clarifying work authorisation expectations in the first call. Compensation note. The posting states meaningful equity in the form of ISO options, with early exercise and a 10 year post-termination exercise window. Who this is for. A technical person with five or more years who genuinely enjoys customers: this is account ownership, not engineering. Retention and expansion of accounts is stated as a responsibility, so there is a commercial dimension, though the requirement list carries no quota or pipeline language. Being the first hire in the region means scope and ambiguity in equal measure.
Requirements. 5+ years of professional experience, preferably in customer success management, relationship management, delivery management, consulting or enterprise delivery. 2+ years of experience in the software industry, preferably in SaaS companies. Prior hands-on experience in Linux. Experience in application security or cybersecurity is an advantage. What you would do. Focus on the customer's continuous interactions with JFrog, their lifetime value and the associated NPS and CSAT scores. Help customers create an adoption and rollout plan so they can socialise and embed the JFrog Platform confidently. Support the JFrog sales team by focusing on customer strategy so the platform helps customers meet their goals, which enables the sales account manager to be there for renewals and upsells. Formulate and deliver projects with customers to agreed timelines. Work with solution engineering and professional services so customer projects complete successfully. Monitor customer health and perception by becoming a platform health expert. Be the first point of escalation. Develop a full understanding of the JFrog platform. ⚠️ Read this before applying: it supports sales. The responsibilities explicitly include enabling the sales account manager to get renewals and upsells done on time. You do not carry a quota and the requirement list contains no selling experience, which is why this sits in the customer facing technical group rather than being excluded, but the commercial context is real and stated. Region and location. This requisition covers the EMEA region, and JFrog states elsewhere on its India postings that the job location is Bangalore (Bellandur) with a hybrid model of 3 mandatory office days per week. JFrog's separate North America seat publishes a 5:30pm to 2:30am IST shift; an EMEA region role would normally run afternoon into evening IST rather than overnight, but the shift is not stated on this posting. Ask in the first call, because it materially changes the job. Who this is for. Someone technical with five or more years who wants customer breadth. Linux hands-on is a stated requirement, so this is not a purely relationship role.
Requirements, and note there are two alternative routes. Either 5+ years of technical support and/or software development, OR 3+ years of solid experience in a business or technical analyst role for medium to large scale business software implementation projects. Strong analytical and problem solving skills. A self starter able to come up to speed on complex, difficult concepts with minimal assistance. The ability to context switch quickly between multiple complex work streams. An instinctive ability to break problems into components to pinpoint root cause. A customer obsessed attitude. A team player with solid collaboration skills. Responsibilities. Support and maintain customers who have implemented the Customer Identity SaaS solution, resolving technical and non-technical issues promptly. Operational management of support tickets. Build and maintain excellent client relationships and achieve high customer satisfaction. Take end to end ownership of customer issues including initial troubleshooting, root cause identification and resolution. Exceed customer expectations on response quality and timeliness. Serve as the internal and external point of contact on customer issues. Work as part of an extended support team in a startup atmosphere. Use business and technical analysis skills and knowledge of the development lifecycle to solve complex issues and promote best practice. Collaborate across departments. Contribute to and maintain a repository of product area knowledge and promote knowledge sharing within Support. Location. Bengaluru. Okta operates a flexible model where the role allows, so confirm office days. Who this is for. Someone with a support or development background who wants to work on a genuinely technical product with developer customers. The dual entry route is worth noting: the 3 year analyst path is a real alternative, so implementation consultants and technical analysts are explicitly in scope, not just support engineers. If you want to move from support toward engineering, identity is a domain that rewards depth, and Okta runs plenty of internal engineering roles.
Requirements. 6+ years of technical consulting or equivalent experience, bridging technical teams and senior business stakeholders. Industry experience in programming languages such as Python or JavaScript. What you would do. Embed deeply with the most strategic platform customers as the technical lead, serving as their technical thought partner to ideate and build novel applications on the API. Work with senior customer stakeholders to identify the best applications of GenAI in their industry and to build and qualify a comprehensive backlog supporting their AI roadmap. Intervene directly to accelerate customer time to value by building hands-on prototypes and delivering strategic guidance. Forge and manage relationships with customer leadership to ensure successful deployment and scale. Contribute to open source developer and enterprise resources. Scale the Solutions Architect function by sharing knowledge, codifying best practices and publishing notebooks to internal and external repositories. Reporting line and organisation. You report to the Head of Technical Success, APAC, and the posting places the role in the Go To Market organisation on the Technical Success team. You would collaborate with Sales, Solutions Engineering, Applied Research and Product. ⛔ Not remote, despite the flag. OpenAI's job board marks this posting as remote. The body says: "This role can be based in Delhi, Mumbai or Bangalore. We use a hybrid work model of 3 days in the office per week and offer relocation assistance to new employees." Three office days is not remote. This is the third consecutive edition in which an OpenAI posting has carried a false remote flag, so treat the flag as meaningless and the body as the truth. Relocation assistance is offered, which is worth knowing if you are moving for it. Who this is for. A solutions or consulting engineer with six or more years who is genuinely technical and genuinely comfortable with executives. The role is customer facing and sits in a go to market organisation, so it is not a research or core engineering seat. There is no quota or selling requirement in the list, which is why it qualifies for this group.
Requirements. 6 to 8+ years of extensive experience in a high level IT technical support, DevOps, systems engineering or Tier-3 escalation role handling enterprise software solutions, with higher level security and DevOps expertise. The role. Fastly is seeking a Tier III engineer for the Security Product Support (SPS) team. You are the definitive escalation point for the most complex, high stakes customer security issues, providing deep technical expertise across the full security suite: Next-Gen WAF (on-prem, edge and cloud), Bot Management, and product level DDoS protection. Operating as a technical multiplier, you bridge standard support operations and Product Engineering. The posting is explicit that you are expected to go beyond reactive troubleshooting: building internal tooling, driving automation, replicating complex customer environments and translating security challenges into product improvement. The team. Within Fastly's Customer Experience organisation, SPS is a specialised unit dedicated to the security portfolio, providing architectural level support and implementation guidance. The team describes itself as technical multipliers rather than a queue. Location and working model. Pune, India. Fastly's metadata lists the Work Location Type as Hybrid, and the posting states that Fastly "currently embraces a largely hybrid model for most roles which allows employees flexibility to split their time between the office and home". The department is Client Services. Who this is for. A support or DevOps engineer with six or more years who wants to go deep on web application security rather than broad across a product suite. WAF, bot management and DDoS are specific domains: if you have run them operationally, this posting is describing your work. The tooling and automation expectation means you should be comfortable writing code, not just diagnosing. It is customer facing escalation work, so incident pressure is part of the job, and the posting does not hide that.
Added August 2, 2026
Requirements as published: - 3+ years of experience. - Systems programming depth in one of C, C++, Python, Go or Java, with a track record of building robust, scalable software. - Practical low level knowledge in at least one of: distributed systems, operating system internals (Linux kernel), database internals, hypervisors, or container orchestration. - Ability to turn complex problems into clean designs while working inside a peer driven engineering team. The actual day to day: - Designing and implementing algorithms and data structures that deliver 99.9999 percent reliability for mission critical enterprise storage. - Owning features end to end, from concept and prototype through to production code. - Root causing deep technical bottlenecks across distributed systems and kernel level software. - Building the integration between FlashArray services and public cloud providers such as AWS, so customers can move traditional and cloud native workloads into a hybrid cloud setup. Location and office reality: - Bengaluru. Everpure states plainly that it is primarily an in office environment and you are expected to work from the Bengaluru office, except when on leave or travelling for work. Treat this as an onsite job, not hybrid. Honest fit guidance: - The 3 year bar is real and it is the lowest Everpure is advertising in India today, so this is the one to look at if you are early in a systems career. - You do not need storage experience specifically. The requirement is low level systems depth, and kernel, database or hypervisor work all count. - If your background is web or application development with no operating system or distributed systems exposure, this will be a hard interview. - Note the company name. Everpure is Pure Storage newly rebranded, so older search results, Glassdoor pages and employee reviews will be under the old name.
Requirements as published: - BS in Computer Science. - 4+ years designing, developing and testing enterprise products. Golang preferred. - Good understanding of microservice architectures and cloud native platforms. - Experience designing and owning microservices that operate and scale in a distributed architecture running to thousands of nodes. - Expert debugging skills, including navigating ambiguous problems at scale in public and private cloud environments. - Experience working with multiple internal and external stakeholders, from product management through to customer beta partners. - Solid computer science fundamentals in data structures, algorithms and software design. - Willingness to work in an open plan office environment, stated explicitly in the posting. The actual day to day: - Designing and building cloud native microservices and adding features to Portworx Enterprise. - Unit and functional testing, code review, documentation, and continuous integration and deployment. - Debugging product and performance issues in large scale clusters, using AI tooling. - Taking designs from first draft to production, then absorbing feedback from system testing and real customer deployments. Location and office reality: - Bengaluru, onsite. The posting carries the #LI-ONSITE tag and Everpure states it is primarily an in office environment. It also asks specifically that you be willing to work in an open office. Honest fit guidance: - Go is preferred rather than mandatory, but the whole Portworx stack is Go, so arriving without it means learning it fast. - Kubernetes knowledge is effectively assumed even though the posting does not spell it out, because Portworx is Kubernetes storage. - The emphasis on debugging at scale is unusually heavy for a 4 year role. Come with real war stories about diagnosing failures in a live cluster.
Requirements as published: - 6+ years of experience in cybersecurity or a related technical field. - 3+ years of hands on experience in incident response and detection. - Ability to design, implement and maintain high fidelity detections, correlation rules, alerts, dashboards and use cases in Splunk and related security platforms. - Working knowledge of frameworks including MITRE ATT and CK and CVE/CVSS, plus attacker tradecraft and risk context. - Python and API skills for building enrichment and automation workflows. The actual day to day: - Building detections across identity, endpoint, network, cloud infrastructure, SaaS, DLP, vulnerability and asset posture data. - Correlating signals from different tools to spot attacker behaviour, misuse and anomalous activity. - Sitting in incident triage, investigation and containment, then feeding the lessons back into detection content. - Tuning noisy alerts down, cutting false positives and raising true positive rates. - Working on logging strategy: event onboarding, normalisation, parsing, correlation, retention and reporting. - Writing playbooks, runbooks and detection documentation for the responders who use them. - Partnering with business units, IT and engineering to map how the business actually works to the telemetry needed to defend it. What the posting says you will help build: - High signal detections for credential misuse, privilege abuse, lateral movement, endpoint compromise, and cloud and SaaS attacks. Location and office reality: - Bangalore, onsite. The posting carries #LI-ONSITE and Everpure states it is primarily an in office environment. Honest fit guidance: - This is a detection engineering role, so a pure SOC analyst background of watching a queue will not be enough on its own. They want the person who writes the rules. - Splunk is the named platform. Experience in another SIEM transfers, but say so directly rather than letting them assume. - The posting explicitly rejects alert volume as a success measure, which is a good sign if you have been stuck in a noisy SOC.
Requirements as published: - 3+ years in a Cloud Operations or DevOps role. - 2+ years using Go, shell scripting and Terraform. - 2+ years as a software developer in a SaaS environment. - Understanding of microservices, cloud infrastructure (AWS, Azure), databases (SQL, NoSQL, key/value), containers (Docker, Kubernetes), web technologies (websockets, HTTP) and networking (SSL, routing, VPN). - Exceptional communication, including technical writing in English. - Knowledge of Datadog or another observability platform is desired rather than required. The actual day to day: - Owning and improving incident response processes with other teams. - Participating in a 24 by 7 on call rotation, which the posting says you handle independently. - Using existing monitoring to find problems and either resolve them or escalate to service teams. - Setting and hitting long term performance, reliability and scalability goals on a platform with an aggressive growth plan. - Automating to reduce toil for yourself and your teammates. Location and office reality: - Bengaluru. Office days are not stated. The posting does say the team works effectively in a remote environment where tasks may be self driven, but the role is listed at the Bengaluru site, so do not read that as a remote job. Honest fit guidance: - The on call rotation is 24 by 7 and it is in the requirements, not the small print. Decide about that before you apply. - At 3 years this is one of the lowest bars on any Senior titled role in this edition, which makes it worth a look even if the word Senior would normally put you off. - Ignore the board metadata showing zero years. It is a placeholder and the real requirement is in the body.
Requirements as published: - 7+ years of software engineering experience, with 3+ years building high scale, cloud native backend systems. - Demonstrated staff level (P4) behaviour: independently owning large tasks end to end, influencing technical decisions across a team, and raising the performance of the engineers around you. - Domain expertise in Privileged Access Management, Identity and Access Management, or deep networking infrastructure. Familiarity with credential management, asset discovery or agentless communication patterns. - Strong hands on Go, or deep expertise in C++, Rust or Java with a proven record of picking up Go quickly. - Hands on experience with networking protocols (SSH, Telnet, TCP/IP), database security, microservices and asynchronous event driven systems. - Familiarity with AWS, Kubernetes, Docker, CI/CD automation and modern telemetry and observability tooling. - What the posting calls a multiplier mindset: high empathy and humility. The actual day to day: - Building secure database and network device connectors, covering routers, switches and firewalls, on the Zero Standing Privileges platform. - Hands on architecture and high velocity coding, with end to end execution. - Acting as a technical multiplier for mid level developers in the pod, working with the local technical team lead. - Keeping architecture aligned with the global team. Location and office reality: - Bengaluru. Office days are not stated in the posting. Honest fit guidance: - This is explicitly an individual contributor role, and the posting says so, so the team lead sits beside you rather than being a path you have to take. - The pod is newly established, which means more influence over how things are built and less existing structure to lean on. - Go is strongly preferred but the posting deliberately leaves the door open for strong C++, Rust or Java engineers. Say directly that you will pick up Go.
Requirements as published: - 8 to 12 years of hands on experience in JavaScript, Node.js, Go and React or Next.js. - Experience designing, building and operating distributed systems in a cloud environment such as AWS or Azure. - Backend: strong service design in Node.js (stated as mandatory) or Go. Deep hands on experience deploying, scaling and operating backend services on AWS, with strong Kubernetes proficiency. - Data and caching: strong experience with PostgreSQL, distributed caching with Redis, and data and deployment pipelines. - Performance and scale: using quantitative analysis of latency and traffic volume to justify design and technology choices. - Strong production experience covering monitoring, debugging and incident response. - Frontend: hands on with modern React and MobX or Redux, plus frontend build tools, module bundlers and package managers. The actual day to day: - Owning technical strategy and architecture for the Auth0 Manage Dashboard and the Auth0 Marketplace. - Designing developer friendly APIs and resilient frameworks across the stack. - Mentoring a team of engineers, framed in the posting as technical mentorship rather than people management. - Leading the technical lifecycle of product areas end to end. Location and office reality: - Bengaluru. Office days are not stated in the posting. Honest fit guidance: - Node.js is called mandatory. If your backend is Java or Python only, this is a real gap rather than a nice to have. - The role is genuinely full stack. Both halves are examined, so a strong frontend with a thin backend will not clear the bar, or the reverse. - Marketplace work means designing for third party developers, which is a different discipline from internal APIs. Bring examples if you have them.
Requirements as published: - 3+ years in Site Reliability Engineering or similar roles supporting production environments. - Expertise in infrastructure as code tools: Pulumi, Terraform, CloudFormation or equivalent. - Deep familiarity with observability tools such as Datadog and Sentry, and incident response practice using PagerDuty or Incident.io. - Proficiency with cloud infrastructure platforms including Azure, GCP or AWS. - Strong programming skills in Python, Bash, Go or a similar language. - A track record of diagnosing complex system problems and shipping durable fixes. - Solid understanding of CI/CD, Kubernetes, containerisation, networking, databases and cloud security principles. - Work eligibility: the posting states you must be authorised to work in India and that visa sponsorship is not available. The actual day to day: - Designing, implementing and managing monitoring, alerting and infrastructure resources. - Keeping a platform that spans more than 50 regions fast, secure and available. - Automating mission critical operations to reduce complexity as the company scales. - Working at the boundary between infrastructure and product. Location and office reality: - Bengaluru. Harvey's own job board marks this posting as remote, but the role sits with the Bengaluru team and two sibling postings on the same board state directly that the role is based in Bengaluru. We have published it at the real location. Confirm the working model in your first call. Honest fit guidance: - At 3 years this is the most accessible role on Harvey's India board, and SRE at a company scaling this fast is unusually good experience. - Azure is the preferred cloud, which is less common than AWS, so say clearly if your background is AWS and you are willing to switch. - The India work authorisation requirement is explicit, so there is no sponsorship route here.
Requirements as published: - 5+ years of backend engineering experience building and operating production web applications or SaaS products. The actual day to day: - Designing and owning backend services and APIs that power Harvey's web applications, workflows and integrations. - Modelling and managing data in Postgres and related stores to support low latency, reliable experiences. - Building secure, multi tenant, permissions aware systems with auditing appropriate to enterprise and government customers. - Implementing backend features and workflows that use LLMs and agentic tools, orchestrating calls to Harvey's AI systems from robust services. - Working with frontend, product and design partners to shape solutions and define clear API contracts. - Collaborating closely with product to prioritise customer focused work and deliver reliable features quickly. Location and office reality: - Bengaluru. Harvey's job board marks the posting as remote, but this is a Bengaluru team role and sibling postings on the same board state the role is based in Bengaluru. Published at the real location. Confirm before you assume remote. Honest fit guidance: - You do not need prior LLM experience. The requirement is backend depth, and the AI orchestration is something you learn on the job. - Enterprise and government customers mean multi tenancy, permissions and audit are first class concerns, not afterthoughts. Interviews are likely to go there. - Harvey states its values as decisiveness, simplicity and job's not finished, and describes an intense pace. Take that at face value when deciding.
Requirements as published: - 6+ years in Infrastructure Engineering or Platform Engineering in a production environment. - A long track record building and scaling complex, large scale distributed systems. - Deep proficiency with cloud infrastructure platforms. Azure is preferred, and the posting says GCP or AWS experience transfers well. - Strong fluency in infrastructure as code: Terraform, Pulumi or CloudFormation. - Solid understanding of Kubernetes, container orchestration, networking and cloud security at scale. - Experience with observability tools such as Datadog and Sentry, and incident response practice with PagerDuty or Incident.io. - Strong programming skills in Python, Go or similar. The actual day to day: - Architecting multi region deployment strategies that meet strict data residency requirements for global enterprise customers. - Building observability infrastructure with granular SLA monitoring, burn rate alerts and detailed token attribution for cost tracking. - Leading the evolution of CI and CD pipelines to improve developer velocity while holding production stable. - Balancing new system building against operational excellence on infrastructure processing billions of prompt tokens and millions of daily requests. Location and office reality: - Bengaluru. As with Harvey's other India postings, the board flags remote while the role sits with the Bengaluru team. Published at the real location. Honest fit guidance: - Data residency across regions is a genuinely hard problem and it is named first in the responsibilities. If you have done it, lead with it. - Token attribution for cost tracking is an AI era infrastructure skill that barely existed three years ago. Nobody expects a long history in it, but show you understand why it matters. - Azure preferred again, same as the SRE role. Be explicit if you are coming from AWS.
Requirements as published: - 5 to 8 years of professional experience in software or data engineering, focused on distributed data systems. - Strong programming in Java, Scala or Python, and expertise in SQL. - At least 2 years hands on with big data systems including Apache Kafka, Apache Spark, EMR or Dataproc, Hive, Delta Lake, Presto or Trino, Airflow, and data lineage tools such as DataHub, Marquez or OpenLineage. - Experience implementing and tuning Spark, Delta Lake and Presto at terabyte scale or beyond. - Strong understanding of Apache Spark internals (Catalyst, Tungsten, shuffle) with experience customising or contributing to open source code. - Familiarity with a modern open source and cloud native data stack: Apache Iceberg, Hudi or Delta Lake; Trino, Presto, DuckDB, ClickHouse, Pinot or Druid; Airflow, Dagster or Prefect; dbt, Great Expectations, DataHub or OpenMetadata; Kubernetes, Terraform and Docker. - Strong analytical and debugging skills for complex issues in large scale systems. The actual day to day: - Building and running data infrastructure for a platform handling millions of orders daily. - Working inside a pod aligned to a business theme, contributing to solution design rather than only implementation. - The posting says engineers are expected to challenge existing solutions, not just build to spec. Location and office reality: - Bangalore. Office days are not stated in the posting. Honest fit guidance: - The Spark internals requirement is the real filter. Many candidates have used Spark; far fewer can talk about Catalyst and shuffle behaviour credibly. - Meesho describes a culture that values speed over perfection and logical debate over authority. That suits some people and not others, and it is worth taking literally. - The scale numbers in the posting are unusually concrete for an Indian ecommerce role, which makes this a good one for a CV if you want volume experience.
Requirements as published: - Bachelor's or Master's degree in computer science or a similar field. - 4 to 7 years of experience as a Data Scientist in a fast paced organisation, preferably business to consumer. - Familiarity with neural networks and machine learning. - Familiarity with tools such as SQL, R and Python. - Strong understanding of statistics and linear algebra. - Strong understanding of hypothesis and model testing, including the ability to identify common model testing errors. - Experience designing and running A and B tests and drawing insight from them. - Proficiency in machine learning algorithms. - Strong analytical skills for sourcing data reliably. Nice to have, as listed: - Experience with personalisation or similar machine learning problems. - Familiarity with big data stacks such as Apache Spark, Hadoop and Redshift. - Experience working in tech and product teams. The actual day to day: - Developing models and running experiments to draw insight from data. - Improving product usability and identifying growth opportunities. - Modelling seasonal demand to predict key organisational metrics. - Designing discount programmes to help resellers sell more. - Understanding reseller preferences to surface the most relevant products. - Mentoring junior data scientists on the team. Location and office reality: - Bangalore. Office days are not stated in the posting. Honest fit guidance: - The mentoring line is mentorship, not people management, so this stays on the individual contributor track. - The problems are commercial: pricing, discounting, fraud and demand. If you want research, this is not it. - Business to consumer experience is stated as a preference rather than a requirement, but the whole role is shaped around consumer marketplace behaviour.
Requirements as published: - 15+ years of production level experience in one of Rust, Java, Scala, C++ or a similar language. - 10+ years of experience developing large scale distributed systems. - Deep networking expertise, which the posting names as the core requirement for the role. The actual day to day: - Owning and driving the design of large scale connectivity platforms that form the backbone between the Databricks control plane and compute plane. - Defining technical vision and architecture for next generation network connectivity and observability services managing millions of virtual machines across multiple clouds. - Operating at org wide level: setting technical direction, leading complex cross team initiatives and mentoring senior engineers. - Working with product management, operations and partner engineering to turn long term business goals into durable networking systems. - Improving the scalability, reliability and efficiency of compute infrastructure, and enabling more cost effective use of cloud resources. Location and office reality: - Bengaluru. The posting notes you would be one of the early members of a rapidly growing Bangalore site, which usually means more influence and less established process. Honest fit guidance: - The 15 year figure is real and it is the highest bar in this edition. Do not apply on the basis of the Senior Staff title alone. - The posting asks for both hands on technical leadership and cross team influence, so this is not a role where you can stay purely in the code. - Databricks uses Staff and Senior Staff titles for much more senior work than many companies do. Its Staff roles in earlier editions have asked for 10 to 15 years while other employers use the same word at 5.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the experience field empty rather than guess, which means this role will not appear when you filter the board by years. - The IR specialist: knowledge of Lucene or Elasticsearch, embeddings and ranking algorithms. - The quality and metrics obsessive: experience building evaluation frameworks, both human in the loop and LLM based, and comfort with relevance metrics such as nDCG, MRR and Precision at K. - The bridge builder: willingness to apply traditional information retrieval practice to retrieval augmented generation. The actual day to day: - Owning result quality for two different users: the AI agent that needs ground truth context, and the human who needs an intuitive, high recall search experience. - Hybrid retrieval work, balancing keyword based search for exactness against semantic vector search for intent. - Dual optimisation of ranking models that have to satisfy human readability and LLM ready context at the same time. - Building the guardrails and relevance scoring that keep agent output grounded, because poor search quality shows up as hallucination. - Connecting structured SQL tables, unstructured documents and real time business metrics. Location and office reality: - Bengaluru. Office days are not stated in the posting. Honest fit guidance: - The Senior Staff title at Databricks has historically meant 10 years or more, and its Network Platform posting in this same edition asks for 15. Since no figure is published here, assume the bar is high and read the title in Databricks terms rather than the industry average. - This is a classical information retrieval role wearing an AI badge. The nDCG and MRR requirements are the giveaway. If your search experience is real, that is what counts. - If you filter job boards by years, note that this role has no published figure, which is why it sits outside the experience filter here.
Requirements as published: - 6+ years of experience designing and building complex, high traffic user interfaces. - Experience with unit and end to end testing frameworks. - Bundling and build tools, and CI/CD pipelines for frontend deployments. - A proven record of translating complex requirements into shipped interfaces. The actual day to day: - Leading development of the user facing monetization platform, driving UI architecture and product innovation in the monetization experience. - Building admin interfaces that let sales, finance and support teams manage custom contracts, discounts and user subscriptions without engineering involvement. - Working on billing systems that handle payments and renewals, subscription lifecycle, sales tax and compliance, revenue systems and post purchase onboarding. - Cross functional collaboration, since monetization touches sales, finance and support as well as product. Location and office reality: - Bengaluru, where Postman was founded. ⚠️ The posting states that for roles based in Bangalore, employees currently work in the office three days a week and will transition to five days per week by the end of the year. That is a change worth knowing before you accept, and Postman puts it in writing. Honest fit guidance: - Billing and monetization is unglamorous and technically harder than it looks. Tax, proration and compliance edge cases are where the difficulty lives. - The role is described as leading development, but it is an engineering seat rather than a management one. - The office policy moving from three days to five within the year is the single most important detail here if you have been planning around hybrid.
Requirements as published: - 6+ years of experience with deep backend expertise in search and ETL systems, plus a strong product mindset. - 6+ years building applications in high level programming languages. - Experience across high performance web services, high volume data pipelines, machine learning and relevance tuning. The actual day to day: - Owning end to end architecture and roadmap of the search platform: distributed indexing pipelines, storage infrastructure and high performance web servers. - Leading core initiatives on the search platform rather than implementing a defined spec. - Mentoring engineers on the team and upholding quality through code review. - Improving discovery and ease of consumption over a fast growing volume of user created API data. Location and office reality: - Bengaluru. ⚠️ Same office policy as Postman's other Bangalore roles: three days a week in the office currently, moving to five days per week by the end of the year, stated in the posting. Honest fit guidance: - Search and ETL are named together for a reason. The indexing pipeline is as much of the job as query time relevance, so pure query side experience is only half. - The product mindset requirement is genuine. Search quality at Postman is judged by whether developers find the right API, which is a product question as much as a technical one. - Postman runs several senior Bangalore roles at once. This one and the Monetization frontend seat are both in this edition and they are very different jobs, so pick deliberately.
Requirements as published: - 8+ years of progressive experience in technology, with at least 5 years in a hands on senior role such as Site Reliability Engineering, DevOps or Security Engineering. - Ability to design, build, maintain and improve secure, scalable and highly available infrastructure. - Automation as the default approach rather than repeated manual fixes, which the posting calls out directly. The actual day to day: - Engineering secure and resilient infrastructure for a service that has to be available to customers 24 by 7. - Maturing both the security and the reliability posture of the production environment by treating each as a software engineering problem. - Working at the intersection of infrastructure, automation and security to build a platform that is resilient and secure by design. Location and office reality: - Bangalore, hybrid. The hybrid arrangement is stated in the job title itself. Specific office days are not published, so ask. Honest fit guidance: - This role wants both halves. An SRE with no security depth, or a security engineer who has never run production infrastructure, will find one side of the interview hard. - The posting is written as a leadership role in the sense of technical maturity, not people management, so it stays on the individual contributor track. - Smartsheet has a second, similar Bangalore role in this edition on the Corporate Systems side. That one is business systems focused. This one is product production infrastructure, and they are not interchangeable.
Requirements as published: - 7+ years of experience in DevOps or System Engineering roles. - Experience building and scaling CI/CD pipelines, infrastructure automation, monitoring frameworks and deployment processes. - Ability to work across a variety of systems and platforms. The actual day to day: - Building and scaling the CI and CD pipelines behind mission critical integrations across Finance, People, Sales, Legal, IT and Engineering systems. - Infrastructure automation and monitoring frameworks for those integrations. - Deployment process work across a varied estate rather than a single product stack. Location and office reality: - Bangalore. The posting metadata lists the working location as Field, India. Office days are not stated, so ask early. Honest fit guidance: - Be clear eyed that this is internal corporate systems engineering, not product infrastructure. The work is real automation engineering, and it is genuinely broad, but the customers are internal teams. - If you want your next role to be about product scale and customer facing reliability, Smartsheet's DevSecOps seat in this same edition is the closer match. - Breadth across Finance, People, Sales and Legal systems is unusual and it builds a rare kind of integration knowledge, which is valuable if you later move toward platform or internal tooling leadership.
Requirements as published: - At least 10 years of experience in a technology discipline, preferably with 6+ years in the cyber security domain. - Working protocol level understanding of encryption at rest and in motion: TLS and SSL, BCrypt, PKI, SHA1, AES and similar, plus key management principles. - Proven experience collaborating with sales, legal and engineering teams. - Familiarity with assurance frameworks and questionnaires including SIG and CAIQ. - Exceptional communication, critical thinking and a strong bias for ownership and learning. The actual day to day: - Owning all activity aimed at building trust and confidence in Druva's data security, privacy and compliance posture with prospects and customers. - Running Druva's third party risk management programme. - Driving improvement in Druva's internal security culture, specifically phishing simulation and security awareness work. Location and office reality: - Pune. Office days are not stated in the posting. Honest fit guidance: - This is a customer facing security role, so if you want to be heads down building detections or breaking things, look elsewhere. Druva has separate engineering security roles. - The collaboration with sales is named in the requirements, which tells you assurance work here supports deals. That is normal for the discipline, and there is no quota attached. - The encryption depth requested is at protocol level, not conceptual. Expect to be asked how TLS actually works rather than what it is for.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the field empty rather than invent one, so this role does not appear when you filter the board by years. - Strong expertise in Windows and Linux, file systems and operating system level concepts. - Strong engineering fundamentals and deep automation capability. - A genuine interest in quality in distributed, cloud based systems. The actual day to day: - Working with the development team in an Agile environment to understand functional specifications and design requirements. - Independently creating comprehensive feature test plans aligned to development milestones. - Using and extending existing automation frameworks, adding library support for new functionality. - Owning the complete test execution cycle for user stories. - A mix of automated, manual, white box and black box testing. - Creating, maintaining and documenting testbed setups and environments. - Reporting and tracking issues and test cases, and working across teams to hold quality benchmarks through the lifecycle. Location and office reality: - Pune. Office days are not stated in the posting. Honest fit guidance: - The Senior Staff title with no published years is a genuine unknown. Druva's other role in this edition asks for 10 years, so read the title accordingly, but ask about levelling early. - Backup and archival testing is systems testing. File system and operating system knowledge matters more here than web test automation experience. - White box testing is explicitly in the list, so expect to read and reason about product code rather than only exercise it from outside.
Requirements as published: - 6+ years of software engineering experience with a focus on security. - Ability to design, build, implement and maintain scalable automation tools and pipelines for application security, covering static (SAST), dynamic (DAST) and software composition analysis (SCA) scanning. - Familiarity with tooling such as OWASP ZAP, Snyk and WhiteSource. - Familiarity with CI/CD pipelines such as Jenkins, GitHub Actions and GitLab CI, and with infrastructure as code. - Ability to advise other engineers on secure coding and secure development lifecycle practice. The actual day to day: - Building and maintaining the application security automation estate. - Working with developers, security engineers and DevOps teams to fold security automation into CI and CD workflows rather than bolting it on. - Finding opportunities to automate work that is currently manual. - Coaching engineers on secure coding practice. Location and office reality: - Bangalore. The posting metadata states Remote Position: No, so treat this as an onsite or hybrid role and confirm the days. Honest fit guidance: - This is an engineering role that happens to be in security, not an analyst role. The requirement is 6 years of software engineering, and you will be judged on the code you write. - If your appsec experience is running scans and triaging output, the automation and pipeline building here is a step up rather than a sideways move. - Commvault includes a recruitment fraud warning in its postings: it says it does not conduct interviews by email or text and will never ask for banking details or identification documents before your first day. Worth knowing given how common job scams are in this market.
Requirements as published: - Bachelor's degree in Computer Science, Electrical Engineering, another technical degree, or equivalent experience. - 5 to 8 years of experience in technical support or system administration and operations, with a preference for storage, backup or infrastructure experience. - Ability to architect Commvault software solutions against customer requirements. - Comfort with incident management and with meeting contractual delivery obligations. The actual day to day: - Direct interaction with customers and their environments, providing day to day operational management of the customer's Commvault deployment. - Incident, problem and change work on production backup and recovery systems. - Working remotely into enterprise level customer environments and dark sites, which the posting names specifically. - Maintaining awareness of the customer base and making sure delivery meets what was contracted. - Raising improvements to standard operating procedures with team leadership. - Staying current with new releases, updates and changes to the product. Location and office reality: - Bangalore. The posting metadata states Remote Position: No. Note that working remotely into customer systems is part of the job, which is different from the role itself being remote. Honest fit guidance: - This is operations and support rather than product engineering, and it says so honestly. If that is what you want, it is a strong version of it, with enterprise scale and real ownership. - Prior Commvault experience is not stated as mandatory, but backup and storage background clearly is the preferred route in. - Dark sites means air gapped or restricted environments. Expect process discipline and change control to matter as much as technical skill.
Requirements as published: - 8 to 12 years of software engineering experience with a track record of shaping how an organisation builds software. - Depth sufficient to set technical direction across multiple services and teams. - Experience leading complex, cross cutting initiatives such as migrations, modernisation and platform work. - Design judgement that other engineers adopt, which is how the posting frames the seniority bar. The actual day to day: - Driving architecture and technical direction across multiple services and teams. - Leading complex, cross cutting initiatives including migrations and modernisation. - Raising engineering standards and mentoring senior engineers. - Operating as a senior individual contributor rather than a manager. Location and office reality: - ⚠️ Read this carefully. Turing's job board lists the role as India Remote. The posting body states: Location: Bangalore, India, In-office, Hybrid. We have published Bangalore because the body is the more specific statement, but confirm it in your first conversation before making any plans that depend on remote work. - The body also calls the role Staff Engineer while the board title reads Software Engineer. Honest fit guidance: - If you are applying because the board said remote, stop and check. This is the second time we have found a Turing posting where the board and the body disagree about location. - The role is a genuine individual contributor track, so it does not push you into management. - Turing's work spans frontier AI research support and enterprise AI systems. Ask which side this seat sits on, because they are quite different day to day.
Requirements as published: - BS or MS degree. - 8 to 11 years of experience in the security domain. - Strong hands on automation skills. - Experience securing cloud products and working with security tooling. The actual day to day: - Running and improving key security engineering and security operations capabilities. - Vulnerability management, named first in the responsibilities. - Security automation, playbooks and operational readiness. Location and office reality: - India. The posting does not name a city, and Yugabyte describes its team as distributed across more than 12 countries and multiple time zones. Ask about location expectations and about overlap hours with other regions. Honest fit guidance: - This is product and cloud security at a database company, so database and distributed systems familiarity helps even though it is not in the requirement list. - The distributed team across 12 countries usually means some meetings outside Indian working hours. The posting does not state a shift, so ask. - Yugabyte in this edition uses Staff for an 8 to 11 year role. Databricks in the same edition uses Senior Staff for 15 years. Titles are a local convention, not a level, which is why we publish the years the posting actually asks for.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the field empty rather than guess, so this role does not appear when you filter the board by years. - Strong technical and problem solving skills with recent hands on software development experience. - Experience with reliable distributed systems, with an emphasis on high volume data management in enterprise or web scale products operating under strict SLAs. - Broad technical knowledge spanning software development and automation. - Experience with a wide array of algorithms and data structures. - Expertise in Java, AWS, cloud based APIs, databases, and software design and programming best practice. Technologies named in the posting: - Java, SQL, Kubernetes, Docker, AWS, GCP, CircleCI. The actual day to day: - Working on the core data pipeline that moves terabytes of data from customers into their data warehouses. - Processing that data into clean, incremental, automated updates. - Working with cloud APIs, SQL and NoSQL databases and event systems. - Ensuring technical quality for your team and owned services through code contribution, code review and architectural design. - Mentoring more junior colleagues. Location and office reality: - Bengaluru. The posting states this is a full time position based out of the Bangalore office, on a hybrid model with two days a week in the office to collaborate as a team. That is unusually specific and clearer than most postings in this edition. Honest fit guidance: - The Senior title with no published years is a gap. Given the requirement for a track record with strict SLA systems, assume mid to senior rather than early career, and ask about levelling. - Fivetran is merging with dbt Labs and its postings warn you will encounter both brands in the process. That is disclosed rather than hidden, and it is not a red flag, just something to expect. - Two office days a week is one of the lighter hybrid requirements in this edition.
Requirements as published: - 8+ years of experience in a relevant field, and the posting states this must be from product based companies only. - Strong experience with microservice architecture. - Ability to lead technical architecture discussions and help drive technical direction. - Technical credibility to lead teams of software engineers, framed as technical leadership rather than people management. - JavaScript and Node.js experience is described as a huge plus rather than mandatory. Celigo says strong developers from other stacks looking to try something new are also welcome to apply. The actual day to day: - Designing and shipping turnkey business applications for users of cloud systems including NetSuite, Salesforce, Google, Amazon and Magento. - Working on business cloud computing (SaaS) integration problems. Location and office reality: - Hyderabad, hybrid. The posting states Location: Hyderabad, India (Hybrid) directly. Specific office days are not given. Honest fit guidance: - The product companies only requirement is unusual and it is explicit, so if your 8 years are from services or consulting firms, expect that to be a real filter. - The open invitation to developers outside the JavaScript and Node.js world is genuine and worth taking up if you have strong fundamentals in another language. - Integration work means other people's APIs, rate limits and data models. It is less glamorous than greenfield product work and considerably harder to do well.
Requirements as published: - 12+ years of professional experience, preferably in customer success management, relationship management, delivery management, consulting or enterprise delivery. - 3+ years of experience in the software industry, preferably at SaaS companies. - Prior hands on experience in Linux. - Command line hands on experience. - REST API experience is described as an advantage. - Docker and Kubernetes experience is good to have. - Ability to liaise with customers and regional teams, and to present technical material effectively. - Flexibility in working hours to accommodate a global presence. The actual day to day: - Owning the customer's continuous interaction with JFrog, their lifetime value and the associated NPS and CSAT scores. - Helping customers build an adoption and rollout plan so the JFrog Platform actually gets embedded. - Acting as the first point of escalation and becoming a platform health expert for your accounts. - Delivering projects with customers to agreed timelines, working with solution engineering and professional services. - Supporting the JFrog sales team on customer strategy so renewals and upsells happen on time. Shift and office reality, stated in the posting: - ⚠️ Working hours are 5:30pm to 2:30am IST. This is a North America region role and the shift is not negotiable in the posting. - Location is Bangalore (Bellandur) on a hybrid model with three mandatory days a week in the office. - JFrog states it provides office transport and a shift allowance. Honest fit guidance: - The night shift is the single biggest factor here. It is a good technical customer role, and it will reshape your day entirely. - There is no people management in this role despite the title, so it does not move you off the individual contributor track. - The technical bar is moderate: Linux, CLI and REST APIs, with containers as a bonus. This is a relationship and adoption role with real technical grounding, not a deep engineering seat.
Requirements as published: - 8+ years of post sales engineering or solutions architecture experience, working directly with customers. - 2+ years of software engineering experience and a strong understanding of the software development lifecycle. - Existing power user of AI coding tools, stated as a genuine expectation rather than a preference. The actual day to day: - Serving as the primary technical subject matter expert on OpenAI Codex for a portfolio of customers, embedding deeply to enable their engineering teams. - Partnering with engineering leaders and hands on builders to design, validate and scale advanced AI workflows. - Using Codex to prototype and build the demos, integrations and automations customers ultimately adopt. - Working across Sales, Solutions Engineering, Product, Applied Engineering and the wider Codex organisation to advocate for customer needs and shape product direction. Location and office reality: - ⚠️ OpenAI's job board marks this posting as remote and lists it under Delhi, India. The posting body states directly: This role is based in Bangalore. We have published Bangalore because the body is the more specific statement. Confirm before making plans. - OpenAI's other India postings state a hybrid model of three days a week in the office, so expect something similar here and ask. Honest fit guidance: - This is a customer facing role and the posting says so throughout. It is not a Codex engineering seat. - The 8 year requirement is for post sales or solutions architecture experience specifically, and the software engineering requirement is only 2 years. That combination is unusual, and it means deep customer facing history matters more here than deep coding history. - We kept this role and dropped OpenAI's Solutions Engineer posting from the same board, because that one is pre sales throughout while this one is technical deployment work with no quota language.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the field empty rather than guess, which means this role does not appear when you filter the board by years. - Creativity, problem solving and technical expertise sufficient to design tailored customer solutions. - Willingness to work embedded with strategic customers. The actual day to day: - Embedding with ElevenLabs' most strategic customers and building tailored solutions on the platform. - Working across the ElevenAgents, ElevenCreative and ElevenAPI product surfaces, which cover voice and chat agents, creative generation across 70 plus languages, and the developer API. Location and working model: - ⭐ Remote. The posting states: This role is remote, so it can be executed globally. ElevenLabs also says it prioritises talent, not location, and offers a monthly co working stipend if you are not near one of its hubs. - We checked this against the posting body rather than trusting the board's remote flag, because three postings in our last edition claimed remote and were not. This one holds up. What the company states about how it works: - High velocity: rapid experimentation, lean autonomous teams, minimal bureaucracy. - No job titles internally. Seniority is framed as impact rather than level. - An AI first expectation: the company says it uses AI across engineering, growth and operations. - Annual company offsite, plus a discretionary stipend to meet colleagues during the year. Honest fit guidance: - Forward Deployed Engineer means customer facing engineering. You write code, and you do it next to a customer with their deadlines in play. If you want to be left alone with a backlog, this is not that. - The absence of any published experience figure cuts both ways. It leaves the door open, and it also means you cannot tell whether you are under the bar until you talk to them. Applying is cheap here. - No job titles sounds appealing and it does make levelling and future job hunting harder to describe on a CV. Worth asking how they handle that.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the field empty rather than guess, which means this role does not appear when you filter the board by years. Note: the posting does contain the phrase 50,000 years of audio, but that is a company statistic about data processed, not an experience requirement. - Based in an APAC time zone with reliable overlap to customer business hours across East Asia, Southeast Asia and Australia and New Zealand. - An AI first way of working, which Deepgram states is not optional: it expects every team member to actively use and experiment with advanced AI tools and to build their own into daily work, and it measures how effectively AI is applied. The actual day to day: - Leading architecture and implementation for enterprise deployments using Deepgram speech to text, text to speech and voice agent capabilities. - Owning post sales technical success for assigned accounts: unblocking integrations, optimising accuracy and latency, and guiding customers to stable production. - Acting as the Tier 3 escalation point for complex issues, driving root cause analysis and writing durable fixes or automation. - Designing reference architectures for common APAC use cases including contact centres, voice analytics, quality assurance and AI agents. - Building samples, internal tools and scripts that make repeatable work easier for customers and the team. - Contributing to pre sales discovery and proofs of concept when deep technical direction is needed. - Partnering with Product and Engineering to prioritise fixes and features. Location and working model: - ⭐ Remote. The posting states: this role is based out of India and will service the APAC region, and separately: Remote across APAC with periodic regional meetups. Verified against the posting body rather than the board's remote flag. - ⚠️ The role services East Asia, Southeast Asia and Australia and New Zealand, and asks for reliable overlap with those business hours. That is a real constraint on your working day even though no fixed shift is stated. Honest fit guidance: - Deepgram's Applied Engineering function deliberately combines what other companies split across solutions engineering, solutions architecture, consulting and senior technical support. Expect breadth. - The AI first expectation is stated more forcefully than at most companies, including that performance is measured on it. Take it literally. - The posting warns the work changes fast and says this may not be the right role if you want something highly prescriptive or a traditional nine to five. That is honest, and worth believing.
Added August 1, 2026
What the posting asks for: - 6 months to 1 year of relevant work experience. This is the stated bar and it is genuinely junior. - SRE experience with large production environments. - Natural curiosity, close attention to detail and strong troubleshooting instincts. - Ability to analyse a complex system and then explain it in simple terms. - The team works in Go, Java, Python, C++ and Linux. The posting asks which of those you use rather than demanding all of them. What the job actually involves day to day: - Leading investigations into emerging customer issues and engineering the fix. - Building services and AI tooling that diagnose and protect the installed fleet. - Designing analytics that monitor fleet health and flag problems before customers hit them. - Working across most of the engineering organisation, which the posting frames as a fast route to learning the whole codebase and building an internal network. - Representing customer problems back to engineering peers, and sometimes representing engineering in front of customers. - Taking part in an on call rotation that responds to outages worldwide. Location and office reality: Bangalore. Everpure states across its postings that it is primarily an in office environment and expects attendance at the Bangalore office outside leave and work travel. Honest fit guidance: the years bar is low but the work is not easy, and on call is part of it from the start. If you want a first or second job where you are handed hard debugging problems on real production systems, apply. If you are looking for a role with no customer contact and no pager, this is not that role.
What the posting asks for: - 3+ years of systems programming experience, with real depth in C, C++, Python, Go or Java and a track record of shipping robust, scalable software. - Practical low level knowledge in at least one of: distributed systems, operating system internals (specifically the Linux kernel), database internals, hypervisors, or container orchestration. - The ability to turn a complex problem into a clean design, working inside a peer review heavy engineering team. What you would work on: - Designing and implementing high availability algorithms and data structures targeting 99.9999 percent reliability for enterprise storage. - Owning features end to end, from prototype through to production code. - Diagnosing deep technical bottlenecks in distributed systems and kernel level software. - Integrating FlashArray services with public cloud providers so customers can run hybrid cloud workloads. Location and office reality: Bengaluru. The posting states plainly that Everpure is primarily an in office environment and that you are expected to work from the Bengaluru office except when on leave or travelling for work. Treat this as a five day in office role unless the recruiter tells you otherwise. Honest fit guidance: three years is the floor, not the target, and the low level requirement is real. If your experience is entirely web or application development with no exposure to operating systems, storage or distributed infrastructure, expect the interview to go into territory you have not covered.
Core requirements: - Bachelor's degree in computer science or a related technical field, or equivalent practical experience. - 4+ years of professional experience designing, developing and testing product components in Go, Java or C++. - Strong grounding in microservices architecture, distributed systems, and building production grade platforms in the cloud. - Solid computer science fundamentals: data structures, algorithms and software design. - A collaborative working style. The posting emphasises open, team oriented development. Preferred, described by the employer as what gives you a head start: - Hands on Kubernetes and container experience. Prior Kubernetes control plane development is called a major plus. - Building and integrating authentication (SSO, LDAP) and authorization (RBAC, OAuth) frameworks. - Familiarity with e-commerce marketplace integration projects. - Automating SaaS billing, usage reporting, or building telemetry systems that pull insight out of production services. - Prior experience building public facing SDKs. Day to day: building and scaling SaaS microservices inside the Portworx product line, owning the full engineering lifecycle including CI/CD, partnering with product management and early adopter customers, and experimenting with new technology to optimise the cloud infrastructure underneath. Location and office reality: Bangalore. The posting states the team works in office and that you will be based out of the Bangalore office outside approved leave or work travel. Honest fit guidance: the Kubernetes items are genuinely optional, so do not screen yourself out for lacking them if your Go or Java backend and distributed systems work is strong. The four year bar is a floor.
What the posting asks for: - 4 to 7+ years developing on Linux or another UNIX variant at a product company. - 3+ years working with remote teams at a product company. - Bachelor's degree or higher in computer science, computer engineering or electrical engineering. - Significant domain knowledge of the networking stack. - Systems development experience covering IPv4 and IPv6 networking protocols, API design, distributed systems and/or device drivers. - Familiarity with modern switch silicon packet processing and features such as ECMP, QoS and packet filtering. - Hands on experience with the Broadcom SDK. - Linux kernel or device driver experience. - Strong problem solving, debugging, algorithmic and coding skills. Explicitly NOT required: - Storage experience. The posting says it is desirable but not necessary. That is unusual for a storage company and it is the reason a pure networking engineer should read this one. Day to day: full lifecycle software development from architecture through release and maintenance, requirements analysis, cross team integration work, contributing to the architectural direction of the FlashBlade networking area, and designing, coding and debugging in C and Python. Location and office reality: Bangalore. Everpure states across its postings that it is primarily an in office environment. Honest fit guidance: the band is wide (4 to 7+) and the Broadcom SDK and switch silicon items are the real filter here, more than the year count. If you have done Linux networking or driver work, the storage gap is not the problem you might assume it is.
What the posting asks for: - BS in computer science. - 7+ years designing, developing and testing enterprise products, with Golang preferred. - Good understanding of microservice architectures and cloud native platforms. - Experience designing and owning microservices that operate and scale in a distributed system architecture reaching thousands of nodes. - Expert debugging skills, and comfort navigating ambiguous problems at scale in public and private cloud environments. - Experience working with internal and external stakeholders, from product management through to customer beta partners. - Solid computer science background in data structures, algorithms and software design. - Willingness to work in an open office environment. The posting says this directly. Day to day: designing and developing cloud native microservices for Portworx, code review and test discipline, CI/CD, debugging product and performance issues in large scale clusters using AI tooling, and taking features from initial design through to production while absorbing customer feedback. Location and office reality: Bangalore. The posting states Everpure is primarily an in office environment and that you are expected to work from the Bangalore office outside leave or work travel. It also names the open plan office explicitly, which is worth knowing if that matters to you. Honest fit guidance: this is a real senior role, not a mid level one with an inflated title. If your Go experience is light but your Java or C++ distributed systems work is strong, it is still worth applying, since Golang is stated as preferred rather than mandatory.
What the posting asks for: - 10+ years of strong expertise in C++, Java, Go or related programming languages. - Experience across one or more related systems software areas: distributed systems, operating systems, the Linux kernel, file systems, database internals, hypervisors, containers or compiler optimisation. - Proven design sensibility and a willingness to work collaboratively. - BS degree in computer science. Advanced degrees are described as a bonus. - Willingness to work in an open office environment. Day to day: designing and implementing new algorithms and technologies for high performance, highly scalable and highly reliable systems, with a six nines reliability target. Owning innovation end to end from concept through to shipped product, and solving hard problems that need persistence rather than a quick answer. Location and office reality: Bangalore. The posting states Everpure is primarily an in office environment and you are expected to work from the Bangalore office outside PTO, work travel or approved leave. Honest fit guidance: ten years is the stated floor and the systems software requirement is not decorative. This is not a role to stretch into from application development. That said, the posting's own line about learning system software from scratch suggests they will consider strong systems generalists who have not specifically worked on storage datapaths.
What the posting asks for: - 5+ years in the software industry with a strong focus on quality, automation and engineering excellence. - Deep understanding of object oriented principles and strong Java proficiency. - Expertise designing scalable automation frameworks and identifying negative, edge and high risk scenarios. - Strong understanding of distributed systems failure modes: schema drift, idempotency failures, data inconsistencies and race conditions. - Hands on experience with cloud platforms (AWS, GCP, Azure) and containers (Docker, Kubernetes). - Experience building and maintaining CI/CD pipelines with Jenkins, CircleCI or Buildkite. - Experience with backend automation frameworks. - Demonstrated ability to use AI and LLM tooling to accelerate development, debugging and test design. Strong plus: database testing and ETL or data pipeline validation. Technologies named: Java 11, JUnit5, Docker, Kubernetes, AWS, GCP, Terraform, WireMock, RestAssured, Bazel, BuildKite. Day to day: designing and evolving Java automation frameworks with an emphasis on reliability and data correctness, writing test strategies for complex features, hardening CI/CD so silent failures and regressions get caught, and building internal AI tooling that speeds up debugging, generates test scenarios, spots flaky patterns and improves log analysis. You would also coach other quality engineers. Location and office reality: Bangalore, full time, hybrid with two days a week in the office. That is stated in the posting and is lighter than most roles in this edition. Honest fit guidance: this is an engineering role that happens to sit in test. If your background is manual testing without strong Java and distributed systems knowledge, the requirement list will not bend for you. Company context: read up on the dbt Labs merger before interviewing, since the org is mid integration.
What the posting asks for: - 5+ years of experience. - Strong technical and problem solving skills with recent hands on software development. - Experience with reliable distributed systems, with an emphasis on high volume data management in enterprise or web scale platforms operating under strict SLAs. - Broad technical knowledge spanning software development and automation. - Wide familiarity with algorithms and data structures. - Expertise in Java, AWS, cloud based APIs, databases, software design and programming best practice. - Ability to identify design flaws in existing systems and propose improvements. - Ability to use conversational AI systems such as Claude or ChatGPT to research, author and review engineering documents including technical design documents, postmortems and test plans. - Entrepreneurial mindset with strong communication and technical leadership. Bonus skills: experience with ETL and ELT pipelines, and performance engineering. Technologies named: Java, SQL, Kubernetes, Docker, AWS, GCP, Azure, Buildkite. Day to day: working with cloud APIs, SQL and NoSQL databases and event streams; working on the core data pipeline that moves terabytes from customers into their warehouses; and processing that data into clean, incremental, automated updates. You are also expected to own technical quality for your team's services, review code, contribute to architecture and mentor junior colleagues. Location and office reality: Bangalore, full time, hybrid with two days a week in the office. Honest fit guidance: mentoring is part of the role but there is no people management in it, so it stays an individual contributor seat. If you have five years of Java backend work at data scale, you clear the bar as written. Company context: the dbt Labs merger is live, so expect both brands in the process.
What the posting asks for: - 9+ years of experience working with SaaS products at scale. - Working knowledge of managed Kubernetes across EKS, AKS and GKE. - Knowledge of cloud platforms and the surrounding tooling: AWS, Azure, GCP, Terraform, Ansible, Buildkite, Pulumi and ArgoCD. - Experience with Python and shell scripting. Java or Go is a bonus. - Experience with Linux operating system internals and administration. - Experience with cloud networking including VPNs, PrivateLink and Private Service Connect on GCP. - Experience with databases such as PostgreSQL. Day to day: owning the ongoing reliability and robustness of Fivetran's production infrastructure, the robustness of the deployment pipeline, and timely incident response and resolution. The posting frames the role as driving both effective incident response and overall issue avoidance, and you would work closely with engineering teams, product managers and support and sales engineers. Location and office reality: Bangalore, full time, hybrid with two days a week in the office. Honest fit guidance: nine years is unusually specific and unusually high for an SRE posting. If you are at six or seven years with strong multi cloud Kubernetes and incident command experience it may still be worth an application, but understand you are applying under the stated bar. Company context: the dbt Labs merger means the platform surface is likely to grow during your first year.
What the posting asks for: - 8+ years of professional software development experience. - 5+ years specialising in large scale, production grade ReactJS and Redux applications. This is the real filter, not the overall year count. - Ability to translate complex UI and UX designs into robust production applications. - Frontend best practice depth: modularity, semantic code, comprehensive automated testing and performance tuning. - Experience defining clean API contracts and integration roadmaps with backend teams. - A focus on accessibility (a11y) and research driven method. Day to day: designing and building ReactJS solutions while mentoring other engineers, shaping and evolving Zscaler's core design system, partnering with DevOps on CI/CD, evaluating emerging frontend technology, and leading systematic refactoring work aimed at long term scalability and maintainability. Reporting and scope: the role reports to the Manager of Software Development Engineering. The posting describes technical mentorship and leadership but no people management responsibilities, so this is a senior individual contributor position. Location and office reality: Bangalore. Zscaler runs a hybrid working model and tags this posting #LI-Hybrid. The posting does not state how many days per week, so ask. Honest fit guidance: if your React experience is real but has been on smaller applications, the five year large scale requirement is where this will be judged. Zscaler also states across its postings that it wants people actively using AI tooling to increase their output, and that theme recurs in its interviews.
What the posting asks for: - 8+ years of experience designing and implementing networking security software and public cloud infrastructure. - Strong public cloud knowledge combined with technical expertise in network security. - Hands on development experience. This is explicitly not an architecture only role. - Proven leadership capability in a technical sense. Day to day: participating in the design, development and optimisation of firewall and secure web gateway platforms running in cloud infrastructure; executing the technical roadmap for those platforms; working closely with engineering teams to improve platform support for virtualised environments; and contributing to the growth of other team members. Reporting and scope: reports to the Senior Manager, ZIA Core Engineering, in the ZIA Cloud department. The responsibilities list contains no people management, so this is a senior individual contributor seat despite the Staff title and the mention of developing team members. Location and office reality: Bangalore, stated in the posting as a hybrid role. The number of office days is not published. Honest fit guidance: the OpenSSL and C protocol depth in the title is the actual requirement. General backend experience at eight years will not carry this interview. Zscaler is also explicit that it wants engineers who use AI tooling actively, which appears in the culture section of every one of its postings.
What the posting asks for: - 12+ years in security engineering or product security. - Within that, 7+ years hands on driving and scaling vulnerability and exposure management programmes in complex environments. - The ability to work both strategically and deep in the technical detail: findings, coverage gaps, scanner limitations and remediation paths. - A builder mindset. The posting repeats this framing throughout. Day to day: - Leading vulnerability and exposure management across infrastructure, cloud, APIs and containers, evolving it from a reporting role into a product security engineering capability. - Defining risk based prioritisation models that go beyond standard CVSS by folding in threat intelligence and business context, in order to cut noise and duplicate findings for engineering teams. - Designing and deploying automated data pipelines, scripting and workflow orchestration across the whole lifecycle: asset discovery, authenticated scanning, triage, routing and validation. - Driving external attack surface management to map internet facing assets, and identifying programme gaps such as unauthenticated scans and stale asset ownership. - Influencing engineering teams rather than directing them. Reporting and scope: reports to the Senior Manager, Information Security Engineering, in the Product Security department. The posting states directly that you operate as an individual contributor. Location and office reality: Bangalore, hybrid. Days per week are not published. Honest fit guidance: twelve years is real and so is the seven year vulnerability management specialisation. If your security background is broad but you have not owned a vulnerability management programme end to end, this is a stretch. If you have, the automation emphasis here is a better job than most roles with this title.
⚠️ Shift: the posting states plainly that this role requires working USA working hours, 8:00 pm to 5:00 am IST. Read that first. Everything below is secondary to whether a permanent night shift works for your life. What the posting asks for: - 3+ years of hands on software engineering experience, including time in a customer facing or escalation engineering role. - Programming, database, API and UI expertise sufficient to resolve critical customer issues end to end. - The communication range to work across engineering, support and customer facing teams. Day to day: owning complex technical escalations coming from the success and support organisations and resolving them at code level; driving longer term improvements to how the product is built, debugged and supported at scale; and helping the company adopt AI across support workflows, tooling and troubleshooting. Where the team sits: the Customer Engineering team is described as the intersection of product engineering and the success and support organisation, acting as the deepest technical escalation layer for the most critical customer issues. Location and office reality: Hyderabad. The posting does not publish an office day policy, but it does specify the US shift. Honest fit guidance: this is a good role for an engineer who likes debugging other people's systems and wants customer exposure early. It is a poor role if you want to build features on a roadmap. Do not apply because the years bar is low and then discover the shift, since the shift is the trade you are making.
What the posting asks for: - 3 to 5 years building production search, retrieval, knowledge base or recommendation systems. Day to day: - Building a unified retrieval layer across enterprise systems including Google Drive, SharePoint, Confluence, Jira, Asana, Zendesk, Freshdesk, Salesforce and Notion, exposed through a clean agent friendly interface. - Designing hybrid retrieval pipelines that combine lexical search (BM25), dense vector retrieval and structured SQL or graph retrieval, with re-ranking tuned for cross source results. - Engineering ingestion and freshness pipelines that incrementally sync millions of documents, tickets, tasks and CRM records at low latency and predictable cost. - Shipping production grade observable systems with strong service level objectives on latency, freshness, recall and cost, plus the dashboards and tracing to evidence them. The genuinely hard parts, named by the employer: heterogeneous content types, heterogeneous permission models where every source has its own access control list, and real freshness constraints. Scope: described in the posting as a hands on senior individual contributor role for someone who wants to go deep on retrieval quality. Location and office reality: Hyderabad. No office day policy is published on this posting, and unlike Workato's Customer Centric Engineer role there is no night shift stated here. Honest fit guidance: if you have built search or RAG systems that ran in production and you can talk about recall and ranking quality with numbers, three years is enough here. If your retrieval experience is a demo or a tutorial pipeline, the bar in the interview will be evidence of production quality work.
What the posting asks for: - A total of 4+ years of relevant experience in design, development and implementation. - Within that, at least 1 year of experience with Workato specifically. The posting states this is a must, so treat it as a hard filter. - Deep understanding of AI and ML technologies, integration and automation experience, and solution architecture. - Strong problem solving and the ability to collaborate across multidisciplinary teams. Day to day: - Implementing agent based AI solutions on the Workato Agentic AI platform. - Building intelligent, autonomous agentic workflows using multi agent collaboration and orchestration. - Implementing and deploying retrieval augmented generation systems using the platform's connectors, workflows and recipes so that model responses are grounded and current. - Developing advanced prompting, memory management and behaviour planning so LLMs and agents can author and execute complex workflows reliably. - Acting as the technical expert troubleshooting and analysing AI driven architectures, including scalable RAG pipelines and agent frameworks. Location and office reality: Hyderabad. No office day policy is published, and no night shift is stated on this particular role. Honest fit guidance: this is customer facing engineering, so expect to spend real time with customers rather than only in a codebase. The one year of Workato platform experience is the requirement most applicants will fail on. If you have integration or iPaaS experience on a competing platform, apply anyway and be direct about the gap, since the rest of the requirement list is transferable.
What the posting asks for: - 7+ years of hands on experience delivering end to end automation and cloud infrastructure projects, from requirements through to production deployment. Day to day: - Leading end to end cloud infrastructure automation projects aligned to business requirements, owning architecture, delivery and outcomes across the full project lifecycle. - Designing enterprise grade automation architectures spanning multi system integrations, event driven workflows and infrastructure provisioning pipelines. - Architecting and implementing cloud infrastructure for project incubation, including provisioning cloud accounts. - Building tooling that lets product, engineering and customer success teams move faster. - Streamlining CI/CD and keeping environments secure, scalable and reliable. Who it serves: this is internal platform work. The stated customers are Workato's product, engineering and customer success teams, not external accounts. Location and office reality: Hyderabad. No office day policy is published on this posting, and no shift requirement is stated. Honest fit guidance: the ownership language here is unusually strong for an automation role, so it suits someone who wants to make architectural calls rather than execute a defined backlog. Seven years is the floor. If you are a DevOps engineer at five or six years with genuine project ownership on your record, the gap is smaller than it looks, but you are applying under the stated bar.
What the posting asks for: - BS or above in computer science or a related field. Master's or PhD preferred. - 10+ years developing search relevance systems at scale, either in production or in high impact research environments. - Experience applying LLMs to search relevance. - Experience in one or more of: query understanding, NLP, text mining, recommendations, personalisation, discovery, or conversational AI. - Strong computer science fundamentals. - Contributions to well used open source projects. Day to day: driving the development and deployment of ML based search and discovery relevance models integrated into Databricks products; designing automated ML and NLP pipelines covering data preprocessing, query understanding and rewriting, ranking and retrieval, and model evaluation so the team can iterate quickly; working with product managers on the search and discovery roadmap; and building a robust framework for evaluating ranking improvements both offline and online. The problem in context: customers can hold hundreds of millions of assets on the platform, so this is a genuine large scale retrieval problem rather than a site search feature. Location and office reality: Bengaluru. The posting does not publish an office day policy. Honest fit guidance: ten years specifically in search relevance is narrow, and the open source contribution line is listed as a requirement rather than a nice to have. General ML engineering at ten years is not the same thing as a decade of ranking and retrieval work, and this interview will find the difference.
What the posting asks for: - 15+ years of production level experience in one of Rust, Java, Scala, C++ or a similar language. - 10+ years of experience developing large scale distributed systems from scratch. - Experience working on a SaaS platform or with service oriented architectures. - Experience with cloud networking, Kubernetes, and infrastructure automation languages such as Terraform or CloudFormation. Note on the years: the posting lists both figures as requirements, so the effective bar is the higher one. We have published 15 rather than the lower figure because both sit in the mandatory list. Day to day: owning and driving the design of large scale connectivity platforms forming the backbone between the Databricks control plane and compute plane; improving the scalability, reliability and efficiency of the compute infrastructure; setting technical direction at org level; leading complex cross team initiatives; and mentoring senior engineers. The posting says the role requires both hands on technical leadership and the ability to influence architecture and execution across teams. Why the site matters: the posting positions this as an early hire at a rapidly growing Bangalore site, with scope to define architecture rather than inherit it. Location and office reality: Bengaluru. The posting does not publish an office day policy. Honest fit guidance: fifteen years is genuinely the floor here and networking depth is not optional. This is the least accessible role in today's list, published because engineers at that level rarely see India based openings of this scope. If you are at ten to twelve years with strong multi cloud networking, you are under the stated bar but close enough that an application is not wasted.
What the posting asks for: - 4+ years of professional frontend and UI engineering experience building and operating production quality web applications, diagnosing UI issues, and improving implementations based on real world behaviour. What the team owns: application architecture, shared frameworks, and the deployment pipelines that deliver frontend assets globally using AWS infrastructure including CloudFront CDN delivery. The team builds with cloud native and micro frontend architectural patterns that allow independent development and deployment of frontend components. Day to day: hands on engineering and ownership of frontend components for the Clumio cloud native data protection platform, working closely with product management, design, backend, QA and platform teams to turn complex workflows into clear interfaces. The posting emphasises standardised build and deployment practice. Reporting: the posting states this role reports to an Engineering Director. Its emphasis is explicitly on strong hands on engineering, so it is an individual contributor seat. Location and office reality: Bangalore. The posting does not publish an office day policy. One thing to be aware of: Commvault opens this posting with a recruitment fraud warning. It states that Commvault does not conduct interviews by email or text, and will never ask you to submit sensitive documents such as banking details or identity numbers before your first day. That is the employer's own guidance and worth carrying into any process that claims to be from them. Honest fit guidance: four years is a real floor rather than a soft one, and the emphasis on diagnosing production UI issues suggests they want someone who has supported a live product, not only built features.
What the posting asks for: - 5+ years of experience in application or software security architecture. - Strong knowledge of threat modelling methodologies such as STRIDE, PASTA and OCTAVE. - Hands on experience conducting security architecture reviews for complex systems. - Familiarity with automated security architecture tools such as IriusRisk, ThreatModeler or the Microsoft Threat Modeling Tool. - Experience reviewing the architecture of generative AI solutions. Preferred: experience with automated tools for security architecture analysis, and relevant security certifications. The posting says these are strongly preferred rather than required. Day to day: conducting in depth security architecture reviews across cloud, on premises and hybrid environments; performing threat modelling to identify risks and define mitigations early in the development lifecycle; working with development teams, DevOps and product owners to guide secure design decisions; evaluating and implementing automated tooling for architecture review and continuous assessment; creating and maintaining security architecture documentation and reusable patterns; and contributing to internal security standards and processes. Location and office reality: Bangalore. The posting does not publish an office day policy. One thing to be aware of: Commvault opens this posting with a recruitment fraud warning, stating it does not interview by email or text and will never request sensitive documents before your first day. Honest fit guidance: this is a design and review role, not a penetration testing or SOC role. If your security experience is entirely operational, the threat modelling methodology requirement is where the interview will focus. Five years plus real architecture review experience clears the stated bar.
What the posting asks for: - Bachelor's degree required. - 8+ years overall experience with a track record of leading complex technical initiatives. - Deep expertise in Linux and Windows systems programming and operating system internals, specifically memory management and storage I/O. - Strong C++ background with production experience in low level or systems software. - Hands on Kubernetes experience covering operators, CRDs, CSI, RBAC and cluster level architecture. - Solid understanding of storage internals: block storage, snapshots, replication and consistency models. - Experience with virtualization platforms. KVM and QEMU familiarity is called a strong plus. - Experience with KubeVirt, OpenShift Virtualization or similar container native VM platforms. Day to day: designing and implementing data protection features for virtualised workloads across KVM, QEMU, VMware and Kubernetes native environments; driving architectural decisions for backup, restore and replication pipelines at the operating system and hypervisor layer; contributing to CSI driver development, Kubernetes operator design and container native storage workflows; and providing technical leadership and mentoring across product lines. Scope: the posting describes this as a high impact individual contributor role with broad scope and visibility. Mentoring is included, people management is not. Location and office reality: open across Bangalore, Hyderabad and Pune. No office day policy is published. One thing to be aware of: Commvault opens this posting with a recruitment fraud warning about fake interviews conducted by email or text. Honest fit guidance: eight years is the floor but the C++ and OS internals depth is the real gate. Kubernetes application experience is not the same as CSI and operator development, and the posting is asking for the latter.
What the posting asks for: - 3 to 7 years of hands on software development experience, preferably in a cloud based or product driven environment. - Strong experience with JavaScript and Node.js development. - Solid hands on experience with AWS services including Lambda, EC2, S3 and DynamoDB. - Familiarity with RESTful API design and microservices architecture. - Proficiency with version control (Git) and CI/CD pipelines. - Bachelor's degree in computer science or a related field, or equivalent practical experience. Nice to have: understanding of containerisation technologies such as Docker. Day to day: architecting, implementing and maintaining backend services and APIs in Node.js and JavaScript for the integrator.io platform; using AWS services to build scalable solutions; improving application performance, reliability and security through continuous monitoring; troubleshooting and resolving production issues; developing automated deployment pipelines using CI/CD practice; and translating business requirements into technical specifications with product, operations and design teams. ⚠️ A note on the title: the posting is advertised as Senior Site Reliability Engineer, but the body describes the role as an AWS System Development Engineer and the requirement list is a backend development list. If you are looking for a pure SRE role with on call and infrastructure ownership, read the description carefully before applying, because this leans backend. Location and office reality: Hyderabad. No office day policy is published on this posting. Honest fit guidance: the three year floor is genuine and the wide band suggests they will level you on interview. Strong Node.js plus real AWS serverless experience is what this hinges on.
What the posting asks for: - At least 5 years designing and building integration solutions, ideally within sales or customer success domains. - At least 2 years of experience with JSON and XML schema design. - Strong expertise developing integrations using REST and SOAP APIs. - Proven experience developing AI agents or bots that autonomously interact with tools and systems to derive and act on business insights. - Expertise integrating large language models such as OpenAI's GPT series, Google's Gemini or Anthropic's Claude with external APIs, vector databases and enterprise platforms. - Strong understanding of prompt engineering, context management and orchestration of multi step tasks. - Proficiency with enterprise iPaaS platforms including Celigo and comparable tools such as SnapLogic. Day to day: designing and delivering scalable data pipelines on modern cloud architectures; building automations with integrator.io to remove repetitive work; contributing to AI chatbots for internal stakeholders; ensuring integrations meet engineering standards for data quality, accuracy, operability and security; managing several projects at once including operational tasks; acting as owner and final escalation point for your integrations; and producing technical documentation and support processes. Who you would serve: the posting says this team supports business and finance teams by connecting systems and data. This is internal platform work, not customer facing product engineering. Location and office reality: Hyderabad. No office day policy is published. Honest fit guidance: be clear that this is internal business systems integration with a real AI component, not product development. If that distinction matters to you, weigh it before applying. The LLM and agent requirements are specific enough that generic integration experience alone will not clear them.
What the posting asks for, listed as must haves: - Bachelor's degree in computer science or equivalent practical education and experience. - 4+ years of cloud or infrastructure engineering experience. - 2+ years of infrastructure security experience. - 2+ years working with modern container technologies. Kubernetes is described as a bonus. - Experience securing infrastructure and services in a multi account AWS environment. - Strong understanding of identity and access management: roles, policies and service control policies. - Experience performing security reviews and risk assessments in SaaS and cloud environments. - Understanding of modern DevOps engineering and containerisation. - Working understanding of common network security controls, authentication and security protocols. - Working understanding of SOC 2, FedRAMP, CIS Critical 18 and PCI DSS frameworks. - Ability to communicate with people of varying technical depth, work autonomously and navigate ambiguity. Day to day: operating as one of the senior technical figures for the Infrastructure Assurance team and partner teams across the Asia Pacific Japan region; educating product and platform engineers on security practice for multi cloud, Kubernetes and internal services; providing security design guidance and running security reviews for a secure by design model; mentoring junior team members; and working with IT, compliance, legal and privacy teams. Location and office reality: Hyderabad. No office day policy is published on this posting. Honest fit guidance: the two year security requirement inside a four year overall bar is the detail that makes this reachable. If you are a cloud or DevOps engineer who has been doing security work for two years, you meet this as written, and that is a more open door than most senior security postings offer.
What the posting asks for, listed as must haves: - 5+ years of professional experience in full stack software development, preferably in a SaaS or product based environment. - Proficiency with React (preferred) or Angular, with solid JavaScript and TypeScript, CSS and modern web standards. - Strong backend expertise. The posting names Java and Python for the server side. Day to day: - Independently designing, developing and deploying scalable features using the UI framework on the frontend and Java or Python on the backend. - Implementing AI enhanced workflows, including building Model Context Protocol servers that expose New Relic's telemetry data to LLMs and AI agents. - Owning the reliability and performance of services processing very large data volumes, ensuring they are multi threaded and highly concurrent. - Writing clean, well tested and maintainable code, reviewing peers' code and contributing to internal technical documentation. - Working with product managers and designers to turn wireframes into production software. - Identifying bottlenecks across the stack, from slow UI renders to inefficient backend queries. ⚠️ A location inconsistency worth knowing: the posting header states the location as Bangalore, India, but one paragraph in the body refers to joining a core data team in Hyderabad. We have published Bangalore because that is the stated location field and the explicit location line. Confirm with the recruiter before you plan around either city. Location and office reality: Bangalore per the posting header. No office day policy is published. Honest fit guidance: this is a genuine full stack role, so a backend engineer with weak React or a frontend engineer with weak Java will both find the interview uneven. The MCP and AI agent work is the most interesting part and it is real, not aspirational.
What the posting asks for, listed as must haves: - 5+ years of professional Java development. - Strong experience building cloud native applications on AWS. - Experience designing and operating containerised microservices on Kubernetes. - Experience building and operating distributed systems at scale. - Familiarity with infrastructure as code (Terraform) and CI/CD pipelines. - Experience with AWS security patterns. - Experience with observability tooling, including defining service level objectives and indicators, dashboards and alerting. - Comfort debugging production issues across multi service architectures. - Experience with gRPC or Thrift based service communication, and with GraphQL APIs. Nice to have: - Strong understanding of SQL query execution: parsing, planning, optimisation or execution engines. - Experience with JDBC drivers, connection pooling and database connector development. - Experience with distributed query engines or SQL on anything platforms. Day to day: designing and maintaining cloud native Java microservices in the query path including the SQL gateway, query gateway and data source connector plugins; hardening JDBC connector integrations covering connection lifecycle, credential handling, query pushdown optimisation and security validation; improving query reliability and performance across a multi tenant deployment serving over 50 customers; implementing security controls for user supplied connection parameters including JDBC URL validation, SSRF prevention and hostname allowlisting; building materialized view scheduling and lifecycle features; and designing canary deployments and progressive rollouts. On call: the posting states you participate in an on call rotation and incident response for production systems. Worth factoring in. Location and office reality: Hyderabad. No office day policy is published. Honest fit guidance: the must have list is long and quite specific, but the genuinely rare items (query engines, JDBC connector development) are all in the nice to have section. Five years of solid Java on AWS with Kubernetes meets the stated bar.
Location, stated plainly by the employer: this will be a remote role, but you must be based in Bangalore to be eligible. Cockroach Labs also runs a hybrid model where people local to an office come in on Mondays, Tuesdays and Thursdays and work flexibly otherwise, so clarify at interview which applies to you. What the posting asks for: - 5 to 8 years of experience working in technical support at a software company. - Knowledge of distributed systems and Linux, and the ability to read and write SQL. - Experience using Zendesk, Jira, Confluence or similar software. - A genuine interest in working with users directly, and the judgement to adjust tone and content so a message lands well. - Critical thinking that defaults to a client centric approach. - Effective written and verbal communication, including delivering root cause analysis to different stakeholders. Day to day: supporting both self service and enterprise customers across CockroachDB's deployment models (self hosted, dedicated and serverless); developing deep expertise in the database and surrounding technologies; spotting patterns across customer issues and feeding product improvements back to documentation, product and engineering; writing runbooks and playbooks to cut future resolution time; and reproducing technical issues so engineering can resolve them. Shift note: the posting mentions a follow the sun model to ensure continuity beyond your shift for priority tickets. Ask what that means for your working hours. The published ramp: within 30 days you should have enough expertise to begin assisting users directly, supported by a self guided onboarding platform. After three months you should be fully integrated and able to manage most customer issues. Beyond that, mentoring and training new team members. Honest fit guidance: this is a support role and it is described as one, so do not apply expecting to write product features. It is, however, one of very few remote eligible technical roles available in India right now, and the distributed systems and SQL depth make it a real engineering job.
What the posting asks for: - 8+ years of experience as a software engineer writing clean, idiomatic code. - 1+ years of hands on experience with GCP or AWS. - Ideally, experience with massively complex codebases and broad experience across distributed systems, cloud infrastructure and automated testing. On AI use, stated in the requirement list: rigorous validation habits and deep domain expertise applied to all AI assisted output, a clear understanding of where AI can be safely integrated and where it introduces unacceptable risk, and final authority over everything that reaches production. The posting's framing is that AI assists your work and does not replace your judgement. Day to day: developing test strategies and methodologies; building and scaling test infrastructure; building tools and frameworks that find bugs in complex distributed systems; building static and dynamic analysers; running at scale cloud benchmarking; and prioritising test suites representative of real customer workloads. Named projects from the posting: a mixed version framework using roachtest and roachprod, failure injection testing with tools such as chaos-mesh, the next generation of roachtest and roachperf, parallelised automated microbenchmarks, a static analysis framework for concurrency bugs, large scale benchmarking, and automated flaky test detection and quarantining. ⛔ What this is not: the posting states explicitly that this is not a QA or manual testing role. Location and office reality: Bangalore. Cockroach Labs runs a hybrid model with office days on Mondays, Tuesdays and Thursdays for people local to an office. Honest fit guidance: if you are a manual QA engineer, this posting has already told you it is not for you. If you are a backend or distributed systems engineer who enjoys building tooling that breaks things on purpose, it is one of the more unusual and interesting roles in this list.
What the posting asks for: - Typically 10+ years of experience building large scale, production grade systems. - A strong background in backend or systems programming, preferably with Go, C, C++ or Rust. - Experience working on indexing or query execution systems such as vector, text or spatial search. - Solid understanding of data structures, algorithms and distributed systems. - Genuine interest in databases, indexing systems and high performance distributed architectures. - Curiosity about AI driven and hybrid workloads combining structured and unstructured data. Day to day: designing, building and maintaining specialised indexing features for CockroachDB including vector, full text and geospatial indexing; improving the performance and reliability of existing vector indexing including backfill, query planning and import workflows; integrating new indexing mechanisms into the query engine with other database teams; developing hybrid search that combines vector similarity with text based search; and owning work from design through implementation, testing and release. The published ramp: in the first month, getting familiar with the SQL architecture, the vector indexing implementation and surrounding systems while contributing smaller fixes. Within three months, owning components of specialised indexing and making measurable performance and reliability improvements. After six months, helping shape the roadmap for future indexing and search features. Why it is unusual: this is a new subteam, so the early work shapes what the team becomes rather than inheriting an established roadmap. Location and office reality: Bangalore. Cockroach Labs runs a hybrid model with Monday, Tuesday and Thursday office days for those local to an office. Honest fit guidance: the word 'typically' in front of the ten year figure suggests some flexibility, and the indexing or query execution experience is likely to matter more than the exact year count. Database internals experience is effectively required.
⚠️ Location warning, and please read this before applying: Notion's job board marks this posting as remote, but the posting body carries an onsite tag. Notion states elsewhere that its Hyderabad roles work from the office on Mondays, Tuesdays and Thursdays. We have published this as Hyderabad, not remote, because the posting body is the more specific statement. Confirm with the recruiter before you plan around remote work. What the posting asks for: - At least 4 years of experience as a software developer, with the ability to perform well in a fast paced environment. - Systems thinking: understanding distributed systems and designing solutions that account for tradeoffs between consistency, latency and scalability. - Pragmatic problem solving, prioritising business impact and balancing craft, speed and long term maintainability. The posting says it wants someone opinionated but not ideological who picks up new technologies as they go. - Ownership and initiative. Day to day: contributing to the evolution and maintenance of the async task runner serving over 100 million global users; keeping systems reliable, efficient and scalable with guidance from senior team members; evaluating and integrating new technologies; debugging live production systems with minimal disruption, including replacing components and managing failovers; participating in an on call rotation and responding to incidents; and partnering with product engineers and other infrastructure teams. What the team owns: Notion's internal async task runner, which is critical to product speed, reliability and security, and the configuration management platform used by Notion's product and infrastructure engineers. Honest fit guidance: the posting's language about working with guidance from senior team members and growing your skills in distributed systems suggests this is pitched at the lower end of mid level, which is unusual and welcome. If you have four years of backend experience and want to move into infrastructure, this is a reasonable stretch. The on call expectation is stated up front, so factor it in.
⚠️ Location note: Notion's job board marks this posting as remote, but the body states plainly that the role is based in Hyderabad, India, and that the team works from the office on Mondays, Tuesdays and Thursdays (described as anchor days). The posting also carries an onsite tag. We have published Hyderabad with three office days, because the body is the specific statement. Do not plan around remote work here. What the posting asks for: - Over 10 years of experience with strong software engineering fundamentals and a track record of turning ambiguous goals into well scoped, shippable milestones. - Leadership in the technical sense: the ability to create a technical roadmap, plan and execute very large projects, and motivate a team towards a goal. - Enjoyment of learning new technologies and a demonstrated record of innovation. - Experience building or operating developer tooling such as CI/CD, infrastructure workflows or internal platforms, with a focus on reliability, observability and developer trust. Day to day: - Building an AI harness to auto resolve bugs reported for the Notion app, which the posting calls high leverage work requiring solid engineering to improve resolution accuracy. - Improving CI and build reliability so engineers get early feedback when a change breaks the build. The posting states a five minute CI target that the team is already tracking towards. - Improving developer features for Notion's in house, AI first remote development environments. - Executing a shared roadmap with the US engineering team, informed by an internal developer experience survey. - Working with the TypeScript language server, lint tooling and the Notion CLI. Honest fit guidance: ten years plus is a high floor for a role with no people management attached, so this is aimed at a genuinely senior individual contributor. The leadership described is roadmap and influence rather than direct reports. If you like platform and tooling work more than product features, the scope here is wider than most developer experience roles.
What the posting asks for: - 6 to 8 years total experience, made up of 2 to 3 years hands on in agentic AI and 2 to 3 years in core NLP and data science before that. - Real experience shipping LLM based inference, RAG or agent work, including multi agent systems. - Core NLP and ML foundations: text classification, named entity recognition, embeddings and feature engineering, from before the LLM era. - The judgement to know when classical NLP or ML is the better fit and when an LLM approach is, which the posting says should come from having actually done both. Day to day: - Prototyping fast: turning a rough problem statement into a working RAG pipeline, LLM inference or agent within days rather than weeks. - Taking your own prototypes from notebook to production quality Python: tested, typed and reviewable. - Partnering with the platform engineers who own the harness and infrastructure to ship. You are not expected to design the harness, but you need to understand it well enough to build in it and debug it. - Owning evaluation for everything you ship: offline eval sets, LLM as judge checks, and tracking regressions before and after changes. - Pulling in proofs of concept and external research when the path is unclear, and course correcting quickly. Location and office reality: the posting states this is a hybrid position requiring the ability to be onsite at the Bengaluru office as needed, and that candidates must be based in India. Honest fit guidance: the posting says outright it is looking for a builder rather than a manager in waiting, and that most of your time goes on prototyping and evaluation. If you want a research role or a team lead track, this is not it. The two to three years of pre LLM NLP experience is a genuine requirement and rules out people who came to the field entirely through prompt engineering.
What the posting asks for: - 8+ years in data science or machine learning. - Within that, at least 2 to 3 years hands on building and operating production AI agents. The posting is explicit that this means production systems, not experimenting with agent frameworks, building demos, or wrapping a single prompt with a tool call. - Staff or lead level experience is preferred. Day to day: - Agent architecture and technical strategy: defining the roadmap for the agentic stack covering the execution loop, harness, memory and tool layers, and deciding when an agent, a classical model or a hybrid is the right answer. - Production agent engineering: building and operating the reasoning and execution loop, the harness that manages tool calls, retries, timeouts and session state, short and long term memory, and the skill and tool registry using MCP style tool calling. - Planning and multi step reasoning: designing task decomposition and planning strategies such as evidence based planning, plan and execute, and multi hop reasoning. - Guardrails, trust and evaluation: owning the evaluation framework for agent behaviour including offline eval, LLM as judge and online A/B testing, plus input and output validation and safety checks. - Generative AI and revenue modelling: applying statistical and time series methods to forecasting, deal health and risk prediction models. - Multi agent and cross system coordination: designing how agents communicate with sub agents and other systems. Location and office reality: the posting states this is a hybrid position in Bengaluru requiring onsite presence as needed, and that candidates must be based in India. Honest fit guidance: the distinction the posting draws is the one to take seriously. Demos and framework experiments will not clear this bar, and the interview will look for agents you have kept running in production, including how they failed and what you did about it.
⚠️ Location correction: OpenAI's job board lists this posting as India Remote and flags it as remote, but the body of the posting states plainly that the role is based in Bangalore. We have published Bangalore because the body is the more specific statement. If remote work is the reason you are applying, confirm this with the recruiter first. What the posting asks for: - 8+ years of technical consulting or equivalent experience, managing C level technical and business relationships with complex global organisations. - Deep technical expertise combined with strong judgement and ecosystem leadership. Day to day: - Serving as the senior technical counterpart to AWS field leadership, building credibility across regions and teams. - Influencing joint account strategy and technical direction for high priority opportunities, and shaping how OpenAI engages with AWS through engagement models and prioritisation frameworks. - Leading technical strategy for large, ambiguous, high stakes enterprise engagements, guiding customers from early ideation through architecture design, prototyping and production deployment. - Acting as a technical decision maker and escalation point to de-risk complex implementations. - Designing end to end AI architectures using OpenAI and AWS services, and building prototypes, proofs of concept and reference implementations. - Establishing best practice for scalable, secure, production ready generative AI systems. - Enabling AWS and partners through workshops, playbooks, reference architectures and demos, and mentoring partner technical teams towards self sufficiency. Honest framing on where this sits: the posting says you work across both pre sales and post sales. We have published it because the requirement list is technical consulting and architecture throughout, with no sales quota or pipeline targets attached. If customer facing work is not what you want, this is not the role, and we would rather say that here than let the title imply otherwise. Honest fit guidance: eight years of enterprise technical consulting with genuine architecture depth is the bar. Engineers without customer facing experience will find the C level relationship requirement is real.
Location: the posting lists this as Remote, India. We found no clause in the body contradicting that, which is worth saying because several postings in today's edition did contradict their own location field. Minimum qualifications from the posting: - 5+ years of experience in a customer facing technical role. The posting names solution architect, solution engineer, onboarding engineering, customer success engineering or technical consulting as acceptable backgrounds. - Hands on experience with production workloads in at least one major cloud provider ecosystem: AWS, Azure or Google Cloud. - Deep technical proficiency in core networking infrastructure, including VPC and VNet architectures, routing protocols, peering, and PrivateLink or private endpoints. - Hands on technical proficiency with SQL or NoSQL databases such as SQL Server, MySQL, PostgreSQL or MongoDB. - Proven track record implementing enterprise identity and access management, including single sign on using OIDC or SAML. - Bachelor's degree or equivalent practical experience. Day to day: leading new enterprise customers through critical infrastructure milestones covering cloud provisioning, security hardening, networking, data modelling and application integration; shaping tailored onboarding blueprints and orchestrating delivery workstreams; using automation to optimise data modelling, connectivity and application health for fully managed AuraDB customers; applying infrastructure as code and platform engineering practice to deliver secure, resilient graph clusters in self managed environments; and architecting data ingestion pipelines covering bulk imports, stream processing and change data capture while advising development teams on driver optimisation, connection pooling and retry logic. Honest fit guidance: this is customer facing work and the posting does not hide it, so expect your calendar to have customers in it. What makes it worth publishing is that the technical bar is genuine: networking, IAM and infrastructure as code are all required, not preferred. Graph database experience is not on the requirement list, so a strong cloud infrastructure engineer can learn Neo4j on the job.
⚠️ Experience: ClickHouse publishes no years of experience requirement anywhere in this posting. We have left the figure blank rather than invent one, which does mean this role will not show up if you filter this page by years. Judge it on the skills below. Location: the posting is listed as India (remote) and tagged remote. It also notes ClickHouse is hiring for this role in any country where it has a hiring presence, and describes itself as a globally distributed, remote friendly company offering a home office setup allowance to remote employees. What the posting asks for: - Extensive knowledge of SQL. - Previous work in a similar SDET, release engineering or QA role related to a classical database or distributed system. - Hands on coding experience with Python. - The ability to read C++ code for validation purposes. - Working knowledge of Git, Linux and shell scripting. - Experience with both manual and automation testing. - Demonstrated ability to work collaboratively, including with remote teams, and to learn complex technology quickly. - Strong problem solving and solid production debugging skills. Day to day: building and enhancing test automation frameworks and writing automated test cases; trying out new features and making sure they land smoothly in production; testing cross functional implementations across internal teams; implementing new testing strategies for large complex distributed systems; evaluating new ClickHouse functionality for each release and finding improvement opportunities in the existing codebase; and improving the existing testing infrastructure. Company context from the posting: ClickHouse reports more than 4,000 customers, annual recurring revenue growth over 250 percent year on year, and a 400 million dollar Series D. It appears on the 2025 Forbes Cloud 100 list. Honest fit guidance: the posting describes an ideal candidate with strong technical skills and a background in release engineering. Because no years figure is published, the skills list is the real filter, and database or distributed systems testing experience is the item that matters most.
⚠️ Read this first. The posting states two conditions directly: - Hybrid working with 3 days a week in the office is mandatory. - The role works a 24x7x365 model, and the shift timings rotate every 4 months between APAC, EMEA and US time zones. That rotation is the single biggest factor in whether this job suits you, so decide on it before anything else. What the posting asks for: - 3+ years of experience as a cloud operations engineer, NOC engineer and/or Linux system administrator. - Working knowledge of public cloud environments (AWS, Azure or GCP) and Kubernetes orchestrated containerised workloads. - Strong written and verbal communication skills. - Strong attention to detail and the ability to handle several concurrent tasks. - Ability to work independently with minimal supervision. Described as a plus rather than required: - Experience with monitoring and instrumentation tools such as Prometheus, Grafana, New Relic or Elastic. - Experience with automation using Jenkins, Python or shell scripting. Day to day: supporting all aspects of cloud operations day to day, monitoring availability, durability, performance, scale and uptime of JFrog's multi cloud SaaS services; analysing events, troubleshooting and running incident response; communicating with internal stakeholders and tracking problems through to resolution; building and maintaining standard operating procedures and team knowledge for monitoring and automation; and working closely with SRE, production engineering and cloud engineering on improvements. Location and office reality: Bangalore, three mandatory office days a week, rotating 24x7 shifts. Honest fit guidance: the technical bar is genuinely accessible at three years, and the monitoring and automation items are plus points rather than requirements, so do not screen yourself out over them. The shift rotation is the real trade. This is a good route into cloud operations at a well known DevOps company if rotating hours work for your circumstances, and a poor one if they do not.
What the posting asks for: - At least 3 years building and shipping software in a production environment. - Solid proficiency in Python, JavaScript and/or Golang. - Hands on experience with Docker, Kubernetes and cloud providers. Fastly uses GCP. - Judgement about when to build a complex system and when a simple solution is right, with care for testing, code quality and monitoring. - The ability to explain technical tradeoffs clearly and collaborate with a distributed team across time zones. - Experience guiding and coaching team members. - Ability to pick up new skills quickly and share them with the team. Described by the employer as things that would impress: - Building or maintaining a custom SIEM or SOAR platform. Day to day: designing, developing and refactoring the custom internal security platform across both the FastAPI backend and the React frontend; partnering with security analysts to turn manual workflows into automated reliable processes; working with GCP infrastructure using Kubernetes for orchestration and Terraform for resource management; using Prometheus and Grafana to detect failures early and maintain availability; building and maintaining API integrations connecting detection tools, ticketing systems and customer environments; and championing code quality through reviews, testing and CI/CD. Location and office reality: Pune. The posting does not publish an office day policy. Honest fit guidance: this is a strong option for a backend or full stack engineer who wants to move into security without already being a security specialist. The requirement list asks for software engineering skill first and security context second, and the SIEM and SOAR experience is explicitly a bonus rather than a gate. If you are a security analyst who does not write production code, the balance runs the other way.
What the posting asks for: - At least 7 years of combined experience in software engineering and/or data engineering, with genuine depth in both. The posting is specific that it wants both, not one with a passing familiarity with the other. - A Trino enthusiast, in the posting's own framing, looking to push the boundaries in an AI future. Day to day: - Designing, building and operating a high quality data lake and the software systems that feed it, supporting product management, finance, customer support and engineering. - Writing production grade software including services, APIs, tooling and automation that enables data workflows and integrations at scale. - Finding ways to use Trino and Starburst to solve complex data management and software architecture problems. - Working with technical leads, product managers and data analysts to build data products and analytics. - Using AI to widen access to datasets across the company, including building the software infrastructure that makes that possible. - Enabling dataset preparation and model evaluation for Starburst's AI projects. - Defining engineering processes and best practice spanning both software and data domains. The team: described as dynamic, talented and globally distributed. Location: listed simply as India, with no city named and no office policy published. Worth clarifying with the recruiter, since Starburst does not state whether this is office based, hybrid or remote. Honest fit guidance: the dual requirement is the thing to weigh. Pure backend engineers with no data platform experience, and pure data engineers who have not shipped production services, both sit outside what this posting describes. If you have genuinely done both, this is an unusually good fit and there are not many roles written this way.
What the posting asks for: - 8+ years of professional, hands on engineering experience. - Within that, 4 to 6+ years specialising in building and deploying AI and ML models and systems. - 1+ year of experience developing generative AI and LLM applications using techniques such as prompt engineering, RAG and agents. Note how much lower this figure is than the seniority of the title suggests. - Expertise architecting generative AI applications and systems using various frameworks and cloud services. - Good proficiency with cloud services from Azure, GCP or AWS for building generative AI applications. - Expert proficiency in Python, LangChain or LangGraph, and SQL. The posting says this is a must. - Experience driving an engineering team towards a technical roadmap. - Strong communication skills for working with business subject matter experts. Day to day: building the technical roadmap from a business requirement and owning delivery; leading the design, training, fine tuning and deployment of large language models using prompt engineering, retrieval augmented generation and agent architectures; maintaining high quality Python and SQL with reusable, scalable components; deploying generative AI applications on cloud platforms with robust CI/CD; and collaborating across product and business teams. A note on scope: the posting says you lead the engineering team towards a technical roadmap and ensure timely execution. We read that as technical leadership rather than people management, since no hiring, performance or reporting duties appear anywhere in the posting. Turing does run separate roles that are explicitly people management, and this is not one of them. Location and office reality: Bengaluru. Turing itself is headquartered in San Francisco. No office day policy is published on this posting. Honest fit guidance: if you have eight years of engineering with several in ML and only about a year of hands on LLM work, you meet this posting as written. That is a genuinely more open door than the Principal title suggests, and it is the reason this role is worth a look.
What the posting asks for: - Bachelor's or Master's degree in computer science, engineering or an equivalent technical field. - 5+ years of hands on experience in DevOps, build or platform engineering, SRE, or a closely related infrastructure role. - Production experience scaling CI platforms such as Jenkins, GitHub Actions or GitLab CI. - Solid experience deploying, operating and debugging Kubernetes clusters and containerised workloads. - Proven track record managing public cloud infrastructure (AWS, GCP or Azure) using Terraform or similar infrastructure as code tooling. - Strong scripting and automation skills in Python, Bash, Go or similar. - Deep knowledge of Linux systems administration, networking fundamentals and distributed systems concepts. - Strong analytical and troubleshooting skills. Day to day: - Owning and optimising the end to end developer pipeline covering source control, build systems, test orchestration and artifact release. - Designing, scaling and maintaining distributed CI/CD engines for a rapidly growing engineering team. - Building internal tooling for large scale test automation execution, observability and flaky test debuggability. - Profiling and optimising compilation, linking and test cycle times to keep developer feedback loops short. - Building cloud native testing and deployment environments with Docker and Kubernetes across AWS, GCP and Azure. - Maintaining global infrastructure using strict infrastructure as code patterns with Terraform and Ansible. The posting's own framing: it states explicitly that this is not a passive infrastructure maintenance role, and that you would work with core engineering, SRE, cloud and security teams to remove developer friction. Location: listed as India with no city named and no office policy published, so clarify that with the recruiter. Yugabyte describes its team as distributed across more than 12 countries and multiple time zones. Honest fit guidance: five years is a real floor and the build optimisation work (compilation and link time profiling) is more specialised than standard DevOps. If your experience is deploying applications rather than building the pipelines that produce them, expect that gap to come up.
What the posting asks for: - At least 5 years of experience developing and optimizing systems software. - Deep expertise, meaning you can speak to both system level design and implementation detail, in at least one of: virtualization, storage, service modelling and REST API or SDK generation, scientific or high performance computing, or kernel development. - Experience designing, developing and/or troubleshooting distributed systems. - Comfort with at least one systems programming language (C, C++ or Go) and one scripting language (Python or Bash). - Comfort with shells on UNIX family systems. - Natural curiosity and drive to learn adjacent technologies. - BS degree or equivalent experience in computer science or a related field. Preferred qualifications: - Experience with low level monitoring and profiling tools such as pcm, perf or bpf. - Experience with, or hobbyist interest in, distributed elastic AI and LLM CPU inference, for example OpenVINO or llama.cpp. - Familiarity with, or interest in, SingleStore or other distributed SQL databases. Day to day: designing and developing major infrastructure components with a focus on fault tolerance and performance; owning your systems end to end from design to production; working closely with other teams on integration and operation; and driving continuous improvement in system reliability and usability. Team culture, as the posting describes it: a small, highly skilled team that works from first principles, practises distributed leadership where you shift between leading, collaborating and following depending on the project, and treats mistakes as something to learn from rather than punish. Location: listed as India with no city named and no office day policy published. Worth clarifying. Honest fit guidance: the preferred list is genuinely preferred, so the hobbyist framing on LLM CPU inference means what it says. The requirement that will decide this is depth in one low level area. Breadth across cloud tooling without that depth is not what this posting is asking for.
Added July 31, 2026
Required by the posting: a minimum of 8 years of experience in performance testing and engineering roles with scalable cloud native multi tenant architectures. Proven expertise with at least one major performance testing tool, with JMeter, Locust, LoadRunner, Gatling, k6 and BlazeMeter named. Strong proficiency in at least one scripting or programming language for test development and customisation, with Java, Python, Golang and JavaScript named. Hands on experience with Docker and Kubernetes, including understanding how container resource limits affect application performance. Solid understanding of system architecture components including web servers, application servers, databases and load balancers. Experience with modern APM and monitoring tools incorporating AI/ML capabilities such as Dynatrace, New Relic, Prometheus, Grafana or Datadog. Working knowledge of SQL and NoSQL databases with the ability to analyse and optimise query performance. Strong analytical skills to interpret large datasets and AI generated outputs such as log traces and metrics to pinpoint root causes. Proficiency in machine learning and AI concepts including supervised learning and predictive modelling, and their application across the performance test cycle. Preferred skills: experience with cloud platforms including AWS, Azure and GCP and testing applications deployed in cloud native environments, and familiarity with continuous integration and continuous delivery pipelines. The real day to day: developing comprehensive performance test strategies and plans covering load, stress, volume and endurance testing; designing and maintaining robust, reusable test scripts for protocols including HTTP, web services, APIs and FTP/SFTP; collaborating with DevOps and infrastructure teams to configure performance test environments that accurately replicate production; designing and deploying containerised load generators onto the Kubernetes cluster to simulate massive scale with minimal overhead; executing tests and conducting deep dive analysis to identify bottlenecks in application code, database performance, network latency and infrastructure resource use; documenting clear reports with metrics and actionable recommendations for engineering and product stakeholders; working with developers and architects on performance tuning and code optimisation; and contributing to continuous improvement of the testing framework. Location: Bengaluru, Karnataka. Honest fit guidance: performance engineering at this depth is a genuine specialism, and eight years of functional test automation is not the same thing. The distinguishing requirements here are the Kubernetes native load generation and the expectation that you can read APM output and pinpoint root causes across code, database, network and infrastructure. The machine learning requirement is worth noting as a trend rather than a barrier: it is asking you to apply ML concepts to test analysis, not to build models. One relevant note from previous editions: Netskope has stated on other postings that it hires across all levels and levels candidates individually after assessment, so its stated year figures have historically been softer than they look.
Required by the posting: 4+ years in Linux/Unix administration with extensive field experience. Computer networking proficiency and working knowledge. Experience with a wide variety of open source technologies and tools with a strong emphasis on cloud services. Ability to implement best practices and IT operations to maintain an always up, always available service. Active participation in the on call rotation schedule. Effective English communication. A strong background in Linux networking including IP, iptables and IPsec. Effective work with MySQL databases, with MariaDB and Percona experience a plus. Coding and scripting skills, with a preference for Perl, Python or Golang. Experience with automation and configuration management using tools like SaltStack. Hands on experience with private cloud environments. Desirable skills: experience implementing cloud services on Linux using KVM and QEMU; familiarity with container orchestration; knowledge of NoSQL databases, especially Aerospike; proficiency in Perl and Golang; understanding of Galera cluster operations; and experience with data centre related activities. The real day to day: maintaining the reliability and performance of large scale fintech infrastructure, with the posting framing the goal as keeping services always up and always available, and the technology mix pointing squarely at private cloud systems engineering rather than managed cloud services. Location: Bangalore. The requisition location is recorded as Bengaluru, Salarpuria Softzone, and the requisition type is full time regular employee. Benefits, which PhonePe publishes in full and few employers do: medical, critical illness, accidental and life insurance; a wellness programme with an employee assistance programme, an onsite medical centre and an emergency support system; parental support covering maternity and paternity benefits, adoption assistance and a day care support programme; mobility benefits including relocation, transfer support and travel policy; and retirement benefits covering employee provident fund contribution, flexible provident fund contribution, gratuity, National Pension System and leave encashment. Honest fit guidance: the private cloud emphasis is the thing to weigh. If your infrastructure experience is entirely AWS or GCP consoles, KVM, QEMU, SaltStack and Galera will be unfamiliar and the interview will find that quickly. If you have run physical or virtualised infrastructure in a data centre, this is a rarer and more durable skill set than it gets credit for, and PhonePe operates it at a scale few Indian employers can offer. One thing to know from previous editions of this list: PhonePe frequently posts near identical job descriptions under several different titles and requisitions, so if you see similar SRE and Service Delivery Engineer listings, they may be the same job.
Minimum requirements from the posting: a BS or MS in Computer Science or an equivalent field. 12+ years of professional experience in software or infrastructure engineering. A proven track record leading complex, cross team or company wide infrastructure projects with high reliability and scale requirements. Strong engineering background in distributed systems, platform engineering or backend infrastructure with a focus on operational safety and correctness. Experience optimising the reliability and security of distributed systems. Experience scaling and migrating systems with little to no downtime. Strong technical judgement and written communication including design docs and trade off analysis. Experience mentoring engineers at various career stages. Experience with one or more major cloud providers, with AWS, Azure, OCI and GCP named. Familiarity with ops culture and a solid understanding of metrics, alarms and dashboards. Preferred qualifications, which the posting states are a bonus and not a requirement: experience validating large scale migrations, failovers, regional launches, regionalisation or control plane behaviour; designing or operating infrastructure with strict reliability, correctness, latency or availability requirements; strong observability judgement across metrics, logs, tracing, alerting and incident analysis; experience with networking, service discovery, traffic routing, databases, Kubernetes, Terraform or cloud infrastructure; experience reducing packet loss, network latency or cross region dependency risk; and experience making infrastructure validation evidence usable by service owners and partner teams. The real day to day: defining evidence based readiness criteria for regional launches, traffic migrations and failovers, replacing manual checklists with repeatable patterns; identifying and mitigating risks on critical payment paths and validating that platform mitigations measurably reduce impact; leading cross functional delivery for new region infrastructure including safe service behaviour for remote control planes; building reusable validation tooling that speeds infrastructure integration for new acquisitions; converting recurring operational friction into platform capabilities; leading technical conversations and defining decision mechanisms across Core Infrastructure and product teams; developing a multi year technical strategy with quarterly milestones; debugging production issues across the stack; and mentoring senior engineers to grow the Bangalore technical bench. Location and working pattern: Bengaluru, India, with the posting noting collaboration in a global distributed environment with asynchronous decision making across AMER, EU and APAC. One thing worth quoting because it is unusually candid: the posting says "We're looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement." Take that at face value and do not self reject on the preferred list. Honest fit guidance: this is a leadership shaped IC role. The mentoring and bench building responsibilities are explicit, as is developing multi year strategy, but there are no direct reports. The domain is narrow and valuable: if you have done regional expansion, failover validation or control plane work, you are rare. If your 12 years are in product engineering rather than infrastructure, the correctness and operational safety focus is a genuine mismatch.
What the posting asks for, and how it frames it. Composio heads its requirement list "Must haves" and then immediately qualifies it with "if you are very good, nothing is a must per-se". The capabilities it lists are: Core platform engineering: you have built systems where the abstractions were the product; you can reason about multi tenancy, isolation, auth, routing and observability without hand waving; you know how to ship reliable systems while the product is still changing fast. Enterprise judgement: you understand deployment flexibility, security, admin tooling and compliance as product problems; you can separate one off customer requests from primitives that should exist for every customer. AI native: you have built with language models; you have opinions about agents, MCP, tool use and where current systems fail. Plus two the posting labels directly: "typist", meaning you can write design docs and explain complex infrastructure clearly, and "human", meaning you build trust and admit what you do not know. Listed as Optional: multiple years writing TypeScript, Go or similar systems languages; experience building enterprise developer platforms inside large organisations; security, compliance or deployment model depth; and having started companies or built large side projects. The real day to day: evolving the platform primitives enterprise agents run on, covering governance, auditability, observability, permissions, routing and control planes; building the secure integration gateway between customer agents, SaaS tools, internal systems and APIs; designing multi tenant abstractions for isolation, configuration, extensibility and deployment flexibility; turning enterprise onboarding from a services engagement into a repeatable product experience; working directly with customers to understand where agent infrastructure breaks in real deployments; and making security, compliance and reliability first class product capabilities rather than later stage patches. Location and team: Bangalore, and Composio's own board marks this as not remote. The posting describes a small team of engineers. ⚠️ Years: this posting states no years of experience anywhere, which is why our experience filter cannot place it. Note that it goes further than most and puts "multiple years writing Typescript, Go, or similar systems languages" under Optional rather than required. Honest fit guidance: do not read the absence of a years bar as an entry level opening. The capability list (multi tenancy, isolation, auth, routing and observability reasoned about "without hand waving", plus systems where the abstractions were the product) describes a senior platform engineer. What the framing does mean is that a strong portfolio can substitute for a conventional CV here in a way it cannot at the enterprise employers on this list. If you have built infrastructure others build on and you have real opinions about agents and MCP, this is a posting where saying so is worth more than your years count.
Required by the posting: 4 to 6 years of industry experience. A Bachelor's or Master's degree in Computer Science, Electrical Engineering or another scientific or technical discipline. Cloud native application development experience using best practices and design patterns. Strong debugging and troubleshooting across the entire technology stack. Deep understanding of AWS networking, compute, storage and managed services. Competency with modern CI/CD tooling including Kubernetes, Terraform, Ansible and Jenkins. Experience with full lifecycle support of services from creation to production support. Infrastructure as code practice using Terraform or CloudFormation. Ability to author production ready code in at least one of Java, Scala or Go. Experience with Linux systems and comfort on the command line. Understanding of modern cloud native software security. Experience with agile frameworks such as Scrum and Kanban. Flexibility to step into new roles and responsibilities, and willingness to learn and use Sumo Logic's own products for solving reliability and security issues. Desirable skills: experience using Sumo Logic or other observability products; planet scale product development; running and operating SaaS products on AWS at expert level; streaming technologies such as Kafka, Kafka Streams or KSQL; expert level experience in one or more of Java, Go, Scala or Python; and expert level experience in one or more of Terraform, Jenkins or Kubernetes. The real day to day: maintaining and executing a reliability roadmap for your product area covering reliability, maintainability, security, efficiency and velocity; collaborating with development infrastructure, Global SRE and product area engineering teams to refine that roadmap; defining, evolving and managing SLOs for several teams; participating in on call rotations specifically to understand the operational workload well enough to improve it; improving the lifecycle of microservices from design through deployment and refinement; writing code and automation to reduce operational workload, improve security posture and eliminate toil; working with developer infrastructure teams and contributing features and bug fixes back; scaling systems sustainably through automation; and facilitating blame free root cause analysis meetings after incidents. Location: the posting body states Noida (Hybrid), while the Greenhouse metadata field for this requisition carries an office requirement value of Remote. We have published the body's statement because it is the more specific one, but this is a genuine ambiguity worth resolving with the recruiter on the first call. Honest fit guidance: the reliability roadmap and SLO ownership make this more strategic than a firefighting SRE seat, and the requirement to author production code in Java, Scala or Go means it is an engineering job rather than an operations one. If you have four to six years and can write real code, this is a strong mid level move.
Required by the posting: 2+ years of professional experience in machine learning and software engineering, with experience shipping production grade ML services. Hands on experience building with modern AI architectures such as LLMs and deep learning, and familiarity with tools including LangGraph, LangSmith, Google ADK, Vertex AI or AWS Bedrock. Strong proficiency in Python with the ability to write clean, maintainable, well tested production code. Working knowledge in at least one domain such as NLP, information retrieval, computer vision or statistical modelling. Ability to write technical design documents and communicate ML system designs clearly to cross functional stakeholders. Responsible use of generative AI with human oversight to deliver business ready outputs. The real day to day: building and improving the orchestration layer that manages state transitions, context sharing and intent routing across vendor and internal LLM frameworks in a distributed conversational environment; developing production grade Python services that bridge AI and ML capabilities with customer facing products; driving well scoped ML projects from design through delivery; contributing to system design, coding standards and AI/ML best practices; and participating in design reviews to ensure features meet Coinbase standards for security, compliance and performance. Team context: the CX Intelligence team sits in Coinbase's Enterprise Applications and Architecture organisation and owns the multi agent platform powering Coinbase chat, the Help Center and agent tooling, working with Conversation Design and CX teams. The role is levelled IC4. Location and working pattern: the board lists this as Remote in India. The posting states that Coinbase is remote first but not remote only, and that you should expect to get together quarterly for in person working sessions the company calls "surges". Factor that travel in before treating this as a fully remote job. Compensation: unusually, the posting publishes a specific annual base salary figure for this requisition of ₹4,408,400, excluding equity and bonus. Very few postings on this board state Indian salary at all. Application limit, stated in the posting: candidates may submit a maximum of 3 applications within a 6 month period at Coinbase. Do not spray applications across their board. Honest fit guidance: the posting opens by saying the bar is high and the environment intense, and that it is not a place for complacency. Take that as written. But the 2 year requirement is genuine and unusually low for a remote role of this quality, so if you have shipped a production ML service and know the modern agent tooling, this is worth your best effort rather than a quick application.
Required by the posting under What Makes You a Match: customer facing security work at a B2B SaaS company, with the ability to hold a credible technical conversation with an enterprise security team. Production AI agent experience, and the posting is emphatic about the standard: "Not prototypes, not prompts in a notebook. Real systems that replaced manual work in compliance, triage, evidence collection, or questionnaire automation." Deep enough understanding of AI and LLM security to explain it to a customer, covering prompt injection, agent guardrails, MCP exposure, model and data risks, and where frameworks like ISO 42001 apply. A closing the loop temperament: identify the gap, build the fix, and do not wait for someone else to execute on a commitment you made on a call. Comfort working evening IST hours to overlap with US and EU customers. Bonus: hands on experience with automation platforms like n8n or Tines, and working knowledge of SOC 2, ISO 27001, ISO 42001, HIPAA or GDPR. The real day to day, split as the posting states it, roughly half the week on direct customer security work and the rest building: owning calls, architecture deep dives and security reviews with sophisticated security teams at Fortune 500 companies across financial services, healthcare and payments; leading AI security conversations on agent behaviour, MCP exposure, context governance and ISO 42001; turning security reviews into an accelerator by handling the judgement cases their compliance tooling cannot, building reusable artifacts, and keeping the public trust centre current, with the measure being shorter customer onboarding rather than completed questionnaires; designing and shipping AI agents that keep evidence current and reduce manual review work every quarter, owned end to end; and contributing to the compliance programme across SOC 2, ISO 27001, ISO 42001, HIPAA and GDPR. Location and hours: the board lists India with the remote flag set on Atlan's own job board, and Atlan describes itself as global, remote first and high trust with a team across 15 or more countries in a trust first, async environment. The one firm constraint is the evening IST working hours, which the posting states is a real part of the role and not occasional. ⚠️ Years: this posting states no years of experience figure anywhere, so our experience filter cannot place it. The production AI agent requirement and the enterprise security review experience are the real bar, and both are more specific than a years count would be. Honest fit guidance on why it is here: the posting does use deal language, including "when the deal is on the line", so it is fair to ask whether this is a sales job. We concluded it is not: there is no quota, no pipeline target and no revenue responsibility, half the week is building systems the person owns end to end, and the hard requirement is having shipped production AI agents. It sits in our customer facing group rather than the main engineering list because the customer half is genuinely half.
Required by the posting: 6 to 9 years of experience in a combination of development and sustenance roles. Extensive hands on experience in Go or Python on Unix, Linux or Windows platforms. Excellent programming skills with data structures, algorithms and design concepts. Strong problem solving skills and demonstrated ability to articulate and present technical solutions. Strong interpersonal and communication skills, written and verbal, with the ability to build working relationships at all levels with both customers and internal stakeholders. Experience in enterprise software with deep knowledge of software development including threading, network and disk IO, data transformations, data integrity, systems management, systems administration and monitoring. Desirable skills: exposure to Office 365, VMware, Hyper-V, Nutanix, file systems or network attached storage; 6+ years of software development in Python or Golang; experience developing complex, scale out distributed systems based on service oriented architecture or microservices; cloud technologies, preferably AWS; and knowledge of the backup or storage domain. The real day to day: proposing solutions to complex design problems for the relevant technology or workload; fixing product bugs and delivering code changes to production; working with Sales, Tech Support, Customer Success and Professional Services to assist on proofs of concept and implementation projects; owning and driving cloud production issues through investigation and root cause analysis, delivering a fix and working with extended development teams; validating future releases in a staging environment against customer use cases, acting as a gatekeeper for product release and quality; partnering with scrum teams and Product Management on feature design and product improvements; and ensuring communication flows cross functionally on product updates and known issues. Qualification: B.Tech, B.E., M.E. or M.Tech in IT or Computer Science or equivalent. Location: Pune, Maharashtra. Honest fit guidance: the phrase "development and sustenance" in the requirement is the key to this role. Sustenance engineering means maintaining and fixing shipped software, and some engineers find it the most satisfying work available because the problems are real and the feedback is immediate, while others find it frustrating because you rarely build greenfield. The customer contact is real but technical, and the release gatekeeper responsibility gives it more authority than a typical bug fixing seat. Know which of those two reactions is yours before applying.
Required by the posting: 3 to 6 years of experience. A B.Tech, B.E., M.E. or M.Tech in Computer Science or equivalent. The real day to day: working closely with the development team in an Agile environment to understand functional specifications and design requirements; independently creating comprehensive feature test plans aligned with development milestones and feature completion; leveraging existing automation frameworks to automate feature tests and actively augmenting libraries to support new functionality; owning the complete test execution cycle for user stories; performing a mix of automated, manual, white box and black box testing; creating, maintaining and documenting testbed setups and environments; reporting, tracking and updating issues and test cases; and collaborating with cross functional teams to meet quality benchmarks across the development lifecycle. Location: Pune, Maharashtra. What this posting does not tell you, stated plainly: Druva's requirement list here is short. It gives the years band and the degree, and then describes responsibilities rather than a technology checklist. For comparison, Druva's more senior Software Engineer in Test requisition asks for Windows and Linux expertise, file systems and operating system concepts, threading, multiprocessing and socket programming, cloud fundamentals with AWS or Azure, Python or Java with Python preferred, shell scripting, SQL, REST API testing and backend automation, and tools including Git, Jira and XRay. That is a reasonable guide to the skills this team works with day to day, even though this particular requisition does not enumerate them. Honest fit guidance: this is a good role for someone in the middle of a test engineering career who wants product company experience in cloud data protection. Two caveats worth being honest about. The posting explicitly includes manual testing alongside automation, so it is not a pure SDET seat. And the responsibilities emphasise independence, with the phrase "independently create comprehensive feature test plans", so it suits someone who has already owned features rather than executed someone else's plan.
Required by the posting: 6+ years of experience, preferably in a product company with exposure to storage architectures. Strong demonstrable experience in systems programming, specifically multithreading, synchronisation, fault tolerance and data consistency at scale. Hands on experience designing and developing complex products. Extensive hands on experience in Go, Python, C, C++ or Java on Unix or Linux platforms. A strong understanding of computer architecture, data structures, algorithms, design concepts and programming practices. Experience with service oriented architecture, especially on the service backend. Desirable rather than required: excellent written and verbal communication; cloud technologies, preferably AWS; working knowledge of Docker and Kubernetes; working knowledge of storage and file systems including file system consistency checks; and hands on experience using generative AI for code generation. The real day to day: metadata versioning and change tracking across petabytes of data residing in the cloud; third party secondary storage appliance integration for data centre data protection; extending the filesystem to store workloads beyond files and folders, such as emails and messages; optimising the filesystem for cost using strategies and algorithms that leverage cheaper cloud storage tiers and reduce IO requests; and developing tools that make production issues easier to debug. The role, in the posting's framing: to be the technical owner building enterprise grade, scalable, performant systems; to design and implement large and complex features or architectural improvements; to propose solutions to complex design problems; to identify engineering improvements and work with product architects and the team on them; to technically guide junior engineers on feature design and implementation and review their work; to independently handle complex escalations; and to write technical blogs and present in internal and external forums. Qualification: B.Tech, B.E., M.E. or M.Tech in Computer Science or equivalent. Location: Pune, Maharashtra. Honest fit guidance: the cost optimisation work is worth calling out because it is unusual and genuinely interesting. Reducing cloud storage spend through tiering strategy and IO reduction is a systems problem with a directly measurable outcome, which is rarer than it sounds. The guidance and review duties are technical mentoring rather than management, with no reports or hiring involved.
Required by the posting under Must Have: 5 to 8 years of experience in AI/ML engineering with at least 2 years leading AI initiatives. Strong expertise in Python, TensorFlow, PyTorch and Hugging Face Transformers. Hands on experience with LangChain or similar LLM application frameworks. Solid understanding of vector databases, RAG architectures and prompt engineering. Proficiency in MLOps tools including MLflow, Kubeflow, Airflow, Docker and Kubernetes. Familiarity with cloud AI platforms including AWS SageMaker, GCP Vertex AI and Azure ML. Strong background in data pipelines, APIs and scalable system design. Nice to have: experience fine tuning LLMs with LoRA, PEFT or parameter efficient training; knowledge of computer vision or multimodal AI; familiarity with responsible AI frameworks and explainability tools such as SHAP, LIME and Captum; and contributions to open source AI projects. Education, and this one is a real filter: the posting requires a minimum Master's degree in Engineering, Computer Science, Mathematics, Computational Statistics, Operations Research, Machine Learning or a related technical field. If you have a Bachelor's only, this specific requisition will screen you out regardless of experience. The real day to day: building production AI systems, assessing emerging frameworks for adoption, mentoring junior AI engineers and promoting best practices in AI engineering, working with business stakeholders to translate requirements into AI driven outcomes, and ensuring adherence to responsible AI principles including bias mitigation, fairness and explainability. ⚠️ A years contradiction inside the posting, which we publish honestly rather than picking the flattering number: the Must Have section says 5 to 8 years of AI/ML engineering experience, while the Desired Experience section further down says 4 to 8 years of relevant Machine Learning experience. Sigmoid's own Greenhouse metadata records a minimum of 4 and a maximum of 8. We have published 5 to 8 because that is the harder requirement stated in the mandatory section, but if you are at 4 years the posting itself gives you grounds to apply. Note on the "leading AI initiatives" requirement: read in context with the responsibilities, this is technical leadership of AI projects and mentoring, not people management. There are no direct reports or hiring duties in the posting. Location: Hyderabad.
Required by the posting: 4 to 6 years of experience developing, enhancing and maintaining enterprise scale Security Operations and SIEM platforms based on the ELK stack (Elasticsearch, Logstash, Kibana). The posting states this bar three separate times and consistently, as 4 to 6 years in detection engineering, SIEM engineering, security operations or SOC environments, and as 4 to 6 years of overall experience as a security operations engineer in medium to large product companies. Strong hands on experience in log parser development, security content engineering, ELK administration, AWS environments, microservices architectures and open source security technologies. The real day to day: designing, developing and maintaining high fidelity detection rules, correlation rules, alerts and security use cases for new and existing log sources, and continuously tuning them to cut false positives and expand coverage; developing detection content for AWS services, Kubernetes, microservices, Linux, macOS, databases, web applications and firewalls using the MITRE ATT&CK framework, threat intelligence and adversary tactics, techniques and procedures; onboarding new log sources by building Logstash pipelines, custom parsers, Grok patterns, ingest processors and enrichment workflows, including analysing raw log formats and normalising events to a common schema; designing operational, executive, SOC and threat hunting dashboards with optimised OpenSearch Query DSL; integrating threat intelligence platforms, indicator feeds and enrichment services with OpenSearch and building indicator correlation rules; and expanding the SIEM with advanced capabilities including UEBA, anomaly detection, OpenSearch notebooks for investigation playbooks, SOAR workflows for automated response, and AI driven automation to streamline Level 1 SOC operations. Location and team: Hyderabad, in the Cloud and Product Security team within Risk and Compliance. Employment type is stated as full time. Company context worth knowing: Zeta is backed by SoftBank Vision Fund and Mastercard, reached a $2 billion valuation in 2025, and runs products including Tachyon (cloud native banking stack), Cipher (authentication) and Pixel (a digital native credit card launched with HDFC Bank). Honest fit guidance: unlike many security postings that blur into governance and compliance, this one is engineering throughout. If you can write parsers and detection content and are comfortable in the ELK and OpenSearch ecosystem, the fit is direct. If your security background is audit, policy or risk assessment, this is the wrong shape of role.
Required by the posting: 10 to 15 years of experience in site reliability engineering. Proficiency in one or more programming languages, with Python, Go, Shell and Bash named. Strong automation skills using Ansible, Puppet, Chef or custom scripts, plus infrastructure as code knowledge with Terraform. Experience with containerisation using Docker and container orchestration with Kubernetes. Proficiency in any of the major cloud platforms including AWS, Azure or Google Cloud. The real day to day, as the posting sets it out: system reliability, meaning designing, implementing and maintaining scalable and reliable infrastructure; automation of operational tasks to reduce manual intervention; incident response and resolution, monitoring performance and responding promptly to minimise downtime; capacity planning by analysing usage patterns and forecasting future needs; performance optimisation by identifying and addressing bottlenecks; infrastructure as code using tools like Terraform or Ansible; monitoring and logging to gain insight into system behaviour; collaborating with security teams on infrastructure and application security practices; disaster recovery planning so systems recover quickly from major outages; continuous improvement by analysing performance, reliability and incidents; and mentorship and coaching of team members. Location and team: Hyderabad, in the Tachyon PLE team within Engineering. Employment type is stated as full time. Why this is on an individual contributor board, and why a sibling role was rejected: we drop people management roles. Zeta is currently running several SRE requisitions, and two of them titled Lead Site Reliability Engineer contain explicit people management duties, including establishing an SRE site and building a team, leading and motivating a team of SREs, managing execution of project priorities and deadlines, and resolving conflicts within the team. Those were rejected. This Principal requisition contains none of that. Its only people related line is mentorship and coaching, which is normal for a principal IC. Company context: Zeta is backed by SoftBank Vision Fund and Mastercard, reached a $2 billion valuation in 2025, and runs Tachyon, its cloud native banking stack built for population scale systems. Honest fit guidance: at 10 to 15 years this is the senior end of the SRE ladder, and the domain is financial infrastructure where downtime has direct consequences. The requirement list is standard SRE rather than exotic, so the differentiator will be the scale and criticality of what you have run, not the tools you can name.
Required by the posting: a 3 to 5 year track record of relevant work experience with a Computer Science or related technical discipline. Experience developing enterprise scale applications and capability with frameworks and design patterns. Experience with functional and object oriented programming, with Java preferred or Python as a must. Hands on knowledge of MapReduce, Hadoop, PySpark, HBase and Elasticsearch. Development and support experience in the big data domain. Experience with database modelling and development, data mining and warehousing. Unit, integration and user acceptance testing. Effective communication skills. The real day to day: developing and evolving highly scalable, fault tolerant distributed components; designing and implementing APIs, abstractions and integration patterns for distributed computing problems; defining technical requirements, data extraction and transformation, automating and productionising jobs, and exploring new big data technologies in a parallel processing environment; application development, support, integration development and quality assurance; and interfacing daily with customers across leading Fortune 500 companies to understand strategic requirements. Two working conditions stated in the posting that you should factor in before applying: the role is client facing with daily customer interaction, and it asks you to be open to working from a client location as the demand of the project or customer requires. The posting also states the position reports to the Engineering Manager. Location: Bengaluru, Karnataka. Sigmoid's Greenhouse metadata records a minimum of 3 and a maximum of 5 years for this requisition, matching the body. Honest fit guidance: one oddity worth flagging so you are not confused in the interview. Sigmoid reuses a common responsibilities block across several postings, so this SDE II listing contains a line about providing technical leadership and managing it day to day that also appears on its Technical Lead requisition. At a 3 to 5 year band with an Engineering Manager reporting line, treat that as boilerplate rather than as a hidden management expectation, but it is fair to ask what the actual scope is. The consulting model is the more important thing to be sure about: this is enterprise client work, not internal product engineering.
Required by the posting: 3 to 5 years of relevant Machine Learning experience. Strong programming in Python with TensorFlow, PyTorch and scikit-learn, plus GenAI frameworks such as LangGraph, AutoGen and the OpenAI SDK, and prompt engineering on foundation models from OpenAI, Hugging Face and Anthropic. Knowledge of NLP, computer vision or generative AI covering LLMs, diffusion models, RAG, model fine tuning, conversational AI and knowledge graphs. Familiarity with cloud AI services including AWS SageMaker, Azure ML and GCP Vertex AI. Solid understanding of data structures, algorithms and software engineering principles. Hands on experience with model deployment through APIs, microservices and real time inference. Nice to have: experience with MLOps tools including MLflow, Kubeflow, Airflow, Docker and Kubernetes, and experience with big data technologies such as Spark and Hadoop. The real day to day: architecting, developing and deploying machine learning models and AI solutions into live production; partnering with data scientists to convert prototypes into scalable enterprise ready applications; designing enterprise AI systems using LLMs, RAG, knowledge graphs and multi agent orchestration; embedding AI models into existing products, APIs and enterprise systems; running experimentation, fine tuning and error analysis to improve model accuracy; monitoring, maintaining and retraining deployed models; translating business challenges into AI solutions with stakeholders; and upholding responsible AI principles. Client facing reality: the posting states you will be engaging with clients to understand their business context, and Sigmoid's work is consulting shaped for large enterprises. Its other postings note openness to working from a client location depending on the project, so ask about that during interviews. Location: Hyderabad. Sigmoid's Greenhouse metadata for this requisition records a minimum of 3 and a maximum of 5 years, which matches the body text, so the band here is reliable. Honest fit guidance: the job title says Data Scientist but the responsibilities are mostly ML engineering and deployment, not research or analysis. If you enjoy getting models into production and keeping them healthy, that is a good thing. If you want to spend your time on modelling and experimentation, read the responsibilities list again before applying.
Required by the posting: 12+ years of production level experience in one of Python, Java, Scala, C++ or a similar language. A BS or higher in Computer Science or a related field. Experience developing large scale distributed systems from scratch. Experience working on a SaaS platform or with service oriented architectures. The real day to day, as the posting frames the role: complete ownership of multiple platforms, being accountable for scalability, platformisation and reliability; designing serving infrastructure abstractions broad enough to support current and emerging use cases such as AI, determining the right tradeoffs and building consensus across the company; re architecting existing systems to handle a 10x to 100x scale increase; revolutionising platform onboarding to cut it from weeks to hours; developing features that improve product functionality and end user experience; cultivating engineering quality standards; and mentoring junior team members. The team context: the Core Experiences Platforms org in Bangalore is responsible for the main platforms used to access and interact with core assets including Workspaces, Notebooks and SQL queries, along with the serving infrastructure powering multiple user experiences. Location: Bengaluru, India, in Databricks India Private Limited. Honest fit guidance: the posting says it is seeking "exceptional technical leaders with a stellar track record", and the shape of the work backs that up: cross org consensus building, tradeoff decisions and re architecture rather than feature delivery. It is an individual contributor role, with mentoring listed rather than management, but the influence expectations are organisational. If your 12 years are deep but narrow within one team's codebase, expect the consensus and cross functional dimensions to be where interviews focus.
Required by the posting: 15+ years of industry experience building and supporting large scale distributed systems. The role as Databricks defines it: an executive engineering individual contributor with full ownership of a product or infrastructure direction in a major area, driving it from initial development through to scalable solutions with clear business impact. The posting describes the person as a force multiplier who elevates stability, reliability and organisational processes, mentors senior engineers, contributes to recruiting, and leads high impact company projects, often on problems outside their comfort zone. It reports to an Engineering Leader. The real day to day: delivering a highly scalable, available and fault tolerant engine processing hundreds of terabytes of data daily across thousands of customers; low level systems debugging and performance measurement and optimisation on large production clusters; architecture design and influencing the product roadmap; using deep experience to prevent and investigate production issues; planning and leading complicated technical projects spanning several teams; acting as a strong influencer on organisational roadmap and direction; leading a technical leadership group or similar review committee, or sustaining an engineering wide initiative; breaking complex problems into solutions, knowns and unknowns and de risking through prototyping; and contributing as a technical team lead by mentoring, leading sprint planning, delegating work and participating in project planning. Scale context worth knowing before you interview: the posting states the fleet consists of millions of virtual machines generating terabytes of logs and processing exabytes of data per day, and that at this scale cloud hardware, network and operating system faults are regularly observed and the software must gracefully shield customers from them. Location: Bengaluru, India, in Databricks India Private Limited. Honest fit guidance: read the delegation and sprint planning line carefully and decide for yourself. This is an individual contributor role by Databricks' own framing, and there are no direct reports or performance management duties in it, but the technical team lead responsibilities described are real and include delegating work and leading planning. If you want to be purely heads down at 15 years, this is not that job. If you want the largest possible blast radius without becoming a manager, it is close to the ceiling of what that looks like in India.
Required by the posting: 3+ years of experience in full stack development with strong expertise in Python and React.js. Proven experience designing, building and deploying at least one production deployed AI agent or LLM application. Deep expertise in LLM orchestration, prompt engineering and using tools and plugins to extend agent capabilities. Experience with agent frameworks like LangChain or LangGraph including implementing reasoning patterns such as the ReAct loop. Experience with observability, logging and tracing for AI agents. Experience building large scale, enterprise grade applications. Strong experience with API integration over REST or GraphQL. Experience working in Agile or Scrum environments. Preferred or good to have: Node.js or Python for middleware development, understanding of Salesforce APIs including REST, Apex and RLM/CPQ, experience with event driven architectures such as webhooks, change data capture and async processing, knowledge of CI/CD pipelines and DevOps practices, and experience with the Databricks platform and Mosaic AI. The real day to day: designing, developing and deploying AI agents for business critical workflows with a focus on LLM orchestration and tools; implementing agentic behaviours with LangChain or LangGraph including ReAct loops; building a high performance React interface for the agent; integrating APIs and services with backend teams and building tools for agents; orchestrating agent calls and data flow through Python or Node.js middleware; implementing observability and tracing for agent runs; building reusable UI components; and contributing to architectural discussions. Location: Bengaluru, India, in Databricks India Private Limited. Honest fit guidance: the years bar and the real bar are different here, and it is worth being clear about that. Three years is genuinely low for Databricks, where most of today's other India requisitions start at 10 or more. But "at least 1 production-deployed AI agent or LLM application" is a hard, checkable requirement, and the Salesforce API preference suggests this agent work plugs into internal business systems rather than the core data platform. If you have shipped an agent into production at any scale, your years matter less than that fact.
Required by the posting: a BS or above, with an M.S. or PhD preferred, in Computer Science or a related field. 10+ years of experience developing search relevance systems at scale in production or in high impact research environments. Experience applying LLMs to search relevance. Experience in one or more of query understanding, NLP, text mining, recommendations, personalisation, discovery or conversational AI. A strong understanding of computer science fundamentals. Contributions to well used open source projects. The real day to day: driving development and deployment of ML based search and discovery relevance models integrated with Databricks products; designing automated ML and NLP pipelines for data preprocessing, query understanding and rewriting, ranking and retrieval, and model evaluation, to enable rapid experimentation; collaborating with product managers and cross functional teams on the search and discovery roadmap; and building a robust framework for evaluating search ranking improvements both offline and online. The team context, in the posting's own terms: this sits in the Applied AI team, and the stated 2026 priorities are enhancing search ranking, improving query understanding, building robust evaluations and growing asset coverage. Databricks customers can hold hundreds of millions of assets, so the scale of the ranking problem is the interesting part of the job. Location: Bengaluru, India, in Databricks India Private Limited. Honest fit guidance: this is a specialist role, not a generalist senior one. Ten years of backend or general ML work without search relevance specifically will not match, because the requirement names relevance systems, ranking, and evaluation metrics as the core skill. Equally, the open source contribution line is listed as a requirement rather than a preference, which is unusual and worth taking at face value. If you have built ranking systems and can point to public work, the fit is strong.
Required by the posting (Minimum Qualifications): 5+ years of professional software development experience with meaningful time building production frontend applications in TypeScript and/or JavaScript. Browser extension development experience for Chrome, Firefox and/or Safari, with a working understanding of extension APIs, manifest versions MV2 and MV3, permission models, and the separation between content scripts, background service workers and extension pages. Strong command of core JavaScript ES6 and above plus TypeScript types, async/await, closures and modules, with a precise mental model of how the language behaves. Experience with at least one modern frontend framework or reactive UI library such as React, Vue or Svelte, and the ability to pick up new ones quickly. Proficiency with HTML5 and CSS3 including responsive, component based UIs. Plus Zscaler's standard minimum qualification on demonstrated curiosity and active use of AI tools. Preferred qualifications: having published extensions directly to a major browser store, or built extensions across multiple browser engines (Chromium, Gecko, WebKit) and reconciled their API differences; familiarity with modern frontend build tooling such as esbuild, Vite, Rollup or Webpack; and a basic understanding of web application security risks including XSS, CSRF and content isolation, plus exposure to Node.js for tooling and API integration. The real day to day: translating product requirements and UI/UX designs into well tested browser extension features spanning user facing UI through to in browser security and detection capabilities; implementing security sensitive logic that runs on every page load with minimal overhead, caring deeply about latency and memory consumption; and producing readable, modular code. Location: hybrid, Bangalore. The posting states explicitly that this is a hands on individual contributor role for someone who wants to deepen their browser platform, security and frontend engineering. Honest fit guidance: browser extension experience is the requirement that will actually filter this pool. Five years of React product work without extension internals is a weak match, because manifest versions, service worker lifecycles and content script isolation are the daily reality here. Conversely if you have shipped an extension to a store, you are in a small group and should apply even if your years are light.
Required by the posting (Minimum Qualifications): 5+ years of experience in customer facing roles with a proven blend of technical expertise and account management. Demonstrated experience leading product feature implementations and driving best practice adoption. Proficiency with operating systems including Linux, Unix and FreeBSD. Hands on experience troubleshooting network issues using tools like ping, traceroute and MTR. Solid understanding of core networking protocols including HTTP, SMTP, FTP and DNS. Preferred qualifications: experience leading discovery discussions, building high level and low level designs and managing large scale migrations; in depth understanding of enterprise infrastructure and cloud security technologies including SASE, SSE and ZTNA; and expertise in open source system administration and authentication protocols such as SAML, LDAP and OAuth. The real day to day: understanding customer goals, technical challenges and business needs to align Zscaler solutions; building relationships with key stakeholders, running periodic reviews and identifying growth opportunities; anticipating technical hurdles and providing proactive recommendations and risk mitigation; mastering Zscaler products well enough to contribute best practice content to internal and customer facing knowledge bases; and collaborating across Sales, Support and Product. Location and reporting: a hybrid role based in Bangalore, reporting to the Manager of Technical Success Management within the Customer Success department. Honest fit guidance on why this is on an engineering board: we reject sales roles with technical titles, and we check the requirement list rather than the title to decide. This one is technical from the first line, asks for hands on network troubleshooting and operating system depth, and contains no quota, revenue target or pipeline language of any kind. It manages accounts, not people, so it is not a people management role either. What it is not is a coding job. If you want to write software daily, this is the wrong seat. If you are a support, solutions or infrastructure engineer who is good with customers and wants the account relationship rather than the ticket queue, it is a strong fit.
Required by the posting (Zscaler labels these Minimum Qualifications): 3+ years of experience in software development for enterprise solutions including web based applications. Solid experience in Core Java, concurrency and distributed computing, with proficiency in SQL. Exposure to test driven development using frameworks such as JUnit, REST Assured, TestNG or Jest. Experience with HTML5, CSS3, JavaScript ES6 and above, and building responsive interfaces. Zscaler also lists demonstrated curiosity and active exploration of AI tools, with a history of integrating new technologies into daily workflows, as a minimum qualification rather than a preference, and this appears on every Zscaler posting we reviewed today. Preferred qualifications: experience developing scalable web applications handling large datasets, working knowledge of GraphQL, expertise in state management frameworks like Redux, performance optimisation including JVM tuning, and understanding of security compliance frameworks, statistics and machine learning. The real day to day: developing product features for data transformation, enrichment, analytics and user facing dashboards; designing performant web applications in ReactJS for data visualisation; building and maintaining data processing pipelines for ingestion, transformation and analysis feeding risk quantification; establishing monitoring for data platform performance and health; and working with UX/UI designers and backend engineers on end to end delivery. Location and reporting: a hybrid role based in Bangalore, India, reporting to the Senior Manager of Software Engineering in the Risk360 department. Honest fit guidance: three years is the floor across the whole of today's Zscaler set, where most other requisitions start at 5 or 8, so if you are early career and want a large security platform on your CV this is the one to aim at. Be realistic that it is a full stack job. The posting weights React and responsive interface work as heavily as the Java and SQL, so a pure backend profile is a partial fit at best.
Required by the posting (Minimum Qualifications): 5+ years of experience in C programming with a strong understanding of its core principles and performance optimisation. Hands on experience with Python and/or shell scripting for automation. Solid knowledge of Linux and FreeBSD based operating systems including process management, threading, memory management and networking. Proficiency working with AWS, Azure and GCP including creating VM images, exporting them and maintaining infrastructure. Zscaler also lists a foundational understanding of AI/ML technologies and experience leveraging, securing or positioning AI driven solutions within your domain as a minimum qualification. Preferred qualifications: experience using AI powered coding assistants and intelligent observability platforms to automate performance profiling and optimise resource utilisation; hands on experience with database internals, tuning and optimisation; and knowledge of networking concepts and protocols with hands on experience translating them into system level solutions. The real day to day: working with Linux and FreeBSD based systems including configuration and scripting for system level optimisation; creating and exporting VM images across the three major clouds; writing and maintaining automation scripts in Python or shell for infrastructure tasks, system monitoring and cloud workloads; performance profiling to identify and troubleshoot resource bottlenecks; and collaborating with senior engineers to debug system and application level issues. Location and reporting: a hybrid role based in Bangalore, reporting to the Director of Software Engineering in the Engineering department. Honest fit guidance: this is one of two Zscaler roles today at a 5 year bar and it is the more specialised of them. The requirement mix (C, FreeBSD, VM image builds, cloud infrastructure) is closer to a systems or platform engineer than to a product developer, and the job explicitly includes collaborating with senior engineers to resolve issues, which suggests a hands on contributor seat rather than an architect one. FreeBSD experience is rare enough that having it will genuinely differentiate you here.
Required by the posting: 6+ years of experience in systems programming with C/C++ preferred. Strong understanding of operating systems concepts including processes, threads, virtual memory and synchronisation. Solid knowledge of data structures, algorithms and computer architecture. Experience debugging and profiling low level code, with gdb and perf named. Familiarity with networking, storage I/O or multithreaded programming. Nice to have and explicitly not required: exposure to database internals such as query planning, indexing, storage engines and transaction processing; experience with open source database projects including PostgreSQL, MySQL and RocksDB; and knowledge of distributed systems or consensus protocols such as Raft and Paxos. The real day to day: designing, developing and optimising core components of the database engine, named in the posting as the storage layer, change data capture, connection manager and query layer; investigating and fixing complex issues around performance, memory usage and concurrency; and writing well tested, maintainable C/C++. Location and working pattern: the board lists India, the posting body names Bangalore or Pune, and it carries a hybrid tag. Confirm which of the two cities applies to this requisition before applying. What the posting offers in return, in its own framing: work on database technology used in production by large enterprises, deep technical problems, a small and highly skilled team where individual work is visible, and the chance to learn from senior engineers with database and distributed systems expertise. That last point matters if you are coming from general systems work rather than databases. Honest fit guidance: the requirement list is systems programming first and databases second, which is the same pattern as Yugabyte's other engineering roles and is good news if you have the operating systems depth but not the database background. The one thing that is not optional is comfort in C and C++ at the level where you reach for gdb and perf by reflex.
Required by the posting: 8+ years of professional software engineering experience with a strong foundation in systems programming using C/C++. A Bachelor's, Master's or PhD in Computer Science or a related field, or equivalent practical experience. Deep understanding of distributed systems fundamentals, which the posting breaks out as replication and consensus, transactions and consistency models, and fault tolerance and recovery. Experience working on storage engines, databases or other infrastructure level systems. Strong problem solving skills and the ability to operate effectively in a collaborative, distributed team. Preferred skills: hands on experience with distributed storage systems, transactional engines or consensus protocols; familiarity with LSM tree based storage engines, write ahead logs, snapshots or compaction strategies; PostgreSQL internals or other relational engine experience described as a strong plus; and prior contributions to open source systems or database projects. The real day to day: leading the design, development, testing and delivery of core storage and replication features in YugabyteDB; writing high quality C/C++ with comprehensive automated tests; participating actively in design discussions and code reviews; and troubleshooting correctness, stability and performance issues in the storage and transactions layer while collaborating with the query layer, platform and cloud teams. Location and working pattern: the board lists India and the posting carries a hybrid tag. Yugabyte's team spans 12 or more countries and multiple time zones. Honest fit guidance: "Staff" here means what it should mean. The DST team sits on consistency and durability guarantees, so the work is unusually unforgiving and the preferred list (LSM trees, WALs, compaction, Postgres internals) tells you what the interview will actually probe. If your eight years are in application or service development rather than storage and systems, the title will not carry you. If you have worked on a storage engine or a consensus implementation, this is a role where that experience is the whole point.
Required by the posting: 3 to 5 years of industry experience in a technical role. A strong technical foundation in at least two of the following: databases, distributed systems, cloud platforms (AWS, GCP, Azure), Linux/Unix administration, or programming and scripting (Python, Bash, Java and similar). Excellent problem solving and analytical skills with the ability to learn new systems quickly. Strong written and verbal communication for both technical and non technical audiences. A proactive, customer first mindset with patience and persistence. Ability to work independently in a fully remote environment while collaborating across global teams. Nice to have but explicitly not required: experience in a technical support, customer success or DevOps/SRE role, familiarity with open source and community driven projects, and knowledge of PostgreSQL or other relational databases. The real day to day: providing technically sound assistance to customers using YugabyteDB; troubleshooting distributed database, cloud infrastructure, API and application integration issues; collaborating with Engineering, Product and Documentation teams; maintaining case documentation; contributing knowledge base articles and support tooling that improve customer self service; and participating in a global on call rotation including after hours and week off support when assigned. Location, hours and schedule, all stated in the posting and all worth reading twice: the location is Remote in the APJ timezone. Work hours are aligned with early morning IST. The role requires weekend coverage, and in exchange you get two fixed, consecutive weekdays off, with Tuesday and Wednesday given as the example. If your life depends on Saturdays and Sundays being free, this specific role does not fit, however good the rest of it looks. Honest fit guidance: the posting says prior support experience is valuable but not a strict requirement, and that it is looking for technical aptitude and mindset over a support CV. That makes this one of the few realistic entry points on today's list for someone at the lower end of the range, and it is fully remote, which readers here ask for constantly. The genuine costs are the shifted hours and the weekend rota, not the technical bar.
Required by the posting: 5 to 8 years of experience with compiled languages, C or C++ specifically named. A BS, MS or PhD in Computer Science or a related field, or equivalent experience. Systems engineering fundamentals covering distributed systems, operating systems and databases, and the posting states this is a must rather than a preference. Experience with compiled languages, with C/C++ preferred and Java, Go and Rust also accepted. Listed as a plus rather than required: knowledge of database internals, compilers, and query planning or optimisation. Location and working pattern: the board lists India and the posting carries a remote tag. Yugabyte describes its team as distributed across 12 or more countries and multiple time zones. Note that other Yugabyte requisitions on this board are tagged hybrid and name Bangalore or Pune, so the remote status is specific to this one; confirm it with the recruiter before you assume it. One piece of boilerplate to ignore if you are applying from India: the posting carries a United States visa notice about H-1B sponsorship following a September 2025 proclamation. It is on Yugabyte's postings generally and has no bearing on an India based role. Honest fit guidance: the interesting detail here is that the database specifics are a plus while the systems fundamentals are a must. If you have spent five or more years in C or C++ on operating systems, networking or storage work and have never touched a query planner, this is a realistic route into database engineering rather than a wall. Yugabyte is also open source, so you can read the codebase before you interview, which is a real advantage worth using.
Required by the posting: 4+ years of experience working on a SaaS product or production platform. Strong software engineering skills with experience in distributed systems, in Go, Python or similar. Experience building cloud native services covering Kubernetes, containers, service to service APIs and CI/CD. A solid understanding of AI/ML fundamentals, and the posting is explicit that you do not need to be a researcher but should understand the concepts well enough to make sound engineering decisions. The real day to day: building and evolving backend services that power AI features, covering agent orchestration, tool execution, retrieval and RAG pipelines and model serving integrations; designing APIs and control plane workflows that are tenant aware, secure by default and observable; implementing MCP style tool discovery and integration so agents can safely call tools, connectors and internal services; engineering for reliability and scale including latency, cost controls, rate limiting, fallbacks, rollouts and incident readiness; establishing evaluation practice with offline test sets, regression detection, prompt, model and version tracking and quality gates; contributing secure by design AI work covering permissions, data access boundaries, prompt injection defences and auditability; and mentoring junior engineers. Location and working pattern: listed as India, with the requisition in SingleStore's Hyderabad office. Honest fit guidance: the phrase to take seriously is "this team is not pure research, it's engineering heavy". The hiring bar is distributed systems and cloud native services, with AI/ML understanding layered on top. If you have shipped production backend services and have taught yourself agents, RAG and evaluation properly, you are the target. If your AI experience is notebook and demo shaped, the reliability, multi tenancy and security requirements will be where it shows. Note also the security emphasis: prompt injection defence and data access boundaries are named requirements, not afterthoughts.
Required by the posting: 5+ years of experience developing and debugging system level software in unmanaged languages like C++ or Rust. A Bachelor's degree in Computer Science or equivalent practical experience. Demonstrated ability to design and build highly reliable, high performance system software. Preferred rather than required: knowledge of database architecture and operating systems, and familiarity with distributed systems managed via Kubernetes. The real day to day: developing database engine features based on company direction and customer requests; delivering code in a low level, unmanaged memory C++ environment; translating high level customer requirements into deliverable software features; learning and adapting techniques from industry and academia into SingleStore's database architecture for analytical and transactional workloads; designing and executing comprehensive engine test plans using Python, C++ and SQL; using low level debugging including GDB and flame graphs to fix problems and improve performance; working on distributed systems algorithms inside the core engine; and taking part in code and design reviews. Levelling, stated in the posting: open across multiple levels, with final levelling as Senior, Staff or Principal determined by experience, scope of impact and demonstrated technical leadership through the interview process. Location and working pattern: listed as India, with the requisition in SingleStore's Hyderabad office. Honest fit guidance: this is one of the more specialised roles on today's board. Unmanaged memory C++ plus query optimiser and SIMD work is a narrow skill set, and five years of general backend experience in Java or Python will not substitute for it. The upside is that the same posting explicitly leaves room to be levelled up to Staff or Principal, so if your systems depth is well beyond your years count, this is a posting where that can actually be recognised.
Required by the posting: 6+ years of experience developing and debugging system level software in Golang or a similar language. Familiarity with distributed systems managed via Kubernetes. Demonstrated ability to design and build highly reliable, high performance system software. Experience working in environments where performance, scalability and reliability are critical. A Bachelor's degree in Computer Science or equivalent practical experience. Preferred qualifications: experience building cloud native SaaS platforms, experience with frontend web frameworks like React, and background with cloud based metering and billing plus generally accepted accounting practices. That last one is unusual and tells you how central the billing system is to this particular seat. The real day to day: leading technical design and decision making for large, release defining projects on the cloud platform; designing and implementing capabilities across networking, control plane and managed service infrastructure with the main focus on billing systems; solving mission critical system problems; working with Product Management to turn customer and business requirements into technical solutions; investigating and resolving difficult production and development issues; debugging billing data synchronisation problems; contributing to data visualisation dashboards; and mentoring engineers on system design, coding standards and architecture. Levelling, stated in the posting: open across multiple levels, with final levelling as Senior, Staff or Principal determined during the interview process. Location and working pattern: listed as India. Unlike SingleStore's other India requisitions this one carries no office tag on the board, so confirm the working location with the recruiter before you commit. Honest fit guidance: read the billing emphasis carefully rather than skimming past it. Metering and billing is real distributed systems work with correctness requirements most services never face, but if you are hoping for database internals this is not that job. The mentoring expectation is stated as raising the technical bar across the team, not as managing people, so it remains an individual contributor role.
Required by the posting: a B.S. degree in Computer Science, Electrical Engineering, Computer Engineering or a related discipline. Deep understanding of computer science fundamentals, particularly operating systems, concurrency, multithreading and server architectures. Strong programming skills in C++ or C. A firm grasp of algorithms and data structures. A stated passion for building highly reliable software. That is the complete requirement list. There is no years of experience bar anywhere in this posting, and no prior industry experience is asked for. The real day to day: the posting names the actual projects rather than speaking in generalities. Engineers here work on cutting edge areas like LLM support and vector indexing, improving the fault tolerance of a SingleStore cluster, accelerating SQL query performance with techniques such as SIMD vectorisation and LLVM code generation, or writing the search and costing modules inside the query optimiser. The posting says its University Graduates are responsible for both brand new and existing projects that get deployed into production with each release, and that the work spans writing software through to testing it. Teams are small and collaborative, with release cycles running throughout the year. Location and working pattern: the board lists the location simply as India, and the requisition sits in SingleStore's Hyderabad office. SingleStore is headquartered in San Francisco with offices including Bangalore and Hyderabad in India. Honest fit guidance: this is the most accessible role in today's edition by a wide margin, and it is the first explicit graduate requisition this board has carried since 2026-07-30. The trade is that the bar is depth rather than years. C++ on a distributed database engine is unforgiving work, and the posting expects operating systems and concurrency knowledge you can actually use, not just coursework you can name. If you are a final year or recently graduated CS student who has written real C or C++ beyond assignments, apply. If your background is web development in higher level languages, this specific team is a stretch, and SingleStore's other India postings sit at 3 years and above.
Required by the posting: 3+ years of experience with one or more general purpose programming languages including but not limited to Python, C/C++, JavaScript or Go. Comprehension of GitOps and managing infrastructure as code. Experience with databases, particularly SQL based ones. Experience with containers and Kubernetes based applications running in public cloud or in on premises data centres, and the posting notes you will have both available to you. Deep interest and experience in distributed systems, databases, networking, storage, multi tenant services and Unix/Linux environments. A B.S. degree in Computer Science or a similar field, or equivalent working experience. The posting also asks for strong empathy toward fellow developers and a passion for quality engineering and software testing efficiency, which fits a team whose customers are other engineers. The real day to day: building observable, microservice oriented applications that let SingleStore engineers build and test in a multi cloud environment; designing technical solutions that raise engineering productivity company wide; and improving CI/CD throughput, debugging and triage operations, and workload execution runtimes for a global engineering workforce. Levelling, stated in the posting: this role is open across multiple levels, and final levelling as Senior, Staff or Principal is determined by experience, scope of impact and demonstrated technical leadership through the interview process. Treat 3 years as the entry bar rather than the target. Location and working pattern: listed as India, with the requisition sitting in SingleStore's Hyderabad office. Honest fit guidance: internal developer platform work is a genuinely good career move at 3 to 5 years because you touch build systems, cloud, Kubernetes and testing at once, but it is not product engineering and your users are colleagues. The posting is clear that it wants someone who enjoys mentoring while staying hands on. If you want to be close to the database engine itself, SingleStore's Database Engine postings are the ones to look at instead.
Required by the posting: 10+ years building systems software in C/C++ or Rust, with Go experience noted as a plus. Deep knowledge of PostgreSQL or other database engine internals, specifically storage, execution or replication subsystems. Strong understanding of concurrency, operating systems and performance engineering. A proven record of shipping large scale systems or core infrastructure features end to end. The posting adds two temperament requirements: a pragmatic problem solver with a bias for simplicity and measurable impact, and someone who thrives in a high autonomy, high velocity environment. Highly desirable rather than mandatory: experience contributing to open source databases or comparable complex systems. Given that ClickHouse itself is open source with more than 42,000 GitHub stars, a visible contribution history is worth more here than at a closed source employer. The real day to day: leading design and implementation across storage, replication, query execution and performance; contributing to and extending Postgres internals; prototyping extensions that integrate with cloud native infrastructure; profiling with low level instrumentation and benchmarking; setting engineering standards; and driving projects from concept to production with significant autonomy. Location and working pattern: India (remote). ClickHouse is a globally distributed company operating in over 20 countries with a home office allowance for remote staff. The same role is also posted for the Netherlands and the United States; this is the India requisition. Honest fit guidance: this is a genuine principal level job, not a senior job with an inflated title. The team is described as small and high talent, and the role expects you to work independently across complex areas and mentor other senior engineers. If your ten years are in application development rather than systems or database internals, the years bar will not carry you. If you have engine level work to point at, it will.
Required by the posting: 5+ years in Professional Services, Support, Technical Account Management, Engineering/SRE and/or Project Management roles, AND 5+ years of relevant industry experience implementing, operating or supporting scalable, fault tolerant distributed database management systems. Technical breadth and depth across DBMS, OLAP, cloud and SaaS platforms, distributed systems software engineering, Linux and Unix, and Kubernetes. The real day to day, as the posting itself splits it: 50 percent project engineering and consulting, meaning design, architecture, integration, implementation and documentation, plus research, benchmarking, performance and functional testing, reference architectures, sizing, migration and tooling. The other 50 percent is case initiated consultative support for strategic users, customers and prospects, covering implementation, onboarding, production launches and proofs of concept. You also handle L1 to L3 support cases when not assigned to a project, partner with Product Management, Engineering and Sales on the roadmap and account plans, produce public and internal documentation, knowledge base articles, learning content, reference architectures, blogs and benchmark results, and assist with hiring and mentoring as the team grows. Location and working pattern: India (Remote), and this requisition sits in ClickHouse's India office within the Support Services department. Two commitments the posting states plainly and you should weigh before applying: you must be available for scheduling and on call to deliver 24x7 support in a global distributed environment, and the role carries up to 35 percent estimated onsite regional travel. That is a materially different life to a desk based remote engineering job, and it is the honest reason this one sits in our customer facing group rather than the main engineering list. Honest fit guidance: this is technical delivery work with customers attached, not pre sales. The requirement list is engineering led (two separate five year bars, both technical) and there is no quota, no pipeline target and no selling language anywhere in it. If you are a support or professional services engineer with genuine DBMS depth and you want the remote flexibility, this fits. If you want to stay heads down in a codebase, the customer half will grate.
Required by the posting: solid professional software development experience in C++ including Unix systems work, strong knowledge of database internals and design, experience in performance engineering (the posting explicitly accepts adjacent fields such as high frequency trading, simulation or real time data processing rather than requiring database work specifically), strong production debugging, and willingness to work openly with an open source community, which here means resolving GitHub issues, reviewing and finishing community pull requests, and answering questions on mailing lists, chats and external Slack channels. Nice to have, listed as bonus points: prior ClickHouse experience, security, privacy and compliance exposure, TCP/IP and network programming, cloud infrastructure work with Kubernetes, public speaking at technical conferences, and previous open source contributions. The real day to day: analysing and optimising the core database, extending performance tests against real world and synthetic datasets, assessing the performance impact of new features from other core teams, and acting as an escalation resource for Support Engineering. Location and working pattern: the board lists this as India (remote), and the posting adds that the role can be located anywhere ClickHouse has a hiring presence. ClickHouse describes itself as a globally distributed, remote friendly company operating in over 20 countries, and offers a home office setup allowance to remote employees. ClickHouse posts this same role separately for the United States, United Kingdom, Germany and the Netherlands; the requisition linked here is the India one. Honest fit guidance: this posting states NO years of experience anywhere, which is why our experience filter cannot place it. Do not read that as an open bar. The requirement set (C++ plus database internals plus performance engineering) is a senior profile in substance, and the compensation section is written for United States salary bands, so the level is set by what you can demonstrate rather than by a number. If you have shipped low level optimisation work you can point at, apply regardless of your years.
Required by the posting: 6+ years in software engineering, ideally building or operating database or cloud platform systems. Deep Postgres understanding across configuration, extensions, operations and performance tuning. Strong programming in one or several of Ruby, Go, Rust, C or Python, plus a stated willingness to work across languages rather than stay in one. Familiarity with cloud infrastructure, APIs and automation tooling (Terraform, Kubernetes, CI/CD). Understanding of distributed systems, data replication and service orchestration patterns. The posting also asks for a specific mindset rather than more tools: pragmatic and detail oriented, comfortable with both greenfield development and operational ownership, and happy to contribute wherever needed, from backend APIs and platform automation through to Postgres internals and debugging. The real day to day: designing backend services that orchestrate database clusters in ClickHouse Cloud, extending the control plane for new Postgres capabilities, contributing to Postgres extensions and data plane agents, building provisioning and scaling automation, developing APIs and integrations, improving observability and debugging workflows, and participating in design discussions, code reviews and on call rotations. Location and working pattern: India (remote). ClickHouse is a globally distributed, remote friendly company operating in over 20 countries and provides a home office setup allowance for remote employees. The same role is posted separately for the Netherlands and the United States; this is the India requisition. Honest fit guidance: the posting describes itself as a flexible, full stack systems role where boundaries are fluid. If you want a narrow, well bounded backend brief, this is not it. If your Postgres knowledge is operational rather than internals deep, you can still be credible here, because the control plane and automation half of the job is as large as the extensions half. Apply if you are at 6 years or beyond and can show real Postgres depth.
Required by the posting: 7+ years in SRE, DevOps or infrastructure engineering with a track record of running distributed, production grade systems. Solid Postgres operations, scaling and performance tuning. Deep hands on AWS with exposure to GCP and Azure, and comfort navigating multi cloud topologies. Proficiency with Terraform, Kubernetes and container based infrastructure. Strong Go development skills, or a stated willingness to write and own production Go. Familiarity with observability tooling such as Prometheus, Grafana, Loki or OpenTelemetry. Deep understanding of SLOs, incident response and continuous reliability improvement. The real day to day: leading reliability and operations for the Postgres integration including upgrades, patching, maintenance and scaling; designing provisioning, deployment and lifecycle automation across the three major clouds; writing infrastructure as code; contributing Go tooling; owning alerting, metrics and tracing; driving incident management and postmortem practice; and mentoring engineers as the team scales. Location and working pattern: India (remote). ClickHouse operates in over 20 countries and provides a home office setup allowance to remote employees. The same requisition also exists for the United States; this is the India one. Honest fit guidance: the posting asks for a "founder's mentality" and describes the role as hands on and high impact, which in practice means the automation, the code and the on call are all yours rather than split across a platform team. If you are an SRE who mostly operates other people's tooling and does not write production Go, expect that to be the gap they probe. Postgres operations depth is the other hard requirement and is harder to fake than the cloud list.
Added July 30, 2026
Required by the posting: a Bachelor's or Master's degree in Computer Science, Computer Engineering or an equivalent field. Understanding and working proficiency in Python, C and C plus plus. Knowledge of networking, operating systems and security. Understanding of unit and integration testing, and the ability to write, debug and deploy testing frameworks. Experience with traditional relational databases such as MySQL, Postgres or Oracle. A keen interest in software development evidenced by side projects, ideally including open source contributions. Desired, not required: Scala, Spark or Java. The day to day, as the posting describes it: work in a small team, do detailed peer code reviews, tackle distributed computing problems, help build continuous integration and delivery on managed AWS services, operate your team's services in production, write unit, integration and load tests, and build monitoring and alerting. Location reality: the posting says this role is remote and based in India, but it names five states only, Karnataka, Tamil Nadu, Telangana, Maharashtra and New Delhi. If you live outside those, check before you invest time in the application. Twilio describes itself as remote first. Who should apply: final year students and recent graduates. The posting states plainly that not all applicants will match the description exactly, that Twilio values experience from other industries, and that people whose careers are just starting or have not followed a traditional path are encouraged to apply. It also says the company uses AI in its hiring process while every hiring decision is made by a person. There is no years of experience bar anywhere in this posting, which is what makes it worth your application if you are at zero.
Required by the posting: 2 to 4 years of experience in software testing, quality assurance or software development. Experience testing web applications, both manually and with automation. The ability to analyse product requirements, technical specifications and user stories, and turn them into adequate test coverage. The day to day: design, develop, execute and maintain test cases and test scripts across functional, regression, integration and system testing. Maintain test documentation, test data, and traceability between requirements and coverage. Work with software engineers and product managers on quality for new and existing functionality. How Tekion frames the level: the posting says this role performs moderately complex testing and quality engineering work across multiple features or components, balances manual and automated testing, identifies risks proactively, and contributes to quality improvements supporting team level delivery. That is an honest description of a second rung QA engineer, not a lead. Location: Chennai. Tekion is also hiring a similar Software Development Test Engineer II in Bengaluru, but that Bengaluru posting asks for 4 or more years, so this Chennai one is the lower bar of the two. Same title, different floors, which is worth knowing before you pick. Who should apply: SDETs and QA engineers two to four years in who can write automation and want product company scale. Tekion does not publish office days on this posting.
Required by the posting: 2 to 4 years of experience in site reliability engineering, and a B.Tech or M.Tech in computer science, information technology or a related field. Experience working for a product organisation is listed as a plus rather than a requirement. Technical ground the posting covers: containerisation with Docker and orchestration with Kubernetes. Monitoring and logging with tools such as Prometheus, Grafana and the ELK stack. Load balancing. Incident response, troubleshooting and resolution. The day to day, in the posting's own framing: designing, implementing and maintaining scalable and reliable infrastructure. Developing automation tools and scripts to cut manual intervention. Monitoring system performance and responding to incidents quickly to minimise downtime. Analysing usage patterns and forecasting capacity. Identifying and fixing performance bottlenecks. Location: Hyderabad, and the posting lists Hyderabad as the only location. Team is Engineering, department is the CTO Office. Zeta does not state office days or shift pattern on this posting, which matters for an SRE role, so ask about the on call rota at the first interview. Who should apply: engineers two to four years into SRE, DevOps or systems work who already have Kubernetes and observability tooling in their hands and want financial infrastructure scale. Note Zeta is also hiring a Senior SRE at 4 to 6 years and a SIEM and SecOps Engineer, so if this one is slightly under your level the adjacent posting may fit better.
Required by the posting: a bachelor's degree in technology or a related field, and a minimum of 2 or more years of professional experience. Sigmoid's own job metadata records the band as 2 to 5 years. Hands on experience with Node.js and related frameworks such as Express.js or NestJS. Strong grounding in data structures, algorithms and backend design. The day to day: build server side applications that are efficient and reusable. Design and build scalable backend services and APIs for the Product Engineering division. Explore and design data driven experiences for cloud based products. Work closely with product managers, designers and frontend developers. Take part actively in design and code reviews. Location: Bengaluru. The posting does not state office days. Who should apply: backend engineers two to five years in whose main language is JavaScript or TypeScript on the server. Because Sigmoid's core business is data engineering, this is a good route in if you eventually want to move toward data platform work but are currently strongest in application backends. If your strength is Python and Spark instead, Sigmoid's Software Development Engineer II role in the same city is the better fit, and it is also on today's list.
Required by the posting: a track record of relevant work experience with a computer science or related technical discipline, which Sigmoid's own job metadata records as 3 to 5 years. Hands on coding experience in Java, Python, C plus plus or Scala. Experience with functional and object oriented programming, with Python or Scala specifically called a must. Experience in application development and support, integration development and data management. Experience designing APIs, abstractions and integration patterns for distributed computing problems. Experience defining technical requirements, extracting and transforming data, automating and productionising jobs in a parallel processing environment. Preferred, not required: technical knowledge of Spark, Hadoop and the Google Cloud storage stack. Vertica, Snowflake or Druid are named as a plus. The posting also asks for a strategic thinker able to think unconventionally, and notes that this position sits on a growing team building large scale big data architectures. Location: Bengaluru, stated in the posting body. Office days are not published. Who should apply: data engineers three to five years in who write Python or Scala daily and have run pipelines in production. Sigmoid's client work means exposure to several industries rather than one product, which is a real advantage early on and a real drawback if you want to own a single product for years. Its Software Development Engineer III role, also on today's list, is the 6 or more year version of this job.
Required by the posting: 3 to 5 years of experience, stated explicitly as Experience Required 3 to 5 years. A bachelor's or master's degree in computer science, artificial intelligence, data science or a related discipline. Hands on experience with ML frameworks such as TensorFlow, PyTorch or Hugging Face. Experience with big data tools and frameworks such as Spark or Hadoop. Preferred, not required: experience with advanced concepts including federated learning, GANs and transfer learning. The day to day: lead the design, development and deployment of scalable AI and ML systems. Own the end to end lifecycle of AI models, from research and development through production and monitoring. Mentor and guide junior engineers on AI concepts. Work with stakeholders to build scalable and robust AI applications. Location: Pune, which is Druva's main engineering centre. Office days are not stated on this posting. Who should apply: ML engineers three to five years in who have actually put a model into production and monitored it there, rather than only trained models in notebooks. Do not be put off by the Staff title: Druva's other openings on today's list, all Senior Staff Software Engineer, ask for 5 to 7 and 6 or more years, so the title ladder at this company sits lower than the same words do elsewhere. The mentoring line is about technical guidance, not managing people: there is no team to run in this role.
Required by the posting: 3 or more years of experience in DevOps, SRE or cloud infrastructure engineering roles. Strong experience with Terraform, Docker, Kubernetes and Linux, specifically Ubuntu. Experience implementing ArgoCD, Jenkins or other CI and CD orchestration tooling. Experience working with multi cloud or hybrid environments. The day to day: design, build and maintain CI and CD pipelines for every HackerRank environment from development to production. Optimise the performance and utilisation of Redis, RDS, Redshift, ElasticSearch and Kafka. Evolve cloud infrastructure and observability frameworks across environments. What the posting says makes someone succeed here: a builder's mindset that automates processes, simplifies workflows and gives other engineers better tools, and genuine interest in reliability, scalability and developer experience. Location: the posting is titled Hybrid in Bangalore, India, so expect a mix of office and home without a stated number of days. Who should apply: DevOps and SRE engineers three or more years in who want to own infrastructure decisions rather than execute tickets. No upper limit on years is stated, so more senior candidates are not excluded by the posting, but the title is Engineer II and the band starts at three years, so calibrate your expectations on scope accordingly.
Required by the posting: a BTech, MTech or equivalent in computer science, data science or a related discipline, and 4 to 6 years of industry experience with a proven track record of ownership and delivery. The day to day: design, implement and optimise the agentic AI platform, which the posting breaks down as the agent harness, proprietary tools that work over big data, the orchestration layer for multi agent long running tasks, and integrations to third party tools. You would join a small, cross geo team and are expected to define scope, set milestones and ship incremental, well tested improvements. The two problems the posting frames the role around: building backend systems that reliably ingest, manage and process petabytes of heterogeneous, high volume data, and building the intelligence that reasons over that data to deliver real time insight. It states plainly that agent orchestration at their scale is highly complex and that long running multi agent tasks bring their own reliability problems. Location: the posting header says Bangalore or Noida, the job is listed in Noida, and Sumo Logic's own posting metadata records the office requirement as Hybrid. Who should apply: backend engineers four to six years in who are strong on distributed systems and want real agentic AI work rather than a wrapper around an API. Sumo Logic also has two SRE roles on today's list, at 4 to 6 and 8 or more years, if reliability is closer to your background.
Required by the posting: 4 to 6 years of sysadmin experience handling large scale distributed system software deployments, in cloud or on premises. A BS degree in computer science or a related technical field involving coding, or equivalent practical experience. The full technical list the posting names: MySQL or PostgreSQL. Observability tools and practices, specifically Prometheus and Grafana. Troubleshooting and resolving incidents. AWS, preferred, including hands on work with the AWS CLI. Orchestration and containerisation with Kubernetes and containers. CI and CD with Jenkins or ArgoCD. Linux and shell or Python scripting. Programming in Python and Go. API gateways such as Kong or Nginx based systems. Security best practices and technologies. The day to day: understand arising issues and overall application performance by building monitoring solutions. Analyse current systems consistently and reduce existing problems, suggesting solutions to upgrade and refine them. Provide support across monitoring, process and tooling, architecture and root cause analysis. Develop and maintain monitoring and alerting to detect issues proactively. Automate routine tasks. Troubleshoot and resolve incidents and outages. Location: Hyderabad, in the Global SRE department. Zeta also lists a Senior Site Reliability Engineer seat in Bangalore. Office days and on call rota are not published, so ask early. Who should apply: SREs and infrastructure engineers four to six years in with real AWS and Kubernetes depth. If you are earlier than that, Zeta's Site Reliability Engineer II role at 2 to 4 years is also on today's list.
Required by the posting: 4 to 6 years of experience in a cloud native SaaS environment with demonstrated depth in at least two security domains, and the posting names AppSec plus cloud security as the preferred combination. Prior experience at a product startup or high growth company is valued. Hands on production experience building AI agents is stated as required, not optional, for the AI portion of the role. The three areas of work the posting sets out. First, AI powered security agents: build agents that handle vulnerability triage, automated security review of pull requests, and initial incident forensics at scale. Second, cloud security automation: build systems that automatically detect and remediate configuration drift, IAM misconfigurations, vulnerable dependencies and exposed secrets across AWS as primary, plus GCP and Azure, owning it end to end rather than only the detection layer. Third, developer security or shift left: integrate SAST, SCA and secrets detection into CI and CD so secure by default is the path of least resistance for every engineer. Location: the posting lists India and Atlan's own board metadata marks it remote, employment type full time. Who should apply: security engineers four to six years in who write real code and would rather build the fix than raise the finding. If you are further along, Atlan's Senior Security Engineer for Corporate Security at 5 or more years is also on today's list and is a broader ownership role.
⚠️ The posting states two different experience floors in the same list: 4 or more years of experience developing large scale internet or SaaS applications, and 2 to 3 years of overall experience as a web or mobile application security engineer or developer. We have published the higher figure rather than the flattering one, but if you have 2 to 3 years of application security behind you, this posting arguably describes you and is worth an application. It also asks for a BE, B.Tech, M.Tech or ME in computer science or equivalent, and specifies a Tier 1 engineering college or university, which is a real eligibility filter rather than a preference. The skills the posting lists: hands on VA and PT experience across web, mobile, SDK, API and network. Thorough understanding of the OWASP Top 10 and their attack and defence mechanisms. Exposure to secure SDLC, threat modelling and secure coding. Commercial and open source tooling including Burp Suite, AppScan, OWASP ZAP, BEEF, Metasploit, Qualys, Nessus and Snyk. Identifying and exploiting business logic vulnerabilities. Cryptography, PKI based systems and TLS. Authentication and authorisation frameworks including OIDC, OAuth and SAML, with the ability to read and write Java. Static analysis and code review with Snyk, Veracode, Checkmarx or SonarQube. Reversing mobile applications with Dex2jar, adb, Drozer, Clang and iMAS, and dynamic instrumentation with Frida or Objection. Penetration testing on internal and external networks, Windows, Linux and AWS infrastructure. Shell scripting or automation in Python or Ruby. Knowledge of PCI DSS, PCI SSF, UIDAI, GDPR and NIST. Java frameworks including Spring Boot, plus CI and CD and Jenkins. Cloudflare WAF rule tuning, traffic and event monitoring, and bot traffic analysis. The posting also states you must have participated in bug bounty programmes such as HackerOne or Bugcrowd. The day to day: guide security and privacy initiatives through design reviews and threat modelling, harden applications built by other teams, and define and hold the scope of security work from project initiation through maintenance. It is explicitly an individual contributor role reporting to a manager. Location: Hyderabad only. Who should apply: application security engineers with real offensive testing experience and bug bounty history, who can read code rather than only run scanners.
Required by the posting: 4 or more years in Linux and Unix administration with extensive hands on experience in the field. The title states the band as 4 to 8 years. Effective work with MySQL databases, with working experience in MariaDB or Percona named as a plus. Coding and scripting skills, with a stated preference for Perl, Python or Go. Experience with automation and configuration management using tools such as SaltStack. Hands on experience with private cloud environments. Experience implementing cloud services on Linux using KVM or QEMU. Experience with data centre related activities. Location: Bengaluru, and the posting names the site as Salarpuria Softzone. Requisition type is full time regular employee. Benefits the posting lists in full, which is rare enough to be worth repeating: insurance benefits, an employee assistance programme, an onsite medical centre and an emergency support system under wellness, plus relocation benefits, a transfer support policy and a travel policy under mobility. Who should apply: systems and infrastructure engineers four to eight years in whose depth is Linux internals, virtualisation and databases rather than managed cloud services. If your entire background is AWS or GCP consoles, read the KVM, QEMU and data centre requirements carefully before applying, because private cloud operation is the core of this job. Note that PhonePe advertises several reliability roles with overlapping descriptions, so check the requisition you are applying to rather than assuming they are interchangeable.
Required by the posting: 5 or more years of experience designing and developing highly available, high scale, secure, mission critical cloud native enterprise distributed systems. Hands on experience with cloud native infrastructure, AWS preferred, microservices patterns, and building highly resilient systems. Practical experience using AI tools such as Copilot, Claude or Cursor to accelerate software delivery. Experience building and maintaining high volume public facing APIs with a focus on developer experience. Experience with high throughput data processing and storage, named as SQL or NoSQL, Redis, Kafka or Spark. Infrastructure as code. Demonstrated ability to influence technical decisions within your team through communication and technical credibility. Desired, not required: experience building internal platforms that help other developer teams move faster. The day to day: own technical strategy for a platform processing millions of requests. Drive the design and implementation of key features. Make architectural decisions that balance rapid feature innovation against reliability and security. Articulate designs and system trade offs through design documents, RFCs and discussion. Use LLMs and agentic tooling to accelerate code generation, automate architectural review and synthesise context. Location: the posting says this role is remote and based in India, and it names five states explicitly: Karnataka, Tamil Nadu, Telangana, Maharashtra and New Delhi. If you live outside those, check with the recruiter before investing in the process. Twilio describes itself as remote first. The posting also lists benefits including generous time off, parental and wellness leave, healthcare and a retirement savings programme, noting that offerings vary by location. Who should apply: senior backend and platform engineers five or more years in who are comfortable being measured partly on how well they use AI tooling, since the posting is unusually direct that this is part of the job rather than a nice to have.
Required by the posting: 5 or more years of experience building complex backend or distributed systems at scale. The day to day: design, build and evolve the backend systems that power Postman's identity and authentication platform. Own projects end to end, which the posting spells out as clarifying requirements, driving technical design, implementing, managing rollout and supporting in production. Work closely with product, design and engineering to scope, build, test and launch new features and platform improvements. What the team owns, per the posting: authentication, session management, access control, service accounts, invites and other foundational identity capabilities. The work is described as a mix of core platform improvements, new product capabilities and hardening, and the posting notes the identity layer sits on the path of every authenticated request and enables users, teams and systems to access Postman securely. Location: Hyderabad for this posting. Postman is headquartered in San Francisco with offices in Boston, New York, Austin, Tokyo, London and Bangalore, where it was founded. Office days are not stated on this particular posting, and other Postman postings have carried a Bangalore specific office policy that does not apply here, so ask rather than assume. Who should apply: backend engineers five or more years in who have worked on authentication, authorisation or another platform component with a blast radius covering the whole product. If you have implemented OAuth or SAML flows in production, or run a session store at scale, say so prominently in your application.
Required by the posting: 5 or more years of hands on security engineering experience in corporate or enterprise security, covering endpoint, network, SaaS, identity or a combination of these. The posting states you need to have done this before, specifically deployed and operated the core corporate security stack, made architectural calls on tooling, and built engineering driven solutions rather than manual processes. The day to day: design, build and operate the security controls for Atlan's corporate environment, which the posting lists as the macOS fleet, SaaS applications, corporate identities via Okta and Google Workspace, email, endpoints and the network edge. Evaluate, select, deploy and operate the corporate security stack: EDR and XDR, MDM, ZTNA, CASB and SSPM, email security, DLP and browser security, owning vendor selection, proofs of concept, deployment, tuning and lifecycle management. Provide technical direction to the IT Operations team on security matters. Partner with infrastructure security, detection and response, GRC and legal. The role reports into security leadership. Location: India, and Atlan's board metadata marks the role remote, employment type full time. Who should apply: security engineers five or more years in who have personally rolled out and run an EDR, an MDM and an identity provider, not just audited them. The posting says the role is high visibility with a lean team, which in practice means broad ownership and no one to delegate to, so it suits someone who wants scope and is comfortable being the technical authority.
Required by the posting: 5 to 7 years of experience, preferably at a product company, building global scale distributed SaaS applications that handle petabytes of data. Hands on experience designing and developing complex products. Extensive hands on experience in Go, Python, C, C plus plus or Java on Unix and Linux platforms. A strong understanding of computer architecture, data structures, algorithms, design concepts and programming practices. Data modelling for OLAP workloads, scalability design and query optimisation. An AI first mindset to software development, with experience using generative AI across the development lifecycle from design to code to test, using tools such as Cursor. Excellent communication, since the posting notes you would work with product management to refine requirements. What the team builds: the Foundation team designs a highly performant and scalable cloud file system on Druva's cloud in AWS. The posting describes it as petabyte scale, distributed and service oriented, turning on file system metadata, versioning and eventual consistency. Location: Pune. Office days are not stated. Who should apply: systems engineers five to seven years in who want storage and file system internals rather than application work. Note Druva's title ladder: this Senior Staff role asks 5 to 7 years while another Senior Staff posting asks 6 or more, and its Staff Software Engineer (AI) role asks only 3 to 5. Judge by the years line, not the title.
Required by the posting: 6 or more years of experience, preferably at a product company. Extensive hands on experience in Go, Python, C, C plus plus, Java or .NET on Unix, Linux or Windows platforms. Excellent programming skills alongside data structures, algorithms and design concepts. Strong experience with service oriented architecture. Experience with cloud technologies, AWS or Azure. Hands on experience with generative AI based development, with Cursor and Windsurf named. Preferred, not required: experience with third party API integrations at scale. The day to day: be the technical leader building enterprise grade scalable, performant systems. Own the design and implementation of the software modules a team owns, focused on backend server side components and on keeping responsiveness high under request load. Design and implement sufficiently large and complex features, or architectural improvements to the product. Context from the posting: the team sits in the Cloud Apps organisation in Pune and provides architectural components supporting the core operations of multiple SaaS application workloads. Location: Pune. Office days are not stated on this posting. Who should apply: backend engineers six or more years in who want platform ownership, where your users are other engineering teams inside the company. Druva has three roles on today's list at 3 to 5, 5 to 7 and 6 or more years, so there is a rung for most mid to senior backend engineers, and the titles are not a reliable guide to which is which.
Required by the posting: 6 or more years of experience, recorded in Sigmoid's own job metadata as a 6 to 9 year band. An engineering bachelor's or master's degree in computer science or IT. Hands on coding experience in Java, Python, C plus plus or Scala, with hands on experience in core Java or Scala named separately. Strong work experience in technical development, which the posting clarifies in brackets as coding. Technical expertise in the big data space: Apache Spark, Kafka, Flink, the Hadoop stack including MapReduce, HDFS, Hive, HBase, Flume and Sqoop, and NoSQL stores such as Cassandra and HBase. Experience in application development and support, integration development and data management. Experience designing APIs, abstractions and integration patterns for distributed computing problems. Experience defining technical requirements, data extraction and transformation, automating and productionising jobs, and exploring new big data technologies in a parallel processing environment. Work experience with third party libraries and frameworks. The posting also asks for a strategic thinker able to think unconventionally, the same phrasing Sigmoid uses on its mid level posting. Location: Bengaluru. Office days are not published. Who should apply: data engineers six to nine years in who want to stay technical. Sigmoid is a services and solutions company, so the work spans client industries rather than one product, which suits engineers who like variety and frustrates those who want to own one system for years. Its 3 to 5 year and 2 to 5 year engineer roles are also on today's list if this band is above you.
Required by the posting: 6 to 8 years of software engineering experience, ideally at scalable product companies. Proven ownership, which the posting defines as end to end delivery, production debugging and mentoring more junior engineers. Solid code quality, testing and design practices. A degree in computer science, IT or a related engineering field is preferred but explicitly not required, and the posting says work outcomes are weighted most heavily. The day to day: own end to end delivery of features and services, from design through production operation. Design scalable, reliable distributed systems and drive key technical decisions. Raise code quality and design standards through thorough, constructive code review. Collaborate across product, design and other teams. ⚠️ Location, and read this before applying: the job board entry says India Remote, while the posting body says Location: Bangalore, India, In-office, Hybrid. Those contradict, and the body is the more specific of the two, so plan for Bangalore hybrid and confirm with the recruiter if remote is what you need. Turing itself is based in San Francisco. Who should apply: engineers six to eight years in who want breadth and ownership at a company whose core business is AI research support and enterprise AI deployment. The posting's own framing is a high ownership individual contributor role with mentoring attached, not a management step, and the degree requirement being waived in writing is worth noting if your path was non traditional.
Required by the posting: a minimum of 7 years of relevant experience designing, analysing and troubleshooting large scale distributed systems. Deep hands on experience with C, Java, GoLang, Python, Terraform, Ansible, Python automation, networking, Kubernetes and AWS cloud. Proven experience in observability, building complex dashboards, managing Grafana, and a sharp understanding of SLIs, SLOs and error budgets. Modern DevOps expertise. Web protocol depth. Demonstrated curiosity and active exploration of AI tools, with a history of integrating new technology into daily workflows, which Zscaler states as a requirement rather than a preference across its postings. The day to day: design, implement and manage advanced cloud management automation to eliminate toil and accelerate delivery. Own cloud operations, deployments, on call support and incident management. Continuously design and tune Linux and BSD based systems. The role reports directly to the Director of Site Reliability Engineering on the SRE Cloud Infrastructure and Operations team. Location: Hyderabad. Division is Engineering, region India, employment type full time employee. Who should apply: SREs seven or more years in with real distributed systems debugging depth and at least one systems language in their hands. The on call responsibility is stated in the posting rather than buried, so weigh it. If you have FreeBSD or other BSD operational experience, this is one of the few postings where it is an explicit advantage rather than trivia.
⚠️ What the posting states about experience: 8 or more years of professional experience in an applied software security role. That line sits in an otherwise entirely site reliability focused posting, and Sumo Logic's Senior Site Reliability Engineer I posting is identical apart from asking 4 to 6 years of industry experience, so the security wording reads like a copy and paste from another requisition. We have published 8 years because that is the figure the posting actually states. If your background is SRE rather than security, apply anyway and ask about it. Also required: a bachelor's or master's degree in computer science, electrical engineering or another scientific or technical discipline. Cloud native application development experience using best practices and design patterns. Strong debugging and troubleshooting across the whole stack. Deep understanding of AWS networking, compute, storage and managed services. Competency with Kubernetes, Terraform, Ansible and Jenkins. Experience with full lifecycle support of services from creation to production support. Infrastructure as code using Terraform or CloudFormation. The ability to author production ready code in at least one of Java, Scala or Go. Linux systems experience and comfort on the command line. Modern approaches to cloud native software security. Experience with agile frameworks such as Scrum and Kanban. The day to day: own availability for your product area. Participate in on call rotations, then work to improve the on call experience and reduce operational workload for microservices. Complete projects that optimise and tune the on call experience for engineering teams. Improve the lifecycle of microservices and architectural components from design through operation. Location: the posting says Noida or Bangalore, hybrid, and Sumo Logic's metadata records the office requirement as Hybrid. Who should apply: senior SREs eight or more years in who want ownership of reliability roadmaps and are comfortable in an on call rotation.
Required by the posting: 8 or more years of experience in software development. Proficiency in one or more of Go, which is preferred, Java, C, C plus plus or Python. Experience in performance engineering, specifically developing high throughput, low latency systems. Experience with continuous integration, writing testable code and test driven development. The day to day: design and develop privacy APIs and the backend infrastructure supporting large scale data and privacy workflows. Contribute to performance engineering so transactions stay low latency and high throughput at scale. Participate in building and implementing effective test strategies, and develop software with high agility and zero downtime. What the product is, in the posting's framing: a state of the art SaaS solution that lets enterprises govern and protect sensitive data. Skyflow describes itself as the runtime AI data control layer its customers use to protect sensitive data and deploy AI safely, trusted by Fortune 500 enterprises and leading SaaS companies across financial services, healthcare, retail, travel and hospitality. Location: India, and Skyflow's board metadata marks the role remote, employment type full time. Headquarters is Palo Alto, California, and the company was founded in 2019. Who should apply: senior backend engineers eight or more years in, ideally writing Go, who have genuinely optimised latency and throughput rather than only scaled horizontally. If remote work is what makes a job possible for you, this is the strongest remote backend option on today's list.
Required by the posting: 5 or more years in a technical, customer facing data or analytics role, and the posting names implementation, solutions or sales engineering, analytics engineering and data consulting as qualifying backgrounds. Separately it asks for at least 5 years of customer facing technical experience with a demonstrated record of engaging enterprise accounts. Working knowledge of customer data platforms and event pipelines, specifically Segment, mParticle and RudderStack. A solid grasp of event taxonomy design and data governance principles. The day to day: develop mastery of Amplitude's products so you can give customers strategic help with data audits and taxonomy cleanup. Help customers map the data flow architecture between Amplitude and upstream sources including Segment, mParticle, Snowflake, BigQuery and RudderStack. Collaborate with Amplitude's product, engineering, platform support and technical success manager teams to streamline internal processes and improve the data management experience for customers. Location: Bengaluru, supporting global customers, which usually implies some overlap with other time zones. Office days are not stated on the posting. Who should apply: analytics engineers, implementation consultants and solutions engineers five or more years in who can hold a technical conversation about event schemas and a commercial one about account outcomes in the same meeting. If you have run a Segment or RudderStack implementation end to end, lead with that.
Required by the posting: 5 or more years of hands on industry ML experience in at least one of two tracks. As an ML engineer, building and maintaining production grade cloud infrastructure on AWS, Azure or GCP supporting ML application deployment, including drift monitoring. As an AI engineer, experience with current LLM and agentic system techniques including vector databases, fine tuning LLMs, AI guardrail systems, and deploying LLMs with tools such as HuggingFace, LangChain and OpenAI. A graduate degree in a quantitative discipline such as computer science, engineering, statistics or operations research, or equivalent practical experience. Experience communicating or teaching technical concepts to both technical and non technical audiences. Preferred, not required: 2 or more years of customer facing experience in a pre sales or post sales role. Note the direction of that requirement, since it means deep ML skill with limited customer facing time is acceptable, but the reverse is not. The day to day: act as the trusted technical ML and AI expert to Databricks customers and to the field engineering organisation. Work with solution architects to guide customers in architecting production grade ML and AI applications on Databricks. Build, scale and optimise customer AI workloads and apply MLOps to productionise them across a variety of domains. Location: the posting states plainly that this is a hybrid role based in Bengaluru. The hiring entity is Databricks India Private Limited and the posting category is Field Engineering. Who should apply: ML and AI engineers five or more years in who enjoy customer work. It is a customer facing seat, so travel and meetings replace some build time, but the technical requirement is hands on rather than presentational.
Required by the posting: 8 or more years of experience in customer facing technical roles, including 3 or more years driving value specifically in technical account management, customer success, solutions delivery or sales engineering, within the cloud, web security, networking or infrastructure domains. Strong technical acumen, with the ability to align a customer's business challenges to the Zscaler portfolio for the security outcomes they want. The day to day: build and maintain relationships with key customer stakeholders and operational service owners across a complex portfolio of accounts, defining and prioritising alignment between customer objectives and Zscaler's. Offer expert technical guidance, proactive recommendations and technical governance, and develop customised strategies for integrating and operationalising Zscaler. Drive adoption by identifying actionable insight, anticipating technical hurdles and building risk mitigation plans. Provide technical expertise and organisational leadership on complex escalations, coordinating resolutions across sales, support and product teams. Reporting line and level: the posting states this is a hybrid role based in Mohali or Bangalore, reporting to the Manager, Technical Success in the Customer Success department. Despite Manager in the title, no people management is described anywhere in the posting. Who should apply: technical account managers, customer success engineers and solutions delivery people eight or more years in with genuine networking or web security depth. This is a customer facing commercial adjacent role rather than an engineering one, and we list it in its own group for that reason, but the technical bar is real and it is the exact title readers asked us to find.
Required by the posting: 8 or more years of professional experience building machine learning models and systems. 1 or more years of hands on experience with how LLMs work and with generative AI techniques, specifically prompt engineering, RAG and agents. Expert proficiency in Python, LangChain or LangGraph, and SQL, which the posting states is a must. Experience driving an engineering team toward a technical roadmap. The day to day: lead the design, training, fine tuning and deployment of large language models, using prompt engineering, retrieval augmented generation and agent based architectures. Maintain high quality, efficient code in Python, with LangChain and LangGraph named, and SQL, focusing on reusable components, scalability and performance. Work closely with product owners, data scientists and business subject matter experts to define project requirements, translate technical detail and deliver AI products. Note on the roadmap line: driving an engineering team toward a technical roadmap here reads as technical leadership rather than line management, since no hiring, performance or reporting responsibility appears anywhere in the posting. Location: Bengaluru. Turing itself is based in San Francisco. Office days are not stated on this posting. Who should apply: ML engineers eight or more years in who have shipped LLM systems into production and are comfortable working in front of a customer. Turing also lists a Principal Forward Deployed AI Engineer at 8 or more years with 4 to 6 of that in AI and ML specifically, so if you are further along, look at that one too.
Required by the posting: 10 or more years of transactional database, OLTP, expertise spanning engineering, product development, administration and pre sales, with a track record of designing and delivering client facing solutions. 6 or more years in a customer facing pre sales or consulting role influencing technical executives and driving data strategy and product adoption. Experience architecting solutions that integrate transactional data systems into broader big data, lakehouse and AI ecosystems. Hands on experience building solutions in major public clouds, AWS, Azure or GCP. Broad understanding across two or more of data engineering, data warehousing, AI, ML, governance, transactional systems, application development and streaming. Experience collaborating with global system integrators and third party consulting organisations. The day to day: collaborate with go to market leadership and account teams to design and execute engagement strategies across your territory. Serve as an expert solutions architect and technical champion, building credibility with stakeholders to drive product adoption. Be clear eyed about the shape of this job: pre sales and territory work are named in the requirements, so it is customer facing and commercially adjacent rather than an engineering seat. We keep roles like this on the list only when the technical requirement is real, and here it is a decade of OLTP depth plus hands on cloud building. Location: Bengaluru. The hiring entity is Databricks India Private Limited and the posting category is Field Engineering. Who should apply: database engineers and architects ten or more years in, with deep OLTP background, who already enjoy the customer facing half of the work.
Added July 29, 2026
HackerRank publishes no years of experience figure anywhere on this posting, so none has been recorded here rather than guessing. This has been consistent across HackerRank listings on this board. What the posting describes as the problem: measuring skill when AI is already in the room. Software engineering has moved from writing code to using AI to solve problems, and the frameworks used to evaluate developers have not kept up. For more than a decade, skills based hiring relied on deterministic evaluation where a candidate's code either passed test cases or did not, producing a binary and reproducible score. The role is hired to work out what replaces that, and the posting states plainly that this is unsolved rather than a matter of implementation. Scope covers every context in which someone is trying to judge how good a developer actually is: live interviews, asynchronous assessments, AI assisted coding environments and pair programming with agents. Location is Bengaluru on a hybrid basis. Good fit if you are a machine learning engineer who is drawn to open ended, ill defined problems and wants to design evaluation methodology rather than tune a known model against a known benchmark. Measurement, fairness and validity are the substance of the work here. Not a fit if you want clear specifications and a defined success metric, because the posting says outright that the framework does not exist yet. Also worth noting that because HackerRank states no experience figure, this listing will not appear under any experience filter on this page.
The employer asks for 2 to 4 years of experience as a full stack engineer, which is the lowest bar in this edition. Required: proficiency with JavaScript, TypeScript and Node.js, working knowledge of both SQL and NoSQL databases, familiarity with web services, and a strong grounding in software development fundamentals and infrastructure. Postman also asks for strong problem solving and what it calls a bias for action, meaning shipping under constraints rather than waiting for perfect requirements. The day to day: owning intuitive, secure and performant end to end experiences for search, optimising search UX around customer needs, working alongside backend engineers, designers and product managers, building quick functional prototypes for internal and external use cases, and contributing through code review and mentoring peers. The posting explicitly asks you to work across silos and iterate in small increments. Location is the Bangalore office, where Postman was founded. The posting does not state a number of office days. Benefits listed include full medical coverage, flexible PTO, a wellness reimbursement and a monthly lunch stipend, and Postman describes a pay on performance philosophy. Good fit if you have two to four years of real full stack product work and want a large developer audience. Not a fit if you are looking for your first job: this is not a graduate role, it wants people who have already shipped.
The employer asks for 6 or more years building infrastructure level or platform software in cloud native or SaaS environments. The posting is explicit that this is founding level engineering: you design, build and own critical systems of the gateway from the ground up, lead architecture decisions for distributed systems that must be fast, reliable and correct at scale, and set patterns the rest of the team follows. The day to day: driving technical direction and high leverage decisions, owning observability, performance and reliability end to end including SLA targets, monitoring and on call, working directly with the engineering manager and product manager to scope milestones and iterate toward Early Access and general availability, plus design and code reviews and mentoring other engineers. Location is Bengaluru. The posting does not state a number of office days. Postman lists full medical coverage, flexible PTO, a wellness reimbursement and a monthly lunch stipend. Good fit if you have taken a platform or infrastructure product from nothing to a production system other engineers trust, and you want that scope again with 40 million developers already in the ecosystem. Not a fit if you prefer a mature codebase and a settled roadmap: the posting says plainly this is not incremental work.
The employer asks for 5 or more years of software development experience. Required: strong backend engineering in Go, hands on experience integrating with relational and document databases (PostgreSQL, MySQL, MongoDB) and Redis, and the ability to write and maintain unit, integration and performance tests while monitoring, debugging and optimising system performance. Zscaler also asks across its postings for a foundational understanding of AI and ML tools and evidence you actively use them in your own workflow. The day to day: designing and implementing scalable, high performance backend services and APIs, mentoring junior engineers, participating in code reviews, collaborating with external teams to deliver integrated solutions, and contributing to Agile and Scrum ceremonies including sprint planning and retrospectives. Location is Bangalore on a hybrid basis, reporting to a Senior Director of Software Engineering in the platform convergence department. The posting does not state the number of office days for this particular req, though other Zscaler listings in this edition specify three days a week. Good fit if you have five or more years of Go backend work and want distributed systems problems at real scale. Not a fit if you want a pure individual contributor seat with no mentoring: coaching junior engineers is written into the responsibilities.
The employer asks for 5 or more years of software development experience building full stack applications. Required: React for user interfaces, Spring Boot microservices in Java, cloud native infrastructure on AWS and Kubernetes, REST API design, and event driven services using Kafka. Zscaler also asks for a foundational understanding of AI and ML technologies and experience leveraging, securing or positioning AI driven solutions in your own domain, which is consistent across its postings this cycle. The day to day: building full stack features across the React UI, Spring Boot microservices and cloud native infrastructure, designing REST APIs and event driven Kafka services within a microservices architecture, and owning features end to end including logging, observability and cross functional collaboration with UX and product management. Location is Bangalore, hybrid at three days a week in the office, reporting to a Director of Software Development Engineering in the AI Security department. Good fit if you genuinely work across the stack and want to do it on security products rather than a CRUD application. Not a fit if you specialise narrowly in either frontend or backend, because the posting asks for end to end ownership of both.
The employer asks for 5 or more years of relevant experience in test automation. Required: designing, reviewing and executing system, integration and end to end tests for backend datapath components, developing automated functional test cases, and building and maintaining an automation framework using modern tooling to enable automation and scheduling for network security products. Zscaler also asks for a foundational understanding of AI and ML tooling and evidence you use it in your daily workflow. The day to day: building test infrastructure to suit product needs, interacting with multiple stakeholders and product management to understand customer use cases and upcoming features, proactively monitoring cloud components, troubleshooting and debugging cloud incidents, and mentoring junior engineers. Location is Bangalore, hybrid with three days a week onsite, reporting to a Manager of Engineering. Good fit if you are a test automation engineer who wants to work on network and cloud infrastructure rather than application UI, and you are comfortable being on the hook for live cloud incidents. Not a fit if you want feature development: this is a quality engineering seat, and the posting is clear about that.
The employer asks for 5 or more years in platform or infrastructure engineering. Required: owning OpenStack architecture and lifecycle across data centre environments, specifically designing, deploying and operating Nova, Neutron, Cinder, Swift and Glance at scale with high availability and operational resilience; architecting enterprise grade block, object and file storage using Ceph and integrating it with OpenStack and bare metal; and automating data centre platform capability with Terraform, Ansible and GitOps workflows. You are also expected to define standards for software defined networking (SDN and OVN), role based access control, multi tenancy, quotas and resource isolation. Zscaler asks additionally for a foundational understanding of AI and ML tooling. The day to day: driving observability and capacity planning by instrumenting the full stack with Prometheus, Grafana and centralised logging to manage SLOs, track storage utilisation and control cost at data centre scale, enforcing security hardening across tiers, managing access controls, troubleshooting complex production issues and mentoring engineers. Location is Bangalore, hybrid with three days a week in office, reporting to a Senior Manager of Software Development Engineering in the Zero Trust Exchange department. Good fit if you have run OpenStack or Ceph in anger and want ownership of the foundation rather than a slice of it. Not a fit if your cloud experience is entirely on managed AWS, Azure or GCP services, because this is the layer underneath that.
The employer asks for 7 or more years of software development experience with extensive coding in Rust, particularly systems programming and async frameworks such as Tokio or async-std. Required: proven expertise building resilient, observable and horizontally scalable distributed systems; a strong grasp of Linux fundamentals including networking, namespaces, sockets and kernel to user space interaction; and proficiency with container based environments, Git, CI and CD workflows and performance instrumentation. The day to day: designing and building the low latency, high throughput data forwarding plane; developing distributed systems with a focus on concurrency, fault tolerance and messaging; implementing and maintaining gRPC based APIs and services that integrate forwarding plane capability with control and orchestration layers; optimising performance through profiling across kernel and user space; and taking part in code reviews, system design discussions, technical documentation and mentoring. Location is Bangalore or Hyderabad on a hybrid basis, reporting to a Senior Director of Software Engineering in the platform convergence department. Good fit if your Rust is real systems work and you want networking data path problems. Not a fit if your Rust experience is limited to side projects or web backends: the posting asks for extensive production coding in it.
The employer asks for 7 or more years of Java or Go coding in a highly distributed, enterprise scale environment. Required: working knowledge of cloud infrastructure services on AWS or Azure, strong experience with distributed systems and microservices architecture, strong database knowledge covering SQL constructs and data modelling, and a bachelor's degree in computer science or equivalent experience. Zscaler also asks for a foundational understanding of AI and ML technologies and experience applying them in your domain. Preferred: experience building full CI and CD systems using Kubernetes and web services. The day to day: building and operating high scale systems, providing service and product wide architectural guidance, driving impactful technical decisions, establishing and enforcing best practice for coding, testing, observability and CI and CD pipelines, and leading cross team initiatives in performance optimisation, reliability and adoption of new technology to speed up feature delivery. Location is stated as a hybrid role based in Hyderabad, with the requisition also listing Bangalore. Good fit if you have deep Java or Go at enterprise scale and want influence across services rather than one component. Not a fit if you want to stay purely hands on inside a single codebase, since much of the value here is cross team architectural work.
The employer asks for a minimum of 8 or more years working as a Support Engineer or Senior Support Engineer supporting cloud networking or web security products, plus 7 or more years with operating systems including Linux, Unix and FreeBSD. Required: experience delivering products and services as cloud based solutions, strong written and verbal communication at both technical and business level with internal teams, customers, partners and executives, and demonstrated curiosity about AI tools with a history of integrating them into daily work. Preferred: deep expertise in cloud networking infrastructure, hybrid connectivity and traffic management across AWS, Azure and GCP, including VPC and VNet peering, Direct Connect, ExpressRoute and load balancing, plus hands on cloud security work with network security groups and network ACLs and infrastructure as code tooling. The day to day: engaging with customers on escalated support issues and important customer situations, participating in a 24x7 support operation and a 24x7 on call rotation, working with engineering to test and troubleshoot, reproducing customer issues to verify problems, and documenting incident resolutions in the technical support knowledge base. Location is Bangalore on a hybrid basis, reporting to an Escalation Manager in the Customer Success department. Good fit if you are a senior support or escalation engineer with real networking depth. Not a fit if you cannot commit to a 24x7 on call rotation.
The employer asks for 8 or more years in data engineering, data platforms and analytics, or software engineering. Required: comfort writing code in Python, Scala or JavaScript and TypeScript with modern frameworks; working knowledge of two or more cloud ecosystems (AWS, Azure, GCP) with expertise in at least one; deep experience with distributed computing on Apache Spark including knowledge of Spark runtime internals; familiarity with CI and CD for production deployments; and working knowledge of MLOps, ML and AI models and AI APIs. Also required: designing and deploying production end to end data architectures that combine data pipelines, ML and AI models and user facing interfaces; technical project delivery experience covering scope, timelines and measurable outcomes; documentation and whiteboarding skills; and experience with enterprise clients including managing conflict across a broad stakeholder range. Databricks certification is listed, and travel to customers is stated at 20% of the time. The day to day: leading customer technical projects end to end, guiding strategic customers through large data and AI implementations, owning architecture and design decisions for secure and scalable solutions, embedding with customer teams, and feeding product and implementation issues back to Databricks engineering and support. Location is listed as remote in India. Good fit if you are a strong data or platform engineer who genuinely enjoys customer contact. Not a fit if you want to write code without stakeholder work, or cannot travel.
The employer asks for 6 or more years of production experience in backend or infrastructure development, with proficiency in at least two of Terraform, Scala, Go, Apache Spark, Java and Python, and experience with at least one compiled language is required. Also required: experience delivering complex backend or infrastructure projects in iterative increments, balancing robustness against development speed, and a stated passion for defensive engineering practice. The day to day: building, debugging and extending internal and public infrastructure components of the Databricks Labs ecosystem with a focus on scalable, reliable backend services and automation; implementing and maintaining backend services, APIs and automation tools that integrate with the Databricks platform; authoring technical documentation, design proposals and internal guides; contributing to engineering best practice, coding standards and reusable patterns; collaborating with Field Engineering, Product and Platform Engineering to clarify requirements; evaluating and integrating new technology for the Labs and automation tooling ecosystem; owning small to medium projects end to end; and taking part in code reviews, design reviews and incident response. Location is Bengaluru. The posting does not state office days. Good fit if you are a backend engineer who wants tooling and platform work with a visible internal customer. Not a fit if you expected a customer facing architect role: the title says architect, the requirement list says backend engineer.
The employer asks for 10 or more years of production level experience in one of Python, Java, Scala, C++ or a similar language, plus a BTech or higher in computer science or a related field. The requisition is advertised as Staff or Senior Staff, so the level is assessed rather than fixed. The day to day: designing, developing and maintaining the SQL drivers that carry the majority of data warehousing traffic, plus the critical infrastructure behind partner integrations; optimising those drivers for performance, reliability and telemetry so partners and enterprise customers get seamless connectivity; maintaining open source repositories and engaging with the developer community; and working with cross functional teams to define technical requirements, architect solutions and implement systems that let partners connect to the platform. Location is Bengaluru. The posting does not state office days. Good fit if you enjoy driver, protocol or connectivity engineering and are comfortable working in public on open source repositories where external developers read your code. Not a fit if you want product feature work with a visible user interface, because this layer is invisible to end users by design and is judged on throughput, correctness and not breaking compatibility.
The employer asks for 10 or more years of industry experience building and operating large scale distributed systems, plus 4 or more years providing technical leadership on planet scale production data systems, and a BS, MS or PhD in computer science or a related field or equivalent experience. The day to day: designing and running the cross company Data Intelligence Platform that holds every business and product metric used to run Databricks; developing tooling and infrastructure to manage and run Databricks on Databricks at scale across multiple clouds, geographies and deployment types, including CI and CD processes, test frameworks for pipelines and data quality, and infrastructure as code tooling; building reliable data pipelines using Databricks, partner products and open source tools; partnering with engineering teams on long term vision and requirements for the product; giving early feedback on the design and operation of those products; and representing Databricks at academic and industry events. The posting also mentions using current AI developer tools and techniques as part of the work. Location is Bengaluru. The posting does not state office days. Good fit if you are a senior data infrastructure engineer who wants breadth across the whole data stack and does not mind that the customer is internal. Not a fit if you want to build externally facing product.
The employer asks for 12 or more years of production level experience in one of Java, Scala, C++ or a similar language, plus a BS, MS or PhD in computer science or a related field. The day to day: owning the Money systems and services that govern usage across all Databricks products and offerings, starting with resource admission control and usage governance infrastructure; improving engineering and infrastructure efficiency, reliability, accuracy and response times including CI and CD processes, test frameworks, data quality assurance, end to end reconciliation and anomaly detection; and collaborating with platform and product teams to build infrastructure that scales. The work sits at the meeting point of abuse prevention, product commercialisation and reliable availability, so you will be translating diverse business needs into one system. Location is Bengaluru. The posting does not state office days. Good fit if you have deep backend systems experience and want ownership of infrastructure the whole company depends on, and you are comfortable being an early hire on a team that is still forming its practices. Not a fit if you need an established team with settled processes, or if billing and metering strike you as unglamorous: this is careful, high consequence systems work rather than greenfield product building.
The employer asks for 12 or more years of production level experience in one of Python, Java, Scala, C++ or a similar language, plus 7 or more years developing large scale distributed systems from scratch. Required: experience working on a SaaS platform or with service oriented architectures, and extensive experience in the networking domain specifically. The day to day: building new backend connectivity services that power millions of virtual machines running on Databricks; leading the design and development of new services connecting the control plane and the compute plane; and working across product management, operations and other engineering teams to deliver networking systems. As one of the seed members of the Bangalore site, you would help establish the team rather than join an existing one. Location is Bengaluru. The posting does not state office days. Good fit if you have genuine networking depth alongside distributed systems experience and want the influence that comes with being early to a new site. Not a fit if your background is application backend without networking: the posting asks for extensive domain experience there, and this is the layer where multi cloud connectivity problems actually live.
The employer asks for 15 or more years of industry experience building and supporting large scale distributed systems. The day to day: delivering a highly scalable, available and fault tolerant engine that processes hundreds of terabytes of data daily across thousands of customers; low level systems debugging plus performance measurement and optimisation on large production clusters; building architecture designs, influencing the product roadmap and taking ownership of new projects; using your experience to prevent and investigate production issues; and planning and leading complex technical projects that span several teams. The posting describes the level explicitly: full ownership of product or infrastructure direction in a major area, driving it from initial development to scalable solutions with clear business impact, acting as a force multiplier by improving stability, reliability and organisational process, mentoring senior engineers, contributing to recruiting and leading high impact company projects. Location is Bengaluru. The posting does not state office days. Good fit if you have fifteen years of distributed systems work and want scope over a major area without moving into people management. Not a fit if you are targeting a management track, or if you want narrow focus: this role is explicitly cross team and expects influence on organisational process as well as code.
MongoDB publishes no years of experience figure on this posting, so none has been recorded here rather than guessing a number. The seniority signal is the title (Senior) and the requirement to have designed and implemented medium to large software projects. Required: having built and operated large scale distributed systems in cloud providers, with AWS strongly preferred; a strong backend programming background with fluency in Go strongly preferred, though deep experience in another compiled or strongly typed language is acceptable; experience working with AI coding agents and the ability to demonstrate building high quality context for high quality output; experience designing and implementing medium to large projects including driving design reviews and mentoring less senior engineers; strong experience operating production Kubernetes clusters rather than only deploying to them; practical experience defining and working against SLIs and SLOs for services you owned; strong experience with observability tooling covering metrics, logging, traces, Prometheus, Grafana and OpenTelemetry; strong Linux and TCP/IP networking skills; familiarity with standard authentication protocols such as OAuth and OIDC; and familiarity with web services or Kubernetes controller development. Location is Gurugram and MongoDB states plainly that it is looking for candidates based there for its hybrid working model. Good fit if you are a Go backend engineer who genuinely enjoys platform work and has operated Kubernetes in production. Not a fit if you are not in or moving to Gurugram.
MongoDB publishes no years of experience figure on this posting, so none has been recorded here rather than guessing. Required: experience building and maintaining complex mission critical production database systems, either relational or NoSQL; coding or scripting ability in one or more of Java, Python, Ruby, C, C++, C#, JavaScript, Node.js or Go; experience working with APIs to integrate third party technologies across areas such as security and fraud, big data analytics and AI, healthcare, content management, IoT and database performance monitoring; solid hands on systems engineering covering Linux performance, memory management, I/O tuning, configuration, security, networking, clusters and troubleshooting; the ability to analyse issues holistically from application tier through database down to storage; troubleshooting the TCP/IP networking stack at operating system and hypervisor level; experience using or administering AWS, Azure or GCP; and hands on administration of NAS, SAN, local storage and multipathing. Preferred: experience using or managing MongoDB, strong understanding of LDAP, Kerberos and Active Directory, distributed version control especially git, and Kubernetes or other orchestration using vendor enterprise operators. MongoDB states the ramp: in 3 months a deep understanding of MongoDB and its partner ecosystem plus new hire training, by 6 months working frontline with customers and partners and completing the Certified DBA Associate exam, and by 12 months acting as a technical specialist handling escalations independently. Location is Bengaluru, hybrid, and MongoDB states it wants candidates based there. Good fit if you are a systems or database engineer who likes diagnosis. Not a fit if you have no production database background.
Sarvam publishes no years of experience figure on this posting, so none has been recorded here rather than guessing a number. Required: strong Python and PyTorch, described as being comfortable reading model internals, profiling inference and debugging production failures; hands on experience integrating and optimising speech models (ASR or TTS) in production; experience with real time and streaming systems including WebSocket pipelines, chunked audio processing and latency sensitive async architectures; a solid understanding of modern speech system architectures covering sequence to sequence models, attention mechanisms, flow matching or diffusion based TTS and streaming ASR; familiarity with model serving infrastructure such as Triton, TorchServe or ONNX Runtime; audio signal processing fundamentals including sample rates, PCM formats, spectrograms, vocoding and time stretching; and strong async Python. The day to day: building and optimising the real time speech to speech translation pipeline with streaming ASR, server side voice activity detection, low latency translation and live TTS audio streams; designing fan out architectures where one ASR stream serves many concurrent listeners with personalised translated audio; implementing voice cloning in both streaming and batch contexts; optimising end to end latency across the ASR, translation and TTS chain; integrating with real time media infrastructure such as WebRTC, RTMP and SRT; and building evaluation harnesses tracking WER and CER, tempo and pronunciation. Location is Bengaluru. Good fit if you have shipped speech models in production. Not a fit if your ML work has been offline and batch only, because latency is the whole problem here.
Sarvam publishes no years of experience figure on this posting, so none has been recorded here rather than guessing. Required: strong Python and PyTorch, described as comfort reading and modifying model internals; hands on experience training or fine tuning large models including debugging broken runs; experience building data pipelines at scale; a solid grounding in transformer architectures and modern training techniques; comfort with ambiguity, since the roadmap is not fully pre specified; a strong focus on secure coding, code quality and system reliability; and an undergraduate degree in a technical discipline such as computer science, statistics or physics. Bonus points listed: experience with vision language or multimodal systems, distributed training using FSDP, DeepSpeed or Megatron-LM, post training methods such as RLHF, DPO or other alignment techniques, and inference optimisation covering quantisation, distillation and serving. The day to day: designing and running training and fine tuning pipelines on GPU clusters; building multimodal data pipelines covering ingestion, filtering, deduplication, synthetic generation and quality assurance; implementing new architectures from research; building evaluation harnesses, benchmarks and automated regression tracking; optimising models for inference; working directly with clients on document processing, visual search and form extraction; and debugging deployed solutions for latency, accuracy and edge cases. Location is Bengaluru. Good fit if you have trained or fine tuned large models yourself and want both research and client facing delivery. Not a fit if you only consume model APIs without touching training.
Sarvam publishes no years of experience figure on this posting, so none has been recorded here rather than guessing. The title is Principal and the posting describes a hands on security leader, so expect it to be pitched senior. Required: hands on experience securing enterprise and BFSI or fintech infrastructure; participation in capture the flag competitions across web, crypto, pwn or mixed categories; and participation in bug bounty programmes, especially private programmes for fintech, cloud or infrastructure companies. The day to day breaks into four areas. Security strategy and architecture: defining and evolving the end to end security strategy, designing secure architectures for Sarvam's products and API platform, applying BFSI grade threat modelling to AI infrastructure, and making pragmatic risk decisions that balance research velocity against security. Product and application security: leading threat modelling for AI products, APIs and data systems, owning application and API security including authentication, access control and data isolation, and driving vulnerability discovery, remediation and verification. Systems and process: building systems to proactively find and validate vulnerabilities, performing targeted adversarial testing and red teaming, and researching emerging threats relevant to AI systems. Cloud and DevSecOps: securing cloud infrastructure, IAM and secrets management, integrating security checks into CI and CD without slowing teams down, and improving detection and response readiness. Location is Bengaluru. Good fit if you are an offensive minded security engineer with fintech depth who wants to stay technical. Not a fit if your background is governance, risk and compliance: the posting rules that out itself.
PhonePe publishes no years of experience figure on this posting, so none has been recorded here rather than guessing. The level in the title is 2, and the posting asks for extensive experience in Linux and Unix administration, so it is not an entry level seat. Required: proficiency in Linux and Unix administration coupled with extensive field experience; computer networking proficiency and working knowledge; the ability to use a wide variety of open source technologies and tools with a strong emphasis on cloud services; implementing best practice and IT operations to maintain an always up, always available service; and active participation in the on call rotation. The day to day is keeping one of the largest fintech infrastructures in the country running: reliability and performance work, incident response, and the operational engineering that sits behind an always available payments service. Location is Bangalore. ⚠️ Note before applying: PhonePe currently advertises a byte identical description under the separate title Service Delivery Engineer. They are the same job description. We publish one listing rather than two so that the board reflects one real opening. Good fit if you have solid Linux and networking fundamentals and want infrastructure at genuine scale, where an outage is immediately visible to hundreds of millions of people. Not a fit if you are looking for a development role, or cannot take part in an on call rotation.
PhonePe publishes no years of experience figure on this posting, so none has been recorded here rather than guessing. The title carries level 2 and the posting asks for an experienced SRE. The day to day, grouped as the posting groups it. Cloud and infrastructure: configuring, maintaining and managing services and packages on Ubuntu virtual machines in Azure, and designing and managing Azure components for log storage, management, alerting and monitoring. Networking and connectivity: configuring and maintaining complex network components including Azure Firewall, route tables, virtual network gateways and ExpressRoute; establishing and managing IPsec and ExpressRoute connectivity with external environments; and managing routing, troubleshooting connectivity problems and supporting network component migrations with minimal downtime. Automation and infrastructure as code: driving automation of business as usual tasks using Terraform, SaltStack, Ansible and scripting languages, including writing new Terraform for infrastructure components. Database and data management: setting up and managing high availability database configurations. Location is Bangalore. The role supports a high volume, mission critical environment. Good fit if your cloud depth is specifically Azure, you are comfortable with enterprise networking constructs like ExpressRoute and IPsec, and you write infrastructure as code rather than clicking through a portal. Not a fit if your experience is AWS only, since almost every named technology here is Azure specific and the networking requirements are the hardest part of the role.
The employer asks for 5 or more years of research or industry experience within computer vision and machine learning models. Note that Netradyne writes this as "5+ yrs", abbreviated, which is worth mentioning because automated parsers frequently miss that form. Required: a BTech, MTech or PhD in computer science, electrical engineering or a related area; in depth understanding of machine learning covering both deep learning and classical ML, and of computer vision concepts; excellent programming skills in Python, which is required, with C++ desired; the ability to turn abstract product concepts into working systems; the ability to innovate on problems without documented solutions; and hands on experience with edge deployments targeting various hardware platforms. Preferred: experience with time series data, camera calibration, multi view geometry, 3D reconstruction and SLAM, and road scene understanding covering objects and lanes. The day to day: designing and commercialising algorithms that characterise driving behaviour, deploying new algorithms and models into thousands of vehicles, and collaborating cross functionally to build and deploy scalable AI systems. Location is Bangalore. Netradyne is consistently the one employer on this board that publishes its office policy, and its other current postings state onsite five days a week at Whitefield on a general shift. Good fit if you have computer vision depth and want models that ship to real hardware. Not a fit if you want purely offline research, or cannot work onsite in Bangalore.
The employer asks for 9 or more years of research or industry experience within computer vision and machine learning models. Netradyne writes this as "9+ yrs", abbreviated, a form automated parsers routinely miss, which is why it was read by hand here. Required: a BTech, MTech or PhD in computer science, electrical engineering or a related area; in depth understanding of machine learning covering deep learning and classical ML, and of computer vision concepts; excellent programming skills in Python, which is required, with C++ desired; the ability to take abstract product concepts and turn them into reality; the ability to innovate on cutting edge problems without documented solutions; and hands on experience handling edge deployments across various hardware platforms. Preferred: experience with time series data, camera calibration, multi view geometry, 3D reconstruction and SLAM, and road scene understanding covering objects and lanes. The day to day: leading development of AI solutions that let drivers and fleets identify unsafe driving in real time, designing and commercialising driver monitoring and driver assistance algorithms, working with very large datasets, and deploying models into thousands of vehicles. Location is Bangalore, and Netradyne's other current postings state onsite five days a week at Whitefield on a general shift, which is more office policy than most employers publish. Good fit if you have close to a decade of computer vision work and want ownership of algorithms that ship to edge hardware at scale. If you have five to eight years, apply to the Staff Research Engineer posting instead: same team, same work, lower stated floor.
The employer asks for 10 or more years in corporate IT, endpoint engineering or IT architecture roles within distributed or hybrid environments. The day to day: defining and maintaining the target state architecture for corporate IT systems; maturing service desk processes across incident, request, problem and change with automation and self service at the core; implementing an AI service desk using large language models and virtual agents for intelligent ticket routing, automated triage and instant user resolution; engineering end to end automation frameworks that turn manual support interventions into self healing workflows; designing modern endpoint management across macOS and Windows using Jamf and Intune; establishing patching, compliance and configuration baselines with measurable enforcement; owning architecture and governance for Google Workspace, Slack, Zoom and conference room AV systems; automating onboarding and offboarding workflows with partner teams; and documenting standards, integration patterns and lifecycle management strategies. The posting describes the role as strategic yet hands on, and says it suits someone who solves complex systems problems and uses data to guide decisions rather than reacting to tickets. You would work as part of a globally distributed IT organisation, partnering with Security, Engineering, HR and Finance. Location is Bangalore. ⚠️ Rubrik's careers site returns an error to automated link checks, so this listing was verified live through the Greenhouse jobs API instead, which confirmed it open and updated on 28 July. It opens normally in a browser. Good fit if you have a decade in enterprise IT and want to build systems rather than staff a queue. Not a fit if you want product engineering.
The employer asks for typically 18 or more years of industry experience in software engineering, with significant depth in developer platforms and infrastructure. The posting states the role operates at the same level as an Engineering Director, so calibrate expectations accordingly. The day to day, as the posting groups it. Platform strategy and AI powered productivity: defining the long term technical vision, described as a 3 or more year horizon, for the Developer Platform including core infrastructure, CI and CD pipelines and observability systems; pioneering the integration of AI and ML both for engineering tasks and to transform internal processes and tools company wide; translating future business opportunities or productivity gaps into solvable multi quarter technical problems with a clear roadmap; and driving improvements in engineering velocity and quality by finding and removing bottlenecks in the software development lifecycle. The role also carries technical leadership, strategic delivery and people growth responsibilities, including coaching and mentoring Staff Engineers toward Principal level impact and raising the hiring bar. Scope spans multiple complex systems and multiple engineering organisations. Location is Bangalore. ⚠️ Rubrik's careers site returns an error to automated link checks, so this listing was verified live through the Greenhouse jobs API, which confirmed it open and updated on 28 July. It opens normally in a browser. Good fit if you have eighteen years behind you, want director level scope and influence, and specifically want to stay on the individual contributor ladder. Not a fit if you are looking for focused hands on coding, because the emphasis here is strategy, cross organisational influence and mentoring.
The employer asks for 8 or more years of experience in software quality engineering. The day to day: designing and owning the overall test automation framework and strategy across both the Voice AI platform and the monitoring and analytics platform; defining test pyramid principles spanning unit, integration and higher level tests; setting acceptance criteria and quality gates at the story level; driving root cause analysis on escaped defects and building preventive test coverage; working closely with product engineering, platform and data teams to embed quality upstream; and mentoring engineers on best practice while driving quality culture across cross functional teams. The posting reports to a Director of NOC Delivery and Automation, and describes the intent as shifting left, moving from reactive bug finding toward proactive prevention at the architecture level. Location is Bangalore. Good fit if you are a senior quality engineer who wants to own strategy and framework design across multiple platforms rather than write test cases against a fixed plan, and who is comfortable being measured on defects that did not happen. The Voice AI element makes this less conventional than most QA automation roles, since testing a voice and AI driven system raises different problems from testing a standard web application. Not a fit if you are early in a quality career: at eight or more years this expects you to have already built and owned an automation framework end to end, not just contributed to one.
Added July 28, 2026
What the posting requires: 2 to 4 years of professional software development experience in backend, distributed systems or platform engineering roles. Proven experience building production grade backend services and APIs in Python or Go. Hands on experience deploying, scaling and troubleshooting containers and Kubernetes, with cloud platform familiarity (they note GCP is a plus). Strong debugging and root cause analysis across distributed components. Solid grounding in system design, performance optimisation and reliability engineering. Zscaler also asks for demonstrated curiosity about AI tools and a history of folding them into your daily workflow, and it states this plainly as a minimum qualification rather than a nice to have, so address it in your application. The day to day: designing, developing and maintaining backend services and APIs; owning the full lifecycle from build through deployment, scaling and production support; running containerised workloads on Kubernetes; monitoring service health, investigating incidents and doing root cause analysis; and working alongside the cloud infrastructure teams on workload deployment and configuration. Location and office reality: Mohali, Punjab. Zscaler's India engineering presence spans Bangalore, Mohali, Hyderabad and Pune, and this req is Mohali only, so treat it as an on site role in Punjab unless recruiting tells you otherwise. Who this is for: an engineer roughly 2 to 4 years in who has already run something in production and wants to go deeper on Kubernetes, cloud native services and security infrastructure. If you have only built features behind someone else's deployment pipeline, the full lifecycle ownership language is the part to prepare for. If you are past about 6 years, the other Zscaler listings on this board will fit you better than this one.
What the posting requires: 2 to 4 years of professional software development experience with meaningful time building production frontend applications in TypeScript or JavaScript. Browser extension development experience for Chrome, Firefox or Safari, including a working understanding of extension APIs, manifest versions (MV2 and MV3), permission models, and the separation between content scripts, background service workers and extension pages. Strong command of core JavaScript (ES6 and later) and TypeScript types, async and await, closures and modules, with a precise mental model of how the language behaves. Experience with React. As with the other Zscaler reqs, active use of AI tooling is listed as a minimum qualification. The day to day: turning product requirements and UI or UX designs into tested browser extension features, from user facing UI down to in browser detection logic; writing security sensitive code that runs on every page load with minimal latency and memory overhead; writing unit and integration tests; debugging across background scripts, content scripts and popups with browser developer tools; and partnering with designers, backend engineers and QA. Location and office reality: Mohali, Punjab. Who this is for: a frontend engineer 2 to 4 years in who wants to stop building dashboards and start working on the browser platform itself. The extension experience is the real gate here. If you have never shipped one, the manifest and permission model questions will be hard to bluff, but a serious side project extension is a legitimate way to answer them.
What the posting requires: four to seven years in cyber security research (the posting spells the numbers out in words rather than digits). Strong proficiency in reverse engineering and debugging with tools such as IDA Pro or x64dbg. Deep understanding of Windows internals, web application security, malware categories, and network protocols across TCP/IP and the OWASP frameworks. Proven experience creating detection signatures with IDS or IPS and YARA. Strong programming in Python, Shell, Perl or Ruby for building automation tooling. Demonstrated curiosity about AI tools is again listed under minimum qualifications. Nice to have: experience designing AI powered automation or prompt engineering workflows to scale threat research and analyse malicious AI agents; certifications in AI, prompt engineering or agentic AI workflows; familiarity with the MCP protocol; and a B.E, M.E, B.Tech or M.Tech in computer science or IT, or advanced cybersecurity certifications. The day to day: static and dynamic malware analysis against emerging threats, C2 frameworks and malicious AI agents; building automation tools, prototypes and detection signatures that ship into Zscaler products; tracking attacker tactics and running reputation analysis on extracted indicators; validating AI and ML model output and feeding that back to engineering; and publishing research. Location and office reality: listed for Bangalore, Hyderabad, Mohali or Pune, and tagged hybrid in the posting itself. Who this is for: a malware analyst or detection engineer with real reverse engineering hours who wants to move toward the AI side of security research without leaving hands on analysis behind. Note the reporting line is into a leader in the Threat Detection Group, and despite the Staff title the years asked for are 4 to 7, which is lower than most Staff titles on this board.
What the posting requires: a bachelor's degree or higher in computer science or engineering, or comparable education and experience, which it defines as typically obtained by five or more years of related work experience. That sentence is the only experience figure in the posting, so treat 5 years as the floor. Beyond that: sound grasp of cybersecurity practice; broad technical knowledge of Windows, Mac and Linux, networking protocols, cloud infrastructure, security devices (firewalls, IPS and IDS, DLP) and SIEM tooling (Splunk, Sumo Logic, Elastic, Kibana); hands on secrets management and PKI including HSMs, certificate generation and re key operations at scale; deep practical virtualisation experience (ESXi, Hyper-V, KVM, Kubernetes, OpenStack); strong networking fundamentals including the OSI model, SDN and cloud VPCs; hands on public cloud (AWS, GCP, Azure); a track record running projects from scoping through documentation; experience across both commercial and public sector environments; and broad Linux administration across varied distributions. The day to day: designing, building and operating security systems; monitoring the security environment and identifying gaps; preparing security reports from collected data and trends; determining security requirements from business strategy and researching standards; running system security and vulnerability analyses and risk assessments; conducting incident response analyses; and mentoring less experienced team members and running training. Location and office reality: Bengaluru. Netskope's India engineering base. Who this is for: an infrastructure or platform security engineer, not a machine learning specialist. If you came for AI model security this is not that job, and the honest read of the requirement list is production infrastructure security with PKI and virtualisation depth. The hiring across all levels note means candidates well past 5 years are also in scope.
What the posting requires: a bachelor's degree in ECE or EEE. 6 or more years of hardware development experience, with the header stating a 6 to 10 year band. Proficiency with OrCAD, Mentor and Cadence. Strong problem solving and debugging. Knowledge of schematic, PCB and Gerber review. Hands on experience with board bring up and field installed system debugging. Hands on qualification experience across ESS, EMI and EMC. Understanding of cellular technologies including GSM, LTE and 5G. Experience with test and measurement equipment including high end oscilloscopes and logic, spectrum and vector network analysers. Nice to have: prior experience at product companies, design experience on Qualcomm or NVIDIA platforms, and experience with camera sensors and AI processors. The day to day: designing and reviewing high speed system hardware; working with the software team on system level issues; supporting manufacturing for production quality; working across mechanical, ECAD, BSP, CE and supply chain teams; and designing for test strategy and sustaining test support across the product lifecycle. Location and office reality: HM Tech Park, Whitefield, Bangalore. Netradyne is one of the few employers on this list that states its office policy in writing, and across its postings that policy is on site five days a week. Who this is for: an embedded hardware engineer with real schematic and bring up hours, not a firmware engineer. The Qualcomm and NVIDIA platform note is the differentiator if you have it. Also note this is the same employer as two other roles on today's list, on different teams.
What the posting requires: over 7 years managing and maintaining distributed big data ecosystems, with the title stating a 7 to 11 year band. Strong Linux expertise including IP, iptables and IPsec. Scripting or programming in Perl, Golang or Python. Hands on experience with the Hadoop stack: HDFS, HBase, Airflow, YARN, Ranger, Kafka and Pinot. Familiarity with open source configuration management and deployment tooling such as Puppet, Salt, Chef or Ansible. Solid networking and open source fundamentals. DevOps tooling: SaltStack, Ansible, Docker and Git. Logging and monitoring: the ELK stack, Grafana, Prometheus, OpenTSDB and OpenTelemetry. Strong communication and collaboration. Nice to have: managing infrastructure on AWS, Azure or GCP; designing and reviewing system architectures for scale; and observability tooling for visualisation and alerting. The day to day: supporting incremental change across Linux and Unix environments; leading on call rotations, incident response, root cause analysis and postmortems; building automation for provisioning, scaling, upgrades and patching; capacity planning and performance tuning; enforcing security standards; and folding reliability practice into how product teams build. Benefits worth knowing: PhonePe publishes its full time benefits on the posting, including medical, critical illness, accident and life insurance, an employee assistance programme and on site medical centre, maternity and paternity benefits, adoption and day care support, relocation and transfer support, PF, gratuity, NPS, leave encashment and higher education support. Very few postings on this board list any of this. Who this is for: an SRE or infrastructure engineer who has actually operated Hadoop at scale, not just used it. If your big data experience is analytics rather than keeping clusters alive at three in the morning, this is not the fit.
What the posting requires: a bachelor's or master's in computer science, IT, AI or a related field. 8 or more years in IT engineering, of which at least 5 in IT automation and AI tooling solution and implementation. Note the title says Staff and the headline skill is automation, but the real floor is 8 years overall, not 5. Hands on experience shipping generative AI solutions with tools such as OpenAI, Microsoft Copilot, Claude, Cursor and GitHub Copilot. Proficiency in Python, Java or similar with the ability to build and integrate APIs and workflows. Working knowledge of AI and ML frameworks, prompt engineering, RAG patterns and agentic or workflow automation such as n8n or Zapier. Strong understanding of enterprise IT infrastructure, cybersecurity and cloud (Azure, AWS or Google Workspace). Experience with Microsoft 365, SharePoint and the Power Platform. Familiarity with IT security frameworks and identity tooling: LDAP, Entra ID, SSO and identity providers, VPNs. Exposure to SOC automation, AI driven ITSM or InfoSec response automation. The day to day: designing and maintaining reusable AI agents, workflows, MCP connectors and assistants; integrating them into enterprise IT and business systems; partnering with function leads to prototype and scale use cases; ensuring deployment meets Netradyne's responsible AI principles, GDPR obligations and InfoSec policy; supporting governance of generative AI tool budgets across the organisation; and monitoring and troubleshooting deployed automation. Location and office reality: Bangalore. Netradyne's stated policy across its postings is on site five days a week at Whitefield. Who this is for: an engineer who likes being a horizontal force multiplier and is comfortable working with every function in a company rather than one product team. If you want to go deep on one system, this is the wrong shape. If you have been the person quietly automating things for everyone and want that as the actual job description, it fits well.
What the posting requires: 8 or more years of software engineering experience. Deep understanding of distributed systems, database internals and network constraints, and clean maintainable code, with the posting stating you will be coding roughly 80 percent of the time. Extensive full stack experience with Python, Django, React or similar modern frameworks, and willingness to pick up whatever language the job needs. Hands on cloud and infrastructure experience: AWS, ECS and Docker, CloudWatch, particularly for data heavy or high throughput applications. A startup mindset, described as thriving in ambiguous zero to one environments with high velocity decision making. The day to day: owning features end to end across the stack; leading technical development of the Lens and Radiant platforms for data enrichment, labelling and continuous QA; architecting and scaling cloud environments and ECS services for video transcoding with telemetry across CPU, memory, network and disk IOPS; designing petabyte scale data pipelines; using agentic models as a force multiplier while making the architectural calls yourself; and mentoring mid and senior engineers through code review, pairing and architecture discussion. Location and office reality: Bengaluru, described as a hub the company is building out. Who this is for: a true generalist who is comfortable being the technical pillar of a small new team and does not want to specialise. The physical AI and robotics data angle is genuinely different from most listings here, so it suits someone who wants that domain. Backed by Benchmark, Spark Capital, Craft Ventures, Greylock and Y Combinator, if investor quality matters to your risk calculation.
What the posting requires: 8 or more years of software engineering experience with 4 or more focused on AI and ML systems in production. A B.Tech, B.E or M.S. in computer science, machine learning or a related field, which ChargePoint specifies should be from what it calls a top tier institution. Deep expertise in Python, FastAPI, Django and modern backend frameworks. Hands on LLM engineering: LangChain, LangGraph, Bedrock or OpenAI APIs, prompt engineering and RAG. Strong Elasticsearch including vector search, hybrid search and semantic retrieval. Vector databases such as Qdrant, ChromaDB or Pinecone. Production LLM systems with low latency inference, caching and observability. Distributed systems design, microservices and event driven patterns with Kafka or RabbitMQ. Cloud (AWS or GCP), Docker, Kubernetes and CI/CD. Strong PostgreSQL including query optimisation and schema design, plus Redis and MongoDB. A track record of measurable performance improvements. Also listed: voice AI and telephony integration (Genesys, SIP) and speech pipelines; computer vision and visual transformers; data engineering with Airflow, DBT, ClickHouse, Trino and Iceberg; experience with datasets over 50TB; fine tuning with LoRA or QLoRA; RLHF style preference tuning; observability stacks; and certifications in generative or agentic AI. Location and office reality: the requisition header says India and the posting body states Bangalore, India. Who this is for: an engineer who has already put LLM systems into production and can talk about latency and cost rather than model choice. The requirement list is long and reads like several roles fused together, so expect to be strong in the LLM and search half and passable on the voice and vision half rather than expert in all of it.
What the posting requires: 8 or more years of engineering experience, extensively with Django or Flask, React and relational databases in a microservice architecture. A bachelor's in computer science or computer engineering preferred. Strong AWS experience across Route53, CloudFront, API Gateway, Aurora RDS, DynamoDB, ElastiCache, EKS, ECS, S3, the AWS SDK, Lambda and SQS. Proficiency writing unit and integration tests plus hands on CI/CD including Git, pipeline tooling and security scans. Linux administration with console commands, scripting and utilities in Python and BASH. Demonstrated REST API building with OpenAPI or Swagger specs. Agile development experience and familiarity with gRPC, GraphQL and automation tooling such as Ansible, Chef or Puppet. Third party integration and custom application development. SQL and NoSQL across MySQL, Postgres, Redis, DynamoDB, Elasticsearch and MongoDB. BI tooling such as Tableau or Power BI. The day to day: designing and maintaining cloud native solutions and analytics dashboards for proactive monitoring and network hygiene; documenting development and modification; ensuring data integrity and security; producing data flow and data structure diagrams; performing code reviews; and helping train and guide others through projects start to finish. Location and office reality: the requisition is tagged IN-Karnataka-Bangalore and the body states Bangalore, India. Who this is for: a backend engineer who is comfortable in the Python web stack and has real AWS breadth, and who cares about code quality standards enough to enforce them. The dashboards and BI tooling mention means part of the output is visible reporting, not just services.
What the posting requires: 8 to 12 years of software engineering experience with deep frontend expertise. Expert level JavaScript, TypeScript, HTML and CSS. Extensive React (or similar) experience in large scale applications. Strong expertise in frontend architecture, design systems and scalable UI development. Proven experience building and evolving shared component libraries or frontend platforms. Deep understanding of browser internals, rendering and performance optimisation. Experience defining and driving frontend standards across teams. The day to day: defining and evolving frontend architecture patterns used across product teams; leading architecture reviews and guiding design decisions; driving adoption of shared platforms, frameworks and tooling to reduce duplicated effort; establishing engineering standards and decision frameworks; setting performance, accessibility and user experience standards; establishing testing, observability and monitoring practice; identifying systemic frontend risks and leading cross team efforts on technical debt; and mentoring senior engineers. Location and office reality: Pune, India. Who this is for: a senior frontend engineer who has already outgrown owning one application and wants to shape how several teams build. Be clear eyed about the influence without authority framing: the posting repeats it, which usually means the organisation knows it is the hard part of the job. If you prefer shipping user facing features, the day to day here is mostly standards, reviews and shared abstractions.
What the posting requires: a bachelor's or master's in computer science, information systems or a related field. 8 or more years in Salesforce development and enterprise application engineering. Strong hands on Apex, Lightning Web Components, JavaScript, Flows, SOQL, APIs and platform customisation. Strong understanding of Salesforce architecture, governor limits, declarative automation, integration patterns and scalable solution design. Experience with CI/CD, deployment processes, code refactoring and performance optimisation in Salesforce environments. Experience integrating Salesforce with enterprise systems using APIs, ETL tools and automation platforms. Salesforce Platform Developer II certification is strongly preferred, with JavaScript Developer, Advanced Administrator, Application Architect or System Architect certifications a plus. Good understanding of AI powered and agentic development tools such as Cursor, Claude Code and Agentforce. The day to day: developing, testing, documenting and deploying Salesforce solutions; supporting enhancements, break fix and ongoing maintenance; investigating technical and integration issues with development, operations and business teams; managing multiple priorities; researching new platform capabilities and prototypes; and mentoring junior engineers and administrators. How they measure you: MongoDB publishes ramp expectations on this posting. At three months you understand its Salesforce ecosystem and current implementations. At six months you have delivered one or more critical initiatives and become a trusted technical contributor. Location and office reality: MongoDB states it is looking to speak to candidates based in Gurugram for its hybrid working model, so this one is not remote. Who this is for: a Salesforce engineer, plainly. Strong general backend engineers without Apex and LWC depth will not clear the bar, and equally, this is a good seat if you have that depth and want it valued at a product company rather than at a consultancy.
What the posting requires: 9 or more years, stated directly in the job header. Demonstrated success driving organisation level architecture and multi team initiatives. Deep expertise in distributed systems, scalability and data platforms. Ability to convert ambiguous business and regulatory requirements into system architecture. Proven ability to influence across teams without authority. Strong storytelling and stakeholder management. The posting frames these as all Staff requirements plus the above, so expect to be assessed against the Staff bar first. Nice to have: experience building enterprise grade compliance systems. The day to day: defining long term platform architecture; leading cross organisation programmes across engineering, product and compliance; shaping architectural frameworks and standards used by other teams; partnering with directors, engineering managers and product or compliance leadership on strategy; architecting high scale ingestion for billions of events a day; leading migrations and re architectures; setting SLOs and driving resilience, data quality and observability work; leading design reviews and technical councils; and mentoring Staff and Senior engineers. Location and office reality: Netradyne publishes this clearly, which almost nobody else does. Whitefield, Bangalore. Full time. Work model on site, five days in office. General shift. If you need hybrid, this posting has already answered you. Who this is for: an architect who is genuinely energised by influence work. Read the responsibilities honestly before applying: the coding content is not spelled out and the described output is architecture, standards, reviews and cross team programmes. It reports alongside directors and engineering managers rather than into a single team.
What the posting requires: 9 or more years building production grade distributed systems in Java, Scala, C++ or Go. A proven track record architecting solutions for large scale infrastructure and cloud compute. The role is described as technical lead for the Bengaluru chapter, defining technical strategy for problems where the solution is not yet known. The day to day: architecting systems to optimise cloud spend at very large scale; defining the roadmap for the efficiency pillar and running design reviews and risk assessments; building regression detection and automated resource rightsizing; building the frameworks that let product teams measure their own efficiency footprint, and the automated release gates that hold them to it; acting as technical authority during incidents involving system wide performance issues; mentoring junior and senior engineers; and designing the AI driven detection, decisioning and autonomous remediation layers that let cost governance run continuously. Location and office reality: Bengaluru, India. Databricks describes itself as still building out this office, so expect a growing team rather than an established one. Who this is for: a distributed systems engineer who finds infrastructure economics interesting rather than tedious. It is a good seat if you want measurable impact you can point at in a performance review, since the output is denominated in dollars saved. The founding engineer framing means more ambiguity and more say in direction than a typical Staff role.
What the posting requires: 10 or more years of work experience in endpoint, network or cloud security product development. Strong C++ programming. Expertise in data structures and algorithms. Deep understanding of TCP/IP networking protocols. Deep understanding of macOS internals and experience developing software on macOS. Knowledge of cryptography techniques. Experience writing multi platform code. Familiarity with web data formats such as JSON, XML and MIME. Knowledge of CI/CD tooling such as Jenkins. Strong written and verbal communication. A BS in computer science is required and an MS is strongly preferred. The day to day: building macOS client security endpoint agent technology; writing multi threaded and multi platform C++; taking requirement specs through research, design and implementation with attention to reliability, sustainability, scalability and observability; writing and running unit tests for your modules; working with product management on requirements; and helping QA test the product properly. Location and office reality: Bengaluru, Karnataka. Netskope's India engineering office. Who this is for: a systems programmer with actual macOS internals depth. This is one of the narrower asks on today's board and general C++ experience without the platform specialism will not carry it. Netskope has a matching Windows client role on this same list at 12 or more years, so if your depth is on the other platform, apply to that one instead.
What the posting requires: a bachelor's degree in computer science or a related field. 10 or more years of software development experience, stated in the job header. Hands on experience with embedded systems, Linux kernel device driver development or operating systems. Hands on hardware bring up using USB, ADC, GPIO, SPI, I2C, Wi-Fi and similar peripherals. Proficiency in embedded C and shell scripting, with Python scripting listed as an added advantage. Strong problem solving and the ability to work independently. Nice to have: prior experience at product or SaaS companies, ability to contribute individually while mentoring juniors, and familiarity with agile methodologies. The day to day: designing and implementing software in C and shell; leading code reviews and mentoring junior engineers; working with product managers on requirements; troubleshooting and debugging complex production issues; and implementing development best practice. Location and office reality: HM Tech Park, Whitefield, Bangalore. Full time. On site five days a week, stated in the posting. Who this is for: an embedded engineer who has actually written or ported kernel drivers, not an application developer who has used embedded Linux. If you have done bring up on real silicon, this is a strong match. Netradyne also has a hardware design role and a platform architecture role on today's list, on different teams, so pick the one that matches where you sit in the stack.
What the posting requires: a bachelor's or master's in computer science, engineering or a related field, with 10 or more years of enterprise integration experience including significant time in lead or architect roles. At least 5 years hands on designing and delivering complex enterprise grade integration solutions with Workato, with understanding beyond the low code surface: advanced recipes, callable recipes and event streams. Experience with event driven integration on Kafka or equivalent, including topics, producers and consumers, durability and retries. RESTful API design plus MCP based interfaces, OAuth2 and JWT, versioning and lifecycle management, and API management platforms such as Apigee. The day to day: leading architecture, design and implementation of Workato integrations and APIs across go to market systems; defining integration standards and best practices; designing and reviewing event driven workflows; translating ambiguous cross functional requirements into technical designs; mentoring other integration engineers and running design and code reviews; partnering with go to market, finance, data and security teams on governance, compliance and audit requirements; setting and enforcing non functional requirements for performance, resilience, observability and security; deep root cause analysis across systems; running proofs of concept; and participating in the on call and support rotation. Location and office reality: MongoDB states it wants candidates based in Gurugram for its hybrid working model. Not remote. Who this is for: an integration architect, and specifically one with real Workato depth. Note the on call expectation, which is unusual to see stated on an enterprise systems role and tells you these integrations are treated as production systems.
What the posting requires: a BS or higher in computer science or a related field. 12 or more years of production level experience in Python, Java, Scala, C++ or a similar language. 6 or more years developing large scale distributed systems from scratch. Experience working on a SaaS platform or with service oriented architectures. Experience on infrastructure related projects is listed as a plus. The day to day: working across problems that span product and infrastructure, including distributed systems, service architecture and monitoring at scale, workflow orchestration and developer experience; delivering services and client libraries for cloud storage backends; and building scalable services in Scala on Kubernetes with Spark data pipelines behind the pricing infrastructure. Location and office reality: Bengaluru, India. Who this is for: a senior distributed systems engineer. Note the gap between the two figures: 12 years total but only 6 building distributed systems from scratch, so a long career with a solid distributed systems core clears this even if the early years were elsewhere. Databricks has two other roles on today's list at 8 and 9 years, so if 12 is out of reach, look at those instead. The 14 new teams note means the specific team may be decided during the process rather than before it.
What the posting requires: 12 or more years of work experience in endpoint, network or cloud security product development. Strong C++ programming. Expertise in data structures and algorithms. Deep understanding of TCP/IP networking protocols. Deep understanding of Windows internals and working experience creating software on Windows. Knowledge of cryptography techniques. Experience writing multi platform code. Familiarity with web data formats such as JSON, XML and MIME. Knowledge of CI/CD tooling such as Jenkins. Strong written and verbal communication, described as open, transparent and consistent. A BS in computer science is required and an MS is strongly preferred. The day to day: building Windows client security endpoint agent technology; writing multi threaded and multi platform C++; taking requirement specs through research, design and implementation with attention to reliability, sustainability, scalability and observability; writing and executing unit test routines; working with product management on requirements; and supporting QA. Location and office reality: Bengaluru, Karnataka. Who this is for: a Windows systems programmer with kernel or driver level depth in security or networking software. If your background is macOS instead, Netskope's macOS client role is on today's list at 10 or more years. Both are on the same team, so applying to the one that matches your platform is better than applying to both.
What the posting requires: a bachelor's or master's in computer science, IT or a related field. 15 or more years securing complex on premises or cloud deployments, with a minimum of 6 years dedicated to cloud security architecture and design, including significant experience across AWS, GCP or Azure. Deep technical understanding of core cloud service models including compute, network and storage. Proficiency in at least one programming or scripting language such as Python, Go or Java for automating security tooling. Extensive experience with containerised applications (Kubernetes, Docker), CI/CD pipelines and microservices. 5 or more years with infrastructure as code for complex systems using Terraform, Ansible or similar. Demonstrated ability to explain complex technical issues to both specialists and non technical stakeholders. The day to day: defining and implementing cloud security architecture frameworks and guidelines; prioritising security maturity initiatives with cross functional teams; designing scalable solutions with cloud security architects, developers and engineers; building proofs of concept, tools and platforms; running architecture reviews, security assessments, threat modelling and risk analysis; establishing secure reference architectures and reusable patterns; strategic planning for cloud security capability including native and third party tooling; and partnering with incident response and SOC analysts. Location and office reality: Bangalore, India. Who this is for: a cloud security architect deep into a career, who still wants to build. One practical note: Rubrik's careers site rejects automated requests, so this listing was verified live through the Greenhouse jobs API rather than by fetching the page. It opens normally in a browser.
What the posting requires: strong Python with hands on FastAPI, Django, Flask or similar. Deep understanding of HTTP, WebSockets and gRPC. Proven experience building low latency distributed backend systems. Hands on experience with PostgreSQL, Redis, ClickHouse or related data systems. Familiarity with Kafka or Redis Streams. Solid understanding of API authentication, authorisation and security practice. Experience with Docker, Kubernetes and CI/CD. Hands on experience with at least one major cloud platform, with Azure preferred. Nice to have: canary deployments, progressive rollouts or feature flag systems; prior work on ML inference or model serving infrastructure; observability tooling such as Prometheus, Grafana and OpenTelemetry; and open source contributions or a solid GitHub portfolio. The day to day: designing and optimising Python APIs for serving ML models at scale; building communication layers over HTTP, WebSockets and gRPC; architecting low latency, fault tolerant and secure backends for real time inference; implementing authentication, rate limiting and request prioritisation; integrating voice agent and LLM SDKs; working with PostgreSQL, Redis and ClickHouse; building event driven and streaming architectures on Kafka and Redis Streams; and working on canary deployments and CI/CD. Location and office reality: Bengaluru. ⚠️ Years of experience: Sarvam publishes no experience figure anywhere in this posting. We write no number rather than guessing one, which means this role will not appear if you filter the board by years. Judged by the requirement list it reads mid to senior, but that is our reading and not the employer's statement. Who this is for: a Python backend engineer who wants latency and reliability problems rather than CRUD, and who is interested in AI infrastructure without needing to be a researcher. The posting describes a high talent density team with high ownership from day one, which usually means a demanding pace.
What the posting requires: experience owning product or platform systems end to end across multiple engineering and product teams at staff level. Strong fullstack skills with proficiency in Go, Ruby and Node. Depth in at least one of reporting and metrics platforms, graph data systems, or data access and warehouse integrations including Snowflake, Databricks or BigQuery. Hands on experience building production data ingestion, systems integrations or data access capabilities. Experience operating across multiple deployment environments. The day to day: architecting how data is ingested, modelled and synchronised into the Knowledge Graph; coordinating integration with Jira, observability tools, Zendesk and ServiceNow; designing the data marketplace for Snowflake, Databricks and BigQuery; publishing observability data as OpenTelemetry and supporting the access APIs; defining operational readiness across GitLab.com, Dedicated and Self-Managed; turning ambiguous product problems into technical plans with Product and Design; coordinating with the graph backend, AI platform and infrastructure teams; and mentoring senior and intermediate engineers. Location and office reality: listed as Bangalore, India. GitLab is a remote first company, but this particular requisition carries a Bangalore location rather than the Remote tag its other postings use, so confirm the arrangement with recruiting rather than assuming. ⚠️ Years of experience: GitLab does not publish a years figure on any of its postings, including this one. We write no number rather than inventing one, so this role will not appear under any experience filter. The Staff title and the end to end ownership language are the only level signals available. Who this is for: a fullstack engineer with genuine data platform depth. GitLab also states that all team members are expected to use AI in their daily workflow, which is a cultural expectation worth knowing before you apply.
What the posting requires: senior full stack development experience with a strong product orientation and a rigorous test first mindset. React and Next.js on the frontend. Ownership of the full delivery lifecycle: building features, defining test cases, running deployments and validating production readiness. Comfort using AI agents and automation to generate test coverage at scale while owning the calls the tooling cannot make. Willingness to commit to sprint and release deadlines and raise risks early. The day to day: designing, building and maintaining full stack features across the Aedeon frontend with a focus on reliability, performance and user experience; working with product management, designers and backend or DevOps engineers to take features from requirement to tested release; participating in sprint planning, backlog grooming and retrospectives; owning delivery end to end including post release validation; and coordinating with DevOps and QA so the deployment pipeline is clean and repeatable. The interview process, which Mactores publishes: a panel interview, described as a structured conversation with members of the hiring team covering your experience, product thinking and how you work. The posting also asks you to answer as many application questions as possible to speed things up. Very few employers on this list tell you the process in advance. Location and office reality: Mumbai, Maharashtra. ⚠️ Years of experience: Mactores publishes no figure. The posting says senior, and we write no number rather than guessing, so this role will not appear under an experience filter. Who this is for: a product minded full stack engineer who wants ownership of releases and is genuinely comfortable with an AI heavy workflow. The posting reads as a demanding delivery culture, and it says so openly, which is better than finding out later.
What the posting requires: experience building and shipping agentic or conversational AI systems in production rather than prototypes. Strong intuition for where LLM behaviour breaks down under real world conditions and how to fix it systematically. Systems thinking that treats conversation architecture, evaluation, serving infrastructure and candidate experience as one problem. Care about the quality bar at the level of a user who depends on the output rather than a researcher measuring aggregate metrics. The day to day: architecting and developing Chakra end to end, covering agent design, conversation management, real time response evaluation, scoring methodology and report generation; building the infrastructure that keeps the 200,000th interview as coherent as the first; designing evaluation and benchmarking pipelines for interview quality, candidate experience consistency and report defensibility; building fine tuning and RLHF workflows to push model judgment past off the shelf behaviour; defining and instrumenting the quality bar; and working across data pipelines, model serving, latency constraints and the product experience itself. Location and office reality: hybrid in Bengaluru, India. ⚠️ Years of experience: HackerRank publishes no figure on this posting. We write no number rather than guessing, so it will not appear under an experience filter. The requirement to have shipped production agentic systems is the real gate, and that tends to imply several years. Who this is for: an ML engineer who has taken LLM systems past the demo stage and has opinions about evaluation. If your experience is model training rather than production behaviour and guardrails, the emphasis here is on the latter. There is a second HackerRank ML role open on the evaluation side if this specific product does not appeal.
What the posting requires: 5 or more years in technical support, product operations, technical account management or engineering, with a specific focus on complex technical products such as APIs, SaaS or telecommunications. Experience in the technology industry including APIs and VOIP, in either a development or support capacity. Proven analytical skills using data tools such as Splunk, Datadog, Snowflake, SQL or Tableau to turn customer feedback and support trends into insight. Excellent communication and influence skills, including the ability to negotiate prioritisation of supportability features with technical stakeholders. Familiarity with customer trust applications is preferred. Nice to have: project management methodology or experience managing programmes and product launches; proficiency in a scripting or programming language such as Python, Java or Node.js to better understand the developer experience; and knowledge of design thinking. The day to day: embedding supportability requirements into the earliest stages of the product development lifecycle through design reviews and technical planning with R&D; analysing support data to build business cases that influence what R&D prioritises; specifying proactive product features that deflect support tickets; orchestrating global operations readiness for new feature launches; and translating complex customer use cases into requirements. Location and office reality: the posting states directly that the role is remote and based in India, with no state restriction listed on this requisition. Twilio describes itself as remote first. Note that some other Twilio India postings do restrict which states you can live in, so confirm during the process. Who this is for: someone who has done deep technical support or technical account management on an API product and wants to influence the product rather than keep absorbing its rough edges. Twilio explicitly encourages applicants whose careers have not followed a traditional path. This is not a coding role, though scripting familiarity helps.
What the posting requires: 8 or more years designing, building and scaling data, machine learning and AI systems on premises and in the cloud using Python, Scala and Java in production, with expertise in machine learning or generative AI. Experience with AWS, Azure or GCP, with Databricks familiarity a plus. Proficiency in the data engineering needed to orchestrate end to end ML training pipelines, ideally processing large datasets with Apache Spark. Subject matter expertise in feature engineering, ML frameworks, model training, monitoring, drift detection and retraining. Proficiency with algorithms, deep learning and NLP techniques. Prior experience building, designing or troubleshooting LLM based generative AI applications. Familiarity with agentic frameworks such as LangChain and LangGraph. Expertise in context orchestration including prompt design, memory management, retrieval systems, vector embeddings, semantic search and tool integrations. Comprehensive MLOps and LLMOps knowledge. Prior support or customer facing experience. The day to day: acting as senior technical expert on complex issues spanning data pipelines, ML pipelines and AI applications; troubleshooting production workloads at code level; diagnosing ML and LLM deployments including inference, autoscaling, monitoring and alerting; guiding customers on model lifecycle and observability; supporting generative AI use cases across RAG, agents, vector search and prompt engineering; and collaborating internally to influence the roadmap and contribute documentation. Location and office reality: Bengaluru, India. Who this is for: an ML engineer who genuinely enjoys debugging other people's systems and talking to customers while doing it. This is a support engineering seat, not a platform building one, but the technical bar is the same. Readers asked for customer facing technical roles by name, and this is one of the more hands on examples on today's list.
What the posting requires: 8 or more years of technical, partner facing experience, and the posting names Systems Engineer, Solutions Architect or Technical Account Manager as the shapes it means, in cybersecurity, cloud infrastructure or networking. Strong technical depth in Cloudflare One or equivalent SASE and SSE architectures, zero trust, DNS and application security, plus hands on familiarity with AI deployment, AI Gateway, LLM orchestration frameworks or vector databases. A proven track record developing technical talent or building champion programmes inside partner organisations. Deep understanding of enterprise IT and multi cloud and hybrid environments, with complex multi stakeholder project management. Demonstrated ability to manage the technical lifecycle of a deal from pre sales discovery through post sale delivery. Strong communication, presenting complex architectures to both partner leadership and engineers. A bachelor's in computer science or engineering, or equivalent practical experience. The day to day: owning the technical relationship with assigned partners and building joint go to market plans; enabling partners to lead their own technical discovery and architecture; cultivating technical champions; owning the technical account plan; co developing joint service catalogues and managed SASE practices; acting as escalated technical contact for architectural health; and using Cloudflare's own AI tooling to automate repeatable technical work. Location and office reality: available locations are listed as Bengaluru, India and India, with the requisition marked hybrid or remote. One of only three roles on today's list with any remote option. Who this is for: a solutions engineer or technical account manager with real network and security depth. Be clear that this is a partner facing commercial role: it involves pre sales work and pipeline influence, and the posting says so. It passes the technical bar because the requirements demand hands on architecture and platform knowledge, but if you want to write code all day this is not that job.
What the posting requires: 12 or more years in a customer facing technical role, including significant pre sales, consulting, partner or solutions architecture experience in enterprise software. Strong experience navigating complex sales cycles and aligning technical and business stakeholders. Hands on experience with modern application development, data platforms or cloud native systems, including at least one scripting or programming language such as Python, JavaScript, Java, C# or SQL. Experience designing distributed systems in cloud and hybrid environments with an understanding of scalability, resilience and security. The ability to translate technical architecture into business value for executives, architects and developers. Experience in one or more of hyperscaler partnerships, ISV integrations, AI and ML applications, data engineering, platform modernisation or developer platforms. Demonstrated ability to create technical assets and lead workshops. The day to day: designing architectures on MongoDB Atlas for customer and partner led solutions; acting as trusted technical advisor through architecture reviews and modernisation strategy; working complex partner opportunities through discovery, demos, proofs of value and sizing; building joint partner offerings and reference architectures; creating reusable field assets; advising on RAG, vector search and agentic workflows; relaying field feedback to product and engineering; supporting territory and account planning; representing MongoDB at workshops and industry events; and mentoring peers. Location and office reality: India, on MongoDB's remote working model, stated in the posting. Who this is for: a senior solutions architect who wants the partner ecosystem rather than direct accounts, and who values working from anywhere in India. The coding requirement is real but light: one language, used to build demos and assets. At 12 or more years this is aimed well into a career.
What the posting requires: a customer facing technical lead with enough full stack depth to configure, debug and explain web applications and integrations, and to generate API scripts as needed in Ruby or Python. Confidence leading onsite conversations with prospects and enterprise customers while gathering requirements and shaping technical approaches. Clear communication that can go deep with engineers or simplify for non technical audiences. Strong operational discipline in planning, executing and following through. Nice to have: experience as a software, solutions or sales engineer working with HR technology, applicant tracking systems, IDEs, developer tools, or API first and integration heavy systems; and a track record of taking projects from scoping through delivery. The day to day: leading customer facing engagements including discovery, pilots and demos as the primary technical voice; partnering onsite with customers to uncover developer needs and shape solutions; keeping projects on track through disciplined execution and proactive updates; using AI tooling where it delivers faster and more reliable outcomes; and collaborating with product, engineering and go to market teams to represent the customer. Location and office reality: hybrid in Bengaluru, India, with the role itself involving onsite work at customer locations. Expect travel. ⚠️ Years of experience: HackerRank states no figure on this posting. We write no number rather than guessing, so it will not appear under an experience filter. Who this is for: an engineer who likes customers and variety and does not want a single codebase. Readers asked for technical account management and customer success roles by name, and this is one of the more technical versions of that shape. If being onsite at a customer site regularly does not appeal, skip it.
What the posting requires: significant experience in field engineering, solution architecture or enterprise platform deployment, with a track record owning senior technical relationships. Deep expertise in enterprise fleet automation, specifically Python and PowerShell scripting at production scale across provisioning, diagnostics and remediation. Advanced proficiency with Intune, SCCM and enterprise MDM architecture. Experience with cross OEM hardware interoperability and platform level troubleshooting. The day to day: owning the technical relationship with strategic enterprise accounts from architecture through deployment and ongoing platform health; leading solution architecture for on device AI on AI-PC platforms including NPU offload design and SLM configuration; owning end to end escalation delivery for the most complex platform, firmware and fleet issues; building fleet automation frameworks; driving cross OEM interoperability directly with hardware partners; defining deployment architecture standards and runbooks; acting as the field to product conduit; leading technical presales including architecture reviews, proof of concept design and executive level presentations; and mentoring other forward deployed engineers. Location and office reality: Bengaluru. ⚠️ Years of experience: Sarvam publishes no figure. The Principal title and the description of it as the most senior IC seat in the function are the only level signals. We write no number rather than guessing, so it will not appear under an experience filter. Who this is for: a field or platform engineer with genuine Windows endpoint management depth, Intune and SCCM specifically, who wants that skill applied to on device AI rather than corporate IT. The presales element is real, so expect executive conversations alongside the debugging. It is a demanding, autonomous seat and the posting does not pretend otherwise.
Added July 27, 2026
What the posting requires: - 0 to 1 years in software development, ideally with internships in integrations or data tools. This is the stated candidate persona and it is the reason this role is on the list. - A B.Tech in Computer Science or equivalent from a reputed college. This is stated in the posting. - Basic object oriented programming skills and familiarity with design principles. - Exposure to data pipelines or APIs, and eagerness to learn concurrency and performance basics. - Foundational knowledge of REST APIs, for example making calls and handling JSON. The posting says explicitly that no deep expertise is needed here. - Proficiency in Java, TypeScript or Python, with good problem solving using data structures and algorithms. - Strong analytical and logical thinking for real world challenges. What the work actually looks like: - Implement SaaS connectors for assigned applications, learning application specific nuances such as basic auth and data extraction. - Assist in building simple REST API components, focusing on clean implementation and testing. - Debug and optimise code for data pipeline efficiency, under mentorship. - Contribute to feature breakdown, coding and documentation for smaller tasks. - Apply logical thinking to solve integration issues and improve component quality. What this tells you about the role: the words under mentorship and assist appear in the responsibilities, which is a good sign for a first job. You are not being asked to own a system alone. The work is connector and integration engineering, which is a real specialism and a useful one, since almost every SaaS company needs people who can make two systems talk to each other. About the company: Hevo is based in San Francisco and Bangalore, powers data analytics for more than 2,000 companies across 45 plus countries, and states its mission as building technology from India for the world that is simple enough that anyone can unlock the potential of their data. Location and working pattern: Bengaluru. Office days are not stated. Honest fit guidance: if you are a recent graduate or in your first year, this is the role on today's list to spend your best application on. The degree requirement from a reputed college is stated explicitly, so know that going in if your background is non traditional. Prepare by being able to talk about an API you have consumed and a data problem you have debugged, because that is exactly what the responsibilities describe. No interview process is published.
What the posting requires: - A Bachelor's or Master's in Computer Science, Engineering or a related field, with 5+ years of enterprise integration experience. - At least 3 years of integration development using platforms such as Workato, MuleSoft or Boomi. - Deep understanding of enterprise integration design patterns, messaging and event driven architectures, plus Workato concepts including callable recipes, event streams and task optimisation. - Proficiency with Workato connectors including Salesforce, NetSuite, HRIS and Google Workspace, along with Python or Ruby scripting. - Strong development experience implementing Workato at scale: automation, observability and monitoring, and debugging in complex environments with many connected systems, plus DevOps process adhering to compliance, audit and internal CI/CD. - Hands on experience implementing secure and scalable REST APIs, and implementing Workato MCP and agentic workflows. - Strong problem solving and debugging across multiple connected systems and their environments. - Excellent analysis and design ability, with focus on system design, flow, scalability and performance, and mapping business requirements to technical solutions. What the work actually looks like: - Automate, develop and support integrations across various business systems, platforms and tools. - Work with different business units and technical teams to gather requirements and design solutions. - Create scalable solutions and operationalise integrations. - Implement and promote integration best practices. - Participate in an on call support rotation. The success measures the employer publishes: - Deliver high quality, scalable integration recipes and flows within the Quote to Cash process and other GTMTech programmes, on time. - Successfully deploy and operationalise integrations while keeping system stability and performance. - Proactively identify and resolve complex integration issues with minimal disruption to core business operations. - Translate complex requirements into technical design with business and technical teams. Location and working pattern: the posting states MongoDB wants candidates based in Gurugram for its hybrid working model. Honest fit guidance: the Workato requirement is specific and enforced, so this suits an integration specialist rather than a general backend engineer. If you have built on MuleSoft or Boomi the transferability is real. The on call rotation is stated, so factor it in.
What the posting requires: - A Bachelor's degree in Computer Science, Engineering or a related field. - 5+ years of professional Java development experience with Spring, JDBC, and MyBatis or Hibernate or equivalent. - Experience with application modernisation, database migrations or large scale refactoring initiatives. - Strong SQL expertise: you can analyse, interpret, optimise and rewrite complex SQL embedded in Java applications. - Deep understanding of JDBC, ORMs, Java transaction patterns and database driven application flows. - Experience on enterprise grade, high performance applications with complex data interactions. - Strong communication skills and the ability to work with globally distributed teams in US time zones. Nice to have: - Experience with PostgreSQL or Aurora PostgreSQL, or modernisation from legacy databases such as Oracle, SQL Server or DB2. - Exposure to automated code refactoring tools or GenAI assisted remediation workflows. - Familiarity with CI/CD environments, performance testing tools and observability stacks. - Consulting or professional services experience delivering fixed timeline modernisation projects. What the work actually looks like: - Analyse and remediate large enterprise Java codebases, replacing legacy and database specific SQL constructs with modern, standards compliant SQL. - Convert embedded SQL in Java services and MyBatis XML mappers: vendor specific functions, sequences, pagination logic, dynamic SQL and error handling patterns. - Work with schema and database migration engineers so application layer SQL lands aligned with the modernised target schema. - Refactor Java transaction logic, error handling, drivers and ORM or DAO layers. - Run unit, integration and performance testing to confirm functional parity and hit performance SLAs after modernisation. - Support production cutover: validation, monitoring setup, rollback planning and stabilisation until the system holds. - Produce engineering documentation that outlives the engagement: SQL remediation guides, code migration runbooks, troubleshooting guides and knowledge transfer material. What the company says about how the work splits: the agent platform does the repetitive 60 to 70 percent that a traditional consulting engagement would staff humans for, including mechanical SQL conversion and the regression harness. Your hours go to the refactoring judgement. Location and working pattern: Mumbai, with distributed collaboration across US and India teams and an expectation of overlap with US time zones. Honest fit guidance: this is deep, unglamorous, high value work. If you have lived inside a large Java codebase with vendor specific SQL, five years is enough. If your Java is greenfield microservices only, the legacy remediation requirement is the gap.
What the posting requires as mandatory: - Experience of 5 to 8 years for the Staff level, or 9 to 12 years for the Sr Staff level. One posting, two levels, so read the band that matches you. - Strong programming experience in Java. - Strong computer science fundamentals, especially algorithms, data structures, object oriented programming and SQL. - Hands on experience with Spring and Spring Boot, and ORM frameworks. - Good understanding of database internals and schema design across different data stores, both relational and NoSQL. - Experience designing and developing APIs for large scale data systems with low latency. - Experience working in a client server, cloud hosted environment. - Strong analytical and problem solving skills. Good to have: - Experience with AWS, described as highly desirable. What the work actually looks like: Device health and monitoring: - Understand IoT devices and accessories to build and enhance device monitoring and health solutions. - Develop systems for device health monitoring covering camera, LTE, GPS, storage, power, real time clock and accessories. - Implement device online and offline detection and recovery mechanisms. - Design health state transitions and root cause classification for device issues. Backend and platform: - Design, develop and maintain high performance, reliable, reusable backend services. - Build and test large scale SaaS products processing massive volumes of real time data. - Build and operate systems processing hundreds of millions of IoT sensor events per day. System design and ownership: - Translate product requirements into technical designs and tasks, and execute across the full development lifecycle. - Design APIs with low response times and efficient resource use for large data sets. - Provide technical guidance and mentorship to junior engineers, and debug complex issues to root cause. ⚠️ Location and working pattern, stated explicitly: Whitefield, Bangalore, **on site 5 days a week**, general shift or evening shift. Netradyne is one of the few employers on this board that publishes its office policy, and this one is fully in office with a possible evening shift. Factor that in before applying. A note on the employer: Netradyne postings carry a recruitment fraud warning. Official communication comes only from netradyne.com or us-greenhouse-mail.io addresses, and the company never charges candidates a fee. Honest fit guidance: if you have 5 to 8 years of Java backend work at scale, apply to the Staff band rather than being put off by Sr Staff in the title. IoT domain experience is not required, but comfort with high volume event processing is.
What the posting requires: - 5 to 10 years of experience in field engineering, enterprise deployment or senior IT support roles. - Deep, hands on expertise with Intune and SCCM covering policy design, compliance management and large scale fleet deployment. The posting marks this **non negotiable**. - Advanced PC hardware diagnostics across BIOS, firmware and hardware level troubleshooting on varied enterprise device configurations. Also marked **non negotiable**. - Strong PowerShell scripting, with the ability to build and maintain automation frameworks for enterprise environments. - Expert level knowledge of Windows OS in enterprise and managed fleet contexts. - A proven track record in customer facing technical roles, comfortable engaging enterprise IT leadership. - Experience owning SLA management and escalation governance across multiple enterprise accounts. Bonus points: - Prior experience with on device AI, edge computing or sovereign enterprise AI deployments. What the work actually looks like: - Lead deployment and configuration of Sarvam's on device AI platform across large enterprise PC fleets using Intune and SCCM. - Own escalated hardware diagnostics, resolving complex BIOS, firmware, driver and hardware level issues. - Architect and maintain PowerShell automation frameworks for deployment, monitoring and configuration management at scale. - Define and enforce MDM policy architecture via Microsoft Intune. - Drive presales engagements: technical discovery, scoping proof of concept deployments, and presenting to enterprise IT leadership. - Own SLA governance across a portfolio of enterprise accounts, managing escalations and resolution quality. - Act as primary technical liaison between enterprise customers and Sarvam's product and engineering teams. - Build and maintain deployment playbooks, technical runbooks and support documentation. - Mentor and guide other field engineers. What makes the context unusual: the posting describes the team as co owning the most ambitious on device AI problem in India, building sovereign models that run at the silicon level, embedded with partners including Qualcomm, Intel, HP, Apple and NVIDIA. Location and working pattern: Bengaluru, described as on site or hybrid, with significant customer facing and mentoring responsibility. Honest fit guidance: this is enterprise endpoint engineering more than it is AI engineering, and the two non negotiables tell you where applications will be judged. If your background is Windows fleet management at scale and you want to work at an AI company, it is a rare bridge. If you want to build models, this is not that role.
What the posting requires: - 5 to 8 years in field engineering, solutions engineering, technical account management or senior client facing engineering roles. - Strong Python proficiency, with the ability to read, debug and contribute to production FastAPI services and ML pipelines. Marked **non negotiable**. - Experience with audio and video processing workflows: FFmpeg, codec pipelines, media formats or streaming infrastructure. Also marked **non negotiable**. - A proven track record working with enterprise media, OTT or content localisation clients. - Comfort operating across the stack: REST APIs, async job queues such as Celery or Redis, PostgreSQL, cloud storage on Azure, GCP or AWS, and Kubernetes. - Strong debugging instincts, tracing failures across distributed systems from API through queue and worker to ML inference and storage. - Experience owning SLA management and escalation governance across multiple enterprise accounts. - Excellent communication, comfortable engaging CXO and VP level stakeholders. What the work actually looks like: - Lead end to end integration of the dubbing platform into enterprise content workflows across OTT, media houses, ed-tech and enterprise learning and development. - Own the technical relationship with strategic accounts: scoping requirements, designing integration architecture and ensuring production readiness. - Debug and resolve complex pipeline issues across the full dubbing stack: audio separation, speech recognition, translation, text to speech and video stitching. - Tune pipeline parameters for client specific content: voice activity detection thresholds, translation glossaries, TTS voice profiles and audio mixing. - Drive presales engagements including technical discovery and proof of concept scoping. - Build and maintain integration playbooks, API guides and troubleshooting runbooks. - Define SLA governance across enterprise accounts covering turnaround time, quality benchmarks and escalation resolution. - Act as primary technical liaison between enterprise clients and Sarvam's dubbing product and ML engineering teams. - Mentor other field engineers, and contribute fixes back to internal platform codebases when client deployments surface bugs. Location and working pattern: Bengaluru, with significant customer facing responsibility. Honest fit guidance: the media pipeline experience is the differentiator. Plenty of engineers can debug a distributed system, far fewer have worked with FFmpeg and codec pipelines, and that is what the posting marks non negotiable alongside Python. If you have both, the customer facing element is learnable. If you have neither, the title being FDSE will not carry the application.
What the posting requires: - 6 to 9 years of software development experience with enterprise grade software. - Experience building scalable, high performance cloud services. - Expert coding skills in Scala or Java backend. The product is built in Scala on the Lightbend stack with Play and Akka. - Deep knowledge of databases, query optimisation and views. - Development on cloud platforms including AWS. - Expertise building scalable, event based asynchronous systems on a microservices architecture. - Experience with Docker and Kubernetes. - Expertise building REST APIs. - Cybersecurity experience and adversarial thinking. - Willingness to learn, challenge yourself and share ideas with the team. - Ability to multitask across roles in a fast paced environment: leading a feature design one week, fixing a critical bug or improving CI the next. - A BSCS or equivalent is required, MSCS or equivalent strongly preferred. What the work actually looks like: - Work with the engineering team to design, build and test the cloud based platform across front end, back end and services. - Participate in feature estimation and prioritisation, sprint planning, biweekly sprints, code reviews and retrospectives. - Contribute to product development: understand customer needs and work with product to design, plan and implement new features. - Support early customers by investigating and fixing production issues. - Improve processes and make the right tradeoffs between agility, cost and reliability. Levelling, which matters here: the posting states this team is hiring across all levels and that candidates are individually assessed and levelled based on their skills and experience. So the Staff in the title is not a hard floor. Location and working pattern: listed as India without a specific city. Netskope has a Bangalore office and describes open desk layouts, so confirm the base location with the recruiter. Honest fit guidance: the Scala requirement is the real filter. Netskope will take strong Java backend engineers, since the posting says Scala or Java, but the codebase is Scala on Play and Akka and you would be working in it daily. If you have wanted an excuse to work in Scala at scale on a security product, this is one of the few such roles in India. The early team member framing means less structure than a mature team.
What the posting states: - Experience required: 6 to 9 years. - Native Android and iOS development. The title specifies both platforms rather than one, so cross platform depth is the expectation rather than a single specialism. - Employment type: full time. What the work involves, based on the role and the product: building and maintaining the native mobile applications through which fleet customers and drivers interact with Netradyne's driver monitoring and safety scoring platform, working alongside the backend, embedded and analytics teams that produce the data those apps display. ⚠️ Location and working pattern, stated explicitly in the posting: Whitefield, Bangalore, **on site 5 days a week**, general shift or evening shift. This is one of the few postings on today's board that publishes its office policy precisely. If you need hybrid or remote, this role is not it, and the evening shift possibility is worth clarifying at first contact. About the employer: Netradyne provides AI powered technologies for fleet management and road safety, is an award winning leader in fleet safety and video telematics, and serves thousands of commercial fleet customers across North America, Europe and Asia. Founded in 2015, headquartered in San Diego with offices in San Francisco, Nashville, the UK and Bangalore. The company reports growth exceeding 4x year over year. A note on the employer: Netradyne postings carry a recruitment fraud warning. Official communication comes only from addresses ending in netradyne.com or us-greenhouse-mail.io, the company never requests sensitive personal data over text or unsecured channels, never promises advance payment for work equipment, and never uses agencies that charge candidates a fee. Honest fit guidance: this posting is thinner on detail than most on today's list, so treat the 6 to 9 years and the dual platform requirement as the firm parts and ask the recruiter about scope, team size and what the apps actually do. The office policy is the clearest signal in it and it is a strict one. If you are a native mobile engineer in Bangalore who is fine with full time office work, the product is more interesting than most: real vehicles, real safety outcomes, real scale.
What the posting states: - Job title: Staff Engineer, Embedded System Engineer. - Department: Device. - Experience: 6 to 12 years. That is a wide band in a single posting, so treat 6 as the real floor. What the work involves, based on the department and product: embedded software for Netradyne's edge devices, the camera units that run computer vision on the vehicle itself rather than in the cloud. That work sits alongside the company's other device roles covering multimedia pipelines, middleware on Linux, board support package development and hardware engineering, all of which Netradyne staffs separately, so expect a specialised slice rather than the whole device stack. Location and working pattern: Bangalore. This particular posting does not state the number of office days, though several other Netradyne listings specify on site five days a week at Whitefield. Ask rather than assume, because the company's other device roles are explicitly full time in office. About the employer: Netradyne provides AI powered technologies for fleet management and safer roads, is an award winning industry leader in fleet safety and video telematics, and empowers thousands of commercial fleet customers across North America, Europe and Asia. It sets its standard on 25 plus billion miles vision analysed for risk and an industry first driver scoring system. Founded in 2015, headquartered in San Diego with offices in San Francisco, Nashville, the UK and Bangalore. A note on the employer: Netradyne includes a recruitment fraud warning in its postings. Official communication comes only from netradyne.com or us-greenhouse-mail.io addresses, the company does not request sensitive personal data via text or unsecured channels, does not promise advance payment for equipment setup, and does not use agencies that charge candidates a fee. Honest fit guidance: this posting is light on a requirements list, which cuts both ways. It means fewer boxes to fail on, and it means you should ask early which part of the device stack the role covers, since Netradyne runs separate reqs for multimedia, middleware, BSP and hardware. If you have shipped embedded software on Linux based devices and want work where the constraint is real hardware rather than cloud cost, six years is enough to be taken seriously here.
What the posting requires as minimum qualifications: - A minimum of 6+ years of experience in technical support, with at least 4 years focused on DLP and CASB solutions. - A foundational understanding of AI and ML technologies, and experience leveraging, securing or positioning AI driven solutions within your functional domain. Zscaler lists this first. - Experience with data loss prevention, securing SaaS, and Cloud Access Security Brokers. - Practical working knowledge of AWS, Azure or GCP cloud environments, paired with a strong understanding of Unix, Linux and Windows operating systems. - Deep understanding of data protection principles and practices. Preferred qualifications: - Experience deploying or supporting AI powered sensitive data discovery tools or automated data classification models to enhance DLP capabilities. - Experience with scripting and automation using Python or PowerShell. - Knowledge of regulatory requirements and compliance standards such as GDPR, HIPAA or PCI DSS. What the work actually looks like: - Provide advanced troubleshooting and resolution for complex DLP issues raised by enterprise customers. - Perform root cause analysis to identify underlying problems and implement lasting solutions. - Work with product development, engineering and other cross functional teams to resolve issues and improve Zscaler's DLP products. - Maintain clear and proactive customer communication through the support process. How this compares to the neighbouring role: Zscaler also lists an Escalation Engineer DLP requiring 8+ years with at least 5 on DLP. Same specialism, one level up. If you sit between 6 and 8 years this posting is the better fit, and the escalation one is a natural next step. Location and working pattern: Bangalore or Mohali. Zscaler's DLP postings are described as hybrid roles based in those offices, reporting into Product Support. What Zscaler says about its culture: impact over activity, constructive and honest debate, customer obsession, ownership and accountability, with an emphasis on using AI to amplify individual impact. Honest fit guidance: the 4 years specifically on DLP and CASB is the filter, not the 6 years overall. General cloud support experience will not clear it. Support engineering at this tier is genuinely technical work with direct engineering contact, but be clear eyed that it is a support function with the customer communication load that implies.
What the posting requires: - A BS or higher in Computer Science, or a related field. - 7+ years of production level experience in one of Java, Scala, C++ or a similar language. - Comfort working towards ambitious goals in a fast moving environment. - Experience developing large scale distributed systems. - Hands on experience developing and operating backend systems. What the work actually looks like, given the team's remit: - Build and operate the platform systems behind usage metering, billing and revenue for Databricks. - Solve real business needs at large scale through software engineering. - Contribute across project phases from design and development through implementation and ongoing operations. - Investigate and help prevent production issues, since correctness in this domain is directly customer visible. Why this kind of team is worth considering: money and billing systems are usually the highest correctness bar in a company. The data volumes are the same as the rest of the platform, but the tolerance for error is far lower, which tends to mean strong engineering practice, good testing culture and clear ownership. Location and working pattern: Bengaluru. Databricks says it is in the process of setting up new teams from scratch at this site, so expect an in office or hybrid arrangement. The exact number of days is not stated in the posting. Compliance note in the posting: where a role requires access to export controlled technology or source code, Databricks states that applying for a US government licence is at its discretion, and it may decline to proceed with an applicant on that basis alone. Worth reading before investing time in the process. Honest fit guidance: seven years of real production backend work is the bar, and the language list is broad enough that the specific language matters less than the scale you have operated at. If you have worked on billing, metering, payments or any system where a wrong number is a customer incident, say so prominently in your application, because that is exactly the experience this team is buying.
What the posting requires: - 7+ years of experience in information security, with at least 5 years focused specifically on endpoint security engineering. - Deep hands on expertise with enterprise EDR platforms. The posting names CrowdStrike Falcon, Microsoft Defender for Endpoint, SentinelOne and Carbon Black. - Strong experience deploying, managing and tuning enterprise DLP solutions. Named examples are Microsoft Purview, Symantec DLP and Cyberhaven. - Demonstrated experience in insider threat detection and response, including familiarity with UEBA tools and behavioural analytics. Nice to have: - Experience with hybrid cloud environments across AWS, Azure and GCP. - Prior experience in the EV, automotive or critical infrastructure industry. What the work actually looks like: - Lead insider threat detection and response: build and maintain detection logic, investigate anomalous user behaviour, and drive incident response for insider threat cases. - Manage and mature the enterprise data loss prevention programme: define and refine DLP policies, monitor alerts, investigate violations and coordinate remediation with stakeholders. - Own end to end management of the enterprise EDR platform across Windows, macOS and Linux endpoints, covering deployment, policy configuration, tuning and ongoing optimisation. ⭐ Location and working pattern: the posting states **Gurgaon or remote**. That makes this the only role on today's board with a remote option, which matters if relocation is what stands between you and a job. The posting does not elaborate on what remote means in practice, so confirm the expectation, including any travel or occasional office days, before assuming it is fully remote. About the employer: ChargePoint has focused since 2007 on making the transition to electric easy for businesses, fleets and drivers, and operates hardware, software and mobile solutions across North America and Europe. Honest fit guidance: the 5 years specifically on endpoint security is the real filter rather than the 7 years overall. This is corporate security engineering, so if you want product security or application security work this is a different discipline. ChargePoint states it provides reasonable accommodations throughout the hiring process and publishes an email address for accommodation requests.
What the posting requires: - 7 to 10 years of experience in FP&A systems, enterprise performance management or enterprise planning implementations. - Hands on experience in at least one platform: Pigment (preferred), Anaplan, or Workday Adaptive Planning. - Strong understanding of financial planning processes and financial statements, annual sales planning, and driver based modelling and forecasting. - Experience with ERP systems, NetSuite preferred. - Experience with CRM systems, Salesforce preferred. - Experience with data warehouses. Additional technical skills: - Exposure to Python or scripting is described as a plus. - Experience with ETL and integration tools. Preferred qualifications: - Certifications: Anaplan Certified Model Builder or Solution Architect, Workday Adaptive Planning certification, or Pigment Modeler experience. - Experience supporting SaaS or consumption based business models. - Exposure to headcount and compensation planning, annual sales planning, and revenue modelling covering ARR, churn and expansion. - Experience working in a Global Capability Centre or offshore delivery model. What the work actually looks like: Enterprise planning delivery: - Design and build scalable planning models across financial planning (profit and loss, cash flow, balance sheet), workforce planning and cost modelling, and sales and revenue forecasting (ARR, pipeline, bookings). - Own end to end delivery working with the product manager: design, build, test, deploy and support. Model development and optimisation: - Build multi dimensional, driver based models with a strong focus on performance. - Develop scenario planning, versioning and forecasting capabilities. - Optimise model size and calculation performance. Location and working pattern: the posting states MongoDB is looking for candidates based in Bengaluru or Gurugram for its hybrid working model. Honest fit guidance: be clear with yourself about what this is. It is a specialist enterprise planning platform role, closer to FP&A systems work than to backend software engineering, and the certifications listed under preferred qualifications tell you the discipline it belongs to. If you have built models in Anaplan, Pigment or Adaptive Planning, this is a strong senior seat at a well known technology company. If you are a software engineer hoping this is a finance flavoured coding job, it is not.
What the posting requires as mandatory: - A B.Tech, M.Tech or PhD in Computer Science, Electrical Engineering, Statistics, Mathematics or a related field. - 8+ years of experience in data science, analytics or a closely related domain. - Strong foundation in probability, statistics and estimation theory. - Strong programming in Python, with solid fundamentals in object oriented programming, algorithms and data structures. - Deep familiarity with SQL, complex query writing, indexing and database internals, plus working knowledge of at least one NoSQL store. - Experience with data visualisation and analytical storytelling. - Excellent written and verbal communication. - Familiarity with AI powered tools for analytics and software development, including using them for exploratory analysis, experiment analysis and documentation, and critically evaluating AI generated output for correctness, statistical validity and reproducibility. Preferred skills: - Exposure to cloud platforms and services such as AWS Kinesis, EKS and autoscaling systems. - Experience building lightweight web or service components with Flask or Django. - Prior experience with large scale, noisy, real world datasets. What the work actually looks like: - Design, implement and maintain offline and online evaluation frameworks for AI and ML features. - Define, validate and evolve the KPIs, success metrics and audit methodologies used across teams. - Perform deep error analysis, bias analysis and segmentation to identify failure modes. - Own golden datasets, validation protocols and benchmarking standards. - Conduct large scale analytical studies on feature performance, data quality and system behaviour. - Design and review experiments including offline evaluations, controlled rollouts and A/B tests, ensuring statistical correctness. - Perform post deployment monitoring and regression detection. - Build tools, dashboards and automation to scale audits and reporting. - Mentor junior data scientists on statistical rigour, experiment design and analytical storytelling. How this differs from the 5+ years version of this role published on this board on 2026-07-26: same team and same responsibilities, but this posting sets the bar at 8+ years rather than 5+. If you are between 5 and 8, look for the other one. Location and working pattern: Bangalore. This posting does not state office days, though other Netradyne listings specify five days on site. Honest fit guidance: if you want to build models, this is explicitly not that role. It suits someone happier proving whether a system works than building it, and willing to tell a product team its metric is wrong.
What the posting requires: - 8+ years of production level experience in one of Python, Java, Scala, C++ or a similar language. - 4+ years of experience in a networking focused context, which is the specialism this role is hiring for. - Experience developing large scale distributed systems. - Hands on experience developing and operating backend systems. What the work actually looks like, given the team's remit: - Build and operate the networking layer for a platform running across AWS, Azure and GCP at a fleet size measured in millions of virtual machines. - Handle the differences between cloud providers' networking primitives, and design so that provider level faults degrade gracefully rather than breaking customer workloads. - Low level systems debugging and performance measurement on large production clusters. - Contribute across the project lifecycle from design through implementation and ongoing operation. The operating context Databricks describes: at its scale the company routinely observes cloud hardware, network and operating system faults, and the software is expected to shield customers from all of them. That is the daily reality of a networking role there rather than an abstract claim. Location and working pattern: Bengaluru. Databricks says it is standing up new teams from scratch at this site, so expect an in office or hybrid arrangement, with the number of days not stated. Compliance note in the posting: the standard Databricks export controlled technology clause applies. Where such access is required, applying for a US government licence is at the employer's discretion and it may decline to proceed on that basis. Honest fit guidance: the 4 years of networking experience is what separates applications here, not the 8 years overall. Cloud networking at multi provider scale is a narrow skill and the people who have it are usually not looking, which is a reason to apply if you do. If your networking exposure is configuring a VPC occasionally, the requirement is deeper than that.
What the posting requires: - 8+ years of experience building distributed systems and/or foundational cloud services at scale, with an interest in working with Python, Go and Java. - A strong background building core components for high scale compute and data distributed systems. - Proven success in designing, writing, testing, debugging and performance tuning, with a strong grip on computer science fundamentals, and maintaining distributed or highly concurrent software in large, long lived codebases. - A track record of identifying problems and implementing solutions. - Eagerness to learn, with a strong technical background. - The ability to be a force multiplier in the software development process, enabling teams to deliver through leadership and technical contribution. Bonus points: - Experience with containerisation and orchestration platforms such as Kubernetes. - Experience with AI frameworks and tools. What the posting sets as position expectations: - Work closely with research, product management, product engineering, product design and other teams to define the first version and future evolution of the service. - Design, build and deliver well tested core pieces of the platform in collaboration with other stakeholders. - Contribute to shaping architecture, code reviews, development practices and developer experience as the teams and product grow. - Mentor fellow engineers and assume ownership and accountability of projects. What kind of role this is: defining the first version of a service means less existing structure and more influence over how it is built. That is attractive if you want architectural ownership and frustrating if you prefer a mature codebase with settled patterns. Location and working pattern: the posting states MongoDB is looking for candidates based in Gurugram for its hybrid working model. Honest fit guidance: eight years is a real bar here because the role is about judgement as much as output. The distinguishing experience is having maintained distributed systems in large, long lived codebases, which is different from having built greenfield services that never had to survive five years. If you have both, say so.
What the posting requires: - 8+ years of software engineering experience, described as being a master of fundamentals. This is the E4 level; Instawork also lists an E3 version of the same role at 6+ years. - Full stack versatility: able to move between frontend, backend and infrastructure and own features end to end. - Comfort designing user experience in React and diving into AWS to tune heavy video transcoding pipelines. - Ability to architect and scale cloud environments, including complex AWS infrastructure and ECS services. - Deep observability practice with precise telemetry across CPU, memory, network and disk IOPS. - Ability to design and optimise data pipelines at scale. - Strong engineering intuition and architectural expertise. The team leverages agentic coding models heavily and says it relies on human judgement to keep systems robust and built the right way. What the work actually looks like: - Own the technical execution for massive scale physical AI training data. - Lead technical development of the global data collection platform and the dedicated quality assurance platform, ensuring high throughput data enrichment, labelling and continuous quality assurance loops. - Architect and scale cloud environments, managing AWS infrastructure and ECS services for video transcoding. - Design and optimise data pipelines capable of operating at scale. - Act as a key engineering leader in the Bengaluru hub. What the business actually does, since it is unusual: Instawork Robotics Labs deploys skilled hourly workers into real commercial and residential environments to capture task data, which robotics labs then use to train foundation models. The posting frames closing that data gap as the defining infrastructure challenge of the physical AI era. Location and working pattern: Bengaluru. Office days are not stated. Honest fit guidance: the posting asks for a generalist and means it, so specialists who have worked in one layer will struggle against the breadth requirement. Video pipeline and transcoding experience is the part most candidates lack. If you are between 6 and 8 years, apply to the E3 posting instead of stretching for this one, since both are open.
What the posting requires as minimum qualifications: - A foundational understanding of AI and ML technologies, and experience leveraging, securing or positioning AI driven solutions to optimise outcomes within your functional domain. Zscaler lists this first. - 8+ years of support and networking experience as a subject matter expert specialising primarily in Zscaler Client Connector technologies. - Expertise in networking, cloud security and performance management, with the ability to quickly master new technologies. - Proven effectiveness at collaborating and building consensus across cross functional teams and organisations. - Experience developing new processes, tools or product features. What the work actually looks like: - Act as the deep subject matter expert on client connector technology for the wider support and engineering organisation. - Develop new processes, tools and product feature input rather than only resolving individual cases, which is what distinguishes a Center of Excellence seat from escalation work. - Collaborate across support, engineering and product to drive consistent outcomes. What Zscaler says about the environment: an AI forward enterprise built around the world's largest security data lake powering its cloud native Zero Trust Exchange platform. Culturally it emphasises impact over activity, constructive and honest debate, customer obsession, ownership and accountability, and a bias toward speed with quality. Location and working pattern: Bangalore or Mohali. Zscaler's support organisation roles in these locations are generally hybrid, though this particular posting does not spell the arrangement out, so confirm it. Honest fit guidance: the specialism is narrow and named. If you have spent years on Zscaler Client Connector or a directly comparable endpoint agent in a security platform, that specific depth is what is being bought and the 8 years is a fair reflection of it. If your background is general network support without that agent level depth, the requirement is more specific than it first appears. The process and tooling development part of the role is worth weighing positively: it is what makes this more than a support ladder step.
What the posting requires as minimum qualifications: - A foundational understanding of AI and ML technologies, and experience leveraging, securing or positioning AI driven solutions to optimise outcomes within your functional domain. - 8+ years of experience in customer facing technical roles such as professional services consulting. What the work actually looks like: - Serve as a dedicated technical advisor for strategic enterprise customers over extended engagements, described in the posting as six months, one year or longer. - Act as the customer's go to expert for all matters relating to their Zscaler environment. - Work embedded within the customer's organisation rather than rotating across many accounts. How this differs from Zscaler's other customer facing roles on this board: escalation engineers handle the hardest cases across many customers as they arrive, and Center of Excellence engineers build the tooling and processes behind them. A resident consultant is assigned to one customer for a long stretch. Same product depth, very different day to day rhythm and relationship. What Zscaler says about the environment: an AI forward enterprise, cloud native Zero Trust Exchange platform, with a culture it describes around impact over activity, honest debate, customer obsession and accountability. Location and working pattern: Mumbai. Resident consulting typically means significant time at the customer site, so clarify what the arrangement looks like for the specific account before accepting. Honest fit guidance: the deciding question is not technical, it is temperamental. If you like building a deep relationship with one customer's environment, knowing its history and its quirks, and being the person they call, this is unusually satisfying work. If you would find that confining, the escalation or Center of Excellence roles at the same company suit better and are also on this board. Eight years of genuinely customer facing technical work is the bar, so pure internal engineering experience will not map cleanly.
What the posting requires: - 8 to 10 or more years of experience in solutions architecture, technical consulting or enterprise SaaS implementations. What this kind of role typically involves at an enterprise SaaS company, based on how the posting frames it: - Owning the technical relationship with customers through implementation and adoption. - Designing how the platform integrates with the customer's existing systems and processes. - Translating business requirements into a technical configuration and integration approach. - Working alongside sales, customer success and product teams. ⚠️ The geography matters here. NAMER in the title means the accounts are North American while the role is based in Pune, so working hours are likely to be shifted to overlap with North American time zones. Confirm the expected shift pattern early in the process, because it is the single largest lifestyle factor in this role and the posting does not spell it out. About the employer: Mindtickle is a revenue enablement platform used by sales organisations for onboarding, training, coaching and readiness. Its engineering and delivery presence in India is in Pune, where it also lists other technical roles. Location and working pattern: Pune, Maharashtra. Office days are not stated in the posting. Honest fit guidance: this is a customer facing technical role, so the skills being bought are as much communication and structured thinking as they are technical depth. If you have implemented enterprise SaaS for large customers and can hold a room of stakeholders through a design decision, the 8 year bar is a fair reflection of the seniority. If you want to write product code, this is not that job. Because the posting is light on a detailed requirements list, ask for specifics on the tech stack, the size of accounts, and the split between pre-sales and post-sales work before investing in the process.
What the posting requires: - 10+ years of experience working on software and operating distributed systems, with deep Kubernetes expertise including designing or evolving multi cluster platforms. - Proficiency in Python, Go or a similar programming language. - Understanding of workload isolation at the systems level: containers, virtual machines, and the tradeoffs between them for running untrusted code. - A customer focused mindset. - Valuing efficiency in processes and operations, with a strong preference for automation over manual processes. What the posting sets as position expectations: - Own the reliability architecture of the platform across regions and cloud providers. - Collaborate with the teams building the platform, providing internal support and guidance on operability, capacity and best practices. - Set operational standards for the team: on call quality, incident response and service level objective discipline. - Mentor and technically develop the SRE team. - Participate in a 24 by 7 on call rotation to resolve issues involving platform infrastructure. ⚠️ The on call commitment is stated plainly as a 24 by 7 rotation. At staff level that usually means you are also the escalation point for others' incidents. Weigh it honestly against the seniority and scope on offer. The detail worth noticing: the requirement about running untrusted code tells you something about the platform. Isolation tradeoffs between containers and virtual machines only become a live question when you are executing code you did not write, which makes this a more interesting systems problem than standard service reliability work. Location and working pattern: the posting states MongoDB is looking for candidates based in Bengaluru for its hybrid working model. Honest fit guidance: ten years plus deep multi cluster Kubernetes is a high and specific bar. The distinguishing experience is having designed or evolved multi cluster platforms rather than operated a single one, and being able to talk about isolation tradeoffs concretely. If you have that, the scope here, reliability architecture across regions and clouds, is genuinely staff level rather than a retitled senior role.
What the posting requires: - 10+ years of overall industry experience, with 6+ years shipping and sustaining production C++ (C++11 and later, including 14, 17 and 20): multi threaded, memory conscious, cross platform code. - Solid distributed systems fundamentals: routing, failover, backpressure, graceful degradation, and the failure modes that come with them. - Deep experience building and sustaining endpoint, client or systems software. - Expertise with data structures, algorithms and performance profiling. - Fluency with agentic coding systems and genuine curiosity about agent harnesses. - A BSCS or equivalent is required, with MSCS or equivalent preferred. What the work actually looks like: - Build and harden the C++ client runtime at the core of the product: lightweight, multi threaded, cross platform, macOS first then Windows. - Architect the distributed systems that keep it fast and resilient at scale, engineering for fault tolerance so failures degrade gracefully rather than breaking a session. - Build a secure agentic harness for safe, high performance execution. - Own reliability, observability, security and performance of the runtime across real, varied hardware. - Set patterns and standards for the endpoint codebase. Why this is a harder problem than it sounds: an endpoint agent runs on hardware you do not control, alongside software you did not choose, and it cannot fail loudly without breaking someone's working day. The posting's emphasis on graceful degradation and varied real hardware is the honest description of that constraint. Levelling: the title spans Staff and Senior Staff, and Netskope's postings state that teams hire across levels with candidates individually assessed and levelled on skills and experience. Location and working pattern: Bengaluru. Netskope describes open desk office layouts, so expect an in office team. Office days are not stated. Honest fit guidance: the 6 years of production C++ is the filter, and it means shipped and sustained rather than studied. Modern C++ across macOS and Windows with real multi threading is a narrower skill than a general backend background, and people who have it are in demand. If that is you, this is one of the more technically serious roles on today's board.
What the posting requires as minimum: - 10+ years of engineering experience, with 5+ years of hands on experience building and operating data systems and pipelines, datasets and data warehouses, infrastructure, and leading small teams to deliver solutions. - A strong engineering background and a genuine interest in data. - Prior experience writing and debugging data pipelines using a distributed data framework such as Spark, Hadoop or Trino. - An inquisitive nature, diving into data inconsistencies to pinpoint issues and resolve deep rooted data problems. Stripe states that the preferred qualifications are a bonus rather than a requirement, and that if you meet the minimum requirements you are encouraged to apply. What the work actually looks like: - Lead the technical outcomes for a team of engineers working on high impact, cutting edge data problems. - Build and operate data pipelines at large scale using the modern data engineering toolchain: Airflow, Spark, Kafka and Flink are named in the posting. - Collaborate with other Stripe teams to understand their use cases and unlock new capabilities for them. - Build strong working relationships across the company, which the posting treats as a core requirement rather than a soft extra. What the emphasis on empathy tells you: for a staff role at this scale, most of the hard problems are cross team. The posting naming empathy and relationship building alongside Spark and Kafka is a signal about how the role is actually evaluated. Location and working pattern: Bengaluru, India. Office days are not stated in the posting. Honest fit guidance: ten years is a real bar and the 5 years of hands on data systems work is the substantive part. The phrase leading small teams appears in the minimum requirements, so this is a technical leadership role even though it is an individual contributor title. If your data engineering has been solo or within one team, the cross organisation scope is the stretch. If you have led data platform work that other teams depended on, that is exactly the story to tell.
What the posting requires: - 10+ years of overall software and integration engineering experience, with 8+ years focused on API and enterprise integration. - 4+ years in a senior, lead or architect capacity, owning API and integration designs, patterns and technical decisions. What the work actually looks like: API and integration architecture: - Own the API and integration architecture and strategy for assigned domains, defining API led patterns across experience, process and system APIs, plus reference architectures and standards. - Design, build and evolve RESTful APIs with clear contracts, documentation and service level agreements for internal and external consumers. - Lead integrations between SaaS and on premises applications including NetSuite, Workday, Salesforce, Snowflake and ServiceNow. - Define non functional requirements and SLAs for APIs and integrations covering availability, latency, throughput, error budgets, RTO and RPO. - Drive observability and reliability by standardising logging, tracing, metrics, dashboards and alerting, and creating operational runbooks for incident response and post incident reviews. AI and intelligent automation: - Identify and prioritise AI opportunities within API and integration flows such as data enrichment, anomaly detection, routing, summarisation, classification and intent extraction. - Define safe and governed AI usage: clear input and output contracts for AI services, guardrails through prompt design, validation and constraints, handling of sensitive personal, financial and HR data in prompts and responses, and monitoring for model performance and drift in production. Governance and delivery: - Partner with security, compliance and audit teams so integrations, APIs and AI services meet security, privacy and regulatory requirements including SOX sensitive data flows, access control, encryption and audit trails. - Lead technical discovery and solution design for new initiatives with product managers, application owners and business stakeholders. - Own vendor and platform technical relationships, anticipating deprecations and coordinating upgrades and migrations. - Oversee CI/CD practice including branching and release strategy, automated testing and environment configuration across development, QA, UAT and production. ⚠️ Applying to Rubrik: rubrik.com returns 403 to automated requests, so this listing was verified live through the Greenhouse jobs API rather than by fetching the page. It opens normally in a browser. Location and working pattern: Bangalore, India. Office days are not stated. Honest fit guidance: the AI governance section is the part that will separate applications, because plenty of engineers have integration depth and far fewer have put guardrails around AI in a SOX sensitive flow.
What the posting requires: - A Bachelor's or Master's degree in Computer Science, Engineering, Information Systems or a related field. - 10 to 15+ years in data engineering or platform architecture, with a shift toward high level technical leadership. - Strong experience designing and implementing modern data architectures and cloud data platforms. - Deep hands on expertise in full stack development including frontend and backend technologies, and DevOps infrastructure. - Experience with Snowflake, Tableau or similar technologies. - Expertise in AI and ML platforms, and the engineering required to support generative AI at scale. What the work involves, based on how the posting frames the role: architecture ownership across Rubrik's AI data platform, meaning the design of the data foundations and the platform engineering that generative AI capabilities are built on, rather than building individual features. The breadth requirement covering frontend, backend and DevOps suggests the architecture spans a full product surface rather than one layer. What kind of role this is: an architect title with an explicit expectation of high level technical leadership means influence, standards and direction setting, with hands on credibility as the entry ticket. If you want to be writing production code most days, an architect seat at this level is usually not that, and the posting is honest about the shift it expects. ⚠️ Applying to Rubrik: rubrik.com returns 403 to automated requests, so this listing was verified live through the Greenhouse jobs API rather than by fetching the page directly. It opens normally in a browser. About the employer: Rubrik builds data security and cyber resilience software for enterprises, protecting and recovering data across cloud, SaaS and on premises environments. Location and working pattern: Bengaluru, India. Office days are not stated in the posting. Honest fit guidance: the breadth is the thing to be honest with yourself about. Data platform architecture plus full stack plus DevOps plus generative AI at scale is a lot of surface, and few people are genuinely deep in all of it. Treat the data architecture and AI platform experience as the core, and the rest as areas where working knowledge and good judgement will do. If your background is purely data warehousing without the AI platform side, that is the gap the posting cares about most.
What the posting states: - Successful candidates for this position typically have 10 to 15 years of experience in a customer or partner facing technical role. The posting frames this as typical rather than an absolute cut off, which is worth knowing if you are close to the range. - A self starter, technically capable professional comfortable operating with autonomy. What this kind of role involves, based on how the posting frames it: enabling global system integrator partners in India to build practices around Datadog, which typically covers technical enablement of partner engineers, supporting partner led solution design, building reference material and demonstrations that partners can reuse, and acting as the technical bridge between the partner organisation and Datadog's own teams. Why the GSI focus changes the job: working through system integrators is different from selling to a customer directly. Your leverage comes from making other organisations capable rather than from personally delivering, so the skills that matter most are teaching, structuring reusable material, and building trust inside a partner's delivery practice. Prior experience working with or inside a system integrator is the most relevant background you can bring. About the product context: Datadog's platform covers infrastructure monitoring, application performance monitoring, log management and security monitoring, so technical credibility here means being able to hold a conversation about how an engineering organisation actually observes and debugs its systems. Location and working pattern: Bangalore, India. Office days are not stated in the posting. Honest fit guidance: at 10 to 15 years this is a senior seat, and the partner lens is the differentiator rather than the product knowledge, which can be learned. If your experience is solutions architecture for direct customers only, the partner motion, co-sell, practice building and enablement, is a genuinely different muscle and worth addressing directly in your application. Because the posting is light on a detailed responsibilities list, ask early about which partners you would cover and how success is measured, since partner roles vary widely on that.
What the posting requires: - 10+ years of successful experience in customer facing technical sales or consulting roles focused on enterprise database technologies and cloud. - A Bachelor's degree in Computer Science, Engineering, or equivalent experience. Core expertise, with deep technical proficiency required in: - Microsoft SQL Server: architecting and managing large scale high availability and disaster recovery solutions, including extensive experience with Always On Availability Groups, Failover Cluster Instances and log shipping. - Cloud databases: design and management of Azure SQL and Azure SQL Managed Instance. What this kind of role involves: acting as the deep database specialist in customer engagements, designing how enterprise SQL Server estates are protected and recovered, and advising customers on architecture decisions that carry real consequences if a recovery is ever needed. Rubrik's product is data security and cyber resilience, so the conversations are about backup, recovery, ransomware resilience and business continuity for databases that organisations cannot afford to lose. Why the specialism is worth noting: HADR architecture for SQL Server at enterprise scale is a genuinely narrow skill. Most database professionals administer, fewer architect availability groups and failover clusters, and fewer still can do that while sitting in front of a customer explaining the tradeoffs. If you are in that overlap, roles like this are where that combination is valued most. ⚠️ Applying to Rubrik: rubrik.com returns 403 to automated requests, so this listing was verified live through the Greenhouse jobs API rather than by fetching the page directly. It opens normally in a browser. Location and working pattern: Bengaluru, India. Office days are not stated in the posting. Honest fit guidance: read the customer facing technical sales or consulting phrasing carefully. This is a pre-sales and consulting seat, so commercial outcomes are part of how it is judged, and the technical depth is what earns the right to be in the room. If you are a SQL Server DBA who enjoys the customer facing side, this is a natural next step. If you want to stay purely hands on inside one estate, it is not.
What the posting requires: - 12+ years of production level experience in one of Python, Java, Scala, C++ or a similar language. - Experience developing large scale distributed systems from scratch. - Hands on experience developing and operating backend systems. - The ability to contribute effectively throughout all project phases, from initial design and development through implementation and ongoing operations. What the work actually looks like at this level, based on how Databricks describes its staff engineering: - Deliver highly scalable, available and fault tolerant systems processing very large data volumes across thousands of customers. - Low level systems debugging, performance measurement and optimisation on large production clusters. - Build architecture designs, influence the product roadmap, and take ownership of new projects. - Help prevent and investigate production issues. - Plan and lead complex technical projects spanning several teams within the company. - Break complex problems quickly into potential solutions, knowns and unknowns, and de risk them through prototyping and validation. The scale you would be working at, in the company's own terms: millions of virtual machines, terabytes of logs and exabytes of data processed daily, with hardware, network and operating system faults treated as expected conditions rather than emergencies. Location and working pattern: Bengaluru. Databricks says it is in the process of setting up new teams from scratch at this site, so expect an in office or hybrid arrangement. The number of days is not stated in the posting. Compliance note in the posting: the standard Databricks export controlled technology clause applies. Where access to export controlled technology or source code is required, applying for a US government licence is at the employer's discretion, and it may decline to proceed with an applicant on that basis alone. Honest fit guidance: twelve years is the real bar and it is the highest on this edition. What distinguishes an application at this level is not more of the same experience but evidence of having led complex, multi team technical projects and having made architectural calls that survived contact with production. If you are at eight to ten years, Databricks has several roles on this board at that level, and stretching for this one is unlikely to clear the filter.
Added July 26, 2026
What the posting requires: - 3 to 6 years in software or ML engineering, with at least one full cycle on premises or enterprise deployment delivered end to end. - Production grade experience with Python, Docker, Linux systems administration, REST APIs and CI/CD pipelines. - Hands on experience with LLM inference stacks such as vLLM, TGI or Ollama, plus RAG architectures and vector stores. - Experience deploying in constrained environments: air gapped networks, limited connectivity, non standard hardware or complex regulatory requirements. - Full stack debugging instinct, comfortable diagnosing across infrastructure, networking and application layers without a specialist to hand. - Demonstrated ability to ship and maintain a working system end to end where reliability was non negotiable. - Proven ability to navigate ambiguous client requirements and make the call without explicit guidance. Nice to have: - Prior experience with strategic or complex enterprise accounts. - MCP server experience or familiarity with agentic frameworks. - Open source projects, side products or entrepreneurial stints showing technical craft and sustained follow through. What the work actually looks like: - Own end to end deployment of Sarvam's full AI stack in client environments, including on premises, air gapped and classified infrastructure. - Serve as technical single point of contact for assigned accounts, from scoping and proof of concept to steady state operations. - Diagnose and resolve integration failures, model drift, inference issues and infrastructure breakdowns without escalation ladders. - Manage deployment pipelines, model serving and environment configuration in constrained settings. - Drive client side adoption through documentation, training and operational handover. - Own client satisfaction, time to value and uptime for your accounts, and flag risks before they become escalations. - Feed field learnings back into the product and the replicable deployment library. What they say about the person: the posting asks for someone who treats ambiguity as the baseline, owns outcomes rather than tasks, and operates in forward deployed environments without daily oversight. It also says plainly that you are expected to be available and responsive when your clients are, which is worth weighing. Location and working pattern: Delhi, embedded with client teams. No remote or hybrid arrangement is stated. Honest fit guidance: this is the most accessible role on today's board by years, but it is not an easy one. The deciding requirement is the full cycle deployment you have already delivered, not the year count. If your experience is building features inside one company's own environment, the constrained deployment requirement will be the gap. No interview process is published.
What the posting requires: - A PhD in Machine Learning, Computer Science or a closely related field, or in the final stages of completion. - 3+ years of research experience post PhD, or equivalent depth. The posting adds that exceptional early career candidates with a strong research record will be considered, so the years figure is not an absolute gate. - First author publications at top tier ML venues such as NeurIPS, ICML, ICLR, ACL, EMNLP or COLM. - Hands on experience pre training transformer based language models from scratch, ideally at 7B parameters or more. The posting says you should be able to describe a training run you owned end to end, including what went wrong and how you debugged it. - Meaningful contributions to the open source LLM ecosystem: research code, model releases, datasets or substantive contributions to widely used projects. - Fluency in PyTorch and comfort with distributed training. You should be able to read a training loop and immediately see where it might be slow, unstable or wrong. - Strong intuition for experimental design: knowing what to measure, what to ablate, and what scale a result needs to hold at before it can be trusted. Nice to have: - Work on novel architectures such as mixture of experts, state space models or hybrid architectures, or non trivial modifications to standard transformers. - Experience with multilingual or multimodal pre training. - Research contributions in post training: RLHF, RLVR, distillation or reasoning models. - A track record of taking a research idea from prototype to a shipped capability. What the work actually looks like: - Drive open ended research on architecture, optimisation, scaling behaviour, training stability and post training recipes for the next generation of foundational models. - Design and execute ablations at scales that genuinely inform large run decisions, including running pre training experiments end to end yourself. - Translate findings into concrete proposals for the next training run, and own those proposals through to production. - Work directly with the infrastructure and data teams, since many of the important research questions live at that boundary. - Read broadly, write internally, and publish externally when the work merits it. Why the role is framed as rare: the posting says you would be one of a small number of people in the world making architectural and training recipe decisions on a frontier scale model run, with the compute and autonomy to back it up. Location and working pattern: Bengaluru. No remote or hybrid arrangement is stated. Honest fit guidance: the 3 year figure is genuinely low for the seniority of the work because it is counted after a PhD. If you do not have a PhD and a first author publication record, this specific posting is not the one to spend an application on, whatever your industry experience.
What the posting requires as mandatory: - A B.Tech, M.Tech or PhD in Computer Science, Electrical Engineering, Statistics, Mathematics or a related field. - 5+ years of experience in data science, analytics or a closely related domain. - Strong foundation in probability, statistics and estimation theory. - Strong programming in Python, with solid fundamentals in object oriented programming, algorithms and data structures. - Deep familiarity with SQL, complex query writing, indexing and database internals, plus working knowledge of at least one NoSQL store. - Experience with data visualisation and analytical storytelling. - Excellent written and verbal communication. - Familiarity with AI powered tools for analytics and software development, including using them for exploratory data analysis, experiment analysis and documentation, and critically evaluating AI generated output for correctness, statistical validity and reproducibility. Preferred skills: - Exposure to cloud platforms and services such as AWS Kinesis, EKS and autoscaling systems. - Experience building lightweight web or service components with Flask or Django. What the work actually looks like: - Design, implement and maintain offline and online evaluation frameworks for AI and ML features. - Define, validate and evolve the KPIs, success metrics and audit methodologies used across teams. - Perform deep error analysis, bias analysis and segmentation to identify failure modes. - Own golden datasets, validation protocols and benchmarking standards. - Conduct large scale analytical studies on feature performance, data quality and system behaviour. - Design and review experiments including offline evaluations, controlled rollouts and A/B tests, ensuring statistical correctness. - Perform post deployment monitoring and regression detection. - Build tools, dashboards and automation to scale audits and reporting, and enable self serve analytics. - Mentor junior data scientists on statistical rigour, experiment design and analytical storytelling. Location and working pattern: Bangalore. This posting does not state the number of office days, though some other Netradyne listings specify a five day on site model, so ask. A note on the employer: Netradyne postings carry a recruitment fraud warning. Official communication comes only from netradyne.com or us-greenhouse-mail.io addresses, and the company never charges candidates a fee. Honest fit guidance: if you want to build models, this is explicitly not that role. It suits someone who is happier proving whether a system works than building it, and who can tell a product team its metric is wrong.
What the posting requires: - 5+ years on ML deployment, with 2+ years specifically on Intel inference stacks. - Production OpenVINO experience, including model conversion, accuracy validation after quantisation, and driver version pinning. - ONNX Runtime execution provider knowledge: when to use the OpenVINO EP versus native OpenVINO, and when to fall back to the CPU EP. - x86 CPU profiling and optimisation with VTune and perf, including comfort reading hot loops at the assembly level when needed. Noted as a strong plus rather than a requirement: - AVX-512 or AMX intrinsics. Bonus points: - Direct prior interaction with the OpenVINO team or Intel ecosystem partners. - Custom OpenVINO operator authoring. What the work actually looks like: - Land Sarvam's edge models on Intel NPU, discrete GPU and integrated GPU inside defined service level agreements. - Own the OpenVINO build and quantisation recipe for the team's models, including the driver version compatibility matrix. - Drive x86 CPU optimisation for the universal fallback path, covering AVX-512, AMX and threading strategy. - Own the Intel device CI pool and regression detection across OpenVINO upgrades. The hardware surface named in the posting: Intel NPU via OpenVINO on Meteor Lake, Lunar Lake and vPro AI PCs, Intel integrated and discrete GPU via OpenVINO and ONNX Runtime, and x86 and AMD64 CPU for fallback paths. Location and working pattern: Bengaluru. No remote or hybrid arrangement is stated. Honest fit guidance: the 2 years on Intel stacks specifically is the real filter, not the 5 years overall. General ML engineering or even CUDA and Nvidia deployment experience does not substitute, because the entire job is the Intel toolchain and its quirks. If you have that background it is a rare seat, since few teams in India run this surface at production scale.
What the posting requires: - 5 to 8 years of experience in security engineering, information security or a compliance focused role. What the work actually looks like, which is where this posting is unusually detailed: Compliance programme ownership: - Own and manage Hevo's compliance certifications end to end, including SOC 2 Type II, ISO 27001, GDPR and other applicable frameworks, across audit cycles, evidence collection and remediation. - Lead internal readiness assessments and gap analyses, and drive remediation roadmaps with Engineering and Infrastructure. - Act as primary point of contact for external auditors, certification bodies and customer security review teams. - Respond to customer security questionnaires, due diligence requests and vendor assessments. Security engineering and controls: - Design, implement and continuously improve security controls across cloud infrastructure, access management, data handling and the software development lifecycle. - Work with DevOps and Engineering to embed security and compliance requirements into CI/CD pipelines, infrastructure as code and deployment practice. - Conduct security risk assessments, vulnerability reviews and internal audits, prioritising findings and driving resolution to deadlines. - Define and enforce policies on data classification, access control, encryption, logging, monitoring and incident response. Policy and governance: - Develop and operationalise security policies, standards and procedures aligned to industry frameworks. - Build and run a compliance awareness and training programme across the company. - Establish continuous compliance monitoring using GRC tooling and automation. - Report compliance metrics, audit findings and risk posture to leadership on a regular cadence. Cross functional work: - Assess compliance implications of new features and infrastructure changes early with Product and Engineering. - Work with Legal and Finance on contractual obligations, data processing agreements and regional regulatory requirements. - Support Sales and Customer Success on enterprise security reviews for security sensitive deals. Location and working pattern: Bengaluru. Office days are not stated. Honest fit guidance: this sits deliberately at the intersection of security engineering and compliance, and the posting calls it high visibility. If you are a pure penetration tester or a pure GRC analyst, only half the role will fit. It suits someone who can both write the policy and change the pipeline that enforces it.
What the posting requires: - 5 to 8 years of experience in a quantitative analyst role, preferably in B2B SaaS, growth analytics or revenue operations. - Proficiency in SQL and experience working with large datasets. - Experience using Tableau, Looker or similar tools to build dashboards and report insights. - Strong communication skills, with the ability to present data to both technical and non technical audiences. - Ability to manage multiple projects simultaneously and drive deliverables with minimal oversight. - Attention to detail, a diagnostic approach to problems, a continuous learning mindset, and the ability to solve complex, open ended problems. Nice to have, listed as a bonus: - Experience with executive or revenue operations reporting. What the work actually looks like: - Query large datasets using SQL to extract and manipulate data. - Maintain and optimise databases on the data warehouse. - Prepare and present weekly business reviews, forecasts and key metric tracking. - Drive analytics projects on customer funnels and lead acquisition, uncover insights and report findings to leadership. - Collaborate with cross functional teams to execute weekly business reviews and track follow up actions. - Lead and manage end to end analytics projects with minimal oversight, and mentor junior team members. - Continuously challenge and improve metrics by aligning them with industry standards. About the company: Hevo is based in San Francisco and Bangalore, has raised $42 million from Sequoia India, Qualgro and Chiratae Ventures, and powers data analytics for more than 2,000 companies. Its stated mission is building technology from India for the world that is simple enough that anyone can unlock the potential of their data. Location and working pattern: Bengaluru. Office days are not stated. Honest fit guidance: this is analytics for the business, not pipeline engineering. If you want to build ETL, look at the data engineering roles on this board instead. If you are strong in SQL and can hold a room of executives through a weekly business review, the fit is direct. No interview process is published.
What the posting requires: - 5+ years of pre-sales experience with enterprise software, and technical aptitude. - 3+ years of software development experience. - Working knowledge and ability to code with one or more modern scripting languages such as Python, Node.js or SQL, or popular programming languages such as C, C++, Java or C#. - Working knowledge of UI development with demonstrable skills in semantic HTML, modern CSS and TypeScript, integrated with a framework such as Vue.js, React.js or Angular.js. - Demonstrated working knowledge of using AI agents such as Cursor, v0, Lovable or Windsurf to orchestrate UI designs and interfaces. - Proficiency deploying applications to the cloud with DevOps best practice, ideally AWS. - Experience with benchmarking, profiling and performance tuning of database systems. - Excellent presentation and communication skills. - A Bachelor's degree or equivalent work experience. Nice to have: - Experience selling databases or deploying applications with a major cloud provider. - Experience with database programming and data modelling. - Knowledge of modern technologies and their integration requirements, such as React.js, cloud storage, API management, Kafka and serverless. - A cloud provider certification or a MongoDB certification. What the work actually looks like: - Work with advisory consulting partners on reference architectures, patterns and technical blueprints for making the best use of MongoDB. - Articulate the business value of MongoDB solutions and bridge that to technical value. - Partner with account teams to support accounts from small startups to large enterprises. - Support sales through technical discovery, demos, proof of value, presentations, sizing and documentation of technical decision criteria, across several opportunities in parallel. - Act as a liaison, gathering field feedback and relaying it to Product Management. - Build and maintain relationships with technical partners, influencing their decisions and reinforcing how MongoDB adds value to their clients. - Drive partner Center of Excellence strategies and create demand for MongoDB solutions. - Mentor other pre-sales team members and share best practice. Location and working pattern: listed as India, without a specific city. Confirm the base location and any hybrid expectation with the recruiter. Honest fit guidance: the partner lens is the differentiator here, so experience working with or inside system integrators and consulting partners matters as much as the technical list. The coding and UI requirements are genuinely enforced by the posting, so this is not a slide deck role.
What the posting requires as mandatory: - A B.Tech, M.Tech or PhD in computer science, electrical engineering or a related area. - 6.5+ years of research or industry experience within computer vision and machine learning models. Note this is higher than the Senior in the title implies, and the body of the posting refers to the role as Staff Research Engineer. - In depth understanding of machine learning, both deep learning and classical ML, and of computer vision concepts. - Excellent programming skills: Python is required, C++ is desired. - Ability to take abstract product concepts and turn them into reality. - Ability to innovate on cutting edge problems without documented solutions. - Hands on experience handling edge deployments targeting various hardware platforms. Preferred skills: - Experience with time series data. - Experience with camera calibration, multi view geometry, 3D reconstruction and SLAM. - Experience with road scene understanding: objects, lanes, intersections, signs. - Experience successfully applying machine learning to a real world problem. - Experience conducting successful statistical experiments. What the work actually looks like: - Help design, implement and commercialise driver monitoring and driver assistance algorithms. - Work with very large datasets and deploy new algorithms and models into thousands of vehicles. - Design and commercialise algorithms characterising driving behaviour. - Design, implement and track key metrics, and architect data driven solutions. - Improve the machine learning infrastructure for scalable training and inference. - Innovate and develop proof of concept solutions showcasing novel capabilities. About the team: Netradyne describes its Analytics team as comprising graduates from IITs, IISc, Stanford, UIUC and UCSD. Location and working pattern: Bangalore. This posting does not state the number of office days, though some other Netradyne listings specify a five day on site model. A note on the employer: Netradyne postings carry a recruitment fraud warning. Official communication comes only from netradyne.com or us-greenhouse-mail.io addresses, and the company never charges candidates a fee. Honest fit guidance: treat this as a staff level computer vision role, because the posting body does. The edge deployment requirement is the part people underestimate: this is vision that has to run on a device in a truck, not in a notebook.
What the posting requires: - A B.E, B.Tech, M.E or M.Tech degree with a minimum of 6+ years of experience in software system optimisation. - Proficiency in C and C++, OpenGL, CUDA and Python. - A solid grasp of basic statistics, probability, and machine learning and computer vision concepts. - Experience with ML frameworks including Caffe, TensorRT, OpenCL, SNPE, OpenVINO and ONNX. - Exceptional attention to detail, strong analytical skills and a creative mindset directed at system performance. Described as a valuable asset rather than required: - Experience with embedded platforms, make files and build systems, and familiarity with Jenkins. What the work actually looks like: - Craft and develop tools, frameworks and reporting mechanisms for system optimisation. - Streamline software for deployment across IoT devices, implementing on GPU, CPU and DSP. - Enhance data platforms and optimise the machine learning models deployed on the platform. - Improve driver monitoring and driver assistance algorithms to boost system efficiency, and report the key performance indicators. - Manage production inquiries and ensure overall application stability in production environments. - Convey highly technical results to diverse audiences. Location and working pattern: Bangalore. Office days are not stated in this posting. A note on the employer: as with Netradyne's other listings, the posting carries a recruitment fraud warning. Official mail comes only from netradyne.com or us-greenhouse-mail.io addresses, and the company never asks candidates for fees or for sensitive data over unsecured channels. Honest fit guidance: this is the inference optimisation and embedded deployment end of ML, not model research. If your background is training models in Python and you have never profiled something on a DSP or converted a model through SNPE or TensorRT, the framework list is the honest gap. If you have done that work, it is one of the clearer matches on today's board.
What the posting requires: - 6+ years of experience, including producing high quality production code and detailed technical design documents for distributed systems. - Proven ability to break down complex, multi month projects into actionable milestones and tasks. - Solid grasp of industry best practice for distributed systems: monitoring, documentation, testing and finish quality. - Experience optimising cloud resource utilisation or developing large scale distributed tools. - Ability to make well reasoned trade offs between system performance, development velocity and technical debt. What the work actually looks like: - Lead projects from concept to deployment, designing and building scalable systems that handle high volume data streams for cost attribution and resource management. - Identify and eliminate inefficiencies in the cloud architecture, engineering solutions that mitigate resource waste and improve attribution accuracy. - Act as technical expert and owner for your service area across its full lifecycle, including code quality, monitoring and operational overhead. - Work with product and infrastructure teams to turn business needs into technical specifications, and build tooling that simplifies cloud economics for other engineers. - Contribute to code reviews, share engineering practice and mentor junior engineers. - Drive a shift left culture by integrating efficiency checks directly into the developer workflow. - Build automation and AI or agentic tooling that detects waste, attributes cost and remediates issues with minimal human intervention. The scale described: the team manages infrastructure efficiency across AWS, Azure and GCP for one of the world's largest data and AI platforms, with cloud spend in the hundreds of millions of dollars. Location and working pattern: Bengaluru. Databricks says it is still building out this site, so expect an in office or hybrid arrangement. The number of days is not stated. Compliance note in the posting: where a role requires access to export controlled technology or source code, Databricks says applying for a US government licence is at its discretion and it may decline to proceed on that basis. Honest fit guidance: cost and efficiency engineering is often dismissed as unglamorous, but at this scale it is a genuine distributed systems problem with a measurable outcome. If you have built large scale tooling and enjoy owning a service end to end, six years is a fair bar.
What the posting requires: - 6+ years of experience in data engineering, data platforms and analytics, or software engineering. - Comfort writing code in Python, Scala or JavaScript and TypeScript, and modern frameworks. - Working knowledge of two or more common cloud ecosystems (AWS, Azure, GCP), with expertise in at least one. - Deep experience with distributed computing using Apache Spark, including knowledge of Spark runtime internals. - Familiarity with CI/CD for production deployments. - Working knowledge of MLOps, ML and AI models, and AI APIs. - Experience designing and deploying performant production data architectures and applications combining data pipelines, ML and AI models, and user facing interfaces. - Experience with technical project delivery: managing scope, timelines and measurable outcomes. - Documentation and whiteboarding skills. - Experience working with enterprise clients and managing conflict across a broad stakeholder range. - Willingness to travel to customers about 20 percent of the time. - A Databricks certification. What the work actually looks like: - Lead customer technical projects, delivering production grade systems, reference architectures, custom applications, and data ingestion with ML and AI model integration. - Guide strategic customers through transformational big data projects, from end to end design through build and deployment. - Work with engagement managers to scope technical delivery with customer input. - Own architecture and design decisions, keeping solutions secure, scalable and aligned to both customer needs and Databricks best practice. - Embed with customer teams, engaging with stakeholders from individual contributors to executives. - Work with Databricks engineering and customer support to feed back product and implementation issues and drive rapid resolution. - Contribute accelerators, frameworks and best practices that scale across accounts and influence the product roadmap. Location and working pattern: Bengaluru, with roughly 20 percent travel to customers. Compliance note in the posting: the standard Databricks export controlled technology clause applies. Honest fit guidance: this is a hands on customer facing engineering role, not a solutions architect who only advises. The posting says it is for builders who thrive at the intersection of technology and business impact, and the billable framing is worth taking seriously: delivery to specification and to date is how the work is judged.
What the posting requires as minimum: - A Bachelor's or Master's degree in Computer Science, Information Systems, Engineering, or equivalent practical experience. - 6+ years of Salesforce development experience, including strong hands on expertise in Salesforce CPQ. - Strong understanding of Quote to Cash processes, sales workflows and Salesforce CPQ best practice. - Hands on experience with Apex, Lightning Web Components, Flows, SOQL, and REST and SOAP APIs. - Experience with product modelling, pricing rules, quoting workflows, approvals, amendments and renewals. - Experience integrating Salesforce with external systems such as ERP, billing, payment or other enterprise platforms. What the work actually looks like: - Design, build and support Salesforce CPQ solutions across product modelling, pricing, quoting, approvals, amendments and renewals. - Configure and enhance CPQ capabilities including product rules, price rules, bundles, product options, quote templates, discounting and approval workflows. - Partner with Sales Operations, Revenue Operations, Finance and Deal Desk to understand requirements and close process gaps. - Develop and maintain Salesforce solutions using Apex, Lightning Web Components, Flows, SOQL and platform APIs. - Build and support integrations between Salesforce CPQ and external enterprise systems. - Participate in technical design, story grooming, sprint planning, testing, code reviews, release management and production deployments. - Troubleshoot issues across CPQ configuration, pricing logic, automation, integrations and system performance. - Support documentation, user acceptance testing, regression testing and user enablement. - Ensure solutions align with security, data governance and Salesforce platform best practice. - Use AI powered engineering tools such as Cursor, Claude Code, Agentforce and GitHub Copilot to improve productivity, while applying sound judgement on security, accuracy and responsible use. Location and working pattern: the posting states MongoDB is looking for candidates based in Gurugram for its hybrid working model. Honest fit guidance: this is a specialist Salesforce CPQ role and the 6 years is specifically Salesforce development, not general software engineering. A backend engineer without CPQ experience would be applying against the core requirement. For an experienced Salesforce developer, working on the systems of a company like MongoDB rather than an agency is the draw.
What the posting requires: - 6+ years of software engineering experience, described as being a master of fundamentals. - Full stack versatility: able to move between frontend, backend and infrastructure and own features end to end. - Comfort designing user experience in React and diving into AWS to tune heavy video transcoding pipelines. - Ability to architect and scale cloud environments, including complex AWS infrastructure and ECS services. - Deep observability practice, with precise telemetry across CPU, memory, network and disk IOPS. - Ability to design and optimise data pipelines at scale. - Strong engineering intuition and architectural expertise, since the team leverages agentic coding models heavily and relies on human judgement for whether systems are built the right way. What the work actually looks like: - Own the technical execution for massive scale physical AI training data. - Lead technical development of Instawork Lens, the global data collection platform, and the dedicated QA platform, ensuring high throughput data enrichment, labelling and continuous quality assurance loops. - Architect and scale cloud environments, managing AWS infrastructure and ECS services for video transcoding. - Design and optimise data pipelines capable of operating at scale. - Act as a key engineering leader in the Bengaluru hub. What the business actually does, since it is unusual: Instawork Robotics Labs deploys skilled hourly workers into real commercial and residential environments to capture task data, which leading robotics labs then use to train their foundation models. The posting frames closing this data gap as the defining infrastructure challenge of the physical AI era. Location and working pattern: Bengaluru. Office days are not stated. Honest fit guidance: the posting asks for a generalist and means it, so specialists who have only worked in one layer will struggle against the breadth requirement. Video pipeline and transcoding experience is the part most candidates will lack. If you like owning infrastructure and product surface at once, and the physical AI data problem interests you, six years is a fair bar for the scope described.
What the posting requires: - 7 to 9 years of hands on experience in a DevOps, Site Reliability Engineering or Platform Engineering role. What the work actually looks like, grouped as the posting groups it: CI/CD and automation: - Design, build and maintain CI/CD pipelines supporting rapid, high quality delivery across multiple teams and environments. - Automate build, test, release and deployment workflows. - Own release management including versioning, tagging, rollback strategies and progressive delivery through canary and blue green deployments. - Integrate automated testing, code quality gates and security scanning into delivery pipelines. Cloud infrastructure and architecture: - Architect, provision and manage scalable cloud infrastructure across AWS, GCP or Azure using infrastructure as code tools such as Terraform, Pulumi or CloudFormation. - Design for high availability, fault tolerance and cost efficiency, and review and optimise cloud spend. - Manage multi environment setups across development, staging and production with environment parity. Containers and microservices: - Build and manage containerised workloads using Docker and Kubernetes on EKS, GKE, AKS or self managed clusters. - Define standards for container image builds, registry management, security scanning and image lifecycle. - Implement service mesh, ingress and networking within Kubernetes. - Drive adoption of Helm or Kustomize for repeatable deployments. Observability and reliability: - Build and maintain an observability stack covering metrics, logs and distributed tracing, using tools such as Prometheus, Grafana, Datadog, ELK or EFK, and Jaeger. - Define SLIs, SLOs and error budgets with engineering teams and lead SRE practice across the organisation. - Lead incident response including on call rotation and blameless post mortems. Security and compliance: - Embed security into infrastructure and pipelines: secrets management with Vault or AWS Secrets Manager, least privilege IAM, network segmentation and vulnerability scanning. Who you report to: the Director of IT and Information Security. Location and working pattern: Gurugram. Office days are not stated. Honest fit guidance: the breadth here is wide and genuinely staff level. An on call rotation is stated. ChargePoint notes it provides reasonable accommodations throughout the hiring process and gives an email address for such requests.
What the posting requires: - 7+ years of engineering experience, extensively with Django or Flask, React, and relational databases in a microservice based architecture. - A Bachelor's degree in Computer Science or Computer Engineering, stated as preferred. - Strong experience with AWS including Route53, CloudFront, API Gateway, Aurora RDS, DynamoDB, ElastiCache, EKS, ECS, S3, the AWS SDK, Lambda and SQS. - Proficiency writing unit and integration tests, with hands on experience across complete CI/CD tooling including Git, CI/CD tools and security scans. - Knowledge of Linux administration, comfortable with console commands, scripting and utilities such as Python and Bash. - Demonstrated experience building REST APIs and using OpenAPI or Swagger specifications. - Knowledge of Kafka or Flink. - Proven experience with agile development, CI/CD tools and project tracking tools, plus familiarity with gRPC, GraphQL and automation tools such as Ansible, Chef or Puppet. - Experience with third party integrations, and custom application development and deployment. - Proficiency across SQL and NoSQL stores including MySQL, Postgres, Redis, DynamoDB, ElasticSearch and MongoDB. - Experience with BI tools such as Tableau or Power BI. Desired rather than required: - Experience with large scale, technically complex accounts that constantly challenge product capabilities. - Demonstrated ability to communicate, present and influence at all levels of an organisation. What the work actually looks like: - Design, develop and maintain cloud native solutions and analytics dashboards for proactive monitoring and network hygiene. - Ensure appropriate documentation for all development and modification. - Ensure the integrity and security of institutional data. - Design data flow diagrams to define workflow, and data structure diagrams to refine database needs. - Translate software requirements into low level design, and evangelise clean architecture and clean code practice. - Perform code reviews, and help train, guide and lead others in building projects start to finish. Who you report to: the Director, NOC Delivery and Automation. Location and working pattern: Bengaluru, India. Office days are not stated. Honest fit guidance: the requirement list is long but the core is Python web services on AWS at senior level. Do not be put off by the breadth of named technologies, which reads more like a wish list than a checklist. The NOC context means the software has real operational consequences when a charger is down.
What the posting requires: - 8 to 12 years designing, building and troubleshooting distributed computing applications, with 4+ years delivering production scale Spark, ML or AI solutions in Python, Java or Scala. - 3 to 5 years in customer facing roles such as Technical Account Manager or Solutions Architect, with strong communication and relationship building. - Hands on expertise with data lakes, SQL based databases, and cloud data warehousing or ETL tools such as Snowflake, Redshift or BigQuery. - Deep knowledge of Spark core internals, Delta or Iceberg, JVM optimisation and memory management. - Proficiency in AI ecosystems including machine learning, deep learning and generative AI. - Practical experience with AWS, Azure or GCP, plus building and managing CI/CD pipelines, monitoring and alerting. - Proven ability to anticipate, identify and mitigate risk while planning solutions for production problems. - Proven ability to work with cross functional teams and senior leadership. What the work actually looks like: - Advanced troubleshooting and root cause analysis on performance and reliability issues across Spark, SQL, Delta, Streaming and Databricks runtime features, using Spark UI metrics, Mosaic AI Model Service, DAGs and event logs. - Work with R&D and network operations teams to define continuous monitoring that catches performance problems early in customer environments. - Build rapid proofs of concept, then test, deploy and monitor solutions. - Develop playbooks and maintain a knowledge base of common issues and solutions for Spark, ML and AI workflows. - Train customer engineering and business teams on performance tuning, debugging and platform features. - Advocate for customers in business review meetings as their trusted advisor and primary technical contact. - Work onsite with field engineering, sales and product teams during customer engagements and technical presentations. How this differs from the senior version of the same role, which is also on this board from an earlier edition: the staff posting raises the distributed computing requirement from 5 to 8 years up to 8 to 12, while keeping the same 3 to 5 years of customer facing experience. If you are between those bands, apply to the senior one. Location and working pattern: Bengaluru, with onsite collaboration during customer engagements. Compliance note in the posting: the standard Databricks export controlled technology clause applies. Honest fit guidance: both halves are required. Deep Spark internals without customer facing experience, or account skill without the ability to read an event log, will each fall short.
What the posting requires: - 8+ years of software engineering experience, with 4+ years focused on AI and ML systems in production. - A B.Tech, B.E. or M.S. in Computer Science, Machine Learning or a related field from what the posting describes as a top tier institution. - Deep expertise in Python, FastAPI, Django and modern backend frameworks for AI service development. - Hands on LLM engineering: LangChain, LangGraph, Amazon Bedrock or OpenAI APIs, prompt engineering and RAG architectures. - Strong Elasticsearch experience including vector search, hybrid search combining BM25 with dense embeddings, and semantic retrieval. - Proficiency with vector databases such as Qdrant, ChromaDB or Pinecone, and embedding based retrieval. - Experience building production LLM systems with a focus on low latency inference, caching strategies and observability. - Strong foundation in distributed systems design, microservices and event driven patterns with Kafka or RabbitMQ. - Experience with AWS or GCP, containerisation with Docker and Kubernetes, and CI/CD pipelines. - Strong knowledge of PostgreSQL including query optimisation and schema design, plus Redis, MongoDB and message queues. - A track record of optimising system performance with measurable improvements in latency or cost. - Experience with voice AI systems, telephony integrations such as Genesys or SIP, and speech processing pipelines. - Background in computer vision, image processing or visual transformer architectures. - Data engineering experience with Airflow, DBT and analytics platforms such as ClickHouse, Trino or Iceberg. - Experience with massive datasets, described as 50TB and above, and building scalable data pipelines. - Hands on experience with model fine tuning techniques such as LoRA or QLoRA. - Familiarity with RLHF style preference tuning and model alignment. - Experience with observability and monitoring stacks covering metrics, logging and tracing. - Certifications in generative AI, agentic AI or a related specialisation. What the work actually looks like: - Lead development of AI solutions across voice AI, computer vision and conversational AI. - Architect and build production grade AI systems that enhance the monitoring and analytics platform, improve customer support, and enable intelligent automation across the charging infrastructure. - Work with cross functional teams to design, build and deploy AI solutions affecting EV drivers and operators worldwide. Who you report to: the Director, NOC Delivery and Automation. Location and working pattern: Bengaluru, India. Honest fit guidance: this is a long requirement list even by staff standards, and the voice AI plus computer vision plus LLM combination is unusually broad. Treat the first block as the real bar and the rest as a preference list. If you have shipped production LLM retrieval systems and can talk about latency and cost numbers, apply.
What the posting requires as minimum qualifications: - A minimum of 8+ years of experience in technical support, with at least 5 years focused on DLP and CASB solutions and escalations. - A foundational understanding of AI and ML technologies, and experience leveraging, securing or positioning AI driven solutions within your domain. Zscaler describes itself as an AI forward enterprise and puts this first in its list. - Experience with data loss prevention, securing SaaS, and Cloud Access Security Brokers. - Practical working knowledge of AWS, Azure or GCP, paired with a strong understanding of Unix, Linux and Windows operating systems. - Deep understanding of data protection principles and practices. Preferred qualifications: - Experience deploying or supporting AI powered sensitive data discovery tools or automated data classification models to enhance DLP capabilities. - Experience with scripting and automation using Python or PowerShell. What the work actually looks like: - Serve as the primary point of contact for escalated DLP issues, providing advanced troubleshooting and resolution. - Take ownership of complex and critical cases through to effective resolution. - Perform detailed root cause analysis to identify underlying issues and implement long term solutions. - Work closely with product development, engineering and other cross functional teams to resolve issues and improve Zscaler DLP products and services. - Maintain clear and proactive communication with customers throughout the escalation, providing regular updates and managing expectations. Who you report to: the Senior Manager, Product Support, in the Support department. Location and working pattern: the posting states this is a hybrid role based in Bangalore. What they say about the person: the posting looks for someone comfortable in ambiguity, with an ownership mindset, a genuine growth mindset and an appetite for feedback. Zscaler frames its culture around impact over activity and constructive, honest debate. Honest fit guidance: the 5 years specifically on DLP and CASB is the real filter, not the 8 years overall. General network security support experience without DLP depth will not clear it. Unlike Zscaler's other escalation roles this one does not state a 24x7 on call rotation in the same terms, but escalation work in a TAC generally carries out of hours obligations, so confirm that before accepting.
What the posting requires: - 9+ years of experience across software engineering, network security and AWS security. Note that it is the combination that is being asked for, not nine years in any one of them. - A proven track record as an expert in the infrastructure security domain. What the work actually looks like: Leadership and strategy: - Develop and document comprehensive security policies, reference architectures, design patterns and the strategic roadmap for infrastructure security. - Keep abreast of current network and infrastructure security trends and best practice. - Collaborate with engineering, AWS and architecture teams so proposed designs meet both business objectives and stringent security requirements. - Partner with stakeholders across the organisation to stay current on infrastructure designs. Technical design and architecture: - Provide technical leadership to build security into all infrastructure and network designs across AWS cloud, SaaS applications and IT environments. - Design and re architect the AWS infrastructure to implement robust security measures, including network segmentation and secure access. - Build defence in depth, secure access and IAM from the ground up. - Address vulnerabilities and misconfigurations across operating systems, infrastructure and cloud. Operations and mentoring: - Work closely with security operations and incident response teams, providing technical leadership. - Mentor other junior infrastructure security professionals. Who you report to: the VP of Information Security. What the company does, for context: Observe.AI's platform lets businesses deploy specialised AI agents that autonomously handle customer conversations, support frontline teams and optimise operations, with each agent built for a specific role. Location and working pattern: Bengaluru. Office days are not stated. Honest fit guidance: the phrase to weigh is from scratch. This is a build the function role rather than a maintain the function role, which suits someone who wants architectural ownership and is comfortable without an existing playbook. If you want mature tooling and established process, this is the opposite of that. The AWS depth is not optional, since the infrastructure being secured is AWS.
What the posting requires: - 10+ years of experience working on enterprise data lakes and warehouses. - 5+ years of Spark and Python experience. - 5+ years of direct hands on experience with AWS or GCP. - Thorough AI knowledge, particularly with codegen tools and agentic frameworks. - Hive, Iceberg, Glue or other technologies that expose big data as tables. - Familiarity with big data file types such as Parquet, Avro and JSON. Nice to have: - Exposure to real time or streaming data technologies. What the work actually looks like: - Guide the data engineering team on building high performance ETL pipelines using Spark and other big data technologies. - Help design the architecture of the internal data platform to support a robust medallion architecture. - Provide thought leadership on achieving infrastructure cost savings on cloud hyperscalers. - Design and build AI agents that automate common development and support tasks the team performs. - Work with Security and Compliance teams so datasets carry appropriate permissions and regulatory controls. - Work with the Data Platform and Governance sibling teams to keep data scalable, consumable and discoverable. The ramp the employer publishes: - In 3 months: a thorough understanding of the architecture of MongoDB's internal data and AI ecosystem. - In 6 months: ownership of the delivery of a large project from scoping and design through to delivery. - In 12 months: having designed new features, led development work, and become a go to expert on parts of the system. Location and working pattern: the posting states MongoDB is looking for candidates based in Gurgaon for its hybrid working model. Honest fit guidance: at 10 years plus this is a technical leadership seat without being a management one, and the AI agent building brief is a genuine part of the job rather than a bolt on. If your data engineering experience is deep but you have not touched agentic frameworks or codegen tooling, that gap is stated explicitly in the requirements and is worth closing before applying.
What the posting requires: - 10+ years of overall industry experience, with 6+ years in backend, services and distributed systems in Go and/or Python, covering services, APIs and data pipelines you have built and operated in production. - Experience with telemetry, event or data pipelines and the storage and query systems behind them. - Expertise with Kubernetes and AWS for deploying, scaling and operating production services. - Understanding of REST, HTTPS and TLS, and designing and shipping secure APIs. - Fluency with agentic coding systems and genuine curiosity about agent harnesses such as Claude Code, Pi and Codex. The posting notes it is a bonus if you have instrumented one. - Expertise with data structures and algorithms, and strong communication skills. - A BS in Computer Science or equivalent is required, and an MS or equivalent is preferred. What the work actually looks like: - Build the configuration backend service that manages and delivers configuration to clients. - Build the telemetry pipeline: ingest usage events, run a multi category classifier, aggregate performance, security and quality patterns, and feed per user and executive dashboards. - Design and ship reliable, observable, secure services and APIs in Go and Python. - Partner with the ML team that consumes the data, the endpoint team that emits it, and partner organisations on the dashboard front end. What the posting says is in it for you, in its own framing: - You build the measurement engine, and the team's whole strategy of optimising where the data points runs on the pipeline you own. - The backend function is net new, so you set the patterns rather than inherit them. - Netskope's customer footprint gives production signal at a volume most teams never touch. Levelling: the posting says this team hires across all levels and that candidates are individually assessed and levelled by skill and experience, which is why the title spans Staff and Senior Staff. Location and working pattern: Bengaluru. Netskope describes open desk office layouts, so expect an in office team. The number of days is not stated. Application timing: the posting states the application window is expected to close within a set period, so do not sit on it. Honest fit guidance: the 6 years specifically in Go or Python backend and distributed systems is the substantive bar. Green field means less structure and more ambiguity than joining an established platform.
What the posting requires as minimum: - 10+ years of experience building software systems, including both user facing products and internal platforms. The preferred qualifications are described by Stripe as a bonus rather than a requirement, and it says explicitly that if you meet the minimum requirements you are encouraged to apply. What the work actually looks like: - Architect and build scalable, reliable systems underpinning Stripe's sales motion, including APIs and services for deal creation and modelling, multi party approval workflows, contract generation and merchant onboarding at global scale. - Lead the single plane of glass vision for sellers, driving architectural decisions on how first party Stripe components and third party platforms such as Salesforce interoperate, and designing systems that surface the right data and actions at the right time. - Integrate AI and agentic workflows into the selling process, from intelligent deal recommendations and pricing guidance to automated contract workflows and proactive activation nudges. - Partner at a senior level with go to market, finance, legal and product teams, translating business requirements into durable technical solutions. - Raise the technical bar through design and code reviews, and establish engineering standards and best practice. - Drive simplification and platform consolidation, reducing complexity in the go to market systems stack and architecting toward a maintainable, extensible platform. - Mentor and sponsor senior engineers, helping them grow in technical scope and organisational influence. How the team describes its own approach: it treats the selling process as an engineering problem from first principles, implemented as a hybrid architecture of first party custom Stripe components interoperating with third party standard business components. Location and working pattern: Bengaluru, India. Office days are not stated in the posting. Honest fit guidance: internal systems at Stripe still run at payments scale, so do not read internal as small. The specific thing that will distinguish an application is experience owning architecture across a boundary between custom systems and large third party platforms, because that hybrid is the core problem the team exists to solve. Ten years is a real bar here rather than a rounded up preference.
What the posting requires: - 12+ years of professional experience in backend systems or platform engineering. - Experience building platforms, infrastructure or database engineering, especially with MySQL and TiDB. - A track record of building and scaling mission critical platforms supporting high throughput global services. - Experience with schema migration frameworks, CI/CD automation and developer tooling. - A champion of developer experience, creating clear, reliable and user friendly workflows. What the work actually looks like: Schema migration platform: - Architect and maintain automated schema change infrastructure for MySQL and TiDB. - Implement versioning, rollback, validation and auditing for safe, predictable and fast migrations. Scale, reliability and test harness: - Ensure the platform operates across thousands of global databases with zero downtime. - Enhance resilience, observability and recovery. - Build a test harness for migration and deployment validation. Developer experience and CI/CD: - Design intuitive tools and APIs for schema and data change management. - Embed migration workflows into CI/CD pipelines to increase velocity and reduce friction. Schema and data management: - Design infrastructure for safe, large scale schema and data operations such as backfills and purging. - Ensure backfill operations are monitored, retryable, minimally disruptive and automated, maintaining data integrity. Why the role matters, in the employer's framing: the platform underpins Databricks' ability to keep evolving rapidly across thousands of databases and more than 60 mission critical services. Location and working pattern: Bengaluru. Office days are not stated. Compliance note in the posting: the standard Databricks export controlled technology clause applies, under which applying for a US government licence is at the employer's discretion where such access is required. Honest fit guidance: this is one of the most specific postings on today's board, which is good news if it matches you and bad news if it does not. MySQL and TiDB experience at scale is named directly, and schema migration tooling is a real specialism. Twelve years is the highest bar in today's edition alongside Samsara's platform role.
What the posting requires as minimum: - A Bachelor's degree in Computer Science or Engineering, or equivalent practical experience. - 12+ years of experience in software design, development and algorithm related solutions, including time in an architect or leadership role. - Stellar programming and coding fundamentals. - 4+ years of experience building large scale distributed systems. - 4+ years of experience leading cross organisation projects. - Expertise working with web services at massive scale deployed on cloud providers such as AWS, GCP or Azure. What an ideal candidate also has, per the posting: - 15+ years of relevant industry experience in software development. - Enjoyment of leading and mentoring other engineers. What the work actually looks like: - Drive technology choices, implement services and establish architectural patterns with broad and lasting impact on Samsara's platform. - Identify opportunities and initiate strategic conversations that influence the direction of platform technology and engineering culture. - Architect, design and develop software that enables Samsara to operate at scale. - Lead teams delivering products and capabilities that contribute to Samsara's products and revenue. - Solve the hardest technical problems and enable products to reach market quickly with high quality. - Keep a platform first approach while collaborating with infrastructure and product teams. The systems in scope, as named: reporting, automations and enterprise capabilities, plus foundational infrastructure including container orchestration, data storage, real time data ingestion and GraphQL execution. Location and working pattern: this one is stated clearly, which is unusual and useful. The role is hybrid at 3 days per week in the office, at Prestige Tech Park, Kadubeesanahalli, Bengaluru 560103. What Samsara says about the environment: engineers have a rare closeness to the end user, with the opportunity to join customer interviews, work with customer success and product managers, and use metrics to check the work is producing better customer outcomes. Honest fit guidance: 12 years with an architect or leadership component is the real bar, and the ideal candidate note pushes it toward 15. This is a technical leadership seat, so the cross organisation project experience matters as much as the coding depth.
What the posting asks for. GitLab publishes no years of experience figure, so judge yourself against the skills: - Strong software development skills with experience in Ruby on Rails. This is stated as required. - Experience working on distributed applications with large codebases deployed in cloud environments, described as strongly preferred. - A passion and desire to proactively develop security engineering skills. Note that formal security engineering experience is explicitly not a hard requirement for this role. - Comfort working in an all remote environment where results and impact matter above hours worked. - Strong experience with cloud native development on Google Cloud Platform and/or AWS. - Interest in thinking like a hacker and defending against attacks with an automation first mindset. - Interest in handling trust and safety security incidents and collaborating with engineering to harden platform defences. - Experience working on an AI native development team maintaining teams of agents, acting as a code reviewer, and abstracting your role away from writing code in most cases. What the work actually looks like: - Maintain core abuse prevention systems and build new abuse detection rules for evolving platform abuse including spam, AI and token abuse, SEO optimisation and redirects, and other financially motivated campaigns. - Become a core maintainer of the in house abuse platform, a Ruby on Rails monolith, supporting and building new features for it. - Improve and expand agentic AI capabilities in the abuse mitigation tools, including improving multi agent reasoning decision patterns with a target of reducing human in the loop operational load. - Lead collaboration with peer engineering teams to deliver safety improvements to the GitLab product. - Resolve automation gaps and create efficient automated processes. - Create and maintain documentation such as runbooks and procedures. About the team: Trust and Safety is a global team that keeps abusive behaviour off GitLab.com using automation, LLM aided anomaly detection and user behaviour analysis. It works closely with Security Incident Response, Signals Engineering, Threat Intelligence and the Red Team. Location and working pattern: GitLab states that all of its roles are remote, with some carrying location based eligibility requirements its talent acquisition team can clarify. This listing includes India. One more thing worth knowing: GitLab treats AI as a core productivity multiplier and expects team members to use it in daily workflows. Honest fit guidance: this is the clearest route on today's board from software engineering into security engineering, because the posting says so itself. Rails is the non negotiable part.
What the posting asks for. As with GitLab's other listings, no years of experience figure is published: - Strong experience building backend applications with Ruby on Rails in a high scale production environment. - Professional experience with Go for backend or infrastructure oriented services. - A track record of leading architecture across multiple systems and influencing technical direction through strong engineering judgement. - Experience writing clear technical proposals, requests for comments and decision records in an asynchronous, documentation first environment. - A solid security mindset, and comfort working on products where trust, risk reduction and secure defaults are central requirements. - Familiarity with software supply chain security concepts such as build provenance, artifact signing, dependency security or software bills of materials. - Strong teamwork and communication skills across distributed teams and functions. What the work actually looks like: - Define and drive the technical architecture for the supply chain security add on, covering package policy enforcement, provenance generation, artifact signing and malicious package detection. - Lead design and implementation for Supply-chain Levels for Software Artifacts Level 2 and Level 3 capabilities within GitLab CI/CD. - Architect integrations with Sigstore services including Cosign, Fulcio and Rekor, covering signing workflows, verification and trust boundaries. - Design backend services and request paths supporting allow, deny and quarantine package policies with strong performance and reliability expectations. - Review merge requests with a focus on security, architectural consistency, maintainability and test quality. - Mentor backend engineers across experience levels, including participating in hiring. - Partner with Product, Infrastructure, Authentication, Authorization and Security counterparts on cross team decisions. - Contribute to open source and industry conversations, including working groups on software supply chain security. Example projects named: a Dependency Firewall for package policy enforcement across supported registries, and artifact attestation and signing using supply chain security standards and the Sigstore ecosystem. Location and working pattern: GitLab states all of its roles are remote, with some carrying location based eligibility requirements. This listing includes India, and the posting describes the environment as remote, asynchronous and values driven, where written communication and ownership are central. Honest fit guidance: this is a genuine architecture role, so the distinguishing requirement is having defined systems before they were built and written the proposals that got others to agree. Rails at high scale plus real Go experience is the technical floor, and supply chain security familiarity is what will separate applications.
What the posting asks for. GitLab publishes no years of experience figure: - Experience owning product or platform systems end to end across multiple engineering and product teams at the staff level. - Strong fullstack technical skills with proficiency in Go, Ruby and Node. - Depth in at least one of: reporting and metrics platforms, graph data systems, or data access and warehouse integrations including Snowflake, Databricks or BigQuery. - Hands on experience building production data ingestion, systems integrations or data access capabilities. - Experience operating multi tenant systems across both SaaS and self managed environments. - Strong judgement in ambiguity, with the ability to make trade offs, create clarity and move early stage work forward. - Clear written communication, including architecture proposals and design records that help distributed teams progress asynchronously. - A practical and proactive approach to collaboration. The posting welcomes transferable experience from adjacent platform, data or product engineering backgrounds. What the work actually looks like: - Architect how GitLab and third party data is ingested, modelled and synchronised into the Knowledge Graph as a near real time graph of the development ecosystem. - Coordinate integration with external systems such as Jira, observability tools, Zendesk and ServiceNow to add business context. - Design the Data Marketplace so customers can consume GitLab data through Snowflake, Databricks and BigQuery without engineering handoffs. - Publish GitLab observability data as OpenTelemetry and support the APIs used for data access. - Define operational readiness for the systems your team ships across GitLab.com, Dedicated and Self Managed deployments. - Translate ambiguous product problems into practical technical plans and iterative roadmaps with Product, Design and the graph backend team. - Resolve cross team coordination with Graph Backend, AI Platform and Infrastructure. - Mentor senior and intermediate engineers through design reviews, pairing and code review. About the team: Data Products covers Software Engineering Intelligence, dashboard and reporting frameworks, external data access and output, and data ingestion across areas such as DORA metrics, value stream reporting, AI impact, software delivery trends, and security and quality metrics. Location and working pattern: all GitLab roles are remote, with some carrying location based eligibility requirements. This listing includes India. Honest fit guidance: the 0 to 1 framing is the main thing to weigh. If you want a defined roadmap this is the wrong role, and if you want to make the early calls it is unusually attractive. The multi tenant across SaaS and self managed requirement is the technical detail most candidates underestimate.
What the posting lists as must haves. GitLab publishes no years of experience figure, though it does specify senior level: - India based and authorised to work in India, specifically Bangalore, Mumbai or Delhi. - Senior level technical pre-sales, solutions architect or sales engineering experience, able to guide stakeholders through solution design and evaluation. - Proficiency across the end to end software development lifecycle, modern DevSecOps practices and CI/CD workflows, with hands on experience with GitLab or a comparable source control, CI/CD or DevSecOps platform, and the ability to map platform capabilities to customer use cases. - Demonstrated experience working with or in leadership roles inside India based global system integrators, either partner facing or on the delivery and practice side. The posting itself calls this the line that makes it a GSI hire rather than a generic solutions architect one. - Channel, cloud and partner ecosystem fluency: understanding partner sourced motion, deal registration, co-sell and services led go to market, rather than a direct sales only background. - Ability to communicate credibly from practitioner to executive, and to own a technical activation plan as the directly responsible individual. - Willingness to use AI as a core productivity multiplier in daily workflow. Nice to haves: - An existing network inside one or more of the named global system integrators. - Experience standing up partner delivery practices, enablement tracks or certification programmes. - Cloud marketplace or hyperscaler co-sell familiarity with AWS or GCP. - Depth in GitLab, AI development, Kubernetes, infrastructure as code, or application security including SAST and DAST. - Coverage value beyond India, such as APAC GSI delivery hubs. What the work actually looks like: - Work with Ecosystem Sales Managers and partner sales leaders on partner activation plans that drive partner sourced pipeline and GitLab adoption. - Own the technical side of partner activation, building and delivering demos, reference architectures and workshops. - Serve as the directly responsible individual on partner technical activation plans, identifying and addressing technical risks and gaps. - Build relationships with technical and business stakeholders at partners so they move from awareness to leading deal registrations and solution development. - Act as partner advocate internally, sharing field feedback with Product, Engineering, Sales, Marketing and Partner Enablement. Location and working pattern: remote, with the posting requiring you to be India based in Bangalore, Mumbai or Delhi. Honest fit guidance: the GSI requirement is the gate. Strong solutions architecture experience without system integrator exposure will not clear it, because the posting says so directly. If you have worked inside an Indian GSI practice and can hold a technical room, this is a rare remote fit.
What the posting requires. Twilio publishes no years of experience figure here, so measure yourself against the skills: - A Bachelor's or Master's degree in Computer Science, Engineering or a related field. - Hands on experience with high scale messaging and streaming systems and processing engines, at several thousand events per second. - Excellent high level service design skills: modelling interfaces and internals in a properly modular, composable and extensible way. - Expert programming experience in Go or a similar object oriented language. - Demonstrated experience identifying, prototyping and deploying GenAI or LLM solutions to solve real world engineering or data processing challenges. - Technical depth in distributed systems, high scale ingestion and cloud native architecture. - Excellent communication, problem solving and operational excellence skills. Desired rather than required: - Proficiency with datastores, distributed caching and container technologies such as Docker and Kubernetes. - Experience with modern CI/CD pipelines and observability tools such as Datadog, Grafana and Prometheus. - Familiarity with AI and ML technologies. - Experience managing and operating AWS infrastructure. - Experience working in a geographically distributed team. What the work actually looks like: - Own and deliver robust, high scale routing experiences for the Twilio Segment data platform and pipelines team. - Architect and operate always available, complex distributed systems in cloud environments. - Guide technical decisions, articulating trade offs between cost, performance and reliability. - Translate complex technical strategies into actionable plans for stakeholders including product managers and architects. ⚠️ Location, and this one has a real restriction: the role is remote but based in India **only in Karnataka, Tamil Nadu, Maharashtra, Telangana and Delhi**. If you live outside those five states you are not eligible, which is unusual and easy to miss. The posting also says you may be required to travel occasionally for project or team meetings. Benefits stated in the posting: competitive pay, generous time off, parental and wellness leave, healthcare and a retirement savings programme, varying by location. Honest fit guidance: Twilio says it values non traditional career paths and encourages anyone meeting the required qualifications to apply. That said, Principal at Twilio is a senior individual contributor level and the scale described, several hundred thousand data points per second, is the real context. The posting also notes Twilio uses AI in its hiring process, with every hiring decision made by a person.
Added July 25, 2026
What the posting requires: - 2 to 4 years of relevant professional experience. The overview line says 2+ years, and the requirements line says 2 to 4, so treat the low end as the real entry point. - Proven success in a fast paced production support environment. - Strong scripting knowledge in Python, Perl or shell. This is stated as required, not preferred. - Good MySQL exposure, including the ability to write and understand complex SQL joins. - Experience in any programming language. C++, Java or Ruby on Rails are called out as a strong plus. - Familiarity with on call tracking systems and production monitoring solutions. - Demonstrated written and verbal communication skill, with a track record of responding to and resolving customer issues in writing. - Strong analytical and problem solving skills, and the ability to work across functional teams. What the work actually looks like day to day: - Diagnose, troubleshoot and fix production software issues. - Build and own monitoring for both production and non production environments and applications. - Develop smaller complexity features and enhancements inside existing stable components. - Adapt installers, shell scripts and Perl scripts to automate manual tasks. - Keep an ongoing record of problem analysis and resolution in an on call tracking system. - Pass user feedback to engineering and product teams. Location and working pattern: Pune. This is a full time PhonePe role, and the posting notes that the listed employee benefits apply to full time employees only, not interns or contractors. Benefits stated in the posting: medical, critical illness, accidental and life insurance, an employee assistance programme with an onsite medical centre, maternity and paternity benefits, adoption and day care support, relocation and transfer support, PF, gratuity, NPS and leave encashment, plus higher education assistance and a car lease scheme. Honest fit guidance: apply if you have spent two or more years close to production systems and enjoy on call, root cause work and automation. The role explicitly sits between technical operations and business requirements, so if you want to build product features full time this is not it. No interview process is published in the posting.
What the posting requires: - A Masters or PhD in Computer Science, Mathematics, Statistics or a related field. This is listed as a qualification, not a preference. - At least two years of demonstrated ML or AI research experience, either in a professional setting or at a reputable academic institution. Academic research counts here, which is unusual and worth noting. - Software engineering experience in Python and C++. - Experience with TensorFlow, Keras or PyTorch is described as highly desirable. - A track record of academic publications is preferred, not required. What the work actually looks like: - Lead research applying machine learning across a wide variety of datasets and trading problems. - Track academic research and bring techniques from other fields into trading problems. - Improve tick by tick order book time series feature sets using current preprocessing methods. - Build and extend deep learning models against a large in house feature pool and compute cluster. - Build a scalable pipeline for producing predictive models across global markets. - Discover new sources of predictive signal, verify they improve existing models, and integrate them into the firm's strategy pipeline. - Work with quant researchers and software developers to move research into production in Python and C++. - Advise the infrastructure team on hardware and software choices for ML research. Location and working pattern: Gurugram. The posting describes cubicle free offices and a non hierarchical culture, which implies an in office team, though it does not state a fixed number of office days. Benefits stated in the posting: competitive compensation, an annual international team outing, fully covered commuting expenses, health insurance, catered breakfast and lunch, gym and sports club memberships, and four weeks of annual leave in addition to market holidays. Honest fit guidance: this is a research seat at a proprietary trading firm, so the work is model quality and signal discovery rather than product engineering. If you have a strong research record and two years of serious ML work, the low year count will not hold you back here. If you do not have a Masters or PhD, this specific posting is not the one to spend an application on. No interview process is published.
What the posting requires: - 3+ years with Apex, Lightning Web Components, SOQL and JavaScript, working in Agile practices. - Advanced flow development. - API integrations across ETL, marketing tools, ERP and analytics. - Data architecture support, performance optimisation and technical debt reduction. - Deployment and CI/CD support, plus security and scalability improvements. - Technical design collaboration with a System Architect, and the ability to break technical requirements into independent features. - Comprehensive debugging and troubleshooting experience in Salesforce, including spotting the common blind spots and bugs. - Experience working with and optimising millions of rows of data. - Proficiency writing unit tests with assertions for core functionality. Nice to have, listed as desired: - AgentForce, Einstein and other AI tools. - SQL, Python, Data Cloud and Snowflake. - Familiarity with a pay as you go business model. - Developing and deploying through Heroku. What the work actually looks like: - Evolve a Salesforce data model that is scalable, reportable and intuitive for end users. - Build custom functionality with SOQL APIs, Apex controllers, Apex web services and Apex callouts. - Run technical analysis, document integration requirements, and work with architects and stakeholders on integration design. - Review and assure quality on all code entering the codebase. Location and working pattern: remote, based in India. The posting states the role may require occasional travel for in person project or team meetings. Twilio describes itself as remote first. Benefits stated in the posting: competitive pay, generous time off, parental and wellness leave, healthcare and a retirement savings programme, with offerings varying by location. Honest fit guidance: Twilio says openly that it values non traditional career paths and encourages people who meet the required qualifications to apply. The required list is Salesforce heavy, so this is a strong fit for a Salesforce developer with three years in and a weak fit for a general backend engineer. The posting also notes Twilio uses AI in its hiring process, with hiring decisions made by people. No interview stages are published.
What the posting requires: - 3+ years of experience in Chromium environments. This is the stated requirement despite the Sr. Staff title. - Strong C++ design and software implementation skills. - Excellent debugging, memory profiling and performance testing skills. - Experience programming multi threaded solutions, with knowledge of synchronisation techniques. - Good understanding of memory management and runtime optimisation. - Experience developing complex products with many components. - The ability to coach and mentor, and to support the growth of team members. - Strong verbal and written communication. - BSCS or equivalent required. MSCS or equivalent strongly preferred. Nice to have: - Unit testing knowledge, with the posting noting that being a proponent of test driven development is a big plus. What the work actually looks like: - Modify and enhance the Chromium engine to support new Netskope Enterprise Browser features. - Apply advanced data structures and algorithms in C++. - Research optimisation algorithms and improve browser performance. - Work on distributed systems problems around scalability, high availability, containerisation and analytics, using technologies including gRPC. Levelling, which matters here: the posting says this team is hiring across all levels and that candidates are individually assessed and levelled by skill and experience. So the Sr. Staff in the title describes the top of the range, not the entry bar. Location and working pattern: Bengaluru. Netskope describes open desk office layouts and large meeting spaces, so expect an in office team. The number of office days is not stated. Application timing: the posting states the application window is expected to close within 50 days of listing, so this one has a real deadline attached. Honest fit guidance: browser and Chromium work is a narrow specialism. If you have three years inside Chromium or a comparable large C++ codebase, do not be put off by the Sr. Staff title. If your C++ is not current, the rest of the list will not carry you.
What the posting requires as mandatory: - 3 to 5 years of experience, stated as the range for the role. - Linux or Android, with multimedia experience: camera work and GStreamer video or audio pipelines, or equivalent exposure to another streaming framework. - Ability to develop software in C and C++. - Hands on experience designing and implementing software modules on embedded systems. - Good spoken and written communication, and the ability to adapt quickly in a fast moving environment. Preferred skills: - Prior experience with embedded products and Linux OS concepts. - Linux device drivers and RTOS experience. - GPU work with CUDA, OpenCL or SNPE, and algorithm optimisation. - Use of AI tools in day to day work. What the work actually looks like: - Design and implement multimedia based applications. - Develop the test environments and test cases that validate the features you build. - Troubleshoot and debug complex issues in production environments. - Implement software development best practices across the team. Location and working pattern: the posting states the position is based at HM Tech Park, Whitefield, Bangalore. Some other Netradyne listings state an on site five day model explicitly. This one names the office but does not state the number of days, so confirm it with the recruiter rather than assuming either way. A note on the employer: Netradyne includes a recruitment fraud warning in its postings. Official communication comes only from addresses ending in netradyne.com or us-greenhouse-mail.io, and the company says it never asks for sensitive personal data over text or unsecured channels and never charges candidates a fee. Worth knowing before you reply to anyone claiming to recruit for them. Honest fit guidance: this is device side embedded work, close to the hardware, on a real shipping product. If your background is application or backend development, the multimedia pipeline requirement will be the gap. No interview process is published.
What the posting requires: - A Bachelor's or Master's degree in Computer Science or Electronics. - 3 to 6 years of experience in system software development on Linux. - Strong C and C++ programming skills. - Solid understanding of Linux internals: process and thread model, scheduling, memory management and IPC. - Experience with IPC mechanisms including message queues, shared memory, semaphores and DBus. - Familiarity with systemd, udev, init scripts and service management on Linux. - Proficiency in multithreading and synchronisation concepts. - Experience with build systems such as CMake, Make or Yocto. Preferred and bonus skills: - Embedded Linux, socket programming, video streaming and Bluetooth programming. - Hands on use of GDB, Valgrind, strace and perf. - Scripting in Bash or Python. - Exposure to security frameworks and hardening for Linux based systems. - Familiarity with Docker and Kubernetes. - Contributions to open source Linux projects. What the work actually looks like: - Design and implement middleware components and services on Linux based platforms. - Develop and optimise IPC mechanisms. - Work on system daemons, service orchestration and resource management modules. - Collaborate with hardware, firmware and application layer teams. - Perform code reviews, unit testing, integration testing and performance tuning. - Debug and resolve system issues across middleware and lower layers. - Contribute to system architecture and design discussions. Location and working pattern: Bangalore. This posting does not state the number of office days, unlike some other Netradyne listings which specify a five day on site model, so ask. A note on the employer: as with Netradyne's other listings, the posting carries a recruitment fraud warning. Official mail comes only from netradyne.com or us-greenhouse-mail.io addresses, and the company never charges candidates a fee. Honest fit guidance: this is a genuine systems role. If you have written daemons, debugged IPC and worked in a Yocto build, three years is enough to be taken seriously here. Application developers who have not worked below the framework layer will struggle against the required list. No interview process is published.
What the posting requires: - Excellent written and spoken English. The posting calls this non negotiable, because you present architecture to customer CTOs, write documents that hold up in audit, and defend decisions in the room. - Production agentic AI systems you have actually shipped on AWS. The posting calls this the primary qualification and says to be ready to walk through what you shipped, the decisions you made and what broke. Proof of concepts and notebooks are explicitly not enough. - Deep understanding of agentic architecture, including single agent versus multi agent systems, supervisor and orchestrator patterns, hierarchical topologies and planner and executor separation. - Orchestration experience with LangGraph, Strands Agents, CrewAI or equivalent. - Memory design: short term working memory and long term episodic and semantic stores, with vector and graph backed retrieval, and the production trade offs of each. - Reflection and self correction patterns: critique loops, self evaluation, retry with feedback, and evaluation harnesses that catch failures before customers do. - Tool use and function calling: schema design, tool selection reliability, error handling and agent to agent composition. - RAG and retrieval pipelines: chunking, embedding, hybrid retrieval, reranking and grounding in customer data. - Strong AWS production experience with Amazon Bedrock and AWS AI services, plus core services such as Lambda, API Gateway, DynamoDB, RDS or Aurora, Glue, EMR, Redshift and Kinesis. - Solid software engineering fundamentals in Python and TypeScript, with CI/CD, infrastructure as code and test driven discipline. - Roughly 3 to 10 years in engineering roles, with agentic AI or GenAI as your current day job. Nice to have: - Experience with data or application modernisation such as database migration, legacy refactoring or data platform builds. - Delivery experience in financial services, healthcare and life sciences, internet and software, manufacturing, or telco, media, entertainment, gaming and sports. - Model tuning and fine tuning. What the work actually looks like: - Deliver production agentic AI systems and AWS modernisation engagements on committed dates. - Convert existing products and business processes into agents, exposing functionality as callable tools or replacing form and click interfaces with intent driven ones. - Embed with customer engineering teams, run architecture sessions and align stakeholders from VP Engineering to CTO. - Make agent decisions traceable and defensible so outputs survive internal audit and regulators, including HIPAA, PCI DSS and finance grade governance where the vertical demands it. Location and working pattern: Mumbai, with the forward deployed model meaning you embed with customer teams. Honest fit guidance: the deciding factor is whether you have shipped agentic systems into production, not how many years you have. The posting says so explicitly. If your agentic AI experience is demos, this application will not clear the first filter.
What the posting requires: - 3+ years working on ML systems. - Solid PyTorch and ONNX export experience, including the awkward parts: dynamic shapes, control flow and custom ops. The posting names these specifically. - Quantisation in production on at least one real model. - Comfort with at least two of ONNX Runtime, TensorRT, CoreML, OpenVINO, QNN and LiteRT. - Profiling fluency on at least one platform. Nice to have: - Custom op authoring in any runtime. What the work actually looks like: - Own one or two model and chipset pairs end to end, taking each from research handoff to a production ready artifact. - Quantise, validate accuracy, benchmark and document. - Author the deployment workbook for each pair you own. - Embed part time with the consuming app team during integration, debugging performance and accuracy issues with them. - Maintain and extend the team's benchmark harness. Target hardware named in the posting: Intel xPU, ARM xPU, Apple xPU, and Nvidia or AMD GPUs. You are expected to deliver on at least two of these. Location and working pattern: Bengaluru. The posting does not state a hybrid or remote arrangement, so assume in office. What the employer says about the team: a high talent density team, AI first in how it builds and ships, with high ownership from day one and population scale impact as the stated draw. Honest fit guidance: this is a narrow, deep specialism. Three years is enough if those years included real quantisation and profiling work on shipped models. General ML engineering experience without on device deployment will not clear the bar, because the entire role is about the gap between a research checkpoint and a model that runs fast on specific silicon. No interview process is published.
What the posting requires: - 4+ years building ETL pipelines for a data lake or warehouse. - Expertise in Python, Spark, SQL and Airflow. - Experience with data warehousing and engineering concepts, analytical data modelling, data quality validation, monitoring and pipeline reliability practices. - Hive, Iceberg, Glue or other technologies that expose big data as tables. - Familiarity with big data file formats including Parquet, Avro and JSON. - A background building data platforms on cloud, for example AWS, GCP or Azure. Nice to have: - Exposure to real time or streaming data technologies. What the work actually looks like: - Design, build and maintain efficient, scalable ETL and ELT pipelines using Python and Spark across batch, file based and streaming architectures. - Keep data quality, reliability and timeliness in line with established data engineering practice. - Model and store large datasets using modern file and table formats. - Deploy pipelines on cloud infrastructure, mostly AWS with some GCP. - Partner with data analysts and data scientists to deliver the datasets that drive their work. - Work with security and compliance teams so datasets carry the right permissions. - Work with the Data Platform and Governance teams to keep data scalable, consumable and discoverable. The ramp the employer publishes: - In 3 months: you will have built your first ETL pipeline with stakeholders in data analytics and data science. - In 6 months: you will have owned a large project from scoping and design through delivery. - In 12 months: you will have designed new features, led development work and become a go to expert on parts of the system. Location and working pattern: Gurgaon, and the posting states directly that MongoDB is looking for candidates based in Gurgaon for its hybrid working model. So this is hybrid, not remote, and location matters to them. Honest fit guidance: at 4+ years this is the lowest floor of the three MongoDB roles on today's board. The requirement list is squarely data engineering, so a backend engineer without Spark and Airflow depth would be applying against the grain.
What the posting requires: - A BS or higher in Computer Science or a related field. - 5+ years of production level experience in one of Python, Java, Scala, C++ or a similar language. - Experience developing large scale distributed systems from scratch. - Hands on experience developing and operating backend systems. - The ability to contribute across all project phases, from design and development through implementation and ongoing operations, with guidance from senior team members. Nice to have: - Experience in database replication, backup or transaction recovery at a major database vendor such as Microsoft SQL Server, Oracle or IBM. The posting lists this as a plus, and it is the clearest signal of what the team actually values. What the work actually looks like: - Deliver a highly scalable, available and fault tolerant engine processing hundreds of terabytes of data daily across thousands of customers. - Low level systems debugging, performance measurement and optimisation on large production clusters. - Build architecture designs, influence the product roadmap and own new projects. - Help prevent and investigate production issues. - Plan and lead complex technical projects that span several teams. - Break complex problems into solutions, knowns and unknowns, and de risk them through prototyping and validation. Why this team exists: ingesting data into the Lakehouse is described as a strategic investment area, and every Databricks surface including dashboards, notebooks, SQL and AI needs ingestion, so the team works closely with other product teams to embed Connect into those surfaces. Location and working pattern: Bengaluru. Databricks says it is building out its Bengaluru site with new teams, so expect an in office or hybrid arrangement. The number of days is not stated. Compliance note in the posting: where a role requires access to export controlled technology or source code, Databricks says applying for a US government licence is at its discretion and it may decline to proceed on that basis. That clause is in the posting and is worth reading before you invest time. Honest fit guidance: five years plus real distributed systems work is the bar. Database internals experience is what will separate applications here.
What the posting requires: - A BS or higher in Computer Science or a related field. - 5+ years of production level experience in one of Python, Java, Scala, C++ or similar languages. - Experience in software development on large scale distributed systems. - Familiarity with metrics collection, health monitoring and observability tools. What the work actually looks like: - Establish standards for logging, metrics and tracing across the platform. - Work with different teams to identify the metrics engineers need to see how the system and its subcomponents are performing. - Build tooling and infrastructure so components can efficiently emit, aggregate and store metrics for dashboards and alerting. - Contribute to and execute the technical roadmap for scalability, performance and reliability. - Participate in on call rotations and reduce incident response times. - Optimise platform and infrastructure cost by analysing system expenses, improving visibility, enforcing retention policies, streamlining queries and right sizing resources. The scale you would be working at, as stated: millions of virtual machines, terabytes of logs and exabytes of data processed per day, with hardware, network and OS faults treated as expected conditions. Location and working pattern: Bengaluru. The posting mentions Databricks is standing up ten new teams from scratch at this site, which suggests early team formation and the ambiguity that comes with it. Compliance note in the posting: the same export controlled technology clause appears here as on other Databricks roles. Where access to export controlled technology or source code is needed, applying for a US government licence is at the employer's discretion. Honest fit guidance: this is infrastructure engineering, not product. If your background is observability, metrics pipelines or large scale operations, the five year bar is met easily by the right experience. If you have never carried a pager, the on call requirement is stated plainly and is a real part of the job.
What the posting requires: - 5+ years of software engineering experience in full stack development. - Strong experience with Node.js, TypeScript and React.js. - Strong understanding of REST APIs, integration patterns and scalable application design. - Experience with relational and/or NoSQL databases. - Experience with cloud platforms, GCP preferred. - Familiarity with CI/CD pipelines, Git and modern engineering workflows. - Strong problem solving, debugging and collaboration skills. - The ability to work independently and mentor junior engineers. - A Bachelor's degree in Computer Science, Engineering or a related field is preferred rather than required. Nice to have: - Exposure to React Native or mobile application development, listed as preferred. - Exposure to Python for automation, integrations or backend services. - Familiarity with AI and LLM APIs or AI assisted engineering tools, listed as preferred. - Exposure to enterprise platforms or CRM integrated applications. What the work actually looks like: - Develop and enhance scalable backend services in Node.js and TypeScript. - Build responsive, maintainable frontends in React. - Develop and consume REST APIs and integration services, contributing to API first platform initiatives. - Participate in code reviews and technical discussions, and guide junior engineers on development standards. - Support CI/CD pipelines and modern engineering workflows. - Use AI assisted development tools to improve engineering productivity. The posting names GitHub Copilot, Claude, OpenAI and Gemini. Who you report to: a Senior Director, Support Systems and Tools Integration. That reporting line tells you the platform serves internal support and tooling needs as much as external ones. Location and working pattern: Bengaluru, India. The posting does not state office days. Honest fit guidance: a good fit for a full stack engineer with five years who wants senior IC scope with mentoring attached, in a company whose product is physical infrastructure. If you want to work on the EV charging hardware or firmware, this is not that role. ChargePoint states it provides reasonable accommodations throughout the hiring process and gives an email address for accommodation requests.
What the posting requires: - 5 to 8 years of industry experience in data engineering, machine learning engineering or related roles. - A B.Tech or equivalent qualification. - Strong understanding of generative AI system design: prompt engineering, RAG architectures, vector search, and evaluation techniques for LLM applications in production. - Experience with agentic AI patterns, including designing, orchestrating and monitoring autonomous or semi autonomous agents that coordinate tools, data sources and ML services with safety, observability and governance controls. - Experience with workflow orchestration platforms such as Apache Airflow, Prefect or Dagster. - Exposure to real time streaming and messaging systems such as Apache Kafka, Amazon Kinesis and Amazon SQS. - Knowledge of containerisation and orchestration with Docker and Kubernetes or EKS. - Proficiency with at least one Python web framework such as FastAPI, Django or Flask for data and model serving APIs. - Experience with data visualisation and BI tools such as Tableau, Grafana or Plotly Dash. - Familiarity with PyTorch, TensorFlow and Hugging Face Transformers. - Background in large scale data processing and lakehouse or warehousing technologies such as Snowflake, Redshift, Spark or EMR, and Delta Lake. - Experience with rapid prototyping tools such as Streamlit, Gradio or Dash for demonstrating ML solutions to stakeholders. What the work actually looks like: - Design, develop and deploy production ready solutions using generative AI, traditional ML, data science workflows and ETL or ELT pipelines on AWS and hybrid edge to cloud environments. - Build and manage real time and batch streaming pipelines for high volume fleet device data. - Implement MLOps practice: CI/CD for training, automated testing, model versioning, continuous monitoring and orchestration. - Champion data quality and governance with data contracts, validation and SLA monitoring. - Collaborate with product, data science, ML engineering and operations to put AI solutions into customer facing products. Location and working pattern: Bangalore. This posting does not state the number of office days. A note on the employer: Netradyne postings carry a recruitment fraud warning. Official communication comes only from netradyne.com or us-greenhouse-mail.io addresses, and the company never asks candidates for fees or sensitive data over unsecured channels. Honest fit guidance: the Staff title sits on a 5 to 8 year range, so treat it as a senior individual contributor role rather than a principal one. The generative AI and agentic requirements are listed as mandatory, not preferred, which is a meaningful filter.
What the posting requires: - 5 to 8 years of experience building scalable, highly critical distributed systems. The posting frames this as the candidate persona. - A B.Tech in Computer Science or equivalent from a reputed college. This is stated in the posting. - Strong object oriented design skills, the ability to apply design patterns, and the ability to design intuitive modules and class level interfaces. - Experience with highly concurrent multithreaded applications, with attention to system performance and throughput. - Good understanding of system performance trade offs, load balancing and engineering for high availability. - Excellent programming skills in Java, Python or another popular language. - Strong problem solving and debugging skills. - Good understanding of data structures and algorithms and their space and time complexity. What the work actually looks like: - Work on highly maintainable and efficient components and systems. - Act as a pod lead, driving features across multiple sprints. - Design, scope and implement independently. - Identify and resolve performance and scalability issues in an increasingly complex enterprise product. - Improve the overall quality of the code structure and the product. - Maintain both code and non code documentation for the components you own. About the product you would be working on: Hevo Pipeline is a no code platform that connects a company's data sources to give a unified view of the business, with integrations across databases, SaaS applications, advertising channels and more. The stated mission is to make the technology simple enough that people without deep technical skills can solve their own data problems. Location and working pattern: Bengaluru. The posting does not state office days. Honest fit guidance: pod lead is a technical leadership role over a feature stream, so expect ownership and mentoring without the people management overhead. The degree requirement from a reputed college is stated explicitly, which is worth knowing before applying if your background is non traditional. No interview process is published.
What the posting requires: - 6+ years of professional software engineering experience. - Deep experience with at least one modern programming language, with Python, Go and Rust named. - Strong technical judgement and the ability to independently solve complex engineering problems. - Excellent communication and comfort collaborating across teams and disciplines. - Comfort with modern infrastructure and delivery systems including containerised applications, Kubernetes and CI/CD tooling such as Drone.io. - A collaborative, detail oriented approach and an interest in building reliable, usable software. Nice to have, listed as a bonus round: - Experience building and maintaining full stack applications, from frontend UIs through backend API handlers to database migrations. - Experience designing systems or services used by other engineers or teams. - Knowledge of Next.js, FastAPI or React. What the work actually looks like: - Own the implementation and long term maintenance of internal tools and platforms. - Lead technical design discussions and contribute to architectural decisions. - Write high quality maintainable code and set an engineering example for a new team. - Identify and proactively address technical debt, reliability risks and scalability concerns. - Work with engineers, product partners and other stakeholders to prioritise and deliver high impact work. The ramp the employer publishes: - In 3 months: strong ownership of one or more internal systems and a meaningful contribution to ongoing initiatives, plus independently delivered improvements that reduce manual effort or operational friction. - In 6 months: technical improvements or new tooling that measurably improve internal engineering efficiency, reliability or velocity. Location and working pattern: the posting states MongoDB wants candidates based in Gurugram for its hybrid working model. Hybrid, not remote. Honest fit guidance: internal tooling work is often undersold, and this one comes with unusual scope because the team is being built from scratch. If you like owning systems other engineers depend on and you have six years behind you, it is a strong fit. If you want to work on the MongoDB database itself, this is a different part of the company.
What the posting requires: - 6+ years of hands on DevOps experience, with strong expertise designing and managing cloud infrastructure. - Strong experience in VMware to AWS migration projects or large scale infrastructure migrations. - 4+ years of Terraform and CloudFormation for infrastructure as code. - 4+ years in configuration management, systems engineering and managing production grade infrastructure. - A solid Linux and/or Windows administration background. - Deep understanding of AWS services including VPC, EC2, IAM, EKS, ECS, RDS, S3, Backup and CloudWatch. - Production experience with Kubernetes on EKS, ECS and Docker. - Hands on experience designing high availability, disaster recovery, security and backup strategies. - Experience with Landing Zone setup, multi account strategy and AWS governance frameworks. - Proficiency in Git, including branching and merging strategy. - Experience with CI/CD pipelines, automation and operational tooling. Nice to have: - Experience across multiple clouds, AWS plus Azure or GCP. - AWS certifications such as Solutions Architect Associate or Professional, or DevOps Engineer Professional. - Exposure to data platforms such as Amazon EMR, Redshift, Lake Formation and SageMaker. - Experience designing cloud architectures at an L3 or architect level. What the work actually looks like: - Lead infrastructure design and implementation for a large scale VMware to AWS migration, from discovery through production cutover. - Architect secure, scalable, highly available AWS environments including Landing Zones built to AWS best practice. - Design and implement containerised platforms on Amazon EKS. - Define and enforce practice across security, backups, HA, DR, monitoring and operations. - Enable configuration management with Ansible, Chef or similar. - Build CI/CD pipelines and own the build and release lifecycle for customer applications. - Provide L3 support for complex infrastructure and platform issues. - Retire legacy infrastructure and land cloud native architecture in its place. - Mentor engineers and contribute to talent evaluation. The delivery model, stated plainly: senior engineers embed with the customer team and personally carry the delivery commitment against fixed dates, with Mactores absorbing overage cost for delays inside its control. The company describes its agent platform as absorbing the discovery and dependency mapping grind so engineers own the judgement calls. Location and working pattern: Mumbai, embedded with customer teams. Honest fit guidance: this is consulting delivery work with a hard commitment attached, not a platform team seat. If prior migration experience is what you want to build on, the posting is direct that the goal is retired VMware clusters rather than revised project plans.
What the posting requires: - 7+ years building production backend systems at scale. - Strong Go in production: designed, built and operated Go services under real load. - Comfort in Python, since you work in both languages through the rewrite and FastAPI is the current foundation. - A track record designing and operating high scale, low latency, multi tenant distributed systems. - Hands on experience with real time and streaming systems: WebSockets, long lived connections and backpressure. - Strong PostgreSQL and Redis fundamentals covering schema design, query performance and caching strategy. - Comfort running services on Kubernetes in production. - Senior individual contributor judgement: when to build versus buy, optimise versus ship, abstract versus inline, and how to bring others with you. Nice to have: - Experience serving LLM, ASR, TTS or vision models in production. - Background in audio processing with pyav, FFmpeg, codec and sample rate work, or VAD. - Experience building metering, billing or wallet and payments infrastructure. - Time at an early or growth stage startup. What the work actually looks like: - Own the end to end design and evolution of the platform, from the moment a request hits the edge to the response going back out. - Lead the Python to Go rewrite: architecture, patterns and migration without losing reliability. - Audio pipeline engineering: TTS chunking around model context limits, sample rate adjustment, format encoding, VAD based silence detection for ASR. - Vision pipelines: orchestrating OCR, layout detection and VLM harnesses for structured data extraction. - Streaming infrastructure: WebSocket connections, queue based batch processing, backpressure and low latency model invocation. - The commercial layer: metering, billing, prepaid wallet management and rate limiting. - Observability across logging, metrics and tracing, and the integration test harness that lets the team ship without breaking customer APIs. - Partner with the Inference and MLOps teams and mentor them on production engineering. How the team works: design first and documentation first, with RFCs before code, decisions written down, and an explicit goal of no tribal knowledge. Location and working pattern: Bengaluru. No remote or hybrid arrangement is stated. Honest fit guidance: this is a senior IC ownership role, and the Go requirement is not negotiable given the rewrite sits at the centre of the job. Python only backend engineers would be applying against the primary ask.
What the posting requires as minimum: - 8+ years of experience designing, implementing and operating large scale, high performance APIs and services. - Experience implementing server side APIs in dynamic languages such as Ruby, working with document and relational datastores, especially Mongo and MySQL, and comfort exploring unfamiliar datasets. Preferred qualifications, described in the posting as a bonus rather than a requirement: - Experience with large scale financial tracking systems. - Practical knowledge of cloud based services such as gRPC, GraphQL, Docker, Kubernetes and AWS. - Experience in the marketing domain, building products in a marketing technology stack. - Experience with machine learning, recommender systems, product led growth or lifecycle marketing. - Prior experience building distributed systems or microservices architecture. What the work actually looks like: - Design, build and maintain robust, high performance APIs and services. - Keep the infrastructure extensible, scalable and reliable, meeting service level agreements for both external and internal users. - Hide complexity from users behind simple but powerful abstractions. - Partner with engineers, analysts and scientists to build scalable systems and comprehensive interfaces. - Build the APIs powering internal stakeholder facing UI experiences, defining composable data models and durable interfaces. - Debug production issues across services and multiple levels of the stack, with a bias toward long term maintainability. - Improve engineering standards, tooling and processes. Which team you would join: the posting covers several, including Seller Systems (deal modelling and pricing engines, approval and orchestration platforms, CLM and CPQ integrations, onboarding automation, seller analytics and AI assisted tooling) and Finance Engineering (accounting automation, auditing, financial planning and forecasting, business intelligence). Location and working pattern: Bengaluru, India. Office days are not stated in the posting. Honest fit guidance: Stripe says directly that if you meet the minimum requirements you are encouraged to apply and that the preferred list is a bonus, not a requirement. That said, eight years is a real bar, and the specific ask is API and service design at scale. Internal systems work at Stripe still runs at payments scale, so do not read internal as small.
What the posting requires: - 8 to 12 years of software engineering experience with deep frontend expertise. - Expert level proficiency in JavaScript, TypeScript, HTML and CSS. - Extensive experience with React or similar frameworks in large scale applications. - Strong expertise in frontend architecture, design systems and scalable UI development. - Proven experience building and evolving shared component libraries or frontend platforms. - Deep understanding of browser internals, rendering and performance optimisation. - Experience defining and driving frontend standards and best practices across teams. - Demonstrated ability to influence technical direction without direct authority. - Strong ability to translate product and design needs into scalable technical solutions. - Experience with modern frontend tooling, CI/CD pipelines and cloud environments. - Familiarity with observability, monitoring and performance tracking tools. - Experience working on large scale SaaS platforms. Nice to have, listed as good to have: - Leading or contributing to design systems at scale. - Exposure to micro frontend architectures or modular frontend systems. - Familiarity with security considerations in frontend applications. - Experience with AI assisted development tools such as Codex or Cursor. - Background in improving developer experience and platform engineering. - Experience driving frontend modernisation or platform adoption initiatives. What the work actually looks like: - Define and evolve frontend architecture patterns and shared capabilities across product teams. - Lead architecture reviews and guide frontend design decisions across teams. - Drive adoption of shared frontend platforms, frameworks and tooling, and reduce duplicated engineering effort. - Establish engineering standards and decision frameworks for frontend development. - Define and drive standards for performance, accessibility and user experience. - Identify systemic risks such as performance bottlenecks, architectural inconsistency and maintainability problems, and lead cross team efforts to address technical debt. - Mentor senior engineers and act as a technical multiplier across teams. What success looks like, per the posting: within 12 to 18 months successful staff engineers at Ontic are driving initiatives across teams rather than owning a single product area. Location and working pattern: Noida, India. Ontic has the same role open in Pune, so check which location suits you before applying. Office days are not stated. Honest fit guidance: this is a platform and architecture seat for a deep frontend specialist. If your experience is feature delivery in React without shared library or design system ownership, the required list will read as a stretch.
What the posting requires: - 5 to 8 years designing, building and troubleshooting distributed computing applications, with 4+ years delivering production scale Spark, ML or AI solutions in Python, Java or Scala. - 3 to 5 years in customer facing roles such as Technical Account Manager or Solutions Architect, with strong communication and relationship building. - Hands on expertise with data lakes, SQL based databases and cloud data warehousing or ETL tools such as Snowflake, Redshift or BigQuery. - Deep knowledge of Spark core internals, Delta or Iceberg, JVM optimisation and memory management. - Proficiency in AI ecosystems including machine learning, deep learning and generative AI. - Practical experience with AWS, Azure or GCP, plus building and managing CI/CD pipelines, monitoring and alerting. - Proven ability to anticipate, identify and mitigate risk while planning solutions for production problems. - Proven ability to work with cross functional teams and senior leadership. What the work actually looks like: - Advanced troubleshooting and root cause analysis on performance and reliability issues across Spark, SQL, Delta, Streaming and Databricks runtime features, using Spark UI metrics, Mosaic AI Model Service, DAGs and event logs. - Work with R&D and network operations teams to define continuous monitoring that catches performance problems early in customer environments. - Build rapid proofs of concept, then test, deploy and monitor solutions that address customer challenges. - Develop playbooks and maintain a knowledge base of common issues and solutions. - Train customer engineering and business teams on performance tuning, debugging and platform features. - Advocate for customers in business review meetings as their trusted advisor and primary technical contact. - Work onsite with field engineering, sales and product teams during customer engagements and technical presentations. Location and working pattern: Bengaluru. The posting refers to collaborating onsite with field teams during customer engagements, so expect customer site visits as part of the job. Compliance note in the posting: the standard Databricks export controlled technology clause applies, under which applying for a US government licence is at the employer's discretion where such access is required. Honest fit guidance: this role needs both halves. Deep Spark internals knowledge without customer facing experience, or account management skill without the ability to read an event log, will each fall short of the stated requirements. It suits a data engineer who has already spent a few years in front of customers.
What the posting requires: - 6 plus years of experience, stated in the ideal candidate section. - Systems engineering experience covering Linux performance, memory management, I/O tuning, configuration, security, storage, networking, clusters and troubleshooting. - Good understanding of networking concepts and protocols including DNS, TCP/IP and SSL/TLS. - Broad awareness of customer workloads and use cases across performance, availability and scalability. - Experience analysing issues holistically, from the application tier through the database down to the storage. The posting also lists things every candidate must have: - Excellent written and verbal communication. - A genuine desire to help people. - A strong urge to investigate and solve problems, with advanced diagnostic and troubleshooting skills. - The ability to think on your feet, stay calm under pressure and solve problems in real time. - The ability to rapidly learn a wide variety of new technical skills. - Strong teamwork, including the judgement to know when to ask for help. Nice to have: - Comfort with modern AI concepts and proficiency using AI assisted tools to speed up troubleshooting. - Experience with one or more of Java, Python, Ruby, C, C++, C#, JavaScript, Node.js, Go, PHP or Perl. What the work actually looks like: - Work alongside MongoDB's largest customers on complex challenges spanning architecture, performance, recovery and security. - Act as an expert resource on best practice for running MongoDB at scale. - Advocate for customer needs with product management and development teams. - Contribute to internal projects, including software development of support tools for performance, benchmarking and diagnostics. The ramp the employer publishes: - In 3 months: a deep understanding of MongoDB and its ecosystem, and completion of new hire training. - In 6 months: comfortable working frontline with customers, and completion of the MongoDB Certified DBA Associate exam. - In 12 months: building expertise toward a technical experts group, helping peers with advanced diagnostics, and handling technical escalations independently. Location and working pattern: the posting states MongoDB wants candidates based in Bengaluru for its hybrid working model. Honest fit guidance: MongoDB says it considers all candidates with an eye for those who are self taught, curious and multi faceted, which is a real signal for non traditional backgrounds. The systems engineering depth is where applications will be judged, not the years alone.
What the posting requires: - Minimum 7+ years of experience supporting large enterprise customers. - Strong networking background, with extensive and in depth knowledge of TCP/IP, HTTP and HTTPS, cookies and SSL/TLS protocols. - Prior experience supporting network security technologies such as proxies, next generation firewalls, SSL and IPSec, VPNs, DLP and SSO. - Demonstrable experience installing, configuring and administering UNIX, Linux and Windows based systems. Active Directory or LDAP experience is desirable. - Expert troubleshooting across scenarios and systems using common tools such as tcpdump and protocols including TCP/IP, NTP, DNS and DHCP. - Good understanding of web technologies including JSON, XML, SOAP, REST, HTML5, web services and JavaScript. - Hands on experience with traffic analysis tools such as Fiddler and Wireshark. - System and server side experience for troubleshooting. - A B.E., B.Tech or M.Tech degree from a recognised and accredited university. Desired technical skills: - Hands on experience configuring and testing applications for SAML single sign on with various identity providers. WS-Fed and WS-Trust experience is a plus. - Prior experience testing HTTP content rewrite solutions. - Cloud technology including Docker, Kubernetes and open source tooling. - Working experience across Linux, Windows and mobile environments. - Strong familiarity with a scripting language, Python or Java, with Python preferred. - Prior experience mentoring and guiding junior team members. What the work actually looks like: - Own and drive escalated support issues to resolution. - Work critical incident response tasks as required, and general support tickets as required. - Work with support managers, engineering and product management to build and improve processes, procedures and tools. - Drive weekly technical team calls alongside other technical leads. - Share knowledge on new issues with the wider team and field. - Assist and mentor frontline support engineers. Location and working pattern: Bengaluru. Netskope describes open desk offices, so expect an in office team. Office days are not stated. Application timing: the posting states the application window is expected to close within 50 days. Honest fit guidance: this is a deep networking and security support role at the escalation tier. If your support experience is application level rather than packet level, the required list will be the gap.
What the posting requires as minimum qualifications: - 8+ years of experience as a Support Engineer or Senior Support Engineer supporting networking or web security products. - A foundational understanding of AI and ML technologies, and experience leveraging, securing or positioning AI driven solutions within your domain. Zscaler describes itself as an AI forward enterprise and puts this first in the list. - Practical knowledge of networking and security products and enterprise network infrastructure. - Experience troubleshooting network issues with tools such as Ping, Traceroute and MTR. - Hands on experience with SD-WAN, routing protocols including BGP and OSPF, firewall, switching, SSL, secure web gateway and VPN. - Working, hands on knowledge of Ubuntu and Python. Preferred qualifications: - Demonstrated experience with Zscaler products such as ZIA, ZPA and ZDX, or similar cloud security platforms, including TLS and SSL inspection and authentication flows. - Proficiency scripting for automation, efficient troubleshooting and reproducing complex customer environments. What the work actually looks like: - Engage with customers on escalated support issues and critical situations, participating in a 24x7 support operation and a 24x7 on call rotation. - Interface with engineering and assist customers with testing and troubleshooting. - Reproduce customer issues to verify problems, and feed findings back to engineering and operations. - Document incident resolutions in the technical support database when they are not already in the knowledge base. - Understand product direction and customer use cases, and give input on product and code changes across the product cycle. Who you report to: the Senior Manager, Product Support. Location and working pattern: the posting states this is a hybrid role based in the Bangalore or Mohali office. That is one of the few explicit hybrid statements on today's board. Benefits stated in the posting: various health plans, time off for vacation and sick leave, and parental leave. Honest fit guidance: the 24x7 on call rotation is stated up front and should be weighed honestly before applying. If you have eight years in network security support and want escalation level work with direct engineering contact, this is a strong match. Zscaler describes a culture of execution centred on customer obsession, ownership and accountability, with an emphasis on speed.
What the posting requires as minimum: - A B.S. in Computer Science, Engineering (mechanical or electrical) or another technical field. - 8+ years in technical support, solutions engineering or similar roles working directly with complex SaaS products, with at least one area of depth in mobile applications or fleet and telematics workflows. - Proven expertise troubleshooting mobile apps across Android and/or iOS, including device and OS constraints, network behaviour, authentication flows, app configuration and data synchronisation with backend services. - Strong debugging and root cause analysis: decomposing ambiguous multi system issues, identifying the high leverage logs and signals, and driving to a clear root cause and mitigation. - Demonstrated experience working directly with engineering and product: reading Jira tickets and RFCs, validating hypotheses in lower environments, and influencing prioritisation with data and customer impact. - Excellent written and verbal English, with comfort presenting complex technical narratives to engineers and to non technical stakeholders including customer success, sales, customers and leadership, across regions. - A strong ownership mindset and bias for action, including making pragmatic decisions under time pressure. - Demonstrated resourcefulness, creativity and problem solving, and the adaptability to work in a fast paced environment. What the work actually looks like: - Act as primary Level 3 owner for high impact and ambiguous mobile issues across driver, fleet, routing and dispatch flows, asset maintenance, connected workflows and mobile to cloud data mismatches. - Lead structured, hypothesis driven investigations end to end. - Partner with engineering teams across mobile experience, driver management, routing and dispatch, connected workflows, asset maintenance, compliance and product security to assess impact, prioritise fixes and influence roadmaps. - Own customer and stakeholder communication on critical issues, including business impact assessments, periodic updates and post incident summaries suitable for senior audiences in EMEA and globally. - Identify patterns across tickets and incidents and drive product and tooling improvements such as better logging, app state capture and diagnostics. - Maintain internal runbooks, incident playbooks and knowledge base content, reflecting regional nuances such as EMEA regulations and language support. - Mentor and coach Level 2 engineers on troubleshooting depth, documentation quality and escalation criteria. - Analyse device telemetry and fleet level patterns using internal tools. Location and working pattern: Bengaluru. The posting refers to supporting senior audiences in EMEA, so expect some overlap with European hours. Honest fit guidance: this is a senior support engineering role with real technical depth and real writing load. Both matter here: the posting asks as much for clear narratives to executives as for log analysis. If mobile debugging is not one of your strengths, the stated area of depth requirement will be the gap.
What the posting asks for. Note that GitLab does not publish a years of experience figure for this role, so judge yourself against the skills rather than a number: - Experience operating backend services in production, including deployment, monitoring and maintenance in Kubernetes and Helm based environments. - Proficiency in Go for building observable and resilient services, with working knowledge of Ruby as a useful addition. - Hands on practice with infrastructure as code, including Terraform, and managing infrastructure across cloud providers such as Google Cloud Platform, AWS or Microsoft Azure. - Knowledge of database design, operations and troubleshooting, especially PostgreSQL in secure and scalable setups. - Knowledge of secure, scalable and reliable deployment practices, including service scaling and rollout strategies. - Familiarity with observability tools and patterns such as Prometheus and Grafana. What the work actually looks like: - Maintain and evolve the Omnibus GitLab package for reliable, production ready self managed deployments, improving deployment stability and upgrade success rates and reducing escalations. - Develop and improve GitLab Helm Charts so core components integrate cleanly and scale across supported environments. - Enhance the GitLab Environment Toolkit, validated reference architectures and the GitLab Operator for secure, Kubernetes native lifecycle management. - Improve installation, upgrade and operational workflows so self managed customers get a consistent experience. - Partner with Security to address vulnerabilities and deliver secure defaults in the deployment stack. - Build and maintain CI/CD pipelines that validate and test Omnibus, Charts, GET and the Operator. - Work with Distribution Engineers, Site Reliability Engineers, Release Managers and development teams. - Guide architectural direction, mentor backend engineers and contribute to the roadmap for self managed delivery. How the team works: the posting describes a globally distributed, all remote group working asynchronously with SRE, Release, Security and Development teams across regions. Location and working pattern: GitLab states that all of its roles are remote, and that some roles carry specific location based eligibility requirements which its talent acquisition team can clarify. This listing is open to India. That combination, remote backend work open to India, is the single most requested thing by readers of this list. One more thing worth knowing: GitLab states that it treats AI as a core productivity multiplier and expects all team members to incorporate AI into their daily workflows. Honest fit guidance: with no years figure published, the deciding factor is whether you have run backend services in Kubernetes and written Go. Deployment tooling is a specialism, so if you have packaged and shipped software that other people install and operate, that experience counts here more than a year count would.
What the posting asks for. GitLab publishes no years of experience figure on this role, so measure yourself against the skills: - Proven backend engineering experience, including production Ruby on Rails expertise, since Rails is the team's primary language. - Working knowledge of Go, or a clear willingness and ability to ramp up quickly in it. - Solid API design skills, including REST, GraphQL and defining clear internal service boundaries. - Solid PostgreSQL fundamentals including schema design, query optimisation and indexing strategies. - Experience with Redis for caching and distributed coordination patterns. - A security aware engineering mindset. What the work actually looks like: - Design and implement backend features across the add on's supply chain security surface: policy enforcement, artifact signing and verification, provenance attestation APIs and malicious package detection integrations. - Build and improve the package policy evaluation engine, covering rule compilation, request matching, enforcement decisions and performance sensitive execution paths tied to GitLab's Dependency Firewall. - Develop artifact signing and verification workflows using Sigstore and Cosign, including signing key lifecycle management, keyless signing with OpenID Connect, and policy based promotion gates. - Create and evolve the configuration interfaces enterprise security teams use, including backend APIs and the GraphQL surface. - Integrate the add on with GitLab's existing security policy framework, including policy inheritance and policy as code through YAML. - Write and maintain comprehensive RSpec and integration test coverage, and improve test reliability across the team. - Review merge requests with a security first mindset, with substantial decision making scope in partnership with the Staff Backend Engineer. What kind of team this is: the posting describes a founding role on a small team with a high level of responsibility, and says the engineering choices made in API design, testing, performance and security will shape how the product grows. Location and working pattern: GitLab states that all of its roles are remote, with some carrying location based eligibility requirements that its talent acquisition team can clarify. This listing is open to India. The posting also describes GitLab's all remote, asynchronous environment as part of what the role is suited to. One more thing worth knowing: GitLab expects team members to incorporate AI into their daily workflows, stating it treats AI as a core productivity multiplier. Honest fit guidance: the Rails requirement is primary and explicit, so this is a fit for a Rails backend engineer with security interest rather than a security specialist looking to learn Rails. Founding team means less process and more ambiguity than a mature team.
What the posting asks for. As with GitLab's other listings, no years of experience figure is published: - Strong software engineering experience designing and delivering production systems that customers install and operate in their own infrastructure. - Proficiency in Go for large, complex codebases, with familiarity with Ruby on Rails and Rails application architecture as a useful addition. - Hands on production Kubernetes experience, including building and maintaining Operators, designing Helm charts for stateful applications, and working with Custom Resource Definitions, admission controllers and controller patterns. - Knowledge of cloud native systems and tooling such as service mesh, observability stacks, infrastructure as code and automation tools like Terraform or Ansible. - Experience with stateful workloads and databases, including PostgreSQL schema design and migrations, persistent volumes, storage classes and approaches for reducing downtime during upgrades. - Understanding of Linux systems and production operations, including package management, systemd, system level debugging, observability, incident response and on call participation. - The ability to guide through influence: clear technical proposals, documented decisions, mentoring and cross team work. - Interest in open source infrastructure or deployment tooling, or transferable experience from adjacent domains. What the work actually looks like: - Guide the technical vision and architecture for GitLab's cloud native self managed deployments and upgrade workflows. - Establish operational maturity standards, service integration patterns and deployment models. - Design and maintain Kubernetes Operators, Helm charts and upgrade orchestration tooling. - Develop automation and integration frameworks for database migrations, rolling deployments, compatibility checks and rollback paths. - Define database and application lifecycle strategies, including safe PostgreSQL migration approaches. - Work with product management, GitLab.com SRE, GitLab Dedicated and development teams to align deployment patterns with customer needs. - Mentor engineers and enable customer facing teams through design reviews, code reviews, documentation and runbooks. - Drive observability, testing, performance and resilience practice, and contribute to incident response and post incident learning. What the first year looks like, per the posting: helping define the architecture for zero downtime upgrades, strengthening observability and reliability practice, and guiding the next generation of deployment automation for self managed environments. Location and working pattern: all GitLab roles are remote, with some carrying location based eligibility requirements. This listing is open to India. Honest fit guidance: this is the most senior of the four GitLab roles on today's board even though none of them state years. Kubernetes Operator authorship and stateful upgrade experience are the distinguishing requirements, and without them the rest of the list will not carry an application.
What the posting asks for. GitLab publishes no years figure, but the overview describes the target level as Intermediate, which is the clearest levelling signal across GitLab's four listings today: - Professional experience operating production infrastructure on AWS at scale, including EC2, Auto Scaling Groups, IAM and VPC networking. - Strong infrastructure as code experience with Terraform, including writing and refactoring modules used by other teams. - Proficiency in Go for building and debugging infrastructure tooling, or strong experience in another systems language and willingness to work in Go daily. - Practical knowledge of CI/CD systems and job execution: how pipelines schedule work, how ephemeral build environments are provisioned and torn down, and what makes CI workloads reliable. - Experience with observability practice including metrics, dashboards, alerting, logging and SLO based monitoring, using tools such as Prometheus, Grafana and OpenSearch. - Experience with on call rotations and incident management for customer facing systems. - Strong problem solving, excellent written communication, and comfort working asynchronously across the Americas, Europe, Middle East, Africa and Asia Pacific. Nice to have: - Direct GitLab Runner experience. - Familiarity with configuration management such as Ansible. - Container tooling such as Docker. What the work actually looks like: - Design, build and operate AWS infrastructure for Hosted Runners across many single tenant environments, spanning EC2, Auto Scaling Groups, VPC networking, subnets, NAT, network ACLs, PrivateLink, IAM and ECR. - Develop and maintain infrastructure as code in Terraform, contributing to common modules and deployment tooling. - Write Go for runner tooling and autoscaling components, including instance lifecycle plugins, a zero downtime deployment CLI and reusable infrastructure toolkits. - Build and improve the GitLab CI/CD pipelines that orchestrate blue green zero downtime deployments, automated upgrades, QA validation and performance testing. - Define and monitor service level objectives for CI job execution, and build the dashboards, alerts and runbooks behind them. - Participate in an on call rotation, handle incidents affecting customer CI/CD workloads, and automate recurring toil away. - Run performance and scale testing that reflects real customer workloads, and tune autoscaling for cost and reliability. - Write documentation and runbooks so the team can operate runner stacks consistently. Location and working pattern: all GitLab roles are remote, with some carrying location based eligibility requirements. This listing is open to India, and the posting explicitly asks for comfort working asynchronously across many time zones. Honest fit guidance: if you have run AWS infrastructure with Terraform and are willing to work in Go daily, this is the most approachable of GitLab's four openings today. The on call rotation is stated plainly. Do not let the SRE title put you off if your Go is not deep yet, because the posting accepts strong experience in another systems language plus willingness to work in Go.
Added July 24, 2026
What the posting asks for: - Professional experience with Ruby on Rails. - A background in site reliability or observability engineering: monitoring, alerting, SLOs, SLIs, runbooks, incident handling, and tools such as Prometheus, Grafana and OpenTelemetry. - Experience building anomaly detection, monitoring or risk management tooling. - Exposure to reporting data stores, especially ClickHouse, and the change data capture and event streaming pipelines that feed them (Siphon, NATS JetStream). - Experience with billing, financial or other business critical systems. - Experience owning a project from concept to production, including proposal, discussion, execution and monitoring. - Clear written communication in English, because the team is remote and largely asynchronous. Counts as a bonus: - Working knowledge of Python for anomaly detection and data work. - Hands on experience with Zuora or Salesforce. The day to day: designing metrics, logs and traces across the Monetization stack, building automated detection for billing and event anomalies and routing those alerts to the right feature team, writing reconciliation and data integrity checks across usage and billing pipelines, defining SLOs and SLIs, writing runbooks, taking part in incident handling, and reviewing other engineers' merge requests. You would report to the Engineering Manager for Observability, Monitoring and Integrations. Experience: GitLab publishes no years figure anywhere in this posting, so we have left it blank rather than guess. What the posting does say is that the role is open at both the Senior Software Engineer and Staff Software Engineer levels, and that GitLab welcomes candidates with varying levels of experience because many successful hires do not meet every requirement. Location: fully remote. GitLab states that all of its roles are remote, though some carry location based eligibility rules, so confirm yours with the recruiter early. Who should apply: a backend engineer who is comfortable in Rails and genuinely enjoys observability work. This is a greenfield team, so you would help set its operating rhythm and quality bar rather than inherit one. If you want a tightly specified ticket queue, this is not that.
What the posting asks for: - Professional experience working with Ruby on Rails. - Experience integrating with third party or enterprise APIs, including billing, CRM or automation platforms. - Strong API design skills: REST, GraphQL, contracts, versioning and backward compatibility. - Familiarity with event driven patterns such as webhooks and message based streaming. - Familiarity with PostgreSQL or a similar relational database, and with data integrity and governance concepts in production. - Systems thinking, and experience owning projects from concept through production. - Ability to communicate clearly in a remote, largely asynchronous environment. Counts as a bonus: - Familiarity with NATS JetStream. - Experience with subscription management or billing systems such as Zuora or Salesforce. The day to day: building and maintaining the integrations between CustomersDot, Monetization services and enterprise applications, defining and evolving API contracts, tracking failure rates and retry success and data integrity incidents, keeping data consistent across integrated financial systems, reviewing merge requests, and working with Product, Finance, IT, Sales and Support to turn cross system needs into reliable integrations. Experience: no years figure is published, so we left it blank rather than invent one. The posting states GitLab is hiring this role at the Software Engineer and Senior Software Engineer levels, and GitLab's standard note applies: they welcome candidates with varying levels of experience and many successful candidates do not meet every requirement. Of the four GitLab roles in today's list this is the one aimed lowest. Location: the posting lists Bangalore, but GitLab is a fully remote company and states that all of its roles are remote, with some carrying location based eligibility rules. Who should apply: a Rails engineer a few years in who wants API and integration depth rather than feature work, and who is comfortable being careful because the data is financial.
What the posting asks for: - Expert knowledge of cloud infrastructure security (AWS, GCP or Azure), container orchestration with Kubernetes, and related infrastructure and data security topics. - Proficiency in multiple programming languages (Go, Python, Ruby) with a track record of shipping production quality security tooling. - Extensive experience with Infrastructure as Code security (Terraform, Ansible, CloudFormation), policy as code and automated compliance. - Hands on experience applying AI to security workflows, with a view on where it creates real leverage. - A track record of leading multi team technical initiatives from an ambiguous problem statement to a measurable outcome, setting direction that peer teams adopt. - Strong written and verbal communication, including explaining security tradeoffs to senior leadership. - Familiarity with security certifications and frameworks: FedRAMP, ISO 27001, SOC 2, PCI DSS. The day to day: setting architectural patterns, reference implementations and foundational security automation; leading security initiatives from problem framing through delivery; running security reviews and threat modelling for complex infrastructure; setting the team's approach to AI assisted security engineering; acting as the authoritative technical voice for Infrastructure Security with stakeholders; and mentoring engineers. GitLab also expects the team to secure GitLab's own infrastructure using GitLab, which they call dogfooding. Experience: no years figure is published anywhere in the posting, so we left it blank. Staff at GitLab is a senior individual contributor level, and the responsibilities listed (multi quarter ambiguous initiatives, setting direction other teams follow) point well above entry level even though no number is given. Location: remote, and open to India, Israel, the United Kingdom and the United States. GitLab notes some roles carry location based eligibility rules. Who should apply: an experienced infrastructure or cloud security engineer who wants scope over a platform rather than a queue of findings, and who is comfortable writing the tooling instead of only reviewing it. This is a leadership role without direct reports.
What the posting asks for: - A proven track record of delivering actionable intelligence that measurably improved an organisation's security. - Experience working with a Threat Intelligence Platform and managing ingested and exported threat feeds. - Experience researching adversaries using OSINT and structured analytical techniques. - The ability to automate tasks by writing scripts or programs, preferably in Python. - Excellent written and verbal communication, with the ability to make complex topics clear. Counts as a bonus: - Experience reverse engineering malware, particularly macOS and Linux malware and malware delivered through code repositories. - Public blogs or open source work related to threat intelligence. The day to day: monitoring the threat landscape and raising ad hoc Flash Reports, administering the Threat Intelligence Platform and extending the open source, proprietary and internal collection pipeline, supporting incident response through malware analysis and threat actor tracking, collaborating on Purple Team Flash Operations where an emerging threat becomes a live exercise, building relationships with industry peers to share intelligence, and writing code and automation to make the team more efficient. Experience: GitLab publishes no years figure, so we left it blank. The posting describes the person as a seasoned threat intelligence engineer and the level is Senior, but no number is given and we will not invent one. Location: remote, open to Canada, India and the United States. Note the manager sits in Australia, so expect some meetings shifted towards Asia Pacific hours rather than a purely India schedule. Team context worth reading carefully: you would be the only dedicated person on this team, supported by Security Operations engineers who spend part of their time on threat intelligence. That is a lot of autonomy and also a lot of solitude. Security Operations at GitLab also covers SIRT, Trust and Safety, Signal Engineering, Red Team and Security Logging. Who should apply: someone who already does threat intelligence and wants to own a programme end to end rather than be one analyst among many. If you need a senior peer in the same specialism sitting next to you, read the team note again first.
What the posting asks for: - 7+ years of experience building campus or data centre network infrastructure, AWS cloud services and networking. - 5+ years with Cisco LAN, WAN and WiFi and Palo Alto Networks firewalls. - 3+ years with AWS cloud services and networking. - Advanced knowledge of IEEE 802 standards and core IETF protocols, including the 802.11 suite, TCP/IP, DNS, DHCP, and routing and switching protocols. - Hands on network monitoring knowledge. - Knowledge of network security, enough to implement security policy for compliance. - Client networking on Windows, Mac and Linux. - Experience troubleshooting network problems across different OSI layers. - A university degree in computer science or equivalent experience. Counts as a bonus: - Cisco CCNA or CCNP certification, and AWS certification. - Zscaler Zero Trust Systems experience or certification. - A scripting language with API automation, and Terraform for infrastructure as code. - Knowledge of ITIL, and project management skills. The day to day: building and supporting the global IT network, tracking network assets, reporting performance and availability metrics to IT leadership, working with stakeholder teams on future network needs, prioritising work using the Scaled Agile Framework, building tools to test and roll out new LAN and WAN systems, responding to incidents, and maintaining network design and standards documentation. Experience: the posting states 7+ years for the primary requirement. Read the three requirements together, because they stack: 7+ years overall on network infrastructure, of which 5+ on Cisco and Palo Alto and 3+ on AWS. Location and travel: remote within India, but restricted to Karnataka, Tamil Nadu, Telangana, Maharashtra and Delhi. Roughly 15 percent travel is expected. Who should apply: a network engineer with real data centre and campus experience who wants to stay hands on. Note this is corporate and internal infrastructure, not Twilio's carrier or product network, so it is closer to enterprise IT engineering than to telecom product work.
What the posting asks for: - Twilio product experience. The posting states this as a must, so it is the hard filter on this role. - 5+ years in Technical Support, Product Operations, Technical Account Management or Engineering, focused on complex technical products such as APIs, SaaS or telecommunications. - Experience in the technology industry, including APIs and VOIP, in either a development or a support capacity. Familiarity with customer or consumer trust applications is preferred. - Proven analytical skills using data tools such as Splunk, Datadog, Snowflake, SQL or Tableau to turn customer feedback and support trends into insight. - Excellent communication and influencing skills, since the job is largely persuading engineering to prioritise supportability work. Counts as a bonus: - Project management experience, or experience running programmes and product launches. - Proficiency in Python, Java or Node.js, enough to understand the developer experience. - Knowledge of design thinking or UX principles for spotting friction in customer journeys. The day to day: embedding supportability requirements into the earliest stages of the product development lifecycle by joining design reviews and technical planning with R&D, analysing support data to build business cases, specifying proactive product features such as clearer error messages and diagnostic tools, orchestrating global operations readiness for new features, and translating complex customer use cases into requirements. Experience: the posting states 5+ years, and accepts that experience from four different directions (support, product operations, technical account management or engineering), which makes it more open than the title suggests. Location: remote within India, restricted to Karnataka, Tamil Nadu, Telangana, Maharashtra and Delhi. Who should apply: someone who has done deep technical support or technical account management on an API product, is tired of fixing the same issue repeatedly, and wants to attack the cause upstream instead. Twilio also says openly that it values non traditional career paths for this role. The Twilio product experience requirement is the real gate, so if you have never used Twilio in anger, expect a hard time.
What the posting asks for: - 15+ years of experience designing and scaling distributed systems and platforms. - A demonstrated ability to set technical vision and strategy at enterprise or company wide level. - Expertise in system design, reliability, scalability, security and cost optimisation for large scale architectures. - Experience leading cross functional initiatives and resolving highly complex, ambiguous technical problems. - A proven record of mentoring senior engineering talent and raising organisational standards. - Exceptional written and verbal communication, influence and leadership skills. - A bachelor's degree in computer science, engineering or a related field, or equivalent practical experience. Counts as a bonus: - Cloud native, multi region systems and architecture patterns. - A history of driving engineering standards across multiple business units or product lines. - Experience with observability, platform capabilities and data architecture at scale. - Open source project leadership or significant external technical impact. - Prior experience at a high growth SaaS, communications or platform company. The day to day: setting and communicating long term architectural vision, leading cross product architecture reviews, standardising engineering practices, driving foundational technical investments, solving the hardest platform wide problems, mentoring principal and staff engineers, and partnering with product, engineering and executive leaders on strategic direction. Experience: the posting states 15+ years explicitly. This is genuinely a senior role and the number is not padding. Location and travel: remote within India, restricted to Karnataka, Telangana, Maharashtra, Delhi and Tamil Nadu. Occasional travel for project or team meetings. Who should apply: a principal or staff engineer with well over a decade of distributed systems work who wants architecture scope across an entire company and does not want to move into management to get it. If you are earlier in your career, the other two Twilio roles in today's list sit far lower.
What the posting asks for: - 15+ years with big data technologies such as Apache Spark, Kafka, cloud native services and data lakes, in a customer facing post sales, technical architecture or consulting role. - 6+ years working on big data architectures independently. - 2+ years on AI based implementations including RAG, MCP and context engineering. - Strong experience within the Databricks ecosystem. - Comfortable writing code in either Python or Scala. - Experience across cloud platforms: GCP, AWS or Azure. - Documentation and whiteboarding skills. - Excellent problem solving and critical thinking, turning business problems into reliable technical products. - Strong stakeholder management, working with both technical people and domain experts. The day to day: collaborating on customer big data projects, creating reference architectures and how to guides, building production ready tooling, advising strategic customers on transformational initiatives including third party migrations, providing architecture and design expertise, partnering with Engineering and Customer Support to feed issues back into the product, and running several diverse client projects at once while managing risk and building trust. Experience: the posting states 15+ years as the headline requirement. Read the three numbers as a stack rather than alternatives: 15+ years overall in a customer facing big data role, 6+ years on big data architectures independently, and 2+ years specifically on AI implementations. The AI requirement is the newest and probably the one most people will fail, not the 15. Location: remote within India. This is one of very few remote senior data roles on the board today. Who should apply: a senior data architect or consultant who genuinely likes customer facing delivery. If you want to build product rather than deliver projects, this is the wrong side of Databricks. Note also that the AI expectation is concrete, not decorative: they want RAG and MCP work you have actually shipped.
What the posting asks for: - 5+ years in a data engineering, data science, technical architecture or similar pre sales or consulting role. - 5+ years with big data technologies including Apache Spark, AI, data science, data engineering, Hadoop and Cassandra. - Strong consulting and customer facing experience with external clients across a variety of industry markets. - Coding experience in Python, R, Java, Apache Spark or Scala. - Experience building distributed data systems. - Solutions built on a public cloud: AWS, Azure or GCP. - Availability to travel to customers in your region. Counts as a bonus: - Databricks certification. The day to day: partnering with the sales team and giving technical leadership so customers understand how Databricks solves their problem, helping develop the book of business and define account strategies, consulting on big data architectures, implementing proofs of concept for strategic projects, validating integrations with cloud services and home grown tools, supporting fellow Solutions Architects, and promoting and recruiting contributors for Databricks backed open source projects such as Spark, Delta Lake and MLflow. Experience: the posting states 5+ years, twice, once for the pre sales or consulting side and once for big data technologies. Compare before you apply: Databricks currently has the same job title live in Delhi at 5+, Bengaluru at 8+ and Pune at 12+. The title alone tells you nothing about the bar. Location: hybrid, based in Delhi, with travel to customers in the region. Who should apply: a data engineer or data scientist who enjoys the customer conversation and wants to move into pre sales without waiting until 10 years in. Be clear eyed that this is a commercial role attached to a sales team, with a book of business and account strategy, so it is not a pure engineering job.
What the posting asks for: - 15+ years of experience in a hands on software engineering role. - A bachelor's or master's degree, preferably in computer science, or equivalent experience. - Experience building, leading and architecting production systems or features with broad impact. - Demonstrated technical leadership: leading project teams, setting technical direction and strategy, prototyping to iterate on ideas, and working across Product, Design and Operations. - Strong communication and collaboration with both technical and non technical partners, including driving initiatives across teams, departments and leadership. - A track record of levelling up the people around you. - Proven experience defining product or technical strategy and getting cross functional leaders aligned behind it. The day to day: working with other senior leaders to define long term technical strategy and architecture, establishing technical vision and leading the work to architect and launch reliable and scalable systems, giving a balanced critical view of new and existing technologies, influencing cross functional partners, leading multi team technical initiatives, aligning technical effort with business outcomes, and raising engineering quality through design and code reviews, mentorship and hands on implementation. Experience: the posting states 15+ years in a hands on software engineering role. Airbnb is explicit that this stays hands on, so it is not an architecture role that has drifted away from code. Location: remote and eligible anywhere within India. The role may include occasional work at an Airbnb office or attendance at offsites, agreed with your manager. Remote roles at this level and in payments are uncommon, which is the main reason this one is worth a look. Who should apply: a very experienced engineer who wants payments scale and cross team architectural ownership while staying an individual contributor. If you are below roughly a decade of experience this is not a stretch application, it is the wrong role, and there are lower bands elsewhere in today's list.
What the posting asks for: - A bachelor's or master's degree or equivalent in computer science or a related field. - 2 to 5 years of relevant work experience. - Proficiency in one or more general purpose programming languages: Java, C, C++, Scala, Python or C#. - Rubrik describes its engineers as self starters who manage themselves, which is worth taking at face value in a distributed systems team. Counts as a bonus: - Prior experience with C++ specifically. - Google Cloud Platform, AWS, Azure or other public cloud technologies. - Experience with two or more of: Unix or Linux environments, Windows environments, distributed systems, networking, developing large software systems, file systems, storage systems, hypervisors, databases, or security software development. The day to day: designing, developing, testing, deploying and improving the software; managing your own projects, priorities, deadlines and deliverables; identifying and fixing bottlenecks in the software stack; and diagnosing and resolving problems inside complex customer environments. Experience: the posting states 2 to 5 years, which is the real floor and ceiling. Of everything in today's edition this is the closest thing to a role a recent graduate can grow into, though it is not a fresher posting and we are not going to pretend otherwise. Location: Bengaluru. A note on the link: rubrik.com blocks automated requests, so this posting was verified live through the Greenhouse jobs API rather than by fetching the page. It was published on 23 July 2026 and is open. The link works normally in a browser. Who should apply: someone two to five years in who wants file systems, storage and distributed systems rather than application or web work. If you have C++ and Linux and you have been stuck on CRUD services, this is the kind of role that changes the shape of your career. Expect systems design and debugging to dominate the interview.
What the posting asks for: - 2 to 5 years of experience, stated plainly at the end of the posting. - Python and SQL. The posting marks both as required for this role. - Hands on experience with Windows, Linux or Mac environments. - Knowledge of at least one programming language such as PHP, Java or ASP.Net, and of the Android and iOS platforms. - The ability to diagnose and troubleshoot technical issues and give step by step technical help. - Familiarity with remote desktop applications. - Excellent problem solving and communication skills. - A good grasp of general IT terminology and concepts. The day to day: managing merchant accounts during integration, working with the product and technology teams to understand different product flows, attending meetings and calls with merchants' technical and business teams, understanding a merchant's flow and requirements and proposing a solution, researching and diagnosing integration issues through to resolution, asking targeted questions to find the root of a problem quickly, and automating the recurring problems so they stop coming back. Experience: the posting states 2 to 5 years directly. This is one of the lower bars in today's list and one of only a handful under three years. Location: Bangalore, at PhonePe's office. Benefits worth knowing, since PhonePe lists them in detail for full time employees: medical, critical illness, accident and life insurance; an employee assistance programme and an onsite medical centre; maternity, paternity, adoption and day care support; relocation and transfer support; provident fund, gratuity, NPS and leave encashment; and higher education assistance. Who should apply: someone with two to five years who likes solving other people's integration problems and wants fintech scale on their CV. Be honest with yourself about the customer facing half: a large share of this job is calls with merchants, not heads down coding. If you want pure backend work, PhonePe's engineering roles are a different queue.
What the posting asks for: - Up to 5 years of experience building end to end applications. Read that carefully: it is an upper bound, not a minimum, which is why this role is open to people early in their careers. - A strong understanding of AI and machine learning fundamentals: NLP, LLMs, embeddings and prompt engineering. - Proficiency in Python and working with REST or GraphQL APIs. - Experience with prototyping frameworks such as Flask, FastAPI or Streamlit. - Familiarity with go to market systems such as Salesforce, HubSpot or Marketo, or BI tools such as Tableau or Looker. - Strong problem solving skills and the ability to prototype quickly. Abilities the posting calls out separately: - Turning messy go to market data into usable inputs for AI models. - Mapping AI outputs back into real workflows and processes. - Explaining technical solutions clearly to non technical people. - Balancing fast experimentation against reliability and compliance. The day to day: building internal applications on LLMs and AI APIs such as OpenAI and Anthropic, integrating AI into go to market tools, writing scripts and automations for data enrichment and reporting, rapidly testing new models and APIs and building MVPs, documenting performance and accuracy for each use case, working with Marketing, Sales and BizOps to find their pain points, running demos and training for internal users, and maintaining what you deploy. How success is measured, which the posting states unusually clearly: two or three working AI prototypes that go to market teams actively use, at least two workflows automated or optimised, documentation good enough to make the work transferable, and measurable gains in productivity. Experience: up to 5 years, with no minimum stated anywhere in the posting. Location: Bangalore. Who should apply: anyone from roughly zero to five years who can actually build with LLM APIs and wants a role where shipping a working prototype counts more than pedigree. The honest caveat is that these are internal tools for sales and marketing teams, not customer facing product engineering, so weigh that against the low bar to entry.
What the posting asks for: - 2 to 6 years of experience in cyber security, pre sales or consulting. Partner or channel experience is preferred but not required. - A strong understanding of cyber security fundamentals: web, cloud, SIEM, IDS and IPS, SOAR, email security, and threat intelligence or dark web work. - Familiarity with the cyber security ecosystem and how tools fit together in a SOC, across small, medium and large enterprises. - The ability to deliver demos and proofs of concept and explain solutions clearly. - Strong communication for both technical and business audiences, and good presentation skills. - A self driven, proactive approach. - Comfort working across sales, product, research and marketing. Counts as a bonus: - Certifications such as CompTIA Security+ or CISSP. The day to day: prospecting, onboarding and managing partner companies and helping them generate leads, training partners to understand and position the product, managing RFP and RFI responses and writing solution documents and sales proposals, running product demos, proofs of concept and customer presentations, working with sales teams and partners to close deals, organising workshops and webinars, sharing research and threat intelligence with partners, and representing partner feedback back inside CloudSEK. Experience: the posting states 2 to 6 years. That band is wide on purpose and the lower end is real. Location: Bengaluru, with travel as required to meet partners and customers. CloudSEK lists flexible working hours and food at the office. Company context worth knowing: founded 2015, headquartered in Singapore, Series A of 7 million dollars in 2021 led by MassMutual Ventures, and 19 million dollars raised in 2025 led by Tenacity Ventures and Commvault. It won the NASSCOM DSCI Security Product Company of the Year award in 2020. Who should apply: someone with a security background who is good in front of people and wants the commercial side without leaving the technology behind. This is a customer facing and partner facing job, so if you want to be heads down in a SOC, it is not for you.
What the posting asks for: - 3+ years of hands on experience in applied machine learning and data science, with a master's or PhD in computer science, machine learning, data science, statistics or a related field, or appropriate experience in place of the degree. - A strong background in machine learning, deep learning and NLP, with proven experience training and fine tuning large scale models such as LLMs, transformers and diffusion models. - Hands on expertise with parameter efficient fine tuning: LoRA, prefix tuning, adapters and quantization aware training. - Proficiency in PyTorch, TensorFlow and the Hugging Face ecosystem. - A basic understanding of MLOps: experiment tracking, model versioning, CI and CD for ML pipelines, and production deployment. - Experience with large datasets, feature engineering and data pipelines using Spark, Databricks or cloud native ML services such as AWS SageMaker, GCP Vertex AI or Azure ML. - Knowledge of GPU and TPU optimisation, mixed precision training and scaling ML workloads. - Excellent communication, including explaining complex ML concepts to non technical audiences. Marked mandatory in the posting: - Demonstrated success adapting foundation models to domain specific applications through fine tuning or transfer learning. - A strong ability to design, evaluate and improve models using robust validation strategies, bias and fairness checks, and performance optimisation. Counts as a bonus: - Distributed training frameworks such as DeepSpeed, PyTorch Lightning or Ray. - Proven ability to mentor junior applied scientists and ML engineers. Experience: the posting states 3+ years. Note the degree expectation is unusually explicit here, and the two mandatory skills are about fine tuning and evaluation rather than years served. Location: Bengaluru. CommerceIQ is headquartered in Mountain View with teams across the US, India, Canada and the UK. Who should apply: someone three or more years into applied ML who has actually fine tuned models rather than only called APIs. If your experience is dashboards and reporting, the mandatory requirements will screen you out, and MongoDB's data analyst role in today's list is a better fit.
What the posting asks for, at 3+ years of experience: - Knowledge of client server architectures and network design. - Solid knowledge of Cisco IOS and NxOS and other network operating systems. - Routing protocols including static routing, BGP and OSPF. - NAT, PAT and PBR. - Strong knowledge of L2 protocols. - WAN, LAN and data centre network architectures. - Network design, network operation or network automation. - Multicast configuration (PIM, IGMP). - Firewall and VPN technology including site to site VPN and GRE. - Knowledge of Unix or Linux. - Knowledge of data centre installation and cabling standards. Counts as a bonus: - Basic scripting, for example Python. - CCNA or higher. - Systems administration experience. The day to day: working with traders to add or change network connectivity to financial exchanges, troubleshooting and analysing network performance problems, helping design networks for new offices and data centres, finding low latency solutions in existing networks, supporting production, office and end user environments, performing market connectivity tests and circuit migrations, assisting with data centre migrations, liaising with third parties over communication lines and data centre infrastructure, and coordinating with remote hands technicians globally. Experience: the posting states the ideal candidate has 3+ years, and the skill list that follows is what those years should contain. Location: Gurugram, in office. Graviton describes cubicle free offices and a non hierarchical culture. Benefits listed in the posting: competitive compensation, an annual international team outing, fully covered commuting expenses, best in class health insurance, catered breakfast and lunch, four weeks of annual leave plus market holidays, gym and sports club memberships, and regular social events. Who should apply: a network engineer around three years in who wants low latency and exchange connectivity work rather than a corporate IT network. Trading firms pay well and expect precision, and the feedback loop when something is slow is immediate.
What the posting asks for: - 3+ years of software development experience in fast paced environments and modern stacks. - A strong technical foundation across any of frontend, backend, cloud, AI and ML, or DevOps. The posting names React, Angular, Node, Spring Boot, AWS, Jenkins and generative AI as examples. - A strategic but hands on product thinker, able to drive execution from concept to delivery. - Skill at working closely with engineers, speaking their language, and turning complex technical problems into clear product direction. - Comfort with tools such as GitHub, JIRA, Slack and analytics platforms. Counts as a bonus: - Contributions to open source. - Exposure to open source communities and other developer ecosystems. - Familiarity with AI driven workflows for scaling products. The day to day: building and managing a global network of experts who create coding challenges, owning the product roadmap for the coding challenge platform and content ecosystem, building tools that scale content delivery and support emerging technologies, partnering with customers to understand their workflows, using data and automation and AI to streamline content creation and review, and making sure everything shipped holds up on fairness, validity and developer experience. HackerRank says you will thrive here if you are a builder who likes creating scalable systems from scratch, are not slowed down by ambiguity, care about developer experience, and are energised by collaboration. Experience: the posting states 3+ years of software development experience. Location: hybrid in Bangalore, so factor in office days. Company context: HackerRank is used by over 2,500 companies including NVIDIA, Amazon and Microsoft, and positions itself around skills rather than pedigree. Who should apply: an engineer around three years in who is drawn to product and content work and wants ownership of a platform millions of developers touch. The honest caveat is that this is not a coding heavy role: the technical foundation is there so you can direct the product credibly, and the day to day is roadmap, tooling and expert network management.
What the posting asks for: - A BS or MS in computer science or a closely related technical field, or equivalent demonstrated experience. - 3+ years building ML training infrastructure or large scale distributed systems. The posting adds that exceptional early career candidates with a strong systems background will be considered, which is worth noting if you are under three years. - Hands on experience training large models with distributed training frameworks: Megatron LM, DeepSpeed, FSDP, NeMo or equivalent. The posting says you should have been on call for a real pretraining run. - Deep working knowledge of GPU architecture, the CUDA programming model, and profiling tools such as Nsight and the PyTorch profiler. - Strong PyTorch internals knowledge, comfortable reading and modifying low level training code rather than only using high level APIs. - Meaningful open source contributions in the training infrastructure ecosystem: Megatron, DeepSpeed, PyTorch, vLLM, Triton, NCCL or similar. Counts as a bonus: - Custom CUDA or Triton kernel development with measurable wins on real workloads. - Direct experience training models at 10B+ parameters or on 1000+ GPU clusters. - Cluster orchestration and job scheduling at scale (Slurm, Kubernetes). - Mixed precision (BF16, FP8), quantization aware training or similar numerical work in production runs. - First author papers or technical reports on training systems, scaling or model efficiency. The day to day: building and pushing the limits of the distributed training stack across large GPU clusters, designing parallelism strategies and reasoning about which combinations suit which architectures and scales, profiling and optimising end to end throughput including kernel performance, communication overlap, memory layout, checkpointing and data loading, writing and tuning custom GPU kernels, owning the reliability of long running jobs through fault tolerance and checkpoint integrity and deterministic restarts, and partnering with researchers and the data team. Experience: the posting states 3+ years, with an explicit exception for exceptional early career systems engineers. Location: Bengaluru. Who should apply: a systems engineer who wants frontier model training work without leaving India. Sarvam is direct that the bar is high and the cost of mistakes is measured in weeks. If you have real distributed training experience, very few Indian employers can offer this problem.
What the posting asks for: - 5+ years building infrastructure or platform software, with a track record of systems you designed and shipped. The posting is pointed about this: services and control planes others built on, not scripts and glue. - Strong software engineering in Go or Python, with the judgement to build maintainable systems and the depth to debug them in production. - Kubernetes at the controller and internals level. You should have written operators or controllers, understand the scheduler and API machinery, and know where the abstractions leak. - Working literacy in GPU specific platform constraints: MIG and GPU sharing, gang scheduling, topology and fabric aware placement, and why training and serving contend for the same hardware. - A product mindset toward internal users, measuring the platform by adoption and self service rather than tickets closed. - The range to own a capability end to end, from design through rollout to the documentation that makes it self serve. Counts as a bonus: - Having built a serving, inference or training platform: routing, autoscaling and rollout for model endpoints at scale. - GPU scheduling systems in multi tenant production (Kueue, Volcano, Slurm, Run:ai or custom). - Multi tenant isolation (MIG, MPS, time slicing) shipped as a self service capability. - Deep Kubernetes networking: CNI internals, custom network components, or RDMA and SR-IOV in pods. - On premise GPU platform work, including multi vendor or Indian NCP environments. - Open source contributions to Kubernetes, scheduling or GPU platform projects. The surface area, from the posting: the serving platform control plane with routing, canary and blue green rollouts and traffic splitting; the scaling and elasticity layer for both training and serving; scheduling and orchestration with gang scheduling, priority and preemption and quota enforcement; multi tenancy, RBAC and isolation; platform networking; observability and cost tooling; the storage and data path; developer experience through CLI, SDK and APIs; and provisioning through Terraform, Crossplane or operators. You would take one capability and build it end to end rather than own all of it at once. Experience: the posting states 5+ years. Location: Bengaluru. Who should apply: a platform engineer who has built control planes rather than maintained them, and who wants GPU scale problems. If your Kubernetes experience is writing manifests rather than controllers, the bar here is above you.
What the posting asks for: - A bachelor's degree in computer science, engineering or a related technical field. - 3+ years in conversational AI, solution engineering, system integration, or delivering AI and LLM based applications in customer environments. - Strong ability to lead customer facing discussions, from deep technical troubleshooting to weekly project demos, and to explain complex concepts to non technical audiences. - Strong hands on skills in prompt design, workflow building and API integration (SIP, Twilio, Amazon Connect and similar). - Familiarity with LLMs (GPT, Claude, Gemini), vector databases, and orchestration frameworks such as LangChain and LlamaIndex. - Working knowledge of retrieval augmented generation: concepts, implementation patterns and performance optimisation. - Programming experience in Python, JavaScript or similar for scripting and integrations. - A strong problem solving mindset, finding workarounds and adapting to each customer's ecosystem. Counts as a bonus: - Integration platforms such as n8n or Zapier, and proficiency in API integration and data flow management. - Familiarity with telephony or voice systems (SIP, CCaaS, PSTN). The day to day: owning AI agent implementation including prompt design, workflow configuration, integrations, telephony setup and evaluation frameworks; acting as the primary technical partner for customers through demos and feedback; configuring API integrations with authentication, data mapping and error handling; setting up SIP, CCaaS and PSTN routing and troubleshooting call quality; refining prompts and monitoring performance against automation and containment targets; and escalating platform gaps to product and engineering. Experience: the posting states 3+ years, and accepts several entry paths into that (conversational AI, solution engineering, system integration or software engineering with AI delivery). Location: Bengaluru. Benefits listed: medical insurance for self and family with free online doctor consultations, accident and group term life insurance, privilege and sick leave, parental leave, an annual learning and development allowance, and flexible tax benefits including meal cards. Who should apply: someone three or more years in who wants applied LLM work with a real deployment target and does not mind that the customer is in the room. If you want to train models, this is the wrong role and Sarvam's postings in today's list are the right ones.
What the posting asks for: - A bachelor's degree, with a technical major such as engineering preferred. An advanced degree is a plus. - 4+ years of experience in a similar role. - A solid technical background with a demonstrable understanding of AI and machine learning. - SaaS experience, which the posting marks as essential. - Experience with tools such as Zendesk, Confluence and JIRA. - Excellent client facing and internal communication skills. - Excellent written and verbal English. Counts as an advantage: - Python or other scripting experience. The day to day: front ending all customer reported issues, reviewing and troubleshooting them within the agreed SLA, managing customer expectations as the point of contact for service issues, proactively diagnosing and analysing problems on the platform, researching alternative solutions and workarounds, escalating internally and owning issues through to resolution, running regular tool upgrades and monitoring the platform, documenting issues and solutions into the knowledge base including SOPs and service notes and recorded videos, and becoming a subject matter expert on the platform. Experience: the posting states 4+ years in a similar role. Location: Bengaluru. What the posting offers beyond the work, in its own words: hands on exposure to real technical problems, a contribution to pre release testing and product quality, ownership, and compensation and benefits closer to a larger established company than the stage would suggest. Benefits listed include medical insurance for self and family with free online doctor consultations, accident and group term life cover, privilege and sick leave, parental leave, an annual learning and development allowance, and flexible tax benefits. Who should apply: a support engineer with four or more years on a SaaS product who wants to move towards AI products and eventually towards solutions or product roles. Readers asked for customer facing technical roles by name, and this is one of the more technical ones in that group.
What the posting asks for: - 3 to 5 years of hands on experience with IAM technologies and solutions. The header states the band as 3 to 6 years, and the posting adds that senior level candidates with broader security expertise will also be considered. - Demonstrated expertise in Microsoft Entra ID, including administration and configuration. - A solid understanding of AWS IAM: identity federation, cross account access and policy management. - Experience with at least one privileged access management solution: Delinea Secret Server, BeyondTrust, CyberArk or similar. - Strong understanding of authentication and authorisation protocols: OAuth, SAML, LDAP and Kerberos. - Knowledge of compliance frameworks: Zero Trust, NIST, SOC 2 and ISO 27001. - Excellent communication and documentation skills. Counts as a bonus: - SC-300 (Microsoft Certified Identity and Access Administrator Associate) or similar. - Experience designing and securing AI agent architectures and autonomous workflows, and hands on work with Copilot Studio agent security. - Knowledge of Model Context Protocol and agent to service authentication patterns. - RBAC model design across complex application ecosystems. - Automating provisioning and deprovisioning with Okta, ServiceNow or Microsoft Identity Manager. - Multi cloud experience (Azure, AWS, GCP), Zero Trust architecture, scripting in PowerShell, Python or Bash, and identity first incident response. The day to day: designing and maintaining identity governance in Entra ID including provisioning, authentication policies and conditional access; managing AWS IAM policies and roles across accounts on least privilege; running PAM to monitor and audit privileged activity; configuring MFA, SSO and federation across hybrid environments; running security audits and access reviews; integrating IAM with enterprise and SaaS applications; managing access for AI agents including scope limits, token management and service principal governance; designing RBAC models; automating provisioning and deprovisioning; and responding to identity compromise incidents. Experience: the posting gives 3 to 6 years in the header and 3 to 5 years in the required qualifications. We have published the wider band because the posting also invites more senior applicants. Location: Bengaluru. Who should apply: an IAM or cloud security engineer around three to six years in. The AI agent identity work is the differentiator: it is early enough that few candidates will have it, so a strong IAM background plus genuine curiosity about agent authentication is likely to be competitive.
What the posting asks for: - 4+ years, stated in the header, with total industry experience of around 4 to 7 years stated in the body. - A BTech, MTech or MS in computer science or a related field from a reputed university. - Programming experience in Python, Ruby, Perl or equivalent, which the posting marks as a must. - Good knowledge and experience of a configuration management tool such as Ansible. - Good knowledge and experience of provisioning tools such as Terraform. - Good knowledge and experience with AWS. - Experience setting up CI and CD pipelines. - Experience, in an individual capacity, managing multiple live SaaS applications with high volume, high load, low latency and 24x7 availability. - Experience setting up web servers such as Apache, application servers such as Tomcat or WebSphere, and both relational and NoSQL databases. - Good knowledge of UNIX and Linux administration tools. - Good knowledge of security best practices and tools such as firewalls and VPNs. - Good knowledge of networking concepts. - The ability to troubleshoot quickly. The day to day: writing scripts to build the infrastructure that keeps Netradyne's services available 24x7, setting up monitoring and alerting, troubleshooting issues reported across multiple environments, and triaging production issues with timely responses to customers. Experience: the posting states 4+ years in its header and around 4 to 7 years in the body, so we published the band. Location and work model, both stated explicitly in the posting: on site, five days a week in the office, at HM Tech Park in Whitefield, Bangalore, on a general shift. If you are looking for remote or hybrid, this one is neither, and today's list has nine remote roles instead. Company context: Netradyne is headquartered in San Diego with offices in San Francisco, Nashville, the UK and Bangalore, was founded in 2015, and reports growth exceeding four times year over year. Who should apply: a DevOps or SRE engineer with four to seven years who has personally carried production SaaS availability and lives near enough to Whitefield for a five day office week.
Mandatory skills from the posting: - Strong computer science fundamentals across data structures, algorithms and system design. - Deep hands on backend experience with Java and Spring Boot. - Strong grounding in distributed systems concepts: consistency, durability, retries, idempotency, backpressure, partitioning and resilience. - Practical experience with Kafka, Kinesis, Pulsar or similar. - Experience operating production systems, including on call, incidents and postmortems. - Excellent communication and technical leadership. Preferred: - Experience building high throughput ingestion or streaming systems. - Exposure to compliance heavy or audit driven domains such as transportation, fintech or healthcare. - Experience with edge or intermittently connected devices. - Hands on work with observability stacks. - Prior experience with ELD, HOS or telematics. The day to day, grouped as the posting groups it. Architecture and technical ownership: owning the architecture, design and evolution of platform services, driving system design for large cross service features from ingestion to downstream consumers, and defining clean service boundaries, APIs and data contracts. Platform and systems development: designing scalable high throughput ingestion pipelines for logs, telematics and event data, building streaming and batch workflows, translating regulatory requirements into system guardrails, and ensuring correctness, ordering, idempotency and fault tolerance. Reliability and observability: defining and upholding SLOs for latency, availability and data accuracy, championing logging, monitoring, tracing and alerting, and designing for backpressure, graceful degradation and recovery. Data modelling and storage: designing data models and partitioning strategies for hot and cold data and selecting between SQL, NoSQL, time series and object storage on scale, performance and cost. Plus cross team collaboration, design reviews and RFCs, and mentoring engineers. Experience: the posting states 6+ years in its header. Staff here is a senior individual contributor role with mentoring attached, not a management position. Location and work model: on site five days a week at HM Tech Park, Whitefield, Bangalore, general shift. Who should apply: a backend engineer with six or more years in Java who wants genuine scale and ownership of a domain rather than a feature team. The five day office requirement is the main thing to weigh.
What the posting asks for: - 6+ years of experience building and operating distributed systems, with proficiency in Python, Go or a similar language. - A strong background in software development and operating distributed systems. - Experience operating Kubernetes in production and debugging below the abstraction layer, including scheduling, cluster networking and node level issues. - Expertise in cloud infrastructure platforms: AWS, Google Cloud or Azure. - A strong understanding of Linux internals and networking concepts such as TCP/IP, DNS, TLS and routing. - A customer focused mindset and strong technical communication. - A strong bias for efficient processes, operational simplicity and automation over manual work. Counts as a bonus: - Kubernetes networking such as Istio or Cilium, service mesh or edge load balancing in production. - Secure multi tenant runtime environments at scale. - Multi cloud infrastructure management. - Virtualisation or workload isolation technologies. The day to day: operating and improving the multi tenant Kubernetes infrastructure that runs customer workloads, building for reliability so services and infrastructure are available, resilient, fault tolerant and self healing, identifying and configuring the key metrics that detect incidents and quantify service health and performance, taking part in a 24/7 on call rotation to resolve platform infrastructure issues, and mentoring early career SREs while shaping the team's operational practices. Experience: the posting states 6+ years. On call: a 24/7 rotation is stated explicitly in the posting. Factor that in rather than discovering it at offer stage. Location: Gurugram, hybrid. MongoDB states it wants candidates based in Gurugram for this model. Who should apply: an SRE with six or more years who wants Kubernetes at multi tenant scale and is comfortable being early on a platform team, which means writing the operational practices rather than following them. If you would rather build the platform than run it, the Senior Software Engineer role on the same team is in today's list.
What the posting asks for: - A bachelor's degree in computer science, information technology, business or a related technical discipline. - 4 to 8 years of progressive, deep technical experience in IT infrastructure, system engineering and workplace operations. - Subject matter expertise in Jamf Pro, Apple Business Manager and corporate device enrolment profiles. Active Jamf certifications (200, 300 or higher) are highly preferred. - Master level administrative knowledge of corporate Google Workspace and Microsoft 365. - Deep technical understanding of IDaaS, single sign on integrations, SAML and OIDC protocols, and lifecycle provisioning through Okta or Azure AD. - Exceptional troubleshooting on modern macOS and Windows, with the ability to write Bash and PowerShell scripts to automate repetitive work. - A proactive, consultative approach, with the presence to mentor junior peers and explain complex systems to non technical stakeholders. The day to day: acting as the subject matter expert for internal infrastructure and handling advanced L3 escalations and complex architectural challenges, administering and tuning Google Workspace and Microsoft 365 at global configuration level, owning and scaling endpoint device management as the technical authority for Jamf Pro and Intune, designing and deploying automated identity provisioning and access governance integrations with Okta and Entra ID, leading user lifecycle automation for onboarding and offboarding and role changes, partnering with information security on endpoint compliance and threat isolation and conditional access and data classification, writing technical runbooks and SOPs to upskill junior helpdesk engineers, and driving automation with scripting and cloud platforms. Experience: the posting states 4 to 8 years. Location: Pune, on Mindtickle's growing infrastructure team. Company context: Mindtickle is recognised as a market leader by industry analysts, won an AI Breakthrough award for AI based sales solution of the year, and holds a Gold Stevie award for sales and customer service. Who should apply: an IT infrastructure engineer four to eight years in who has outgrown a helpdesk queue and wants ownership of endpoint and identity platforms globally. This is a good fit if you enjoy automation and being the last escalation, and a poor fit if you are aiming at product engineering, since the customers here are Mindtickle's own employees.
What the posting asks for: - 5+ years of experience with PHP, Node.js and relational databases such as MySQL or Postgres, plus Kafka, RabbitMQ and React. - Profound experience in backend development. - Experience with object oriented programming. - Experience designing APIs. - Experience with event based distributed applications. - A focus on clean and readable code. - Source code management with Git. - The ability to work in a team and a willingness to take part in an open feedback culture. The day to day: working with other developers to align on project goals, architecture and delivery timelines; implementing and maintaining scalable software in PHP while balancing technical excellence against pragmatic delivery; using GitOps, Kubernetes and related tools to streamline deployment and infrastructure management; and taking part in architecture discussions, bringing new ideas and constructively challenging others. You would report to a Software Engineering Manager. Experience: the posting states 5+ years, and lists the specific technologies inside that same requirement rather than separately, so the years are expected to include PHP and Node.js. Location: Bangalore. A note on the title: the posting is listed as Software Engineer but the description opens with "As a PHP Developer", so the role is squarely backend PHP work. If PHP is not a language you want on your next CV line, that is worth knowing before you apply rather than after. Company context: ChargePoint has focused solely on electric mobility since 2007 and trades on the NYSE as CHPT. The posting frames electric vehicles as heading toward more than half of new vehicle sales by 2040. Who should apply: a backend engineer with five or more years in PHP and Node who wants scale and a sector with a long runway. Charging networks are real infrastructure work with genuine reliability requirements, which makes this more interesting than a generic PHP posting.
What the posting asks for: - 10+ years of software engineering experience with significant exposure to distributed systems and cloud native architectures. - Strong expertise in observability: monitoring, logging, distributed tracing, telemetry pipelines and incident management. - Experience operating large scale production systems with a focus on reliability, scalability and performance. - Deep understanding of system debugging, root cause analysis, performance optimisation and production operations. - Strong programming experience in one or more of Go, Java, Python, Node.js or similar. - Experience with observability technologies such as OpenTelemetry, Prometheus, Grafana, Elasticsearch, Datadog, New Relic, Splunk or Honeycomb. - The ability to influence technical direction across teams without direct authority. - Strong communication and a data driven approach. Counts as a bonus: - Building internal developer platforms or observability platforms at scale. - Exposure to AIOps, intelligent alerting, anomaly detection or AI powered operational tooling. - Driving reliability initiatives across multiple engineering organisations. - A background in SRE, platform engineering, infrastructure engineering or developer productivity. The day to day: driving the technical vision and architecture for Postman's observability platform, designing scalable solutions for metrics, logging, tracing, alerting and operational analytics, investigating complex production issues and driving long term corrective action, partnering with engineering teams on reliability and operational maturity, establishing observability standards and instrumentation frameworks, building tooling and automation for faster incident detection and resolution, using telemetry to find performance bottlenecks and capacity risks, and mentoring senior engineers. Experience: the posting states 10+ years. This is the clearest title mismatch in today's list: the role is advertised as Senior Engineer, but the opportunity section says "We are looking for a Staff Engineer" and the requirement is 10+ years. Do not rule yourself in or out on the title. Location and office days, stated explicitly: Postman values in person collaboration. Bangalore based employees currently work in the office three days a week and will move to five days a week by the end of the year. That is a material change and worth weighing now rather than later. Who should apply: an experienced platform, SRE or infrastructure engineer who likes diagnosis and wants company wide scope. If you are a senior engineer at six or seven years, the title will tempt you but the stated bar will not stretch that far.
Added July 23, 2026
What the posting asks for: - About 1 year of experience handling cases in compliance, fraud, risk or trust and safety (the role states 1 to 3 years and welcomes people early in their careers). - Fluent written and spoken English, since almost all of the work is written customer contact. - A habit of writing clear internal and external documentation. - Comfort with critical thinking to spot and stop fraudulent activity. The day to day: you respond to customers over email, chat and calls, guide them through compliance and account verification, evaluate alternatives when something is blocked, and resolve account suspensions. You file clean internal reports and add to the knowledge base as you go. Location and hours: fully remote within India. This is a 24/7 team, so expect a rotating shift schedule that can include one or both weekend days. Read the shift terms before you apply. Honest read: one of the few genuinely entry friendly, fully remote roles on this list. It is customer facing support rather than software development, so pick it if you like the investigative, people facing side of a technical product.
What the posting asks for: - 3+ years of hands on Salesforce development with Apex, Lightning Web Components (LWC) and SOQL. - Experience with Apex controllers, Apex web services, Apex callouts and integration design. - The judgement to understand the underlying business problem, weigh solution alternatives, and balance speed against quality. - Comfort managing large volumes of data and building reportable, intuitive systems for non technical end users. The day to day: you evolve a Salesforce data model that stays scalable and reportable, build custom functionality with Apex and LWC, take part in technical analysis and integration design with architects, review incoming code, and refactor the existing codebase for maintainability. Location: fully remote within India. Honest read: this is a software development role, but it lives on the sales systems side of the house. If you are a Salesforce engineer who wants to work closer to the business and own more than tickets, it fits. If you want product engineering away from CRM, it will not.
What the posting asks for: - Overall 3+ years of experience, with a deep understanding of email infrastructure and deliverability. - Strong technical troubleshooting plus the diplomacy to handle customers whose issues carry costly, far reaching consequences. - Ability to read APIs and SDKs well enough to act as a subject matter expert. - Comfort filing reproducible bug reports (JIRA) and collaborating with product and engineering over Slack. The day to day: you resolve customer issues over the support channel, feed customer signal back to product and engineering, work with developers and architects on complex problems, and contribute to internal and external documentation. Location and hours: remote within India, supporting EMEA. Current shift is 12pm to 9pm or 1pm to 10pm IST, on a five day roster (Mon to Fri, Tue to Sat, or Sun to Thu) that can include weekend days. Confirm the shift before applying. Honest read: a remote, mid level support engineering role for someone who already knows email or messaging infrastructure. The shift timing is the real trade off, so weigh it honestly.
What the posting asks for: - 8+ years writing production grade code, with real experience building and operating high scale distributed systems (several thousand events per second and processing engines handling 1M+ events per second). - A Bachelor's or Master's in Computer Science, Engineering or a related field. - Depth in designing for high availability, throughput and eventual consistency, plus reliability and security of the platform. - The ability to act as a team tech lead and mentor other engineers on architecture. The day to day: you design and ship high scale routing for the Segment data pipelines, build and optimise globally available distributed systems, partner with product and other Segment teams, and support platform reliability and security. Location: fully remote within India. Honest read: a genuine Staff level distributed systems role. Twilio notes it welcomes non traditional paths, but the 8+ year bar and the 1M events per second scale are real. Best for engineers who have operated data platforms at scale and want a remote seat with technical leadership.
GitLab does not state a years requirement anywhere in this posting, so we have left the experience figure blank rather than invent one. Judge fit on the substance below. What the posting asks for: - Strong backend engineering in Go, applied to high throughput, multi component systems. - Experience with core system design: ingestion, transport, replication, query serving and query oriented storage. - Familiarity with the surrounding stack: ClickHouse or similar column stores, NATS or comparable messaging, gRPC, and deployment across multiple environments. - Comfort owning reliability, operability and production readiness end to end. The day to day: you design and evolve Go backend services for the Data Insights Platform and Siphon, own significant parts of the architecture including the gRPC integration with GitLab Rails, and drive safe rollout across SaaS, Dedicated and Self Managed environments. Location and ways of working: GitLab is all remote and asynchronous. The posting is tagged Bangalore, India, which in GitLab terms means remote within India. Some GitLab roles carry location based eligibility, so confirm yours. Honest read: a strong remote backend role for a Go engineer who likes data infrastructure. No stated years, so do not rule yourself out on seniority alone.
GitLab does not state a years requirement in this posting, so the experience figure is left blank rather than guessed. This is a Staff level role, so expect the bar to be high. What the posting asks for: - Strong distributed systems instincts: durability, tenant isolation and horizontal scalability, and the judgement to tell a design that is durable from one that only looks durable under light load. - Go backend depth and the ability to decompose complex architecture into shippable work for a team. - Experience owning reliability end to end and migrating production workloads off legacy systems without disruption. The day to day: you lead technical execution on the consolidated messaging and event platform, solve high complexity problems, set and hold the technical bar, and own the migration of existing production traffic off Sidekiq and the legacy event bus. Location and ways of working: all remote and asynchronous. Tagged Bangalore, India, meaning remote within India in GitLab's model. Some roles carry location based eligibility, so confirm yours. Honest read: a rare remote, Staff level distributed systems seat with real architectural ownership. Narrow pool, since durable multi tenant messaging is a specific skill, which cuts both ways.
GitLab does not publish a years figure for this role, so we have left it blank. It is pitched at Senior level, hands on. What the posting asks for: - Strong engineering skills combined with systems thinking and genuine business understanding. - Practical fluency with LLM and agent based systems, and the judgement to know when AI is not the right tool. - The ability to own initiatives end to end, from stakeholder discovery and design through deployment and iteration. - Comfort delivering working prototypes fast and measuring real outcomes. The day to day: you diagnose business problems before building, map workflows and constraints, and ship AI powered solutions into Sales, Marketing and Customer Support systems. You take ownership from discovery to production and iterate on what the data shows. Location and ways of working: remote within India, asynchronous, reporting to the Director, Enterprise AI. Some GitLab roles carry location based eligibility, so confirm yours. Honest read: an applied, internal facing AI engineering role for someone who leads with the problem, not the model. If you want frontier model research this is not it. If you want to ship AI that changes how a company works, it is a strong remote option.
What the posting asks for: - 3+ years building large scale data systems (petabyte scale processing, distributed data pipelines or comparable). Exceptional early career candidates with a strong systems background will also be considered. - A BS or MS in Computer Science or a closely related field, or equivalent demonstrated experience. - Hands on experience with data curation and filtering for LLM training, and the ability to defend the choices in a corpus you helped build. - Depth in distributed data frameworks (Spark, Ray, Beam, Dask or equivalent) and the storage underneath, plus strong Python and comfort with tokenization, sharding, packing and IO tradeoffs. Nice to have: experience with large open pretraining corpora, model based quality classifiers, contamination detection, or data attribution research. The day to day: you build ingestion, parsing, filtering, dedup, tokenization and packing pipelines at petabyte scale, improve quality filtering, own mixture and curriculum design with the research team, and build tooling so researchers can slice and debug the data. Location: Bengaluru. Honest read: a serious data engineering role at a pretraining lab. The 3+ years is a soft floor, so strong systems focused early career engineers should still consider it.
What the posting asks for: - 3 to 5 years in frontend engineering, shipping production web applications. - Strong React and TypeScript (hooks, context, custom abstractions, performance optimisation), described as non negotiable. - Hands on Next.js with the App Router, server components, API routes and middleware, also non negotiable. - Experience with state management at scale (React Query, Redux, Zustand or similar). The day to day: you build Studio's core media workflows (video and voice dubbing, voice cloning), own a visual node based pipeline editor, implement real time job progress tracking, build in browser recording and media playback, work in a Next.js monorepo, extend a shared design system, and instrument features with analytics and error monitoring. Location: Bengaluru, high ownership role on a small team. Honest read: an unusually substantial frontend role, closer to product engineering than UI work, at an Indian AI company solving hard media problems. If you want deep React and Next.js work with real product impact, it fits well.
What the posting asks for: - 5 to 10 years building production backend systems, with deep Python and FastAPI (or Golang). - A track record of full stack ownership: designing systems end to end, making the tradeoffs, and operating them in production. - Hands on workflow orchestration at scale, ideally Temporal. - Strong PostgreSQL and Redis fundamentals (schema design, query performance, caching strategy), and experience with high scale, multi tenant, low latency distributed systems. Nice to have: building products on top of LLMs or ML systems, a telephony, VoIP or SIP background, and time at an early or growth stage startup. The day to day: you own the backend for agent, campaign and user management from data model to deployment, run workflow orchestration with Temporal, own performance and reliability at sub second SLOs, build observability and integration testing, and set a design first, documentation first culture (RFCs before code). Location: Bengaluru. Pure individual contributor Staff role, no people management. Honest read: a strong senior backend seat for someone who wants system ownership without moving into management.
What the posting asks for: - 4+ years preferred, but Sarvam hires across levels: strong AI fundamentals, range across the stack, high agency and a clear track record of shipping matter more than years. - A technical degree in Computer Science, Electrical Engineering or equivalent. - Deep, practical understanding of how LLMs and agents work in production: context engineering, memory, RAG, tool use, structured outputs and real failure modes. - Experience with agentic frameworks (LangGraph, LlamaIndex, Google ADK or equivalent) and both open and closed source models. Nice to have: deploying AI systems in regulated environments (BFSI, public sector) or with on premise and VPC deployments. The day to day: you embed with clients, scope and design end to end AI systems, build integration scripts and platform configuration, deploy into the customer environment, set up evaluations that measure whether the system works, and bring field learnings back to product and research. Location: Bengaluru, client facing engineering role. Honest read: an engineering role, not a support one, but one where half the job is with customers. It suits a high agency generalist. Because Sarvam hires across levels, do not rule yourself out on years alone.
What the posting asks for: - At least 5 years as a Machine Learning Engineer, with proven experience taking ML systems to production. - Strength across the full lifecycle: data ingestion, model development, deployment and monitoring. - Solid MLOps practice: logging, monitoring and CI/CD pipelines for distributed ML systems. - Comfort researching and rapidly prototyping emerging AI and ML frameworks, then driving full scale implementation. The day to day: you design and deploy production grade Gen AI and ML systems, implement and maintain MLOps, evaluate and prototype new frameworks, mentor junior engineers on system design, and translate business needs into technical solutions with cross functional teams. Location and ways of working: hybrid, based in Bangalore, reporting to the Sr. Manager, Engineering Strategy, Planning and Analytics. Honest read: a hands on Staff ML engineering role inside a security business, strong for someone who likes owning production ML and MLOps end to end. It is hybrid Bangalore, not remote, so factor in office days. Mentoring is expected but it is an individual contributor seat.
What the posting asks for: - 4 to 10 years of deep technical support, cloud support or escalation engineering experience. - Strong hands on troubleshooting across cloud security services, configuration, policy engines and APIs. - The ability to do detailed log, telemetry and packet level analysis, reproduce complex defects, and write engineering ready bug reports. - Willingness to own an on call rotation for the highest severity issues. Useful here: exposure to the secure use of AI models, governance of AI agents, data protection and inference security. The day to day: you resolve the highest severity escalations end to end, troubleshoot complex issues across the platform, investigate AI security scenarios, perform root cause analysis, and drive cross functional collaboration with engineering to validate fixes. Location and ways of working: hybrid, based in Bangalore (Mohali also listed), reporting to the Escalation Manager within Customer Success. Honest read: a senior, customer facing technical role that is squarely in scope for the readers who asked for escalation and customer success engineering. It manages accounts and incidents, not people. Hybrid Bangalore, with on call, so weigh both.
What the posting asks for: - 5+ years as a Software Development Engineer, with real strength in automation. - Hands on Python and the ability to design and maintain scalable automation frameworks and internal tooling. - Experience with networking concepts, since the products are network security systems. - Depth in scalability, stress and performance testing. The day to day: you design, implement and run comprehensive automated test cases for complex features, build and maintain automation frameworks that streamline the testing lifecycle, and lead performance and stress testing to find bottlenecks across web filtering, firewall, policy enforcement and CASB products. Location and ways of working: hybrid, based in Bangalore, reporting to the Sr Manager of Engineering in Cyber Security and Data Protection. Honest read: read the title carefully. This is a senior automation and quality engineering role inside a security business, not a feature development seat. If you are a strong SDET or automation engineer with Python and networking, it fits. If you want to write product features, it will not. Hybrid Bangalore, so factor in office days.
What the posting asks for: - 0 to 3 years in a technical support or customer facing technical role. Strong freshers with demonstrated technical aptitude are explicitly welcome. - A basic understanding of REST APIs: HTTP methods, status codes, and how to read a request and response. - The ability to read logs, browser developer tools and error messages to understand what happened before escalating. - Familiarity with SQL: enough to write or understand a basic query. - Comfort using AI tools to speed up investigation. The day to day: you own first response within SLA, resolve standard issues independently, triage and escalate complex tickets with full context, keep the queue healthy during your shift, maintain ticket hygiene, and contribute to the knowledge base. Location and hours: hybrid in Bangalore, on a rotational shift covering mornings, evenings and weekends for 24x7 global coverage. Honest read: a real entry level, customer facing technical role with a stated path into the next level. It is support, not development, and it involves shift work, but for someone early in their career who wants a technical foot in the door it is one of the honest 0 to 1 options here.
What the posting asks for: - 2 to 7 years in technical support or product support for a B2B SaaS platform. - Strong debugging instincts across web applications, REST APIs and third party integrations, tracing failures to root cause rather than the surface error. - Solid SQL: you write your own queries to investigate data issues and validate behaviour. - Working knowledge of SSO, SAML and OAuth flows. The day to day: you own complex escalations end to end, debug platform, API and integration failures, collaborate with engineering on confirmed bugs, lead incident management and customer facing RCAs for high severity issues, manage many open tickets without losing SLA, and turn recurring patterns into runbooks. Location and hours: hybrid in Bangalore, with a rotational on call that can include occasional late night or weekend coverage. Honest read: a mid level, customer facing technical role with real debugging depth, one of the customer success and support seats readers asked for. It is support engineering, not product development, and it carries on call, so weigh both against what you want.
What the posting asks for: - A degree in a highly analytical field such as Engineering, Mathematics or Computer Science, from a strong university. - 3+ years of experience with Python and Shell or Bash scripting. - Working knowledge of Linux and command line tools. - Strong problem solving and analytical skills, and clear communication. - Some mentorship experience guiding junior developers. The day to day: you build software tools that help quants run analysis and simulations, build scalable post trade systems that analyse statistics across all production strategies, implement tools for centrally analysing market data across exchanges, and write comprehensive C++ and Python scripts for risk attribution and performance breakdowns. Location: Gandhinagar, Gujarat. Graviton lists strong perks (covered commuting, catered meals, health insurance, international team outing). Honest read: a tools engineering role inside a quant trading firm, C++ and Python heavy and data intensive. You do not need to be a quant, but you should enjoy building infrastructure that quants use. Note the location is Gandhinagar, not one of the metros, which matters if relocation is a factor.
What the posting asks for: - 4+ years with Terraform for infrastructure as code. - 4+ years in configuration management and systems engineering supporting large scale Agile environments. - 4+ years of Linux or Windows administration, and 4+ years with Git and solid branching and merging strategy. - 2+ years hands on with AWS infrastructure and platform services, cloud automation tools (Ansible or Chef), and container orchestration (Kubernetes on EKS, ECS, Docker). Nice to have: experience across AWS, Azure and GCP. The day to day: you automate infrastructure with Terraform and CloudFormation, own the build and release cycle end to end, deploy releases and handle operations, improve the operations tooling (Jenkins, monitoring with Consul, metrics with Graphite and Grafana), migrate and retire legacy infrastructure, and set operational best practices. You work client facing, embedded with customer teams across the US and India. Location: Mumbai. Honest read: a senior, client facing DevOps role at a delivery focused firm that is honest about how agents change the work. The real floor is 4+ years across several areas, not the incidental 2+ some parsers pick up. Good for someone who wants ownership of migrations and carries delivery dates personally.
What the posting asks for: - 5+ years as an Oracle and PostgreSQL DBA and database developer. - Strong hands on experience with Oracle Database and PostgreSQL or Aurora PostgreSQL, and real Oracle to PostgreSQL migration work. - Advanced SQL and query performance tuning, plus PostgreSQL internals (indexing, statistics, execution plans). - Experience with AWS SCT and AWS DMS, and with a schema migration tool such as Flyway or Liquibase. Nice to have: AWS services (RDS, Aurora, CloudWatch, IAM), automation tools (Ansible, Chef, Puppet), IaC (Terraform, CloudFormation), and AWS Database Specialty or Solutions Architect certification. The day to day: you convert Oracle SQL and PL/SQL to PostgreSQL, remediate AWS SCT findings, manage the Flyway migration codebase, support and monitor AWS DMS through full load and CDC, tune PostgreSQL queries, and validate and reconcile data between Oracle and PostgreSQL. Location: Mumbai. Honest read: a specialist database migration role, not a general backend seat. If you have lived through heterogeneous Oracle to PostgreSQL migrations, this is squarely for you. If your database work is incidental, it will be a stretch.
What the posting asks for: - 8 to 12 years of professional experience in database architecture and migration delivery. - Hands on expertise with AWS DMS and AWS SCT for enterprise scale migrations. - Deep proficiency across Oracle, SQL Server, PostgreSQL and Aurora PostgreSQL, and a track record of heterogeneous migrations across on premises and cloud. - Skill authoring and executing migration runbooks, validation plans, cutover procedures and rollback strategies. The day to day: you lead migrations end to end (assessment, planning, schema conversion, execution, post migration validation), design and manage the DMS and SCT environments, convert Oracle PL/SQL and SQL Server T-SQL to PostgreSQL PL/pgSQL, author the cutover runbooks, drive migration testing and production readiness reviews, and provide technical leadership and governance to migration teams. Location: Mumbai. This is customer facing, enterprise migration delivery. Honest read: a senior, lead level database migration role. It carries technical leadership of teams but the core is deep hands on migration engineering, not people management. Best for a database migration specialist who wants ownership of whole enterprise programmes.
What the posting asks for: - 5+ years of hands on experience in applied machine learning and data science. - A degree in Computer Science, Machine Learning, Data Science, Statistics or a related field. - A strong background in machine learning, deep learning and NLP, with proven experience training and fine tuning large scale models (LLMs, transformers, diffusion models). - Hands on expertise with parameter efficient fine tuning (LoRA, prefix tuning, adapters, quantization aware training). - Proficiency in PyTorch, TensorFlow and the Hugging Face ecosystem, plus a basic understanding of MLOps (experiment tracking, model monitoring). Nice to have: distributed training frameworks such as DeepSpeed, PyTorch Lightning or Ray. The day to day: you build and fine tune large models for production, apply efficient fine tuning and quantization techniques, and ship AI capabilities into the workflows of large brand customers. Location: Bengaluru. Honest read: a hands on applied ML role, senior individual contributor, at a company shipping AI into enterprise commerce. Lead is a seniority marker here, not a management title. Strong for someone who wants modern model training work that reaches production.
What the posting asks for: - 5+ years in business intelligence, analytics engineering, data engineering or a similar role. - Strong SQL for data transformation, and comfort in at least one functional or object oriented language such as Python or Scala. - Expertise building reporting and data visualisation with tools like Looker, Tableau or Sigma. - Familiarity with database fundamentals (S3, Trino, Hive, Spark) and SQL performance tuning, plus experience writing data quality checks (Pydeequ, Great Expectations). The day to day: you translate business needs into data requirements, build and maintain canonical datasets and high volume ETL and ELT pipelines, lead the development of self serve data products, design metrics and dashboards, and champion high data integrity, reusability and standardisation across domains. Location: Hyderabad. Honest read: a strong, technical data role that leans analytics engineering rather than pure platform work. If you enjoy modelling data and building the datasets and tools the whole company relies on, it is a good fit. The 5+ years and SQL depth are real.
What the posting asks for: - 5 to 7 years of software engineering with a strong focus on frontend development. - Strong hands on React and TypeScript in production environments. - Experience designing and building scalable, high performance web applications, and with frontend testing frameworks such as Vitest, Jest and React Testing Library. - Working knowledge of backend systems, REST APIs and distributed systems, and comfort with backend for frontend and API layer changes. Nice to have: experience with design systems or shared component libraries. The day to day: you lead development of complex frontend features, translate ambiguous requirements into scalable solutions, own end to end delivery from design to production, drive improvements in UI architecture and performance, lead code reviews, set frontend standards, and mentor junior engineers. Location: Noida. Honest read: a senior frontend engineering role with genuine architectural ownership and a mentoring element, at a security intelligence company. It is frontend first but expects some backend fluency. Good for an experienced React engineer who wants to lead technical direction without moving into management.
What the posting asks for: - 7+ years in Linux and Unix administration, with extensive hands on experience. - Strong computer networking, including IP, iptables and IPsec. - Broad familiarity with open source technologies and tools, with an emphasis on cloud services. - Working experience with MySQL (MariaDB or Percona a plus), and coding and scripting skills, preferably Perl, Python or Golang. - Willingness to take part in the on call rotation. The day to day: you keep PhonePe's services always up and always available, apply IT operations best practices, work across a wide range of open source and cloud tooling, manage Linux networking and databases, automate with configuration management, and participate actively in on call. Location: Bangalore. Honest read: a senior, hands on SRE role at very high scale, weighted toward operating system, networking and database operations rather than software development. The 7+ year bar and the on call are real. Strong for a systems focused SRE who wants a high scale fintech environment.
What the posting asks for: - An active Elastic Certified Engineer certification (mandatory). - A minimum of 7 years as a Consulting Architect or in a senior IT role. An alternative path is accepted: at least 2 years as a Security Analyst working with SIEM tools such as Splunk, ArcSight or IBM QRadar. - Deep hands on Elastic Stack expertise: data modelling, query development and optimisation, cluster tuning and scaling. - Senior level consulting skills: workshop facilitation, requirements gathering, stakeholder communication and customer advocacy. The day to day: you deliver end to end Elastic projects for enterprise customers, run strategy, roadmap, design and sizing workshops, build proof of concepts, tune and scale clusters for fast search and analytics, and feed field learnings back to product, engaging with the sales team to scope opportunities and assess technical risk. Location and travel: based in India, with remote work plus required on site client engagement across time zones. Honest read: a senior customer facing consulting and solutions architecture role, not an internal product seat. The Elastic Certified Engineer requirement is a hard gate. Best for an experienced Elastic or security analytics specialist who likes client delivery and travel.
What the posting asks for: - 6+ years of experience in technical support, field engineering or a similar customer facing technical role. - A degree in Computer Science, Engineering (Mechanical or Electrical) or another technical field. - Strong troubleshooting and root cause analysis across software and connected hardware systems. - The ability to act as the primary technical authority and the bridge between customers, field teams and R&D. Helpful here: exposure to compliance or regulatory systems (DoT and FMCSA, ELD, Hours of Service), telematics or IoT. The day to day: you own the most challenging escalations on the ELD compliance product, ensure accurate recording of Hours of Service and Records of Duty Status data, reproduce and root cause complex issues, and work across customers, field teams and R&D to protect data integrity. Location: Bengaluru, within the Global Technical Support organisation. Honest read: a senior, customer facing technical support role with a compliance and IoT flavour, not a software development seat. The subject matter (US transport compliance) is specialised, so it suits someone who enjoys owning a complex product domain end to end. The 6+ year bar is real.
Cloudflare does not state a specific years figure in this posting, so we have left the experience number blank rather than guess. It is pitched as a senior, customer facing technical role. What the posting asks for: - A trusted technical advisor profile: someone who can own the technical relationship from discovery through adoption and expansion. - Strength across Cloudflare's portfolio: security, networking and developer platforms. - The ability to lead technical discovery, design bespoke architectures, and deliver compelling demos and proofs of concept. - Comfort operating as a quota carrying technologist within a go to market org, using AI augmented workflows to cut administrative work. The day to day: you partner with Account Executives on technical discovery, build architectures and proofs of concept, act as the continuous technical advisor through onboarding, renewal and expansion, and drive measurable business outcomes across the customer journey. Location and ways of working: fully remote within India, based in Mumbai, reporting to the Regional Customer Engineering Leader within the GTM organisation. Honest read: a pre sales and solutions engineering role, technically deep but quota carrying, so it has a commercial edge that a pure engineering seat does not. It is fully remote within India, which is its standout feature. Strong for a solutions or sales engineer who wants a remote, customer facing technical career.
Added July 22, 2026
What the posting asks for: a degree in a highly analytical field such as Engineering, Mathematics or Computer Science, and up to 2 years of experience with Python and shell or Bash scripting. You need working Linux and command line skills, hands on experience with SQL and NoSQL databases, strong problem solving and analytical ability, clear communication, and the temperament to stay calm and methodical while production is broken. Nice to have, not required: familiarity with monitoring and alerting stacks such as Prometheus, Grafana or ELK, exposure to Kafka and Redis, experience with CI/CD pipelines and deployment automation, and any prior time in a support, SRE or production engineering role. The real day to day: monitoring production services and trading systems, responding fast to alerts, incidents and outages, triaging across trading support services, databases and infrastructure, escalating to the right owners, and driving fixes to completion. You will also build automation to cut repeated manual work, improve observability by extending monitoring, logging and alerting, and maintain operational runbooks and SLO and SLA metrics. Location and setup: Gurugram, Haryana, on site. Graviton describes an open plan office with no cubicles, catered breakfast and lunch, a stocked kitchen, 6 weeks of paid vacation and an international team outing. Honest fit guidance: read the phrase "up to 2 years" as an upper bound, not a floor, which makes this reachable straight out of college if your Python, Linux and database fundamentals are solid. It suits someone who likes operational work and debugging live systems more than greenfield feature building. Trading support means production pressure and incident response are the job, not an occasional interruption. The posting does not publish an interview process.
What the posting asks for: a Bachelor's degree in computer science or a related field, proficiency in Linux and C or C++, and strong problem solving with the ability to work independently. Netradyne states the experience range as 1 to 3 years. Nice to have, not required: familiarity with Agile development methodologies and an understanding of Python. The real day to day: designing and implementing software solutions for the IoT platform, turning functional and technical requirements into detailed architecture and design, building scalable and high performing systems, architecting data driven solutions, writing documented and testable code, troubleshooting and debugging complex production issues, and applying software development best practices. Location and setup: Netradyne states this explicitly, which is unusually clear. Employment type is full time, the work model is on site, and the shift is general shift, 5 days a week. The office is HM Tech Park, Whitefield, Bangalore, and the posting notes potential for some work flexibility. Treat this as a 5 day in office role in Whitefield unless the recruiter tells you otherwise. Honest fit guidance: this is one of the few roles on today's board that a first job engineer can actually clear, but the C and C++ requirement is real and the work is embedded, not web or application development. If your experience is in Java or Python web stacks, the title will fit and the skills will not. Netradyne also publishes a recruitment fraud warning: official communication comes only from addresses ending in netradyne.com or us-greenhouse-mail.io, the company never asks for payment for equipment, and it does not use agencies that charge candidates a fee. The posting does not publish an interview process.
What the posting asks for: 1 to 3 years of L2 technical support experience with enterprise SaaS platforms in a customer facing role, AWS cloud preferred. Mindtickle also wants a track record handling technical issues in production while supporting distributed systems, experience supporting a multi tenant SaaS product including its integrations and configuration management, and hands on troubleshooting of AI powered features with the ability to separate model issues from data, configuration or system level failures. Knowledge of authentication and enterprise integrations is required, specifically SSO protocols such as SAML, OAuth 2.0 and OpenID Connect. The real day to day, in three parts. Operational support: responding quickly to customer queries, providing workarounds while permanent fixes are built, owning tickets to SLA, acting as an escalation point, and working across Product, Engineering, Quality Engineering and DevOps to kill recurring issues. Technical investigation: reproducing and debugging problems across backend services, APIs, data flows, UI behaviour and AI components, capturing browser logs, HAR files and network traces, analysing AI decision paths and validating model outputs for drift or anomalies, and running structured impact and severity analysis before escalating. The named tooling is Zipy, Datadog, SumoLogic, FullStory, Mixpanel and Metabase. Knowledge work: building runbooks, playbooks and troubleshooting guides, converting solved issues into product and documentation improvements, and running deep dive sessions and post incident walkthroughs. Automation: writing Bash, Python and SQL to automate log extraction, data analysis and issue replication, and contributing to AI assisted troubleshooting tooling. Location and setup: Pune, Maharashtra. The posting does not state office days. Honest fit guidance: this is support engineering, not product engineering, so you will be measured on resolution and SLA rather than shipped features. In exchange you get real depth in distributed systems debugging and unusually direct access to Engineering and Product. Mindtickle itself frames it as an L2 role with more influence than most. Good fit if you enjoy diagnosis and customer contact, poor fit if you want to be writing product code most of the week. The posting does not publish an interview process.
What the posting asks for: 2 to 5 years of professional software engineering experience, experience with a modern programming language such as Python, Go or Rust, excellent communication, and comfort with modern infrastructure and delivery systems including containerised applications, Kubernetes and CI/CD tooling such as Drone.io or similar. MongoDB describes the ideal candidate as collaborative, detail oriented and genuinely interested in making software usable. Nice to have, called the bonus round in the posting: experience building full stack applications from front end UIs through backend API handlers to database migrations, and knowledge of Next.js, FastAPI or React. The real day to day: building and maintaining internal tools and platforms that improve workflows and efficiency, writing clean and maintainable code to fix bugs and add features, and working with other engineers and teams to prioritise and deliver. MongoDB publishes its success measures for the role, which is rare and worth reading as the actual expectation. Within three months you should be familiar with internal platforms and workflows and contributing meaningfully to projects in flight, and should have reduced manual friction in internal processes by delivering working features or improvements. Within six months you should have implemented tooling or enhancements that measurably improve internal engineering efficiency and productivity. Location and setup: Gurugram, and the posting is explicit that MongoDB is looking for candidates based in Gurugram for its hybrid working model. Honest fit guidance: internal tooling is sometimes treated as lower status than customer facing product work, and it is worth being clear eyed that your users are colleagues rather than customers. The upside is a new team, early influence over how it works, and a short path from writing something to seeing it used. If you want to work on the MongoDB database engine, this is not that role.
What the posting asks for: 2 to 5 years as a Software Engineer or Python Developer, strong Python with the ability to pick up new frameworks and libraries quickly, hands on SQL for querying and data manipulation, experience with data visualisation and plotting tools such as Matplotlib, Seaborn or Plotly, familiarity with alerting and monitoring tools, and a solid grounding in data structures, algorithms and object oriented programming. Graviton also asks for strong analytical thinking and attention to detail. The real day to day: designing and developing efficient Python scripts for data analysis and automation, building accurate data visualisations that support decision making, implementing and maintaining alerting tools that monitor data workflows and systems, working with other teams to gather requirements, and continuously optimising data processing pipelines for scalability and performance. Location and setup: Gurugram, Haryana, on site. Graviton describes a cubicle free office and a deliberately non hierarchical culture. Published benefits are competitive compensation, 6 weeks of paid vacation, catered breakfast and lunch, a fully stocked kitchen, monthly after work parties and an international team outing. Honest fit guidance: this is a data and tooling engineering role inside a trading firm, not a quant researcher or trader seat, so do not apply expecting to build alpha models. What you get instead is a high signal engineering environment, exposure to financial market data at scale, and a bar set by a firm that says openly it insists on hiring the very best. Graviton has three separate openings on today's board (this one, HPC Engineer at 2 to 3 years, and Application Reliability Engineer at up to 2 years), all in Gurugram and all distinct teams, so compare the three before applying rather than sending the same application to each. The posting does not publish an interview process.
What the posting asks for: Netradyne states the experience range as 2 to 5 years, and separately asks for 2 to 4 years in SDET or quality engineering roles. It publishes a skills table: Python at expert level and shell scripting in Bash or Zsh at intermediate or above are required, while SQL and PostgreSQL at intermediate level and Jenkins or similar CI/CD tooling at intermediate level are listed as desired. The real day to day: designing and executing end to end test plans that validate hardware and software modules of IoT devices, including firmware behaviour, sensor integrations and communication interfaces. Developing and maintaining automated test scripts that verify device function across real operating conditions, edge cases and failure scenarios. Building tooling that simulates real world device conditions so resilience can be verified without relying solely on physical test environments. Monitoring and querying large scale device datasets and telemetry logs to detect anomalies, regressions and performance degradation. Contributing to the architecture of the in house test automation framework so it stays extensible and reusable across teams. Integrating automated tests into CI/CD pipelines for fast feedback on every build. Identifying and triaging defects with clear reproduction steps and root cause analysis. Championing quality practices including code review, coverage standards and shift left testing. You would work directly with hardware engineers, firmware developers, backend engineers and product teams, on the Engineering Quality team in Bangalore. Location and setup: Bangalore. This posting does not state office days, though Netradyne's other Bangalore openings specify on site, general shift, 5 days a week at HM Tech Park, Whitefield, so ask. Honest fit guidance: the Senior label and the 2 to 5 year range are a good illustration of why the years matter more than the title. This is hands on test engineering with real hardware in the loop, which is a different skill set from pure web QA automation. If you want to move from manual or UI testing into device and telemetry work, it is a strong bridge. The posting does not publish an interview process.
What the posting asks for: the ideal candidate has 2 to 3 years of experience, with a degree in EE, CS or CSE. Graviton adds that Bachelor's graduates will also be considered given an exceptional background and prior experience in the HPC field. Required skills are programming in Python or Bash, a good working understanding of Linux at user level, experience with large scale distributed HPC systems, and an understanding of large scale batch processing systems such as PBS Pro, Torque or Slurm along with approaches to efficient scheduling. HPC system monitoring and automation tools are preferred. The responsibilities as listed: hands on experience deploying high performance clusters, working with cluster management tools, exposure to multiprocessor and multithreading concepts, working on Linux, and handling testing, user support, troubleshooting and root cause analysis of issues. Experience with parallel filesystem environments is marked optional. Location and setup: Gurugram, on site. Published benefits are competitive compensation, an annual international team outing, fully covered commuting expenses, health insurance, catered breakfast and lunch, a stocked kitchen, 4 weeks of annual leave plus market holidays, gym and sports club memberships, and regular social events. Honest fit guidance: this is infrastructure and systems work, not trading or model development, and the day to day is closer to a research computing role at a university or national lab than to a software product team. That makes it an unusual and quite specific opening. The explicit note that strong Bachelor's graduates will be considered is worth taking seriously if you have real cluster experience from an academic or internship setting, since HPC exposure is genuinely hard to come by in India outside a handful of employers. Note this is Graviton's third open role today alongside a Python engineer role and an application reliability role. The posting does not publish an interview process.
What the posting asks for: a Bachelor's or Master's degree in Computer Science or a related field, and 3 to 6 years of Python based data or backend engineering. Required alongside that are strong programming fundamentals in data structures, algorithms and object oriented design, experience with AWS services such as Kinesis, SQS or Lambda, experience building and managing data pipelines and workflows with Airflow DAGs, a good understanding of data modelling and both relational and NoSQL databases, experience with Docker and Kubernetes, hands on GitHub and CI/CD tooling such as Jenkins, and strong Linux fundamentals and debugging skills. Preferred, not required: prior experience at a product or SaaS company, streaming and event driven architectures, exposure to NoSQL stores such as MongoDB or Cassandra, a basic understanding of ML pipelines, and familiarity with modern AI concepts such as RAG, AI agents and prompting. The real day to day: building and maintaining scalable pipelines for real time and batch processing on Kinesis and SQS based systems, developing data platforms that support ML feature generation, training and validation, optimising pipeline performance and reliability at high volume, writing backend components and services for data processing, deploying and troubleshooting production data systems, working with distributed systems in Docker and Kubernetes on EKS, partnering with Data Science and ML teams to productionise AI solutions, and following engineering practices around code quality, testing and CI/CD. The posting also lists working with AI agents to solve data engineering problems. Location and setup: Bangalore. This posting does not state office days, but Netradyne's other Bangalore roles specify on site, general shift, 5 days a week at HM Tech Park, Whitefield, so assume in office and confirm. Honest fit guidance: strong choice if you want data engineering that stays close to production ML rather than to BI and reporting, and if you are comfortable that a good share of the week is backend service work and on call style troubleshooting. Netradyne has three separate openings on today's list across different teams, so pick the one that matches rather than applying to all three.
What the posting asks for: extensive and expert programming experience in at least one general purpose language such as Java, C or C plus plus, and the ability to write maintainable, scalable, unit tested code. Also required are experience with multithreading and concurrency programming, experience building highly scalable business applications involving complex business flows and large data volumes, strong object oriented design skills with knowledge of design patterns and a genuine interest in designing clean module and class level interfaces, excellent coding ability so a design converts fluently into code, knowledge of test driven development, a good understanding of databases such as MySQL and NoSQL stores such as HBase, Elasticsearch and Aerospike, and full lifecycle development experience on Linux. PhonePe also asks for experience in a startup environment with high levels of ownership. The title states 3 to 5 years. The real day to day: building robust and scalable web based applications, building abstractions and contracts with separation of concerns at larger scope, driving problem solving for high level business and technical problems, doing high level design with guidance including functional modelling and module breakdown, making incremental architecture changes and analysing their impact, performance tuning large scale distributed systems, working closely with a Product Manager to turn features into capability views and leading execution of medium sized projects, tracking the impact of what ships and iterating, and mentoring junior engineers while breaking execution into phases to make delivery predictable. Location and setup: Pune. The posting does not state office days. Honest fit guidance: PhonePe describes a culture where you own your work end to end from day one and where teams often build frameworks from scratch, which is a real signal about pace and expectations. The payments domain means correctness and availability matter more than shipping speed, and the volumes quoted are not marketing: 330 million transactions a day is a genuinely demanding backend environment. Note this is the Pune opening, and PhonePe also has a Bangalore SRE role on today's board, which is a different team and a different skill set.
What the posting asks for: 3 or more years in a DevOps, SRE or Infrastructure Engineering role. Sarvam marks two requirements non negotiable: strong hands on production Kubernetes covering deployments, Helm charts, HPAs, CronJobs, node affinity, resource management and debugging pod failures, and proficiency with at least one major cloud among Azure, GCP or AWS covering managed Kubernetes, container registries, blob storage, secrets vaults and IAM. Beyond those it asks for experience building and maintaining CI/CD pipelines with container builds, automated testing gates, multi environment promotion and deployment automation, solid containerisation including production Dockerfiles, multi stage builds and image optimisation, experience with monitoring and observability stacks such as Prometheus, Grafana, OpenTelemetry or Sentry, strong Linux systems knowledge across networking, process management, storage and system level debugging, scripting in Python or Bash, a good understanding of networking including DNS, load balancing, ingress controllers, TLS termination and CDN configuration, experience with secrets management patterns such as External Secrets Operator or Sealed Secrets, and familiarity with Redis or similar in memory stores for queues and pub sub. The real day to day: operating production Kubernetes with multi role deployments across API servers, task schedulers, per stage workers and WebSocket servers. Building and optimising CI/CD with staged rollouts across QA, staging and production. Maintaining Helm charts, shared module dependencies and environment specific value overlays. Implementing metrics, dashboards, error tracking and distributed tracing. Operating blob storage with CDN for media delivery, ingress, secrets and IAM. Coordinating multi cloud deployments and artifact management for Docker images and internal Python packages. Running vault to cluster secret sync. Optimising async task queues including dead letter handling and stuck message recovery. Monitoring database query health, connection pooling and backup and recovery. Building developer productivity tooling and local dev environments. Owning incident response including runbooks, alerting rules and post mortems. Driving cost optimisation through right sizing, autoscaling policies and storage lifecycle management. Location and setup: Bengaluru. The posting does not state office days. Honest fit guidance: the workload is ML heavy and GPU backed, which is meaningfully harder to operate than a standard web stack, and the posting is honest that failures cascade across pipeline stages. Good fit if you want infrastructure work at a company where the infrastructure is the hard part. Sarvam also has a Studio backend role open today at 4 to 6 years, which is the same platform from the application side.
What the posting asks for, listed by Zscaler as minimum qualifications: demonstrated curiosity and active use of AI tools with a history of integrating new technology into daily workflows, 3 or more years of Java in a highly distributed and enterprise scale environment with experience in Kafka, Druid and Elasticsearch, experience being on call and handling cloud incidents including writing root cause analyses, working knowledge of cloud infrastructure services on AWS or Azure, and a Bachelor's or Master's in Computer Science or equivalent experience. Preferred qualifications, described as what will make you stand out: experience building full CI/CD systems using Kubernetes and web service frameworks, experience building reliable and extensible data tiers for large scale web services with Postgres and Redis, and experience with identity and access management systems such as Okta, SAML protocols and OAuth. The real day to day: understanding how to build and operate high scale systems, providing service and product wide architectural guidance and driving technical decisions, establishing and enforcing best practices for coding, testing, observability and CI/CD to keep services production ready, and driving cross team collaboration on performance optimisation, reliability improvements and adoption of new technology to accelerate feature velocity. Zscaler also publishes a success profile: comfort with ambiguity and building the path as you walk it, acting like an owner with a bias for action, running toward hard problems, and being a high trust collaborator who puts team success first. Location and setup: the posting lists the location as India and is tagged hybrid, reporting to a Senior Director of Software Engineering. The location field on this posting reads "India, Update Location", so confirm the specific city with the recruiter before applying. Honest fit guidance: the mismatch between the Senior title and the 3 year minimum is worth acting on, because engineers at 3 to 4 years often filter out anything labelled Senior and would never see this. The AI tooling requirement is listed first among the minimum qualifications, not as a nice to have, which tells you something about how the team expects to work. Being on call is explicitly part of the job.
What the posting asks for: 3 or more years of industry experience building large scale NLP and NLU systems, with recent hands on work in LLMs and LLM powered paradigms including agentic AI. The real day to day: designing and developing state of the art LLM powered AI capabilities and agentic or multi agent systems end to end, from idea through to production, in a fast moving startup environment. Working with current tooling across machine learning, deep learning and natural language processing. Building and maintaining highly scalable production systems that power the AI capabilities in the product. Optimising ML models and processing pipelines for performance, cost effectiveness and scale. Mentoring more junior engineers and influencing peers and stakeholders. Collaborating across engineering, product, customer facing teams and customers. What the team offers beyond the work: Observe.AI states that you will have the opportunity to publish at top conferences and to influence the company's product and platform strategy, and describes the ML team as working on multi agent systems, LLMs and applied research turned into production systems handling millions of interactions daily. Location and setup: Bengaluru. The posting does not state office days. Honest fit guidance: the posting says plainly that it wants someone who is "truly an engineer at heart", and the responsibilities back that up: this is applied ML with a heavy production systems component, not a research seat. If your experience is fine tuning and evaluation without owning the serving path, expect the scale and reliability parts to be the stretch. At 3 or more years it is one of the more accessible senior ML openings on the board, and it sits in the same company as an SDE III backend role also listed today, which is a different team.
What the posting asks for: Twilio states it is hiring for multiple positions at either a Senior or a Staff level under this one listing. The Senior level asks for 3 or more years of professional software development experience, ideally full stack. The Staff level asks for 5 or more years of professional full stack software development experience. Apply against the level that matches you rather than assuming the higher bar applies. The real day to day differs by level, and Twilio spells both out. At the Senior level: developing, testing and deploying code for prototypes and new product features, working with the team to solve technical problems and improve solution design, taking part in code reviews, documentation and knowledge sharing, experimenting with modern tools, frameworks and emerging technology, and adapting to changing requirements while contributing to process improvement. Twilio calls this a growth role, suited to someone eager to learn in a fast paced and entrepreneurial environment. At the Staff level: designing, developing and implementing prototypes and production ready solutions, experimenting with AI, machine learning and emerging technology alongside the team, contributing to engineering best practice through code review, communicating progress and technical concepts to stakeholders, and adapting quickly to feedback and changing requirements. Location and setup: remote within India. Twilio describes a dedication to remote first work and a culture of global connection, and this is genuinely a distributed role rather than a hybrid one. Two things worth knowing before you apply. Twilio states openly that it uses AI to help make its hiring process efficient, while adding that every hiring decision is made by a person. And Twilio's remote India postings have historically been restricted to a subset of Indian states, so confirm your state is eligible with the recruiter rather than assuming all of India qualifies. Honest fit guidance: incubation work means ambiguity, short cycles and a real chance that something you build does not ship, which suits some engineers and frustrates others. The compensating benefit is breadth and exposure to new technology early. Twilio also has a Staff Business Intelligence Engineer role open remotely today at 7 or more years, which is a different team on the data side.
What the posting asks for: a Bachelor's degree in Computer Science, Engineering or a related field, 3 or more years working with PySpark and SQL, 2 or more years building and maintaining data pipelines on Amazon EMR or Amazon Glue, 2 or more years of data modelling and end user querying with Amazon Redshift or Snowflake plus Athena and Presto, and 1 or more years building and maintaining pipeline orchestration with Airflow. It also asks for strong problem solving and troubleshooting, excellent communication and collaboration, and the ability to work both independently and in a team. Preferred, not required: an AWS Data Analytics Specialty certification and experience with Agile development. The real day to day: building and maintaining production data pipelines on EMR or Glue, designing data models and end user querying on Redshift or Snowflake, Athena and Presto, building pipeline orchestration with Airflow, working with customer and internal teams to understand data needs and design solutions, troubleshooting and optimising pipelines and models until they hold under real load, writing and maintaining PySpark and SQL for extract, transform and load work, documenting and communicating technical decisions to both technical and non technical audiences since customers sign off on what ships, and tracking new AWS data technology to judge whether it belongs in the systems Mactores runs. Location and setup: the listing is tagged Mumbai, Maharashtra, but the posting body states plainly that the role is fully remote. It also describes a forward deployed model where senior engineers embed with the customer's team and carry the delivery commitment personally against fixed dates, with Mactores absorbing overage cost for delays inside its control. Confirm the remote arrangement and any client site travel expectation with the recruiter, since embedded consulting and fully remote can pull in different directions. Honest fit guidance: this is consulting delivery work, so you will be working against customer commitments and sign offs rather than an internal roadmap, and the posting is candid that the culture is measured by what ships. Note also that Mactores lists a separate freelancer variant of this same role, so check which one you are applying to. The 3 year floor against a Senior title makes this reachable earlier than the name suggests.
What the posting asks for: 4 to 6 years in backend engineering with a focus on building and operating production services at scale. Sarvam marks Python and production FastAPI or similar async web service experience as non negotiable. Beyond that it asks for a deep understanding of async programming including asyncio, concurrent execution patterns and designing for high throughput, experience with distributed task systems covering task queues such as Celery, message brokers and fault tolerant job orchestration, hands on PostgreSQL with an async ORM such as SQLAlchemy including query optimisation, schema design and migrations, familiarity with audio and media processing using FFmpeg, common audio formats and libraries such as soundfile or librosa, experience integrating ML models into production whether API based over REST or gRPC or local inference with PyTorch or ONNX Runtime, experience building reusable libraries or SDKs with clean APIs and backward compatibility, proficiency with Docker, Kubernetes, Helm and at least one major cloud, and strong testing discipline including mocking external services and maintaining CI/CD. Bonus points: prior experience with speech or NLP systems such as ASR, TTS or machine translation. The real day to day, across three areas. Service and infrastructure: designing production FastAPI services for dubbing and live translation with multi stage task orchestration, rate limited scheduling and backpressure controls, building distributed worker architectures with independent scaling per pipeline stage and automatic recovery of stuck tasks, owning the async ORM data layer and migrations on PostgreSQL, implementing WebSocket based job tracking and streaming audio pipelines, and managing Kubernetes deployments including Helm charts, secrets, ingress and multi role images. ML pipeline and library: extending the core dubbing library across audio extraction, voice activity detection, speech recognition, translation, quality control, text to speech and video stitching, integrating and optimising ML model serving for both remote inference and local inference, building quality control orchestration including automated scoring, tempo analysis and pronunciation verification, and maintaining LLM integration layers across multiple provider backends. Platform SDK: maintaining the shared Studio SDK with reusable FastAPI middleware and routers for authentication, billing, workspace isolation and input validation. Location and setup: Bengaluru. The posting does not state office days. Honest fit guidance: the media and audio processing element is a genuine specialisation, and the posting is explicit that FastAPI and async depth are not negotiable. If your backend experience is synchronous request and response web services, this will be a real jump. Sarvam also has a Studio DevOps role open today at 3 or more years, which is the same platform from the infrastructure side.
What the posting asks for: a minimum of 4 to 7 years of strong hands on Linux and Unix system administration, including TCP/IP, DNS and load balancers, plus expertise in managing and scaling infrastructure. The real day to day: troubleshooting issues across the entire stack covering hardware, software, application and network. Improving the reliability and performance of distributed systems and containerised deployments. Diagnosing complex distributed systems handling millions of queries per second. Working in a heavily command line driven environment that requires strong Linux understanding. Participating in an on call rotation. Designing, building and maintaining the core infrastructure that lets PhonePe scale to hundreds of thousands of concurrent users. Taking part in analysis and system improvement planning. Driving performance testing, capacity planning and high availability practices. Owning implementations of new technology with proper testing and documentation. Proactively monitoring and solving issues that could affect infrastructure. Onboarding new team members and getting them production ready. Location and setup: Bangalore. The posting does not state office days. Honest fit guidance: the on call rotation is stated in the posting rather than buried, and in a payments business an incident at 2am is a real incident, so weigh that honestly. PhonePe describes a culture where you own your work end to end from day one and teams frequently build frameworks from scratch, which suggests genuine autonomy but also limited hand holding. Worth noting PhonePe has several similarly titled SRE openings live, including SRE 3 and a big data focused SRE at 7 or more years, so check you are applying to the level that fits. This is the Bangalore infrastructure role; PhonePe's Pune backend role on today's board is a different team and skill set.
What the posting asks for: 4 or more years of professional experience in engineering or technical consulting. The role is built on deep Kubernetes knowledge, since Nirmata expects you to go deep in Kubernetes and in Nirmata's own solutions, including using its AI capabilities against customer problems. The real day to day, as Nirmata lists it. Custom engineering and proof of value: building working solutions against live production systems to demonstrate provable return on investment tied to the customer's own data and environment. Cloud native and AI expertise: being the expert who goes deep on Kubernetes as the orchestrator for both software and AI workloads. Enterprise implementation: verifying and implementing detailed technical designs that address complex customer problems and drive platform adoption. Technical leadership: leading customer initiatives by understanding the business implications and architecting for operational, integration and scaling requirements. Operational excellence: providing design and operational solutions for enterprise container adoption, including building the necessary tools and automation. Research and development feedback: gathering field insight and giving Engineering clear product feedback grounded in real customer requirements. Customer advocacy: managing technical escalations, educating customers and documenting best practice. Value realisation: helping customers define, capture and document the financial value the platform delivers. Location and setup: Bangalore. The posting does not state office days. Honest fit guidance: Nirmata says outright that this is unlike a traditional customer success role, and the responsibilities support that, since you are building against live production systems rather than running adoption checklists. The trade off is that your work is measured in customer outcomes and renewals rather than shipped features, and you will spend real time in meetings and escalations. Good fit if you have Kubernetes depth and want to use it in front of customers. Poor fit if you want to be heads down in a codebase. Nirmata is also a much smaller company than most on this list, which usually means broader scope and less structure.
What the posting asks for: 5 to 9 years of experience building large scale products. The real day to day: contributing to building and deploying AI agents for customer service in the form of voice agents, chat agents and copilots at enterprise scale. Owning the full application lifecycle through design, coding, testing, deployment and debugging with a high quality bar. Working with product and design to translate the product roadmap into a clear technical roadmap. Developing reusable code, frameworks and libraries to speed up development and keep projects consistent. Optimising applications for speed, scalability and reliability by proactively addressing bottlenecks and performance issues. Implementing security measures and data protection practices to safeguard applications and sensitive customer data. Designing and managing scalable data storage that stays efficient, reliable and maintainable. Building and scaling efficient data pipelines that process large volumes accurately. Reviewing others' work as part of the team's quality process. Location and setup: Bengaluru. The posting does not state office days. Honest fit guidance: this is backend platform engineering supporting AI products, not machine learning engineering, so the daily work is distributed systems, data pipelines and API design rather than models and evaluation. If you want to move closer to AI without retraining as an ML engineer, that distinction works in your favour. Observe.AI describes a culture that prizes speed and ownership, which usually means less process and more direct responsibility. Note Observe.AI also has a Senior ML Engineer NLP role on today's board at 3 or more years, which is the model side of the same product, so pick according to which half of the system you want to own.
What the posting asks for: 5 or more years of professional experience in machine learning and software engineering. Coinbase states the level directly, hiring an IC5 Machine Learning Engineer. The real day to day: architecting and deploying the orchestration layer that manages state transitions, context sharing and intent routing across vendor and internal LLM frameworks in a distributed conversational environment. Building production grade Python services that connect ML and AI research to reliable, measurable customer facing products. Leading end to end execution on complex ML initiatives, managing priorities, technical trade offs and cross functional dependencies from design through delivery. Establishing best practice for system design, coding standards and AI and ML development workflows across the team. Mentoring engineers on architectural integrity and modern AI and ML patterns. Running design reviews. The team context: CX Intelligence sits inside Coinbase's Enterprise Applications and Architecture organisation and owns the multi agent platform powering Coinbase chat, the Help Center and agent tooling, working with Conversation Design, CX and other engineering teams to deliver secure and compliant AI powered support. Location and setup, and this matters: the role is remote within India, but Coinbase states plainly that it is remote first, not remote only, and that you should expect to gather quarterly for in person working sessions it calls surges. If travel every quarter is a problem, factor that in now rather than at offer stage. Coinbase is also unusually blunt about culture in the posting itself, saying the bar is high and the environment is intense. Honest fit guidance: the interesting engineering here is the hand off logic between different LLM frameworks and between AI and human agents, which is a genuinely hard and current problem. It is applied ML with a heavy production systems and architecture component, so it suits someone who has shipped and operated ML services rather than someone whose experience is model training alone. Coinbase has three remote India roles on today's board across different teams.
What the posting asks for: 5 or more years in IT engineering, automation or systems engineering, with demonstrated ownership of architecture decisions, engineering standards or platform level systems that others build on. Also required are deep expertise building and maintaining complex automations using n8n, Airflow, Temporal, Jira Automation or Workato, paired with strong Git based development workflows including branching, CI/CD and code review, and working knowledge of Okta, Slack API and Google Workspace administration sufficient to design against them. The real day to day: owning the technical architecture of IT Tooling automations and driving design decisions on system structure, integration patterns and tooling across n8n, Airflow, Temporal and Jira. Establishing architecture standards and code review practices that raise the team's engineering bar. Leading as technical decision maker on the most complex, highest impact automation projects from discovery through production. Partnering with Security, Corporate Engineering and Identity and Access Management to clear technical blockers and representing the team in cross functional architecture discussions. Building shared frameworks and reusable components that reduce single points of failure. Producing architecture documentation and decision records so the team scales without depending on one person. Managing your own workload with high independence, turning loosely scoped problems into production ready specifications. Location and setup: remote within India. As with Coinbase's other openings, the company states it is remote first but not remote only, and that you should expect quarterly in person working sessions called surges. The team partners with regional IT groups across Asia Pacific, Europe and the Americas, so some schedule overlap across time zones is likely. Honest fit guidance: be clear about what this is. It is internal IT automation engineering, not product engineering, and your users are Coinbase employees. That is a real career distinction and some engineers will not want it. What it offers in exchange is genuine architectural ownership at 5 years, a modern automation stack, and a remote role at a large employer. If you have been doing IT operations and want to move toward platform engineering, this is a credible bridge. If you want to build customer facing product, look at Coinbase's other two openings on today's board instead.
What the posting asks for: a minimum of 5 or more years of relevant experience as a Data Scientist, preferably in a consulting role. Alongside that Databricks asks for experience building GenAI applications including RAG, multi agent systems, Text2SQL and fine tuning with tools such as HuggingFace, LangChain and DSPy, expertise deploying production grade GenAI applications including evaluation and optimisation, extensive hands on industry data science experience with common tooling such as pandas, scikit learn and PyTorch, experience building production grade machine learning deployments on AWS, Azure or GCP, a graduate degree in a quantitative discipline such as Computer Science, Engineering, Statistics or Operations Research or equivalent practical experience, and the ability to explain technical concepts to both technical and non technical audiences. Preferred, not required: experience using the Databricks Intelligence Platform and Apache Spark to process large scale distributed datasets. The real day to day: developing GenAI solutions that incorporate techniques from Databricks' own Mosaic AI research to solve customer problems. Owning production rollouts of both consumer facing and internal GenAI applications. Serving as a trusted technical advisor to customers across a variety of domains. Presenting at conferences such as the Data and AI Summit and being recognised as a thought leader internally and externally. Collaborating with product and engineering teams to influence priorities and shape the roadmap. Location and setup: the posting states the role can be remote, and the listing specifies India. Honest fit guidance: this is a customer facing professional services role, so a real share of your week goes to customer meetings, discovery and advisory work rather than heads down building. Databricks describes the team as an ensemble that looks for individuals with strong unique specialisations, which suggests depth in one area matters more than breadth. The graduate degree requirement is stated, though Databricks allows equivalent practical experience, so do not self reject on that alone if your production GenAI record is strong. The conference speaking expectation is unusual and worth taking at face value: visibility is part of the job.
What the posting asks for, and read this carefully because the numbers stack: 5 or more years of professional experience overall, and separately 3 or more years working in data engineering, business intelligence or a similar role. The effective floor is 5 years, not 3. Also required are proficiency using AI coding tools such as Claude Code, Codex or Cursor across the full software development lifecycle from design and code generation through testing, monitoring and release, proficiency in Python or Java, 3 or more years with ETL orchestration and workflow management tools such as Airflow, Flink, Oozie or Azkaban on AWS or GCP, expert level database fundamentals, SQL and distributed computing, 3 or more years with the distributed data ecosystem including Spark, Hive, Druid and Presto plus streaming technologies such as Kafka or Flink, experience with Snowflake, Redshift, PostgreSQL or other database platforms, knowledge of reporting tools such as Tableau, Superset and Looker, and strong communication with both technical and non technical teams. The real day to day: working with business partners and stakeholders to understand data requirements, working with engineering, product teams and third parties to collect the required data, designing and implementing large scale high volume high performance data models and pipelines for the data lake and warehouse, developing data quality checks and monitoring routines, improving the reliability and scalability of ETL processes, managing a portfolio of data products that deliver trustworthy data, and helping onboard and support engineers joining the team. Location and setup: Hyderabad, India. The posting states that you must be located near one of DoorDash's engineering hubs, so this is not a remote role despite being on a large distributed company's board. Honest fit guidance: the explicit requirement for proficiency with AI coding tools is worth noting, since it is listed as a requirement rather than a nice to have and names specific products. This is a good example of why reading the experience sentence by hand matters: an automated parser would report this role as 3 years because that number appears three times, when the actual floor is 5. Strong choice if you want data engineering at genuine consumer scale, and DoorDash's data organisation is explicitly the foundation for company decision making rather than a reporting function.
What the posting asks for: 5 to 7 years of experience in a customer account facing role. Datadog also wants a strong communicator with excellent attention to detail, someone motivated by building long lasting relationships, experience negotiating contract terms and overcoming pricing objections without direct guidance for upsell and cross sell, and a proven track record of hitting account expansion targets measured by growth and retention of a portfolio. The real day to day: partnering with the sales team for a smooth transition and onboarding, proactively building customer relationships to create mutual trust, carrying out the full sales cycle for growth opportunities inside existing accounts, advising customers so they use Datadog effectively, monitoring usage trends to uncover renewal risk and promote adoption, and collaborating across Datadog's Support, Product, Finance and Legal teams. What Datadog offers around the role: it publishes a structured onboarding programme and sales training in MEDDIC and Command of the Message, which is a real signal that the methodology is taught rather than assumed. Location and setup: Bangalore, India. Datadog states its position openly, saying it values office culture and operates as a hybrid workplace. Ask what hybrid means in days for this team. Honest fit guidance: be clear about what this role is. Despite sitting on a technical products board, it is a commercial customer success role carrying expansion targets, not an engineering or solutions engineering job. If you want the technical version, Datadog's Technical Account Manager 2 role is also on today's board and asks for hands on cloud, scripting and CI/CD skills instead. Datadog adds a note worth repeating, that not everyone will meet all the qualifications on day one and it encourages applying anyway if you are passionate about the technology.
What the posting asks for: 6 or more years of data engineering experience, with at least 2 of those in a senior or lead capacity. The real day to day: owning and evolving the data platform across StarRocks for OLAP, Apache Hudi for the data lake, Trino, Spark and Apache Ranger, keeping performance, reliability and security intact at scale. Building the next generation AI optimised data layer, meaning clean structured datasets that power natural language querying and AI add on features for HackerRank for Work customers. Owning in product data features including exports, insights dashboards, interview analytics and the self serve custom reports interface. Enabling self service pipelines for internal teams across AI platform, analytics and go to market, which reduces ad hoc data requests. Enforcing data security through access controls, Apache Ranger policies and confidence scoring guardrails on AI generated output. Leading technical design reviews and defining engineering standards for the data team. Partnering with product managers and business stakeholders to identify and scope AI enabled data use cases. Location and setup: hybrid in Bangalore, India. The posting does not state how many days. Honest fit guidance: HackerRank is unusually specific about where the platform stands, which is useful, because it tells you the painful migration is behind you and the work ahead is building features rather than firefighting legacy. The posting calls this a greenfield opportunity to shape the next phase of data at the company. Note the framing as a senior individual contributor at the heart of the data organisation: the Lead in the title means technical leadership and design authority, not people management, so it stays on this board. Good fit if you want platform ownership and direct line of sight from your work to revenue features. Less good if you want a large existing team around you, since the role reads as a small senior group with wide scope.
What the posting asks for: 7 or more years of experience in business intelligence, data analytics or a related field, with at least 2 of those in a staff or senior individual contributor role. The real day to day: owning and evolving Twilio's suite of business intelligence tools, driving governance, performance and long term roadmap decisions. Designing and building scalable, reusable dashboards and reports that surface actionable insight for stakeholders across legal, billing operations and other mission critical functions. Architecting and deploying agentic AI solutions that enable natural language querying, automated insight generation and self service analytics for non technical business partners. Collaborating with data engineers, business partners and AI and ML engineers to turn complex analytical requirements into reliable, well documented data products. Establishing and championing BI best practice including semantic layer design, metric definitions, data access governance and documentation standards. Partnering with business leaders to find opportunities where better data visibility changes decisions. Location and setup: remote within India. Twilio describes a dedication to remote first work and a strong culture of global connection, so this is a genuinely distributed role. One caveat: Twilio's remote India postings have historically been open only to a subset of Indian states, so confirm your state qualifies before you invest in the process. Twilio also states openly that it uses AI to help make its hiring process efficient, while adding that every hiring decision is made by a person. Honest fit guidance: this is a platform and strategy role rather than a report building one, and the agentic AI element is a real part of the brief rather than decoration, so experience with semantic layers and self service analytics architecture matters more than dashboard volume. The stakeholder set is heavily internal business functions including legal and billing operations, which means influence and documentation are as important as technical skill. Twilio also has a remote Senior or Staff Applied Research Software Engineer role on today's board at 3 or more years, which is a very different team.
What the posting asks for: 8 or more years of hands on software engineering experience with a demonstrated track record of the kind of platform ownership this role requires. Coinbase names the level explicitly as Staff. The real day to day: architecting and delivering foundational platform capabilities including tool registries, AI orchestration layers, risk based access automation, and the contribution model that lets product groups across Coinbase build on the platform safely and quickly. Driving the evolution of Control Center into an AI agent ready, headless operations platform by designing procedure constructs, agentic guardrails, human in the loop orchestration and evaluation frameworks so that both people and autonomous agents can carry out sensitive customer operations securely. Partnering with the Engineering Manager and product counterparts to define architectural roadmaps, author technical design documents, lead design reviews, break complex initiatives into deliverable milestones, and raise the engineering bar through code review and mentorship. Building and maintaining highly reliable platform services. Location and setup: remote within India. Coinbase states it is remote first but not remote only, and that you should expect quarterly in person working sessions it calls surges. Coinbase is also direct in the posting about culture, saying the bar is high and the environment is intense. Honest fit guidance: the substance here is unusually current, since designing guardrails and evaluation frameworks so AI agents can safely execute sensitive customer operations is a problem most companies are only starting to think about. The trade off is that this is an internal platform rather than a customer facing product, and the users are Coinbase specialists in compliance, legal and investigations. At Staff level the expectation is architectural leadership and mentorship rather than pure output, so the application should evidence decisions you owned, not just systems you worked on. This is one of three Coinbase remote India roles on today's board.
⚠️ Years of experience: GitLab does not state a number anywhere in this posting, and we do not publish figures we cannot source. What GitLab does state is the level range in the title itself, Intermediate through Senior to Staff, so the entry point is the Intermediate rung rather than Staff. GitLab adds that it welcomes interest from candidates with varying levels of experience and that many successful candidates do not meet every requirement. Ask the recruiter where each level sits before you self reject. What the posting asks for: experience building instrumented, observable software systems. Knowledge of Git internals including its code and data structures, or practical experience operating Git servers. Experience writing and testing production code. GitLab also asks that you share its values and work in accordance with them, which it treats as a real requirement rather than boilerplate. The real day to day: taking part in architectural discussions and technical decisions on Git and Gitaly, helping drive implementation choices that improve correctness, performance and maintainability. Contributing features and fixes to upstream Git. Adapting Gitaly to make effective use of new and existing Git capabilities. Representing GitLab as a constructive participant in the open source ecosystem and building relationships that support ongoing collaboration with the Git community. Working across repository access, performance and long term maintainability. Location and setup: fully remote, with India among the listed locations alongside Canada, Poland, the United Kingdom and the United States. GitLab is one of the best known all remote companies, so remote here is the default operating model rather than an accommodation. Honest fit guidance: this is systems programming in C on one of the most widely used pieces of software in the world, and the requirement for Git internals knowledge or Git server operations experience is the real gate. Very few engineers have that, which cuts both ways: the pool is small, so genuine C and Git depth counts for a lot more than years on a CV. The upstream contribution element means your work is public and permanent, which is rare and valuable. Because GitLab spans three levels here, do not rule yourself out on seniority. Note also that a role open across five countries is competitive globally, not just in India.
⚠️ Years of experience: GitLab does not state a number in this posting, and we do not publish figures we cannot source. GitLab does say it welcomes interest from candidates with varying levels of experience and that many successful candidates do not meet every requirement. The framing that you are "eager to grow into customer facing technical leadership with strong mentorship and support" suggests this is not a first job but also not a principal level role. Ask the recruiter directly. What the posting asks for: experience providing technical consultancy and solution guidance through video calls and written channels, helping users or customers successfully adopt technical solutions. Familiarity with DevSecOps workflows and related tooling. The ability to manage multiple customer engagements in parallel, prioritise effectively and communicate status, risks and next steps clearly. An interest in supporting customers across Asia Pacific and Japan and adapting to different cultures, working styles and levels of technical maturity. GitLab states one hard requirement: you must be based in India with full working rights in India. The real day to day: providing on demand technical consultancy and solution guidance over Zoom and in writing, helping customers solve day to day issues and design and implement GitLab solutions for their DevSecOps workflows. Delivering workshops, demos and best practice guidance across the Asia Pacific and Japan region. Working with Account Executives and Renewals Managers to align technical recommendations with customer goals and support renewals and expansion by showing outcomes. Managing multiple engagements in parallel and keeping implementations on track. Contributing documentation and enablement content back to the wider team. Mentoring team members and customers through complex technical challenges. Location and setup: fully remote within India, and GitLab is explicit that this role suits someone who thrives in a remote, asynchronous environment. GitLab is an all remote company, so this is the default way the whole organisation works rather than an exception made for one role. Supporting the Asia Pacific and Japan region means your hours align reasonably well with India, unlike customer roles covering the Americas. Honest fit guidance: this is the technical end of customer success, closer to solutions engineering than to account management, and DevSecOps familiarity is the real requirement. It suits someone who enjoys explaining and unblocking as much as building. The renewals and expansion element means commercial outcomes are part of how the role is judged, so it is not purely technical. GitLab also has a remote backend engineering role on today's board on the Git and Gitaly team.
⚠️ Years of experience: Datadog does not state a number in this posting, and we do not publish figures we cannot source. It does ask for previous experience working as a TAM supporting mid market or enterprise customers in the cloud space, which implies you have done the job before rather than entering it fresh. Ask the recruiter what band the "2" in the title corresponds to. What the posting asks for: a solid technical grounding with hands on IT operations experience. Confident hands on experience with AWS, Azure or GCP. Comfort with scripting languages such as Python, JavaScript, Ruby, Perl, Go or PHP, or configuration tooling such as Chef or Puppet. Skill with CI/CD tools such as Jenkins or GitLab. Knowledge of containerisation tools such as Docker, Kubernetes or Rancher. Previous experience as a TAM supporting mid market or enterprise cloud customers. Experience working across Sales, Support and Engineering. Experience using Datadog or other cloud monitoring tools. One requirement that is easy to miss and hard to undo: the posting asks that you be able to travel by road, rail or air up to 30% of the time. That is roughly one week in three. If travel at that level does not work for you, this is the wrong role regardless of technical fit. The real day to day: advising on technical support and product adoption for customers across pre sales, post sales and renewal processes. Analysing the customer's IT operations environment regularly and recommending changes that maximise the value they get from Datadog. Acting as the customer's advocate by knowing their goals and use cases, then suggesting process changes, product adoption, configuration and additional features. Preparing for and taking part in monthly and quarterly business reviews with customers. Working with Datadog's product management, engineering and technical services teams to help identify new features and products. Continuously evolving best practice for technical product adoption. Location and setup: Bangalore, India. Datadog states it values office culture and operates as a hybrid workplace, so ask what that means in days per week for this team. Honest fit guidance: this is on the board because a reader asked for Technical Account Manager roles specifically, and it is worth saying that the "Manager" in the title refers to managing accounts, not people. The technical requirements are real, so this suits an engineer or IT operations specialist who wants customer facing work rather than a career account manager. Datadog notes that not everyone will meet every qualification on day one and encourages applying anyway. Its Customer Success Manager Key Accounts role is also on today's board and is the commercial counterpart to this one.
Added July 21, 2026
What the posting requires - 8+ years in systems or infrastructure software engineering, with a meaningful portion on Kafka or comparable distributed systems such as Pulsar, BookKeeper, ZooKeeper, etcd or CockroachDB - Deep familiarity with the Kafka codebase. The posting draws a sharp line here: it wants people who have read, modified and debugged the broker, controller or client internals, not people who have operated Kafka - A track record of upstream contribution: committed patches, participation in KIP discussions, reviewed pull requests or equivalent engagement with the Apache Kafka community. Committer or PMC status is strongly preferred but not strictly required - Strong distributed systems fundamentals understood as engineering tradeoffs you have navigated: consensus protocols, replication, exactly once semantics, log structured storage and distributed state machines - Systems level programming comfort: JVM internals including garbage collection tuning, memory layout and JIT behaviour; operating system I/O including page cache, fsync semantics and zero copy; and networking including TCP tuning and socket buffers - Experience maintaining a fork or distribution, and managing the tension between carrying local patches and staying mergeable with upstream Counts as a bonus, not a requirement - Apache Kafka committer or PMC membership - Experience with KRaft, the ZooKeeper free controller - Having authored or co-authored a KIP - Kafka Streams or Kafka Connect internals, rather than just usage - Familiarity with Kafka's own test infrastructure including system tests, Trogdor and ducktape What you would actually be doing - Owning the internal Kafka distribution: branches, patch curation, releases and upgrade planning - Contributing upstream to Apache Kafka - Diagnosing and fixing deep broker and controller issues across replication, partition reassignment, KRaft consensus, log storage and protocol handling - Building custom patches for production needs unsuited to upstream - Establishing how the team tests, benchmarks and validates patches before rollout - Mentoring a supporting engineer and growing the team's capability - Advising platform teams on configuration, capacity planning and architecture, and acting as the primary interface for audit and compliance Location and working pattern Bangalore. Staff at PhonePe is a senior individual contributor track. Also worth knowing PhonePe's listed benefits include comprehensive insurance, an onsite medical centre, parental and adoption support, relocation help, provident fund and gratuity, higher education assistance and a car lease policy. A good fit if You have gone deep on infrastructure internals rather than broad across product features, and you want one of the few Indian roles that will pay you to work on an open source distributed system at source level. Think twice if You have operated Kafka but never modified it. The posting makes that distinction explicitly, and the interview will go straight there.
What the posting requires - 3 to 6 years building and operating production backend systems at scale - Expert level in at least one modern backend language such as Python, Ruby, Go, Java or Node.js, with strong fundamentals across the stack - Proven ability to design distributed systems, having made real architectural decisions on service decomposition, data consistency, fault tolerance and observability - Deep expertise with relational databases such as PostgreSQL and MySQL plus NoSQL stores, including schema design, query optimisation and modelling for high throughput - Strong understanding of caching with Redis or Memcached, asynchronous messaging with Kafka or RabbitMQ, and event driven architecture - Hands on containerisation with Docker and Kubernetes, CI/CD pipelines and infrastructure as code - A track record of taking technical projects from an ambiguous problem statement through to production Read the AI section before you apply Unusually, HackerRank lists AI fluency as its own requirement block rather than a bonus, and asks for: - Deep hands on proficiency with AI powered development tools such as GitHub Copilot, Cursor or Claude Code, to the point where you have built workflows and practices you could teach to others - Strong working knowledge of large language models and agentic systems, including capabilities, limitations, context management and tool use - Proven ability to use AI across the full development lifecycle: architecture exploration, implementation, code review, test generation, documentation, incident analysis and technical writing - Solid understanding of AI and ML fundamentals: transformer architectures, embedding models, inference optimisation, retrieval augmented generation, the tradeoff between fine tuning and prompt engineering, and evaluation methods - The ability to evaluate AI tooling and integration patterns on cost, latency, reliability and security Counts as a bonus, not a requirement - Systems serving millions of concurrent users under strict latency and availability requirements - Deep expertise in patterns such as microservices, CQRS, event sourcing or domain driven design - Significant cloud experience across AWS, GCP or Azure including serverless and cost optimisation - Building platform level APIs, SDKs or developer tools used by other engineering teams - A history of improving engineering culture, through RFC processes, architecture review boards or engineering blog writing Location and working pattern Hybrid in Bangalore, so plan for regular office days. A good fit if You have a few years of backend work and want a product where reliability genuinely matters, and you are already comfortable working with AI tooling rather than avoiding it. Think twice if You have kept AI tools at arm's length. That section is long, specific and clearly being screened on, and it is the part of this posting most likely to decide the outcome.
What the posting requires - 4+ years building and shipping machine learning systems that run in production at scale - Proficiency in Python, with practical experience building data pipelines and deploying models - Systems thinking, which the posting defines precisely: model accuracy, data pipelines, serving infrastructure and customer outcomes are one problem, not four - Treating evaluation methodology as seriously as model performance, on the stated view that a metric measured wrong is worse than no metric Counts as a bonus, not a requirement - Multimodal systems across vision, natural language, audio or behavioural signal pipelines - Large language model experience including fine tuning, RLHF or multi turn agentic systems - A background in adversarial machine learning, fraud detection or anomaly detection - Publications or open source contributions in detection, robustness or evaluation methodology What you would actually be doing - Designing and shipping production machine learning across the Chakra, integrity and evaluation domains - Owning the full lifecycle: problem framing, data strategy, experimentation, deployment and iteration - Building evaluation infrastructure and benchmarking pipelines that measure model quality reliably before and after deployment - Defining the architecture and production bar for new signal categories from scratch - Mentoring junior machine learning engineers and establishing team practice for monitoring, feedback loops and quality standards Location and working pattern Hybrid in Bangalore. The company is explicit about who thrives here The posting says you will do well if messy, undefined problems interest you more than optimising inside clean ones, if ambiguity energises you when the right framing is itself part of the work, and if defining what a system should be appeals more than maintaining what already exists. It also offers direct access to leadership and fast feedback loops. A good fit if You have production machine learning experience and want genuinely unsolved problems. Detecting AI assisted cheating and redefining how coding skill is measured are live, open questions, and few Indian roles work on them directly. Think twice if You want a stable, well specified roadmap, or your machine learning work has been mostly research without deployment. The requirement is specifically shipping systems that run in production at scale.
What the posting requires - Over 8 years building and operating production grade services with clear ownership of outcomes - Strong system design and distributed systems, hands on across AWS or GCP, containers and Kubernetes, infrastructure as code with Terraform, and CI/CD automation - Depth in one or more of Go, Java, Ruby, Python or JavaScript, plus the ability to pick up new languages and frameworks quickly - Proficiency with PostgreSQL or MySQL and NoSQL databases, and experience with event driven architectures using Kafka or similar for streaming and async work - Excellent communication: writing clear documentation, explaining tradeoffs simply, mentoring peers and influencing across teams without direct authority Counts as a bonus, not a requirement - Exposure to AI systems in production such as language model gateways, prompt or model evaluation, and guardrails - Experience improving developer experience across a company - Public artefacts such as design write ups, talks or open source contributions What you would actually be doing - Aligning the engineering roadmap with business outcomes, and communicating the tradeoffs in plain language - Designing and evolving core API, data and AI platforms that stay scalable, observable, secure and cost aware under thousands of concurrent sessions and bursty traffic - Embedding AI as a first class concern: request orchestration, evaluation harnesses, guardrails and safety, and prompt and data governance - Partnering with product managers and customer facing teams to drive impact - Mentoring through reviews, design reviews and hands on pairing Location and working pattern Hybrid in Bangalore. A good fit if You have most of a decade of backend experience and want platform ownership at a product engineers choose to use, and you are as comfortable writing a design document as writing code. The posting says outright that it values balancing long term decisions with fast incremental delivery, and caring about developer experience as much as raw performance. Think twice if You want a pure coding role. A large share of this one is judgement, communication, roadmap and influence, and the posting weights communication unusually heavily for an engineering listing.
What the posting requires - 3 to 5 years as a database developer or engineer, with exposure to migration work - Working experience with at least one of Oracle, Microsoft SQL Server, or PostgreSQL and Aurora PostgreSQL - A bachelor's degree in computer science or a related field What you would actually be doing - Converting SQL, stored procedures and database objects into PostgreSQL compatible SQL and PL/pgSQL, escalating complex or ambiguous cases to a senior engineer - Working through AWS Schema Conversion Tool findings and flagging limitations that need senior review - Maintaining the Flyway migration codebase: versioned scripts, repeatable migrations and rollbacks - Identifying and troubleshooting database related application bugs, with support on the harder ones - Supporting PostgreSQL query optimisation through execution plans, indexing and query rewrites - Monitoring AWS DMS during full load and change data capture phases, and helping diagnose data and performance issues - Validating and reconciling data between source and target databases, which the posting describes as proof rather than confidence - Working with application teams to align SQL behaviour and performance expectations before cutover Location and working pattern Mumbai. This is consulting delivery, so the work is organised around client engagements and committed cutover dates. A good fit if You are a database engineer who wants AWS depth, or a backend engineer who has drifted into data work and wants to make that the specialism. The escalation path is unusually clearly described, which makes it a reasonable step up rather than a role that quietly expects senior judgement. Think twice if You want product engineering. This is client facing modernisation work with the deadlines and delivery pressure that implies, and much of the day is careful, detailed conversion and verification rather than green field building.
What the posting requires Core Python and systems - Strong Python with 4+ years in production: asyncio, performance optimisation and idiomatic code - A solid grasp of distributed systems concepts: state machines, retries, idempotency and eventual consistency - Integrating language model APIs from Anthropic, OpenAI or similar in production code, covering streaming, function calling, structured output, retries and prompt management - Comfort with FastAPI or an equivalent async web framework Cloud and infrastructure - Working knowledge of AWS: EKS, ECS Fargate, S3, DynamoDB, Lambda, Secrets Manager and CloudWatch - Docker and Kubernetes, including writing Dockerfiles, Helm charts and manifests - CI/CD pipelines, with GitHub Actions preferred - Comfort navigating multi account AWS environments across dev, UAT and production Testing and automation - Test driven development as a discipline, with tests written before the code - Hands on pytest, integration testing and end to end testing - The ability to design behaviour verification harnesses: dual run, output comparison and equivalence proof - Using AI tools such as Claude, Copilot or LLM based test generators to improve test quality Explicitly not required The posting states that you do not need prior Amazon Bedrock or LangChain experience. What it wants is a strong Python engineer who will learn agent frameworks properly. That makes this genuinely open to backend engineers who have not worked on agents before, which is unusual for this kind of role. What you would actually be doing - Building and shipping specialised agents: parsers, business rule extractors, dependency mappers, test synthesizers, behaviour replayers and the orchestration between them - Designing agents that operate against a code intelligence graph so every action traces to a line of code - Implementing governed autonomy through shadow, supervised and autonomous stages with human review at each - Orchestrating frontier models from Anthropic, OpenAI and Google, choosing the right model per task - Owning delivery of your agents from prototype through deployment and post release validation The interview process, as published Mactores lists its process openly, which is rare and worth preparing for specifically. There is a hands on technical session with a panel member covering your skills, experience and how you deliver quality under pressure, then a structured panel interview covering experience, product thinking and how you work, then a 30 minute HR discussion about the offer and next steps. The posting also asks applicants to answer as many of the application questions as possible to speed things up. Location and working pattern Mumbai. A good fit if You are a strong Python engineer curious about agent systems but have been put off by postings that demand specific framework experience. Think twice if You dislike heavy test discipline. Testing runs through this entire posting, including test driven development as a stated requirement and the ability to build equivalence proof harnesses.
What the posting requires - A B.E., B.Tech, M.E., M.Tech or PhD in computer science or equivalent - 6+ years with computer science fundamentals and experience with at least one of Go, Java or Python - Proficiency using AI coding tools such as Claude Code, Codex or Cursor across the full software development lifecycle, covering design, code generation, testing, monitoring and release. DoorDash lists this as a requirement rather than a bonus - Prior technical experience in big data infrastructure and in cost efficiency and governance, having built meaningful pieces of data infrastructure - Experience improving the efficiency, scalability and stability of data platforms - Experience building or operating backend systems in production Counts as a bonus, not a requirement - Having built data infrastructure on open sourced technologies such as Spark or ClickHouse What you would actually be doing - Working across data infrastructure, reliability, governance, developer tooling and AI systems - Supporting thousands of internal data users including engineers, analysts, data scientists and business stakeholders - Helping establish a founding engineering team in India, with the ownership and direct influence that implies Location and working pattern Pune. A good fit if You have solid backend or data platform experience and want early team influence rather than a defined slot in an existing structure. Note also that the AI tooling requirement is stated plainly, so make sure you can speak to how you actually use these tools day to day rather than in the abstract. Think twice if You want a settled team, established process and a clear roadmap. Founding teams trade that stability for ownership, and the posting is honest that this is one.
What the posting requires - 8+ years of professional experience as a hands on engineer and technical leader, leading multiple projects - 6+ years working specifically in data platform and data engineering or a similar role - Proficiency in Python, Kotlin or Scala - 4+ years with ETL orchestration and workflow management tools such as Airflow - 4+ years with the distributed data ecosystem such as Spark and Presto, and streaming technologies such as Kafka, Flink or Spark Streaming - Expert level database fundamentals, SQL, data reliability practices and distributed computing - Proficiency using AI coding tools such as Claude Code, Codex or Cursor across the full development lifecycle, which DoorDash asks for explicitly - Excellent communication with both technical and non technical teams, and knowledge of reporting tools What you would actually be doing - Acting as technical lead, architecting and scaling data reliability, infrastructure, automation and tooling - Owning critical data systems that support multiple products and teams - Developing, implementing and enforcing best practices for data infrastructure - Improving the reliability and scalability of ingestion, data processing, ETL, reporting tools and data ecosystem services Location and working pattern Hyderabad. A good fit if You have led data platform work before and want ownership of systems the business genuinely depends on, including financial reporting where correctness is not negotiable. Think twice if You are still early in a data engineering career, or your data work has been alongside another specialism rather than the main thing. The stacked requirements, 8 years overall and 6 in data, mean a generalist backend engineer with some pipeline experience is unlikely to clear the bar.
What the posting requires - 3+ years of hands on experience in applied machine learning - A strong background in machine learning, deep learning and natural language processing, with proven experience training and fine tuning large scale models such as language models, transformers and diffusion models - Hands on expertise with parameter efficient fine tuning approaches: LoRA, prefix tuning, adapters and quantization aware training - Proficiency in PyTorch, TensorFlow and the Hugging Face ecosystem - Basic understanding of MLOps: experiment tracking, model versioning, CI/CD for ML pipelines and production deployment - Experience with large datasets, feature engineering and data pipelines using tools such as Spark, Databricks or cloud native ML services including SageMaker, Vertex AI or Azure - Knowledge of GPU and TPU optimisation, mixed precision training, and scaling workloads on cloud or HPC environments - Excellent communication, able to explain complex ML concepts to technical and non technical audiences Marked mandatory in the posting - Demonstrated success adapting foundation models to domain specific applications through fine tuning or transfer learning - Strong ability to design, evaluate and improve models using robust validation strategies, bias and fairness checks, and performance optimisation Counts as a bonus, not a requirement - Distributed training frameworks such as DeepSpeed, PyTorch Lightning or Ray - Applied AI work across natural language, computer vision or multimodal systems - Proven ability to lead and mentor junior applied scientists and ML engineers Location and working pattern Bengaluru. A good fit if You have a few years of real modelling work and want problems where the business outcome is measurable, since commerce data gives fast, unambiguous feedback on whether a model is helping. Think twice if Your fine tuning experience is thin. The posting marks foundation model adaptation as mandatory rather than preferred, so it is likely to be a hard filter rather than something you can compensate for elsewhere.
What the posting requires - 3 to 6 years designing and developing complex systems - Strong Java, with exceptional software system design, problem solving and object oriented coding skills - Experience with distributed transaction processing systems or asynchronous messaging technology, which the posting states is required rather than preferred - A good understanding of system performance tradeoffs, load balancing and engineering for high availability - A genuine focus on software quality and end to end ownership of the features you build - A BS or MS in computer science, engineering, mathematics, statistics or a similar field Counts as a bonus, not a requirement - Understanding of enterprise information systems, service oriented architectures and operational data stores Read the level carefully The title says Software Development Engineer II, which at many companies signals an early career or new graduate role. The stated requirement starts at three years, so this is squarely mid level. It is one of the clearest examples in today's edition of why the years matter more than the level in the title, and applying to it as a recent graduate would waste your time. Location and working pattern Bengaluru. A good fit if You are a Java backend engineer with a few years behind you who wants data heavy commerce systems and clear ownership of what you build. Think twice if You are a recent graduate, or your Java experience is mostly CRUD web services. The distributed transaction and async messaging requirement is where this posting will actually be decided.
What the posting requires - 4 to 8 years building scalable, highly critical distributed systems - Strong object oriented design skills, the ability to apply design patterns, and what the posting calls an uncanny ability to design intuitive modules and class level interfaces - Strong technical aptitude and good computer science fundamentals - A B.Tech in computer science or equivalent What you would actually be doing - Working on highly maintainable and efficient components and systems - Excelling as an individual contributor, which the posting names as part of the role rather than a consequence of it - Identifying and resolving performance and scalability issues in an increasingly complex enterprise product - Improving the overall quality of the code structure and the product - Designing features alongside architects - Owning scoping, breakdown and implementation independently - Maintaining documentation for the component you work on The scale behind it More than 300 billion events a month, 2,000 plus customers across 40 plus countries. At that volume the interesting problems are throughput, correctness and failure behaviour rather than feature breadth. Location and working pattern Bangalore. A good fit if You have solid backend experience, want data infrastructure at genuinely high event volumes, and specifically want a senior individual contributor track rather than a step toward managing people. Think twice if You are looking for people management or team lead responsibility. The posting deliberately points the other way, and independence is a stated expectation rather than something you grow into.
What the posting requires - 8+ years of experience in software development, from an enterprise background - Experience with popular open source data processing engines such as Spark, Kafka or Flink, or equivalent - Experience developing with concurrent and non blocking systems - A bachelor's degree in computer science, software engineering or a related field, or equivalent experience The broader stack spans Java, Python, Go and C++. What you would actually be doing Engineering on the core pipeline engine behind a platform handling more than 300 billion events a month for over 2,000 customers across 40 plus countries. The problems at that scale are throughput, backpressure, correctness under load and failure behaviour rather than feature breadth. Location and working pattern Bangalore. A good fit if You have deep backend systems experience and want data infrastructure at scale. If you have specifically worked on concurrency and non blocking systems, this posting is asking for you more directly than most listings do, and that is worth leading with in your application. Think twice if Your experience is mainly request and response web services or CRUD applications. The concurrency requirement is called out separately from the general experience bar, which usually means it is a real filter rather than a preference.
What the posting requires - 6+ years of backend engineering building distributed systems, platform services or large scale backend applications - Strong proficiency in one or more common backend languages such as JavaScript, Python, Java, Go, PHP or C++ - Experience designing APIs, frameworks or platform abstractions used by multiple engineering teams - A strong understanding of reliability, observability, operational excellence and system failure modes - Experience with event driven architectures, messaging systems, queues, workflow engines or orchestration platforms - The ability to translate product requirements into durable, scalable platform capabilities - A collaborative mindset, with experience driving alignment across teams that have different priorities - A preference for simple, reliable solutions over unnecessary complexity - Strong communication and the ownership to move ambiguous projects from idea to production Counts as a bonus, not a requirement - Curiosity about AI and agentic product experiences, and how infrastructure needs to evolve to support them Know this before you apply Postman is direct about its in office model. Staff at its hubs in the San Francisco Bay Area, Boston, Austin, New York, Tokyo and London are in office five days a week. For roles based in Bangalore, employees currently work in the office three days a week and will transition to five days per week by the end of the year. If you are optimising for hybrid or remote flexibility, factor that in now rather than at offer stage. Location and working pattern Bengaluru, on the schedule described above. A good fit if You have genuine distributed systems depth, want to build platform capabilities other engineers depend on, and are happy working in an office. Think twice if Remote or hybrid flexibility matters to you. The direction of travel here is explicitly toward five days a week in office, and the posting states it rather than leaving it to be discovered.
What the posting requires - 10+ years of hands on coding, with familiarity across common programming languages such as C, C++, Java, PHP, Python, JavaScript and NodeJS - 10+ years of engineering experience building end to end backend services - Strong experience with security offerings such as vault stores, token scanning and cryptography - Demonstrated experience leading cross functional projects with meaningful impact on the business - Exceptional problem solving, design and analytical skills - Demonstrated experience designing highly scalable systems - A bachelor's degree in a computer science related field, or equivalent practical experience What the work concentrates on Keeping the platform trustworthy for a user base that stores credentials and secrets alongside their API work. The named security areas, vault storage, token scanning and cryptography, point at secret handling and leak prevention rather than general application security. Know this before you apply The same in office model applies as Postman's other Bengaluru opening: employees based in Bangalore currently work in the office three days a week, moving to five days per week by the end of the year. Location and working pattern Bengaluru, on the schedule above. A good fit if You have a decade of backend engineering and want scope over trust, security and reliability rather than feature delivery, and you have real cryptography or secret management experience to point to. Think twice if You are earlier in your career, or your security exposure is general rather than hands on with vaults, tokens and cryptography. Both the coding and the backend service requirements are stated as ten years, so this is not a stretch application.
What the posting requires - A degree in computer science - 3 to 5 years of experience with C and C++ and object oriented programming - Expertise in algorithms and data structures - A working knowledge of Linux systems - Excellent problem solving skills and strong communication - Experience in the high frequency trading industry is listed among the requirements Also mentioned in the posting - Familiarity with other languages including Java, Scala, Python, bash and Lisp - Familiarity with parallel programming models and parallel algorithms - Experience with big data environments What you would actually be doing - Designing and implementing a high frequency automated trading system that trades on multiple exchanges - Building live reporting and administration tools for that trading system - Performance optimisation and improving overall system latency through algorithm research and current technology Location and working pattern Gurugram. How to prepare Quantitative trading firms interview hard on data structures, algorithms, systems internals and low level performance, and Graviton describes its team in those terms. If you are applying, prepare for that specifically rather than for a general backend interview. Domain knowledge of finance is usually not required, and these firms hire primarily on engineering ability, so a strong systems background without trading experience is still worth an application even though HFT experience appears in the list. A good fit if You write performance sensitive C++, enjoy profiling and optimisation, and want work where microseconds are measured and genuinely matter commercially. Think twice if You prefer product breadth or working across a varied stack. This is deep, narrow, latency focused systems engineering, and most of the value you add comes from going further down rather than wider.
What the posting requires - 2 to 5 years of software development experience - 2+ years of product development experience - A BS, MS or PhD in computer science or a related field - Proficiency in one of C++, Java, Go, Scala or Python - The ability to identify scalable and elegant solutions to complex problems - A strong interest in and ability to learn new technologies Counts as a bonus, not a requirement - Full stack development experience What you would actually be doing - Working on the hypervisor protection layer, the most widely protected workload on Rubrik's platform - Building large scale distributed systems that serve both cloud and on premise protection - Designing, developing, testing, deploying, maintaining and improving the products, drawing on your experience with large software systems - Driving large projects end to end, working independently or partnering closely with other engineers Location and working pattern Bangalore. Why this one is worth a look if you are earlier in your career At 2 to 5 years it is the most accessible role in today's edition, and it asks for only one language from a fairly broad list rather than deep expertise across a stack. Distributed systems and storage is also a specialisation that holds its value for a long time, so it is a useful direction to move in early. The posting explicitly values willingness to learn new technologies, which suggests the team expects to bring people up rather than hire fully formed specialists. One practical note Rubrik's application page sits behind bot protection and can be slow to load or refuse automated traffic. We confirmed this posting is live and open. If the link does not open first time, try again in a normal browser window. Think twice if You want to specialise in application or product feature work. This is systems and infrastructure engineering at the storage and virtualisation layer.
What the posting requires - 9+ years of software engineering with a deep backend and infrastructure focus - Strong Python and/or Go. The posting is pointed here, asking for people who ship production code rather than scripts and configuration - Deep hands on Kubernetes: building and operating clusters, not just deploying onto them - Proven experience designing and operating distributed systems in production - Cloud native fluency across AWS and/or GCP spanning compute, storage, identity and access management, networking and managed services - Experience with infrastructure as code using Terraform or similar, and CI/CD pipelines - Familiarity with applied AI tooling and patterns, including agentic AI tools, AI gateways and agent frameworks, and the ability to build backend services that integrate with them - Strong system design and architectural judgement - Clear communication, partnering across product, security and AI teams Counts as a bonus, not a requirement - Observability stacks such as Prometheus, Grafana, Datadog or OpenTelemetry - Multi cloud or hybrid infrastructure experience across AWS, GCP and on premise Read where this role sits Rubrik places this position in its Information Technology organisation rather than core product engineering. That team centralises infrastructure, technology and data management to create operational efficiency as the company scales, and owns the secure environment the development lifecycle runs in. The AI capability you would build is for internal use. Location and working pattern Bangalore. One practical note Rubrik's application page sits behind bot protection and may refuse automated traffic or load slowly. We confirmed this posting is live. If it does not open first time, retry in a normal browser window. A good fit if You are experienced, genuinely interested in enterprise AI and internal platform engineering, and you want deep infrastructure work with modern AI tooling attached. Think twice if You specifically want to build a product customers buy. Rubrik's hypervisor opening in this same edition is the product engineering one, and the two lead to quite different careers.
What the posting requires - 3+ years with Apex, Lightning Web Components, SOQL and JavaScript, working in an Agile team - Force.com coding standards and the Salesforce Lightning Design System - Experience spotting the blind spots and bugs specific to Salesforce - Experience working with and optimising millions of rows of data - CSS, HTML and jQuery - Version control with Git or SVN - Writing unit tests with assertions for core functionality - The ability to turn technical requirements into independent features, with real debugging depth Counts as a bonus, not a requirement - AgentForce, Einstein and other AI tooling - SQL, Python, Data Cloud and Snowflake - Familiarity with a pay as you go business model - Building and deploying through Heroku - Conga or Apttus CPQ or CLM What you would actually be doing - Evolving the Salesforce data model behind Twilio's sales systems so it stays scalable and intuitive for the people using it - Building custom functionality using SOQL APIs, Apex controllers, Apex web services and Apex callouts - Running technical analysis, documenting integration requirements, and working with architects on integration design - Reviewing code quality across the codebase and refactoring for extensibility Location and working pattern Remote, but not from anywhere in India. The posting names five states: Karnataka, Tamil Nadu, Telangana, Maharashtra and New Delhi. Check you are in one before applying. Occasional travel may be required for project or team meetings in person. Also worth knowing Twilio lists competitive pay, generous time off, parental and wellness leave, healthcare and a retirement savings programme, noting that offerings vary by location. Twilio also states that it uses AI to make its hiring process more efficient, while every hiring decision is made by a person. A good fit if You are already a Salesforce developer with around three years behind you, and you want that skill inside a large global product company on a remote Indian contract. Think twice if You are a general backend or full stack engineer. Very little transfers here without Salesforce platform experience, and the required list is specific about it. The other two Twilio roles in today's edition are ordinary software engineering.
What the posting requires - 7+ years of applied machine learning with strong Python - A real grounding in machine learning foundations and the building blocks of modern deep learning - A track record of building, shipping and maintaining models in production in an ambiguous, fast paced environment - Experience designing large scale experiments and analysis that inform a product roadmap - Understanding of why frameworks like PyTorch, TensorFlow or Keras work as they do, not just how to call them - MLOps familiarity: testing, retraining and monitoring models once live - The ability to ramp up quickly in unfamiliar business domains - Exposure to modern data storage, messaging and processing tools such as Kafka, Spark, Hadoop, Presto and DynamoDB, including coding against big data components - Experience working in an agile team with shifting priorities - Experience working on AWS Counts as a bonus, not a requirement - Experience with large language models What you would actually be doing - Building and maintaining scalable machine learning in production - Training and validating deep learning and statistical models, weighing use case, complexity, performance and robustness - Developing an end to end understanding of the systems and the reasoning behind them - Partnering with product managers, tech leads and stakeholders to scope what needs building - Working with data platform teams on robust batch and real time pipelines - Mentoring, knowledge sharing, and upholding code review, automated testing and monitoring practice Location and working pattern Remote and based in India. Unlike Twilio's other two openings today, this one states no restriction to particular states. Occasional travel may be required for in person team meetings. Also worth knowing Twilio lists competitive pay, generous time off, parental and wellness leave, healthcare and a retirement savings programme, varying by location. A good fit if You have several years of production machine learning and want unusual scale plus a genuinely remote Indian role. Think twice if Your experience is mostly notebooks, coursework or research without deployment. The posting returns repeatedly to shipping and maintaining models, not building them once.
What the posting requires - 12+ years designing and building highly available, high scale, secure, mission critical cloud SaaS applications in Java, Go or Python - Knowledge of architectural patterns for mature services, especially distributed and multi regional deployments - Strong high level service design: modelling interfaces and internals so they stay modular, composable and extensible - AWS, GCP or another public cloud, with multi region deployment a plus - Building distributed systems at scale on a microservices architecture - Extensive REST API design and implementation - Data architecture experience such as ClickHouse, Lakehouse or Snowflake - SQL and NoSQL databases and caches - Familiarity with streaming systems such as Kafka, Flink or Spark - Container technologies, Docker and Kubernetes - Modern automated testing and CI/CD pipelines, with genuine ownership of develop, test and deploy - Strong track record solving complex production issues What you would actually be doing - Leading architecture and system design for complex distributed systems, and guiding teams toward maintainable solutions - Writing and reviewing high quality code for core services, APIs and platforms - Turning business goals into technical roadmaps and aligning stakeholders on direction - Improving resiliency, latency, throughput and cost efficiency, and establishing SLOs, SLAs and operational practice - Driving standards for coding, testing, CI/CD, observability, security and documentation - Coaching and mentoring engineers at every level, leading design reviews, postmortems and technical deep dives - Identifying security, scalability and compliance risks early and driving mitigation Location and working pattern Remote, but restricted to five Indian states: Karnataka, Tamil Nadu, Telangana, Maharashtra and New Delhi. Occasional travel may be required for in person meetings. A good fit if You are an experienced architect who wants breadth across many teams while staying hands on, working remotely from India. Think twice if You are below roughly a decade of experience. If you are earlier in your career, the requirement list is still worth reading as a map of what deep distributed systems specialisation builds toward.
What the posting requires - 3 to 5 years as a machine learning engineer, with a track record of building and deploying ML systems - Hands on experience creating generative AI systems including large language models and retrieval augmented generation, plus a clear history of operationalising agentic AI in production - Deep understanding of MLOps and LLMOps, specifically the monitoring, observability and debugging problems created by non deterministic agents - A solid computer science foundation in data structures and algorithms - Python expertise with scikit-learn and PyTorch or TensorFlow, plus SQL for feature engineering and model evaluation - Strong communication, able to work independently and in a team Counts as a bonus, not a requirement - Cloud services such as AWS, GCP or Azure, and ML platforms such as Kubeflow or SageMaker - Familiarity with systems programming or distributed systems - Visible contribution to the field such as technical blogs, papers or industry knowledge sharing What you would actually be doing - Independently developing machine learning models and generative AI solutions, with the emphasis on building and deploying agentic architectures - Driving AI agents end to end into production, handling multi step reasoning, tool use, state management and model orchestration in live environments - Designing LLMOps frameworks that give real observability, monitoring, logging and evaluation for agents - Refining and optimising both generative pipelines and existing classical models through feature engineering and hyperparameter tuning - Working with cross functional teams to turn business needs into technical solutions Location and working pattern A hybrid position based in Bangalore, reporting to the Manager of Machine Learning Engineering. A good fit if You have shipped machine learning before and want to move into agent based systems, on a security product where a mistake has real consequences. Security data is adversarial in a way most recommendation and forecasting work is not, because someone is actively trying to defeat your model. Think twice if You have only used language models through an API. The posting asks specifically for agents you have run in production, and repeats the point about non deterministic behaviour, which is where that experience shows.
What the posting requires - 4+ years in automation testing, preferably within an enterprise or cloud environment - A foundational understanding of AI and machine learning, and experience using AI driven approaches in your own domain, which Zscaler asks for across its engineering roles - The Python, Kubernetes and networking combination named in the title, all three of which the role genuinely depends on What you would actually be doing - Designing scalable, reusable and maintainable test automation frameworks using an AI first development approach - Writing and running end to end tests across ZDX components: cloud services, analytics dashboards, APIs and user facing applications - Working with engineering and DevOps to integrate testing pipelines into CI/CD so release cycles stay fast without losing quality - Using analytics tools, logs and test output to find bottlenecks and troubleshoot systematically - Continuously refining test methodology to improve coverage and catch issues earlier Location and working pattern Bangalore, in the Platform and Reliability Engineering department, reporting to the Director of Platform and Reliability Engineering. Zscaler operates a hybrid working model. A good fit if Your background is QA automation or SDET work and you want to go deeper into Kubernetes and networking. That combination is what makes this more valuable long term than generic test automation, and it is a realistic route out of pure manual or scripted QA. Think twice if You want to build product features. This is a testing, tooling and reliability role. Also do not treat the networking requirement as decoration: it is in the title, and ZDX is a network and digital experience product, so expect it in the interview.
What the posting requires - 5+ years as a software engineer or machine learning engineer - Experience applying machine learning to improve key business metrics, optimising models for both accuracy and latency - Experience researching newer techniques and innovating to build ML based solutions - Experience with the algorithms behind data collection and processing infrastructure, model training, and serving platforms - Deep expertise with AWS Counts as a bonus, not a requirement - A proven track record designing, building and shipping end to end applications at scale - Experience identifying and solving problems in data using machine learning systems - Familiarity with multi agent systems, agent architectures, prompt engineering and current AI frameworks What you would actually be doing - Building and maintaining large scale distributed systems covering the whole pipeline: data collection, feature engineering, model training, evaluation, deployment and real time serving - Writing functional specifications, assessing task requirements and scheduling, and staying involved through development, debugging and support - Solving problems such as threat detection and business intelligence in direct collaboration with data scientists, product management and product engineering Location and working pattern Based in Bangalore, reporting to the Manager of Machine Learning Engineering. Zscaler operates a hybrid working model. A good fit if You have several years of production machine learning and want an adversarial domain. Threat detection behaves very differently from the recommendation and forecasting problems most machine learning engineers see, because the data changes in response to your model. Think twice if You prefer modelling to infrastructure. A large part of this role is the distributed systems underneath the models, and the posting leads with that rather than with modelling technique.
What the posting requires - 13+ years in software development, with at least 8 of those specialising in production grade microservices - Hands on experience in a modern language such as Java, Go or Rust - Expertise in distributed data patterns including CQRS and event sourcing, and event driven communication using Kafka, RabbitMQ or SQS - Extensive hands on Docker and Kubernetes within AWS, Azure or GCP - Proficiency in both SQL (PostgreSQL, MySQL) and NoSQL (Cassandra, MongoDB or Cosmos DB) design and scaling - A foundational understanding of AI and machine learning, and experience applying it in your own domain Counts as a bonus, not a requirement - Implementing AI assisted engineering tools, or integrating predictive models to improve control plane resiliency and automated scaling - Service mesh technologies such as Istio or Linkerd - Practical chaos engineering and advanced performance testing What you would actually be doing - Leading the technical roadmap to modernise enterprise platforms using API first design and microservices - Designing and deploying highly resilient, low latency, event driven solutions, owning them from the API tier through to back end services - Setting coding standards, performing code reviews, and championing test driven and behaviour driven development - Partnering with product, DevOps and system architects to turn business needs into scalable technical solutions - Managing service lifecycles through Docker and Kubernetes, and monitoring health with tools such as Prometheus and Grafana Location and working pattern A hybrid role based in Bangalore, reporting into senior engineering leadership. A good fit if You have well over a decade of backend depth and want architectural ownership across a platform while staying hands on with code. Think twice if You are early or mid career. This is genuinely a 13 year role. If you are starting out, read the requirements as a picture of what deep backend specialisation looks like across a full career rather than as something to apply for now.
What the posting requires - 3 to 6 years in frontend engineering with shipped, production grade products - Deep React proficiency, TypeScript, modern CSS such as Tailwind, and strong component architecture instincts - State management with Zustand, Redux Toolkit or equivalent, plus solid async data patterns - Data visualisation experience with at least one of D3.js, Mapbox or Leaflet, Deck.gl for geospatial, or Recharts, used in production - REST and WebSocket integration, with enough backend awareness to debug across the boundary - Performance engineering: bundle optimisation, lazy loading and rendering performance in low resource environments Counts as a bonus, not a requirement - WebGL or Three.js for 3D visualisation - Electron or desktop application experience - Offline first or progressive web app architecture - Prior work on dashboards, command and control interfaces, or complex enterprise tooling What you would actually be doing - Building production grade interfaces for strategic sector and enterprise AI use cases, including geospatial overlays, simulation interfaces, ontology viewers and data ingestion dashboards - Owning the frontend layer of atoms end to end, from component architecture through deployment into client embedded environments - Building for genuinely constrained conditions: offline first, low bandwidth and limited hardware - Contributing to shared frontend infrastructure, component libraries, the design system and state management patterns - Joining field testing and client feedback loops alongside the deployment engineers Worth knowing before you self reject Sarvam adds a note to this posting saying it is looking for people who can own the outcomes described, not people who match every line of the specification. If the problem interests you and you believe you can do the work, the company is explicitly inviting you to apply. A good fit if You are a frontend engineer who wants to work close to real AI systems rather than on marketing pages, and you find hard constraints interesting rather than irritating. Think twice if You are used to shipping to modern browsers on fast connections and would rather not think about offline behaviour or locked down client machines. That constraint runs through the entire role.
What the posting requires - 3 to 5 years in machine learning engineering or MLOps, with at least one production language model or ML system in continuous operation - Deep model serving expertise using vLLM, TGI, Triton Inference Server or equivalent, including quantised formats such as GGUF, AWQ or GPTQ - Experience fine tuning and adapting models in constrained, on premise or air gapped environments, managing the data pipeline and compute limits those bring - Containerisation with Docker and Kubernetes, or lightweight alternatives such as K3s or K0s for constrained and edge deployments, across varied hardware - Monitoring and observability with Prometheus, Grafana or equivalent, including building custom evaluation dashboards - Python fluency, with familiarity with fine tuning workflows and model evaluation frameworks - CI/CD tooling for ML pipelines such as GitHub Actions, ArgoCD or DVC The signals they say they look for - You have kept a production ML system running under load, and debugged it when it broke - You do not wait for failures, you build systems that warn you before they happen - You write documentation that people other than you actually use What you would actually be doing - Designing and operating model serving infrastructure across on premise and cloud deployments - Building CI/CD pipelines for model updates, rollbacks and evaluation gated releases - Monitoring latency, accuracy drift, throughput and failure modes, and building systems that surface problems before clients notice - Building evaluation infrastructure: harnesses, A/B testing and model comparison tooling for both lab and field use - Managing containerised serving in constrained, air gapped and edge environments - Writing runbooks and operational playbooks for deployment engineers in the field - Owning incident response for model layer failures across every active deployment Location and working pattern Based in Delhi rather than Bengaluru, which is worth noting because most Indian AI roles cluster in Bangalore. A good fit if You would rather keep models running reliably than train them, and you treat uptime and correctness as equally non negotiable. Think twice if You want research or modelling work. This is squarely infrastructure, reliability and operations, and the air gapped and edge constraints mean the usual managed cloud conveniences often are not available.
What the posting requires - 4 to 8 years in data infrastructure, data engineering, platform engineering or site reliability engineering, ideally somewhere operating at significant data scale - Direct experience managing multi terabyte data stores, having personally built or operated systems holding 10TB or more with sustained high throughput ingestion - Deep working knowledge of at least two of PostgreSQL, MongoDB, Elasticsearch, ClickHouse or comparable systems, including tuning, indexing, partitioning and operational management - Production ingestion pipelines built with Kafka, Spark, Airflow, Flink, dbt or equivalent - Strong Python and/or Go, writing production infrastructure tooling and automation - Solid understanding of storage systems and formats: object storage such as S3 or MinIO, columnar formats such as Parquet and ORC, and how to pick the right layer for a workload - Containerisation and orchestration with Docker and Kubernetes in production - Infrastructure as code and deployment automation with Terraform or similar Counts as a bonus, not a requirement - Vector databases or embedding stores such as Milvus, Weaviate, Qdrant or pgvector - Deploying and operating infrastructure in air gapped, on premise or hybrid environments What you would actually be doing - Designing and operating storage architectures across relational, document, vector and object stores at terabyte scale and across multiple data types - Building ingestion pipelines that reliably handle daily influx across both batch and streaming workloads - Making the decisions on indexing strategy, pipeline orchestration and system performance - Owning reliability and performance of the infrastructure layer for your assigned accounts Location and working pattern Delhi based, working closely with teams deployed at client sites. Worth knowing before you self reject As with its other openings, Sarvam notes it wants people who can own the outcomes described rather than people matching every line of the specification. A good fit if You are a data or platform engineer comfortable working at customer sites and making architecture decisions without a managed cloud safety net. Think twice if You want to stay on internal systems with modern tooling. Air gapped and operationally sensitive environments are the norm here, not the exception.
What the posting requires - 5+ years of backend or data platform engineering, with a meaningful part of it designing and operating analytics systems in production - A track record of building zero to one platforms that other engineering teams depend on - ClickHouse in production at scale: sharding, replication, MergeTree variants, materialized views, projection design, query tuning, and the operational side including backups, upgrades and capacity planning - Go for high throughput backend services, with a strong grasp of concurrency, performance and API design across REST and gRPC - Kafka as a primary streaming backbone: partitioning strategy, consumer groups, exactly once and idempotency patterns, and schema registry - Debezium based change data capture, built and operated from transactional databases into analytical stores - Strong systems instincts, reasoning about throughput, latency, cost and failure modes before writing code Counts as a bonus, not a requirement - Spark and Airflow for batch enrichment, backfills and scheduled aggregation - Multi tenant SaaS platforms with row level security, per tenant quotas and tenant aware access control - Building or integrating BI and dashboard tools such as Superset, Metabase or Cube, especially embedded customer facing analytics - Exposure to billing or metering data feeds where correctness is not negotiable What you would actually be building - A high throughput event ingestion API in Go that accepts arbitrary event payloads, validates them, and lands them in ClickHouse with automatic table creation - Change data capture replication from product databases into the analytics store - A tenant aware query API and no code dashboard layer feeding customer analytics, internal reporting and billing Location and working pattern On site in Bengaluru, working with a small team of senior engineers. The posting says this directly, so treat it as an on site role rather than hybrid. A good fit if You want to be the technical owner of a foundational platform rather than a feature contributor on someone else's system, you like writing design docs as much as code, and you think about cost per query as well as latency. Staff here means senior individual contributor, so the scope is architectural. Think twice if You prefer a defined slice of an existing system, or you need hybrid or remote flexibility.
What the posting requires - 4+ years of experience in software development - Proficiency in at least two of Rust, Go and Python - Good networking fundamentals and systems knowledge, with exposure to open source technologies - Strong data structures and algorithms - Experience with or knowledge of operating systems and current technologies Counts as a bonus, not a requirement - Awareness of cloud technologies, Mesos, KVM or QEMU, and NodeJS or React What you would actually be doing - Gathering product requirements and designing solutions with stakeholders across different domains - Developing and maintaining in house cloud architecture components, including procurement, provisioning, patching, migration and retirement of instances - Owning implemented solutions end to end, from inception through deployment, monitoring and regular upkeep - Identifying infrastructure wide and company wide problems and providing scalable solutions - Measuring and increasing compliance of those solutions, and bringing a DevOps mindset to how they are implemented Location and working pattern Bangalore. Also worth knowing PhonePe lists a substantial benefits package for full time staff: medical, critical illness, accidental and life insurance, an employee assistance programme with an onsite medical centre, maternity and paternity benefits with adoption and day care support, relocation and transfer support, provident fund, gratuity and leave encashment, plus higher education assistance, car lease and a salary advance policy. A good fit if You are a backend or infrastructure engineer who wants to write Rust professionally rather than as a side project. Roles that will pay you to work in Rust in India are genuinely uncommon, and that is the strongest reason to look at this one. Think twice if You want consumer product work. This is internal reliability and cloud tooling. The posting also asks for two languages rather than one, so pure Python engineers with no systems language exposure are a weaker match.
What the posting requires - 5 to 9 years of full time iOS app development, with strong fundamentals and end to end exposure - Strong system design and architecture skills specifically for iOS, not general mobile experience - Hands on experience with modern iOS technology: Swift, UIKit and SwiftUI, MVVM or VIPER architecture, Combine, Core Data and dependency injection frameworks - Experience with unit testing and UI testing across full end to end app development - Strong problem solving, plus what the posting describes as curiosity to tinker and explore new paradigms Counts as a bonus, not a requirement - Experience developing SDKs Location and working pattern Pune, which is unusual for PhonePe engineering roles and worth knowing if you are based in Maharashtra. Also worth knowing PhonePe lists medical, critical illness, accidental and life insurance, an employee assistance programme with an onsite medical centre, maternity and paternity benefits including adoption and day care support, relocation and transfer support, provident fund, gratuity and leave encashment, plus higher education assistance, car lease and a salary advance policy. A good fit if You are an experienced iOS engineer who wants consumer scale rather than enterprise app work, and you are interested in the problems that only appear at very large install bases. Think twice if You are earlier in your mobile career. The band starts at five years of full time iOS work specifically, so treat it as a target to grow toward rather than a stretch application. If you are a cross platform developer working mainly in React Native or Flutter, note that the requirements are consistently native.
Added July 20, 2026
No years stated. Data pipeline work: ingestion, processing, indexing.
No years stated. Familiarity with OWASP Top 10 and finding real issues.
No years stated, but Go experience is required.
2 to 5 years backend. Java, Spring Boot, Elasticsearch, MongoDB.
2 to 3 years in firmware, embedded systems or a related field.
No years stated. Fullstack, with support from senior and staff engineers.
Bachelor's or master's in CS. About 2 years in test automation or SDET.
About 2 years in test automation. Strong Java, RestAssured, Selenium.
⚠️ Eligibility changed on this posting and we have corrected it. ChargePoint edited this same requisition after we first listed it. It originally read "B.A / B.Com / BBA graduates only" and it now reads "Only BCA/B.Sc. graduates", with the body asking for a bachelor's degree (BCA or B.Sc) from the **2025 or 2026 batch**. If you are a B.A, B.Com or BBA graduate, you are no longer eligible for this one, and we are sorry if you saw the earlier version here. Required by the posting: a bachelor's degree, BCA or B.Sc, 2025 or 2026 batch. **Fresher or a minimum of 1 year of experience** as a Technical Support Engineer providing phone support. Excellent English communication, described as a must. The ability to read and understand site drawings, field repair guides and product specifications. Exceptional troubleshooting and advanced analytical thinking for resolving complex issues that span hardware and software. Ability to convey complex concepts clearly in writing and verbally. Account management skills, including investigating current and historical issues for specific accounts. Ability to work with minimal supervision. A tenacious commitment to customer focused support, and comfort making complex decisions. Nice to have: additional certification in Microsoft, Linux, networking or similar technologies. Familiarity with Jira or other bug management tools. The real day to day: providing technical and network problem resolution to end users by diagnosing issues and engineering solutions. The posting lists the actual mechanics: adjusting network configurations, verifying and applying correct software configurations, working with field technicians to troubleshoot and correct physical installation issues, and compiling, pulling and parsing station and network logs. Where an issue is large enough you work directly with the product and engineering teams. You also create test plans, test cases and other documents based on software specifications. Reporting line and location: reports to the Senior Manager, Technical Support. Bangalore, India. Honest fit guidance: this is a support engineering role, not a software development one, so you would be debugging and configuring rather than building. That said, it is one of the very few postings on this board that says "Fresher" in its requirement list, and hardware plus software fault diagnosis on an EV charging network is a real technical foundation. If you are a 2025 or 2026 BCA or B.Sc graduate, this is worth a careful application.
About 2 years of integration development across enterprise systems.
Strong Java and OOP. Bachelor's in maths, CS or similar. About 1 year.
Bachelor's or master's in CS. About 1 year in test automation or SDET.
About 1 year building tools or test automation.
Basic Java, Linux and CI/CD. About 1 year of experience.
Any technical degree. No years of experience stated in the posting.
Strong ReactJS and TypeScript. No years of experience stated in the posting.
Added July 18, 2026
About 1 year of experience. Degree in Computer Science, Information Security or related.
About 1 year of experience. Hybrid working from Bangalore.
1 to 3 years. Linux systems and middleware experience.
1 to 3 years. QA for IoT devices. Five days per week in office.
About 1 year of experience in systems or cloud infrastructure.
About 1 year of experience. Interest in reliability engineering and production systems.
About 1 year of Android development experience. Kotlin or Java.
About 1 year of experience. Interest in security automation and DevSecOps.
About 1 year of experience in information security, privacy or compliance.
About 2 years of experience. Production troubleshooting, automation and observability.
About 2 years of hands on high performance computing experience.
About 2 years of Python experience. Data analysis, automation and visualisation.
2 to 4 years. SQL, data modelling and BI tooling.
About 2 years. Strong statistics and evaluation design.
About 2 years. Comfort working directly with client data and stakeholders.
About 2 years. Building with LLMs, APIs and production systems.
About 2 years. Linux, GPU infrastructure and cluster operations.
2 to 4 years as a data engineer. Cloud warehouses and pipelines.
About 2 years. Comfort analysing logs and test data.
2 to 5 years in operations engineering or production support.
About 3 years of data engineering experience. Pipelines and warehousing.
About 3 years of backend engineering experience.
1 to 3 years in network operations or network engineering. Entry level scripting in Python or Go. Knowledge of VxLAN is an advantage.
1 or more years in a similar technical support role. Comfort debugging customer facing issues.
About 2 years each with Terraform, configuration management and Linux administration.
Entry level backend software engineering role (SDE I) on the CommerceIQ engineering team in Bengaluru. Open to 1 to 3 years of experience.
Early career software engineer joining the Instawork Robotics Labs team in Bengaluru.
SQL, PL/SQL and data modeling. Oracle ERP Cloud Financials (BIP and OTBI reports).