What this edition tells you
Two genuine 1 to 3 year openings today, which is the most this list has carried in weeks. Zscaler is hiring a Software Development Engineer who will write custom Jira apps and plugins in Java and Groovy, and the posting says outright that internships, co-ops or substantial project work count instead of professional years. Meesho is hiring an SDE II on its data platform, also at 1 to 3 years, and that one is real distributed data work: Kafka, Spark on EMR, Flink, Presto, tuning at terabyte scale.
Read the Meesho posting carefully though, because it argues with itself. The requirements say 1 to 3 years. The responsibilities section, a few lines above, says you will oversee your entire team's work, plan long term strategies for junior engineers and provide management mentorship. Those two things cannot both be true. It reads like a senior job description was pasted over a junior requisition and shipped without anyone reading it end to end. We have listed it at the stated 1 to 3 years because that is what the requirement list says, and the job page spells out the contradiction so nobody walks into that interview surprised.
One more thing worth knowing before you sort by title. Zscaler's Senior Software Development Engineer asks for 3 to 4 years. Okta's Principal Software Engineer roles ask 7 years for the Windows one and 12 for the AI Engineering one. Same seniority word, a decade apart.
Here is today's complete edition in one place:
https://www.munotes.in/dailytechjobs/2026-08-07
No roles match that combination.
Added August 7, 2026
Zscaler asks for 1 to 3 years of software development experience, and states plainly that equivalent experience through internships, co-ops or substantial project work counts. That wording is why this role sits at the bottom of today's list: it is one of the few postings on the board that tells a recent graduate they are eligible. What you will actually do: build, test and maintain custom Jira Data Center apps, plugins and scripted extensions using Java, Groovy and the Atlassian SDK. Build and maintain integrations between Jira and Confluence, ServiceNow, Slack, CI/CD pipelines and SSO using REST APIs and webhooks. Work directly with business and engineering stakeholders to turn raw requirements into workflows, schemes, permissions, automation rules and reporting. Contribute to the Jira Data Center to Cloud migration through app compatibility assessments, data mapping, migration tooling, dry runs and post migration validation. Support platform operations alongside the team: upgrades, patching, performance tuning and troubleshooting production issues on AWS. Location and office: hybrid, based in Bangalore. Honest fit guidance. Be clear eyed about what this is. The artifact is Zscaler's internal engineering tooling, not the security product, so if your goal is to work on the Zero Trust Exchange itself this is the wrong door. What you get instead is genuine Java and Groovy development, real API integration work, AWS operations exposure and a platform migration to put on a CV, at an experience bar almost nothing else on this board will accept. Zscaler also states it expects candidates to actively use AI tools in their work, and lists that as a minimum qualification rather than a nice to have.
Meesho asks for a Bachelor's or Master's in Computer Science and at least 1 to 3 years of professional experience, plus 1+ years each with big data systems (Kafka, Spark or EMR, Hive or Impala, Delta Lake, Presto, Airflow), hands on implementation and performance tuning of Spark, Delta Lake or Presto at terabyte scale, and building streaming solutions with Flink, Spark Streaming or Samza. You need to have written code in at least one of Java, Scala or Python and to understand the AWS big data stack. Nice to have: contributor or committer history on the big data stack, data modelling and end to end pipelining, OLAP cubes and BI tools, working knowledge of ELK, Redis and MySQL, and RxJava, Java Spring Boot and microservices. Location: Bangalore. ⚠️ Read the responsibilities section with care, because it contradicts the experience bar. Under About the role the posting says you will oversee your entire team's work, plan long term strategies for junior engineers, monitor project progress and provide management mentorship. That language cannot be describing a 1 to 3 year job, and it reads as copy paste from a more senior template, which Meesho has left in place. The requirement list underneath it is unambiguously an individual contributor data engineering list. We have published it at the stated 1 to 3 years and flagged the contradiction rather than quietly picking one. If the split matters to you, ask on the first call which version of the role is being hired. Honest fit guidance: this suits someone who has already touched Spark or Kafka in a first job or a serious internship and wants volume and scale rather than greenfield. If you have never run a pipeline in production, the 1+ years of specific big data experience is a real gate, not a soft preference.
Observe.AI asks for 2+ years building large scale products, expertise in Java or Golang, good knowledge of at least one SQL or NoSQL database (Postgres, MongoDB, Cassandra, Redis), and hands on experience with telecom protocols (SIP and SDP, RTP), plus SIPREC, REST APIs, WebSockets, WebRTC and gRPC, and tools like Wireshark and Postman. Container management (Docker Swarm, Kubernetes) is listed as a plus. The day to day is a genuine mix of engineering and customer contact: driving technical discovery calls with clients, running feasibility studies on a customer's CCaaS offering, writing the design document and execution plan, building a proof of concept to validate the integration, then coding, unit testing and deploying it to production. You will also guide junior engineers on technical questions, handle customer escalations, join live troubleshooting sessions, and work with pre sales, customer success and implementation managers. Location: Bengaluru. Benefits named in the posting include medical insurance with free online doctor consultations, privilege and sick leave per the Karnataka Shops and Establishments Act, national and festival holidays, and parental leave. Honest fit guidance: the telecom protocol list is the real filter here, not the years. Two years is a genuinely accessible bar, but SIP, RTP and SIPREC are specialist knowledge that most 2 year backend engineers will not have, and the posting lists them as requirements rather than preferences. If you have worked anywhere near voice, telephony or contact centre infrastructure this is a strong fit. If you have not, expect to make the case on protocol fundamentals. Note also that this is not a heads down coding seat: direct client calls and escalations are in the job.
MongoDB asks for 3+ years of professional software engineering experience building and supporting production systems, strong coding in a modern language such as JavaScript or Python, and experience building web applications, backend services, APIs, data pipelines or internal platforms. It also wants solid fundamentals (testing, debugging, code quality, maintainability), experience with cloud services and CI/CD, the ability to work across systems with cross functional partners, strong written and verbal communication, and specifically experience partnering with marketing, sales and revenue operations teams to turn business requirements into technical specifications. Nice to have: go to market platforms such as Marketo, Salesforce, Segment or ad platforms, analytics or experimentation platforms, the ability to map a lead's path from website through to opportunity, familiarity with data pipelines, event instrumentation or web performance optimisation, and experience integrating AI or ML capabilities into products or developer tooling. How success is measured, published by MongoDB: in the first 3 months, understand the team's systems and standards, contribute code and take ownership of scoped work. In the first 6 months, independently deliver meaningful features across one or more team owned systems and improve at least one area of reliability, automation, documentation or developer workflow. Location and office: MongoDB states it is looking to speak to candidates based in Gurugram, for its hybrid working model. Not remote. Honest fit guidance: this is martech engineering, and you should want that. The systems are internal and the stakeholders are marketing and revenue operations, so a large part of the job is translating their requirements. If you want to work on database internals at MongoDB, this is the wrong requisition. If you want a 3 year bar, real backend ownership and a company that has written down what good looks like at 3 and 6 months, it is a strong one.
Zscaler asks for 3 to 4 years of software engineering experience, including ownership of complex production systems and a demonstrated ability to lead technically ambiguous, cross functional projects. Note the gap between that figure and the title: this is posted as a Senior Software Development Engineer and reports to a Director of Software Engineering, but the stated bar is 3 to 4 years. Job titles mislead in both directions on this board, and this is today's clearest example in the accessible direction. What the role expects: lead the design and delivery of major product capabilities, owning projects from problem definition through implementation, rollout and production operation. Design secure, reliable, scalable systems with clearly defined trust boundaries. Lead complex investigations while improving engineering practices, testing and operational readiness. Mentor engineers and give direction through design and code reviews. Partner with product and research teams and contribute to technical strategy and longer term architecture. Location and office: hybrid, based in Bangalore, with Mohali also listed on the requisition. Honest fit guidance: the domain is the draw. Securing AI applications and agents is new enough that nobody has a decade of experience in it, which is plausibly why the years bar is set where it is. Zscaler's culture section is unusually specific about wanting people who work in ambiguity and use AI tooling actively, and it lists AI fluency as a minimum qualification. If you are three years in, have shipped something you owned end to end, and want a senior title on a product that is being defined right now, this is one of the best value roles in today's list.
Paytm asks for 3 to 5 years of experience in DevOps engineering. The rest of the requirement list is unusually specific, and worth reading as a checklist: Strong practical knowledge of AWS infrastructure, specifically EC2, load balancers, CloudFront, ElastiCache, EBS, S3, IAM, CloudWatch, Auto Scaling and Lambda. Very good experience in infrastructure automation with Ansible, Terraform, CloudFormation or similar. Hands on Kubernetes, EKS, Docker or ECS. Hands on automation scripting in Shell, Python or PowerShell. Strong experience with Jenkins, Maven or Gradle. Experience with DevOps and CI/CD pipelines using Jira, Confluence, Jenkins, Git, Maven, Nexus and Docker, including CI/CD automation for EC2, ASG, EKS and ECS using Helm and Jenkins. Understanding of open source server software such as Tomcat, HBase, Kafka, MySQL, Redis and Elasticsearch. Experience with configuration management and Agile. Listed as a big plus rather than required: hands on experience with any of Hadoop, Kafka, EMR, Ranger, Spark, Hive, Starburst, Looker, TigerGraph or Neo4j. Location: Noida, Uttar Pradesh. This is one of only a handful of roles in today's edition outside Bangalore. Honest fit guidance: this is a checklist posting, which cuts both ways. It tells you exactly what to prepare, and there is no ambiguity about the stack. But the list is long for a 3 to 5 year bar, so expect the interview to probe breadth rather than depth on any one tool. If you have run AWS and Kubernetes in production and written your own Terraform and Jenkins pipelines, you can map yourself against this posting line by line before you apply, which is more than most postings allow.
CloudSEK asks for 3+ years of experience in threat intelligence, malware analysis, threat hunting or digital investigations, and a strong working grasp of MITRE ATT&CK, MITRE Engage, the Diamond Model and the Cyber Kill Chain applied in operational and strategic research contexts. The stated responsibilities: conduct ransomware initial access vector mapping to understand infiltration patterns, affiliate ecosystems and monetisation structures. Perform e-crime and underground forum research to identify, profile and map threat actors, their infrastructure, tools and tradecraft. Execute infrastructure hunting campaigns against APT and e-crime command and control frameworks using passive DNS, TLS certificates and web fingerprinting. Develop and maintain cyber HUMINT sources for early warning, infiltration and intelligence collection. Correlate and analyse global threat campaigns across ransomware, APT and e-crime activity. Location: Bengaluru. Company context worth knowing: CloudSEK won the NASSCOM DSCI Excellence Award for Security Product Company of the Year in 2020 and the NASSCOM Emerge 50 Cybersecurity Award, joined the NVIDIA Inception Program, raised a $7M Series A led by MassMutual Ventures in 2021, and secured $19 million in 2025 led by Tenacity Ventures and Commvault. Honest fit guidance: this is a specialist seat and the 3 year bar is doing less work than the skills list. If your background is SOC alert handling you are not automatically a match, because the job is proactive hunting and source development rather than responding to what a tool surfaces. If you already read threat reports critically, have tracked an actor's infrastructure yourself, and are comfortable operating in underground communities, this is one of the more genuinely interesting security roles on the board.
Tekion asks for 4+ years of experience in manual and automation testing of web applications. The duties as published: design, develop, execute and maintain test cases and scripts for functional, regression, integration and system testing. Create and enhance automated test scripts for recurring scenarios and critical workflows. Analyse product requirements, technical specifications and user stories to ensure coverage. Identify, document, prioritise and track defects through resolution, partnering with developers on root cause analysis. Validate new features, enhancements, bug fixes and release candidates across web, mobile, APIs and platform applications. Participate in sprint planning, backlog grooming, stand ups, retrospectives and release readiness discussions. Collaborate with engineering, product and DevOps on test strategy, environments and release quality. Maintain test documentation, test data and traceability. Support API, database and end to end testing. Contribute to QA process, framework and standards improvement. Mentor junior test engineers on execution, defect documentation and quality practice. Tekion also publishes its own levelling notes for the role: job complexity is moderately complex testing across multiple features or components, balancing manual and automated work and identifying risks proactively. Required supervision is general, with the ability to manage routine testing activities independently. Location: Bangalore HQ. Honest fit guidance: if you want to move to pure automation, read the duties again. Manual testing is explicitly half of this job and Tekion does not hide it, describing automation expertise as growing rather than expert. That honesty is useful. As a 4 year role with clear scope, defined supervision and a real product behind it, it is a solid step, but it is not an SDET role in the sense of building frameworks all day. Tekion's own SDET postings at 5 to 8 and 8+ years are the ones that do that.
Tekion asks for a Bachelor's degree in Computer Science, Cybersecurity, Engineering or a related field (equivalent experience considered) and 4 to 6 years of experience in security engineering, IT security or related roles. Required knowledge: strong understanding of network, application and cloud security principles. Experience with security tools including SIEM, IDS and IPS, vulnerability scanners and endpoint protection. Knowledge of cloud platforms (AWS, GCP, Azure) and their security services. Familiarity with compliance and security frameworks (NIST, ISO 27001, SOC 2, CIS). Scripting or automation experience in Python, Bash or equivalent is preferred. Strong analytical and problem solving skills and good written and verbal communication. Industry certifications such as CISSP, GSEC or CEH are preferred, not required. Day to day: implement, configure and maintain security tools, monitoring systems and access controls. Support vulnerability management including scanning, analysis and remediation coordination. Participate in incident detection, response and root cause analysis. Work with engineering and IT to embed security practice into development and infrastructure. Help maintain compliance with SOC 2, ISO 27001 and NIST. Perform security assessments and testing of applications, systems and cloud environments. Contribute to threat modelling and risk assessments. Maintain security documentation, runbooks and knowledge bases. Provide guidance and mentorship to junior engineers. Location: Bangalore HQ. Honest fit guidance: this is a broad generalist security seat, not a specialist one. You touch tooling, compliance, incident response and assessment rather than going deep on any single one, which suits someone who wants range at the 4 to 6 year mark and suits a specialist less well. The certifications are preferred rather than required, so do not self reject over them.
Commvault asks for a Bachelor's degree and 4+ years of experience in backend software development, with strong proficiency in C++ and SQL. It also wants a solid understanding of algorithms, data structures, multithreading and system design, experience with Linux development and performance optimisation, and strong ownership, problem solving, communication and mentoring skills. Security and SaaS experience is strongly preferred. What you will do: build scalable systems with a focus on performance, concurrency and efficiency. Design and optimise SQL queries and database schemas for large scale workloads. Drive technical design and end to end delivery of complex features. Use AI assisted and agentic coding tools to improve development productivity and code quality. Mentor engineers through code reviews, design discussions and technical guidance. Location: Bangalore and Pune are both listed on this requisition. Benefits named in the posting: employee stock purchase plan, continuous professional development and product training with career pathing, annual health check ups, a car lease programme, tuition reimbursement, personal accident cover and term life cover, and internal Community Guilds. ⚠️ Worth reading before you apply: Commvault opens this posting with a recruitment fraud warning. It states that Commvault does not conduct interviews by email or text and will never ask for sensitive documents such as banking information or national ID numbers before your first day, and gives wwrecruitingteam@commvault.com for reporting suspected scams. Apply through the official link on this page and treat any off channel approach as suspect. Honest fit guidance: modern C++ plus SQL at depth is a narrower skill set than generic backend, so the 4 year bar is generous only if you actually have the C++. If your background is Java or Python services, this is a harder sell than the years suggest.
Okta asks for 5+ years of experience working on large scale systems or services, previous experience using Node.js (TypeScript or JavaScript) to build backend services and create and maintain public or internal APIs, experience with SQL (PostgreSQL) and NoSQL (MongoDB), and experience with containerisation (Docker) and cloud environments (AWS or Azure preferred). Full stack background is a plus rather than a requirement: the role is backend focused but a portion of the work involves React. Okta also asks for someone who communicates and mentors well, and who works autonomously while knowing when to ask for help. What you will be doing: collaborate with engineers inside and outside the team to design and deliver new APIs and features for B2B customers. Drive technical improvements to the codebase and architecture for reliability, maintainability and scalability. Mentor and coach other engineers on engineering practice and testing. Work with the Product Manager and Product Designer to define new features and review customer feedback. Participate in the team's on call rotation. Location and office: Bengaluru, hybrid. ⚠️ Okta currently has many near identical Bengaluru engineering titles open at once, several of them called simply Senior Software Engineer. They are different teams with different stacks and different experience bars. This one is Auth0 Enablement: Node.js, TypeScript, PostgreSQL, MongoDB, B2B enterprise APIs, 5+ years. Check the team paragraph on the posting matches the one described here before you apply. Honest fit guidance: on call for a Tier 0 service is a real commitment and the posting is upfront about it. If you want Node and TypeScript at genuine scale with clear enterprise customers on the other end, this is a good fit at five years.
Okta asks for 5 to 8 years of software development experience. Beyond that: proficiency in Go or a genuine desire to learn it (the posting allows both), experience managing infrastructure with Terraform, experience with Kubernetes and CI/CD, comfort working with data storage systems at scale in a team environment using PostgreSQL, MongoDB, Redis and DynamoDB, comfort with datastore reliability work (standard configurations, latency, throughput, availability, utilisation indicators, performance analysis), and experience with Azure or AWS. Okta also asks for someone who delivers work incrementally to get feedback and iterate. What you will do: develop the large, distributed, highly available infrastructure. Implement platform tools that let feature teams deploy and manage the datastores for their services. Research new technologies to accelerate new environment creation. Carry cross team initiatives end to end, covering code reviews, design reviews, operational robustness and security hygiene. Participate in the team's on call rotation. Location and office: Bengaluru, hybrid. ⚠️ As with Okta's other Bengaluru listings, the title on the board is just Senior Software Engineer. This is the Datastores Engineer seat on Platform Infrastructure at 5 to 8 years, which is a different job from the Auth0 Enablement role also in today's edition. Confirm the team paragraph before applying. Honest fit guidance: this is a platform and infrastructure role, not product engineering, so your users are other engineers. The posting is unusually welcoming on language, allowing a desire to learn Go rather than demanding years of it, which widens the door for strong infrastructure people coming from other stacks. The real requirements are the datastore and Terraform experience. Cross organisation coordination is named as something you should not be intimidated by, which is a fair warning that influence is part of the work.
Okta asks for 5+ years of professional expertise in native Android development using Kotlin and Java, and 3+ years of hands on expertise building production interfaces with Jetpack Compose. The posting names the most vital qualifications explicitly: deep Android engineering expertise, strong empathy for developers, self direction and a collaborative mindset. What you will be doing: architecting and developing composable, production ready UI components from the ground up using Jetpack Compose, and traditional XML views where necessary. Directly shaping, developing and maintaining the open source Universal Components Android SDKs and client libraries. Writing, curating and polishing technical content including tutorials, guides, sample applications and comprehensive API documentation. Engaging directly with the open source developer community, providing domain knowledge and technical assistance. Serving as the go to technical expert internally, working across developer relations, onboarding, growth, dashboard and core SDK teams. Location and office: Bengaluru, hybrid. Honest fit guidance: read the content and community half of this job as real work, not garnish. Roughly speaking you are a library maintainer with a public audience, which means writing documentation and answering developers in open channels is part of the week, not an interruption to it. That suits some Android engineers very well and frustrates others. If your satisfaction comes from shipping user facing app features on a product surface, this is the wrong seat. If you have ever been the person on your team who owns the shared UI module and cares how the API reads, it is a strong one. The 3+ years of production Jetpack Compose is the tighter of the two experience gates.
MongoDB asks for 5+ years of experience building backend systems, primarily in Node.js and TypeScript, with an interest in working across a polyglot codebase. It also wants a strong background building core components for scalable, high availability web applications and services, proven success designing, writing, testing, debugging and performance tuning software in large long lived codebases, and a track record of delivering complex projects independently with minimal guidance. Beyond the technical list it asks for a product minded approach, comfort operating amid ambiguity and rapidly evolving technology, collaboration and intellectual honesty, and excellent technical communication. Position expectations: work with research, product management, product engineering and design to define the first version and future evolution of the AI interfaces. Design, build and deliver well tested core pieces of the platform, including the MongoDB MCP Server, Agent Skills, the Intelligent Assistant Platform and purpose built agents. Take ownership of ambiguous problems and drive them to completion independently. Contribute to architecture, code reviews, development practice and developer experience as the team and product grow. Mentor fellow engineers. ⚠️ Two hard constraints stated in the posting. First, this position requires participation in a 24 by 7 on call rotation for business continuity and incident response. Second, MongoDB is looking to speak to candidates based in Gurugram, for its hybrid working model. Neither is negotiable in the text. Honest fit guidance: a new team charting new territory means less structure and more ambiguity, which MongoDB states plainly rather than selling around. If you want a defined roadmap, this is not it. If you want to build the agent interface layer for a database tens of thousands of teams use, at 5 years, it is a rare seat. Weigh the 24 by 7 on call against that honestly.
Tekion asks for 5+ years building large scale data, ML or platform systems, with strong software engineering fundamentals covering abstracted API design, concurrency and distributed systems. Responsibilities as published: build and run the LLM control plane and gateway (smart routing, rate limits and quotas, failover, token and cost tracking). Ship a unified API and SDKs over REST and gRPC with normalized schemas, structured outputs, caching and full observability across traces, logs and metrics. Enforce safety and privacy by default through content filtering, prompt and response validation and PII redaction. Enable multi model and multi vendor LLM use with automated canarying and versioning. Operationalise a graph based contextual ecosystem so agents retrieve the right context and enforce policy. Maintain and enhance the platform to support classical supervised and unsupervised ML models. What Tekion says makes it distinctive: end to end ownership of an LLM control plane serving multi tenant workloads under SLAs with quality and cost guardrails, and a rich vertical dataset and domain graph spanning sales, service, parts, finance and insurance, accounting and consumer touchpoints. Improvements in latency, reliability, evaluation quality and safety map to dealer outcomes such as upsell, cycle time, customer satisfaction and service revenue. Explicitly valued: having built or operated an LLM gateway or control plane before, including provider adapters, routing policies, caching, quota and rate limiting, and cost and token accounting. Location: Bangalore HQ. Honest fit guidance: this is platform engineering that happens to serve AI, so the skills that matter are distributed systems, API design and observability rather than model training. If your AI experience is fine tuning and prompt work but you have never run a gateway or thought about tail latency and cost attribution, expect the interview to go somewhere you are not ready for. Conversely, a strong backend or platform engineer with limited LLM exposure is a better fit here than the title suggests.
Tekion asks for 5 to 8 years in SDET, quality engineering or software engineering with a strong track record building test automation frameworks, plus strong programming in Python (preferred for ML tooling) or Java, with the ability to write production quality automation code. Also required: hands on experience testing data intensive or ML and AI systems, or a strong software testing background with demonstrated ML and LLM fluency. A solid understanding of ML concepts including model training and inference, evaluation metrics such as precision, recall and F1, and the non deterministic nature of model outputs. Experience designing evaluation frameworks or working with eval datasets, benchmarks or LLM as judge approaches. Familiarity with LLM and agent concepts covering prompting, RAG, embeddings and vector search, and with generative failure modes including hallucination, drift and prompt sensitivity. Experience with CI/CD, test orchestration and API and integration testing. Strong analytical and debugging skills, comfortable with root cause analysis across model, data and code layers. Location: Bangalore HQ. Honest fit guidance: note the deliberate either/or in the requirements. Tekion will take a strong traditional SDET who has built ML fluency, not only someone who has already tested ML systems, and that is a real opening because very few people have five years of ML testing experience. If you are an experienced automation engineer who has been reading about evals and wants a way into AI work without retraining as a data scientist, this is one of the cleaner routes on today's board. The Python preference is worth taking seriously even though Java is allowed, because the ML tooling ecosystem is Python.
Commvault asks for a Bachelor's degree in Computer Science, Cybersecurity, Information Technology or a related field, and 5+ years of experience in application security testing or offensive security. Required: deep understanding of the OWASP Top 10, CWE and SANS Top 25 and other security best practice. Hands on experience testing applications hosted in AWS, Azure or GCP. Familiarity with RESTful APIs, microservices architecture and container security (Docker, Kubernetes). Experience testing GenAI solutions. Strong command of scripting in Python, Bash or PowerShell for custom testing and automation. Solid understanding of secure SDLC and DevSecOps. Experience with security testing tools across three categories: static analysis (Fortify, Checkmarx, Veracode), dynamic analysis (Burp Suite Pro, OWASP ZAP, AppSpider) and software composition analysis (Snyk, Black Duck, WhiteSource). Preferred: security certifications such as OSCP, GWAPT, GPEN, CISSP or CSSLP, infrastructure as code scanning experience (Terraform, CloudFormation), and working knowledge of compliance frameworks such as PCI DSS. Day to day: perform detailed application security testing, lead threat modelling and assessments across the SDLC, use automated tooling to find vulnerabilities, manually validate and prioritise findings, collaborate with DevOps, engineering and cloud teams, provide remediation guidance and validate fixes, conduct secure code review as necessary, stay current on emerging threats, document findings clearly, and mentor junior security staff. Location: Bangalore. ⚠️ Commvault opens this posting with a recruitment fraud warning: it does not conduct interviews by email or text and will never request banking details or national ID before your first day. Apply through the official link only. Honest fit guidance: the tool list is long but the certifications are preferred rather than required, so an OSCP is not a gate. The GenAI testing requirement is the one most candidates will not have, and it is listed as a requirement rather than a preference, so be ready to talk about how you would approach prompt injection and model abuse even if you have not done it professionally.
Okta asks for 7+ years of progressive software development experience with a proven track record designing and building Windows features using C++, C# and the .NET framework. Required depth: deep expertise with Windows software environments including design and performance optimisation and security considerations. Solid understanding of advanced debugging and performance optimisation on Windows, the Win32 API, inter process communication, Windows services and secure credential handling. Experience in fast paced agile environments with a strong understanding of CI/CD and automated testing. Excellent communication, with the ability to explain complex technical concepts to varied audiences and influence technical direction. Proficiency using AI coding assistants such as GitHub Copilot to accelerate development. Strong conceptual understanding of Windows security features in a cross platform context. Nice to have: security domain expertise such as cryptography and endpoint security concepts (Trusted Platform Module, device management and MDM protocols, endpoint detection), and an understanding of identity and access management. What you will do: partner with product management, engineering directors and principal architects to turn business objectives into technical roadmaps. Drive cross functional collaboration with product, design and QA. Lead design and implementation of new features and services from conception to deployment. Act as a force multiplier across teams, mentoring staff and senior engineers and guiding design reviews. Raise the bar through code standards, automated testing and modernised CI/CD. Maintain high quality technical documentation. Location and office: Bengaluru, hybrid. Honest fit guidance: 7+ years for a principal title is on the accessible side, but the Windows systems depth is not negotiable. Win32, IPC and secure credential handling are specialist skills that a general full stack background will not cover. If you have spent years on Windows client software, the title is likely a promotion in name; if you have not, the years figure will not save you.
Everpure asks for 8+ years of experience designing, developing and testing product components, with Python and Go preferred among the languages listed. What you will do: design and develop microservices and integrate new features into Portworx products. Bring focus to design, development, unit and functional testing, code reviews, documentation and continuous integration and deployment. Collaborate with peers and stakeholders to take solutions from initial design through to production. Take full ownership of design and development activity, adapting to customer feedback and handling issues found in unit testing, system testing and customer environments. Product context: Everpure acquired Portworx in October 2020, its largest acquisition at the time, to build what it describes as the industry's most complete Kubernetes data services platform for cloud native applications. The team's stated remit is a secure, consistent experience for customers buying and using the Portworx offerings. Location: Bangalore. Note that Everpure states elsewhere in its postings that it is primarily an in office environment and expects attendance at the Bangalore office in line with company policy, other than PTO, work travel or approved leave. ⚠️ Naming caution, worth knowing if you search for this company. Everpure is the former Pure Storage and its postings still refer to Pure Storage and Pure in places, including on this requisition. It is the same employer. Honest fit guidance: Kubernetes depth is what actually gets tested here, not just Go. Portworx work means operators, custom resource definitions, controllers and CSI, and a candidate who knows Go but has never built against the Kubernetes API will struggle. If you have run stateful workloads on Kubernetes in anger, this is one of the more technically interesting storage roles in today's edition.
Tekion asks for 8 to 11+ years in ML engineering and MLOps, or backend and platform engineering with production ML. The published qualification list is long and specific: Experience with LLMs, retrieval systems, vector stores and graph or knowledge stores. Strong software engineering fundamentals: Python plus one of Java, Go or Scala, API design, concurrency and testing. Hands on with orchestration frameworks and libraries such as LangChain, LlamaIndex, OpenAI function calling and AgentKit. Knowledge of agent architectures (reactive, planning, retrieval augmented) and safe execution patterns. Pipelines and data: Airflow or Kubeflow or similar, Spark or Flink, Kafka or Kinesis, with strong data quality practices. Microservices and runtime: Docker and Kubernetes, service meshes, REST and gRPC, plus performance and reliability engineering. Model ops: experiment tracking, registries such as MLflow, feature stores, A/B and shadow testing, and drift detection. Observability: OpenTelemetry, Prometheus and Grafana, including debugging latency, tail behaviour and memory or CPU hotspots. Cloud: AWS preferred (IAM, ECS and EKS, S3, RDS and DynamoDB, Step Functions and Lambda) with cost optimisation experience. Security and compliance: secrets management, RBAC and ABAC, and PII handling. Location: Bangalore HQ. Honest fit guidance: this is an engineering role with ML in it, not a modelling role. Nothing in the requirement list asks you to design novel architectures or publish; almost all of it is about running models reliably and affordably in production. Data scientists who want to move into engineering will find the operational half unfamiliar. Platform and backend engineers who have shipped ML systems are, by Tekion's own wording, explicitly welcome, since it accepts backend or platform engineering with production ML as an alternative to an ML engineering title.
Fivetran asks for 8+ years in the software industry with a focus on building test automation frameworks, tools and infrastructure at scale. The expectations are written as a staff level scope: defining and driving code quality for tests including review processes, efficiency and maintainability. Writing critical or common code shared across multiple teams. Identifying and designing fixes for critical issues in core parts of the product. Contributing to and enforcing department wide coding standards. Identifying major improvements to product quality and resilience. Finding and fixing performance, scalability and reliability gaps in tests and test frameworks. Defining testing efficiency and reporting strategies. Defining guidelines for product releases including quality gates and readiness criteria. Expert application of design principles to test architecture. Technical requirements: strong knowledge of object oriented programming, preferably Java. Hands on experience with cloud platforms (AWS, GCP or Azure). Experience with CI/CD systems (Buildkite, Jenkins, GitHub Actions, CircleCI), modern build tools (Bazel, Maven, Gradle) and observability platforms (New Relic, Datadog, Prometheus, Grafana). SQL and NoSQL databases such as Postgres and MongoDB. Location and office: Bengaluru, listed as India and APAC on the requisition, hybrid. Benefits named: 100 percent employer paid medical insurance, generous paid time off plus sick time, inclusive parental leave, holidays including a year end global week of rest, volunteer days, RSU stock grants and professional development. ⚠️ Standing check on this employer: Fivetran sometimes ships requisitions carrying internal priority flags such as P3 (Future Open) or P2 (Internal Resources), meaning the role may not be actively funded. We checked this posting explicitly and no such flag is present. Honest fit guidance: the influence half is as large as the engineering half. If you want to write automation code and be left alone, the standards setting and cross team persuasion in this role will chafe.
Everpure asks for 10+ years of proven development experience in cloud architecture across AWS, Azure or GCP. What you will do: lead the design, development and deployment of Portworx's Kubernetes native backup and restore solution, serving as a technical anchor for the team. Design and build cloud native services that operate reliably at scale, with emphasis on performance, quality and efficiency in both design and implementation. Deeply leverage Kubernetes constructs including operators, custom resource definitions, controllers and CSI to build production grade data protection capabilities. Ensure security, resilience, stability and high availability are first class considerations in every design decision. Design robust, well defined APIs that integrate with the frontend and web UI. Drive architectural decisions and technical direction for the product, mentor engineers, and set the engineering quality bar through design and code reviews. Product context: Everpure acquired Portworx in October 2020, its largest acquisition at the time, expanding into multi cloud data services for Kubernetes and containers. Location: Bangalore. Everpure states in its postings that it is primarily an in office environment and expects work from the Bangalore office in line with company policy. ⚠️ Two cautions on this employer. First, Everpure is the former Pure Storage and its postings still say Pure Storage in places, including this one. Second, Everpure publishes some team lead roles under individual contributor sounding titles such as Member of Technical Staff, and we rejected two of those from today's edition for exactly that reason. This posting is the reverse case: the title says Lead but the responsibilities are architecture, mentoring and code review with no people management, so we have published it as an IC role. If that distinction matters to you, confirm it on the first call. Honest fit guidance: the CSI and operator experience is the real gate at this level, not the ten years.
Okta asks for 12+ years in software engineering with a strong emphasis on backend systems design and development, 8+ years in Python preferred, and separately 6+ years with modern front end frameworks such as React, Next.js and TypeScript, including principles of accessibility and the ability to collaborate with product and design. Also required: proven experience building and deploying production grade AI applications and services. A strong background building distributed systems, microservices and resilient APIs (REST and GraphQL) on AWS, GCP or Azure. Demonstrated ability to influence technical strategy and lead architecture decisions across global teams. Excellent communication with experience working across time zones and cultures. Experience with agentic frameworks such as LangChain, LangGraph and LangSmith is called a strong plus rather than a requirement. What you will do: drive architecture and design of AI solutions, leading cross functional initiatives across product, design and data science. Design, build and refine the core backend services powering AI solutions, including LLM orchestration, RAG pipelines and generative AI features. Build high performance agentic experiences for web and mobile engineered for streaming responses and low latency. Champion observability and operational excellence so AI services meet enterprise reliability and performance standards. Enable delivery of key AI projects through technical leadership and hands on execution. Mentor engineers. Location and office: Bengaluru, hybrid, on a cross geo team. Honest fit guidance: this is the highest experience bar in today's edition and the requirement set is genuinely wide. The 6+ years of React alongside 12+ years of backend Python is the part most candidates will fail on, and it is not written as a preference. If your last six years have been purely backend, read that line carefully before investing in the application.
GitLab publishes no years of experience figure anywhere in this posting, which is consistent across its listings, so we have left the experience field blank rather than invent one. What it asks for instead is specific: Significant professional experience with Go and building command line interfaces or systems level tools, including thoughtful command and flag design, clear terminal experiences, scripting friendly output, backwards compatibility and distribution across Linux, macOS and Windows. A sustained history of open source contributions through issues, merge requests and reviews, ideally including project triage or maintainership. Proven ability to operate as a self directed owner who can absorb multiple and frequently changing inputs, re-prioritise with discretion and continue delivering. Strong product and user experience instincts for developer workflows. Experience setting technical direction and influencing work across teams in an individual contributor role. Experience collaborating transparently in a remote, asynchronous environment. Additional experience with TypeScript or JavaScript developer tools, AI powered developer tools or agents, and plugin or extensibility architectures. What you will do: guide the technical direction of glab, owning architecture, implementation and evolution. Design and ship terminal first features and workflows in Go. Absorb changing inputs from product, the open source community and internal teams, re-prioritise and keep shipping. Partner with product management to shape and execute the roadmap. Steer the open source project and community by triaging issues, reviewing and merging contributions and upholding a quality bar. Team: about nine engineers in the Developer Clients group, part of the roughly 20 engineer AI Clients stage, working across the GitLab CLI, GitLab Duo CLI and the JetBrains and VS Code extensions, with a weekly sync. ⚠️ Location: the posting states the role is based in Bangalore. GitLab is an all remote company and its listings often are remote, but this specific requisition names Bangalore, so do not assume remote here. Honest fit guidance: the public open source contribution history is a real gate. GitLab asks for a sustained record, ideally including maintainership, and that is not something you can assemble during a notice period. If you already maintain something, this is a rare seat where that history is the qualification.
Fivetran states no years of experience requirement anywhere in this posting. We have left the experience field blank rather than infer a number from the Staff title, which means this role will not appear under any experience filter on this page. The skills asked for are: Strong experience building and operating production services in Python or Go. Experience with at least one cloud provider (AWS, Azure or GCP) and core primitives including IAM, networking and compute. Experience building developer productivity tooling such as CI systems, build tooling, developer portals and workflow automation. A track record leading ambiguous, cross team technical projects to completion. Strong communication and engineering judgment. You will have an edge with: Kubernetes and platform abstractions, infrastructure as code using Terraform or OpenTofu including reusable modules, safe state practices and modernisation of shared platform foundations, and experience building internal developer platforms or developer portals. What you will do: lead end to end projects that improve developer tooling, environments and operational workflows for speed, reliability and safety. Design and operate internal tooling and services in Python or Go. Build tooling for the internal developer platform covering self service workflows, shared patterns and developer facing interfaces. Help develop AI based workflows for productivity and efficiency, including automation that improves infrastructure operations such as faster triage and automated runbook steps. Location and office: Bengaluru, listed as India and APAC, hybrid. Benefits named: 100 percent employer paid medical insurance, generous paid time off plus sick time, inclusive parental leave, holidays including a year end global week of rest, volunteer days, RSU stock grants and professional development. ⚠️ Standing check: Fivetran sometimes ships requisitions with internal priority flags such as P3 (Future Open). We checked this posting and no flag is present. Honest fit guidance: with no years figure published, the gate is the portfolio. If you have built an internal developer platform that people actually adopted, say so early, because adoption is the outcome this team is measured on.
Everpure publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess a number from the Member of Technical Staff title. The requirements are stated as capabilities instead. What you will do: design and deliver automated validation suites that stress test PCIe, NVMe and OCP compliance, ensuring firmware maturity and hardware robustness for the Everpure platform. Drive technical root cause analysis for complex failures across firmware and system layers, using telemetry and logs to resolve performance or data integrity bottlenecks. Own and scale the regression infrastructure, improving test repeatability and coverage to accelerate the qualification cycle for next generation NAND technologies. Collaborate with cross functional engineering teams to provide clear risk assessments and quality metrics that directly influence product readiness and release timelines. Develop custom validation tools and scripts in Python to automate characterisation of drive level behaviour under power loss, snapshot and high volume scenarios. What you bring: deep technical expertise in storage validation, with proficiency across the areas above. Location: Bangalore. Everpure states in its postings that it is primarily an in office environment and expects attendance at the Bangalore office in line with company policy, other than PTO, work travel or approved leave. ⚠️ Two cautions on this employer. Everpure is the former Pure Storage and its postings still refer to Pure Storage in places. Separately, Everpure sometimes publishes team lead roles under this same Member of Technical Staff title, and we rejected two such roles from today's edition. This posting describes an individual contributor: it opens by calling the role a key contributor and names no reports. Read the role summary line rather than the title at this employer. Honest fit guidance: this is a genuinely specialist seat. PCIe, NVMe and OCP compliance work does not transfer easily from general software testing, and Python automation alone will not carry an application. If you have worked on storage, firmware or hardware validation, the competition here is much thinner than for a generic backend role.
Everpure publishes no years of experience figure on this posting, so we have left the experience field blank rather than infer one from the title. The stated requirements: Strong skills using Linux command line environments alongside Python, Go or C and C++ to build automated triage and analysis tooling. Exceptional communication with a proven ability to translate complex log evidence, metrics and test outputs into high quality bug reports and cross team alignment. A continuous improvement mindset, using large scale test environments and CI/CD pipelines to share system level validation best practice. What you will do: lead root cause investigations as a core member of the Everpure Forensics team, maximising reliability and performance of the flagship storage platforms at hyperscale. Look beyond surface level symptoms to solve complex technical puzzles where firmware intersects the broader storage stack. Collaborate with cross functional engineering, hardware and platform teams to turn critical escalations into systemic engineering improvements. ⚠️ Location, stated explicitly in this posting: Everpure is primarily an in office environment and you will be expected to work from the Bangalore office in compliance with company policy, other than PTO, work travel or other approved leave. Everpure is one of the few employers in today's edition that states its office expectation in writing rather than leaving it to be discovered. ⚠️ Naming: Everpure is the former Pure Storage and its postings still refer to Pure Storage in places. Same employer. Honest fit guidance: debugging is the job, not a phase of it. Some engineers find deep root cause work across firmware and storage the most satisfying thing available, and others find the absence of feature building draining. Be honest with yourself about which you are before applying, because the posting is honest about which this is. Note also that this employer publishes team lead roles under the same Member of Technical Staff title; this one is an individual contributor seat, described as a core member rather than a lead.
Thoughtworks publishes no years of experience figure on this posting. Note that its opening line, "For 30+ years, our clients have trusted our autonomous teams", is the age of the company and not an experience requirement, a trap worth knowing because automated parsers read it as one. We have left the experience field blank rather than publish a wrong number. Technical qualifications as stated: experience writing clean, maintainable and testable code with attention to refactoring and readability. Proficiency in scripting languages such as Python or shell for automation. Knowledge of distributed systems and scalable architectures for large scale ML applications. Experience building, deploying and maintaining ML systems using relevant techniques and platforms including Scikit-learn, TensorFlow, MLflow, Kubeflow and PyTorch. Experience applying MLOps principles and CI/CD to machine learning. Experience in machine learning engineering and data science, familiarity with key ML concepts, algorithms and frameworks, and an understanding of model lifecycles. Experience designing and operating the infrastructure required to run different types of ML training and serving workloads, covering on premises versus cloud infrastructure, infrastructure as code and monitoring. What you will do: contribute to design and drive development of robust, scalable ML systems, and enable credible, collaborative problem solving to execute on a strategy. Location: Bangalore. ⚠️ Remote flag caution. This posting carries a #LI-Remote tag. Thoughtworks postings have previously carried that tag alongside metadata saying remote eligible is false and an office expectation, so we have published this as a Bangalore role rather than a remote one. If remote matters to you, confirm it directly before you invest in the process. Do not treat the tag as an answer. Honest fit guidance: consultancy ML work means changing client contexts, varied maturity levels and sometimes inheriting other people's systems. That breadth is genuinely valuable early and mid career and suits people who like new problems. If you want to own one model in production for years and tune it deeply, a product company is the better home.
Sarvam publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess. It asks for capabilities and evidence instead: Deep understanding of vision language models covering training dynamics, architecture tradeoffs and failure modes. A track record of good research, demonstrated through publications, technical reports or impactful shipped work. Rigorous experimental design, specifically the ability to isolate variables and draw defensible conclusions. Strong PyTorch skills, with the ability to run experiments end to end. Intellectual range, meaning a willingness to work across data, training and evaluation problems. Bonus points: a PhD or Master's with relevant research experience in ML, computer vision, NLP or a related field. Research papers published at A or A star venues. Experience with multilingual or low resource language modelling. Familiarity with document understanding, OCR or structured visual prediction. Experience with large scale data curation and its effect on model quality. What you will do: work across the full lifecycle of vision language model development, from data through training and evaluation to production. Research vision language architectures including encoders and their tradeoffs. Location: Bengaluru. Honest fit guidance: note that the advanced degree and the publications sit under bonus points, not requirements, and "impactful shipped work" is offered as an alternative to papers. That is a deliberately wider door than most research postings, and it means a strong engineer with real model training experience and no PhD should not self reject. What is not optional is the PyTorch depth and the experimental rigour: Sarvam wants someone who designs an experiment properly rather than someone who runs training scripts. If your ML work has been fine tuning with off the shelf recipes, this is a step up rather than a lateral move.
Databricks states the ideal experience three ways, and any of them qualifies: 2+ years as a Deployment Strategist, or 2+ years at a high growth startup in a builder or founder capacity, or alternatively 5+ years in a senior client facing product or delivery role at a top tier technology company or consultancy. We have recorded the bar as 2+ years because that is the floor the posting sets. Also required: demonstrated experience in value based scoping (total cost of ownership and return on investment), managing agile software projects and writing PRDs. Strong communication skills, described as opinionated and humble, able to build rapport and drive decisions in days rather than weeks. A product and systems thinking mindset, able to perform a SWOT analysis and understand a competitive landscape. Relentless execution with a hands on mentality, expert at escalation. What you will do: partner with Account Executives to build C-suite trust, perform deep discovery to map the customer's political and technical landscape, scope the value, define the minimum viable product for a pilot, write the PRD that guides the engineering team, and manage delivery. ⚠️ Two things to weigh carefully. First, location is listed as Remote, India, which makes this one of very few genuinely remote roles on today's board. Second, and directly against that, the posting requires the ability and interest to travel up to 50 percent. Remote here means no fixed office, not staying at home. If relocation is your constraint this role helps; if travel is the constraint it does not. Honest fit guidance: this is not an engineering role and we have grouped it with the customer facing listings for that reason. There is no coding requirement anywhere in the posting. What it wants is someone who can sit with a large enterprise, work out what is worth building, write it down precisely and push it through. The founder or early startup route in is genuine and rare, so if you have built something from nothing for two years without a conventional title, this posting was written with you in mind.
Zenoti asks for 2 to 5 years of experience implementing software systems, with hands on experience in data transformation, system validation and migration tasks. Required skills: deep knowledge of features in Microsoft Excel, with working knowledge of database systems a plus. The ability to use tools and scripts to transform data for setting up customer sites. The ability to innovate and develop tools to enhance the migration process. Experience with data migrations and data mapping. The ability to adhere to and develop quality checks that demonstrate the integrity of data migration from legacy systems into Zenoti. A technology centric background. Strong logical, analytical and problem solving skills. Excellent communication skills. The ability to work in a fast paced environment across multiple projects. Knowledge of web design using HTML is listed as good to have. What you will do: solution and configure Zenoti to meet each customer's business processes, work with customers to define requirements, and manage customer expectations through the implementation. Location: Hyderabad, Telangana. Honest fit guidance: be clear that this is a consulting and configuration role, not a software engineering one. You will write scripts and transform data, and the posting genuinely rewards people who automate rather than click, but you are not building the product. That makes it a good fit for someone with a technical background who likes customer contact and project variety, and a poor fit for someone who wants to grow as a developer, because the code you write is throwaway migration tooling rather than shipped software. The Excel requirement is not a joke and appears above the database line, which tells you something about the day to day. At 2 to 5 years with a genuine technology requirement, it is a real door into a product company for people whose first job was support or operations.
ElevenLabs asks for 3+ years of experience working with customers in a technical capacity, with direct enterprise customer experience preferred. Also required: experience in product development, delivery and change management. Commercial instinct, described as comfort engaging in deal conversations, structuring value propositions and navigating enterprise sales cycles alongside go to market partners. Basic proficiency in Python and familiarity with API integration, sufficient to prototype, demo and communicate credibly with engineering teams. Excellent communication and problem solving, particularly the ability to simplify complex technical concepts. A proven track record taking ownership of complex, ambiguous projects and delivering results. Adaptability across different customer environments, industries and technical use cases. Technical aptitude and familiarity with common LLM tooling and AI agent frameworks. The ability to creatively map enterprise use cases and workflows to AI systems. ⚠️ Location, read carefully. The posting states this role is remote and can be executed globally, and adds that if you prefer you can work from the ElevenLabs offices in Bangalore, Dublin, London, New York, San Francisco, Tokyo and Warsaw. The requisition is titled for India and Bangalore is among the offices, so India is clearly in scope, but the remote wording is global boilerplate rather than an India specific commitment. Confirm your own eligibility and expected hours before assuming. Benefits named in the posting: an annual discretionary stipend for learning and development, an annual discretionary stipend for social travel to meet colleagues, and an annual company offsite. Honest fit guidance: the commercial instinct requirement is the one to weigh. This is not a role where you can stay purely technical, because deal conversations are named in the requirements list. If you are an engineer who wants customer contact but not commercial exposure, look at the support and solutions architecture roles in this group instead. If you like being the person who can talk to both the buyer and the engineers, the Python bar here is genuinely basic and the door is wider than most AI company postings.
Druva states experience as 3 to 6 years, and separately asks in the same requirement list for a Bachelor's degree preferably in a technical field and 4+ years of relevant work experience or an equivalent combination of training and experience. Those two figures do not quite agree, which is worth knowing before you rule yourself out at the low end. We have published the stated 3 to 6 year band. Required knowledge: excellent written and verbal communication with prior experience communicating with enterprise, service provider or SMB customers. Good understanding of backup and recovery concepts including backup types and replication. Administrative experience in Windows, Linux, Unix and Solaris. Knowledge and understanding of AWS cloud infrastructure. Administration and maintenance knowledge of Microsoft 365, Entra ID, Dynamics 365, PowerApps, Google Workspace and Salesforce. Working knowledge of Active Directory and APIs. Proficiency troubleshooting a wide variety of applications using standard tools including Wireshark, tcpdump, procmon, perfmon and OpenSSL. Fundamental knowledge of storage technologies (tape devices, SCSI, SAN, iSCSI, NAS) and networking concepts (routers, firewalls, proxies). System integration and identity and access management knowledge including LDAP. Location: Pune, Maharashtra. Honest fit guidance: the title says Associate but the requirement list does not read like an entry level job, and that gap is the single most useful thing to know here. This is a broad infrastructure knowledge test more than a years test, so a candidate at three years who has genuinely administered Windows and Linux, touched AWS and debugged with Wireshark is a better fit than someone at six years who has only worked one product. Customer support at an enterprise backup vendor also means escalations under pressure when a customer cannot recover their data, which is a specific kind of stress worth being honest with yourself about. In return you learn a very wide surface quickly, and it is a well known route into cloud and storage engineering.
Hevo Data asks for 5 to 8 years in sales engineering, solutions engineering, pre sales or solution architecture within B2B SaaS, plus strong experience handling technical discovery conversations for global customers. Required understanding: SQL and NoSQL databases, REST APIs and integrations, data architectures and system design, and cloud and SaaS ecosystems. Excellent communication and stakeholder management. Hevo marks strong database expertise with excellent technical problem solving as a must have. Ideal but not required: experience with ETL and ELT, data warehouses or analytics platforms, and exposure to Snowflake, BigQuery, Redshift or Databricks. What you will do: drive the technical side of the sales cycle for US mid market and enterprise customers, partner with account executives to lead technical discoveries, understand customer architectures, uncover integration challenges and influence technical decision making. Collaborate with product and engineering to relay customer feedback. ⚠️ Working hours and location, stated in the requirements: comfortable working US hours from the Bengaluru or Pune office. This is a night shift in practice and it is a requirement, not a preference. Weigh it before applying. ⚠️ This is a commercially measured role and we have grouped it with the customer facing listings rather than the engineering ones for that reason. Hevo describes itself as entering hyper growth with ambitious revenue targets. Most pre sales roles carry a number even when the posting does not say so, so assume this one does. Honest fit guidance: Hevo's flexibility on ETL background is the genuinely useful detail here. It states that deep database expertise with strong solutioning can substitute for data pipeline specific experience, which opens the role to database engineers, solution architects and support engineers who have never worked at a data infrastructure vendor. If you can run a discovery conversation and reason about someone else's architecture out loud, the domain knowledge is learnable and Hevo says as much.
Databricks asks for 8+ years in a data engineering, data science, technical architecture or similar pre sales or consulting role, and separately 8+ years of experience with big data technologies including Apache Spark, AI, data science, data engineering, Hadoop and Cassandra. Also required: strong consulting and customer facing experience working with external clients across a variety of industry markets. Coding experience in Python, R, Java, Apache Spark or Scala. Experience building distributed data systems. Experience building solutions with public cloud providers such as AWS. What you will do: work with sophisticated data engineering and data science teams to help them achieve data driven outcomes on the Databricks platform, integrating it into their enterprise ecosystem. Act as technical advisor internally to the sales team and work with the product team as an advocate for your customers in the field. Become an expert in, promote and recruit contributors for Databricks inspired open source projects (Spark, Delta Lake, MLflow) across the developer community. Location: Bengaluru. ⚠️ Commercial framing, stated plainly so you can judge it. The posting says you will work directly with the sales team to develop your book of business, define account strategies and execute them. We publish technically demanding customer facing roles and reject ones that are sales jobs with a technical title, and this one clears that line on the strength of its 8+ years of hands on data engineering and coding requirements. But the book of business language is in the posting and you should read it as meaning your work will be measured commercially as well as technically. Honest fit guidance: this is one of the more technically credible pre sales roles you will see, and the open source advocacy element makes it a genuinely good platform for building a public profile in the data community. It suits a senior data engineer who has realised they enjoy the customer conversations more than the pipeline maintenance. It does not suit someone looking to avoid commercial pressure, and it does not suit someone who wants to keep building product.
MongoDB asks for 10+ years of experience in customer and market facing roles at the principal or Field CTO level. Required: a recognised technical leader with deep hands on experience with enterprise scale applications. Demonstrated success in scaling technical influence and earned credibility, with experience speaking at major technology conferences, hosting technical webinars, or contributing deeply to the developer community through technical blogs, open source contributions or whitepapers described as highly desired. A deep portfolio and history of published content, presentations at events, and interviews or quotes in the press and media. Executive presence, meaning the ability to command a room with credibility, deliver compelling keynote presentations and influence at senior level. What you will do: work closely with account teams to engage C-suite executives and senior technical leaders at MongoDB's most strategic customers. Bridge complex data architectures and AI to power business transformation, positioning MongoDB as the platform for modernising legacy systems and building next generation AI applications. Shape industry perspectives as a recognised technical thought leader. ⚠️ Location: the posting states plainly that this role can be based remotely in India. That is an explicit statement in the body rather than a tag on the listing, which is why we count it as genuinely remote. It is one of only two such roles in today's edition. Honest fit guidance: the public profile requirement is the real gate and it cannot be assembled quickly. If you have never spoken at a conference or published technical writing, the 10 years alone will not carry an application, because MongoDB has listed the portfolio as a qualification rather than a preference. Equally, if you are a well known engineer in the Indian data community who has been wondering what the commercial route looks like without moving into people management, this is that route: it is an individual contributor seat with no reports named anywhere in the posting.
ClickHouse publishes no years of experience requirement anywhere in this posting, so we have left the experience field blank rather than infer one. That means this row will not appear under any experience band filter on this page. What it asks for instead: Strong technical and communication skills, capable of bridging business objectives with technical solutions, and the ability to serve as a trusted advisor guiding clients on how to use ClickHouse for real time analytics, cloud native applications and enterprise scale workloads. What you will be doing: translate complex business and technical requirements into scalable solution designs, covering architecture, migrations, workflows and data visualisation. Work directly with stakeholders across every level, from the C-suite to data scientists and developers, to enable customer success. Evangelise ClickHouse's vision and capabilities, driving adoption and securing strategic commitments. Apply a solution based approach to demonstrate and deliver customer value. Lead new initiatives as the India presence grows. Location: Bangalore. Company context worth knowing, as stated in the posting: recognised on the 2025 Forbes Cloud 100, more than 4,000 customers, annual recurring revenue growth over 250 percent year on year, and a $400M Series D financing round. It names Capital One, Lovable, Decagon, Polymarket and Airwallex among customers that recently adopted or expanded deployments. Honest fit guidance: with no years figure published, the assessment will rest on what you can demonstrate rather than what your CV says, which cuts both ways. Someone with genuine analytics database depth and customer facing experience should apply regardless of the number of years they have, because there is no stated bar to fall short of. Note that this is an early India seat at a company scaling quickly, described as leading new initiatives, so expect ambiguity and breadth rather than a defined patch. Familiarity with ClickHouse itself is not stated as a requirement, but competing on this without it would be difficult given the open source community around the product.
Temporal publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess one from the Staff title. The stated requirements are capability based: Reside within Bangalore, India. This is listed as the first requirement, not a preference. Exceptional technical communication skills including presenting, whiteboarding and writing. Deep understanding of distributed system technologies, design principles and best practices. Proficiency building application prototypes and providing design, development, build and deployment guidance using one or more of Temporal's supported languages: Java, Go, TypeScript, Python, C# or PHP. A firm grasp of operational considerations in production environments such as security, reliability, performance, cost management and operations. The ability to give insightful advice on architectural topics including application patterns and platform architectures. Experience with at least one major cloud provider. What you will do: collaborate with prospects to determine whether their applications fit Temporal's platform well. Educate customers and prospects on the technical benefits and limitations of the platform and cloud service. Position Temporal as a leading solution against competing technologies and architectural patterns. Foster an environment within customer engineering organisations to increase adoption and expansion of Temporal in production. Partner closely with account executives to develop and execute account plans. Manage and nurture technical relationships. Location: Bengaluru, Karnataka, with residence in Bangalore required. Honest fit guidance: the banking specialisation in the title matters. Financial services buyers ask about correctness, audit and failure semantics in ways other industries do not, so distributed systems depth is genuinely load bearing here rather than decorative. This is a strong fit for a senior backend or platform engineer who has run into workflow orchestration problems personally and can therefore speak about them with conviction. It is a weak fit for a generalist pre sales professional, because the prototype building requirement means you will be writing code in front of customers.
Cursor publishes no years of experience figure on this posting, so we have left the experience field blank rather than infer one. That means this row appears in no experience band filter on this page. What you will do: partner with account executives to lead technical discovery, demos and proof of concept engagements. Build trusted relationships with engineering leaders, architects and developers, serving as their technical advisor. Translate customer requirements into solution designs, guiding them on best practices for rollout, prompt strategy and context configuration. Develop and deliver technical presentations, whiteboard sessions and hands on workshops tailored to customer needs. Act as the customer's technical advocate internally, influencing roadmap priorities and escalating feedback to product and engineering. Collaborate with post sales teams to ensure smooth handoff. The posting describes this as a highly customer facing role combining deep technical fluency with strong communication skills, working hand in hand with sales, product and engineering to scope solutions and demonstrate capabilities. Location: India. Note on the employer name: the posting refers to Anysphere, which is the company that builds Cursor. Same employer. Honest fit guidance: this is a pre sales role and we have grouped it with the customer facing listings accordingly. The difference between this and Cursor's Solutions Architect role, also in today's edition, is the stage: Field Engineer works with prospective customers before they buy, Solutions Architect is embedded post sale in strategic accounts. If you are choosing between them, that is the distinction to weigh, and the Field Engineer role is the more commercially exposed of the two. You should be a working engineer or recent one, because the audience is engineering leaders and architects who will know immediately whether you have shipped code. With no published years bar, evidence of that carries the application.
Cursor publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess. The requirements are stated as background rather than duration. You may be a fit if: you have a strong technical background in software engineering, infrastructure, DevOps, platform engineering or developer tooling. You have experience in customer facing technical roles such as Solution Architect, Solutions Engineer, Forward Deployed Engineer, Technical Account Manager, Enterprise Architect or similar. You have the ability to work hands on with engineering teams while also operating strategically with technical leadership. You have a strong understanding of developer workflows, SDLC tooling, integrations, CI/CD systems, governance and enterprise requirements. What you will do: work directly with engineering teams inside strategic enterprise accounts to roll out high impact workflows and accelerate adoption. Help organisations move from initial excitement to deeply integrating AI into how they build software. Help shape new capabilities through lighthouse customers and design partnerships. Turn successful customer workflows into reusable playbooks and reference patterns. Location: India. Note on the employer name: the posting refers to Anysphere, the company that builds Cursor. Same employer. Honest fit guidance: the explicit list of accepted backgrounds is the most useful line in this posting. Technical Account Manager and Forward Deployed Engineer are named directly, which is worth knowing if you have one of those titles and have been unsure whether solutions architecture roles are open to you. This is the post sale seat, so it is less commercially exposed than the Field Engineer role Cursor also has open today, and more about long horizon adoption inside accounts that have already bought. If you like seeing a rollout through rather than winning the deal, this is the better of the two. Expect the work to be genuinely undefined: nobody yet knows what AI native development looks like at enterprise scale, which is precisely the job.
Zscaler publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess one. That means this row appears in no experience band filter on this page. Role expectations as published: drive opportunity acceleration in GSI partner led large sales scenarios, providing technical expertise to expand account sales engineer efforts and highlight the potential of the Zscaler Zero Trust Exchange. Lead strategic enablement by collaborating with GSI sales engineers to develop their technical capabilities, so they can independently deliver high quality demonstrations, architecture workshops and proofs of value. Elevate industry visibility as a technical thought leader through reference architectures, whitepapers, blogs and public speaking. Provide technical advisory support, education and mentorship to the global partner engineering team, explicitly without direct people management responsibilities. Zscaler's stated success profile: acting like an owner, navigating between high level strategy and hands on execution. Being a high trust collaborator who gives candid, respectful feedback. Approaching complex challenges with constructive energy. Operating with urgency and a focus on execution. Being driven by innovation and technical curiosity, constantly seeking more secure and scalable approaches. Zscaler also states across its postings that it expects candidates to actively use AI tooling to amplify their impact. Location: Bangalore. Honest fit guidance: the without direct people management line is genuinely useful and worth reading twice. Senior customer facing titles routinely hide a reporting line, and candidates who want to stay individual contributors have no way to tell from the outside. Zscaler has said it in writing here. What you should weigh instead is that this is a partner facing rather than customer facing seat: your audience is other engineers at integrators like the large consultancies, and success looks like their competence rather than your own delivery. That is a genuinely different satisfaction model, and enablement work suits people who enjoy teaching. If you want to architect for end customers directly, a straight solutions architect seat fits better.
Commvault asks for a Bachelor's degree and 4 or more years of software development experience. Note the phrasing: the posting writes it as "4 or more years" rather than "4+ years", which is the kind of wording automated parsers miss entirely. Read by hand, the bar is 4 years. Required: strong experience in C++, C#, object oriented design and .NET. Good knowledge of operating systems (Windows and Linux), multithreading and concurrency, data structures and algorithms, networking concepts and distributed systems. Experience with debugging and performance optimisation. Strong analytical and problem solving abilities. Excellent communication. Ability to work in Agile development environments. Security and SaaS experience strongly preferred. What you will do: design, develop and maintain core server side components. Build scalable, high performance enterprise software. Participate in architecture discussions and technical design reviews. Write clean, maintainable, well tested code. Debug complex production issues and improve system performance. Collaborate with globally distributed engineering teams. Locations: Bangalore, Hyderabad and Pune are all listed on this requisition, which gives more geographic choice than almost anything else in today's edition. Benefits named: employee stock purchase plan, continuous professional development and product training with career pathing, annual health check ups, car lease programme, tuition reimbursement, personal accident cover, term life cover and internal Community Guilds. ⚠️ Commvault opens this posting with a recruitment fraud warning: it does not conduct interviews by email or text and will never ask for banking details or national ID before your first day. Apply only through the official link. Honest fit guidance: the C++ and C# combination with real operating system and concurrency depth is a narrower profile than the 4 year bar suggests, and it is the requirement that will decide the interview. Backup and recovery is not a fashionable domain, but the engineering is genuinely hard and the systems are long lived, which tends to make for good technical mentorship.
Zenoti asks for 3 to 8 years of experience in implementation and support of enterprise products. That is a deliberately wide band and suggests the level is set after assessment rather than by the number itself. What you will be doing: work with customers to define requirements and help them adopt Zenoti solutions to streamline operations and increase revenue. Drive demos, walk throughs and solution reviews with customers. Solution, design and set up proof of concepts and pilots for high priority and large customers, ensuring successful implementations. Configure Zenoti to meet customer business scenarios. Identify risks based on current product capabilities, and define and implement mitigation plans. Address customer issues and concerns in a timely fashion. Stay current with product knowledge, business flow, sales process and market dynamics. ⚠️ Working hours, stated in the posting: this is a customer facing role and you will need to align your working hours to overlap the customer timezone in order to build relationships and provide timely service. Zenoti's customers are largely international, so treat this as a shift commitment rather than a formality. Location: Hyderabad, Telangana. Honest fit guidance: this is consulting and configuration work rather than software engineering, and we have grouped it with the customer facing roles for that reason. The difference from Zenoti's more junior implementation seat, also in today's edition, is real: this one leads solution design and pilots for the largest accounts, where the junior one is weighted towards data transformation and migration. If your strength is scripting and data work, the other posting fits better. If your strength is running a room, scoping what is achievable and being straight with a customer about what the product cannot do yet, this is the one. Note that risk identification is written into the responsibilities, which means the company expects you to say no to customers sometimes, and that is a healthier implementation culture than it sounds.
Read this before you apply
- The two entry level roles are not the same kind of job, and the difference matters. Meesho's is core data platform engineering, so the Kafka, Spark and Flink experience it asks for is the real gate even though the years are low. Zscaler's is internal engineering tooling: you build custom Jira apps and integrations for Zscaler's own teams, not the security product. It is genuine Java and Groovy development with an AWS platform migration attached, and it is the only posting here that says internships count, but go in knowing which product you are working on.
- Remote is 3 of 43 and none of them are engineering roles. We read every one out of the posting body. Databricks' Deployment Strategist is listed Remote India and is the lowest bar of the three at 2 years, but the same posting requires travel up to 50 percent, so remote means no fixed desk rather than staying home. MongoDB's Principal Technologist states in writing that it can be based remotely in India, at 10+ years. ElevenLabs says the role is remote and can be executed globally, which is boilerplate rather than an India commitment. There is no remote backend role today and we would rather say that than stretch one of these to fill the gap.
- Eleven roles publish no years figure at all , so they sit in no experience band on the page and will not show up if you filter. GitLab, Fivetran, Everpure, Thoughtworks, Sarvam and Cursor all do this. We leave the field blank rather than invent a number. Two of them are worth a look regardless: Sarvam's vision language researcher lists the PhD and the published papers under bonus points rather than requirements, and GitLab's glab role weighs your open source history more than any year count.
- Watch Thoughtworks' remote tag. The posting carries a #LI-Remote tag and we have still listed it as Bangalore, because this employer has previously shipped that tag alongside metadata saying remote eligible is false and a five day office expectation. Confirm before you assume. Everpure is the opposite and states its office policy in writing: primarily in office, expected at the Bangalore office other than leave or travel.
- Okta and Tekion are 5 roles each and they are genuinely different teams. Okta spans Auth0 enablement, Auth0 platform infrastructure, Android SDKs, Windows client engineering and AI engineering, at 5, 5 to 8, 5, 7 and 12 years. Tekion spans QA, security, AI platform, ML test and staff ML. Read the team, not the title, because Okta in particular has many near identical Bengaluru titles open at once.
- Two roles have hours attached. Hevo Data's Senior Sales Engineer requires working US hours from the Bengaluru or Pune office, which is a night shift in practice. Zenoti's Senior Implementation Consultant requires aligning your hours to overlap the customer timezone. Both are stated in the postings and both are lifestyle decisions rather than details.
- It is not all Bangalore. MongoDB has two in Gurugram, Zenoti two in Hyderabad, Paytm one in Noida, Druva one in Pune. Commvault lists Bengaluru, Hyderabad and Pune on one requisition and Bengaluru or Pune on another, and Zscaler's senior role lists Mohali alongside Bengaluru, so those four give you an actual choice of city.
- Commvault opens both its postings with a recruitment fraud warning , saying it never interviews by email or text and never asks for banking details or ID documents before your first day. Worth repeating because that scam is aimed squarely at people applying for jobs. Apply through the official link and treat any off channel approach as fake.
We read every posting by hand before it goes on this page. The same write-up goes out to the daily email.