No roles match that combination.
Added August 1, 2026
What the posting asks for: - 6 months to 1 year of relevant work experience. This is the stated bar and it is genuinely junior. - SRE experience with large production environments. - Natural curiosity, close attention to detail and strong troubleshooting instincts. - Ability to analyse a complex system and then explain it in simple terms. - The team works in Go, Java, Python, C++ and Linux. The posting asks which of those you use rather than demanding all of them. What the job actually involves day to day: - Leading investigations into emerging customer issues and engineering the fix. - Building services and AI tooling that diagnose and protect the installed fleet. - Designing analytics that monitor fleet health and flag problems before customers hit them. - Working across most of the engineering organisation, which the posting frames as a fast route to learning the whole codebase and building an internal network. - Representing customer problems back to engineering peers, and sometimes representing engineering in front of customers. - Taking part in an on call rotation that responds to outages worldwide. Location and office reality: Bangalore. Everpure states across its postings that it is primarily an in office environment and expects attendance at the Bangalore office outside leave and work travel. Honest fit guidance: the years bar is low but the work is not easy, and on call is part of it from the start. If you want a first or second job where you are handed hard debugging problems on real production systems, apply. If you are looking for a role with no customer contact and no pager, this is not that role.
What the posting asks for: - 3+ years of systems programming experience, with real depth in C, C++, Python, Go or Java and a track record of shipping robust, scalable software. - Practical low level knowledge in at least one of: distributed systems, operating system internals (specifically the Linux kernel), database internals, hypervisors, or container orchestration. - The ability to turn a complex problem into a clean design, working inside a peer review heavy engineering team. What you would work on: - Designing and implementing high availability algorithms and data structures targeting 99.9999 percent reliability for enterprise storage. - Owning features end to end, from prototype through to production code. - Diagnosing deep technical bottlenecks in distributed systems and kernel level software. - Integrating FlashArray services with public cloud providers so customers can run hybrid cloud workloads. Location and office reality: Bengaluru. The posting states plainly that Everpure is primarily an in office environment and that you are expected to work from the Bengaluru office except when on leave or travelling for work. Treat this as a five day in office role unless the recruiter tells you otherwise. Honest fit guidance: three years is the floor, not the target, and the low level requirement is real. If your experience is entirely web or application development with no exposure to operating systems, storage or distributed infrastructure, expect the interview to go into territory you have not covered.
Core requirements: - Bachelor's degree in computer science or a related technical field, or equivalent practical experience. - 4+ years of professional experience designing, developing and testing product components in Go, Java or C++. - Strong grounding in microservices architecture, distributed systems, and building production grade platforms in the cloud. - Solid computer science fundamentals: data structures, algorithms and software design. - A collaborative working style. The posting emphasises open, team oriented development. Preferred, described by the employer as what gives you a head start: - Hands on Kubernetes and container experience. Prior Kubernetes control plane development is called a major plus. - Building and integrating authentication (SSO, LDAP) and authorization (RBAC, OAuth) frameworks. - Familiarity with e-commerce marketplace integration projects. - Automating SaaS billing, usage reporting, or building telemetry systems that pull insight out of production services. - Prior experience building public facing SDKs. Day to day: building and scaling SaaS microservices inside the Portworx product line, owning the full engineering lifecycle including CI/CD, partnering with product management and early adopter customers, and experimenting with new technology to optimise the cloud infrastructure underneath. Location and office reality: Bangalore. The posting states the team works in office and that you will be based out of the Bangalore office outside approved leave or work travel. Honest fit guidance: the Kubernetes items are genuinely optional, so do not screen yourself out for lacking them if your Go or Java backend and distributed systems work is strong. The four year bar is a floor.
What the posting asks for: - 4 to 7+ years developing on Linux or another UNIX variant at a product company. - 3+ years working with remote teams at a product company. - Bachelor's degree or higher in computer science, computer engineering or electrical engineering. - Significant domain knowledge of the networking stack. - Systems development experience covering IPv4 and IPv6 networking protocols, API design, distributed systems and/or device drivers. - Familiarity with modern switch silicon packet processing and features such as ECMP, QoS and packet filtering. - Hands on experience with the Broadcom SDK. - Linux kernel or device driver experience. - Strong problem solving, debugging, algorithmic and coding skills. Explicitly NOT required: - Storage experience. The posting says it is desirable but not necessary. That is unusual for a storage company and it is the reason a pure networking engineer should read this one. Day to day: full lifecycle software development from architecture through release and maintenance, requirements analysis, cross team integration work, contributing to the architectural direction of the FlashBlade networking area, and designing, coding and debugging in C and Python. Location and office reality: Bangalore. Everpure states across its postings that it is primarily an in office environment. Honest fit guidance: the band is wide (4 to 7+) and the Broadcom SDK and switch silicon items are the real filter here, more than the year count. If you have done Linux networking or driver work, the storage gap is not the problem you might assume it is.
What the posting asks for: - BS in computer science. - 7+ years designing, developing and testing enterprise products, with Golang preferred. - Good understanding of microservice architectures and cloud native platforms. - Experience designing and owning microservices that operate and scale in a distributed system architecture reaching thousands of nodes. - Expert debugging skills, and comfort navigating ambiguous problems at scale in public and private cloud environments. - Experience working with internal and external stakeholders, from product management through to customer beta partners. - Solid computer science background in data structures, algorithms and software design. - Willingness to work in an open office environment. The posting says this directly. Day to day: designing and developing cloud native microservices for Portworx, code review and test discipline, CI/CD, debugging product and performance issues in large scale clusters using AI tooling, and taking features from initial design through to production while absorbing customer feedback. Location and office reality: Bangalore. The posting states Everpure is primarily an in office environment and that you are expected to work from the Bangalore office outside leave or work travel. It also names the open plan office explicitly, which is worth knowing if that matters to you. Honest fit guidance: this is a real senior role, not a mid level one with an inflated title. If your Go experience is light but your Java or C++ distributed systems work is strong, it is still worth applying, since Golang is stated as preferred rather than mandatory.
What the posting asks for: - 10+ years of strong expertise in C++, Java, Go or related programming languages. - Experience across one or more related systems software areas: distributed systems, operating systems, the Linux kernel, file systems, database internals, hypervisors, containers or compiler optimisation. - Proven design sensibility and a willingness to work collaboratively. - BS degree in computer science. Advanced degrees are described as a bonus. - Willingness to work in an open office environment. Day to day: designing and implementing new algorithms and technologies for high performance, highly scalable and highly reliable systems, with a six nines reliability target. Owning innovation end to end from concept through to shipped product, and solving hard problems that need persistence rather than a quick answer. Location and office reality: Bangalore. The posting states Everpure is primarily an in office environment and you are expected to work from the Bangalore office outside PTO, work travel or approved leave. Honest fit guidance: ten years is the stated floor and the systems software requirement is not decorative. This is not a role to stretch into from application development. That said, the posting's own line about learning system software from scratch suggests they will consider strong systems generalists who have not specifically worked on storage datapaths.
What the posting asks for: - 5+ years in the software industry with a strong focus on quality, automation and engineering excellence. - Deep understanding of object oriented principles and strong Java proficiency. - Expertise designing scalable automation frameworks and identifying negative, edge and high risk scenarios. - Strong understanding of distributed systems failure modes: schema drift, idempotency failures, data inconsistencies and race conditions. - Hands on experience with cloud platforms (AWS, GCP, Azure) and containers (Docker, Kubernetes). - Experience building and maintaining CI/CD pipelines with Jenkins, CircleCI or Buildkite. - Experience with backend automation frameworks. - Demonstrated ability to use AI and LLM tooling to accelerate development, debugging and test design. Strong plus: database testing and ETL or data pipeline validation. Technologies named: Java 11, JUnit5, Docker, Kubernetes, AWS, GCP, Terraform, WireMock, RestAssured, Bazel, BuildKite. Day to day: designing and evolving Java automation frameworks with an emphasis on reliability and data correctness, writing test strategies for complex features, hardening CI/CD so silent failures and regressions get caught, and building internal AI tooling that speeds up debugging, generates test scenarios, spots flaky patterns and improves log analysis. You would also coach other quality engineers. Location and office reality: Bangalore, full time, hybrid with two days a week in the office. That is stated in the posting and is lighter than most roles in this edition. Honest fit guidance: this is an engineering role that happens to sit in test. If your background is manual testing without strong Java and distributed systems knowledge, the requirement list will not bend for you. Company context: read up on the dbt Labs merger before interviewing, since the org is mid integration.
What the posting asks for: - 5+ years of experience. - Strong technical and problem solving skills with recent hands on software development. - Experience with reliable distributed systems, with an emphasis on high volume data management in enterprise or web scale platforms operating under strict SLAs. - Broad technical knowledge spanning software development and automation. - Wide familiarity with algorithms and data structures. - Expertise in Java, AWS, cloud based APIs, databases, software design and programming best practice. - Ability to identify design flaws in existing systems and propose improvements. - Ability to use conversational AI systems such as Claude or ChatGPT to research, author and review engineering documents including technical design documents, postmortems and test plans. - Entrepreneurial mindset with strong communication and technical leadership. Bonus skills: experience with ETL and ELT pipelines, and performance engineering. Technologies named: Java, SQL, Kubernetes, Docker, AWS, GCP, Azure, Buildkite. Day to day: working with cloud APIs, SQL and NoSQL databases and event streams; working on the core data pipeline that moves terabytes from customers into their warehouses; and processing that data into clean, incremental, automated updates. You are also expected to own technical quality for your team's services, review code, contribute to architecture and mentor junior colleagues. Location and office reality: Bangalore, full time, hybrid with two days a week in the office. Honest fit guidance: mentoring is part of the role but there is no people management in it, so it stays an individual contributor seat. If you have five years of Java backend work at data scale, you clear the bar as written. Company context: the dbt Labs merger is live, so expect both brands in the process.
What the posting asks for: - 9+ years of experience working with SaaS products at scale. - Working knowledge of managed Kubernetes across EKS, AKS and GKE. - Knowledge of cloud platforms and the surrounding tooling: AWS, Azure, GCP, Terraform, Ansible, Buildkite, Pulumi and ArgoCD. - Experience with Python and shell scripting. Java or Go is a bonus. - Experience with Linux operating system internals and administration. - Experience with cloud networking including VPNs, PrivateLink and Private Service Connect on GCP. - Experience with databases such as PostgreSQL. Day to day: owning the ongoing reliability and robustness of Fivetran's production infrastructure, the robustness of the deployment pipeline, and timely incident response and resolution. The posting frames the role as driving both effective incident response and overall issue avoidance, and you would work closely with engineering teams, product managers and support and sales engineers. Location and office reality: Bangalore, full time, hybrid with two days a week in the office. Honest fit guidance: nine years is unusually specific and unusually high for an SRE posting. If you are at six or seven years with strong multi cloud Kubernetes and incident command experience it may still be worth an application, but understand you are applying under the stated bar. Company context: the dbt Labs merger means the platform surface is likely to grow during your first year.
What the posting asks for: - 8+ years of professional software development experience. - 5+ years specialising in large scale, production grade ReactJS and Redux applications. This is the real filter, not the overall year count. - Ability to translate complex UI and UX designs into robust production applications. - Frontend best practice depth: modularity, semantic code, comprehensive automated testing and performance tuning. - Experience defining clean API contracts and integration roadmaps with backend teams. - A focus on accessibility (a11y) and research driven method. Day to day: designing and building ReactJS solutions while mentoring other engineers, shaping and evolving Zscaler's core design system, partnering with DevOps on CI/CD, evaluating emerging frontend technology, and leading systematic refactoring work aimed at long term scalability and maintainability. Reporting and scope: the role reports to the Manager of Software Development Engineering. The posting describes technical mentorship and leadership but no people management responsibilities, so this is a senior individual contributor position. Location and office reality: Bangalore. Zscaler runs a hybrid working model and tags this posting #LI-Hybrid. The posting does not state how many days per week, so ask. Honest fit guidance: if your React experience is real but has been on smaller applications, the five year large scale requirement is where this will be judged. Zscaler also states across its postings that it wants people actively using AI tooling to increase their output, and that theme recurs in its interviews.
What the posting asks for: - 8+ years of experience designing and implementing networking security software and public cloud infrastructure. - Strong public cloud knowledge combined with technical expertise in network security. - Hands on development experience. This is explicitly not an architecture only role. - Proven leadership capability in a technical sense. Day to day: participating in the design, development and optimisation of firewall and secure web gateway platforms running in cloud infrastructure; executing the technical roadmap for those platforms; working closely with engineering teams to improve platform support for virtualised environments; and contributing to the growth of other team members. Reporting and scope: reports to the Senior Manager, ZIA Core Engineering, in the ZIA Cloud department. The responsibilities list contains no people management, so this is a senior individual contributor seat despite the Staff title and the mention of developing team members. Location and office reality: Bangalore, stated in the posting as a hybrid role. The number of office days is not published. Honest fit guidance: the OpenSSL and C protocol depth in the title is the actual requirement. General backend experience at eight years will not carry this interview. Zscaler is also explicit that it wants engineers who use AI tooling actively, which appears in the culture section of every one of its postings.
What the posting asks for: - 12+ years in security engineering or product security. - Within that, 7+ years hands on driving and scaling vulnerability and exposure management programmes in complex environments. - The ability to work both strategically and deep in the technical detail: findings, coverage gaps, scanner limitations and remediation paths. - A builder mindset. The posting repeats this framing throughout. Day to day: - Leading vulnerability and exposure management across infrastructure, cloud, APIs and containers, evolving it from a reporting role into a product security engineering capability. - Defining risk based prioritisation models that go beyond standard CVSS by folding in threat intelligence and business context, in order to cut noise and duplicate findings for engineering teams. - Designing and deploying automated data pipelines, scripting and workflow orchestration across the whole lifecycle: asset discovery, authenticated scanning, triage, routing and validation. - Driving external attack surface management to map internet facing assets, and identifying programme gaps such as unauthenticated scans and stale asset ownership. - Influencing engineering teams rather than directing them. Reporting and scope: reports to the Senior Manager, Information Security Engineering, in the Product Security department. The posting states directly that you operate as an individual contributor. Location and office reality: Bangalore, hybrid. Days per week are not published. Honest fit guidance: twelve years is real and so is the seven year vulnerability management specialisation. If your security background is broad but you have not owned a vulnerability management programme end to end, this is a stretch. If you have, the automation emphasis here is a better job than most roles with this title.
⚠️ Shift: the posting states plainly that this role requires working USA working hours, 8:00 pm to 5:00 am IST. Read that first. Everything below is secondary to whether a permanent night shift works for your life. What the posting asks for: - 3+ years of hands on software engineering experience, including time in a customer facing or escalation engineering role. - Programming, database, API and UI expertise sufficient to resolve critical customer issues end to end. - The communication range to work across engineering, support and customer facing teams. Day to day: owning complex technical escalations coming from the success and support organisations and resolving them at code level; driving longer term improvements to how the product is built, debugged and supported at scale; and helping the company adopt AI across support workflows, tooling and troubleshooting. Where the team sits: the Customer Engineering team is described as the intersection of product engineering and the success and support organisation, acting as the deepest technical escalation layer for the most critical customer issues. Location and office reality: Hyderabad. The posting does not publish an office day policy, but it does specify the US shift. Honest fit guidance: this is a good role for an engineer who likes debugging other people's systems and wants customer exposure early. It is a poor role if you want to build features on a roadmap. Do not apply because the years bar is low and then discover the shift, since the shift is the trade you are making.
What the posting asks for: - 3 to 5 years building production search, retrieval, knowledge base or recommendation systems. Day to day: - Building a unified retrieval layer across enterprise systems including Google Drive, SharePoint, Confluence, Jira, Asana, Zendesk, Freshdesk, Salesforce and Notion, exposed through a clean agent friendly interface. - Designing hybrid retrieval pipelines that combine lexical search (BM25), dense vector retrieval and structured SQL or graph retrieval, with re-ranking tuned for cross source results. - Engineering ingestion and freshness pipelines that incrementally sync millions of documents, tickets, tasks and CRM records at low latency and predictable cost. - Shipping production grade observable systems with strong service level objectives on latency, freshness, recall and cost, plus the dashboards and tracing to evidence them. The genuinely hard parts, named by the employer: heterogeneous content types, heterogeneous permission models where every source has its own access control list, and real freshness constraints. Scope: described in the posting as a hands on senior individual contributor role for someone who wants to go deep on retrieval quality. Location and office reality: Hyderabad. No office day policy is published on this posting, and unlike Workato's Customer Centric Engineer role there is no night shift stated here. Honest fit guidance: if you have built search or RAG systems that ran in production and you can talk about recall and ranking quality with numbers, three years is enough here. If your retrieval experience is a demo or a tutorial pipeline, the bar in the interview will be evidence of production quality work.
What the posting asks for: - A total of 4+ years of relevant experience in design, development and implementation. - Within that, at least 1 year of experience with Workato specifically. The posting states this is a must, so treat it as a hard filter. - Deep understanding of AI and ML technologies, integration and automation experience, and solution architecture. - Strong problem solving and the ability to collaborate across multidisciplinary teams. Day to day: - Implementing agent based AI solutions on the Workato Agentic AI platform. - Building intelligent, autonomous agentic workflows using multi agent collaboration and orchestration. - Implementing and deploying retrieval augmented generation systems using the platform's connectors, workflows and recipes so that model responses are grounded and current. - Developing advanced prompting, memory management and behaviour planning so LLMs and agents can author and execute complex workflows reliably. - Acting as the technical expert troubleshooting and analysing AI driven architectures, including scalable RAG pipelines and agent frameworks. Location and office reality: Hyderabad. No office day policy is published, and no night shift is stated on this particular role. Honest fit guidance: this is customer facing engineering, so expect to spend real time with customers rather than only in a codebase. The one year of Workato platform experience is the requirement most applicants will fail on. If you have integration or iPaaS experience on a competing platform, apply anyway and be direct about the gap, since the rest of the requirement list is transferable.
What the posting asks for: - 7+ years of hands on experience delivering end to end automation and cloud infrastructure projects, from requirements through to production deployment. Day to day: - Leading end to end cloud infrastructure automation projects aligned to business requirements, owning architecture, delivery and outcomes across the full project lifecycle. - Designing enterprise grade automation architectures spanning multi system integrations, event driven workflows and infrastructure provisioning pipelines. - Architecting and implementing cloud infrastructure for project incubation, including provisioning cloud accounts. - Building tooling that lets product, engineering and customer success teams move faster. - Streamlining CI/CD and keeping environments secure, scalable and reliable. Who it serves: this is internal platform work. The stated customers are Workato's product, engineering and customer success teams, not external accounts. Location and office reality: Hyderabad. No office day policy is published on this posting, and no shift requirement is stated. Honest fit guidance: the ownership language here is unusually strong for an automation role, so it suits someone who wants to make architectural calls rather than execute a defined backlog. Seven years is the floor. If you are a DevOps engineer at five or six years with genuine project ownership on your record, the gap is smaller than it looks, but you are applying under the stated bar.
What the posting asks for: - BS or above in computer science or a related field. Master's or PhD preferred. - 10+ years developing search relevance systems at scale, either in production or in high impact research environments. - Experience applying LLMs to search relevance. - Experience in one or more of: query understanding, NLP, text mining, recommendations, personalisation, discovery, or conversational AI. - Strong computer science fundamentals. - Contributions to well used open source projects. Day to day: driving the development and deployment of ML based search and discovery relevance models integrated into Databricks products; designing automated ML and NLP pipelines covering data preprocessing, query understanding and rewriting, ranking and retrieval, and model evaluation so the team can iterate quickly; working with product managers on the search and discovery roadmap; and building a robust framework for evaluating ranking improvements both offline and online. The problem in context: customers can hold hundreds of millions of assets on the platform, so this is a genuine large scale retrieval problem rather than a site search feature. Location and office reality: Bengaluru. The posting does not publish an office day policy. Honest fit guidance: ten years specifically in search relevance is narrow, and the open source contribution line is listed as a requirement rather than a nice to have. General ML engineering at ten years is not the same thing as a decade of ranking and retrieval work, and this interview will find the difference.
What the posting asks for: - 15+ years of production level experience in one of Rust, Java, Scala, C++ or a similar language. - 10+ years of experience developing large scale distributed systems from scratch. - Experience working on a SaaS platform or with service oriented architectures. - Experience with cloud networking, Kubernetes, and infrastructure automation languages such as Terraform or CloudFormation. Note on the years: the posting lists both figures as requirements, so the effective bar is the higher one. We have published 15 rather than the lower figure because both sit in the mandatory list. Day to day: owning and driving the design of large scale connectivity platforms forming the backbone between the Databricks control plane and compute plane; improving the scalability, reliability and efficiency of the compute infrastructure; setting technical direction at org level; leading complex cross team initiatives; and mentoring senior engineers. The posting says the role requires both hands on technical leadership and the ability to influence architecture and execution across teams. Why the site matters: the posting positions this as an early hire at a rapidly growing Bangalore site, with scope to define architecture rather than inherit it. Location and office reality: Bengaluru. The posting does not publish an office day policy. Honest fit guidance: fifteen years is genuinely the floor here and networking depth is not optional. This is the least accessible role in today's list, published because engineers at that level rarely see India based openings of this scope. If you are at ten to twelve years with strong multi cloud networking, you are under the stated bar but close enough that an application is not wasted.
What the posting asks for: - 4+ years of professional frontend and UI engineering experience building and operating production quality web applications, diagnosing UI issues, and improving implementations based on real world behaviour. What the team owns: application architecture, shared frameworks, and the deployment pipelines that deliver frontend assets globally using AWS infrastructure including CloudFront CDN delivery. The team builds with cloud native and micro frontend architectural patterns that allow independent development and deployment of frontend components. Day to day: hands on engineering and ownership of frontend components for the Clumio cloud native data protection platform, working closely with product management, design, backend, QA and platform teams to turn complex workflows into clear interfaces. The posting emphasises standardised build and deployment practice. Reporting: the posting states this role reports to an Engineering Director. Its emphasis is explicitly on strong hands on engineering, so it is an individual contributor seat. Location and office reality: Bangalore. The posting does not publish an office day policy. One thing to be aware of: Commvault opens this posting with a recruitment fraud warning. It states that Commvault does not conduct interviews by email or text, and will never ask you to submit sensitive documents such as banking details or identity numbers before your first day. That is the employer's own guidance and worth carrying into any process that claims to be from them. Honest fit guidance: four years is a real floor rather than a soft one, and the emphasis on diagnosing production UI issues suggests they want someone who has supported a live product, not only built features.
What the posting asks for: - 5+ years of experience in application or software security architecture. - Strong knowledge of threat modelling methodologies such as STRIDE, PASTA and OCTAVE. - Hands on experience conducting security architecture reviews for complex systems. - Familiarity with automated security architecture tools such as IriusRisk, ThreatModeler or the Microsoft Threat Modeling Tool. - Experience reviewing the architecture of generative AI solutions. Preferred: experience with automated tools for security architecture analysis, and relevant security certifications. The posting says these are strongly preferred rather than required. Day to day: conducting in depth security architecture reviews across cloud, on premises and hybrid environments; performing threat modelling to identify risks and define mitigations early in the development lifecycle; working with development teams, DevOps and product owners to guide secure design decisions; evaluating and implementing automated tooling for architecture review and continuous assessment; creating and maintaining security architecture documentation and reusable patterns; and contributing to internal security standards and processes. Location and office reality: Bangalore. The posting does not publish an office day policy. One thing to be aware of: Commvault opens this posting with a recruitment fraud warning, stating it does not interview by email or text and will never request sensitive documents before your first day. Honest fit guidance: this is a design and review role, not a penetration testing or SOC role. If your security experience is entirely operational, the threat modelling methodology requirement is where the interview will focus. Five years plus real architecture review experience clears the stated bar.
What the posting asks for: - Bachelor's degree required. - 8+ years overall experience with a track record of leading complex technical initiatives. - Deep expertise in Linux and Windows systems programming and operating system internals, specifically memory management and storage I/O. - Strong C++ background with production experience in low level or systems software. - Hands on Kubernetes experience covering operators, CRDs, CSI, RBAC and cluster level architecture. - Solid understanding of storage internals: block storage, snapshots, replication and consistency models. - Experience with virtualization platforms. KVM and QEMU familiarity is called a strong plus. - Experience with KubeVirt, OpenShift Virtualization or similar container native VM platforms. Day to day: designing and implementing data protection features for virtualised workloads across KVM, QEMU, VMware and Kubernetes native environments; driving architectural decisions for backup, restore and replication pipelines at the operating system and hypervisor layer; contributing to CSI driver development, Kubernetes operator design and container native storage workflows; and providing technical leadership and mentoring across product lines. Scope: the posting describes this as a high impact individual contributor role with broad scope and visibility. Mentoring is included, people management is not. Location and office reality: open across Bangalore, Hyderabad and Pune. No office day policy is published. One thing to be aware of: Commvault opens this posting with a recruitment fraud warning about fake interviews conducted by email or text. Honest fit guidance: eight years is the floor but the C++ and OS internals depth is the real gate. Kubernetes application experience is not the same as CSI and operator development, and the posting is asking for the latter.
What the posting asks for: - 3 to 7 years of hands on software development experience, preferably in a cloud based or product driven environment. - Strong experience with JavaScript and Node.js development. - Solid hands on experience with AWS services including Lambda, EC2, S3 and DynamoDB. - Familiarity with RESTful API design and microservices architecture. - Proficiency with version control (Git) and CI/CD pipelines. - Bachelor's degree in computer science or a related field, or equivalent practical experience. Nice to have: understanding of containerisation technologies such as Docker. Day to day: architecting, implementing and maintaining backend services and APIs in Node.js and JavaScript for the integrator.io platform; using AWS services to build scalable solutions; improving application performance, reliability and security through continuous monitoring; troubleshooting and resolving production issues; developing automated deployment pipelines using CI/CD practice; and translating business requirements into technical specifications with product, operations and design teams. ⚠️ A note on the title: the posting is advertised as Senior Site Reliability Engineer, but the body describes the role as an AWS System Development Engineer and the requirement list is a backend development list. If you are looking for a pure SRE role with on call and infrastructure ownership, read the description carefully before applying, because this leans backend. Location and office reality: Hyderabad. No office day policy is published on this posting. Honest fit guidance: the three year floor is genuine and the wide band suggests they will level you on interview. Strong Node.js plus real AWS serverless experience is what this hinges on.
What the posting asks for: - At least 5 years designing and building integration solutions, ideally within sales or customer success domains. - At least 2 years of experience with JSON and XML schema design. - Strong expertise developing integrations using REST and SOAP APIs. - Proven experience developing AI agents or bots that autonomously interact with tools and systems to derive and act on business insights. - Expertise integrating large language models such as OpenAI's GPT series, Google's Gemini or Anthropic's Claude with external APIs, vector databases and enterprise platforms. - Strong understanding of prompt engineering, context management and orchestration of multi step tasks. - Proficiency with enterprise iPaaS platforms including Celigo and comparable tools such as SnapLogic. Day to day: designing and delivering scalable data pipelines on modern cloud architectures; building automations with integrator.io to remove repetitive work; contributing to AI chatbots for internal stakeholders; ensuring integrations meet engineering standards for data quality, accuracy, operability and security; managing several projects at once including operational tasks; acting as owner and final escalation point for your integrations; and producing technical documentation and support processes. Who you would serve: the posting says this team supports business and finance teams by connecting systems and data. This is internal platform work, not customer facing product engineering. Location and office reality: Hyderabad. No office day policy is published. Honest fit guidance: be clear that this is internal business systems integration with a real AI component, not product development. If that distinction matters to you, weigh it before applying. The LLM and agent requirements are specific enough that generic integration experience alone will not clear them.
What the posting asks for, listed as must haves: - Bachelor's degree in computer science or equivalent practical education and experience. - 4+ years of cloud or infrastructure engineering experience. - 2+ years of infrastructure security experience. - 2+ years working with modern container technologies. Kubernetes is described as a bonus. - Experience securing infrastructure and services in a multi account AWS environment. - Strong understanding of identity and access management: roles, policies and service control policies. - Experience performing security reviews and risk assessments in SaaS and cloud environments. - Understanding of modern DevOps engineering and containerisation. - Working understanding of common network security controls, authentication and security protocols. - Working understanding of SOC 2, FedRAMP, CIS Critical 18 and PCI DSS frameworks. - Ability to communicate with people of varying technical depth, work autonomously and navigate ambiguity. Day to day: operating as one of the senior technical figures for the Infrastructure Assurance team and partner teams across the Asia Pacific Japan region; educating product and platform engineers on security practice for multi cloud, Kubernetes and internal services; providing security design guidance and running security reviews for a secure by design model; mentoring junior team members; and working with IT, compliance, legal and privacy teams. Location and office reality: Hyderabad. No office day policy is published on this posting. Honest fit guidance: the two year security requirement inside a four year overall bar is the detail that makes this reachable. If you are a cloud or DevOps engineer who has been doing security work for two years, you meet this as written, and that is a more open door than most senior security postings offer.
What the posting asks for, listed as must haves: - 5+ years of professional experience in full stack software development, preferably in a SaaS or product based environment. - Proficiency with React (preferred) or Angular, with solid JavaScript and TypeScript, CSS and modern web standards. - Strong backend expertise. The posting names Java and Python for the server side. Day to day: - Independently designing, developing and deploying scalable features using the UI framework on the frontend and Java or Python on the backend. - Implementing AI enhanced workflows, including building Model Context Protocol servers that expose New Relic's telemetry data to LLMs and AI agents. - Owning the reliability and performance of services processing very large data volumes, ensuring they are multi threaded and highly concurrent. - Writing clean, well tested and maintainable code, reviewing peers' code and contributing to internal technical documentation. - Working with product managers and designers to turn wireframes into production software. - Identifying bottlenecks across the stack, from slow UI renders to inefficient backend queries. ⚠️ A location inconsistency worth knowing: the posting header states the location as Bangalore, India, but one paragraph in the body refers to joining a core data team in Hyderabad. We have published Bangalore because that is the stated location field and the explicit location line. Confirm with the recruiter before you plan around either city. Location and office reality: Bangalore per the posting header. No office day policy is published. Honest fit guidance: this is a genuine full stack role, so a backend engineer with weak React or a frontend engineer with weak Java will both find the interview uneven. The MCP and AI agent work is the most interesting part and it is real, not aspirational.
What the posting asks for, listed as must haves: - 5+ years of professional Java development. - Strong experience building cloud native applications on AWS. - Experience designing and operating containerised microservices on Kubernetes. - Experience building and operating distributed systems at scale. - Familiarity with infrastructure as code (Terraform) and CI/CD pipelines. - Experience with AWS security patterns. - Experience with observability tooling, including defining service level objectives and indicators, dashboards and alerting. - Comfort debugging production issues across multi service architectures. - Experience with gRPC or Thrift based service communication, and with GraphQL APIs. Nice to have: - Strong understanding of SQL query execution: parsing, planning, optimisation or execution engines. - Experience with JDBC drivers, connection pooling and database connector development. - Experience with distributed query engines or SQL on anything platforms. Day to day: designing and maintaining cloud native Java microservices in the query path including the SQL gateway, query gateway and data source connector plugins; hardening JDBC connector integrations covering connection lifecycle, credential handling, query pushdown optimisation and security validation; improving query reliability and performance across a multi tenant deployment serving over 50 customers; implementing security controls for user supplied connection parameters including JDBC URL validation, SSRF prevention and hostname allowlisting; building materialized view scheduling and lifecycle features; and designing canary deployments and progressive rollouts. On call: the posting states you participate in an on call rotation and incident response for production systems. Worth factoring in. Location and office reality: Hyderabad. No office day policy is published. Honest fit guidance: the must have list is long and quite specific, but the genuinely rare items (query engines, JDBC connector development) are all in the nice to have section. Five years of solid Java on AWS with Kubernetes meets the stated bar.
Location, stated plainly by the employer: this will be a remote role, but you must be based in Bangalore to be eligible. Cockroach Labs also runs a hybrid model where people local to an office come in on Mondays, Tuesdays and Thursdays and work flexibly otherwise, so clarify at interview which applies to you. What the posting asks for: - 5 to 8 years of experience working in technical support at a software company. - Knowledge of distributed systems and Linux, and the ability to read and write SQL. - Experience using Zendesk, Jira, Confluence or similar software. - A genuine interest in working with users directly, and the judgement to adjust tone and content so a message lands well. - Critical thinking that defaults to a client centric approach. - Effective written and verbal communication, including delivering root cause analysis to different stakeholders. Day to day: supporting both self service and enterprise customers across CockroachDB's deployment models (self hosted, dedicated and serverless); developing deep expertise in the database and surrounding technologies; spotting patterns across customer issues and feeding product improvements back to documentation, product and engineering; writing runbooks and playbooks to cut future resolution time; and reproducing technical issues so engineering can resolve them. Shift note: the posting mentions a follow the sun model to ensure continuity beyond your shift for priority tickets. Ask what that means for your working hours. The published ramp: within 30 days you should have enough expertise to begin assisting users directly, supported by a self guided onboarding platform. After three months you should be fully integrated and able to manage most customer issues. Beyond that, mentoring and training new team members. Honest fit guidance: this is a support role and it is described as one, so do not apply expecting to write product features. It is, however, one of very few remote eligible technical roles available in India right now, and the distributed systems and SQL depth make it a real engineering job.
What the posting asks for: - 8+ years of experience as a software engineer writing clean, idiomatic code. - 1+ years of hands on experience with GCP or AWS. - Ideally, experience with massively complex codebases and broad experience across distributed systems, cloud infrastructure and automated testing. On AI use, stated in the requirement list: rigorous validation habits and deep domain expertise applied to all AI assisted output, a clear understanding of where AI can be safely integrated and where it introduces unacceptable risk, and final authority over everything that reaches production. The posting's framing is that AI assists your work and does not replace your judgement. Day to day: developing test strategies and methodologies; building and scaling test infrastructure; building tools and frameworks that find bugs in complex distributed systems; building static and dynamic analysers; running at scale cloud benchmarking; and prioritising test suites representative of real customer workloads. Named projects from the posting: a mixed version framework using roachtest and roachprod, failure injection testing with tools such as chaos-mesh, the next generation of roachtest and roachperf, parallelised automated microbenchmarks, a static analysis framework for concurrency bugs, large scale benchmarking, and automated flaky test detection and quarantining. ⛔ What this is not: the posting states explicitly that this is not a QA or manual testing role. Location and office reality: Bangalore. Cockroach Labs runs a hybrid model with office days on Mondays, Tuesdays and Thursdays for people local to an office. Honest fit guidance: if you are a manual QA engineer, this posting has already told you it is not for you. If you are a backend or distributed systems engineer who enjoys building tooling that breaks things on purpose, it is one of the more unusual and interesting roles in this list.
What the posting asks for: - Typically 10+ years of experience building large scale, production grade systems. - A strong background in backend or systems programming, preferably with Go, C, C++ or Rust. - Experience working on indexing or query execution systems such as vector, text or spatial search. - Solid understanding of data structures, algorithms and distributed systems. - Genuine interest in databases, indexing systems and high performance distributed architectures. - Curiosity about AI driven and hybrid workloads combining structured and unstructured data. Day to day: designing, building and maintaining specialised indexing features for CockroachDB including vector, full text and geospatial indexing; improving the performance and reliability of existing vector indexing including backfill, query planning and import workflows; integrating new indexing mechanisms into the query engine with other database teams; developing hybrid search that combines vector similarity with text based search; and owning work from design through implementation, testing and release. The published ramp: in the first month, getting familiar with the SQL architecture, the vector indexing implementation and surrounding systems while contributing smaller fixes. Within three months, owning components of specialised indexing and making measurable performance and reliability improvements. After six months, helping shape the roadmap for future indexing and search features. Why it is unusual: this is a new subteam, so the early work shapes what the team becomes rather than inheriting an established roadmap. Location and office reality: Bangalore. Cockroach Labs runs a hybrid model with Monday, Tuesday and Thursday office days for those local to an office. Honest fit guidance: the word 'typically' in front of the ten year figure suggests some flexibility, and the indexing or query execution experience is likely to matter more than the exact year count. Database internals experience is effectively required.
⚠️ Location warning, and please read this before applying: Notion's job board marks this posting as remote, but the posting body carries an onsite tag. Notion states elsewhere that its Hyderabad roles work from the office on Mondays, Tuesdays and Thursdays. We have published this as Hyderabad, not remote, because the posting body is the more specific statement. Confirm with the recruiter before you plan around remote work. What the posting asks for: - At least 4 years of experience as a software developer, with the ability to perform well in a fast paced environment. - Systems thinking: understanding distributed systems and designing solutions that account for tradeoffs between consistency, latency and scalability. - Pragmatic problem solving, prioritising business impact and balancing craft, speed and long term maintainability. The posting says it wants someone opinionated but not ideological who picks up new technologies as they go. - Ownership and initiative. Day to day: contributing to the evolution and maintenance of the async task runner serving over 100 million global users; keeping systems reliable, efficient and scalable with guidance from senior team members; evaluating and integrating new technologies; debugging live production systems with minimal disruption, including replacing components and managing failovers; participating in an on call rotation and responding to incidents; and partnering with product engineers and other infrastructure teams. What the team owns: Notion's internal async task runner, which is critical to product speed, reliability and security, and the configuration management platform used by Notion's product and infrastructure engineers. Honest fit guidance: the posting's language about working with guidance from senior team members and growing your skills in distributed systems suggests this is pitched at the lower end of mid level, which is unusual and welcome. If you have four years of backend experience and want to move into infrastructure, this is a reasonable stretch. The on call expectation is stated up front, so factor it in.
⚠️ Location note: Notion's job board marks this posting as remote, but the body states plainly that the role is based in Hyderabad, India, and that the team works from the office on Mondays, Tuesdays and Thursdays (described as anchor days). The posting also carries an onsite tag. We have published Hyderabad with three office days, because the body is the specific statement. Do not plan around remote work here. What the posting asks for: - Over 10 years of experience with strong software engineering fundamentals and a track record of turning ambiguous goals into well scoped, shippable milestones. - Leadership in the technical sense: the ability to create a technical roadmap, plan and execute very large projects, and motivate a team towards a goal. - Enjoyment of learning new technologies and a demonstrated record of innovation. - Experience building or operating developer tooling such as CI/CD, infrastructure workflows or internal platforms, with a focus on reliability, observability and developer trust. Day to day: - Building an AI harness to auto resolve bugs reported for the Notion app, which the posting calls high leverage work requiring solid engineering to improve resolution accuracy. - Improving CI and build reliability so engineers get early feedback when a change breaks the build. The posting states a five minute CI target that the team is already tracking towards. - Improving developer features for Notion's in house, AI first remote development environments. - Executing a shared roadmap with the US engineering team, informed by an internal developer experience survey. - Working with the TypeScript language server, lint tooling and the Notion CLI. Honest fit guidance: ten years plus is a high floor for a role with no people management attached, so this is aimed at a genuinely senior individual contributor. The leadership described is roadmap and influence rather than direct reports. If you like platform and tooling work more than product features, the scope here is wider than most developer experience roles.
What the posting asks for: - 6 to 8 years total experience, made up of 2 to 3 years hands on in agentic AI and 2 to 3 years in core NLP and data science before that. - Real experience shipping LLM based inference, RAG or agent work, including multi agent systems. - Core NLP and ML foundations: text classification, named entity recognition, embeddings and feature engineering, from before the LLM era. - The judgement to know when classical NLP or ML is the better fit and when an LLM approach is, which the posting says should come from having actually done both. Day to day: - Prototyping fast: turning a rough problem statement into a working RAG pipeline, LLM inference or agent within days rather than weeks. - Taking your own prototypes from notebook to production quality Python: tested, typed and reviewable. - Partnering with the platform engineers who own the harness and infrastructure to ship. You are not expected to design the harness, but you need to understand it well enough to build in it and debug it. - Owning evaluation for everything you ship: offline eval sets, LLM as judge checks, and tracking regressions before and after changes. - Pulling in proofs of concept and external research when the path is unclear, and course correcting quickly. Location and office reality: the posting states this is a hybrid position requiring the ability to be onsite at the Bengaluru office as needed, and that candidates must be based in India. Honest fit guidance: the posting says outright it is looking for a builder rather than a manager in waiting, and that most of your time goes on prototyping and evaluation. If you want a research role or a team lead track, this is not it. The two to three years of pre LLM NLP experience is a genuine requirement and rules out people who came to the field entirely through prompt engineering.
What the posting asks for: - 8+ years in data science or machine learning. - Within that, at least 2 to 3 years hands on building and operating production AI agents. The posting is explicit that this means production systems, not experimenting with agent frameworks, building demos, or wrapping a single prompt with a tool call. - Staff or lead level experience is preferred. Day to day: - Agent architecture and technical strategy: defining the roadmap for the agentic stack covering the execution loop, harness, memory and tool layers, and deciding when an agent, a classical model or a hybrid is the right answer. - Production agent engineering: building and operating the reasoning and execution loop, the harness that manages tool calls, retries, timeouts and session state, short and long term memory, and the skill and tool registry using MCP style tool calling. - Planning and multi step reasoning: designing task decomposition and planning strategies such as evidence based planning, plan and execute, and multi hop reasoning. - Guardrails, trust and evaluation: owning the evaluation framework for agent behaviour including offline eval, LLM as judge and online A/B testing, plus input and output validation and safety checks. - Generative AI and revenue modelling: applying statistical and time series methods to forecasting, deal health and risk prediction models. - Multi agent and cross system coordination: designing how agents communicate with sub agents and other systems. Location and office reality: the posting states this is a hybrid position in Bengaluru requiring onsite presence as needed, and that candidates must be based in India. Honest fit guidance: the distinction the posting draws is the one to take seriously. Demos and framework experiments will not clear this bar, and the interview will look for agents you have kept running in production, including how they failed and what you did about it.
⚠️ Location correction: OpenAI's job board lists this posting as India Remote and flags it as remote, but the body of the posting states plainly that the role is based in Bangalore. We have published Bangalore because the body is the more specific statement. If remote work is the reason you are applying, confirm this with the recruiter first. What the posting asks for: - 8+ years of technical consulting or equivalent experience, managing C level technical and business relationships with complex global organisations. - Deep technical expertise combined with strong judgement and ecosystem leadership. Day to day: - Serving as the senior technical counterpart to AWS field leadership, building credibility across regions and teams. - Influencing joint account strategy and technical direction for high priority opportunities, and shaping how OpenAI engages with AWS through engagement models and prioritisation frameworks. - Leading technical strategy for large, ambiguous, high stakes enterprise engagements, guiding customers from early ideation through architecture design, prototyping and production deployment. - Acting as a technical decision maker and escalation point to de-risk complex implementations. - Designing end to end AI architectures using OpenAI and AWS services, and building prototypes, proofs of concept and reference implementations. - Establishing best practice for scalable, secure, production ready generative AI systems. - Enabling AWS and partners through workshops, playbooks, reference architectures and demos, and mentoring partner technical teams towards self sufficiency. Honest framing on where this sits: the posting says you work across both pre sales and post sales. We have published it because the requirement list is technical consulting and architecture throughout, with no sales quota or pipeline targets attached. If customer facing work is not what you want, this is not the role, and we would rather say that here than let the title imply otherwise. Honest fit guidance: eight years of enterprise technical consulting with genuine architecture depth is the bar. Engineers without customer facing experience will find the C level relationship requirement is real.
Location: the posting lists this as Remote, India. We found no clause in the body contradicting that, which is worth saying because several postings in today's edition did contradict their own location field. Minimum qualifications from the posting: - 5+ years of experience in a customer facing technical role. The posting names solution architect, solution engineer, onboarding engineering, customer success engineering or technical consulting as acceptable backgrounds. - Hands on experience with production workloads in at least one major cloud provider ecosystem: AWS, Azure or Google Cloud. - Deep technical proficiency in core networking infrastructure, including VPC and VNet architectures, routing protocols, peering, and PrivateLink or private endpoints. - Hands on technical proficiency with SQL or NoSQL databases such as SQL Server, MySQL, PostgreSQL or MongoDB. - Proven track record implementing enterprise identity and access management, including single sign on using OIDC or SAML. - Bachelor's degree or equivalent practical experience. Day to day: leading new enterprise customers through critical infrastructure milestones covering cloud provisioning, security hardening, networking, data modelling and application integration; shaping tailored onboarding blueprints and orchestrating delivery workstreams; using automation to optimise data modelling, connectivity and application health for fully managed AuraDB customers; applying infrastructure as code and platform engineering practice to deliver secure, resilient graph clusters in self managed environments; and architecting data ingestion pipelines covering bulk imports, stream processing and change data capture while advising development teams on driver optimisation, connection pooling and retry logic. Honest fit guidance: this is customer facing work and the posting does not hide it, so expect your calendar to have customers in it. What makes it worth publishing is that the technical bar is genuine: networking, IAM and infrastructure as code are all required, not preferred. Graph database experience is not on the requirement list, so a strong cloud infrastructure engineer can learn Neo4j on the job.
⚠️ Experience: ClickHouse publishes no years of experience requirement anywhere in this posting. We have left the figure blank rather than invent one, which does mean this role will not show up if you filter this page by years. Judge it on the skills below. Location: the posting is listed as India (remote) and tagged remote. It also notes ClickHouse is hiring for this role in any country where it has a hiring presence, and describes itself as a globally distributed, remote friendly company offering a home office setup allowance to remote employees. What the posting asks for: - Extensive knowledge of SQL. - Previous work in a similar SDET, release engineering or QA role related to a classical database or distributed system. - Hands on coding experience with Python. - The ability to read C++ code for validation purposes. - Working knowledge of Git, Linux and shell scripting. - Experience with both manual and automation testing. - Demonstrated ability to work collaboratively, including with remote teams, and to learn complex technology quickly. - Strong problem solving and solid production debugging skills. Day to day: building and enhancing test automation frameworks and writing automated test cases; trying out new features and making sure they land smoothly in production; testing cross functional implementations across internal teams; implementing new testing strategies for large complex distributed systems; evaluating new ClickHouse functionality for each release and finding improvement opportunities in the existing codebase; and improving the existing testing infrastructure. Company context from the posting: ClickHouse reports more than 4,000 customers, annual recurring revenue growth over 250 percent year on year, and a 400 million dollar Series D. It appears on the 2025 Forbes Cloud 100 list. Honest fit guidance: the posting describes an ideal candidate with strong technical skills and a background in release engineering. Because no years figure is published, the skills list is the real filter, and database or distributed systems testing experience is the item that matters most.
⚠️ Read this first. The posting states two conditions directly: - Hybrid working with 3 days a week in the office is mandatory. - The role works a 24x7x365 model, and the shift timings rotate every 4 months between APAC, EMEA and US time zones. That rotation is the single biggest factor in whether this job suits you, so decide on it before anything else. What the posting asks for: - 3+ years of experience as a cloud operations engineer, NOC engineer and/or Linux system administrator. - Working knowledge of public cloud environments (AWS, Azure or GCP) and Kubernetes orchestrated containerised workloads. - Strong written and verbal communication skills. - Strong attention to detail and the ability to handle several concurrent tasks. - Ability to work independently with minimal supervision. Described as a plus rather than required: - Experience with monitoring and instrumentation tools such as Prometheus, Grafana, New Relic or Elastic. - Experience with automation using Jenkins, Python or shell scripting. Day to day: supporting all aspects of cloud operations day to day, monitoring availability, durability, performance, scale and uptime of JFrog's multi cloud SaaS services; analysing events, troubleshooting and running incident response; communicating with internal stakeholders and tracking problems through to resolution; building and maintaining standard operating procedures and team knowledge for monitoring and automation; and working closely with SRE, production engineering and cloud engineering on improvements. Location and office reality: Bangalore, three mandatory office days a week, rotating 24x7 shifts. Honest fit guidance: the technical bar is genuinely accessible at three years, and the monitoring and automation items are plus points rather than requirements, so do not screen yourself out over them. The shift rotation is the real trade. This is a good route into cloud operations at a well known DevOps company if rotating hours work for your circumstances, and a poor one if they do not.
What the posting asks for: - At least 3 years building and shipping software in a production environment. - Solid proficiency in Python, JavaScript and/or Golang. - Hands on experience with Docker, Kubernetes and cloud providers. Fastly uses GCP. - Judgement about when to build a complex system and when a simple solution is right, with care for testing, code quality and monitoring. - The ability to explain technical tradeoffs clearly and collaborate with a distributed team across time zones. - Experience guiding and coaching team members. - Ability to pick up new skills quickly and share them with the team. Described by the employer as things that would impress: - Building or maintaining a custom SIEM or SOAR platform. Day to day: designing, developing and refactoring the custom internal security platform across both the FastAPI backend and the React frontend; partnering with security analysts to turn manual workflows into automated reliable processes; working with GCP infrastructure using Kubernetes for orchestration and Terraform for resource management; using Prometheus and Grafana to detect failures early and maintain availability; building and maintaining API integrations connecting detection tools, ticketing systems and customer environments; and championing code quality through reviews, testing and CI/CD. Location and office reality: Pune. The posting does not publish an office day policy. Honest fit guidance: this is a strong option for a backend or full stack engineer who wants to move into security without already being a security specialist. The requirement list asks for software engineering skill first and security context second, and the SIEM and SOAR experience is explicitly a bonus rather than a gate. If you are a security analyst who does not write production code, the balance runs the other way.
What the posting asks for: - At least 7 years of combined experience in software engineering and/or data engineering, with genuine depth in both. The posting is specific that it wants both, not one with a passing familiarity with the other. - A Trino enthusiast, in the posting's own framing, looking to push the boundaries in an AI future. Day to day: - Designing, building and operating a high quality data lake and the software systems that feed it, supporting product management, finance, customer support and engineering. - Writing production grade software including services, APIs, tooling and automation that enables data workflows and integrations at scale. - Finding ways to use Trino and Starburst to solve complex data management and software architecture problems. - Working with technical leads, product managers and data analysts to build data products and analytics. - Using AI to widen access to datasets across the company, including building the software infrastructure that makes that possible. - Enabling dataset preparation and model evaluation for Starburst's AI projects. - Defining engineering processes and best practice spanning both software and data domains. The team: described as dynamic, talented and globally distributed. Location: listed simply as India, with no city named and no office policy published. Worth clarifying with the recruiter, since Starburst does not state whether this is office based, hybrid or remote. Honest fit guidance: the dual requirement is the thing to weigh. Pure backend engineers with no data platform experience, and pure data engineers who have not shipped production services, both sit outside what this posting describes. If you have genuinely done both, this is an unusually good fit and there are not many roles written this way.
What the posting asks for: - 8+ years of professional, hands on engineering experience. - Within that, 4 to 6+ years specialising in building and deploying AI and ML models and systems. - 1+ year of experience developing generative AI and LLM applications using techniques such as prompt engineering, RAG and agents. Note how much lower this figure is than the seniority of the title suggests. - Expertise architecting generative AI applications and systems using various frameworks and cloud services. - Good proficiency with cloud services from Azure, GCP or AWS for building generative AI applications. - Expert proficiency in Python, LangChain or LangGraph, and SQL. The posting says this is a must. - Experience driving an engineering team towards a technical roadmap. - Strong communication skills for working with business subject matter experts. Day to day: building the technical roadmap from a business requirement and owning delivery; leading the design, training, fine tuning and deployment of large language models using prompt engineering, retrieval augmented generation and agent architectures; maintaining high quality Python and SQL with reusable, scalable components; deploying generative AI applications on cloud platforms with robust CI/CD; and collaborating across product and business teams. A note on scope: the posting says you lead the engineering team towards a technical roadmap and ensure timely execution. We read that as technical leadership rather than people management, since no hiring, performance or reporting duties appear anywhere in the posting. Turing does run separate roles that are explicitly people management, and this is not one of them. Location and office reality: Bengaluru. Turing itself is headquartered in San Francisco. No office day policy is published on this posting. Honest fit guidance: if you have eight years of engineering with several in ML and only about a year of hands on LLM work, you meet this posting as written. That is a genuinely more open door than the Principal title suggests, and it is the reason this role is worth a look.
What the posting asks for: - Bachelor's or Master's degree in computer science, engineering or an equivalent technical field. - 5+ years of hands on experience in DevOps, build or platform engineering, SRE, or a closely related infrastructure role. - Production experience scaling CI platforms such as Jenkins, GitHub Actions or GitLab CI. - Solid experience deploying, operating and debugging Kubernetes clusters and containerised workloads. - Proven track record managing public cloud infrastructure (AWS, GCP or Azure) using Terraform or similar infrastructure as code tooling. - Strong scripting and automation skills in Python, Bash, Go or similar. - Deep knowledge of Linux systems administration, networking fundamentals and distributed systems concepts. - Strong analytical and troubleshooting skills. Day to day: - Owning and optimising the end to end developer pipeline covering source control, build systems, test orchestration and artifact release. - Designing, scaling and maintaining distributed CI/CD engines for a rapidly growing engineering team. - Building internal tooling for large scale test automation execution, observability and flaky test debuggability. - Profiling and optimising compilation, linking and test cycle times to keep developer feedback loops short. - Building cloud native testing and deployment environments with Docker and Kubernetes across AWS, GCP and Azure. - Maintaining global infrastructure using strict infrastructure as code patterns with Terraform and Ansible. The posting's own framing: it states explicitly that this is not a passive infrastructure maintenance role, and that you would work with core engineering, SRE, cloud and security teams to remove developer friction. Location: listed as India with no city named and no office policy published, so clarify that with the recruiter. Yugabyte describes its team as distributed across more than 12 countries and multiple time zones. Honest fit guidance: five years is a real floor and the build optimisation work (compilation and link time profiling) is more specialised than standard DevOps. If your experience is deploying applications rather than building the pipelines that produce them, expect that gap to come up.
What the posting asks for: - At least 5 years of experience developing and optimizing systems software. - Deep expertise, meaning you can speak to both system level design and implementation detail, in at least one of: virtualization, storage, service modelling and REST API or SDK generation, scientific or high performance computing, or kernel development. - Experience designing, developing and/or troubleshooting distributed systems. - Comfort with at least one systems programming language (C, C++ or Go) and one scripting language (Python or Bash). - Comfort with shells on UNIX family systems. - Natural curiosity and drive to learn adjacent technologies. - BS degree or equivalent experience in computer science or a related field. Preferred qualifications: - Experience with low level monitoring and profiling tools such as pcm, perf or bpf. - Experience with, or hobbyist interest in, distributed elastic AI and LLM CPU inference, for example OpenVINO or llama.cpp. - Familiarity with, or interest in, SingleStore or other distributed SQL databases. Day to day: designing and developing major infrastructure components with a focus on fault tolerance and performance; owning your systems end to end from design to production; working closely with other teams on integration and operation; and driving continuous improvement in system reliability and usability. Team culture, as the posting describes it: a small, highly skilled team that works from first principles, practises distributed leadership where you shift between leading, collaborating and following depending on the project, and treats mistakes as something to learn from rather than punish. Location: listed as India with no city named and no office day policy published. Worth clarifying. Honest fit guidance: the preferred list is genuinely preferred, so the hobbyist framing on LLM CPU inference means what it says. The requirement that will decide this is depth in one low level area. Breadth across cloud tooling without that depth is not what this posting is asking for.