What this edition tells you
Today has something this list has not had before: a real new graduate job that is also remote. Twilio's Software Engineer (L1) states no years of experience anywhere in the posting, calls the people in it New Grad Software Engineers, and asks for a Bachelor's or Master's in computer science. If you graduated this year, that is the one to spend your effort on. It is remote across five states, Karnataka, Tamil Nadu, Telangana, Maharashtra and New Delhi, so check yours before you apply.
The reason it exists is that we added ten new company boards today. Entry level had been at zero or one for eight editions running, and the honest reason was our sources: enterprise boards do not carry graduate hiring, and we had already published every junior role on them. So Tekion, Sigmoid, Zeta, Druva, Turing, Sumo Logic, Atlan, Skyflow and Amplitude appear here for the first time. Two things came out of that. Remote went from one role yesterday to five today, including a remote backend job at Skyflow, which is the single thing readers reply asking for most. And no company is more than 4 of the 30, where yesterday two companies were 14 of 30.
One warning before the list. Titles are misleading in both directions again, and today so is a location. Druva calls a 3 to 5 year job "Staff Software Engineer (AI)" while its Senior Staff postings ask 5 to 7 and 6 plus. And Turing's board says "India - Remote" while the posting body says Bangalore, in office, hybrid. We have listed it as Bangalore hybrid, because the body is the specific statement. Read the years and the location clause, not the title.
No roles match that combination.
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: 3 to 5 years of experience in software development, and a bachelor's degree in computer science, engineering or a related field. A strong understanding of full stack development and system design. The day to day: design, develop and maintain software features and services across the application stack. Participate in design discussions and give input on system architecture and component design. Collaborate with cross functional teams to gather requirements and deliver technical solutions. Optimise performance and improve the development process. How Tekion frames the level: the posting states you work with minimal supervision on standard tasks and need guidance only on highly complex or strategic issues, and that engineers at this level are recognised for quality code and consistent delivery. That is a fair description of a self sufficient mid level engineer. Location: Chennai. Office days are not stated on this posting. Who should apply: engineers three to five years in who want product ownership at a company selling into a traditional industry rather than to other software companies. Tekion runs four openings on today's list at four different levels, from a 2 to 4 year QA seat up to an 8 or more year backend staff role, so you can pick the rung that matches you instead of stretching for one that does not.
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: 4 to 6 years of experience in data engineering or a closely related discipline. The day to day: design, develop and maintain data pipelines, data models and data platform services across the Bronze, Silver and Gold layers. Participate in data architecture discussions and contribute to decisions on pipeline design, data modelling and platform components. Build and enforce data quality checks at every layer, including schema validation, null checks, referential integrity and business rule assertions. Design pipelines with end to end reconciliation in mind so row counts, aggregates and key metrics can be traced and validated from source systems through to Gold layer outputs. Work independently on complex data engineering features while collaborating with peers, including on AI assisted data products. Location: Bengaluru. Office days are not stated on this posting. Who should apply: data engineers four to six years in who have owned production pipelines and care about lineage and reconciliation, not only about getting the job to finish. Tekion carries the same Software Engineer II title in Chennai at 3 to 5 years for general application development, so check which of the two matches your background before applying: the title is identical and the work is not.
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: 8 or more years of backend engineering experience with a strong track record delivering production grade Java systems. The day to day: own core domain models and service boundaries end to end, from initial hexagonal design through production operation, Kafka event contracts and iterative enhancement. Build scalable, secure REST APIs and robust Kafka based event driven pipelines that consume and produce events across multiple source systems. Design MongoDB document schemas and PostgreSQL relational schemas for high throughput multi tenant workloads, with attention to indexing strategy, TTL and tenant isolation patterns. Design Cosmos DB data models for high throughput event and state storage, covering partition key strategy, consistency levels and TTL configuration. Act as the technical anchor defining architecture patterns for the area. What the services do: power customer intelligence, campaign orchestration and attribution for Tekion's automotive retail platform, which serves dealerships, manufacturers and partners. Location: Chennai. Office days are not stated on this posting. Who should apply: backend engineers eight or more years in whose main language is Java and who have designed event driven systems, not only consumed them. The multi database requirement is genuine: the posting asks for document, relational and Cosmos DB modelling in the same role, so be ready to talk about partition keys and consistency levels as well as indexing. Tekion has four roles on today's list from 2 to 4 years up to this one, and this is the top of that range.
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.
Read this before you apply
- The five remote roles, named, so you do not have to hunt for them. Twilio Software Engineer (L1) and Software Engineer L3, both remote India but only in Karnataka, Tamil Nadu, Telangana, Maharashtra and New Delhi. Atlan's two security roles, both marked remote on Atlan's own board with India as the location. Skyflow Senior Software Engineer, remote, and the only remote backend role of the five: the posting opens "As a Backend Software Engineer" and the work is privacy APIs in Go.
- Zeta's Product Security Engineer II contradicts itself on experience, so apply even if you are at 2 years. One bullet asks 4 plus years building large scale internet or SaaS applications. The next asks 2 to 3 years as a web or mobile application security engineer. We published the higher number rather than the flattering one. Two other things about it: it wants bug bounty history on HackerOne or Bugcrowd, and it asks for a Tier 1 engineering college, which is a real filter rather than a preference.
- Sumo Logic's Staff SRE years line looks like a copy paste error. It asks for "8+ years of professional experience in applied software security role" in a posting that is otherwise pure site reliability work, and its Senior SRE I twin is the same posting asking 4 to 6 years of industry experience. If your background is SRE and not security, apply anyway and ask. We published 8 because that is what it states.
- Tekion has four roles here at four different levels, and the same title means different jobs. Its Software Engineer II in Chennai is general application work at 3 to 5 years. Its Software Engineer II in Bengaluru is data engineering at 4 to 6. Its SDTE II in Chennai asks 2 to 4 while the Bengaluru SDTE II asks 4 plus. Check which city and which body before you apply, because the titles do not tell you.
- PhonePe is posting the same job description under different titles, third edition running. It ran three near identical SRE requisitions today and one Service Delivery Engineer carrying a byte identical body. We published one. The one here is real private cloud systems work: Linux, KVM and QEMU, SaltStack, MySQL, in its own data centres, which is a different skill set to cloud console work.
- Two we would apply to first. At the junior end, Sumo Logic's Senior Backend Engineer at 4 to 6 years: distributed systems plus real agentic AI work, and the posting is honest that long running multi agent reliability is unsolved. At the senior end, Skyflow, because a remote backend role at 8 plus years with Go and performance engineering is genuinely rare.
We read every posting by hand before it goes on this page. The same write-up goes out to the daily email.