What this edition tells you
Today's finding is unusual. Tekion moved its entire job board from one hiring system to another overnight. Yesterday its listings were on Greenhouse; today that board returns "not found" and everything has reappeared on Ashby with new ids. Same company, largely the same jobs, but every stored link is dead.
That defeats duplicate detection entirely. We match jobs by their id on the hiring system, so all 26 Tekion roles looked new today even though several were ones we posted this week. A company switching hiring systems is indistinguishable from a company closing every requisition and opening new ones. Because the old descriptions are now unreachable, we could not separate the genuinely new roles from the reposts, so Tekion is left out of today's edition entirely. It also expired 17 Tekion rows from the board. Those jobs are likely still open at new links, and we will re-check tomorrow.
In the same vein: Everpure is reposting jobs under fresh ids. Two of its listings today were 99 percent identical to ones we published on 1 and 3 August. Same job, new reference number. If a listing looks familiar, it may be.
Remote went from 1 yesterday to 3 today, each verified by reading the posting body rather than trusting the tag.
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+ 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. 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 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.
Read this before you apply
- The three genuinely remote roles, with their catches stated. Twilio's Software Engineer L2 is remote but only if you live in Karnataka, Tamil Nadu, Telangana, Maharashtra or New Delhi, and it is a frontend role (React, TypeScript, GraphQL) despite the general title. Neo4j's Cloud Operations Engineer is remote India with no restriction we could find, but the first responsibility listed is an on call rotation. Databricks' Forward Deployed Engineer is remote with 20 percent travel to customers, stated in the posting.
- Nothing today asks for under 3 years. The floor is Twilio's L2 at 3 years, and it happens to be the remote one, which is unusual and good. If you are early career, use the experience filter on the page and set it to 0 to 1 yr, because roles from earlier editions are still open there.
- Six roles publish no years figure at all , so they sit in no experience bucket on the page. That is Fivetran (2), Starburst, Composio, Zscaler and Smartsheet. we would rather leave the field blank than invent a number. Composio is the interesting one: it writes its requirements as capabilities rather than years, which gives an unconventional background a real chance.
- Check Fivetran's hiring priority before you apply to it. Fivetran publishes an internal status field on some jobs, and two of its roles today are marked "Future Open" and "Internal Resources". Those apply pages load perfectly normally. The jobs are not open to outside applicants. Same two roles as yesterday, so this is how they operate rather than a one off. we published only the ones with no flag.
- Three companies have a number in their opening line that has nothing to do with you. Smartsheet opens "For over 20 years", Thoughtworks opens "For 30+ years", Tekion says its industry has not innovated "in over 50 years". Any tool reading years automatically swallows those. It is why we read every figure by hand.
- Two office warnings. Thoughtworks says in writing you may be expected in a Thoughtworks or client office all five working days, and its own board data says "Remote Eligible: False", while the posting still carries a remote tag. Smartsheet tags all its India roles remote while the job titles themselves say "Hybrid in Bangalore". Second day running for Smartsheet.
- Agoda publishes something almost nobody does. Its Staff Backend role states you stay hands-on with coding and system design 50 to 60 percent of the time. At staff level that number is normally left vague, and you can hold them to it.
We read every posting by hand before it goes on this page. The same write-up goes out to the daily email.