No roles match that combination.
Added August 2, 2026
Requirements as published: - 3+ years of experience. - Systems programming depth in one of C, C++, Python, Go or Java, with a track record of building robust, scalable software. - Practical low level knowledge in at least one of: distributed systems, operating system internals (Linux kernel), database internals, hypervisors, or container orchestration. - Ability to turn complex problems into clean designs while working inside a peer driven engineering team. The actual day to day: - Designing and implementing algorithms and data structures that deliver 99.9999 percent reliability for mission critical enterprise storage. - Owning features end to end, from concept and prototype through to production code. - Root causing deep technical bottlenecks across distributed systems and kernel level software. - Building the integration between FlashArray services and public cloud providers such as AWS, so customers can move traditional and cloud native workloads into a hybrid cloud setup. Location and office reality: - Bengaluru. Everpure states plainly that it is primarily an in office environment and you are expected to work from the Bengaluru office, except when on leave or travelling for work. Treat this as an onsite job, not hybrid. Honest fit guidance: - The 3 year bar is real and it is the lowest Everpure is advertising in India today, so this is the one to look at if you are early in a systems career. - You do not need storage experience specifically. The requirement is low level systems depth, and kernel, database or hypervisor work all count. - If your background is web or application development with no operating system or distributed systems exposure, this will be a hard interview. - Note the company name. Everpure is Pure Storage newly rebranded, so older search results, Glassdoor pages and employee reviews will be under the old name.
Requirements as published: - BS in Computer Science. - 4+ years designing, developing and testing enterprise products. Golang preferred. - Good understanding of microservice architectures and cloud native platforms. - Experience designing and owning microservices that operate and scale in a distributed architecture running to thousands of nodes. - Expert debugging skills, including navigating ambiguous problems at scale in public and private cloud environments. - Experience working with multiple internal and external stakeholders, from product management through to customer beta partners. - Solid computer science fundamentals in data structures, algorithms and software design. - Willingness to work in an open plan office environment, stated explicitly in the posting. The actual day to day: - Designing and building cloud native microservices and adding features to Portworx Enterprise. - Unit and functional testing, code review, documentation, and continuous integration and deployment. - Debugging product and performance issues in large scale clusters, using AI tooling. - Taking designs from first draft to production, then absorbing feedback from system testing and real customer deployments. Location and office reality: - Bengaluru, onsite. The posting carries the #LI-ONSITE tag and Everpure states it is primarily an in office environment. It also asks specifically that you be willing to work in an open office. Honest fit guidance: - Go is preferred rather than mandatory, but the whole Portworx stack is Go, so arriving without it means learning it fast. - Kubernetes knowledge is effectively assumed even though the posting does not spell it out, because Portworx is Kubernetes storage. - The emphasis on debugging at scale is unusually heavy for a 4 year role. Come with real war stories about diagnosing failures in a live cluster.
Requirements as published: - 6+ years of experience in cybersecurity or a related technical field. - 3+ years of hands on experience in incident response and detection. - Ability to design, implement and maintain high fidelity detections, correlation rules, alerts, dashboards and use cases in Splunk and related security platforms. - Working knowledge of frameworks including MITRE ATT and CK and CVE/CVSS, plus attacker tradecraft and risk context. - Python and API skills for building enrichment and automation workflows. The actual day to day: - Building detections across identity, endpoint, network, cloud infrastructure, SaaS, DLP, vulnerability and asset posture data. - Correlating signals from different tools to spot attacker behaviour, misuse and anomalous activity. - Sitting in incident triage, investigation and containment, then feeding the lessons back into detection content. - Tuning noisy alerts down, cutting false positives and raising true positive rates. - Working on logging strategy: event onboarding, normalisation, parsing, correlation, retention and reporting. - Writing playbooks, runbooks and detection documentation for the responders who use them. - Partnering with business units, IT and engineering to map how the business actually works to the telemetry needed to defend it. What the posting says you will help build: - High signal detections for credential misuse, privilege abuse, lateral movement, endpoint compromise, and cloud and SaaS attacks. Location and office reality: - Bangalore, onsite. The posting carries #LI-ONSITE and Everpure states it is primarily an in office environment. Honest fit guidance: - This is a detection engineering role, so a pure SOC analyst background of watching a queue will not be enough on its own. They want the person who writes the rules. - Splunk is the named platform. Experience in another SIEM transfers, but say so directly rather than letting them assume. - The posting explicitly rejects alert volume as a success measure, which is a good sign if you have been stuck in a noisy SOC.
Requirements as published: - 3+ years in a Cloud Operations or DevOps role. - 2+ years using Go, shell scripting and Terraform. - 2+ years as a software developer in a SaaS environment. - Understanding of microservices, cloud infrastructure (AWS, Azure), databases (SQL, NoSQL, key/value), containers (Docker, Kubernetes), web technologies (websockets, HTTP) and networking (SSL, routing, VPN). - Exceptional communication, including technical writing in English. - Knowledge of Datadog or another observability platform is desired rather than required. The actual day to day: - Owning and improving incident response processes with other teams. - Participating in a 24 by 7 on call rotation, which the posting says you handle independently. - Using existing monitoring to find problems and either resolve them or escalate to service teams. - Setting and hitting long term performance, reliability and scalability goals on a platform with an aggressive growth plan. - Automating to reduce toil for yourself and your teammates. Location and office reality: - Bengaluru. Office days are not stated. The posting does say the team works effectively in a remote environment where tasks may be self driven, but the role is listed at the Bengaluru site, so do not read that as a remote job. Honest fit guidance: - The on call rotation is 24 by 7 and it is in the requirements, not the small print. Decide about that before you apply. - At 3 years this is one of the lowest bars on any Senior titled role in this edition, which makes it worth a look even if the word Senior would normally put you off. - Ignore the board metadata showing zero years. It is a placeholder and the real requirement is in the body.
Requirements as published: - 7+ years of software engineering experience, with 3+ years building high scale, cloud native backend systems. - Demonstrated staff level (P4) behaviour: independently owning large tasks end to end, influencing technical decisions across a team, and raising the performance of the engineers around you. - Domain expertise in Privileged Access Management, Identity and Access Management, or deep networking infrastructure. Familiarity with credential management, asset discovery or agentless communication patterns. - Strong hands on Go, or deep expertise in C++, Rust or Java with a proven record of picking up Go quickly. - Hands on experience with networking protocols (SSH, Telnet, TCP/IP), database security, microservices and asynchronous event driven systems. - Familiarity with AWS, Kubernetes, Docker, CI/CD automation and modern telemetry and observability tooling. - What the posting calls a multiplier mindset: high empathy and humility. The actual day to day: - Building secure database and network device connectors, covering routers, switches and firewalls, on the Zero Standing Privileges platform. - Hands on architecture and high velocity coding, with end to end execution. - Acting as a technical multiplier for mid level developers in the pod, working with the local technical team lead. - Keeping architecture aligned with the global team. Location and office reality: - Bengaluru. Office days are not stated in the posting. Honest fit guidance: - This is explicitly an individual contributor role, and the posting says so, so the team lead sits beside you rather than being a path you have to take. - The pod is newly established, which means more influence over how things are built and less existing structure to lean on. - Go is strongly preferred but the posting deliberately leaves the door open for strong C++, Rust or Java engineers. Say directly that you will pick up Go.
Requirements as published: - 8 to 12 years of hands on experience in JavaScript, Node.js, Go and React or Next.js. - Experience designing, building and operating distributed systems in a cloud environment such as AWS or Azure. - Backend: strong service design in Node.js (stated as mandatory) or Go. Deep hands on experience deploying, scaling and operating backend services on AWS, with strong Kubernetes proficiency. - Data and caching: strong experience with PostgreSQL, distributed caching with Redis, and data and deployment pipelines. - Performance and scale: using quantitative analysis of latency and traffic volume to justify design and technology choices. - Strong production experience covering monitoring, debugging and incident response. - Frontend: hands on with modern React and MobX or Redux, plus frontend build tools, module bundlers and package managers. The actual day to day: - Owning technical strategy and architecture for the Auth0 Manage Dashboard and the Auth0 Marketplace. - Designing developer friendly APIs and resilient frameworks across the stack. - Mentoring a team of engineers, framed in the posting as technical mentorship rather than people management. - Leading the technical lifecycle of product areas end to end. Location and office reality: - Bengaluru. Office days are not stated in the posting. Honest fit guidance: - Node.js is called mandatory. If your backend is Java or Python only, this is a real gap rather than a nice to have. - The role is genuinely full stack. Both halves are examined, so a strong frontend with a thin backend will not clear the bar, or the reverse. - Marketplace work means designing for third party developers, which is a different discipline from internal APIs. Bring examples if you have them.
Requirements as published: - 3+ years in Site Reliability Engineering or similar roles supporting production environments. - Expertise in infrastructure as code tools: Pulumi, Terraform, CloudFormation or equivalent. - Deep familiarity with observability tools such as Datadog and Sentry, and incident response practice using PagerDuty or Incident.io. - Proficiency with cloud infrastructure platforms including Azure, GCP or AWS. - Strong programming skills in Python, Bash, Go or a similar language. - A track record of diagnosing complex system problems and shipping durable fixes. - Solid understanding of CI/CD, Kubernetes, containerisation, networking, databases and cloud security principles. - Work eligibility: the posting states you must be authorised to work in India and that visa sponsorship is not available. The actual day to day: - Designing, implementing and managing monitoring, alerting and infrastructure resources. - Keeping a platform that spans more than 50 regions fast, secure and available. - Automating mission critical operations to reduce complexity as the company scales. - Working at the boundary between infrastructure and product. Location and office reality: - Bengaluru. Harvey's own job board marks this posting as remote, but the role sits with the Bengaluru team and two sibling postings on the same board state directly that the role is based in Bengaluru. We have published it at the real location. Confirm the working model in your first call. Honest fit guidance: - At 3 years this is the most accessible role on Harvey's India board, and SRE at a company scaling this fast is unusually good experience. - Azure is the preferred cloud, which is less common than AWS, so say clearly if your background is AWS and you are willing to switch. - The India work authorisation requirement is explicit, so there is no sponsorship route here.
Requirements as published: - 5+ years of backend engineering experience building and operating production web applications or SaaS products. The actual day to day: - Designing and owning backend services and APIs that power Harvey's web applications, workflows and integrations. - Modelling and managing data in Postgres and related stores to support low latency, reliable experiences. - Building secure, multi tenant, permissions aware systems with auditing appropriate to enterprise and government customers. - Implementing backend features and workflows that use LLMs and agentic tools, orchestrating calls to Harvey's AI systems from robust services. - Working with frontend, product and design partners to shape solutions and define clear API contracts. - Collaborating closely with product to prioritise customer focused work and deliver reliable features quickly. Location and office reality: - Bengaluru. Harvey's job board marks the posting as remote, but this is a Bengaluru team role and sibling postings on the same board state the role is based in Bengaluru. Published at the real location. Confirm before you assume remote. Honest fit guidance: - You do not need prior LLM experience. The requirement is backend depth, and the AI orchestration is something you learn on the job. - Enterprise and government customers mean multi tenancy, permissions and audit are first class concerns, not afterthoughts. Interviews are likely to go there. - Harvey states its values as decisiveness, simplicity and job's not finished, and describes an intense pace. Take that at face value when deciding.
Requirements as published: - 6+ years in Infrastructure Engineering or Platform Engineering in a production environment. - A long track record building and scaling complex, large scale distributed systems. - Deep proficiency with cloud infrastructure platforms. Azure is preferred, and the posting says GCP or AWS experience transfers well. - Strong fluency in infrastructure as code: Terraform, Pulumi or CloudFormation. - Solid understanding of Kubernetes, container orchestration, networking and cloud security at scale. - Experience with observability tools such as Datadog and Sentry, and incident response practice with PagerDuty or Incident.io. - Strong programming skills in Python, Go or similar. The actual day to day: - Architecting multi region deployment strategies that meet strict data residency requirements for global enterprise customers. - Building observability infrastructure with granular SLA monitoring, burn rate alerts and detailed token attribution for cost tracking. - Leading the evolution of CI and CD pipelines to improve developer velocity while holding production stable. - Balancing new system building against operational excellence on infrastructure processing billions of prompt tokens and millions of daily requests. Location and office reality: - Bengaluru. As with Harvey's other India postings, the board flags remote while the role sits with the Bengaluru team. Published at the real location. Honest fit guidance: - Data residency across regions is a genuinely hard problem and it is named first in the responsibilities. If you have done it, lead with it. - Token attribution for cost tracking is an AI era infrastructure skill that barely existed three years ago. Nobody expects a long history in it, but show you understand why it matters. - Azure preferred again, same as the SRE role. Be explicit if you are coming from AWS.
Requirements as published: - 5 to 8 years of professional experience in software or data engineering, focused on distributed data systems. - Strong programming in Java, Scala or Python, and expertise in SQL. - At least 2 years hands on with big data systems including Apache Kafka, Apache Spark, EMR or Dataproc, Hive, Delta Lake, Presto or Trino, Airflow, and data lineage tools such as DataHub, Marquez or OpenLineage. - Experience implementing and tuning Spark, Delta Lake and Presto at terabyte scale or beyond. - Strong understanding of Apache Spark internals (Catalyst, Tungsten, shuffle) with experience customising or contributing to open source code. - Familiarity with a modern open source and cloud native data stack: Apache Iceberg, Hudi or Delta Lake; Trino, Presto, DuckDB, ClickHouse, Pinot or Druid; Airflow, Dagster or Prefect; dbt, Great Expectations, DataHub or OpenMetadata; Kubernetes, Terraform and Docker. - Strong analytical and debugging skills for complex issues in large scale systems. The actual day to day: - Building and running data infrastructure for a platform handling millions of orders daily. - Working inside a pod aligned to a business theme, contributing to solution design rather than only implementation. - The posting says engineers are expected to challenge existing solutions, not just build to spec. Location and office reality: - Bangalore. Office days are not stated in the posting. Honest fit guidance: - The Spark internals requirement is the real filter. Many candidates have used Spark; far fewer can talk about Catalyst and shuffle behaviour credibly. - Meesho describes a culture that values speed over perfection and logical debate over authority. That suits some people and not others, and it is worth taking literally. - The scale numbers in the posting are unusually concrete for an Indian ecommerce role, which makes this a good one for a CV if you want volume experience.
Requirements as published: - Bachelor's or Master's degree in computer science or a similar field. - 4 to 7 years of experience as a Data Scientist in a fast paced organisation, preferably business to consumer. - Familiarity with neural networks and machine learning. - Familiarity with tools such as SQL, R and Python. - Strong understanding of statistics and linear algebra. - Strong understanding of hypothesis and model testing, including the ability to identify common model testing errors. - Experience designing and running A and B tests and drawing insight from them. - Proficiency in machine learning algorithms. - Strong analytical skills for sourcing data reliably. Nice to have, as listed: - Experience with personalisation or similar machine learning problems. - Familiarity with big data stacks such as Apache Spark, Hadoop and Redshift. - Experience working in tech and product teams. The actual day to day: - Developing models and running experiments to draw insight from data. - Improving product usability and identifying growth opportunities. - Modelling seasonal demand to predict key organisational metrics. - Designing discount programmes to help resellers sell more. - Understanding reseller preferences to surface the most relevant products. - Mentoring junior data scientists on the team. Location and office reality: - Bangalore. Office days are not stated in the posting. Honest fit guidance: - The mentoring line is mentorship, not people management, so this stays on the individual contributor track. - The problems are commercial: pricing, discounting, fraud and demand. If you want research, this is not it. - Business to consumer experience is stated as a preference rather than a requirement, but the whole role is shaped around consumer marketplace behaviour.
Requirements as published: - 15+ years of production level experience in one of Rust, Java, Scala, C++ or a similar language. - 10+ years of experience developing large scale distributed systems. - Deep networking expertise, which the posting names as the core requirement for the role. The actual day to day: - Owning and driving the design of large scale connectivity platforms that form the backbone between the Databricks control plane and compute plane. - Defining technical vision and architecture for next generation network connectivity and observability services managing millions of virtual machines across multiple clouds. - Operating at org wide level: setting technical direction, leading complex cross team initiatives and mentoring senior engineers. - Working with product management, operations and partner engineering to turn long term business goals into durable networking systems. - Improving the scalability, reliability and efficiency of compute infrastructure, and enabling more cost effective use of cloud resources. Location and office reality: - Bengaluru. The posting notes you would be one of the early members of a rapidly growing Bangalore site, which usually means more influence and less established process. Honest fit guidance: - The 15 year figure is real and it is the highest bar in this edition. Do not apply on the basis of the Senior Staff title alone. - The posting asks for both hands on technical leadership and cross team influence, so this is not a role where you can stay purely in the code. - Databricks uses Staff and Senior Staff titles for much more senior work than many companies do. Its Staff roles in earlier editions have asked for 10 to 15 years while other employers use the same word at 5.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the experience field empty rather than guess, which means this role will not appear when you filter the board by years. - The IR specialist: knowledge of Lucene or Elasticsearch, embeddings and ranking algorithms. - The quality and metrics obsessive: experience building evaluation frameworks, both human in the loop and LLM based, and comfort with relevance metrics such as nDCG, MRR and Precision at K. - The bridge builder: willingness to apply traditional information retrieval practice to retrieval augmented generation. The actual day to day: - Owning result quality for two different users: the AI agent that needs ground truth context, and the human who needs an intuitive, high recall search experience. - Hybrid retrieval work, balancing keyword based search for exactness against semantic vector search for intent. - Dual optimisation of ranking models that have to satisfy human readability and LLM ready context at the same time. - Building the guardrails and relevance scoring that keep agent output grounded, because poor search quality shows up as hallucination. - Connecting structured SQL tables, unstructured documents and real time business metrics. Location and office reality: - Bengaluru. Office days are not stated in the posting. Honest fit guidance: - The Senior Staff title at Databricks has historically meant 10 years or more, and its Network Platform posting in this same edition asks for 15. Since no figure is published here, assume the bar is high and read the title in Databricks terms rather than the industry average. - This is a classical information retrieval role wearing an AI badge. The nDCG and MRR requirements are the giveaway. If your search experience is real, that is what counts. - If you filter job boards by years, note that this role has no published figure, which is why it sits outside the experience filter here.
Requirements as published: - 6+ years of experience designing and building complex, high traffic user interfaces. - Experience with unit and end to end testing frameworks. - Bundling and build tools, and CI/CD pipelines for frontend deployments. - A proven record of translating complex requirements into shipped interfaces. The actual day to day: - Leading development of the user facing monetization platform, driving UI architecture and product innovation in the monetization experience. - Building admin interfaces that let sales, finance and support teams manage custom contracts, discounts and user subscriptions without engineering involvement. - Working on billing systems that handle payments and renewals, subscription lifecycle, sales tax and compliance, revenue systems and post purchase onboarding. - Cross functional collaboration, since monetization touches sales, finance and support as well as product. Location and office reality: - Bengaluru, where Postman was founded. ⚠️ The posting states that for roles based in Bangalore, employees currently work in the office three days a week and will transition to five days per week by the end of the year. That is a change worth knowing before you accept, and Postman puts it in writing. Honest fit guidance: - Billing and monetization is unglamorous and technically harder than it looks. Tax, proration and compliance edge cases are where the difficulty lives. - The role is described as leading development, but it is an engineering seat rather than a management one. - The office policy moving from three days to five within the year is the single most important detail here if you have been planning around hybrid.
Requirements as published: - 6+ years of experience with deep backend expertise in search and ETL systems, plus a strong product mindset. - 6+ years building applications in high level programming languages. - Experience across high performance web services, high volume data pipelines, machine learning and relevance tuning. The actual day to day: - Owning end to end architecture and roadmap of the search platform: distributed indexing pipelines, storage infrastructure and high performance web servers. - Leading core initiatives on the search platform rather than implementing a defined spec. - Mentoring engineers on the team and upholding quality through code review. - Improving discovery and ease of consumption over a fast growing volume of user created API data. Location and office reality: - Bengaluru. ⚠️ Same office policy as Postman's other Bangalore roles: three days a week in the office currently, moving to five days per week by the end of the year, stated in the posting. Honest fit guidance: - Search and ETL are named together for a reason. The indexing pipeline is as much of the job as query time relevance, so pure query side experience is only half. - The product mindset requirement is genuine. Search quality at Postman is judged by whether developers find the right API, which is a product question as much as a technical one. - Postman runs several senior Bangalore roles at once. This one and the Monetization frontend seat are both in this edition and they are very different jobs, so pick deliberately.
Requirements as published: - 8+ years of progressive experience in technology, with at least 5 years in a hands on senior role such as Site Reliability Engineering, DevOps or Security Engineering. - Ability to design, build, maintain and improve secure, scalable and highly available infrastructure. - Automation as the default approach rather than repeated manual fixes, which the posting calls out directly. The actual day to day: - Engineering secure and resilient infrastructure for a service that has to be available to customers 24 by 7. - Maturing both the security and the reliability posture of the production environment by treating each as a software engineering problem. - Working at the intersection of infrastructure, automation and security to build a platform that is resilient and secure by design. Location and office reality: - Bangalore, hybrid. The hybrid arrangement is stated in the job title itself. Specific office days are not published, so ask. Honest fit guidance: - This role wants both halves. An SRE with no security depth, or a security engineer who has never run production infrastructure, will find one side of the interview hard. - The posting is written as a leadership role in the sense of technical maturity, not people management, so it stays on the individual contributor track. - Smartsheet has a second, similar Bangalore role in this edition on the Corporate Systems side. That one is business systems focused. This one is product production infrastructure, and they are not interchangeable.
Requirements as published: - 7+ years of experience in DevOps or System Engineering roles. - Experience building and scaling CI/CD pipelines, infrastructure automation, monitoring frameworks and deployment processes. - Ability to work across a variety of systems and platforms. The actual day to day: - Building and scaling the CI and CD pipelines behind mission critical integrations across Finance, People, Sales, Legal, IT and Engineering systems. - Infrastructure automation and monitoring frameworks for those integrations. - Deployment process work across a varied estate rather than a single product stack. Location and office reality: - Bangalore. The posting metadata lists the working location as Field, India. Office days are not stated, so ask early. Honest fit guidance: - Be clear eyed that this is internal corporate systems engineering, not product infrastructure. The work is real automation engineering, and it is genuinely broad, but the customers are internal teams. - If you want your next role to be about product scale and customer facing reliability, Smartsheet's DevSecOps seat in this same edition is the closer match. - Breadth across Finance, People, Sales and Legal systems is unusual and it builds a rare kind of integration knowledge, which is valuable if you later move toward platform or internal tooling leadership.
Requirements as published: - At least 10 years of experience in a technology discipline, preferably with 6+ years in the cyber security domain. - Working protocol level understanding of encryption at rest and in motion: TLS and SSL, BCrypt, PKI, SHA1, AES and similar, plus key management principles. - Proven experience collaborating with sales, legal and engineering teams. - Familiarity with assurance frameworks and questionnaires including SIG and CAIQ. - Exceptional communication, critical thinking and a strong bias for ownership and learning. The actual day to day: - Owning all activity aimed at building trust and confidence in Druva's data security, privacy and compliance posture with prospects and customers. - Running Druva's third party risk management programme. - Driving improvement in Druva's internal security culture, specifically phishing simulation and security awareness work. Location and office reality: - Pune. Office days are not stated in the posting. Honest fit guidance: - This is a customer facing security role, so if you want to be heads down building detections or breaking things, look elsewhere. Druva has separate engineering security roles. - The collaboration with sales is named in the requirements, which tells you assurance work here supports deals. That is normal for the discipline, and there is no quota attached. - The encryption depth requested is at protocol level, not conceptual. Expect to be asked how TLS actually works rather than what it is for.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the field empty rather than invent one, so this role does not appear when you filter the board by years. - Strong expertise in Windows and Linux, file systems and operating system level concepts. - Strong engineering fundamentals and deep automation capability. - A genuine interest in quality in distributed, cloud based systems. The actual day to day: - Working with the development team in an Agile environment to understand functional specifications and design requirements. - Independently creating comprehensive feature test plans aligned to development milestones. - Using and extending existing automation frameworks, adding library support for new functionality. - Owning the complete test execution cycle for user stories. - A mix of automated, manual, white box and black box testing. - Creating, maintaining and documenting testbed setups and environments. - Reporting and tracking issues and test cases, and working across teams to hold quality benchmarks through the lifecycle. Location and office reality: - Pune. Office days are not stated in the posting. Honest fit guidance: - The Senior Staff title with no published years is a genuine unknown. Druva's other role in this edition asks for 10 years, so read the title accordingly, but ask about levelling early. - Backup and archival testing is systems testing. File system and operating system knowledge matters more here than web test automation experience. - White box testing is explicitly in the list, so expect to read and reason about product code rather than only exercise it from outside.
Requirements as published: - 6+ years of software engineering experience with a focus on security. - Ability to design, build, implement and maintain scalable automation tools and pipelines for application security, covering static (SAST), dynamic (DAST) and software composition analysis (SCA) scanning. - Familiarity with tooling such as OWASP ZAP, Snyk and WhiteSource. - Familiarity with CI/CD pipelines such as Jenkins, GitHub Actions and GitLab CI, and with infrastructure as code. - Ability to advise other engineers on secure coding and secure development lifecycle practice. The actual day to day: - Building and maintaining the application security automation estate. - Working with developers, security engineers and DevOps teams to fold security automation into CI and CD workflows rather than bolting it on. - Finding opportunities to automate work that is currently manual. - Coaching engineers on secure coding practice. Location and office reality: - Bangalore. The posting metadata states Remote Position: No, so treat this as an onsite or hybrid role and confirm the days. Honest fit guidance: - This is an engineering role that happens to be in security, not an analyst role. The requirement is 6 years of software engineering, and you will be judged on the code you write. - If your appsec experience is running scans and triaging output, the automation and pipeline building here is a step up rather than a sideways move. - Commvault includes a recruitment fraud warning in its postings: it says it does not conduct interviews by email or text and will never ask for banking details or identification documents before your first day. Worth knowing given how common job scams are in this market.
Requirements as published: - Bachelor's degree in Computer Science, Electrical Engineering, another technical degree, or equivalent experience. - 5 to 8 years of experience in technical support or system administration and operations, with a preference for storage, backup or infrastructure experience. - Ability to architect Commvault software solutions against customer requirements. - Comfort with incident management and with meeting contractual delivery obligations. The actual day to day: - Direct interaction with customers and their environments, providing day to day operational management of the customer's Commvault deployment. - Incident, problem and change work on production backup and recovery systems. - Working remotely into enterprise level customer environments and dark sites, which the posting names specifically. - Maintaining awareness of the customer base and making sure delivery meets what was contracted. - Raising improvements to standard operating procedures with team leadership. - Staying current with new releases, updates and changes to the product. Location and office reality: - Bangalore. The posting metadata states Remote Position: No. Note that working remotely into customer systems is part of the job, which is different from the role itself being remote. Honest fit guidance: - This is operations and support rather than product engineering, and it says so honestly. If that is what you want, it is a strong version of it, with enterprise scale and real ownership. - Prior Commvault experience is not stated as mandatory, but backup and storage background clearly is the preferred route in. - Dark sites means air gapped or restricted environments. Expect process discipline and change control to matter as much as technical skill.
Requirements as published: - 8 to 12 years of software engineering experience with a track record of shaping how an organisation builds software. - Depth sufficient to set technical direction across multiple services and teams. - Experience leading complex, cross cutting initiatives such as migrations, modernisation and platform work. - Design judgement that other engineers adopt, which is how the posting frames the seniority bar. The actual day to day: - Driving architecture and technical direction across multiple services and teams. - Leading complex, cross cutting initiatives including migrations and modernisation. - Raising engineering standards and mentoring senior engineers. - Operating as a senior individual contributor rather than a manager. Location and office reality: - ⚠️ Read this carefully. Turing's job board lists the role as India Remote. The posting body states: Location: Bangalore, India, In-office, Hybrid. We have published Bangalore because the body is the more specific statement, but confirm it in your first conversation before making any plans that depend on remote work. - The body also calls the role Staff Engineer while the board title reads Software Engineer. Honest fit guidance: - If you are applying because the board said remote, stop and check. This is the second time we have found a Turing posting where the board and the body disagree about location. - The role is a genuine individual contributor track, so it does not push you into management. - Turing's work spans frontier AI research support and enterprise AI systems. Ask which side this seat sits on, because they are quite different day to day.
Requirements as published: - BS or MS degree. - 8 to 11 years of experience in the security domain. - Strong hands on automation skills. - Experience securing cloud products and working with security tooling. The actual day to day: - Running and improving key security engineering and security operations capabilities. - Vulnerability management, named first in the responsibilities. - Security automation, playbooks and operational readiness. Location and office reality: - India. The posting does not name a city, and Yugabyte describes its team as distributed across more than 12 countries and multiple time zones. Ask about location expectations and about overlap hours with other regions. Honest fit guidance: - This is product and cloud security at a database company, so database and distributed systems familiarity helps even though it is not in the requirement list. - The distributed team across 12 countries usually means some meetings outside Indian working hours. The posting does not state a shift, so ask. - Yugabyte in this edition uses Staff for an 8 to 11 year role. Databricks in the same edition uses Senior Staff for 15 years. Titles are a local convention, not a level, which is why we publish the years the posting actually asks for.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the field empty rather than guess, so this role does not appear when you filter the board by years. - Strong technical and problem solving skills with recent hands on software development experience. - Experience with reliable distributed systems, with an emphasis on high volume data management in enterprise or web scale products operating under strict SLAs. - Broad technical knowledge spanning software development and automation. - Experience with a wide array of algorithms and data structures. - Expertise in Java, AWS, cloud based APIs, databases, and software design and programming best practice. Technologies named in the posting: - Java, SQL, Kubernetes, Docker, AWS, GCP, CircleCI. The actual day to day: - Working on the core data pipeline that moves terabytes of data from customers into their data warehouses. - Processing that data into clean, incremental, automated updates. - Working with cloud APIs, SQL and NoSQL databases and event systems. - Ensuring technical quality for your team and owned services through code contribution, code review and architectural design. - Mentoring more junior colleagues. Location and office reality: - Bengaluru. The posting states this is a full time position based out of the Bangalore office, on a hybrid model with two days a week in the office to collaborate as a team. That is unusually specific and clearer than most postings in this edition. Honest fit guidance: - The Senior title with no published years is a gap. Given the requirement for a track record with strict SLA systems, assume mid to senior rather than early career, and ask about levelling. - Fivetran is merging with dbt Labs and its postings warn you will encounter both brands in the process. That is disclosed rather than hidden, and it is not a red flag, just something to expect. - Two office days a week is one of the lighter hybrid requirements in this edition.
Requirements as published: - 8+ years of experience in a relevant field, and the posting states this must be from product based companies only. - Strong experience with microservice architecture. - Ability to lead technical architecture discussions and help drive technical direction. - Technical credibility to lead teams of software engineers, framed as technical leadership rather than people management. - JavaScript and Node.js experience is described as a huge plus rather than mandatory. Celigo says strong developers from other stacks looking to try something new are also welcome to apply. The actual day to day: - Designing and shipping turnkey business applications for users of cloud systems including NetSuite, Salesforce, Google, Amazon and Magento. - Working on business cloud computing (SaaS) integration problems. Location and office reality: - Hyderabad, hybrid. The posting states Location: Hyderabad, India (Hybrid) directly. Specific office days are not given. Honest fit guidance: - The product companies only requirement is unusual and it is explicit, so if your 8 years are from services or consulting firms, expect that to be a real filter. - The open invitation to developers outside the JavaScript and Node.js world is genuine and worth taking up if you have strong fundamentals in another language. - Integration work means other people's APIs, rate limits and data models. It is less glamorous than greenfield product work and considerably harder to do well.
Requirements as published: - 12+ years of professional experience, preferably in customer success management, relationship management, delivery management, consulting or enterprise delivery. - 3+ years of experience in the software industry, preferably at SaaS companies. - Prior hands on experience in Linux. - Command line hands on experience. - REST API experience is described as an advantage. - Docker and Kubernetes experience is good to have. - Ability to liaise with customers and regional teams, and to present technical material effectively. - Flexibility in working hours to accommodate a global presence. The actual day to day: - Owning the customer's continuous interaction with JFrog, their lifetime value and the associated NPS and CSAT scores. - Helping customers build an adoption and rollout plan so the JFrog Platform actually gets embedded. - Acting as the first point of escalation and becoming a platform health expert for your accounts. - Delivering projects with customers to agreed timelines, working with solution engineering and professional services. - Supporting the JFrog sales team on customer strategy so renewals and upsells happen on time. Shift and office reality, stated in the posting: - ⚠️ Working hours are 5:30pm to 2:30am IST. This is a North America region role and the shift is not negotiable in the posting. - Location is Bangalore (Bellandur) on a hybrid model with three mandatory days a week in the office. - JFrog states it provides office transport and a shift allowance. Honest fit guidance: - The night shift is the single biggest factor here. It is a good technical customer role, and it will reshape your day entirely. - There is no people management in this role despite the title, so it does not move you off the individual contributor track. - The technical bar is moderate: Linux, CLI and REST APIs, with containers as a bonus. This is a relationship and adoption role with real technical grounding, not a deep engineering seat.
Requirements as published: - 8+ years of post sales engineering or solutions architecture experience, working directly with customers. - 2+ years of software engineering experience and a strong understanding of the software development lifecycle. - Existing power user of AI coding tools, stated as a genuine expectation rather than a preference. The actual day to day: - Serving as the primary technical subject matter expert on OpenAI Codex for a portfolio of customers, embedding deeply to enable their engineering teams. - Partnering with engineering leaders and hands on builders to design, validate and scale advanced AI workflows. - Using Codex to prototype and build the demos, integrations and automations customers ultimately adopt. - Working across Sales, Solutions Engineering, Product, Applied Engineering and the wider Codex organisation to advocate for customer needs and shape product direction. Location and office reality: - ⚠️ OpenAI's job board marks this posting as remote and lists it under Delhi, India. The posting body states directly: This role is based in Bangalore. We have published Bangalore because the body is the more specific statement. Confirm before making plans. - OpenAI's other India postings state a hybrid model of three days a week in the office, so expect something similar here and ask. Honest fit guidance: - This is a customer facing role and the posting says so throughout. It is not a Codex engineering seat. - The 8 year requirement is for post sales or solutions architecture experience specifically, and the software engineering requirement is only 2 years. That combination is unusual, and it means deep customer facing history matters more here than deep coding history. - We kept this role and dropped OpenAI's Solutions Engineer posting from the same board, because that one is pre sales throughout while this one is technical deployment work with no quota language.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the field empty rather than guess, which means this role does not appear when you filter the board by years. - Creativity, problem solving and technical expertise sufficient to design tailored customer solutions. - Willingness to work embedded with strategic customers. The actual day to day: - Embedding with ElevenLabs' most strategic customers and building tailored solutions on the platform. - Working across the ElevenAgents, ElevenCreative and ElevenAPI product surfaces, which cover voice and chat agents, creative generation across 70 plus languages, and the developer API. Location and working model: - ⭐ Remote. The posting states: This role is remote, so it can be executed globally. ElevenLabs also says it prioritises talent, not location, and offers a monthly co working stipend if you are not near one of its hubs. - We checked this against the posting body rather than trusting the board's remote flag, because three postings in our last edition claimed remote and were not. This one holds up. What the company states about how it works: - High velocity: rapid experimentation, lean autonomous teams, minimal bureaucracy. - No job titles internally. Seniority is framed as impact rather than level. - An AI first expectation: the company says it uses AI across engineering, growth and operations. - Annual company offsite, plus a discretionary stipend to meet colleagues during the year. Honest fit guidance: - Forward Deployed Engineer means customer facing engineering. You write code, and you do it next to a customer with their deadlines in play. If you want to be left alone with a backlog, this is not that. - The absence of any published experience figure cuts both ways. It leaves the door open, and it also means you cannot tell whether you are under the bar until you talk to them. Applying is cheap here. - No job titles sounds appealing and it does make levelling and future job hunting harder to describe on a CV. Worth asking how they handle that.
Requirements as published: - The employer publishes no years of experience figure anywhere in this posting. We have left the field empty rather than guess, which means this role does not appear when you filter the board by years. Note: the posting does contain the phrase 50,000 years of audio, but that is a company statistic about data processed, not an experience requirement. - Based in an APAC time zone with reliable overlap to customer business hours across East Asia, Southeast Asia and Australia and New Zealand. - An AI first way of working, which Deepgram states is not optional: it expects every team member to actively use and experiment with advanced AI tools and to build their own into daily work, and it measures how effectively AI is applied. The actual day to day: - Leading architecture and implementation for enterprise deployments using Deepgram speech to text, text to speech and voice agent capabilities. - Owning post sales technical success for assigned accounts: unblocking integrations, optimising accuracy and latency, and guiding customers to stable production. - Acting as the Tier 3 escalation point for complex issues, driving root cause analysis and writing durable fixes or automation. - Designing reference architectures for common APAC use cases including contact centres, voice analytics, quality assurance and AI agents. - Building samples, internal tools and scripts that make repeatable work easier for customers and the team. - Contributing to pre sales discovery and proofs of concept when deep technical direction is needed. - Partnering with Product and Engineering to prioritise fixes and features. Location and working model: - ⭐ Remote. The posting states: this role is based out of India and will service the APAC region, and separately: Remote across APAC with periodic regional meetups. Verified against the posting body rather than the board's remote flag. - ⚠️ The role services East Asia, Southeast Asia and Australia and New Zealand, and asks for reliable overlap with those business hours. That is a real constraint on your working day even though no fixed shift is stated. Honest fit guidance: - Deepgram's Applied Engineering function deliberately combines what other companies split across solutions engineering, solutions architecture, consulting and senior technical support. Expect breadth. - The AI first expectation is stated more forcefully than at most companies, including that performance is measured on it. Take it literally. - The posting warns the work changes fast and says this may not be the right role if you want something highly prescriptive or a traditional nine to five. That is honest, and worth believing.