No roles match that combination.
New today · September 6, 2026
Who this is for: a systems programmer with about four years behind them who wants to work close to the metal on storage and is comfortable being handed a crash dump rather than a ticket. What the posting asks for: a bachelor's degree, four or more years of software development experience, and strong C++ with object oriented programming. A good understanding of Linux and Windows internals, specifically process, memory, storage and networking concepts. Hands on experience with debugging and troubleshooting tools such as gdb, WinDbg, ProcMon, Wireshark or tcpdump. Proven experience with crash dump analysis, memory leaks, handle leaks, deadlocks, race conditions and performance tuning. Strong experience with microservices and service architecture, client server architecture and distributed systems. A strong grounding in data structures, algorithms, object oriented design and design patterns. The day to day: designing, developing and maintaining core components in a distributed storage platform, participating in architecture discussions and technical design reviews, writing clean and well tested code, debugging complex production issues, improving system performance, mentoring junior engineers and running code reviews, and working with cross functional teams. Location: three named offices, Bangalore, Hyderabad and Pune. The advertisement does not state an office day policy. ⚠️ Read this before you engage with any recruiter: Commvault opens this advertisement with a fraud warning. It says scammers are impersonating Commvault staff, including HR and leadership, over email and text, and running fake interviews that ask for personal information such as national identity numbers. Commvault states that it does not conduct interviews by email or text, and that it will never ask you to submit sensitive documents, including banking information, before your first day. Suspected scams go to its recruiting team address. Honest fit note: the title says Senior but the bar is four years, which is unusually low for that word. If you have four to six years of C++ and you have ever debugged a production crash from a dump file, you are in range.
Who this is for: a front end engineer of five to seven years who is ready to own architecture and standards, not just tickets, and who is comfortable being the person others ask. What the posting asks for: five to seven years of experience in software engineering. A bachelor's or master's degree in computer science, engineering or a related field. Expertise in one or more modern programming languages, with Java, Python, JavaScript and C++ named. A strong understanding of distributed systems, cloud native services and performance optimisation. Experience with microservices, containerisation using Docker and Kubernetes, and cloud platforms across AWS, GCP or Azure. Excellent problem solving, mentorship and communication skills. A proven track record of delivering production grade software and improving team effectiveness. The day to day: designing and building scalable, high performance systems and services; leading feature development end to end with responsibility for quality, performance and maintainability; working with architects and senior engineers to influence system design and technical strategy; mentoring junior engineers; running code reviews and setting engineering standards; and finding and fixing bottlenecks in both production and development environments. Location: Bangalore HQ. The advertisement states no remote or hybrid policy. Worth knowing: Tekion moved its job board from Greenhouse to Ashby, and the advertisement itself notes the recruiting tool change and asks for patience with it. Existing Tekion employees are directed to apply through the internal board instead. Honest fit note: the qualification list is generic across several Tekion engineering advertisements, so the front end specificity lives in the title rather than the requirements. Ask at screening which product surface the requisition is attached to.
Who this is for: a security engineer of five to seven years who writes code, not just policy, and wants to own both the preventive controls and the detection layer. What the posting asks for: five to seven years of experience in security engineering, cloud security or infrastructure protection. A bachelor's or master's degree in computer science, cybersecurity or a related field. Deep experience with AWS, GCP or Azure security services and infrastructure hardening. Strong scripting and automation skills, with Python, Bash and Terraform named. Proficiency with security tooling across SIEMs, IDS and IPS, SAST and DAST, and web application firewalls. Familiarity with compliance frameworks including SOC 2, ISO 27001 and NIST. Excellent analytical, troubleshooting and communication skills. The day to day: designing and implementing advanced security controls across cloud, application and network layers; leading threat modelling and security design reviews for high impact systems; developing detection mechanisms, incident response playbooks and remediation strategies; driving automation of security operations including monitoring, alerting and vulnerability management; working with engineering, product and DevOps teams to build security into development pipelines and platform architecture; and mentoring junior security engineers. Location: Bangalore HQ. No remote or hybrid statement is published. Honest fit note: Tekion was running three identical copies of this advertisement on its board today. We published one. If you see the role listed several times, it is one job, not three teams hiring.
Who this is for: an SDET of about five years with expert Python who wants to specialise in evaluating machine learning and large language model systems rather than testing conventional web applications. What the posting asks for: five or more years in an SDET role. Expert level Python for test automation and evaluation pipelines. Experience building and maintaining scalable test automation frameworks for APIs, backend services and model endpoints. Familiarity with the AI evaluation frameworks named, RAGAS and DeepEval. Understanding of retrieval augmented generation, vector databases, embeddings and semantic similarity. Statistical literacy sufficient to validate data distributions and analyse precision, recall and error patterns. Experience embedding evaluation suites into MLOps and CI/CD pipelines. The day to day, in the posting's own structure: generative AI and large language model evaluation, covering hallucination, bias, toxicity and prompt injection testing, RAG evaluation, multi agent workflow validation, automated conversation simulation across intents and multi turn dialogue, and prompt regression frameworks that measure how system prompt, temperature and sampling changes affect output consistency. Data quality assurance, covering statistical validation of AI outputs, programmatic auditing of ingestion, transformation and feature store pipelines for schema drift and corruption, vector database index and retrieval validation, and privacy compliance checks on synthetic training data. Classical machine learning and deep learning validation, tracking standard metrics and loss curves across versions and monitoring live endpoints for drift. Automation engineering, embedding all of it into CI/CD so quality failures block releases automatically, and defining AI quality key performance indicators for release readiness. Location: Bangalore HQ. No remote or hybrid statement is published. Honest fit note: this is a genuinely specialised role and the requirement list is deep. If you have strong Python test automation but have never evaluated a model, say so early rather than hoping the overlap carries you, because the responsibilities are almost entirely on the AI side.
Who this is for: a mechanical engineer of five to seven years who has taken a physical product from CAD through contract manufacture and into the field, and who wants that product to be robotics hardware feeding AI training data. What the posting asks for: a bachelor's or master's degree in mechanical engineering or a related discipline. Five to seven years of hands on experience designing and delivering physical products or robotics hardware. The advertisement writes that figure out in words rather than digits, which is worth noting because automated experience filters miss it. The day to day: owning mechanical design and development of Instacore and future hardware from requirements through production and field deployment; creating detailed CAD models, assemblies, engineering drawings, bills of materials and manufacturing documentation; rapid prototyping and validation using 3D printing, machining, fabrication and off the shelf components; designing durable mounts, enclosures, fixtures, wearable components, packaging and protective systems; owning design for manufacturability, assembly, serviceability, reliability and cost; improving cable routing, connector retention, strain relief, thermal management, ingress protection and resistance to vibration and impact; designing packaging and logistics that survive storage and transit; establishing verification, stress testing and acceptance procedures; investigating field failures and implementing fleet wide corrective improvements; owning maintenance and repair strategy including spare parts, repair documentation and technician procedures; managing vendors, fabricators, suppliers and contract manufacturers; owning component sourcing, inventory planning and hardware logistics; and working with robotics, electrical, firmware, software, operations and field teams. The role also mentors technicians and junior engineers, but the advertisement is explicit that it stays deeply hands on. Location: Bangalore. No remote or hybrid statement is published. Honest fit note: this is the only mechanical engineering role in today's edition. If you are a software engineer, this is not a bridge into robotics, because the entire requirement list is physical design and manufacturing.
Who this is for: a data analyst of six to eight years who is fluent in SQL, can build a dashboard people actually use, and is comfortable presenting a recommendation to leadership. What the posting asks for: six to eight years of experience in data analytics, business intelligence or a related field. A bachelor's degree in data science, statistics, computer science or a related field. Advanced proficiency in SQL and in a data visualisation tool, with Power BI and Tableau named. Strong analytical thinking, problem solving and business acumen. Excellent communication and presentation skills for both technical and non technical audiences. Experience working with large datasets and across cross functional teams. The day to day: data extraction, transformation and analysis supporting business performance monitoring and strategic decisions; building dashboards, reports and visualisations; deep dive analyses to find trends and opportunities to improve operational efficiency; working with stakeholders to gather requirements and build models for forecasting, segmentation and scenario analysis; enforcing data quality through validation and quality control procedures; partnering with engineering and data teams to improve data infrastructure and access to clean, structured datasets; and presenting findings with a clear business narrative. Location: Chennai Regional Office. No remote or hybrid statement is published, and note this is a different city from the Bangalore headquarters carrying Tekion's other listings today. Honest fit note: the advertisement's internal summary calls the role Senior Data Analyst while the title says Data Analyst. Ask which level the requisition is approved at, because the six to eight year bar suggests the summary is the more accurate one.
Who this is for: a front end or full stack engineer of seven or more years who wants to build operator tooling for infrastructure rather than consumer surfaces, and who is ready to set architectural direction for a UI team. What the posting asks for: seven or more years of professional experience in frontend or full stack software development. Strong proficiency with React and modern React practice, covering hooks, state management, component architecture and asynchronous data flows. Deep understanding of TypeScript, JavaScript, browser behaviour, API integration and frontend performance. A strong command of HTML5, CSS3, responsive design, accessibility and cross browser compatibility. Experience with modern styling approaches such as Tailwind CSS or SCSS. Experience delivering multiple production features through release and support. Strong communication, collaboration, problem solving and mentoring skills. Preferred rather than required: working knowledge of Angular, TypeScript component architecture and RxJS. The day to day: designing and maintaining scalable single page applications in React and TypeScript; owning features from requirements through production support; building reusable, accessible, responsive components against a design system; working with UX, product and backend teams; contributing to frontend architecture, API integration, performance and maintainability; writing unit, integration and end to end tests with Cypress or similar and closing coverage gaps; diagnosing complex frontend, test and environment issues with minimal oversight; giving design and code review feedback, mentoring engineers and taking part in interviewing; and folding customer and field feedback back into usability and quality. ⚠️ Location, and a defect in the advertisement itself: the posting says you will be expected to work primarily from the office, but the office name is an unrendered template placeholder. The advertisement literally reads that you will work from the {{OFFICE_LOCATION}} office. The listing location is Bangalore, and a sibling Everpure advertisement posted at the same time has the placeholder correctly filled with Bangalore, so Bangalore is the near certain answer. Get it confirmed in writing anyway. The posting also carries an internal onsite tag. Honest fit note: this is a senior individual contributor role with a Lead title. There is no people management in it, which is good news if you want to stay technical and worth checking if you wanted the other thing.
Who this is for: a Java engineer of seven or more years who is already doing system design work and wants the architecture influence written into the job rather than earned informally. What the posting asks for: seven or more years of experience. Strong experience producing high level and low level design for large scale systems. Proficiency in Java, Python or C++. Expertise in data structures, algorithms and design patterns. Hands on experience with microservices architecture, RESTful APIs and a cloud platform across AWS, Azure or GCP. Knowledge of SQL and NoSQL databases and caching mechanisms. Excellent problem solving and analytical skills. A bachelor's or master's degree in computer science or a related field. Preferred rather than required: experience with distributed systems, event driven architecture and messaging queues; exposure to CI/CD pipelines, Docker and Kubernetes; strong communication and leadership skills. The day to day: creating high level and low level designs for complex distributed systems and defining architecture patterns, data flow and integration points; writing clean, efficient, maintainable code in Java, Python or a similar language; implementing microservices and APIs; optimising systems for high availability and low latency; working with product managers, architects and QA; mentoring junior engineers on design and coding standards; and ensuring adherence to coding guidelines and design principles through code review. Location: Hyderabad. This particular advertisement does not state an office day policy, though HighRadius has published a five days in office requirement on other engineering advertisements, so ask. Honest fit note: the responsibilities section is oddly labelled, with a good to have marker sitting above the system design duties. Treat the requirement list as the reliable half of this posting.
Who this is for: a Java web developer of seven or more years who wants to move into identity and security engineering and does not yet have that background, because the posting puts identity knowledge in the optional column. What the posting asks for as minimum requirements: seven or more years of experience building Java based web applications. A good understanding of design patterns, scalability patterns, security engineering and object oriented principles. Experience working in fast paced software development teams using continuous integration and deployment. Strong communication skills and the ability to work across functions. A bachelor's degree in computer science or equivalent experience, with the education section separately noting seven years of software development experience. Nice to have rather than required: experience building anomaly detection or risk systems, which the posting calls a huge plus; experience in cloud security, identity or authentication protocols; experience with a UI technology such as Angular, React, Backbone or Vue; and a strong understanding of identity and access management protocols including FIDO, WebAuthn, single sign on, SAML and OAuth. The day to day: working with QA, product, support and UX for integration; contributing to technical designs, proposals and architectural decisions; developing maintainable software components with comprehensive unit and functional tests; taking part in code reviews with attention to coding standards and security practice; and contributing to technical documentation and knowledge sharing. Location: Bengaluru, and the advertisement carries an internal hybrid tag, so expect a mix of office and home rather than either extreme. Get the specific office day count in writing. Honest fit note: this is the most open door of Okta's five listings today. If your Java is strong but your identity knowledge is thin, this is the one to read first.
Who this is for: a backend engineer of seven or more years in Java or Go who wants to work on access governance at enterprise scale and is comfortable owning production consequences. What the posting asks for: seven or more years of experience with Java, using Spring or Dropwizard, and or Golang, with a deep understanding of multi threading and asynchronous processing. An understanding of OAuth 2.0, OpenID Connect and JSON web tokens, specifically for service to service communication. Demonstrated AI fluency in agentic systems. A bachelor's degree in computer science or a related field. The day to day: end to end ownership of feature areas from technical design through implementation, testing, deployment and post launch monitoring; designing, building and shipping production ready features across the Identity Governance system with a focus on correctness, reliability and performance; delivering bug fixes quickly and handling customer reported issues; writing clean, well tested, maintainable code and holding the team to that bar; and partnering with product development, QA and site reliability engineering to scope development and deployment work. Location: Bengaluru, with an internal hybrid tag on the advertisement. Confirm the office day count at screening. Worth knowing: Okta lists AI fluency in agentic systems as a required ability here rather than a preference. That pattern has now appeared in several employers' requirement sections rather than their bonus lists, so it is worth being able to describe concrete work you have done with AI tooling. Honest fit note: Okta was running two advertisements under this exact title today, under two different requisition ids, with bodies that are about 95 percent identical. A third, separately worded advertisement adds Full Stack to the title. We published one of the pair. If you find the same title twice, it is very likely one job.
Who this is for: a backend engineer of eight or more years who wants to build cloud infrastructure software in Go and is comfortable owning a service in production rather than handing it to an operations team. What the posting asks for as minimum qualifications: a bachelor's degree in computer science, a related technical field, or equivalent practical experience. Eight or more years of professional experience designing, building and deploying production grade product components using Go, Java or C++. A proven background in microservices architecture, cloud deployments and distributed systems design. Strong knowledge of core computer science fundamentals including algorithms, data structures and maintainable software engineering principles. Exceptional team oriented communication skills. The day to day: developing, testing and integrating high performance microservices and features into the Portworx product suite with high availability in distributed systems; leading software lifecycle activities including architectural design, code reviews, unit and functional testing, documentation and continuous integration and deployment; working with product managers, engineering peers and early adopter customers to turn requirements into production ready software; owning feature stability by acting on customer feedback and resolving issues found in testing and deployment; and researching emerging technologies and cloud infrastructure tools. Location: Bangalore, and the advertisement carries an internal onsite tag, so treat this as an in office role rather than hybrid. Worth knowing: Everpure ran a second advertisement today, titled Portworx Enterprise, whose body is identical to this one. It is the same job described twice, not two openings. Honest fit note: Everpure is the company formerly known as Pure Storage, and its recruiting email addresses still use the old domain. The company name in this listing comes from the job description text, which is the only reliable source.
Who this is for: a Salesforce engineer of eight or more years who wants the work treated as real platform engineering, with governance, release management and technical debt reduction in scope. What the posting asks for as minimum requirements: a bachelor's or master's degree in computer science, information systems or a related field. Eight or more years of experience in Salesforce development and enterprise application engineering. Strong hands on capability across the core Salesforce platform including custom development, automation and integrations. The day to day: designing, building and maintaining scalable Salesforce solutions across the core platform; working with business stakeholders, program managers and technical teams to turn requirements into secure, maintainable solutions; owning delivery across design, development, testing, deployment, documentation and production support; working with globally distributed engineering teams in an Agile environment; driving engineering practice across code quality, documentation, release management and platform governance; finding opportunities to improve performance, simplify architecture, reduce technical debt and strengthen the Salesforce operating model; troubleshooting complex production issues with durable fixes; and keeping current with platform capabilities. On AI tooling: the advertisement names GitHub Copilot, Agentforce, Claude Code and Cursor as tools you are expected to use to improve productivity, code quality, troubleshooting and documentation, while exercising judgement about security, privacy and responsible use. Location: Gurugram, and the posting states plainly that it is looking for candidates based in Gurugram for a hybrid working model. This is not a remote role. Honest fit note: the title says GTM Tech, which reads like a go to market or sales role. It is not. It is Salesforce platform engineering, and the requirement list is entirely technical.
Who this is for: a DevSecOps or platform security engineer of eight or more years who is comfortable being the single technical authority across a heterogeneous enterprise estate rather than one product codebase. What the posting asks for: eight or more years of hands on experience in DevSecOps, site reliability engineering or security engineering, with at least three years in a senior or lead capacity supporting enterprise applications. The day to day, by the posting's own headings. Enterprise DevSecOps architecture and CI/CD security: architecting enterprise grade CI/CD and deployment frameworks across Salesforce via Gearset or Copado, Adobe Experience Manager and web via CircleCI or GitHub Actions, NetSuite and Workday; integrating automated static analysis, dynamic analysis, software composition analysis and secrets detection using SonarQube, Snyk, PMD, GitGuardian and OWASP ZAP; standardising secrets management with tooling such as HashiCorp Vault and safeguarding third party dependencies, API integrations and package deployments. Edge, web application firewall and network security: managing and optimising enterprise content delivery network policies via Cloudflare to protect web properties and API endpoints against denial of service, volumetric and layer seven attacks; defining web application firewall rules, rate limiting, ModSecurity policies and bot management for public facing endpoints. Identity access and platform hardening: working with information security to manage identity policies, role based access control, OAuth 2.0, JSON web token authentication and SAML or single sign on integrations across Salesforce, NetSuite, Adobe Experience Manager Cloud, Workday and Okta or Entra ID. Location: Bengaluru. This advertisement publishes no remote or hybrid statement, unlike Okta's other listings today which carry hybrid tags. Ask. Honest fit note: the breadth here is the risk. If your depth is in one platform, expect to be tested on the others, because the role is defined as the authority across all of them.
Who this is for: a front end engineer of eight or more years who has already been operating as an architect informally and wants the mandate written down, including the authority to choose technologies. What the posting asks for as basic qualifications: a bachelor's or master's degree in computer science, software engineering or a related field. Eight or more years of professional frontend development experience, including significant experience in architectural or lead roles. The day to day: defining, designing and documenting front end application architecture with attention to scalability, performance, accessibility and maintainability; establishing and enforcing front end best practices, frameworks and design patterns across teams; working with UX and UI designers to turn design concepts into accurate interfaces; working with backend engineers to design robust APIs and data integration strategies; providing technical guidance and mentorship to front end teams and running code reviews; optimising front end performance across browsers and devices and proactively finding bottlenecks; evaluating and selecting technologies, frameworks and tools; contributing to cross team architectural initiatives and promoting reusability across web and mobile; tracking emerging front end trends and assessing their relevance; and maintaining documentation of architecture, workflows and practices. Location: Bangalore HQ. No remote or hybrid statement is published. Honest fit note: this is an architect title without direct reports, so the influence is technical rather than managerial. If you want headcount, this is not that role. If you want to set the front end direction for a product suite, it is.
Who this is for: a Java backend engineer of eight or more years who needs to work remotely from anywhere in India, which readers of this list have said repeatedly is what makes a job possible rather than a perk. What the posting asks for as required qualifications: a bachelor's degree in a computer science related field as a minimum requirement. Eight or more years of proven experience as a Java developer with a strong understanding of the Java language and ecosystem. Experience building resilient, high throughput microservices and distributed systems. A strong understanding of REST APIs. Strong communication and collaboration skills. Experience with Java frameworks. The day to day: designing, developing and implementing high quality Java applications and microservices; working with cross functional teams to define, design and ship features; taking part in code reviews for code quality and standards adherence; troubleshooting and debugging to keep application performance smooth; owning and operating high scale cloud based systems and services; documenting technical specifications and procedures; and managing your work through GitHub, Jira and Twilio's build and deploy systems. Location and remote policy, which is the reason this role leads: the listing location is Remote, India. Twilio states a dedication to remote first work and says that no matter your location you are part of the team. It is equally clear that while it is a remote first company, you may be asked to report in person on an ad hoc basis for team gatherings, functional off sites or customer meetings. The team itself is described as the Identity Platform Team in Bangalore, so occasional travel to Bangalore is the sensible assumption. On hiring process: Twilio states that it uses artificial intelligence to make its hiring process efficient, and that every hiring decision is made by a person. Honest fit note: Twilio adds that it values diverse experience and encourages people whose careers have not followed a traditional path to apply. That is boilerplate on many advertisements, but the eight year Java bar is not, so treat the experience line as the real gate.
Who this is for: a full stack engineer of nine or more years who is fluent in both a modern backend language and modern JavaScript, and who has real, describable experience using AI coding tools in production work. What the posting asks for: nine or more years of extensive programming experience in a modern programming language such as Go, Java or C++, especially in backend services. Eight or more years of experience working with PostgreSQL or an equivalent relational database system. Proven expertise leveraging AI development tools, with GitHub Copilot and Anthropic Claude named, to accelerate the software development lifecycle while maintaining high code quality. The day to day: using AI pair programmers and large language models to accelerate development of secure, enterprise grade privileged access management products; working with engineering teams to design, develop and deliver cloud based privileged access management solutions; designing, building and maintaining end to end features using modern JavaScript and cloud native backend technologies; leading technical design for key initiatives with attention to quality, scalability and maintainability; building reusable and performant user interface components for a no code builder experience; driving evaluation, development and rollout of new features and common platform components; and evolving existing systems for specialised circumstances. Location: Bengaluru, with an internal hybrid tag on the advertisement. ⚠️ Worth knowing before you negotiate level: Okta is running a second advertisement with a nearly identical body under the title Staff Software Engineer, Privileged Access Management. Both ask for nine or more years of programming. The only material difference we found between the two is the database line, where the Principal version asks for eight years of PostgreSQL and the Staff version asks for four. If you are being screened for one, it is reasonable to ask why the same work carries two level names, and which requisition your offer would be made against. Honest fit note: the body itself says the team is looking for a staff level full stack engineer, inside an advertisement titled Principal. Read the requirements, not the title.
Who this is for: a backend engineer of ten or more years in Go who wants to be the technical anchor for a new team without moving into management, and who is comfortable with vaguely specified problems and no daily oversight. What the posting asks for: ten or more years of software engineering experience, with a proven track record of acting as a technical leader or a Principal or Staff level individual contributor. The advertisement uses the phrase individual contributor explicitly, which is worth noting given the level. The day to day: turning high level, complex privileged access and network access problems into clear, modular technical designs the team can execute; designing, architecting and optimising resilient connector plugins for diverse database environments across software as a service, NoSQL and relational systems, and for complex network infrastructure, using the existing core platform frameworks; setting the standard for clean, secure and performant backend development in Go and running deep code reviews with a mentoring focus; working with global technical leads in Tel Aviv to review major architectural decisions while keeping local autonomy and velocity; and taking part in the global on call and support rotations. Location: Bengaluru, with an internal hybrid tag on the advertisement. There is a reference to leading technical direction for highly autonomous remote engineering pods, but that describes the working style of the teams, not a remote work offer for this role. Honest fit note: the collaboration is with Tel Aviv, so expect some overlap hours outside the Indian working day. The advertisement does not quantify that, so ask what the expected overlap is before you accept.
Who this is for: an enterprise information technology engineer of ten or more years whose depth is in Google Workspace administration and who wants the architecture and AI adoption side rather than a helpdesk queue. What the posting asks for: ten or more years of experience administering and managing enterprise grade Google Workspace environments. The day to day: leading the design, implementation and long term strategic vision for enterprise Google Workspace tools across Gmail, Drive, Meet, Calendar and Docs, together with integrated generative AI capabilities in Google Gemini; driving the rollout, administration, governance and organisational adoption of Google Gemini Enterprise capabilities across Workspace; developing automation scripts using Google Apps Script, Google Apps Manager and APIs to optimise group management, administrative workflows and AI enabled automation; configuring SAML based single sign on and SCIM provisioning and deprovisioning for automated user lifecycle management and role based access control; implementing security policies, compliance standards, data loss prevention, AI governance frameworks and mobile device management to secure corporate data across endpoints; and resolving complex technical escalations, working with Google and third party vendors, and delivering end user training. Location: Bangalore, and the posting states plainly that the role joins the Bangalore information technology team in a hybrid capacity. Reporting line: the Director of Business Applications Support. Honest fit note: if you are a software engineer looking at this because it says Staff Engineer at a security company, it is not that. It is a Workspace platform role and the requirement is ten years of Workspace administration specifically.
Who this is for: a distributed systems engineer of twelve or more years who wants ownership of a major area rather than a team, and who is genuinely comfortable debugging at the operating system and cluster level. What the posting asks for: twelve or more years of industry experience building and supporting large scale distributed systems. This is the highest experience bar in today's edition. The day to day: delivering a highly scalable, available and fault tolerant engine processing hundreds of terabytes of data daily across thousands of customers; low level systems debugging, performance measurement and optimisation on large production clusters; architecture design, influencing the product roadmap and owning new projects; using deep experience to prevent and investigate production issues; planning and leading complicated technical projects spanning several teams; acting as a strong influencer on the organisation's roadmap and direction; leading a technical leadership group or similar review committee, or initiating and sustaining an engineering wide initiative; and breaking down complex problems into solutions, knowns and unknowns in order to de risk them. How the role is framed: the advertisement describes it as an executive engineering individual contributor position reporting to an engineering leader, with full ownership of a product or infrastructure direction in a major area, serving as a force multiplier by raising stability, reliability and organisational process. Mentoring senior engineers and contributing to recruiting are named responsibilities. Location: Bengaluru. The advertisement publishes no remote or hybrid statement. Honest fit note: this is a level where the interview will probe organisational impact as hard as it probes system design. Come with examples of initiatives you sustained across teams, not just systems you built.
Who this is for: a support or platform engineer of four or more years who can read logs and API traces confidently, and who wants customer facing ownership rather than a ticket queue with a script. What the posting asks for: four or more years of experience in a similar role. The day to day: front ending all customer reported issues and owning them through resolution; reviewing, identifying, troubleshooting and resolving issues within agreed service level agreements; managing customer expectations as the primary point of contact for technical support issues; proactively diagnosing and troubleshooting issues on the Observe.AI platform; escalating complex issues to engineering with appropriate debugging information and impact analysis; working with product, engineering and customer success teams to drive resolution; performing log analysis, API troubleshooting and root cause analysis; creating and maintaining internal knowledge base articles and troubleshooting documentation; and continuously improving support processes. What the posting offers beyond the queue: hands on exposure to real technical challenges, contribution to pre release testing and product quality, and a hand in shaping customer facing documentation and training materials. The advertisement also states competitive compensation and benefits of the kind usually found at larger, established companies. Location: Bengaluru. No remote or hybrid statement is published, so ask. Honest fit note: this is customer facing work with service level agreements attached, and the posting mentions participation in rotations. If you want to write product code all day, this is not that role, but it is one of the more accessible technical seats on today's list.
Who this is for: a technical support or solutions engineer of six or more years with real mobile depth, who wants senior escalation ownership and a route into influencing product rather than only closing cases. What the posting asks for: six or more years of experience in technical support, solutions engineering or similar roles working directly with complex software as a service products. The day to day: acting as a senior technical escalation owner leading complex investigations end to end across Samsara's mobile ecosystem; working with engineering and product teams to drive issue resolution, improve product quality and influence roadmap decisions affecting reliability, compliance and supportability of the mobile applications; representing the voice of the customer across North America and Europe; driving operational excellence in escalation and support processes; setting a high bar for technical investigations; mentoring and guiding level two engineers; and owning high impact, multi customer issues spanning multiple products and regions. How the role is framed: the posting states plainly that Product Support Engineer III is a senior individual contributor role requiring technical depth, ownership and leadership. There are no direct reports. Location: Bengaluru. Samsara describes a flexible, employee led remote model and says its offices are open for those who prefer to work in person, while supporting remote work where it aligns with operational requirements. That is a genuine but conditional statement, so confirm what it means for this specific team before you rely on it. Honest fit note: the customers are North American and European, so expect the support coverage to shape your hours. Ask about the shift pattern at screening.
Who this is for: a technical support engineer with customer facing experience who is comfortable across hardware and software, and who can genuinely accept a rotating shift pattern that includes weekends. What the posting asks for: hands on experience in customer facing roles and or technical support environments. A strong customer service mindset with excellent interpersonal and communication skills. Solid technical aptitude with attention to detail and problem solving ability. No years of experience figure is published anywhere in the advertisement, so we have recorded none rather than inventing one. The day to day: owning, troubleshooting and resolving customer technical issues across all severity levels; proactively understanding customer requirements and expectations; communicating clearly and professionally with customers; creating and maintaining knowledge base articles and frequently asked questions for internal and customer facing use; managing multiple support cases and priorities at once; acting as a customer advocate internally and representing the company externally; working within a team while continuing to learn; and taking part in weekend, public holiday and on call support rotations. The work also includes implementation such as software and hardware upgrades and return merchandise authorisation dispatch. ⚠️ Shift reality, stated plainly by the employer: workdays include weekends, with an expectation to adapt to rotational shift schedules within a twenty four by seven support environment. This is unusually direct for a job advertisement and it is the single most important line in it. Location: the posting says you will work primarily from the Bangalore office in alignment with company policies, unless on approved leave, travel or remote exceptions. The advertisement also carries an internal onsite tag. Honest fit note: Everpure is the company formerly known as Pure Storage and its recruiting email addresses still use the old domain. The employer name here comes from the job description text.
Who this is for: someone who has worked at the intersection of business and technology, thrives in customer facing work, and understands how modern engineering organisations and the software development lifecycle actually operate. A reader of this list asked for technical account management and customer success roles specifically, and this is that shape of job. What the posting asks for: experience at the intersection of business and technology with a track record in customer facing roles. The ability to translate customer needs into clear technical plans and measurable outcomes. An understanding of modern engineering organisations, the software development lifecycle, developer workflows and tool adoption. Comfort communicating with both developers and senior executives. An analytical and operational approach, using data to prioritise. Being an existing Cursor user or power user of modern AI coding tools with strong opinions is listed as a big plus. No years of experience figure is published, so we have recorded none. The day to day: managing a book of business made up of top enterprise customers and owning the long term success of each account; engaging chief technology officer, vice president and senior vice president engineering stakeholders to demonstrate return on investment and guide AI driven organisational change; leading enterprise rollouts end to end covering onboarding, enablement, internal champions and scaled adoption; turning high impact use cases into durable, repeatable workflows across teams; monitoring account health and usage data to drive renewals and expansion alongside account executives; and representing the customer internally to influence product priorities. How success is measured, in the posting's own words: customer retention, product adoption and revenue expansion. Location: listed as India, with no city named and no remote or hybrid statement. Ask, because Cursor's advertisement is unusually short and leaves this open. Honest fit note: the title says Manager but there are no direct reports. What it manages is a portfolio of accounts. If you want pure engineering, this is not it. If you have wanted a technical role that is customer facing without being a quota carrying sales job, this is closer than most.
Who this is for: an MLOps or platform engineer with deep Python who wants to work on the infrastructure layer under large model training, and who is comfortable that part of the audience for the work is internal sales and field teams. What the posting asks for: deep Python expertise, described as the core requirement for the role. Experience with the open source MLOps ecosystem, with Kubeflow, MLflow and Ray named. Experience with continuous integration tooling such as Git and Jenkins. Infrastructure as code, with Ansible and Terraform named. GPU accelerated Kubernetes, bare metal and virtual machine environments. Model serving and optimisation, with NVIDIA Triton Inference Server, quantisation, model sharding via DeepSpeed or Megatron, and dynamic batching named. No years of experience figure is published anywhere in the advertisement, so we have recorded none rather than guessing. The day to day: leading development of end to end MLOps workflows integrating the company's storage products as the data plane for ingestion, training and inference; creating validated, repeatable reference architectures as infrastructure as code spanning bare metal, virtual machines and GPU accelerated Kubernetes clusters for distributed training; architecting high throughput, low latency model serving for large models; developing automated, GPU enabled MLOps lab environments, technical documentation and live demonstrations to enable global sales, field engineering teams and strategic partners; and working with data scientists and product management on the technical strategy for AI platform integrations. ⚠️ Location, and a defect in the advertisement: the posting says you will be expected to work from the office, but the office name is an unrendered template placeholder and the advertisement literally reads {{OFFICE_LOCATION}}. The listing location is Bangalore and a sibling Everpure advertisement has the same sentence correctly filled with Bangalore. Confirm it in writing. Honest fit note: the internal title in the body is Senior MLOps Solutions Engineer, and sales enablement is one of five named duties. If you want to be purely behind the product, weigh that.
Who this is for: a systems performance engineer with expert Linux depth who wants to own benchmarking strategy for a storage product line rather than run someone else's test plan. What the posting asks for: proven experience designing and executing system level performance testing for enterprise grade solutions, including servers, storage using storage area network protocols such as iSCSI, NFS and SMB, and databases. Expert level proficiency with Linux systems including in depth knowledge of network configuration, the storage stack and system settings. No years of experience figure is published anywhere in the advertisement, so we have recorded none. The day to day: establishing comprehensive, next generation performance benchmarking requirements and metrics for all FlashArray products across diverse platforms; providing technical direction and leadership to a team of engineers and ensuring timely delivery of performance results; working with product management, solutions and sales engineering to research and develop performance validation strategies that model real customer use cases; and overseeing deep dive analysis of performance bottlenecks within the Linux storage and networking stack to find optimisations that produce measurable throughput and latency gains. Location: Bangalore. This advertisement states that you will be expected to work primarily from the Bangalore office, and unlike two of Everpure's other listings today, this one has the office name correctly filled in rather than left as a template placeholder. Honest fit note: the posting includes providing technical direction and leadership to a team. It names no hiring, headcount or performance review duties, so we read it as technical leadership rather than people management, but if that distinction matters to you, get it confirmed at screening.
Who this is for: a backend engineer who wants to work on data infrastructure at the connector layer, is comfortable with Kubernetes as the runtime, and can accept two days a week in a Bangalore office. What the posting asks for: experience building and operating production backend services, sufficient to own technical excellence for a team's services. Comfort working across a wide range of tasks from patching existing software through to building new connectors. Experience with Kubernetes as a compute platform. The ability to contribute to architectural design, review code and mentor junior colleagues. No years of experience figure is published anywhere in the advertisement, so we have recorded none rather than inferring one from the word Senior. The day to day: building and working on data pipelines that move data from various sources into data warehouses; work described by the employer as very diverse, from patching software to building new connectors operating on a global Kubernetes compute cluster; ensuring technical excellence for your team and its owned services by contributing code, reviewing code and contributing to architectural design; and mentoring junior colleagues. Location and office policy, published clearly: this is a full time position based out of the Bangalore office, and the hybrid model includes two days in the office each week. Publishing a specific day count is rarer than it should be, and it is worth crediting. Company context worth knowing: Fivetran and dbt Labs are integrating. The advertisement says you may encounter references to both companies across the recruiting process and career sites during the transition. If team structure or product ownership matters to your decision, ask where this team lands after the integration. Honest fit note: with no years figure published, the level is genuinely ambiguous. Ask what band the requisition is approved at before you discuss compensation.
Who this is for: a test automation engineer who wants architecture and strategy responsibility rather than script maintenance, and whose toolkit is the mainstream automation stack rather than something proprietary. What the posting asks for: strong programming skills in Java, Python or JavaScript. Expertise in test automation frameworks, with Selenium, TestNG, Cypress and Playwright named. Experience in API automation testing. Knowledge of SQL and NoSQL databases. Hands on experience with continuous integration and deployment pipelines. No years of experience figure is published anywhere in the advertisement, so we have recorded none, and the Roman numeral three in the title is the only level signal. The day to day, by the posting's own headings. Automation and test strategy: designing, developing and maintaining scalable automation frameworks across user interface, API and backend; driving test strategy and architecture decisions for complex systems; building reusable testing utilities and tools; and ensuring high automation coverage across releases. Test development and execution: developing automated scripts using Selenium, Cypress or Playwright; API testing using RestAssured, Postman or similar; and implementing performance and load testing with JMeter or Gatling. Continuous integration and DevOps: integrating automated tests into pipelines using Jenkins, GitHub Actions or Azure DevOps, ensuring continuous testing, and working with DevOps to improve build and deployment pipelines. Quality engineering practice: defining and enforcing quality standards and processes, reviewing test automation code, and mentoring junior software development engineers in test and quality assurance engineers. Cross functional work: working with developers and product teams on requirements, taking part in sprint planning, design discussions and retrospectives, and championing shift left testing. Location: Hyderabad. This advertisement publishes no office day policy, though HighRadius has stated a five days in office requirement on other engineering advertisements, so ask. Honest fit note: the title Agent Developer Test is HighRadius internal naming and does not mean you build AI agents. The requirement list is test automation engineering throughout.
Who this is for: an MLOps or platform engineer who wants ownership of the whole path from a trained model to a monitored production service, including the cost of running it. What the posting asks for: experience with enterprise software as a service solutions built for high availability and scalability. Experience handling large scale structured and unstructured data from varied sources. Practical experience with containerisation and orchestration using Docker and Kubernetes or serverless platforms. Experience with model versioning and governance tooling, with MLflow named. Familiarity with retrieval augmented generation stacks including vector databases and knowledge graphs. AWS Bedrock is stated as preferable, as is Monte Carlo for monitoring. No years of experience figure is published anywhere in the advertisement, so we have recorded none. The day to day: designing, developing and maintaining stable AI and machine learning operations platforms and pipelines; packaging and deploying services to production so they are reproducible and interpretable; designing automated continuous integration and deployment pipelines to accelerate model deployment; provisioning and optimising training and serving infrastructure; implementing post deployment monitoring for model performance, data drift and latency; automating retraining and data pipeline workflows; managing deployment of foundation models, fine tuning workflows and retrieval augmented generation stacks; managing GPU and CPU utilisation to minimise cloud cost while keeping inference latency low; working with data scientists, data engineers and software engineers; managing versioning and governance for data, code and models; implementing data security and governance compliance; and diagnosing complex data platform issues. ⚠️ Location, and an honest warning: the listing location is Bangalore, India, and the only statement about working arrangements anywhere in the body is an internal remote tag. There is no policy sentence, no office day count and no remote commitment in the prose. We have published it as Bangalore because that is the stated location. Yesterday two Smartsheet advertisements carried the same remote tag while their own titles said Hybrid in Bangalore, so treat the tag as unreliable and get the arrangement in writing before you invest in the process. Honest fit note: the requirements section is written loosely, with several sentences trailing off mid clause. Expect the screening call to be where the real bar gets defined.
Read this before you apply
- The only number of years in some advertisements is the company's own age. Commvault's listing contains exactly one figure written as years, and it is 25, from the sentence about how long Commvault has been in business. The actual requirement is four years, and it is written as "4 or more years". Any tool that looks for a digit sitting next to the word years walks straight past that phrasing and reports 25. The same trap sits in Smartsheet's advertisement, which prints only "For over 20 years", and in an Appian one at 25. The consequence for you is direct: today the most accessible engineering job on this list was the one that automated filters would rank as the most senior. We read the requirement sentences by hand, which is the only reason it is in the four year group.
- Nothing at one year or less in this edition, the second running, and the floor has risen. We read all 125 genuinely new advertisements and the lowest real bar was four years, twice: Commvault's C++ role and Observe.AI's technical support role. Every mention of one or two years we found was something else, either a secondary skill line on a senior job or a requirement to have managed people. The board itself is a different story, with 20 roles open right now at one year or less, and you can open exactly that slice here: https://www.munotes.in/dailytechjobs?exp=0
- One employer is advertising the same job at two different levels. Okta has a Principal Software Engineer and a Staff Software Engineer listing for its Privileged Access Management product. Both ask for nine or more years of programming, and the bodies are near identical. The only material difference we could find is the database line, where one asks for eight years of PostgreSQL and the other asks for four. If you are in that process, it is fair to ask which requisition an offer would be written against, because the level word usually decides the band.
- Only one genuinely remote role today, and one that only looks remote. Twilio's Staff Software Engineer role is listed as Remote, India, the company describes itself as remote first, and it says plainly that you may occasionally be asked in person for team gatherings or customer meetings. That is an honest statement of a real remote job. Smartsheet's machine learning operations role carries an internal remote tag while its stated location is Bangalore and its body contains no remote policy sentence at all. We published it as Bangalore. If remote is what makes a job possible for you rather than a preference, get it in writing before you invest in the process.
- An advertisement that never says which office you would work in. Everpure tells applicants they are expected to work from the office, but two of its five listings today contain an unfilled template placeholder where the office name should be, so the sentence reads that you will work from the OFFICE_LOCATION office. A third Everpure listing has the same sentence with Bangalore filled in correctly, which is how we know what it should say. We flagged this a day ago and it is still live.
- Two employers publish the thing most employers hide. Fivetran states that its hybrid model is two days in the office each week, with a number rather than a vague word. Everpure's support role states outright that workdays include weekends and that you should expect rotational shifts inside a twenty four by seven operation. Neither is necessarily good news, but both let you decide before you apply rather than after.
- Read the discipline, not just the title. Instawork's role is mechanical engineering for robotics hardware, with CAD, contract manufacture and field repair, and it is not a route into robotics from software. Zscaler's Staff Information Systems Engineer is Google Workspace administration and architecture, not product engineering. MongoDB's Senior Engineer, GTM Tech is Salesforce platform engineering despite a title that reads like sales. All three are genuine technical jobs and all three are commonly misread.
- We drew 38 and published 28, and we would rather say so. Our daily target is a random number between thirty and fifty, drawn before we look at anything. Today's draw was 38. After rejecting internships, sales roles carrying quotas, people management jobs, non technical analytics and one Bangalore advertisement that requires United States citizenship, there were 28 roles we could stand behind. We do not pad a list to hit a number.
- Several roles from one employer. Tekion, Everpure and Okta account for five each, out of 15 employers today. They are separate teams and separate requisitions, not one job posted repeatedly, and where we found an employer running the identical advertisement twice we published it once and said so on the job page.
We read every posting by hand before it goes on this page. The same write-up goes out to the daily email.