No roles match that combination.
Added July 31, 2026
Required by the posting: a minimum of 8 years of experience in performance testing and engineering roles with scalable cloud native multi tenant architectures. Proven expertise with at least one major performance testing tool, with JMeter, Locust, LoadRunner, Gatling, k6 and BlazeMeter named. Strong proficiency in at least one scripting or programming language for test development and customisation, with Java, Python, Golang and JavaScript named. Hands on experience with Docker and Kubernetes, including understanding how container resource limits affect application performance. Solid understanding of system architecture components including web servers, application servers, databases and load balancers. Experience with modern APM and monitoring tools incorporating AI/ML capabilities such as Dynatrace, New Relic, Prometheus, Grafana or Datadog. Working knowledge of SQL and NoSQL databases with the ability to analyse and optimise query performance. Strong analytical skills to interpret large datasets and AI generated outputs such as log traces and metrics to pinpoint root causes. Proficiency in machine learning and AI concepts including supervised learning and predictive modelling, and their application across the performance test cycle. Preferred skills: experience with cloud platforms including AWS, Azure and GCP and testing applications deployed in cloud native environments, and familiarity with continuous integration and continuous delivery pipelines. The real day to day: developing comprehensive performance test strategies and plans covering load, stress, volume and endurance testing; designing and maintaining robust, reusable test scripts for protocols including HTTP, web services, APIs and FTP/SFTP; collaborating with DevOps and infrastructure teams to configure performance test environments that accurately replicate production; designing and deploying containerised load generators onto the Kubernetes cluster to simulate massive scale with minimal overhead; executing tests and conducting deep dive analysis to identify bottlenecks in application code, database performance, network latency and infrastructure resource use; documenting clear reports with metrics and actionable recommendations for engineering and product stakeholders; working with developers and architects on performance tuning and code optimisation; and contributing to continuous improvement of the testing framework. Location: Bengaluru, Karnataka. Honest fit guidance: performance engineering at this depth is a genuine specialism, and eight years of functional test automation is not the same thing. The distinguishing requirements here are the Kubernetes native load generation and the expectation that you can read APM output and pinpoint root causes across code, database, network and infrastructure. The machine learning requirement is worth noting as a trend rather than a barrier: it is asking you to apply ML concepts to test analysis, not to build models. One relevant note from previous editions: Netskope has stated on other postings that it hires across all levels and levels candidates individually after assessment, so its stated year figures have historically been softer than they look.
Required by the posting: 4+ years in Linux/Unix administration with extensive field experience. Computer networking proficiency and working knowledge. Experience with a wide variety of open source technologies and tools with a strong emphasis on cloud services. Ability to implement best practices and IT operations to maintain an always up, always available service. Active participation in the on call rotation schedule. Effective English communication. A strong background in Linux networking including IP, iptables and IPsec. Effective work with MySQL databases, with MariaDB and Percona experience a plus. Coding and scripting skills, with a preference for Perl, Python or Golang. Experience with automation and configuration management using tools like SaltStack. Hands on experience with private cloud environments. Desirable skills: experience implementing cloud services on Linux using KVM and QEMU; familiarity with container orchestration; knowledge of NoSQL databases, especially Aerospike; proficiency in Perl and Golang; understanding of Galera cluster operations; and experience with data centre related activities. The real day to day: maintaining the reliability and performance of large scale fintech infrastructure, with the posting framing the goal as keeping services always up and always available, and the technology mix pointing squarely at private cloud systems engineering rather than managed cloud services. Location: Bangalore. The requisition location is recorded as Bengaluru, Salarpuria Softzone, and the requisition type is full time regular employee. Benefits, which PhonePe publishes in full and few employers do: medical, critical illness, accidental and life insurance; a wellness programme with an employee assistance programme, an onsite medical centre and an emergency support system; parental support covering maternity and paternity benefits, adoption assistance and a day care support programme; mobility benefits including relocation, transfer support and travel policy; and retirement benefits covering employee provident fund contribution, flexible provident fund contribution, gratuity, National Pension System and leave encashment. Honest fit guidance: the private cloud emphasis is the thing to weigh. If your infrastructure experience is entirely AWS or GCP consoles, KVM, QEMU, SaltStack and Galera will be unfamiliar and the interview will find that quickly. If you have run physical or virtualised infrastructure in a data centre, this is a rarer and more durable skill set than it gets credit for, and PhonePe operates it at a scale few Indian employers can offer. One thing to know from previous editions of this list: PhonePe frequently posts near identical job descriptions under several different titles and requisitions, so if you see similar SRE and Service Delivery Engineer listings, they may be the same job.
Minimum requirements from the posting: a BS or MS in Computer Science or an equivalent field. 12+ years of professional experience in software or infrastructure engineering. A proven track record leading complex, cross team or company wide infrastructure projects with high reliability and scale requirements. Strong engineering background in distributed systems, platform engineering or backend infrastructure with a focus on operational safety and correctness. Experience optimising the reliability and security of distributed systems. Experience scaling and migrating systems with little to no downtime. Strong technical judgement and written communication including design docs and trade off analysis. Experience mentoring engineers at various career stages. Experience with one or more major cloud providers, with AWS, Azure, OCI and GCP named. Familiarity with ops culture and a solid understanding of metrics, alarms and dashboards. Preferred qualifications, which the posting states are a bonus and not a requirement: experience validating large scale migrations, failovers, regional launches, regionalisation or control plane behaviour; designing or operating infrastructure with strict reliability, correctness, latency or availability requirements; strong observability judgement across metrics, logs, tracing, alerting and incident analysis; experience with networking, service discovery, traffic routing, databases, Kubernetes, Terraform or cloud infrastructure; experience reducing packet loss, network latency or cross region dependency risk; and experience making infrastructure validation evidence usable by service owners and partner teams. The real day to day: defining evidence based readiness criteria for regional launches, traffic migrations and failovers, replacing manual checklists with repeatable patterns; identifying and mitigating risks on critical payment paths and validating that platform mitigations measurably reduce impact; leading cross functional delivery for new region infrastructure including safe service behaviour for remote control planes; building reusable validation tooling that speeds infrastructure integration for new acquisitions; converting recurring operational friction into platform capabilities; leading technical conversations and defining decision mechanisms across Core Infrastructure and product teams; developing a multi year technical strategy with quarterly milestones; debugging production issues across the stack; and mentoring senior engineers to grow the Bangalore technical bench. Location and working pattern: Bengaluru, India, with the posting noting collaboration in a global distributed environment with asynchronous decision making across AMER, EU and APAC. One thing worth quoting because it is unusually candid: the posting says "We're looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement." Take that at face value and do not self reject on the preferred list. Honest fit guidance: this is a leadership shaped IC role. The mentoring and bench building responsibilities are explicit, as is developing multi year strategy, but there are no direct reports. The domain is narrow and valuable: if you have done regional expansion, failover validation or control plane work, you are rare. If your 12 years are in product engineering rather than infrastructure, the correctness and operational safety focus is a genuine mismatch.
What the posting asks for, and how it frames it. Composio heads its requirement list "Must haves" and then immediately qualifies it with "if you are very good, nothing is a must per-se". The capabilities it lists are: Core platform engineering: you have built systems where the abstractions were the product; you can reason about multi tenancy, isolation, auth, routing and observability without hand waving; you know how to ship reliable systems while the product is still changing fast. Enterprise judgement: you understand deployment flexibility, security, admin tooling and compliance as product problems; you can separate one off customer requests from primitives that should exist for every customer. AI native: you have built with language models; you have opinions about agents, MCP, tool use and where current systems fail. Plus two the posting labels directly: "typist", meaning you can write design docs and explain complex infrastructure clearly, and "human", meaning you build trust and admit what you do not know. Listed as Optional: multiple years writing TypeScript, Go or similar systems languages; experience building enterprise developer platforms inside large organisations; security, compliance or deployment model depth; and having started companies or built large side projects. The real day to day: evolving the platform primitives enterprise agents run on, covering governance, auditability, observability, permissions, routing and control planes; building the secure integration gateway between customer agents, SaaS tools, internal systems and APIs; designing multi tenant abstractions for isolation, configuration, extensibility and deployment flexibility; turning enterprise onboarding from a services engagement into a repeatable product experience; working directly with customers to understand where agent infrastructure breaks in real deployments; and making security, compliance and reliability first class product capabilities rather than later stage patches. Location and team: Bangalore, and Composio's own board marks this as not remote. The posting describes a small team of engineers. ⚠️ Years: this posting states no years of experience anywhere, which is why our experience filter cannot place it. Note that it goes further than most and puts "multiple years writing Typescript, Go, or similar systems languages" under Optional rather than required. Honest fit guidance: do not read the absence of a years bar as an entry level opening. The capability list (multi tenancy, isolation, auth, routing and observability reasoned about "without hand waving", plus systems where the abstractions were the product) describes a senior platform engineer. What the framing does mean is that a strong portfolio can substitute for a conventional CV here in a way it cannot at the enterprise employers on this list. If you have built infrastructure others build on and you have real opinions about agents and MCP, this is a posting where saying so is worth more than your years count.
Required by the posting: 4 to 6 years of industry experience. A Bachelor's or Master's degree in Computer Science, Electrical Engineering or another scientific or technical discipline. Cloud native application development experience using best practices and design patterns. Strong debugging and troubleshooting across the entire technology stack. Deep understanding of AWS networking, compute, storage and managed services. Competency with modern CI/CD tooling including Kubernetes, Terraform, Ansible and Jenkins. Experience with full lifecycle support of services from creation to production support. Infrastructure as code practice using Terraform or CloudFormation. Ability to author production ready code in at least one of Java, Scala or Go. Experience with Linux systems and comfort on the command line. Understanding of modern cloud native software security. Experience with agile frameworks such as Scrum and Kanban. Flexibility to step into new roles and responsibilities, and willingness to learn and use Sumo Logic's own products for solving reliability and security issues. Desirable skills: experience using Sumo Logic or other observability products; planet scale product development; running and operating SaaS products on AWS at expert level; streaming technologies such as Kafka, Kafka Streams or KSQL; expert level experience in one or more of Java, Go, Scala or Python; and expert level experience in one or more of Terraform, Jenkins or Kubernetes. The real day to day: maintaining and executing a reliability roadmap for your product area covering reliability, maintainability, security, efficiency and velocity; collaborating with development infrastructure, Global SRE and product area engineering teams to refine that roadmap; defining, evolving and managing SLOs for several teams; participating in on call rotations specifically to understand the operational workload well enough to improve it; improving the lifecycle of microservices from design through deployment and refinement; writing code and automation to reduce operational workload, improve security posture and eliminate toil; working with developer infrastructure teams and contributing features and bug fixes back; scaling systems sustainably through automation; and facilitating blame free root cause analysis meetings after incidents. Location: the posting body states Noida (Hybrid), while the Greenhouse metadata field for this requisition carries an office requirement value of Remote. We have published the body's statement because it is the more specific one, but this is a genuine ambiguity worth resolving with the recruiter on the first call. Honest fit guidance: the reliability roadmap and SLO ownership make this more strategic than a firefighting SRE seat, and the requirement to author production code in Java, Scala or Go means it is an engineering job rather than an operations one. If you have four to six years and can write real code, this is a strong mid level move.
Required by the posting: 2+ years of professional experience in machine learning and software engineering, with experience shipping production grade ML services. Hands on experience building with modern AI architectures such as LLMs and deep learning, and familiarity with tools including LangGraph, LangSmith, Google ADK, Vertex AI or AWS Bedrock. Strong proficiency in Python with the ability to write clean, maintainable, well tested production code. Working knowledge in at least one domain such as NLP, information retrieval, computer vision or statistical modelling. Ability to write technical design documents and communicate ML system designs clearly to cross functional stakeholders. Responsible use of generative AI with human oversight to deliver business ready outputs. The real day to day: building and improving the orchestration layer that manages state transitions, context sharing and intent routing across vendor and internal LLM frameworks in a distributed conversational environment; developing production grade Python services that bridge AI and ML capabilities with customer facing products; driving well scoped ML projects from design through delivery; contributing to system design, coding standards and AI/ML best practices; and participating in design reviews to ensure features meet Coinbase standards for security, compliance and performance. Team context: the CX Intelligence team sits in Coinbase's Enterprise Applications and Architecture organisation and owns the multi agent platform powering Coinbase chat, the Help Center and agent tooling, working with Conversation Design and CX teams. The role is levelled IC4. Location and working pattern: the board lists this as Remote in India. The posting states that Coinbase is remote first but not remote only, and that you should expect to get together quarterly for in person working sessions the company calls "surges". Factor that travel in before treating this as a fully remote job. Compensation: unusually, the posting publishes a specific annual base salary figure for this requisition of ₹4,408,400, excluding equity and bonus. Very few postings on this board state Indian salary at all. Application limit, stated in the posting: candidates may submit a maximum of 3 applications within a 6 month period at Coinbase. Do not spray applications across their board. Honest fit guidance: the posting opens by saying the bar is high and the environment intense, and that it is not a place for complacency. Take that as written. But the 2 year requirement is genuine and unusually low for a remote role of this quality, so if you have shipped a production ML service and know the modern agent tooling, this is worth your best effort rather than a quick application.
Required by the posting under What Makes You a Match: customer facing security work at a B2B SaaS company, with the ability to hold a credible technical conversation with an enterprise security team. Production AI agent experience, and the posting is emphatic about the standard: "Not prototypes, not prompts in a notebook. Real systems that replaced manual work in compliance, triage, evidence collection, or questionnaire automation." Deep enough understanding of AI and LLM security to explain it to a customer, covering prompt injection, agent guardrails, MCP exposure, model and data risks, and where frameworks like ISO 42001 apply. A closing the loop temperament: identify the gap, build the fix, and do not wait for someone else to execute on a commitment you made on a call. Comfort working evening IST hours to overlap with US and EU customers. Bonus: hands on experience with automation platforms like n8n or Tines, and working knowledge of SOC 2, ISO 27001, ISO 42001, HIPAA or GDPR. The real day to day, split as the posting states it, roughly half the week on direct customer security work and the rest building: owning calls, architecture deep dives and security reviews with sophisticated security teams at Fortune 500 companies across financial services, healthcare and payments; leading AI security conversations on agent behaviour, MCP exposure, context governance and ISO 42001; turning security reviews into an accelerator by handling the judgement cases their compliance tooling cannot, building reusable artifacts, and keeping the public trust centre current, with the measure being shorter customer onboarding rather than completed questionnaires; designing and shipping AI agents that keep evidence current and reduce manual review work every quarter, owned end to end; and contributing to the compliance programme across SOC 2, ISO 27001, ISO 42001, HIPAA and GDPR. Location and hours: the board lists India with the remote flag set on Atlan's own job board, and Atlan describes itself as global, remote first and high trust with a team across 15 or more countries in a trust first, async environment. The one firm constraint is the evening IST working hours, which the posting states is a real part of the role and not occasional. ⚠️ Years: this posting states no years of experience figure anywhere, so our experience filter cannot place it. The production AI agent requirement and the enterprise security review experience are the real bar, and both are more specific than a years count would be. Honest fit guidance on why it is here: the posting does use deal language, including "when the deal is on the line", so it is fair to ask whether this is a sales job. We concluded it is not: there is no quota, no pipeline target and no revenue responsibility, half the week is building systems the person owns end to end, and the hard requirement is having shipped production AI agents. It sits in our customer facing group rather than the main engineering list because the customer half is genuinely half.
Required by the posting: 6 to 9 years of experience in a combination of development and sustenance roles. Extensive hands on experience in Go or Python on Unix, Linux or Windows platforms. Excellent programming skills with data structures, algorithms and design concepts. Strong problem solving skills and demonstrated ability to articulate and present technical solutions. Strong interpersonal and communication skills, written and verbal, with the ability to build working relationships at all levels with both customers and internal stakeholders. Experience in enterprise software with deep knowledge of software development including threading, network and disk IO, data transformations, data integrity, systems management, systems administration and monitoring. Desirable skills: exposure to Office 365, VMware, Hyper-V, Nutanix, file systems or network attached storage; 6+ years of software development in Python or Golang; experience developing complex, scale out distributed systems based on service oriented architecture or microservices; cloud technologies, preferably AWS; and knowledge of the backup or storage domain. The real day to day: proposing solutions to complex design problems for the relevant technology or workload; fixing product bugs and delivering code changes to production; working with Sales, Tech Support, Customer Success and Professional Services to assist on proofs of concept and implementation projects; owning and driving cloud production issues through investigation and root cause analysis, delivering a fix and working with extended development teams; validating future releases in a staging environment against customer use cases, acting as a gatekeeper for product release and quality; partnering with scrum teams and Product Management on feature design and product improvements; and ensuring communication flows cross functionally on product updates and known issues. Qualification: B.Tech, B.E., M.E. or M.Tech in IT or Computer Science or equivalent. Location: Pune, Maharashtra. Honest fit guidance: the phrase "development and sustenance" in the requirement is the key to this role. Sustenance engineering means maintaining and fixing shipped software, and some engineers find it the most satisfying work available because the problems are real and the feedback is immediate, while others find it frustrating because you rarely build greenfield. The customer contact is real but technical, and the release gatekeeper responsibility gives it more authority than a typical bug fixing seat. Know which of those two reactions is yours before applying.
Required by the posting: 3 to 6 years of experience. A B.Tech, B.E., M.E. or M.Tech in Computer Science or equivalent. The real day to day: working closely with the development team in an Agile environment to understand functional specifications and design requirements; independently creating comprehensive feature test plans aligned with development milestones and feature completion; leveraging existing automation frameworks to automate feature tests and actively augmenting libraries to support new functionality; owning the complete test execution cycle for user stories; performing a mix of automated, manual, white box and black box testing; creating, maintaining and documenting testbed setups and environments; reporting, tracking and updating issues and test cases; and collaborating with cross functional teams to meet quality benchmarks across the development lifecycle. Location: Pune, Maharashtra. What this posting does not tell you, stated plainly: Druva's requirement list here is short. It gives the years band and the degree, and then describes responsibilities rather than a technology checklist. For comparison, Druva's more senior Software Engineer in Test requisition asks for Windows and Linux expertise, file systems and operating system concepts, threading, multiprocessing and socket programming, cloud fundamentals with AWS or Azure, Python or Java with Python preferred, shell scripting, SQL, REST API testing and backend automation, and tools including Git, Jira and XRay. That is a reasonable guide to the skills this team works with day to day, even though this particular requisition does not enumerate them. Honest fit guidance: this is a good role for someone in the middle of a test engineering career who wants product company experience in cloud data protection. Two caveats worth being honest about. The posting explicitly includes manual testing alongside automation, so it is not a pure SDET seat. And the responsibilities emphasise independence, with the phrase "independently create comprehensive feature test plans", so it suits someone who has already owned features rather than executed someone else's plan.
Required by the posting: 6+ years of experience, preferably in a product company with exposure to storage architectures. Strong demonstrable experience in systems programming, specifically multithreading, synchronisation, fault tolerance and data consistency at scale. Hands on experience designing and developing complex products. Extensive hands on experience in Go, Python, C, C++ or Java on Unix or Linux platforms. A strong understanding of computer architecture, data structures, algorithms, design concepts and programming practices. Experience with service oriented architecture, especially on the service backend. Desirable rather than required: excellent written and verbal communication; cloud technologies, preferably AWS; working knowledge of Docker and Kubernetes; working knowledge of storage and file systems including file system consistency checks; and hands on experience using generative AI for code generation. The real day to day: metadata versioning and change tracking across petabytes of data residing in the cloud; third party secondary storage appliance integration for data centre data protection; extending the filesystem to store workloads beyond files and folders, such as emails and messages; optimising the filesystem for cost using strategies and algorithms that leverage cheaper cloud storage tiers and reduce IO requests; and developing tools that make production issues easier to debug. The role, in the posting's framing: to be the technical owner building enterprise grade, scalable, performant systems; to design and implement large and complex features or architectural improvements; to propose solutions to complex design problems; to identify engineering improvements and work with product architects and the team on them; to technically guide junior engineers on feature design and implementation and review their work; to independently handle complex escalations; and to write technical blogs and present in internal and external forums. Qualification: B.Tech, B.E., M.E. or M.Tech in Computer Science or equivalent. Location: Pune, Maharashtra. Honest fit guidance: the cost optimisation work is worth calling out because it is unusual and genuinely interesting. Reducing cloud storage spend through tiering strategy and IO reduction is a systems problem with a directly measurable outcome, which is rarer than it sounds. The guidance and review duties are technical mentoring rather than management, with no reports or hiring involved.
Required by the posting under Must Have: 5 to 8 years of experience in AI/ML engineering with at least 2 years leading AI initiatives. Strong expertise in Python, TensorFlow, PyTorch and Hugging Face Transformers. Hands on experience with LangChain or similar LLM application frameworks. Solid understanding of vector databases, RAG architectures and prompt engineering. Proficiency in MLOps tools including MLflow, Kubeflow, Airflow, Docker and Kubernetes. Familiarity with cloud AI platforms including AWS SageMaker, GCP Vertex AI and Azure ML. Strong background in data pipelines, APIs and scalable system design. Nice to have: experience fine tuning LLMs with LoRA, PEFT or parameter efficient training; knowledge of computer vision or multimodal AI; familiarity with responsible AI frameworks and explainability tools such as SHAP, LIME and Captum; and contributions to open source AI projects. Education, and this one is a real filter: the posting requires a minimum Master's degree in Engineering, Computer Science, Mathematics, Computational Statistics, Operations Research, Machine Learning or a related technical field. If you have a Bachelor's only, this specific requisition will screen you out regardless of experience. The real day to day: building production AI systems, assessing emerging frameworks for adoption, mentoring junior AI engineers and promoting best practices in AI engineering, working with business stakeholders to translate requirements into AI driven outcomes, and ensuring adherence to responsible AI principles including bias mitigation, fairness and explainability. ⚠️ A years contradiction inside the posting, which we publish honestly rather than picking the flattering number: the Must Have section says 5 to 8 years of AI/ML engineering experience, while the Desired Experience section further down says 4 to 8 years of relevant Machine Learning experience. Sigmoid's own Greenhouse metadata records a minimum of 4 and a maximum of 8. We have published 5 to 8 because that is the harder requirement stated in the mandatory section, but if you are at 4 years the posting itself gives you grounds to apply. Note on the "leading AI initiatives" requirement: read in context with the responsibilities, this is technical leadership of AI projects and mentoring, not people management. There are no direct reports or hiring duties in the posting. Location: Hyderabad.
Required by the posting: 4 to 6 years of experience developing, enhancing and maintaining enterprise scale Security Operations and SIEM platforms based on the ELK stack (Elasticsearch, Logstash, Kibana). The posting states this bar three separate times and consistently, as 4 to 6 years in detection engineering, SIEM engineering, security operations or SOC environments, and as 4 to 6 years of overall experience as a security operations engineer in medium to large product companies. Strong hands on experience in log parser development, security content engineering, ELK administration, AWS environments, microservices architectures and open source security technologies. The real day to day: designing, developing and maintaining high fidelity detection rules, correlation rules, alerts and security use cases for new and existing log sources, and continuously tuning them to cut false positives and expand coverage; developing detection content for AWS services, Kubernetes, microservices, Linux, macOS, databases, web applications and firewalls using the MITRE ATT&CK framework, threat intelligence and adversary tactics, techniques and procedures; onboarding new log sources by building Logstash pipelines, custom parsers, Grok patterns, ingest processors and enrichment workflows, including analysing raw log formats and normalising events to a common schema; designing operational, executive, SOC and threat hunting dashboards with optimised OpenSearch Query DSL; integrating threat intelligence platforms, indicator feeds and enrichment services with OpenSearch and building indicator correlation rules; and expanding the SIEM with advanced capabilities including UEBA, anomaly detection, OpenSearch notebooks for investigation playbooks, SOAR workflows for automated response, and AI driven automation to streamline Level 1 SOC operations. Location and team: Hyderabad, in the Cloud and Product Security team within Risk and Compliance. Employment type is stated as full time. Company context worth knowing: Zeta is backed by SoftBank Vision Fund and Mastercard, reached a $2 billion valuation in 2025, and runs products including Tachyon (cloud native banking stack), Cipher (authentication) and Pixel (a digital native credit card launched with HDFC Bank). Honest fit guidance: unlike many security postings that blur into governance and compliance, this one is engineering throughout. If you can write parsers and detection content and are comfortable in the ELK and OpenSearch ecosystem, the fit is direct. If your security background is audit, policy or risk assessment, this is the wrong shape of role.
Required by the posting: 10 to 15 years of experience in site reliability engineering. Proficiency in one or more programming languages, with Python, Go, Shell and Bash named. Strong automation skills using Ansible, Puppet, Chef or custom scripts, plus infrastructure as code knowledge with Terraform. Experience with containerisation using Docker and container orchestration with Kubernetes. Proficiency in any of the major cloud platforms including AWS, Azure or Google Cloud. The real day to day, as the posting sets it out: system reliability, meaning designing, implementing and maintaining scalable and reliable infrastructure; automation of operational tasks to reduce manual intervention; incident response and resolution, monitoring performance and responding promptly to minimise downtime; capacity planning by analysing usage patterns and forecasting future needs; performance optimisation by identifying and addressing bottlenecks; infrastructure as code using tools like Terraform or Ansible; monitoring and logging to gain insight into system behaviour; collaborating with security teams on infrastructure and application security practices; disaster recovery planning so systems recover quickly from major outages; continuous improvement by analysing performance, reliability and incidents; and mentorship and coaching of team members. Location and team: Hyderabad, in the Tachyon PLE team within Engineering. Employment type is stated as full time. Why this is on an individual contributor board, and why a sibling role was rejected: we drop people management roles. Zeta is currently running several SRE requisitions, and two of them titled Lead Site Reliability Engineer contain explicit people management duties, including establishing an SRE site and building a team, leading and motivating a team of SREs, managing execution of project priorities and deadlines, and resolving conflicts within the team. Those were rejected. This Principal requisition contains none of that. Its only people related line is mentorship and coaching, which is normal for a principal IC. Company context: Zeta is backed by SoftBank Vision Fund and Mastercard, reached a $2 billion valuation in 2025, and runs Tachyon, its cloud native banking stack built for population scale systems. Honest fit guidance: at 10 to 15 years this is the senior end of the SRE ladder, and the domain is financial infrastructure where downtime has direct consequences. The requirement list is standard SRE rather than exotic, so the differentiator will be the scale and criticality of what you have run, not the tools you can name.
Required by the posting: a 3 to 5 year track record of relevant work experience with a Computer Science or related technical discipline. Experience developing enterprise scale applications and capability with frameworks and design patterns. Experience with functional and object oriented programming, with Java preferred or Python as a must. Hands on knowledge of MapReduce, Hadoop, PySpark, HBase and Elasticsearch. Development and support experience in the big data domain. Experience with database modelling and development, data mining and warehousing. Unit, integration and user acceptance testing. Effective communication skills. The real day to day: developing and evolving highly scalable, fault tolerant distributed components; designing and implementing APIs, abstractions and integration patterns for distributed computing problems; defining technical requirements, data extraction and transformation, automating and productionising jobs, and exploring new big data technologies in a parallel processing environment; application development, support, integration development and quality assurance; and interfacing daily with customers across leading Fortune 500 companies to understand strategic requirements. Two working conditions stated in the posting that you should factor in before applying: the role is client facing with daily customer interaction, and it asks you to be open to working from a client location as the demand of the project or customer requires. The posting also states the position reports to the Engineering Manager. Location: Bengaluru, Karnataka. Sigmoid's Greenhouse metadata records a minimum of 3 and a maximum of 5 years for this requisition, matching the body. Honest fit guidance: one oddity worth flagging so you are not confused in the interview. Sigmoid reuses a common responsibilities block across several postings, so this SDE II listing contains a line about providing technical leadership and managing it day to day that also appears on its Technical Lead requisition. At a 3 to 5 year band with an Engineering Manager reporting line, treat that as boilerplate rather than as a hidden management expectation, but it is fair to ask what the actual scope is. The consulting model is the more important thing to be sure about: this is enterprise client work, not internal product engineering.
Required by the posting: 6+ years of experience in Data Engineering. Strong expertise in Python, SQL and Apache Spark. Experience building scalable batch and real time ETL and ELT pipelines. Hands on experience with AWS services including EMR, S3, Glue and Athena. Experience with Kafka, Flink or Kinesis for streaming data processing. Strong knowledge of dimensional modelling, Data Vault and data warehousing concepts. Experience with Delta Lake, Apache Iceberg or Apache Hudi. Expertise in workflow orchestration using Airflow. Experience implementing data quality frameworks and monitoring solutions. Strong understanding of partitioning, schema evolution and performance optimisation. Familiarity with CI/CD, Git and infrastructure as code tools is listed as a plus rather than a requirement. The real day to day: designing and building scalable data platforms, data warehouses and lakehouse architectures; data modelling including dimensional modelling, Data Vault and enterprise data architecture; advanced SQL with query optimisation, performance tuning and large scale processing; distributed processing with Spark; designing batch, streaming and change data capture ingestion pipelines; and helping drive the platform's evolution from batch oriented processing to near real time and real time ingestion. Platform context from the posting: a multi tenant, cloud scale data platform serving thousands of dealerships and business users while maintaining tenant isolation, governance and data quality standards, feeding analytical products, operational insights and AI driven experiences. Location: Bengaluru, Karnataka. Benefits named on Tekion's postings: competitive compensation, generous stock options, and medical insurance coverage. Honest fit guidance: this requirement list is long but coherent, and it describes a modern lakehouse stack rather than a legacy warehouse one. If your data engineering has been mostly batch SQL and scheduled jobs, the streaming half (Kafka, Flink or Kinesis, plus change data capture) is the gap that will show. The multi tenancy requirement is the genuinely hard part and is rarer on a CV than Spark is.
Required by the posting: 6 to 9 years of experience in software engineering. A Bachelor's or Master's degree in Computer Science, Engineering or a related field. Proven experience leading development of distributed systems, cloud native applications or large scale platforms. Deep proficiency in programming languages, development frameworks and cloud infrastructure, with AWS, GCP and Kubernetes named. Strong problem solving, architecture design and technical mentoring skills. Excellent communication, collaboration and leadership capabilities. The real day to day: leading end to end technical execution for major projects from design through deployment and monitoring; developing and enforcing engineering standards, coding practices and architectural guidelines across teams; working with product, UX and architecture teams to define scalable technical solutions; mentoring engineers at various levels and supporting development through code reviews and knowledge sharing; investigating production issues and leading root cause analysis and long term fixes; and championing innovation, system improvements and performance optimisation. Scope, as the posting defines it in its own structured sections: job complexity is leading projects with cross functional dependencies and significant technical complexity, guiding technical strategy and driving execution. Required supervision is that the role functions independently and provides technical leadership to multiple engineers, accountable for design decisions and engineering quality. Expertise is described as strong technical depth in system architecture, application development and software design. Location: Chennai, Tamil Nadu. Why this is on an individual contributor board: we reject people management roles. This one contains no hiring responsibility, no direct reports, no performance management and no headcount language. What it does contain is technical leadership over multiple engineers, standards ownership and mentoring, which is what a staff or lead IC does. If you specifically want line management, this is not that job, and Tekion posts separate Manager, Engineering requisitions for that. Benefits named on Tekion's postings: competitive compensation, generous stock options, and medical insurance coverage.
Required by the posting: 3 to 5 years of relevant Machine Learning experience. Strong programming in Python with TensorFlow, PyTorch and scikit-learn, plus GenAI frameworks such as LangGraph, AutoGen and the OpenAI SDK, and prompt engineering on foundation models from OpenAI, Hugging Face and Anthropic. Knowledge of NLP, computer vision or generative AI covering LLMs, diffusion models, RAG, model fine tuning, conversational AI and knowledge graphs. Familiarity with cloud AI services including AWS SageMaker, Azure ML and GCP Vertex AI. Solid understanding of data structures, algorithms and software engineering principles. Hands on experience with model deployment through APIs, microservices and real time inference. Nice to have: experience with MLOps tools including MLflow, Kubeflow, Airflow, Docker and Kubernetes, and experience with big data technologies such as Spark and Hadoop. The real day to day: architecting, developing and deploying machine learning models and AI solutions into live production; partnering with data scientists to convert prototypes into scalable enterprise ready applications; designing enterprise AI systems using LLMs, RAG, knowledge graphs and multi agent orchestration; embedding AI models into existing products, APIs and enterprise systems; running experimentation, fine tuning and error analysis to improve model accuracy; monitoring, maintaining and retraining deployed models; translating business challenges into AI solutions with stakeholders; and upholding responsible AI principles. Client facing reality: the posting states you will be engaging with clients to understand their business context, and Sigmoid's work is consulting shaped for large enterprises. Its other postings note openness to working from a client location depending on the project, so ask about that during interviews. Location: Hyderabad. Sigmoid's Greenhouse metadata for this requisition records a minimum of 3 and a maximum of 5 years, which matches the body text, so the band here is reliable. Honest fit guidance: the job title says Data Scientist but the responsibilities are mostly ML engineering and deployment, not research or analysis. If you enjoy getting models into production and keeping them healthy, that is a good thing. If you want to spend your time on modelling and experimentation, read the responsibilities list again before applying.
Required by the posting: 5 to 7 years of experience in software engineering. A Bachelor's or Master's degree in Computer Science, Engineering or a related field. Expertise in one or more modern programming languages, with Java, Python, JavaScript and C++ named. Strong understanding of distributed systems, cloud native services and performance optimisation. Experience with microservices, containerisation (Docker, Kubernetes) and cloud platforms (AWS, GCP, Azure). Excellent problem solving, mentorship and communication skills. A proven track record of delivering production grade software and improving team effectiveness. The real day to day: designing and building scalable, high performance systems and services; leading feature development from concept to deployment with responsibility for quality, performance and maintainability; collaborating with architects and senior engineers to influence system design and technical strategy; mentoring junior engineers; conducting code reviews and setting engineering standards; and identifying and resolving bottlenecks in production and development. Location: Bengaluru, Karnataka. Benefits named on Tekion's postings: competitive compensation, generous stock options, and medical insurance coverage. Honest fit guidance: this is a clean senior individual contributor role with mentoring attached rather than people management, and the requirement list is generic enough that a strong backend or full stack engineer at 5 to 7 years is a genuine fit. One caution specific to Tekion: it runs multiple requisitions with identical or near identical titles across Bengaluru and Chennai at different experience bands, so confirm which requisition and which city you are being interviewed for. The company also runs a separate Lead Software Engineer role at 6 to 9 years, so there is a visible next step.
Required by the posting: 5+ years building large scale data, ML or platform systems, with strong software engineering fundamentals covering abstracted API design, concurrency and distributed systems. The requirement list also covers hybrid retrieval patterns and vector stores including pgvector, Qdrant and Milvus. Highly relevant experience the posting calls out: having built or operated an LLM gateway or control plane, covering provider adapters, routing and policies, caching, quota and rate limiting, and cost and token accounting; powering retrieval with hybrid search across graph, vector and keyword, with cache and TTL strategy to balance accuracy, latency and cost. The preferred mindset, which the posting sets out at unusual length and is worth reading as a description of the team's values: platform as product, meaning an obsession with developer experience, paved roads and clear SLAs; thinking in systems, where observability, fallback and access control are core rather than afterthoughts; genuine enthusiasm for enabling real world LLM and agentic use cases; cost awareness, treating latency and dollars as first class metrics and designing for graceful degradation; vendor agnostic thinking, choosing the right model or provider per use case and building for portability and resilience; and documentation and teaching, making complex systems understandable and upskilling teams. Location: Bengaluru, Karnataka. Benefits named on Tekion's postings: competitive compensation, generous stock options, and medical insurance coverage. Honest fit guidance: do not be put off by "Machine Learning Engineer" if you have never trained a model. The requirement set is platform engineering, retrieval infrastructure and cost control, not research. Conversely, if you are a data scientist looking for modelling work, this is the wrong role, because nothing in it asks you to build models. Note that Tekion also runs a Staff Software Engineer AI Engineer requisition at 8+ years over a near identical brief, so the same work exists at a more senior band if you are past this one.
Required by the posting: 12+ years of production level experience in one of Python, Java, Scala, C++ or a similar language. A BS or higher in Computer Science or a related field. Experience developing large scale distributed systems from scratch. Experience working on a SaaS platform or with service oriented architectures. The real day to day, as the posting frames the role: complete ownership of multiple platforms, being accountable for scalability, platformisation and reliability; designing serving infrastructure abstractions broad enough to support current and emerging use cases such as AI, determining the right tradeoffs and building consensus across the company; re architecting existing systems to handle a 10x to 100x scale increase; revolutionising platform onboarding to cut it from weeks to hours; developing features that improve product functionality and end user experience; cultivating engineering quality standards; and mentoring junior team members. The team context: the Core Experiences Platforms org in Bangalore is responsible for the main platforms used to access and interact with core assets including Workspaces, Notebooks and SQL queries, along with the serving infrastructure powering multiple user experiences. Location: Bengaluru, India, in Databricks India Private Limited. Honest fit guidance: the posting says it is seeking "exceptional technical leaders with a stellar track record", and the shape of the work backs that up: cross org consensus building, tradeoff decisions and re architecture rather than feature delivery. It is an individual contributor role, with mentoring listed rather than management, but the influence expectations are organisational. If your 12 years are deep but narrow within one team's codebase, expect the consensus and cross functional dimensions to be where interviews focus.
Required by the posting: 15+ years of industry experience building and supporting large scale distributed systems. The role as Databricks defines it: an executive engineering individual contributor with full ownership of a product or infrastructure direction in a major area, driving it from initial development through to scalable solutions with clear business impact. The posting describes the person as a force multiplier who elevates stability, reliability and organisational processes, mentors senior engineers, contributes to recruiting, and leads high impact company projects, often on problems outside their comfort zone. It reports to an Engineering Leader. The real day to day: delivering a highly scalable, available and fault tolerant engine processing hundreds of terabytes of data daily across thousands of customers; low level systems debugging and performance measurement and optimisation on large production clusters; architecture design and influencing the product roadmap; using deep experience to prevent and investigate production issues; planning and leading complicated technical projects spanning several teams; acting as a strong influencer on organisational roadmap and direction; leading a technical leadership group or similar review committee, or sustaining an engineering wide initiative; breaking complex problems into solutions, knowns and unknowns and de risking through prototyping; and contributing as a technical team lead by mentoring, leading sprint planning, delegating work and participating in project planning. Scale context worth knowing before you interview: the posting states the fleet consists of millions of virtual machines generating terabytes of logs and processing exabytes of data per day, and that at this scale cloud hardware, network and operating system faults are regularly observed and the software must gracefully shield customers from them. Location: Bengaluru, India, in Databricks India Private Limited. Honest fit guidance: read the delegation and sprint planning line carefully and decide for yourself. This is an individual contributor role by Databricks' own framing, and there are no direct reports or performance management duties in it, but the technical team lead responsibilities described are real and include delegating work and leading planning. If you want to be purely heads down at 15 years, this is not that job. If you want the largest possible blast radius without becoming a manager, it is close to the ceiling of what that looks like in India.
Required by the posting: a Bachelor's degree in Computer Science, Cybersecurity, Engineering or a related field, with equivalent experience considered. 4 to 6 years of experience in security engineering, IT security or related roles. Strong understanding of network, application and cloud security principles. Experience with security tools such as SIEM, IDS/IPS, vulnerability scanners and endpoint protection. Knowledge of cloud platforms (AWS, GCP, Azure) and their security services. Familiarity with compliance and security frameworks. The real day to day: implementing, configuring and maintaining security tools, monitoring systems and access controls; supporting vulnerability management across scanning, analysis and remediation coordination; participating in incident detection, response and root cause analysis; working with Engineering and IT to embed security practices into development and infrastructure; helping maintain compliance with SOC 2, ISO 27001 and NIST; performing security assessments and testing of applications, systems and cloud environments; contributing to threat modelling and risk assessments for new projects; creating security documentation, runbooks and knowledge bases; and providing guidance and mentorship to junior engineers. Scope, in the posting's own words: this role works on moderately complex projects with minimal supervision, partnering with IT, Engineering and Security Operations to identify risks, remediate vulnerabilities and strengthen the overall security posture. Location: Bengaluru, Karnataka. Honest fit guidance: this is a broad security generalist role rather than a specialist one. You touch tooling, vulnerability management, incident response, compliance and assessments, which is excellent for building range at this stage of a career but means you will not go deep in any single area quickly. Tekion runs several security requisitions at once, including Senior Security Engineer roles at 5 to 7 years, so if you are above this band look at those instead of stretching this one.
Required by the posting: 3+ years of experience in full stack development with strong expertise in Python and React.js. Proven experience designing, building and deploying at least one production deployed AI agent or LLM application. Deep expertise in LLM orchestration, prompt engineering and using tools and plugins to extend agent capabilities. Experience with agent frameworks like LangChain or LangGraph including implementing reasoning patterns such as the ReAct loop. Experience with observability, logging and tracing for AI agents. Experience building large scale, enterprise grade applications. Strong experience with API integration over REST or GraphQL. Experience working in Agile or Scrum environments. Preferred or good to have: Node.js or Python for middleware development, understanding of Salesforce APIs including REST, Apex and RLM/CPQ, experience with event driven architectures such as webhooks, change data capture and async processing, knowledge of CI/CD pipelines and DevOps practices, and experience with the Databricks platform and Mosaic AI. The real day to day: designing, developing and deploying AI agents for business critical workflows with a focus on LLM orchestration and tools; implementing agentic behaviours with LangChain or LangGraph including ReAct loops; building a high performance React interface for the agent; integrating APIs and services with backend teams and building tools for agents; orchestrating agent calls and data flow through Python or Node.js middleware; implementing observability and tracing for agent runs; building reusable UI components; and contributing to architectural discussions. Location: Bengaluru, India, in Databricks India Private Limited. Honest fit guidance: the years bar and the real bar are different here, and it is worth being clear about that. Three years is genuinely low for Databricks, where most of today's other India requisitions start at 10 or more. But "at least 1 production-deployed AI agent or LLM application" is a hard, checkable requirement, and the Salesforce API preference suggests this agent work plugs into internal business systems rather than the core data platform. If you have shipped an agent into production at any scale, your years matter less than that fact.
Required by the posting: a BS or above, with an M.S. or PhD preferred, in Computer Science or a related field. 10+ years of experience developing search relevance systems at scale in production or in high impact research environments. Experience applying LLMs to search relevance. Experience in one or more of query understanding, NLP, text mining, recommendations, personalisation, discovery or conversational AI. A strong understanding of computer science fundamentals. Contributions to well used open source projects. The real day to day: driving development and deployment of ML based search and discovery relevance models integrated with Databricks products; designing automated ML and NLP pipelines for data preprocessing, query understanding and rewriting, ranking and retrieval, and model evaluation, to enable rapid experimentation; collaborating with product managers and cross functional teams on the search and discovery roadmap; and building a robust framework for evaluating search ranking improvements both offline and online. The team context, in the posting's own terms: this sits in the Applied AI team, and the stated 2026 priorities are enhancing search ranking, improving query understanding, building robust evaluations and growing asset coverage. Databricks customers can hold hundreds of millions of assets, so the scale of the ranking problem is the interesting part of the job. Location: Bengaluru, India, in Databricks India Private Limited. Honest fit guidance: this is a specialist role, not a generalist senior one. Ten years of backend or general ML work without search relevance specifically will not match, because the requirement names relevance systems, ranking, and evaluation metrics as the core skill. Equally, the open source contribution line is listed as a requirement rather than a preference, which is unusual and worth taking at face value. If you have built ranking systems and can point to public work, the fit is strong.
Required by the posting (Minimum Qualifications): 5+ years of professional software development experience with meaningful time building production frontend applications in TypeScript and/or JavaScript. Browser extension development experience for Chrome, Firefox and/or Safari, with a working understanding of extension APIs, manifest versions MV2 and MV3, permission models, and the separation between content scripts, background service workers and extension pages. Strong command of core JavaScript ES6 and above plus TypeScript types, async/await, closures and modules, with a precise mental model of how the language behaves. Experience with at least one modern frontend framework or reactive UI library such as React, Vue or Svelte, and the ability to pick up new ones quickly. Proficiency with HTML5 and CSS3 including responsive, component based UIs. Plus Zscaler's standard minimum qualification on demonstrated curiosity and active use of AI tools. Preferred qualifications: having published extensions directly to a major browser store, or built extensions across multiple browser engines (Chromium, Gecko, WebKit) and reconciled their API differences; familiarity with modern frontend build tooling such as esbuild, Vite, Rollup or Webpack; and a basic understanding of web application security risks including XSS, CSRF and content isolation, plus exposure to Node.js for tooling and API integration. The real day to day: translating product requirements and UI/UX designs into well tested browser extension features spanning user facing UI through to in browser security and detection capabilities; implementing security sensitive logic that runs on every page load with minimal overhead, caring deeply about latency and memory consumption; and producing readable, modular code. Location: hybrid, Bangalore. The posting states explicitly that this is a hands on individual contributor role for someone who wants to deepen their browser platform, security and frontend engineering. Honest fit guidance: browser extension experience is the requirement that will actually filter this pool. Five years of React product work without extension internals is a weak match, because manifest versions, service worker lifecycles and content script isolation are the daily reality here. Conversely if you have shipped an extension to a store, you are in a small group and should apply even if your years are light.
Required by the posting (Minimum Qualifications): 5+ years of experience in customer facing roles with a proven blend of technical expertise and account management. Demonstrated experience leading product feature implementations and driving best practice adoption. Proficiency with operating systems including Linux, Unix and FreeBSD. Hands on experience troubleshooting network issues using tools like ping, traceroute and MTR. Solid understanding of core networking protocols including HTTP, SMTP, FTP and DNS. Preferred qualifications: experience leading discovery discussions, building high level and low level designs and managing large scale migrations; in depth understanding of enterprise infrastructure and cloud security technologies including SASE, SSE and ZTNA; and expertise in open source system administration and authentication protocols such as SAML, LDAP and OAuth. The real day to day: understanding customer goals, technical challenges and business needs to align Zscaler solutions; building relationships with key stakeholders, running periodic reviews and identifying growth opportunities; anticipating technical hurdles and providing proactive recommendations and risk mitigation; mastering Zscaler products well enough to contribute best practice content to internal and customer facing knowledge bases; and collaborating across Sales, Support and Product. Location and reporting: a hybrid role based in Bangalore, reporting to the Manager of Technical Success Management within the Customer Success department. Honest fit guidance on why this is on an engineering board: we reject sales roles with technical titles, and we check the requirement list rather than the title to decide. This one is technical from the first line, asks for hands on network troubleshooting and operating system depth, and contains no quota, revenue target or pipeline language of any kind. It manages accounts, not people, so it is not a people management role either. What it is not is a coding job. If you want to write software daily, this is the wrong seat. If you are a support, solutions or infrastructure engineer who is good with customers and wants the account relationship rather than the ticket queue, it is a strong fit.
Required by the posting (Zscaler labels these Minimum Qualifications): 3+ years of experience in software development for enterprise solutions including web based applications. Solid experience in Core Java, concurrency and distributed computing, with proficiency in SQL. Exposure to test driven development using frameworks such as JUnit, REST Assured, TestNG or Jest. Experience with HTML5, CSS3, JavaScript ES6 and above, and building responsive interfaces. Zscaler also lists demonstrated curiosity and active exploration of AI tools, with a history of integrating new technologies into daily workflows, as a minimum qualification rather than a preference, and this appears on every Zscaler posting we reviewed today. Preferred qualifications: experience developing scalable web applications handling large datasets, working knowledge of GraphQL, expertise in state management frameworks like Redux, performance optimisation including JVM tuning, and understanding of security compliance frameworks, statistics and machine learning. The real day to day: developing product features for data transformation, enrichment, analytics and user facing dashboards; designing performant web applications in ReactJS for data visualisation; building and maintaining data processing pipelines for ingestion, transformation and analysis feeding risk quantification; establishing monitoring for data platform performance and health; and working with UX/UI designers and backend engineers on end to end delivery. Location and reporting: a hybrid role based in Bangalore, India, reporting to the Senior Manager of Software Engineering in the Risk360 department. Honest fit guidance: three years is the floor across the whole of today's Zscaler set, where most other requisitions start at 5 or 8, so if you are early career and want a large security platform on your CV this is the one to aim at. Be realistic that it is a full stack job. The posting weights React and responsive interface work as heavily as the Java and SQL, so a pure backend profile is a partial fit at best.
Required by the posting (Minimum Qualifications): 5+ years of experience in C programming with a strong understanding of its core principles and performance optimisation. Hands on experience with Python and/or shell scripting for automation. Solid knowledge of Linux and FreeBSD based operating systems including process management, threading, memory management and networking. Proficiency working with AWS, Azure and GCP including creating VM images, exporting them and maintaining infrastructure. Zscaler also lists a foundational understanding of AI/ML technologies and experience leveraging, securing or positioning AI driven solutions within your domain as a minimum qualification. Preferred qualifications: experience using AI powered coding assistants and intelligent observability platforms to automate performance profiling and optimise resource utilisation; hands on experience with database internals, tuning and optimisation; and knowledge of networking concepts and protocols with hands on experience translating them into system level solutions. The real day to day: working with Linux and FreeBSD based systems including configuration and scripting for system level optimisation; creating and exporting VM images across the three major clouds; writing and maintaining automation scripts in Python or shell for infrastructure tasks, system monitoring and cloud workloads; performance profiling to identify and troubleshoot resource bottlenecks; and collaborating with senior engineers to debug system and application level issues. Location and reporting: a hybrid role based in Bangalore, reporting to the Director of Software Engineering in the Engineering department. Honest fit guidance: this is one of two Zscaler roles today at a 5 year bar and it is the more specialised of them. The requirement mix (C, FreeBSD, VM image builds, cloud infrastructure) is closer to a systems or platform engineer than to a product developer, and the job explicitly includes collaborating with senior engineers to resolve issues, which suggests a hands on contributor seat rather than an architect one. FreeBSD experience is rare enough that having it will genuinely differentiate you here.
Required by the posting: 6+ years of experience in systems programming with C/C++ preferred. Strong understanding of operating systems concepts including processes, threads, virtual memory and synchronisation. Solid knowledge of data structures, algorithms and computer architecture. Experience debugging and profiling low level code, with gdb and perf named. Familiarity with networking, storage I/O or multithreaded programming. Nice to have and explicitly not required: exposure to database internals such as query planning, indexing, storage engines and transaction processing; experience with open source database projects including PostgreSQL, MySQL and RocksDB; and knowledge of distributed systems or consensus protocols such as Raft and Paxos. The real day to day: designing, developing and optimising core components of the database engine, named in the posting as the storage layer, change data capture, connection manager and query layer; investigating and fixing complex issues around performance, memory usage and concurrency; and writing well tested, maintainable C/C++. Location and working pattern: the board lists India, the posting body names Bangalore or Pune, and it carries a hybrid tag. Confirm which of the two cities applies to this requisition before applying. What the posting offers in return, in its own framing: work on database technology used in production by large enterprises, deep technical problems, a small and highly skilled team where individual work is visible, and the chance to learn from senior engineers with database and distributed systems expertise. That last point matters if you are coming from general systems work rather than databases. Honest fit guidance: the requirement list is systems programming first and databases second, which is the same pattern as Yugabyte's other engineering roles and is good news if you have the operating systems depth but not the database background. The one thing that is not optional is comfort in C and C++ at the level where you reach for gdb and perf by reflex.
Required by the posting: 8+ years of professional software engineering experience with a strong foundation in systems programming using C/C++. A Bachelor's, Master's or PhD in Computer Science or a related field, or equivalent practical experience. Deep understanding of distributed systems fundamentals, which the posting breaks out as replication and consensus, transactions and consistency models, and fault tolerance and recovery. Experience working on storage engines, databases or other infrastructure level systems. Strong problem solving skills and the ability to operate effectively in a collaborative, distributed team. Preferred skills: hands on experience with distributed storage systems, transactional engines or consensus protocols; familiarity with LSM tree based storage engines, write ahead logs, snapshots or compaction strategies; PostgreSQL internals or other relational engine experience described as a strong plus; and prior contributions to open source systems or database projects. The real day to day: leading the design, development, testing and delivery of core storage and replication features in YugabyteDB; writing high quality C/C++ with comprehensive automated tests; participating actively in design discussions and code reviews; and troubleshooting correctness, stability and performance issues in the storage and transactions layer while collaborating with the query layer, platform and cloud teams. Location and working pattern: the board lists India and the posting carries a hybrid tag. Yugabyte's team spans 12 or more countries and multiple time zones. Honest fit guidance: "Staff" here means what it should mean. The DST team sits on consistency and durability guarantees, so the work is unusually unforgiving and the preferred list (LSM trees, WALs, compaction, Postgres internals) tells you what the interview will actually probe. If your eight years are in application or service development rather than storage and systems, the title will not carry you. If you have worked on a storage engine or a consensus implementation, this is a role where that experience is the whole point.
Required by the posting: 3 to 5 years of industry experience in a technical role. A strong technical foundation in at least two of the following: databases, distributed systems, cloud platforms (AWS, GCP, Azure), Linux/Unix administration, or programming and scripting (Python, Bash, Java and similar). Excellent problem solving and analytical skills with the ability to learn new systems quickly. Strong written and verbal communication for both technical and non technical audiences. A proactive, customer first mindset with patience and persistence. Ability to work independently in a fully remote environment while collaborating across global teams. Nice to have but explicitly not required: experience in a technical support, customer success or DevOps/SRE role, familiarity with open source and community driven projects, and knowledge of PostgreSQL or other relational databases. The real day to day: providing technically sound assistance to customers using YugabyteDB; troubleshooting distributed database, cloud infrastructure, API and application integration issues; collaborating with Engineering, Product and Documentation teams; maintaining case documentation; contributing knowledge base articles and support tooling that improve customer self service; and participating in a global on call rotation including after hours and week off support when assigned. Location, hours and schedule, all stated in the posting and all worth reading twice: the location is Remote in the APJ timezone. Work hours are aligned with early morning IST. The role requires weekend coverage, and in exchange you get two fixed, consecutive weekdays off, with Tuesday and Wednesday given as the example. If your life depends on Saturdays and Sundays being free, this specific role does not fit, however good the rest of it looks. Honest fit guidance: the posting says prior support experience is valuable but not a strict requirement, and that it is looking for technical aptitude and mindset over a support CV. That makes this one of the few realistic entry points on today's list for someone at the lower end of the range, and it is fully remote, which readers here ask for constantly. The genuine costs are the shifted hours and the weekend rota, not the technical bar.
Required by the posting: 5 to 8 years of experience with compiled languages, C or C++ specifically named. A BS, MS or PhD in Computer Science or a related field, or equivalent experience. Systems engineering fundamentals covering distributed systems, operating systems and databases, and the posting states this is a must rather than a preference. Experience with compiled languages, with C/C++ preferred and Java, Go and Rust also accepted. Listed as a plus rather than required: knowledge of database internals, compilers, and query planning or optimisation. Location and working pattern: the board lists India and the posting carries a remote tag. Yugabyte describes its team as distributed across 12 or more countries and multiple time zones. Note that other Yugabyte requisitions on this board are tagged hybrid and name Bangalore or Pune, so the remote status is specific to this one; confirm it with the recruiter before you assume it. One piece of boilerplate to ignore if you are applying from India: the posting carries a United States visa notice about H-1B sponsorship following a September 2025 proclamation. It is on Yugabyte's postings generally and has no bearing on an India based role. Honest fit guidance: the interesting detail here is that the database specifics are a plus while the systems fundamentals are a must. If you have spent five or more years in C or C++ on operating systems, networking or storage work and have never touched a query planner, this is a realistic route into database engineering rather than a wall. Yugabyte is also open source, so you can read the codebase before you interview, which is a real advantage worth using.
Required by the posting: 4+ years of experience working on a SaaS product or production platform. Strong software engineering skills with experience in distributed systems, in Go, Python or similar. Experience building cloud native services covering Kubernetes, containers, service to service APIs and CI/CD. A solid understanding of AI/ML fundamentals, and the posting is explicit that you do not need to be a researcher but should understand the concepts well enough to make sound engineering decisions. The real day to day: building and evolving backend services that power AI features, covering agent orchestration, tool execution, retrieval and RAG pipelines and model serving integrations; designing APIs and control plane workflows that are tenant aware, secure by default and observable; implementing MCP style tool discovery and integration so agents can safely call tools, connectors and internal services; engineering for reliability and scale including latency, cost controls, rate limiting, fallbacks, rollouts and incident readiness; establishing evaluation practice with offline test sets, regression detection, prompt, model and version tracking and quality gates; contributing secure by design AI work covering permissions, data access boundaries, prompt injection defences and auditability; and mentoring junior engineers. Location and working pattern: listed as India, with the requisition in SingleStore's Hyderabad office. Honest fit guidance: the phrase to take seriously is "this team is not pure research, it's engineering heavy". The hiring bar is distributed systems and cloud native services, with AI/ML understanding layered on top. If you have shipped production backend services and have taught yourself agents, RAG and evaluation properly, you are the target. If your AI experience is notebook and demo shaped, the reliability, multi tenancy and security requirements will be where it shows. Note also the security emphasis: prompt injection defence and data access boundaries are named requirements, not afterthoughts.
Required by the posting: 5+ years of experience developing and debugging system level software in unmanaged languages like C++ or Rust. A Bachelor's degree in Computer Science or equivalent practical experience. Demonstrated ability to design and build highly reliable, high performance system software. Preferred rather than required: knowledge of database architecture and operating systems, and familiarity with distributed systems managed via Kubernetes. The real day to day: developing database engine features based on company direction and customer requests; delivering code in a low level, unmanaged memory C++ environment; translating high level customer requirements into deliverable software features; learning and adapting techniques from industry and academia into SingleStore's database architecture for analytical and transactional workloads; designing and executing comprehensive engine test plans using Python, C++ and SQL; using low level debugging including GDB and flame graphs to fix problems and improve performance; working on distributed systems algorithms inside the core engine; and taking part in code and design reviews. Levelling, stated in the posting: open across multiple levels, with final levelling as Senior, Staff or Principal determined by experience, scope of impact and demonstrated technical leadership through the interview process. Location and working pattern: listed as India, with the requisition in SingleStore's Hyderabad office. Honest fit guidance: this is one of the more specialised roles on today's board. Unmanaged memory C++ plus query optimiser and SIMD work is a narrow skill set, and five years of general backend experience in Java or Python will not substitute for it. The upside is that the same posting explicitly leaves room to be levelled up to Staff or Principal, so if your systems depth is well beyond your years count, this is a posting where that can actually be recognised.
Required by the posting: 6+ years of experience developing and debugging system level software in Golang or a similar language. Familiarity with distributed systems managed via Kubernetes. Demonstrated ability to design and build highly reliable, high performance system software. Experience working in environments where performance, scalability and reliability are critical. A Bachelor's degree in Computer Science or equivalent practical experience. Preferred qualifications: experience building cloud native SaaS platforms, experience with frontend web frameworks like React, and background with cloud based metering and billing plus generally accepted accounting practices. That last one is unusual and tells you how central the billing system is to this particular seat. The real day to day: leading technical design and decision making for large, release defining projects on the cloud platform; designing and implementing capabilities across networking, control plane and managed service infrastructure with the main focus on billing systems; solving mission critical system problems; working with Product Management to turn customer and business requirements into technical solutions; investigating and resolving difficult production and development issues; debugging billing data synchronisation problems; contributing to data visualisation dashboards; and mentoring engineers on system design, coding standards and architecture. Levelling, stated in the posting: open across multiple levels, with final levelling as Senior, Staff or Principal determined during the interview process. Location and working pattern: listed as India. Unlike SingleStore's other India requisitions this one carries no office tag on the board, so confirm the working location with the recruiter before you commit. Honest fit guidance: read the billing emphasis carefully rather than skimming past it. Metering and billing is real distributed systems work with correctness requirements most services never face, but if you are hoping for database internals this is not that job. The mentoring expectation is stated as raising the technical bar across the team, not as managing people, so it remains an individual contributor role.
Required by the posting: a B.S. degree in Computer Science, Electrical Engineering, Computer Engineering or a related discipline. Deep understanding of computer science fundamentals, particularly operating systems, concurrency, multithreading and server architectures. Strong programming skills in C++ or C. A firm grasp of algorithms and data structures. A stated passion for building highly reliable software. That is the complete requirement list. There is no years of experience bar anywhere in this posting, and no prior industry experience is asked for. The real day to day: the posting names the actual projects rather than speaking in generalities. Engineers here work on cutting edge areas like LLM support and vector indexing, improving the fault tolerance of a SingleStore cluster, accelerating SQL query performance with techniques such as SIMD vectorisation and LLVM code generation, or writing the search and costing modules inside the query optimiser. The posting says its University Graduates are responsible for both brand new and existing projects that get deployed into production with each release, and that the work spans writing software through to testing it. Teams are small and collaborative, with release cycles running throughout the year. Location and working pattern: the board lists the location simply as India, and the requisition sits in SingleStore's Hyderabad office. SingleStore is headquartered in San Francisco with offices including Bangalore and Hyderabad in India. Honest fit guidance: this is the most accessible role in today's edition by a wide margin, and it is the first explicit graduate requisition this board has carried since 2026-07-30. The trade is that the bar is depth rather than years. C++ on a distributed database engine is unforgiving work, and the posting expects operating systems and concurrency knowledge you can actually use, not just coursework you can name. If you are a final year or recently graduated CS student who has written real C or C++ beyond assignments, apply. If your background is web development in higher level languages, this specific team is a stretch, and SingleStore's other India postings sit at 3 years and above.
Required by the posting: 3+ years of experience with one or more general purpose programming languages including but not limited to Python, C/C++, JavaScript or Go. Comprehension of GitOps and managing infrastructure as code. Experience with databases, particularly SQL based ones. Experience with containers and Kubernetes based applications running in public cloud or in on premises data centres, and the posting notes you will have both available to you. Deep interest and experience in distributed systems, databases, networking, storage, multi tenant services and Unix/Linux environments. A B.S. degree in Computer Science or a similar field, or equivalent working experience. The posting also asks for strong empathy toward fellow developers and a passion for quality engineering and software testing efficiency, which fits a team whose customers are other engineers. The real day to day: building observable, microservice oriented applications that let SingleStore engineers build and test in a multi cloud environment; designing technical solutions that raise engineering productivity company wide; and improving CI/CD throughput, debugging and triage operations, and workload execution runtimes for a global engineering workforce. Levelling, stated in the posting: this role is open across multiple levels, and final levelling as Senior, Staff or Principal is determined by experience, scope of impact and demonstrated technical leadership through the interview process. Treat 3 years as the entry bar rather than the target. Location and working pattern: listed as India, with the requisition sitting in SingleStore's Hyderabad office. Honest fit guidance: internal developer platform work is a genuinely good career move at 3 to 5 years because you touch build systems, cloud, Kubernetes and testing at once, but it is not product engineering and your users are colleagues. The posting is clear that it wants someone who enjoys mentoring while staying hands on. If you want to be close to the database engine itself, SingleStore's Database Engine postings are the ones to look at instead.
Required by the posting: 10+ years building systems software in C/C++ or Rust, with Go experience noted as a plus. Deep knowledge of PostgreSQL or other database engine internals, specifically storage, execution or replication subsystems. Strong understanding of concurrency, operating systems and performance engineering. A proven record of shipping large scale systems or core infrastructure features end to end. The posting adds two temperament requirements: a pragmatic problem solver with a bias for simplicity and measurable impact, and someone who thrives in a high autonomy, high velocity environment. Highly desirable rather than mandatory: experience contributing to open source databases or comparable complex systems. Given that ClickHouse itself is open source with more than 42,000 GitHub stars, a visible contribution history is worth more here than at a closed source employer. The real day to day: leading design and implementation across storage, replication, query execution and performance; contributing to and extending Postgres internals; prototyping extensions that integrate with cloud native infrastructure; profiling with low level instrumentation and benchmarking; setting engineering standards; and driving projects from concept to production with significant autonomy. Location and working pattern: India (remote). ClickHouse is a globally distributed company operating in over 20 countries with a home office allowance for remote staff. The same role is also posted for the Netherlands and the United States; this is the India requisition. Honest fit guidance: this is a genuine principal level job, not a senior job with an inflated title. The team is described as small and high talent, and the role expects you to work independently across complex areas and mentor other senior engineers. If your ten years are in application development rather than systems or database internals, the years bar will not carry you. If you have engine level work to point at, it will.
Required by the posting: 5+ years in Professional Services, Support, Technical Account Management, Engineering/SRE and/or Project Management roles, AND 5+ years of relevant industry experience implementing, operating or supporting scalable, fault tolerant distributed database management systems. Technical breadth and depth across DBMS, OLAP, cloud and SaaS platforms, distributed systems software engineering, Linux and Unix, and Kubernetes. The real day to day, as the posting itself splits it: 50 percent project engineering and consulting, meaning design, architecture, integration, implementation and documentation, plus research, benchmarking, performance and functional testing, reference architectures, sizing, migration and tooling. The other 50 percent is case initiated consultative support for strategic users, customers and prospects, covering implementation, onboarding, production launches and proofs of concept. You also handle L1 to L3 support cases when not assigned to a project, partner with Product Management, Engineering and Sales on the roadmap and account plans, produce public and internal documentation, knowledge base articles, learning content, reference architectures, blogs and benchmark results, and assist with hiring and mentoring as the team grows. Location and working pattern: India (Remote), and this requisition sits in ClickHouse's India office within the Support Services department. Two commitments the posting states plainly and you should weigh before applying: you must be available for scheduling and on call to deliver 24x7 support in a global distributed environment, and the role carries up to 35 percent estimated onsite regional travel. That is a materially different life to a desk based remote engineering job, and it is the honest reason this one sits in our customer facing group rather than the main engineering list. Honest fit guidance: this is technical delivery work with customers attached, not pre sales. The requirement list is engineering led (two separate five year bars, both technical) and there is no quota, no pipeline target and no selling language anywhere in it. If you are a support or professional services engineer with genuine DBMS depth and you want the remote flexibility, this fits. If you want to stay heads down in a codebase, the customer half will grate.
Required by the posting: solid professional software development experience in C++ including Unix systems work, strong knowledge of database internals and design, experience in performance engineering (the posting explicitly accepts adjacent fields such as high frequency trading, simulation or real time data processing rather than requiring database work specifically), strong production debugging, and willingness to work openly with an open source community, which here means resolving GitHub issues, reviewing and finishing community pull requests, and answering questions on mailing lists, chats and external Slack channels. Nice to have, listed as bonus points: prior ClickHouse experience, security, privacy and compliance exposure, TCP/IP and network programming, cloud infrastructure work with Kubernetes, public speaking at technical conferences, and previous open source contributions. The real day to day: analysing and optimising the core database, extending performance tests against real world and synthetic datasets, assessing the performance impact of new features from other core teams, and acting as an escalation resource for Support Engineering. Location and working pattern: the board lists this as India (remote), and the posting adds that the role can be located anywhere ClickHouse has a hiring presence. ClickHouse describes itself as a globally distributed, remote friendly company operating in over 20 countries, and offers a home office setup allowance to remote employees. ClickHouse posts this same role separately for the United States, United Kingdom, Germany and the Netherlands; the requisition linked here is the India one. Honest fit guidance: this posting states NO years of experience anywhere, which is why our experience filter cannot place it. Do not read that as an open bar. The requirement set (C++ plus database internals plus performance engineering) is a senior profile in substance, and the compensation section is written for United States salary bands, so the level is set by what you can demonstrate rather than by a number. If you have shipped low level optimisation work you can point at, apply regardless of your years.
Required by the posting: 6+ years in software engineering, ideally building or operating database or cloud platform systems. Deep Postgres understanding across configuration, extensions, operations and performance tuning. Strong programming in one or several of Ruby, Go, Rust, C or Python, plus a stated willingness to work across languages rather than stay in one. Familiarity with cloud infrastructure, APIs and automation tooling (Terraform, Kubernetes, CI/CD). Understanding of distributed systems, data replication and service orchestration patterns. The posting also asks for a specific mindset rather than more tools: pragmatic and detail oriented, comfortable with both greenfield development and operational ownership, and happy to contribute wherever needed, from backend APIs and platform automation through to Postgres internals and debugging. The real day to day: designing backend services that orchestrate database clusters in ClickHouse Cloud, extending the control plane for new Postgres capabilities, contributing to Postgres extensions and data plane agents, building provisioning and scaling automation, developing APIs and integrations, improving observability and debugging workflows, and participating in design discussions, code reviews and on call rotations. Location and working pattern: India (remote). ClickHouse is a globally distributed, remote friendly company operating in over 20 countries and provides a home office setup allowance for remote employees. The same role is posted separately for the Netherlands and the United States; this is the India requisition. Honest fit guidance: the posting describes itself as a flexible, full stack systems role where boundaries are fluid. If you want a narrow, well bounded backend brief, this is not it. If your Postgres knowledge is operational rather than internals deep, you can still be credible here, because the control plane and automation half of the job is as large as the extensions half. Apply if you are at 6 years or beyond and can show real Postgres depth.
Required by the posting: 7+ years in SRE, DevOps or infrastructure engineering with a track record of running distributed, production grade systems. Solid Postgres operations, scaling and performance tuning. Deep hands on AWS with exposure to GCP and Azure, and comfort navigating multi cloud topologies. Proficiency with Terraform, Kubernetes and container based infrastructure. Strong Go development skills, or a stated willingness to write and own production Go. Familiarity with observability tooling such as Prometheus, Grafana, Loki or OpenTelemetry. Deep understanding of SLOs, incident response and continuous reliability improvement. The real day to day: leading reliability and operations for the Postgres integration including upgrades, patching, maintenance and scaling; designing provisioning, deployment and lifecycle automation across the three major clouds; writing infrastructure as code; contributing Go tooling; owning alerting, metrics and tracing; driving incident management and postmortem practice; and mentoring engineers as the team scales. Location and working pattern: India (remote). ClickHouse operates in over 20 countries and provides a home office setup allowance to remote employees. The same requisition also exists for the United States; this is the India one. Honest fit guidance: the posting asks for a "founder's mentality" and describes the role as hands on and high impact, which in practice means the automation, the code and the on call are all yours rather than split across a platform team. If you are an SRE who mostly operates other people's tooling and does not write production Go, expect that to be the gap they probe. Postgres operations depth is the other hard requirement and is harder to fake than the cloud list.