No roles match that combination.
New today · September 5, 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.
Added September 4, 2026
Who this is for: a test or quality engineer who wants to work on data correctness and on evaluating an AI agent, rather than on user interface regression suites. What the posting describes: building confidence in the quality, reliability and correctness of data across an enterprise data platform. Working closely with data engineering, product management, analytics and AI teams to define robust validation strategies. Automating testing so data products meet quality standards. As the AI powered Analytics Agent expands, validating user intents, defining evaluation frameworks, and working on the accuracy and consistency of what the agent returns. An honest caveat about this listing: it is one of the thinner advertisements in today's edition. Tekion describes the team and the mission clearly but does not publish a years figure, a named tool list, or an office days policy on this requisition. If the specifics matter to you, and for a testing role they usually do, treat the first recruiter call as the place to establish them. What the title suggests: the two in Software Development Test Engineer II is Tekion's second rung. Across today's Tekion advertisements the same company uses five to seven years for Senior, eight or more for Staff and nine or more for its Staff platform roles, so the two here sits below all of those. That is an inference from the sibling postings, not a figure this advertisement states. Location: listed as Bangalore HQ, which is Tekion's own shorthand for its Bengaluru office. The company does not publish office days on this listing. Experience: not stated anywhere in the posting, so this listing appears in no years band on our filter.
Who this is for: a Java backend engineer with five or more years who has built microservices at scale and wants enterprise domain work. What the posting asks for: a Bachelor's or Master's in computer science or a relevant field. Five or more years of relevant software engineering experience. Excellent Java and object oriented development skills. Experience building and scaling microservices. Strong problem solving, technical troubleshooting and diagnosis. Strong knowledge of both relational and NoSQL databases. Experience developing backends for enterprise systems, with ecommerce, manufacturing and supply chain named as examples. Excellent understanding of debugging, performance and optimisation. Hands on experience with Java, MongoDB, MySQL, AWS, the ELK stack, Spring Boot and Kafka. Experience with large scale cloud native applications. A strong understanding of large language model fundamentals. On the mentoring line: the advertisement says you are expected to be a role model for young engineers with a strong sense of code quality, and to enforce code quality within the team. We read that as senior individual contributor scope. There is no mention of direct reports, hiring or performance reviews anywhere in the posting, which is the line we use to separate an engineering role from a management one. The day to day: backend service work on a platform where the domain is genuinely complicated, and where correctness across dealership operations matters more than novelty. Location: Bangalore HQ, Tekion's Bengaluru office. No office days policy is published on this listing. Experience: five or more years, stated in the qualifications.
Who this is for: a Staff level engineer with nine or more years who has built platform infrastructure, and who has real depth in large language model systems rather than in consuming them. What the posting asks for: a Bachelor's or Master's in computer science or a relevant field. Nine or more years of relevant software engineering experience. A strong sense of ownership and technical leadership. Excellent Java and object oriented development skills. Deep experience building and scaling microservices. Experience developing backends for enterprise systems such as ecommerce, manufacturing or supply chain. Excellent understanding of debugging, performance and optimisation. Experience with Java, MongoDB, MySQL, AWS, the ELK stack, Spring Boot and Kafka. Deep experience in cloud technologies and large scale distributed systems. Deep expertise in large language model systems, including model selection and evaluation. What you would actually own: the technical vision and architecture for the AI native platform layer that other Tekion products build on. Architecting the AI gateway as a highly available, multi provider abstraction over language model vendors. Leading the design of Tekion's Model Context Protocol ecosystem. On leadership: the advertisement asks you to be a role model for engineers, enforce code quality and drive engineering excellence. As with the other Tekion listings, there is no mention of direct reports, hiring or performance management, so we read it as individual contributor scope with architectural authority. Location: Bangalore HQ, Tekion's Bengaluru office. No office days policy is published. Experience: nine or more years, stated in the qualifications.
Who this is for: a kernel or systems engineer who already works in Linux storage or networking subsystems. This is not a role you move into from application development. What the posting asks for: proven expertise in Linux and Unix kernel development and in writing robust device drivers, specifically within storage or networking subsystems. Deep technical command of storage protocols such as NVMe over TCP, RoCE and Fibre Channel, or SCSI including FCP and iSCSI, including experience designing and implementing significant components of those stacks. Demonstrated ability to lead complex engineering projects from conception to delivery while mentoring peers. Expert level debugging of complex system and kernel issues, and a track record of using performance analysis tools to find and remove storage bottlenecks. The office question, and it is a real one: the advertisement says Everpure is primarily an in office environment and that you will be expected to work from a named office, but the name is missing. The sentence contains an unfilled template variable where the location should be. The listing is placed in Bangalore, so that is the reasonable assumption, but the advertisement itself does not say it. Three Everpure listings in today's sourcing carry the same unfilled placeholder. Ask which office and how many days before you go far into the process. Also worth knowing: Everpure renamed itself from Pure Storage and its own advertisements have not fully caught up, so the same posting refers to both names and the recruiting contact address is still the old domain. That is a rename in progress, not a different employer. Experience: no years figure is stated anywhere in this posting, so it appears in no years band on our filter. The nature of the work implies real seniority.
Who this is for: a backend engineer with seven or more years, ideally in Go, who wants distributed systems and infrastructure rather than product features. What the posting asks for: a BS in computer science. Seven or more years designing, developing and testing enterprise products, with Go preferred. A good understanding of microservice architectures and cloud native platforms. Experience designing and owning microservices that operate and scale in a distributed architecture reaching thousands of nodes. Expert debugging skills and the ability to work through ambiguous problems at scale in public and private cloud environments. Experience working with multiple stakeholders, from product management through to customer beta partners, in designing highly scalable production quality software. Proven design sensibility and willingness to work in a collaborative team environment. A solid computer science background in data structures, algorithms and software design. On the title: it reads Member of Technical Staff, Backend Engineering Lead. Everpure uses Member of Technical Staff as its actual engineering level and appends a descriptor, and across its eleven live advertisements that same title spans three to eight years. Nothing in this requirement list involves managing people, so read Lead as technical ownership of a component. The office reality: the advertisement states plainly that you must be willing and able to work in an open office environment. Everpure describes itself as primarily an in office employer. The listing is placed in Bangalore. Experience: seven or more years, stated in the requirements.
Who this is for: an experienced support or escalation engineer who is genuinely technical and is comfortable being the person a large angry customer is escalated to. It is a named reader request on this board, so it is worth saying clearly that this is a customer facing role, not a product engineering one. What the posting asks for: end to end technical troubleshooting and root cause analysis across multi vendor environments, covering Linux and Windows administration, cloud architecture on AWS, REST API services, virtualisation with VMware and Hyper V, and enterprise storage protocols including NFS, S3 and SMB. An in depth understanding of enterprise networking and systems architecture with hands on proficiency in DNS, HTTP, SSL and TCP over IP, and the ability to diagnose complex networking, replication, performance and capacity problems. Exceptional customer crisis management, including leading multi stakeholder technical calls, de escalating high pressure situations and turning complex engineering concepts into concise communication. A commitment to peer mentorship and to creating knowledge base content. What the job is really like: escalation work is reactive by nature and the pressure is real. The upside is unusually deep exposure to how enterprise systems fail, which is why people who have done it well tend to move into reliability or solutions architecture afterwards. Location: Bangalore. Everpure describes itself as primarily an in office employer, though this particular listing does not state a number of days. Experience: no years figure is stated anywhere in this posting, so it appears in no years band on our filter.
Who this is for: a detection engineer or threat researcher who already owns a domain and wants formal accountability for it, rather than working through someone else's backlog. What the posting asks for: deep detection experience in at least one of endpoint and managed detection, cloud and SaaS, identity, email or SIEM, plus the judgement to own that area. A track record of owning technical work end to end and being answerable for its quality without much oversight. A strong grasp of how attackers actually operate, and fluent use of MITRE ATT&CK to decide where coverage belongs. Detection as code as your existing way of working, meaning version control, code review and controlled deployment through Git and CI and CD. A foundational understanding of AI and machine learning technologies and experience using or securing AI driven solutions in your domain, which Zscaler now puts in the minimum qualifications on most of its advertisements. Preferred rather than required: experience using AI driven automation, large language models or machine learning to speed up detection engineering and threat analysis, and programming or scripting in Python, Go or Ruby. The day to day: taking complete accountability for a coverage domain's health, backlog and performance, being the point of contact for its efficacy, and personally solving the hardest detection problems so the rest of the team has patterns to follow. Location and working pattern: this is a hybrid role in Pune, stated in the advertisement, reporting into the Threat Hunting department. Zscaler publishes a hybrid working model and benefits page but does not put the number of office days on this particular listing. Experience: no years figure is stated anywhere, so this appears in no years band on our filter.
Who this is for: someone from a customer facing technical consultancy or success background in cybersecurity who wants strategic enterprise accounts rather than a ticket queue. This is a directly requested category on this board. What the posting asks for: experience in a customer facing technical consultancy or success role within cybersecurity. A proven track record of executive stakeholder management, strategic customer engagements, and conveying complex technical concepts clearly. Hands on experience analysing technical environments, working across functions and troubleshooting critical customer escalations. A background in data modelling methodologies, SQL or ETL within technical or security domains. A Bachelor's degree in computer science, engineering or a related technical field. Demonstrated curiosity about AI tools and a history of integrating new technology into daily workflows. Preferred rather than required: deep domain expertise in vulnerability management programmes, enterprise risk scoring and security operations. On the job title, because it matters: Manager here refers to managing an account relationship. The posting reports into a Manager of Technical Success Management, and contains no direct reports, no hiring and no performance management. We publish roles like this because readers asked for them, and we exclude genuine people management roles, so the distinction is worth being explicit about. What it is not: this is a post sales technical role. It is not a quota carrying sales job, and the advertisement contains none of the sales target language that gets other listings excluded from this board. Location and working pattern: Bangalore, stated as hybrid. The number of office days is not published on the listing. Experience: no years figure appears anywhere in this posting, so it sits in no years band on our filter.
Who this is for: a cloud or infrastructure security engineer with five to seven years who works across all three major clouds and is comfortable owning identity and secrets infrastructure. What the posting asks for: five to seven years of experience, stated plainly. Hands on experience with Terraform and Ansible. A strong understanding of identity protocols including SAML, OAuth2, OIDC, LDAP and Kerberos. Experience with Azure AD and Entra ID, AWS IAM and GCP IAM. Expertise in HashiCorp Vault, Azure Key Vault and AWS KMS. Proficiency in Kubernetes RBAC, secrets management and workload identity management. A solid understanding of PKI, TLS certificates and cryptographic primitives. Strong Linux administration on RHEL, CentOS or Rocky Linux. Familiarity with firewall technologies, Fortigate in particular, covering firewall, NAT, VPN, IPS and URL filtering, and cloud security controls across Azure, AWS and GCP. Desirable rather than required: certifications in Azure Security Engineer, AWS Security or GCP Security, a network security certification such as Fortinet NSE4 or above, and the AWS Security Speciality. What to expect on working pattern: HighRadius is unusually direct about office attendance across its advertisements, and a sibling listing in today's edition puts five days a week in the office in bold. This particular advertisement does not repeat it, so confirm it for this specific requisition rather than assuming either way. Location: Hyderabad, Telangana. Experience: five to seven years, stated in the required skills section.
Who this is for: a DevOps or platform engineer with five to eight years who genuinely enjoys infrastructure as code, and who can work five days a week from an office in Hyderabad. What the posting asks for: expert level Terraform including HCL, state management, workspaces and reusable module development. Strong hands on experience with AWS, Azure or GCP covering VPC, IAM, compute, RDS and S3. Proficiency in Kubernetes and Docker, including writing Dockerfiles and managing manifests and Helm charts. Advanced scripting in Python, Bash or Go for automation. Expert knowledge of Git including branching strategies and GitOps workflows. Experience with build tools such as Maven or Gradle for Java, Node and Python environments. The ability to debug complex networking or deployment problems in a distributed system. The scope boundary, in the ad's own words: this role focuses strictly on provisioning, configuration management and CI and CD pipelines. If you want a role that also carries product reliability and incident ownership, this specific listing is narrower than that, which may be exactly what you want or exactly what you do not. The office policy: the advertisement states the work mode as five days working from office, and puts it in bold in its own text. Very few employers on this board publish attendance at all, so we surface it rather than leaving you to find out at offer stage. Location: Hyderabad, Telangana. Experience: five to eight years, stated as the experience level in the posting body.
Who this is for: a backend or platform engineer who works in Go or Rust and wants event driven, security sensitive infrastructure rather than product feature work. What the posting asks for: strong backend engineering in Go or Rust, with the advertisement stating directly that the team is moving away from Java heavy backgrounds for new platform work. Experience building event driven systems with Kafka, event sourcing patterns and at least once delivery guarantees. Familiarity with Temporal or another durable workflow engine. Experience with identity and access management systems covering OAuth 2.0, OIDC, token lifecycle management and fine grained authorisation models. A solid understanding of encryption patterns including envelope encryption, key hierarchy design and KMS integration. Comfort operating in multi tenant regulated environments where correctness and audit evidence are not negotiable. Strong observability instincts covering structured logging, distributed tracing and metrics. Preferred rather than required: experience with Zitadel, Keycloak or similar identity providers, and with ClickHouse or another columnar append only store. Why the Java sentence is worth taking seriously: most advertisements list preferred languages and quietly accept adjacent ones. This one states a direction of travel. Read it as a genuine filter rather than a preference, and if you are a Java engineer moving toward Go, say so explicitly in your application rather than hoping it is not noticed. Location: Pune. No office days policy is published on this listing. Experience: Kaseya publishes no years figure on this advertisement, so it appears in no years band on our filter. The Staff title and the scope of the surface imply real seniority.
Who this is for: a systems engineer who works close to the operating system and has built or operated isolation infrastructure. The pool of people who match this honestly is small, which is worth knowing in both directions. What the posting asks for: deep Linux systems experience across iptables and netfilter, process namespaces, cgroups, socket options and Unix domain sockets. Experience with at least one sandboxing or isolation technology, naming gVisor, Firecracker micro virtual machines, WebAssembly runtimes or equivalent. Strong networking fundamentals including the TCP and IP stack, transparent proxying, and TLS termination and origination. A language agnostic mindset, since you would design platforms other languages run on rather than systems tied to one runtime. Comfort working close to the operating system with memory management, process lifecycle and privilege separation. Go or Rust strongly preferred, with C and C plus plus experience relevant. Familiarity with SPIFFE or SPIRE or similar workload identity frameworks is called a strong plus. Preferred rather than required: experience building or operating multi tenant container or virtual machine isolation infrastructure, and prior work in security tooling, endpoint detection and response, or zero trust networking. On the title: Kaseya calls this Staff Systems Engineer, while the body calls the role an Intelligence Systems Engineer. The body is the more specific description of the work, and the two do not conflict about the level. Location: Pune. No office days policy is published on this listing. Experience: no years figure is stated anywhere, so it appears in no years band on our filter.
Who this is for: a DevOps, SRE or platform engineer with eight to twelve years whose Linux administration is genuinely deep, not just enough to use the tooling. What the posting asks for: eight to twelve years in DevOps, platform engineering, Linux administration or site reliability engineering. Strong Linux system administration expertise covering performance tuning, kernel parameters, storage and filesystem management, process management, system troubleshooting and networking fundamentals. Hands on experience managing Kubernetes clusters in production. Strong knowledge of infrastructure as code using Terraform or Pulumi. Experience designing and maintaining CI and CD pipelines with GitHub Actions, Jenkins, ArgoCD or equivalent. Experience with monitoring and observability using Prometheus, Grafana, Datadog or ELK. Strong scripting in Shell, Python or Go. Experience managing production incidents, on call support, alert tuning and operational excellence. A strong understanding of DNS, load balancers and firewalls. What the domain adds: backup and disaster recovery is a workload where storage behaviour and filesystem performance are the whole game, which is why the Linux requirement here is written more specifically than the usual DevOps list. If your background is Kubernetes and pipelines but thin on the operating system underneath, this listing will find that out. On call: the posting names production incident management and on call support as part of the role. Ask what the rotation looks like before offer stage. Location: Pune. No office days policy is published on this listing. Experience: eight to twelve years, stated in the required skills.
Who this is for: a test automation engineer roughly two to four years into their career. This is the lowest experience bar in today's edition, and we want to be straight about what that means: it asks for two or more years of relevant experience, so it is an early career role rather than a first job. Nothing in today's sourcing asked for under two years. What the posting asks for: a Bachelor's degree in a related field or equivalent business experience, and two or more years of relevant experience. Strong proficiency in Python or Ruby, with experience writing and maintaining automated tests using behaviour driven development frameworks such as Behave. Solid experience with Git version control including branching strategies, pull request workflows and managing Git submodules. Hands on experience integrating, executing and troubleshooting automated test suites within pipelines, specifically Jenkins or GitLab Runners. Practical experience interacting with, configuring or managing virtualised environments, particularly VMware ESXi. Solid knowledge of Linux, Windows and macOS including basic system administration and command line usage. Working knowledge of IP networking including TCP and IP, routing and subnets, and an understanding of basic firewall configuration. The ability to work independently on projects. What makes it a good early career role: the technologies named are ones you can learn and demonstrate on your own, and the mix of automation, virtualisation and networking is unusually broad for a role at this level. That breadth is worth more than the title. Location and working pattern: Pune, with the working condition stated as hybrid in the advertisement. Experience: two or more years, stated in the experience recommendations.
Who this is for: an engineer with eight or more years who is comfortable joining on the strength of the level and the company rather than a detailed technical brief. What the posting asks for: a Bachelor's degree in a related field or equivalent business experience, and eight or more years of relevant experience. The ability to manage projects and processes independently with limited supervision. Advanced knowledge of the applicable work area. The ability to adapt to new technology and processes as business requirements change. Knowledge of a variety of the field's concepts, practices and procedures. The ability to work constructively and independently under pressure in a fast paced, multitasking environment. The ability to manage competing priorities while producing high quality work. Strong verbal and written communication. Strong organisation and time management. Strong knowledge of programming languages and software basics, and of relevant development tools including version control. Our honest read: this is a thin advertisement for a principal level role. The technology names appear in the surrounding text rather than in the requirements, so we have listed them as context, not as a specification. There is nothing wrong with the role, but you will learn more in twenty minutes with the hiring manager than the posting tells you. What we can say concretely: ConnectWise serves roughly 45,000 partner businesses, so the systems are multi tenant and operate at real scale, and the Pune office runs engineering rather than only support. Location and working pattern: Pune. The sibling ConnectWise listing in today's edition states hybrid working conditions. Experience: eight or more years, stated in the experience recommendations.
Who this is for: an integration or enterprise applications engineer with eight or more years who understands finance systems and is comfortable working inside an audited environment. What the posting asks for: eight or more years in software engineering, integrations or enterprise applications. A strong finance systems background with hands on experience supporting and modernising finance business processes. Deep expertise in APIs, middleware, event driven architectures and enterprise integration patterns. Proven experience delivering AI, automation or intelligent process transformation. A solid understanding of SOX, audit, cybersecurity awareness and internal controls in an enterprise environment. A foundational understanding of AI and machine learning technologies and experience using or securing AI driven solutions, which now appears in the minimum qualifications on most Zscaler advertisements. Preferred rather than required: hands on experience with NetSuite, Workday, FloQast and Workiva. Being honest about what this is: enterprise systems engineering has a reputation problem among product engineers, and some of it is deserved. The compensating advantages are that the domain is genuinely intricate, the systems are business critical so quality is taken seriously, and the skills transfer across every large company. If the phrase internal controls makes you switch off, this is not your listing. Location and working pattern: Bangalore. Zscaler operates a hybrid model and links to its policy from the advertisement, but does not state the number of office days on this listing. Experience: eight or more years, stated in the minimum qualifications.
Who this is for: an engineer with five or more years who wants deep database and distributed systems work in a customer facing shape. This is one of the technical support and customer success roles readers of this list asked for by name. What the posting asks for: five or more years of proven experience, with the advertisement adding that MongoDB considers all candidates and looks particularly for people who are self taught and curious. The ability to work alongside the company's largest customers, resolving questions on architecture, performance, recovery and security. Expertise, or the ability to build it, in best practices for running MongoDB at scale. Comfort operating across Linux, the major clouds, containers, and the application languages customers build in. What the ramp actually looks like, because MongoDB publishes it: the advertisement sets out success measures. At three months you are expected to have a deep understanding of MongoDB and its ecosystem and to have completed new hire training. At six months you should be comfortable working directly with customers and to have completed the MongoDB Certified DBA Associate exam. At twelve months you would be working toward expertise within a technical specialism. Very few employers publish a ramp this explicitly, and it is a fair signal that the onboarding is real. One clarification: the six and twelve month figures above are onboarding milestones, not experience requirements. The requirement is five or more years. Location and working pattern: MongoDB states it is looking to speak to candidates based in Gurugram for its hybrid working model, so this is a location specific hybrid role rather than an all India one. Experience: five or more years, stated in the requirements.
Who this is for: an SAP developer with six or more years who wants to work where SAP meets a modern data platform, rather than in a traditional ERP consultancy. What the posting asks for: six or more years of SAP development experience with hands on delivery of at least one end to end SAP solution, an S4HANA extension named as an example. Domain knowledge in finance, procurement or supply chain that speeds up requirements understanding. Experience extending or customising Joule agents through SAP Build or Joule Studio, or building agents on SAP AI Foundation. Experience building applications on modern data platforms such as Databricks that extend or sit alongside SAP. Cloud native experience including containerisation and Kubernetes through Kyma, observability and scalability patterns. SAP certification in ABAP, SAP BTP or SAP Build, and prior work in a high growth technology company. What you would actually build: side by side extensions on SAP BTP, event driven integrations into the Lakehouse using OData and REST, IDoc, Cloud Integration and Event Mesh across a hybrid landscape, and AI assisted workflows over finance processes. Why the combination is worth noticing: SAP roles and modern data platform roles usually sit in different companies and different career tracks. This one is inside a data platform vendor, so the ERP work is expected to integrate with a Lakehouse rather than stay in its own world. If you have been trying to move an SAP background toward data engineering, this is an unusually direct route. Location: Bengaluru. No office days policy is published on this listing. Experience: six or more years, stated in the qualifications.
Who this is for: a backend or infrastructure engineer with seven or more years who wants to work on telemetry, metrics and diagnostic systems at large scale. What the posting asks for: seven or more years of production level experience in at least one of Python, Java, Scala, C plus plus or a similar language. The advertisement leads with the production qualifier, which matters: this is a role about systems that are already carrying load, not about building something new in isolation. What observability work involves in practice: building and running the systems that collect, store and query metrics, logs and traces for a platform that thousands of organisations depend on. The engineering difficulty is usually volume and cardinality rather than logic, and the constraint is that your systems have to stay up precisely when the platform is having its worst day. If you have run into the limits of an off the shelf monitoring stack and enjoyed the problem, this is the job shape that follows. About the employer: Databricks states that more than 20,000 organisations rely on its Data and AI platform, including around 70 percent of the Fortune 500. Scale is genuinely part of the role rather than a recruiting line. Being honest about the advertisement: it is lighter on named tooling than most listings in today's edition. The experience requirement is unambiguous, but the specific stack is worth asking about in the first conversation. Location: Bengaluru. No office days policy is published on this listing. Experience: seven or more years, stated in the requirements.
Who this is for: a full stack engineer with eight or more years whose centre of gravity is the front end, and who wants a product where the interface is the operational tool rather than a marketing surface. What the posting asks for: eight or more years of full stack software development experience. Expertise in JavaScript. Experience with HTML5 and CSS3 and modern component frameworks. Experience developing reusable user interface components in React, Angular 16 or later, JavaScript and HTML5 with CSS3. The ability to work in the web interface backend to support application service features, so this is not a purely client side role. Responsibility for making sure the interface works seamlessly across browsers, and for keeping up with web technologies the product might adopt. A levelling note worth knowing about this employer: Netskope states on several of its advertisements that the team hires across all levels and that candidates are individually assessed and appropriately levelled. That has appeared consistently on its postings over several months. It means the eight year figure on this listing is the stated floor for this title rather than a hard wall, and that a strong candidate slightly under it is usually levelled rather than rejected outright. We still publish the stated figure, because that is what the advertisement says. About the odd title: the listing carries a name in brackets, which is an internal hiring manager reference that Netskope has left in the public title. It is not part of the role. Location: listed as India, without a city. Netskope does not state a remote policy on this advertisement, so confirm the working location before assuming it is flexible. Experience: eight or more years, stated in the required skills.
Who this is for: a principal or architect level engineer with fifteen or more years who has owned the architecture of a high throughput data plane. What the posting asks for: fifteen or more years of overall experience, including eight or more years in the relevant specialism. The ability to set and drive overall architectural design and strategic technical direction for the Secure Web Gateway team. Experience understanding requirement specifications and designing and implementing high quality features with reliability, sustainability, scalability and observability for a data plane. Experience building sophisticated key management algorithms. The ability to work with product management to understand customer requirements and provide architectural guidance, and to provide technical leadership to other engineers. What data plane work means here: a secure web gateway sits in the path of customer traffic, so latency, throughput and failure behaviour are not quality attributes bolted on afterwards, they are the product. Engineers who have worked on proxies, network middleboxes or high performance traffic processing will recognise the shape immediately. On the levelling caveat: Netskope states across its advertisements that its teams hire across all levels and that candidates are individually assessed and appropriately levelled. We publish the fifteen year figure because the advertisement states it, but that standing sentence is a real signal that the number is a floor for the title rather than an absolute cut off. On management: despite the technical leadership language, this posting contains no direct reports, no hiring and no performance management. We exclude genuine people management from this board, and this listing does not cross that line. Location: listed as India, without a city, and no remote policy is stated. Confirm the working location. Experience: fifteen or more years, stated in the required skills.
Who this is for: a developer with three or more years in C sharp who wants systems level work, and who is comfortable that this is infrastructure software rather than web or application development. What the posting asks for: three or more years of software development experience. Proficiency in C sharp as the primary language, with good knowledge of C plus plus. Strong fundamentals in data structures, algorithms and object oriented design. Experience designing, developing, testing and maintaining software in C sharp and .NET. The ability to build efficient, scalable and reliable solutions. Experience with multithreaded and concurrent applications. The ability to debug complex software issues. Why the language pairing matters: C sharp with C plus plus underneath is a specific combination, common in enterprise infrastructure products where a managed layer sits over performance sensitive native code. If you have only ever worked in web focused .NET, the C plus plus expectation is the part to prepare for. A detail Commvault includes that almost nobody else does: the company opens its advertisements with a recruitment fraud warning. It states that scammers impersonate its recruiters and leadership by email and text, that it never conducts interviews solely by email or text message, and that it never asks for banking details before your first day. That is good advice for any application you make anywhere, and it is worth repeating: no legitimate employer needs your bank details to make you an offer. Location: listed across Bangalore, Hyderabad and Pune. The advertisement does not state office days. Experience: three or more years, stated in the requirements.
Who this is for: a systems engineer with six or more years in Rust, Go or another performance oriented language who wants database internals and open source work. What the posting asks for: six or more years of software engineering experience with strong systems level skills. A strong programming background in Rust, Go, C plus plus or similar performance oriented languages. Experience designing or maintaining SDKs, libraries, connectors, or compute and data integration codebases. Exposure to data warehouses, query engines, Arrow and columnar ecosystems, or execution runtimes. A desire to build foundational platform components other teams and community members depend on. Comfort working in public code review loops, asynchronous first communication and collaborative RFC processes. A mindset grounded in debuggability, reliability and ownership in ambiguous problems. It separately mentions two or more years working in open source, SDK, runtime or low level integration environments, which is a narrower sub requirement and not the overall bar. Why we publish six rather than two: an automated reader taking the smallest figure in this advertisement returns two years. The qualifications line says six or more years of software engineering with strong systems level skills. We publish six, read by hand. An edge rather than a requirement: contributions to or interaction with Arrow, ADBC, DuckDB, Presto, DataFusion, Spark or ClickHouse, experience shaping adapter or plugin standards and driver contracts, and familiarity with the Rust async ecosystem. One thing to know about the employer: the advertisement says you may see references to both Fivetran and dbt Labs during recruiting, because the teams and systems are being integrated. That is expected, not a red flag. Location: Bengaluru, Karnataka. The listing carries an internal remote tag, but no remote policy sentence appears in the text, so treat the location as the office and confirm. Experience: six or more years.
Who this is for: an engineer who wants MLOps and platform work rather than model research, and who can work hybrid in Bangalore. What the posting describes: designing and overseeing the strategy and architecture of scalable AI and machine learning operations platforms and pipelines. Packaging and deploying models to production so they are reproducible and interpretable. Designing automated CI and CD pipelines to speed up model deployment. Provisioning and optimising infrastructure for training and serving using Docker, Kubernetes or serverless platforms. Implementing post deployment monitoring for model performance, data drift and latency, with Monte Carlo named as preferable. Automating retraining and data pipeline workflows. Managing the deployment of foundation models, fine tuning workflows and retrieval augmented generation stacks including vector databases and knowledge graphs, with AWS Bedrock preferred. Managing GPU and CPU utilisation to minimise cloud cost while keeping inference latency low. Versioning data, code and models with tools such as MLflow. Implementing data security measures and data governance compliance. The location contradiction, and why we are flagging it: the advertisement carries the internal tag LI-Remote, while the job title itself says Hybrid in Bangalore. Two other Smartsheet listings in today's sourcing carry the same remote tag, and one of those also says Hybrid in its own title. The tag and the title cannot both be right. We have published this as hybrid in Bangalore, because the title is the more specific statement and because it is the one that would actually govern your working week. If remote is what makes a job possible for you, confirm it in writing before you invest in the process. Experience: Smartsheet publishes no experience requirement anywhere in this advertisement. The only years figure in the text is the company saying it has been going for over twenty years, which is not a requirement. So this listing appears in no years band on our filter, and the II in the title is the only level signal given.
Who this is for: a platform or site reliability engineer with eight or more years who writes real code and wants to build tooling other engineers use, rather than to service requests. What the posting asks for: eight or more years in platform engineering, infrastructure engineering, DevOps or SRE roles, with real ownership of production cloud infrastructure. Strong software engineering skills in Go or Python, with the advertisement stating you should write tested, maintainable code and treat infrastructure automation as software rather than scripting. Deep hands on Kubernetes experience in production covering workload scheduling, networking, autoscaling and upgrades. Infrastructure as code tooling such as Terraform, Pulumi or OpenTofu. Solid experience with at least one major public cloud, with experience across AWS, GCP and Azure called a strong plus given the multi cloud footprint. A track record of building tools or platforms other engineers use, naming internal CLIs, provisioning frameworks, self service portals and automation pipelines, and stating explicitly that maintaining existing infrastructure is not the same thing. On mentoring versus managing: the posting mentions leading, mentoring and technically guiding a team of junior and early career platform engineers. There are no direct reports, no hiring and no performance management anywhere in the advertisement, so we read this as senior individual contributor scope with technical guidance attached. The operational reality: it names deep operational ownership including being on call and root causing incidents, and describes a bias toward automating recurring problems away rather than repeatedly firefighting them. Location: listed as India without a city. Skyflow mentions a work from home expense in its benefits but states no remote working policy anywhere in the advertisement, so we have not described this as a remote role. If that is what you need, confirm it explicitly. Experience: eight or more years, stated in the requirements.
Who this is for: a mobile or desktop engineer with nine or more years who has shipped production applications and wants to work on the client layer of AI products under real Indian network conditions. What the posting asks for: nine or more years building production mobile or desktop applications that real users depend on, with strong ownership of what you shipped. Deep Kotlin expertise in production including coroutines, flows and modern Android architecture, plus comfort with Swift on iOS and at least one desktop platform among Windows, Linux and macOS. Hands on Kotlin Multiplatform experience on a shipped or in production product, specifically designing shared modules, managing expect and actual boundaries, and dealing with the real friction of sharing code across mobile and desktop. A strong command of native audio and streaming pipelines covering audio capture, playback, buffering, voice activity detection, codec handling and low latency streaming to and from model endpoints. Experience shipping applications that work in constrained environments, described as offline first, low bandwidth and low memory, and the advertisement adds pointedly that working on a flagship device over fibre is not the same thing. What you would own: the client application layer across mobile and desktop for Sarvam's consumer and enterprise products, named in the advertisement as Indus and Kivi and whatever follows them, with Kotlin Multiplatform as the unifying approach. The posting also asks you to mentor engineers across the client team on platform native depth and Kotlin Multiplatform discipline, which is technical mentorship rather than management. Why the constraint is the interesting part: most mobile listings describe features. This one describes an environment, and building for the bottom of India's hardware and network range is a genuinely harder engineering problem than building for the top of it. Location: Bengaluru. No office days policy is published on this listing. Experience: nine or more years, stated in the requirements.
Who this is for: an experienced test engineer who wants infrastructure and cloud platform testing, and who already uses AI tooling as part of how they work. The requirement worth reading first: Druva lists, under must have skills, that the engineer must demonstrate proficiency in using AI for routine tasks, including generating functional test cases from specifications or precise prompts and then automating those test cases using AI. That is not a bonus line on this advertisement, it sits in the must have section. Several employers in today's edition have moved AI tooling from the nice to have list into the requirements, and this is the most explicit example. What else the posting asks for: knowledge of Docker, Linux and Windows. A good grasp of networking and cloud architecture fundamentals, preferably with exposure to AWS or Azure networking, storage and compute. Proficiency in Python or Java, with Python preferred, and strong shell scripting. Hands on experience with SQL databases. Strong experience in REST API testing and backend automation. Experience in user interface automation, with Selenium or Playwright preferred. Proficiency with Git, Jira, XRay and Jenkins. Strong analytical and debugging skills. Exposure to load and performance testing. The day to day: independently creating comprehensive feature test plans aligned with development milestones, leveraging and extending automation frameworks, owning the complete test execution cycle for user stories, performing a mix of automated, manual, white box and black box testing, creating and documenting testbed setups, and reporting and tracking issues. Location: Pune, Maharashtra. No office days policy is published on this listing. Experience: Druva states no years figure anywhere in this advertisement, so it appears in no years band on our filter. The Senior Staff title is the only level signal given, and at most employers that sits well above mid level.
Who this is for: a backend engineer with seven or more years who wants senior individual contributor work on large scale systems. What the posting asks for: seven or more years of experience. Strong experience with high level and low level design for large scale systems. Proficiency in Java, Python or C plus plus. Expertise in data structures, algorithms and design patterns. Hands on experience with microservices architecture, RESTful APIs and cloud platforms across AWS, Azure or GCP. Knowledge of SQL and NoSQL databases and caching mechanisms. 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 and CD pipelines, Docker and Kubernetes. The duplicate requisition: HighRadius has this same description live under the title Software Development Engineer IV as well, and the two bodies are identical. We publish one of them. If you find the other one yourself, applying to both gets you nothing extra, and it is worth asking the recruiter which requisition is actually open and funded. On mentoring: the advertisement asks you to mentor and guide junior engineers on design and coding standards. There are no direct reports, no hiring and no performance management in the posting, so this is senior individual contributor scope. Working pattern: HighRadius advertisements in today's edition state five days from the office on at least one sibling role. This listing does not state its own policy, so confirm it directly. Location: Hyderabad, Telangana. Experience: seven or more years, stated in the required skills.
Who this is for: a backend or platform engineer with seven or more years who wants to work on machine learning systems without necessarily having held a machine learning job title. What the posting asks for: seven or more years of industry experience in backend or platform engineering or equivalent, with a BE or BTech preferably in computer science or an equivalent qualification. Experience in applied machine learning is stated as a plus, not a requirement, which is the detail worth noticing. Strong programming in Python, Java or equivalent, with data structures and algorithms and solid data engineering foundations. An understanding of machine learning best practices, with the advertisement naming training and serving skew minimisation, A and B testing, feature engineering and model and feature selection. Why that framing matters: most machine learning adjacent listings demand machine learning experience outright, which shuts out backend engineers who have built the systems around models without owning the models. This one inverts it, asking for backend and platform depth first and treating applied machine learning as an advantage. If you have built feature pipelines, serving infrastructure or experimentation systems, read this listing properly rather than filtering it out on the AI and ML in the title. What the domain involves: trust and safety work means detection systems where false positives harm legitimate users and false negatives cause real damage. Engineers who like problems with genuine consequences and measurable trade offs tend to find it more interesting than growth work. One caution about this employer: Airbnb has appeared on this board before with roles that were withdrawn and re opened under new requisition identifiers inside a week. This listing was verified live today, but apply promptly rather than sitting on it. Location: Bangalore, India. This is an India based listing, not one of Airbnb's United States remote roles. Experience: seven or more years, stated in the expertise section.
Who this is for: a test automation engineer with five or more years who has tested Salesforce specifically, and who works in Playwright rather than only Selenium. What the posting asks for: five or more years of quality assurance automation experience. Strong hands on Salesforce testing across Sales Cloud, Salesforce CPQ, Revenue Cloud and Service Cloud, with Commerce Cloud preferred. Strong experience with Playwright automation using TypeScript or JavaScript. Experience building and maintaining automation frameworks from scratch. A solid understanding of Salesforce business processes and end to end testing. Strong experience with REST API testing using Playwright or Postman. Proficiency in JavaScript or TypeScript and working knowledge of Java or Python. Experience with CI and CD tooling such as Jenkins, GitHub Actions, Azure DevOps or GitLab. Experience with Git and version control best practice. Strong analytical, troubleshooting and debugging skills. Good to have rather than required: experience with AI powered testing tools. A verification note, since this board promises every link is checked: ZoomInfo's careers site returns an automated blocking response to scripted requests, so the direct page could not be confirmed by our usual method. This posting was verified live through the underlying applicant tracking system interface instead, which returned the role as open with the title and the Bengaluru location intact. The apply link is the employer's own canonical one and will open normally in a browser. We would rather tell you how a listing was checked than quietly skip the check. Duplicate listing note: ZoomInfo has the identical job description live for Chennai as well as Bengaluru. They are the same role in two cities, so pick the one you can actually work from. Location: Bengaluru, Karnataka. Experience: five or more years, stated in the must have section.
Who this is for: a backend engineer who has already shipped and supported production services and wants remote work without leaving India. What the posting asks for: professional experience building and shipping production backend applications, with real fundamentals in programming, APIs, databases, testing, debugging and performance. Experience with Ruby on Rails or Go, though the advertisement says plainly that it values the ability to learn a language over mastery of one. The ability to take a feature from clarification through delivery and follow up, working independently and asking for input at the right moment. Sound judgement about security, reliability, performance, maintainability and operational risk, and an understanding of modular backend boundaries and what coupling costs you later. One requirement worth reading twice: GitLab lists AI fluency as a requirement, not a bonus. It asks for practical experience with AI coding tools including the ability to review and correct what they generate. Several employers now do this, and it has moved from the nice to have list into the requirements list over the last month. The day to day: working inside one product area, partnering with product management, frontend, infrastructure and security, and contributing to the quality of shared backend code rather than only your own corner. Location and working pattern: the advertisement says all GitLab roles are remote, and adds that some roles carry location based eligibility requirements, so confirm India eligibility with the recruiter. Communication is asynchronous and written, which suits some people and genuinely does not suit others. Experience: GitLab states no years figure anywhere in this posting, so this listing appears under no years band on our filter. Read the level word instead. Intermediate at GitLab sits above entry level and below senior.
Who this is for: a senior backend engineer who has designed systems rather than only built inside them, and who has genuinely shipped an agentic AI system into production rather than prototyped one. What the posting asks for: deep backend expertise across architecture, APIs, data systems and performance tuning in a complex product or service environment. Proficiency in modern backend languages and a deep understanding of systems programming, with the ad again saying it values adaptability over mastery of one language. Architectural judgement, specifically experience designing or evolving modular backend boundaries, bounded contexts and migration safe architectures. The ability to lead through influence and clear written communication rather than authority. The requirement most candidates will screen out on: proven experience building or operating agentic systems in production. The advertisement is unusually specific that prompt engineering does not count, and names architecting loops, tool use and error handling strategies that ensure reliability at scale. The day to day: working across product, frontend, infrastructure, data and security boundaries, making architectural trade offs, and helping define standards for a high scale global product. The ad frames it as moving beyond assigned work to actively improving reliability and performance. Location and working pattern: all GitLab roles are remote, with the caveat that some carry location based eligibility requirements. Asynchronous written communication is central to how the company operates, not an afterthought. Experience: no years figure is published anywhere in this posting, so it sits in no years band on our filter. The title is the only level signal GitLab gives you.
Who this is for: a release or DevOps engineer with seven or more years behind them who has run deployments for enterprise SaaS platforms, not only for a product codebase. What the posting asks for: a Bachelor's degree in computer science or information systems, or equivalent practical experience. Seven or more years in release engineering, DevOps or a related discipline. Experience with releases and deployments for enterprise SaaS applications such as Salesforce, Zuora or comparable business systems. Strong hands on experience designing and operating GitLab CI and CD pipelines, or a comparable system, in production. Proficiency in at least one scripting language, Python named specifically, with the ability to write maintainable automation and integrations. Experience with source control, branching and merging strategies, artifact management, automated testing, deployment orchestration and rollback. The mandatory AI clause: the advertisement states that hands on experience using AI assisted development and automation tools such as Claude, or comparable enterprise approved tools, is mandatory as part of day to day DevOps and release engineering work. It is listed among the requirements, not among the bonuses. If you have not used these tools in a working context, this specific listing will screen you out. The day to day: standardising how business critical enterprise platforms get released, building the tooling other engineering teams use to ship, and putting operational controls and governance around changes that touch revenue systems. Location and working pattern: all GitLab roles are remote, subject to location based eligibility that the recruiter can confirm. The company runs asynchronously and in writing. Experience: seven or more years, stated plainly in the posting, which makes this the rare GitLab advertisement that publishes a figure at all.
Who this is for: an engineer with five or more years who enjoys internal platform and integration work, and who is comfortable that this is enterprise automation rather than product engineering. What the posting asks for: five or more years in software engineering, enterprise automation, platform engineering, DevOps, integration engineering or a related field. Proven experience building production grade automation that removes manual operational or development work. Strong programming in Python, JavaScript or TypeScript, Node.js, Java or similar. Experience with REST APIs, webhooks, OAuth, event driven workflows, asynchronous processing and SaaS integrations. Experience with Git and GitHub, CI and CD pipelines, automated testing, release engineering and environment management. Experience with at least two enterprise platforms, preferably including Salesforce, NetSuite, AEM, Boomi or Okta. Hands on Salesforce work with Apex, SOQL and SOSL, Flows, the Salesforce CLI, metadata APIs and platform security. The title problem, stated plainly: the listing is titled Senior Software Engineer and the first line of the body says the company is looking for a Senior Automation Engineer. The requirements are automation and integration requirements throughout. This matters for levelling and for what your next role looks like, so raise it with the recruiter early. The day to day: reducing manual operational work across Okta's internal enterprise systems, building reusable integration patterns, and improving developer productivity for teams that are not your own. Location: Bengaluru. Okta does not publish an office days policy on this advertisement, so ask. Experience: five or more years, stated in the requirements.
Who this is for: a backend engineer with five or more years in Java or Go who wants identity and access work, and who is comfortable owning infrastructure alongside code. What the posting asks for: five or more years with Java, using Spring or Dropwizard, or with Go, and a deep understanding of multithreading and asynchronous processing. Experience building high performance RESTful APIs or gRPC services. Solid experience with relational databases, MySQL or PostgreSQL, and caching layers such as Redis, at scale. Hands on AWS experience across Fargate, EC2 and Lambda, and infrastructure as code with Terraform, with the advertisement stating you should be comfortable managing your own cloud resources. Strong proficiency with Docker and Kubernetes and with CI and CD automation using Jenkins, ArgoCD or GitHub Actions. Nice to have rather than required: an understanding of OAuth 2.0, OIDC and JWT tokens, particularly for service to service communication. Experience with Splunk, SignalFX or Datadog for monitoring and troubleshooting production issues. Familiarity with Kafka or SQS for cross service messaging. If you have the backend fundamentals but not the identity protocols, the protocols are the part the posting treats as learnable. The day to day: building and operating the services behind identity administration, which means real production ownership, monitoring and on call exposure alongside feature work. Location: Bengaluru. The advertisement does not state a number of office days, so confirm it with the recruiter. Experience: five or more years, stated in the required knowledge and skills section.
Who this is for: an SRE or infrastructure engineer with eight or more years who has led a real platform migration, not only maintained an existing cluster. What the posting asks for: eight or more years in SRE, DevOps or infrastructure engineering roles. Strong hands on experience architecting and operating cloud native distributed systems on AWS and GCP. Deep Kubernetes expertise on EKS and GKE covering design, provisioning, scaling and advanced production troubleshooting, with three to five years stated against the tool itself. Proven experience leading ECS to EKS or GKE migrations and driving microservice enablement at scale. Proficiency with infrastructure as code using Terraform across multiple providers, Ansible or CloudFormation. Solid coding and scripting in Python, Go or Shell aimed at automation and tooling. Advanced understanding of CI and CD pipelines using ArgoCD, GitLab CI or Spinnaker, plus Linux systems and networking fundamentals including Direct Connect and Interconnect, DNS, routing and load balancing. Experience managing cloud databases and caching systems such as RDS, Cloud SQL, Redis, Memorystore, PostgreSQL and MySQL. Why we flag the numbers: an automated reader that takes the smallest figure in this advertisement returns three years. The actual requirement line says eight or more. We publish eight, because that is what the experience sentence says, and the three to five figures are attached to specific tools. The day to day: operating production infrastructure, leading reliability and modernisation initiatives, and acting as the escalation point for Kubernetes and multi cloud problems. Location: Bengaluru. No office days policy is published on the advertisement. Experience: eight or more years.
Who this is for: an engineer with eight or more years who wants to work on authentication at consumer scale, where an outage is a login outage for everyone downstream. What the posting asks for: eight or more years of software development experience, stated in the section describing who is a good fit for the role. Depth in building and operating production services, an eye for detail and a bias toward user experience, since the product is a login flow that other developers embed. Comfort in a highly collaborative and remote friendly environment, in the ad's own words. Bonus points, explicitly not requirements: experience building APIs for mobile applications and SDKs, one or more years of identity and access management domain experience, experience with Go and Terraform, front end work in React or Vue, and a deep understanding of the Node.js event loop. Why we flag the numbers: read by a script that takes the smallest year figure in the text, this advertisement returns one year, because of the identity and access management bonus line. Read properly it is an eight year role. This is the single clearest example in today's edition of why the years on our listings are read by hand. The day to day: building and running the business to consumer authentication domain inside Auth0, working across Node.js and React on the front end with Java and Kotlin services behind, and caring about standards compliance because the product is an implementation of them. Location: Bengaluru, with the advertisement describing the environment as remote friendly. It does not state a remote policy or office days, so confirm before assuming. Experience: eight or more years.
Added September 3, 2026
Who this is for: someone at the very start of a database or cloud operations career. The posting asks for 6 months to 1 year of experience in database administration, cloud operations, DevOps or infrastructure support, and states that internship experience in database or cloud technologies will be considered. That combination is what makes this a real entry level role rather than a junior title with a senior bar. Required: a Bachelor's degree in Computer Science, Information Technology, Engineering or a related field. Basic administration knowledge of PostgreSQL, MongoDB, Cassandra or AWS RDS. Experience managing databases in on premises or AWS cloud environments. Exposure to Terraform for provisioning and Ansible for configuration management. Knowledge of Linux administration, SQL, and backup and recovery concepts. Experience with monitoring tools such as Datadog and AWS CloudWatch. An understanding of database performance monitoring, high availability, security and troubleshooting. Familiarity with Git, shell or Python scripting, and DevOps automation practices. An advantage: an AWS Cloud Practitioner or AWS Associate certification. The day to day, from the posting: assisting with provisioning and managing database infrastructure as code; administering self managed databases on EC2 alongside managed AWS services including RDS, ElastiCache, OpenSearch, DynamoDB and Neptune; monitoring health, performance, availability and capacity; user management, backup verification, patching and upgrades; helping identify and resolve performance issues, alerts and incidents; supporting backup, restore, disaster recovery and high availability configurations; taking part in migration and upgrade projects; maintaining security standards and access controls; writing runbooks and standard operating procedures; and working with development, DevOps and infrastructure teams during deployments. Be aware: the role includes participation in on call support rotations. It is based in Bengaluru. Netradyne states that recruiting agencies should not contact it and that it will approach candidates directly where there is a match. Honest fit note: this is operations work, not feature development. You will spend your time on reliability, monitoring and automation around databases somebody else's application uses. If you want to write product code, this is the wrong first job. If you want to become a database or platform engineer, it is an unusually clean entry point, because most listings at this level in India are support desk roles rather than infrastructure ones.
Who this is for: a recent graduate or someone in their first year of work who has hands on machine learning projects, not just coursework. The requirement reads "1+ years of experience in AI/ML engineering, platform engineering, or relevant academic/internship projects", and because project work is offered as an alternative rather than an extra, a strong final year project or an internship can meet the bar on its own. The responsibilities confirm it: they are written as assist, support, contribute, and deploy "under the guidance of senior team members". Required: a Bachelor's degree in Computer Science, Data Science, Engineering, or equivalent practical experience. Solid Python and the foundational libraries, meaning NumPy, Pandas and scikit-learn. A basic understanding of a deep learning framework, PyTorch or TensorFlow. Exposure to natural language processing, large language models, or computer vision projects. An understanding of data structures, algorithms and model evaluation metrics. Strong analytical problem solving and a proactive willingness to learn. Preferred: hands on experience with end to end ML projects, hackathons or applied research. Familiarity with AWS, Azure or GCP. Version control with Git, containerisation with Docker, or basic MLOps concepts. An understanding of vector databases, embeddings, or retrieval augmented generation. The day to day, from the posting: writing clean, modular, documented Python for AI experiments and platform prototypes; developing APIs and model inference scripts; automating small tasks to streamline engineering workflows; implementing preprocessing, feature engineering and data validation; testing and optimising model performance; and translating business requirements into technical deliverables with other teams. Location: the posting lists "Bangalore / Gurgaon / Remote", so remote is offered as an option here rather than ruled out. It reports to the Director of Information Security. Honest fit note: this is an AI and platform engineering hybrid, so you need to be comfortable with infrastructure and deployment as well as models. If your interest is purely research or purely web development, look elsewhere. If you want a first job where you ship ML into production rather than write notebooks, this is one of the few on the board that will genuinely consider you.
Who this is for: an engineer with roughly three years of professional experience who wants low level systems work on a storage platform. Unusually, this advertisement tells you directly if you are too junior: it says "Candidates with less than 1 year of experience are encouraged to explore University opportunities on our careers page". That is a rare and useful piece of honesty, and it means the three year figure is a real floor rather than a wish. Required: 3 or more years of professional development experience using C, C plus plus, Python, Go, Java or related programming languages. Hands on experience or coursework in systems software domains, specifically distributed systems, operating systems, the Linux kernel, database internals, hypervisors, containers or compiler optimisation. Strong design sensibility and a track record of working well in a team oriented, open office environment. A Bachelor of Science in Computer Science or a related technical field, with an MS or PhD counted as a plus. The day to day, from the posting: creating algorithms and technologies for high performance systems aiming at 99.9999 percent reliability; leading feature work from initial concept through to a shipped product; analysing and resolving complex technical problems; and working closely with peers on features that affect customers directly. The team has also extended FlashArray into the public cloud through CloudSnap and Cloud Block Store for AWS, so there is cloud work alongside the on premises product. Office days: this is stated as an office centric role based in Bengaluru requiring presence in the office 3 days a week, with variation over time according to the company's hybrid work policy. Honest fit note: the coursework clause means a strong systems background from a degree can substitute for some industry breadth, but three years of real development is still expected. If your experience is application or web development, the domain list here is the part to take seriously. Note also that Everpure uses "Member of Technical Staff" as a catch all title across a wide range of seniorities, so do not read the title as a level: check the years line on each of its adverts separately.
Who this is for: a developer with roughly three years of C sharp experience who is comfortable close to the Windows platform. The years figure is stated plainly as "3 years' experience with C# and the .NET ecosystem", making this one of the more accessible bars in today's edition. Required: 3 years of experience with C sharp and the .NET ecosystem. A willingness to learn and develop with functional programming in F sharp. Good knowledge of Win32 APIs. Basic familiarity with networking protocols such as HTTP and TLS. The ability to write clean and testable code. A general understanding of how distributed systems work on the platform side. The ability to use AI assisted development tools for code generation, analysis and reviews, which the posting lists as a requirement rather than a bonus. Bonus skills: developing software on macOS and Linux. Experience with SDLC tooling such as Jira, GitHub and Jenkins. React programming. AWS cloud infrastructure. Contributions to open source. Experience performing peer code reviews. The day to day, from the posting: designing, developing, testing and maintaining features for enterprise SaaS platforms; building reliable and scalable services, APIs, platform components, integrations and customer facing capabilities; taking part in technical design, code reviews, troubleshooting and production support; working with product management, QA, UX and operations; and contributing to performance, reliability, security, maintainability, automation and observability improvements. Office days: stated clearly as a hybrid role requiring onsite presence at the Pune office three days per week. Honest fit note: the Win32 API requirement is the filter here. Plenty of C sharp developers have never touched it, and if that is you, expect the interview to probe it. Kaseya also describes itself as a high growth, high performance organisation that values urgency, which is worth reading as a statement about pace.
Who this is for: an engineer with about three years of experience who wants foundational distributed systems work on a product that has not been built yet. The bar is stated as "3+ years experience of building distributed systems, and/or foundational cloud services at scale", which is one of the lower floors among today's senior sounding titles. Required: a strong background building core components for high scale compute and data distributed systems. 3 or more years building distributed systems or foundational cloud services at scale, and an interest in working with Python, Go and Java. Proven success designing, writing, testing, debugging and performance tuning distributed or highly concurrent software in large, long lived code bases, with a firm grip on computer science fundamentals. A track record of identifying problems, implementing solutions and delivering complex projects in distributed systems or databases. Good verbal and written technical communication. Bonus points: experience with containerisation and orchestration platforms such as Kubernetes, and with AI frameworks and tools. The day to day, from the posting: working with research, product management, product engineering and design to implement the first version of the service and its later evolution; designing, building and delivering well tested core pieces of the platform; contributing to architecture, code reviews and developer experience as the team and product grow; and mentoring fellow engineers while owning projects. Location: MongoDB states it is looking to speak to candidates based in Gurugram for its hybrid working model. The requisition id is 426117. Honest fit note: the posting mentions mentoring fellow engineers, but there are no direct reports, no hiring and no performance responsibilities anywhere in it, so this reads as an individual contributor seat with senior expectations. Because it is a new team on a new product, expect ambiguity and rework rather than a settled roadmap.
Who this is for: a backend engineer with around four years of experience who wants developer productivity and platform work rather than customer facing features. The stated bar is 4 or more years, and the emphasis on typed systems languages is a real filter. Required: 4 or more years of strong expertise in typed systems languages such as Go or Rust for backend platform services, paired with Python proficiency for automation and AI logic integration. Practical mastery of microservice architecture including concurrency, retries and idempotency, along with solid Linux and Unix debugging across network, storage and application layers. Practical knowledge of building agentic workflows, prompt design, and integrating large language model APIs with vector databases and retrieval augmented generation systems. Hands on skill containerising microservices and managing workloads with Kubernetes, plus data querying proficiency in SQL or analytics engines to demonstrate operational impact. The day to day, from the posting: designing and deploying production microservices and durable Temporal workflows for the continuous integration of FlashArray, FlashBlade and Hyperscale; extending in house scheduling and placement algorithms across bare metal hardware and virtual machine fleets to cut queue times; engineering RAG pipelines and agentic workflows over failure logs, vector stores and test metadata to automate root cause analysis, flake classification and developer triage; establishing platform metrics such as time to signal and pass or flake rates; and operating your own services end to end. Office days: the posting states that Everpure is primarily an in office environment and that you are expected to work from the Bangalore office unless on leave or work travel. Honest fit note: the AI requirement here is not decorative. Building RAG pipelines and agentic workflows is listed as a requirement, not a nice to have, so if you have never integrated an LLM API with a vector store you will be behind. Note also that Everpure reuses "Member of Technical Staff" across levels from three years to eight, so read each advert's years line rather than the title.
Who this is for: an experienced ServiceNow developer, not a general application developer. The posting asks for 4 or more years of proven success specifically as a ServiceNow Developer, and the skill list is entirely platform specific, so general Java or Python experience will not substitute. Required: 4 or more years as a ServiceNow Developer with deep technical command of Business Rules, Client Scripts, UI Policies, Flow Designer, ACLs, Script Includes, UI Scripts and custom third party API integrations. Hands on implementation and configuration expertise in core ServiceNow applications, specifically ITSM, CSM, ITOM, HR or IRM, with proven capability managing data migrations, code promotions and Update Sets. Strong analytical and interpersonal skills to manage several simultaneous deliverables, decode complex business requirements, and give constructive technical reviews and mentorship to peer developers. The day to day, from the posting: leading end to end architecture, development and deployment of functional workflows, business rules and secure integrations to improve platform performance, scalability and automation; partnering with process owners and business analysts to turn operational workflows into automated solutions; conducting code reviews and unit testing against security, reliability and extensibility standards; executing production deployments through established change management; driving technical documentation; prioritising root cause analysis queues for periodic releases; and taking part in a shared team on call rotation to keep the 24x7 customer service tools available. Office days: the posting states Everpure is primarily an in office environment and that you are expected to work from the Bangalore office in line with company policy. Honest fit note: this supports a 24 hour a day operation and carries on call, which is the trade for the stability of an in house platform role. If you want product engineering, this is not it. If you have spent four years implementing ServiceNow for clients and want to own one estate properly instead, it fits well.
Who this is for: an engineer with four or more years who builds test frameworks and developer tooling, and who has genuinely worked with large language model evaluation rather than just used a chatbot. The years bar is "4+ years of commercial software development experience with at least one JVM language such as Java, preferably using the Spring ecosystem". Required: 4 or more years of commercial software development with a JVM language, preferably Spring. Proven experience evaluating large language models, whether OpenAI, Anthropic or open weights. Familiarity with evaluation frameworks such as DeepEval, Ragas or Promptfoo and with LLM as a judge concepts. Experience integrating LLMs into developer workflows to automate unit test generation and edge case discovery. Experience curating golden datasets, adversarial test sets and scoring rubrics to test LLM accuracy, safety and relevance. Experience building developer tools, infrastructure or complex testing frameworks. Solid software architecture experience. Experience in application or database modernisation, with the ability to design frameworks that ensure database state equivalence across implementations, which requires understanding change data capture, event driven database interception through MongoDB listeners or RDBMS triggers, and state comparison algorithms with pattern based exclusions. Experience with relational and document data modelling and hands on work with at least one SQL database and one document database. A good understanding of algorithms and data structures and their complexity. The day to day: contributing well tested code to the modernisation and framework team; collaborating with product management, engineers and designers on the roadmap; taking an active part in code reviews; troubleshooting complex issues in distributed systems; and giving and seeking feedback on design documents and pull requests. Location: MongoDB states it is looking to speak to candidates based in Gurgaon for its hybrid working model. Honest fit note: the advertisement says "You will lead a talented team building a complex product suite", but no direct reports, hiring or performance duties appear anywhere in it, and the expectations listed are all individual contributor work. Read "lead" here as technical leadership. The genuine filter is the LLM evaluation experience, which is still rare and is asked for specifically rather than in passing.
Who this is for: a JavaScript and TypeScript engineer with five or more years who genuinely enjoys developer experience work. The stated bar is "5+ years of professional experience with JavaScript and TypeScript, including Node", and the posting is explicit that this is primarily a software engineering role with meaningful opportunities to engage with developers, rather than a developer relations or advocacy job. Required: 5 or more years of professional JavaScript and TypeScript experience across browser and Node.js environments. An understanding of developers and their experience, and the ability to design intuitive APIs, libraries, CLIs, SDKs, documentation and examples that let developers integrate a product quickly, correctly and securely. The day to day, from the posting: developing and maintaining libraries that let users integrate with Auth0; shaping and developing the open source CLIs and SDKs; writing, curating and editing developer resources including tutorials, examples, guides and documentation; owning Auth0 code samples and implementation guidance and making them clear, structured and discoverable for both developers and AI agents; improving quickstart guides and onboarding; troubleshooting and fixing issues in the libraries, SDKs, CLI and integrations; and gathering user feedback and channelling it back across engineering, product, documentation, support, developer relations and community teams. Location: Bengaluru. Honest fit note: Okta states plainly that it is "not looking for someone who checks every single box", which is worth taking at face value if you are close but not exact. The part to be honest with yourself about is the writing. A meaningful share of this job is producing documentation and samples, and if that sounds like a chore rather than a craft, you will not enjoy it. Auth0 is described as a Tier 0 global service, so the reliability expectations on anything you ship are high.
Who this is for: a backend engineer with five or more years who wants deep, narrow systems work on database connectivity rather than broad product features. The stated bar is 5 or more years of production level experience in one of Java, Python, Go or a similar language, alongside a BTech or higher in computer science or a related field. Required: a BTech or higher in Computer Science or a related field. 5 or more years of production level experience in Java, Python, Go or similar. The day to day, from the posting: designing, developing and maintaining the SQL drivers that carry the majority of data warehousing traffic, plus the infrastructure components behind partner integrations; optimising those drivers for performance, reliability and telemetry; maintaining open source repositories and actively engaging with the developer community; evolving the Partner Connect offering so customers can add their preferred tools directly inside Databricks; and working with cross functional teams to define technical requirements and architect solutions. Location: Bengaluru. The internal requisition reference on the posting is P-1405. Honest fit note: this is a driver and protocol role. The work is ODBC and JDBC style connectivity, correctness and performance, and it is the kind of engineering where a subtle bug affects thousands of customer integrations at once. That is either exactly what you want or exactly what you do not. The open source element is genuine, so your work is publicly visible, which cuts both ways. Note that Databricks publishes several similar senior titles at very different bars, so check the years line on each one rather than assuming the level from the title.
Who this is for: a performance specialist with five or more years, not a generalist who has run a load test occasionally. The posting states two separate five year bars: 5 or more years of software development experience including substantial Java, and 5 or more years in performance engineering or a closely related discipline. Required: 5 or more years of software development experience including substantial Java. 5 or more years in performance engineering or a closely related discipline. The ability to independently plan and execute performance engineering activities for large scale services in cloud native environments, and to own work from planning through execution, analysis, documentation, stakeholder communication and completion with minimal supervision. The day to day, from the posting: defining and executing performance testing strategies for identity management products; planning and running system level load, scalability, endurance, stress, reliability, regression, baseline and benchmark tests; defining meaningful metrics, analysing results and communicating trends and trade offs to engineering, cloud, SRE, product and customer facing stakeholders; troubleshooting and performing root cause analysis on performance and reliability issues across multiple components; coordinating with engineering teams to implement and verify fixes; performing Java application profiling, stack tuning, memory analysis and optimisation; determining configurations for optimal performance, capacity planning and resource sizing across virtualised and containerised environments; improving performance test automation in continuous integration; and maintaining documentation on test methods, results, tuning guidance and capacity planning. Location: Bengaluru. Ping Identity is headquartered in Denver, Colorado, with offices worldwide. Honest fit note: performance engineering is a career track of its own, and this posting is written by people who know that. The emphasis on communicating findings to stakeholders is not filler: a large part of the job is convincing other teams that their component is the bottleneck and getting the fix landed. If you like measurement and dislike persuasion, weigh that honestly.
Who this is for: a backend engineer with five or more years who wants genuine scale. The stated bar is "5+ years of hands-on backend engineering experience, Java, Spring Boot, AWS". Despite the Technical Lead title, no direct reports, hiring or performance review duties appear in the posting: the leadership it describes is mentoring, code review and pushing engineering standards, so this reads as a hands on individual contributor role. Required: 5 or more years of hands on backend engineering with Java, Spring Boot and AWS. Proven ownership of high scale distributed systems. Deep knowledge of microservices, messaging systems, caching, storage optimisation and cloud scalability. Clear architectural thinking, described as being able to design systems for billions of transactions rather than millions. An AI first mindset, meaning practical use of GPT and other AI coding tools to work faster. Strong mentoring and code review skills. Eligibility to note: under preferred qualifications the posting states a Bachelor's or Master's degree in Computer Science or equivalent "Only from Tier 1/2 colleges". It is listed as preferred rather than required, but it is stated plainly enough that you should factor it in before spending time on an application. The day to day, from the posting: designing scalable architectures rather than only writing code; driving backend systems supporting more than 100 million daily active users; optimising APIs to sub 50 millisecond latencies; coaching engineers; and leading technology first projects. The team describes itself as a pure technology team inside Paytm with no unnecessary meetings or bureaucracy. Location: Bangalore, Karnataka. Honest fit note: the ideal profile section says the role suits someone who wants to grow into a principal engineer, architect or CTO over time, which tells you the seat is pitched at ambitious mid career engineers. The college preference is the part most likely to affect whether an application is read, and we would rather you knew it before applying than after.
Who this is for: an engineer with six or more years whose experience is in internal tools and developer platforms specifically. The bar is stated as "6+ years of experience building internal tools or developer platforms", which is narrower than six years of general software engineering, and it is the phrase to match your CV against. Required: 6 or more years building internal tools or developer platforms. Strong CI and CD and automation expertise, including generative AI integration in the software development lifecycle. Deep grounding in data structures, algorithms and microservices or distributed system architecture patterns. Appian describes itself as language agnostic but states a preference for strong Java or Python. A major advantage: hands on experience with cloud infrastructure, container frameworks such as Docker and Kubernetes, and CI and CD pipelines. Highly valued: daily use of AI tools and agentic engineering environments, with Kiro, Claude and Copilot named directly, to accelerate software design, automate background workflows and improve developer productivity. What Appian offers around the role: department specific training during onboarding, a mentorship scheme and a First Friend programme for new hires, access to Appian University, skills based training and tuition reimbursement. Benefits may include health coverage, an employee assistance programme with free mental health support, life and disability insurance, an employee stock purchase programme, a retirement or pension plan, wellness allowance and family forming benefits, though the posting notes these vary by country. Location: Chennai, India. Honest fit note: Appian leads its advertisement with values it calls Intensity and Excellence and language about high standards, which is a reasonable signal about pace and expectations. The AI tooling requirement is worth taking literally. This team's product is developer productivity, so an engineer who has not actually used agentic coding tools in anger will struggle to speak to the core of the job.
Who this is for: a backend or data engineer with six or more years who wants observability and platform work at genuine scale. The stated bar is 6 or more years of production level experience in one of Java, Scala, Python, C plus plus or a similar language. Required: 6 or more years of production level experience in Java, Scala, Python, C plus plus or similar. Experience with cloud technologies including AWS, Azure, GCP, Docker and Kubernetes. A proven track record architecting, developing, deploying and operating components of large scale distributed systems. Strong software engineering maturity across security, correctness and operational excellence. A platform mindset, described as building effectively for other software teams, iterating quickly to reduce friction to adoption, and advocating for platform use. Cross functional skills, because the team serves both internal Databricks customers and external ones. The day to day, from the posting: developing systems that let customers answer questions about their Databricks environment through a reliable and timely observability interface; making it easy for framework teams across the company to publish their data to customers; leading large milestones from the observability roadmap and contributing to long term vision and requirements; mentoring other engineers; optimising the scalability and cost of large data pipelines; and driving integration with popular tools in the data warehousing ecosystem. The posting notes customers use this for DevOps, FinOps, SecOps and AIOps work. Location: Bengaluru. The internal requisition reference is P-1385. Honest fit note: the role explicitly includes leading technical development of product milestones from requirements through execution and iteration, so it expects ownership beyond writing code, but there is no people management in it. Mentoring is listed as a responsibility. If you want to be handed well specified tickets, this is not that job.
Who this is for: an SDET with six or more years who builds frameworks. The bar is stated as "6+ years of experience in the software industry with strong passion for quality, automation, and engineering excellence", and the role is described as requiring extensive industry experience. Required: 6 or more years of experience in the software industry with a strong focus on quality, automation and engineering excellence. The ability to define and execute the design, development and maintenance of test automation tools and frameworks using reliable and scalable techniques. The posting asks for someone highly technical, detail oriented, creative and results focused. The day to day, from the posting: solving complex testing problems by designing, developing and improving automation and reporting frameworks; investing in test stability and framework performance through new solutions that improve testing efficiency; coaching Fivetran quality engineers to become strong automation engineers; and working continuously with the team to hold high automation standards. The role emphasises leveraging AI driven solutions to accelerate testing, improve developer productivity and sharpen operational insight. Office days: Fivetran states a hybrid model with two days in the office each week. Benefits listed include 100 percent employer paid medical insurance, a generous paid time off policy, paid sick time and an inclusive parental leave policy. Worth knowing: Fivetran and dbt Labs are integrating, and the posting says openly that you may see references to both companies through the recruiting process as teams, systems and career sites are merged. If organisational change during your first year matters to you, that is disclosed up front. Honest fit note: coaching quality engineers is listed as a responsibility, but there are no direct reports or hiring duties, so this is a senior individual contributor seat. Note that another Fivetran advertisement this week carries a remote tag while this one and a third state two days in the office, so treat the two day expectation as the company's real model unless a recruiter tells you otherwise.
Who this is for: an application security engineer with six to nine years of experience who wants to work with development teams rather than police them. The posting states 6 to 9 years of experience in application security, product security, DevSecOps or security engineering, so both ends of that range are given, which is more than most adverts offer. Required: 6 to 9 years in application security, product security, DevSecOps or security engineering. The ability to lead threat modelling and security design reviews for high impact systems and features. Experience conducting architectural reviews and risk assessments for new capabilities and major design changes. Experience building and improving security automation inside CI and CD pipelines. Hands on experience integrating and optimising application security tooling, specifically SAST, DAST, software composition analysis, secrets scanning, infrastructure as code scanning and API security controls. The scope spans web, mobile, APIs and cloud connected systems. The day to day, from the posting: driving integration of security across all phases of the development lifecycle from design to deployment; partnering with development teams to implement scalable application security controls, standards and guardrails; promoting secure by design principles across web, mobile, cloud, APIs and distributed systems; leading threat modelling exercises; helping engineering teams identify practical mitigations and reduce design level risk early; and driving vulnerability reduction and developer enablement. Location: Bangalore HQ. Honest fit note: Tekion describes a security culture that prioritises guardrails over roadblocks and empowers developers to move fast, which suits someone who prefers building tooling and standards to running a gate. Note that Tekion advertises a very large number of similarly named engineering roles at once, and that its "Senior Software Engineer" postings mostly sit at 5 to 7 years, so check the years line on any other Tekion advert you consider rather than assuming from the title.
Who this is for: a senior .NET engineer with a genuine systems background. The bar is stated as "Minimum 7 years of experience working with C# and the .NET ecosystem", and the surrounding requirements make clear this is a platform and endpoint role rather than an application one. Required: a minimum of 7 years with C sharp and the .NET ecosystem. The ability to lead and influence technical direction. Participation in design reviews and mentoring of other engineers. The ability to understand deeply interconnected systems from a system architecture view. Excellent knowledge of Win32 APIs. Solid knowledge of networking protocols including HTTP, TLS and WebSockets. Experience working with large cross platform codebases. An excellent understanding of concurrency and thread related work. The day to day, from the posting: designing, developing, testing and maintaining software features for enterprise SaaS platforms; building reliable and scalable services, APIs, platform components, integrations and customer facing capabilities; taking part in technical design, code reviews, troubleshooting and production support; collaborating with product management, QA, UX and operations; contributing to performance, reliability, security, maintainability, automation and observability improvements; following and improving agile, CI and CD, automated testing and DevOps practices; mentoring junior and mid level engineers; and communicating progress, risks and technical trade offs clearly. Office days: Kaseya's companion adverts for the same team state a hybrid arrangement with three days per week onsite at the Pune office. Honest fit note: mentoring is in the responsibilities but there are no reports, hiring or performance duties, so this is a senior individual contributor role. The Win32 and cross platform codebase requirements are the real filter, and they are the reason a .NET web developer with seven years may still not match. Kaseya is candid that it is a high growth, high performance organisation that values urgency.
Who this is for: an experienced SRE. The posting states the seniority twice, once in the job summary as "Site Reliability Engineer (7+ Years)" and again in the requirements as 7 or more years of industry experience, so the bar is unambiguous despite the plain title carrying no seniority marker. Required: 7 or more years of industry experience. The ability to design, build and maintain resilient cloud infrastructure supporting scalable and reliable applications, including managing and optimising cloud platforms for high availability, performance and cost efficiency. Experience establishing and managing monitoring and alerting systems to detect anomalies proactively, and working with service level indicators, objectives and agreements to measure and improve reliability. Experience automating provisioning and standardising infrastructure resources and system configurations, and writing standard operating procedures and automated workflows using tools such as Rundeck or Jenkins. Experience participating in and resolving major incidents, conducting root cause analysis and implementing permanent fixes. Office days: the posting states the work mode directly and emphatically as 5 days working from office, in Hyderabad. That is worth weighing before applying, because it is stricter than most roles in this edition. About the employer: HighRadius is India headquartered with a global presence across more than 8 locations, reports a valuation of 3.1 billion dollars and annual recurring revenue above 100 million dollars with 24 percent year on year growth, and states that it is at pre IPO stage. Honest fit note: the role mixes live production management with engineering work such as automation and system improvement, so expect genuine operational load including incident response, not a pure build role. The five day office requirement is the single biggest practical filter here and the posting does not hedge it.
Who this is for: a backend engineer with seven or more years who wants platform and developer tooling work. The stated bar is 7 or more years of professional experience in software development with a strong focus on backend systems and distributed applications, plus 5 or more years hands on in Java, Go, Python or similar backend languages building scalable and reliable applications. Required: 7 or more years of professional software development experience focused on backend systems and distributed applications. 5 or more years hands on with Java, Go, Python or similar backend languages. Deep expertise in software engineering principles and cloud native development, applied to tooling for infrastructure provisioning, vulnerability management and infrastructure as code deployments. The day to day, from the posting: leading design and development of scalable microservices and tools forming the backbone of Okta's continuous delivery platform, including components for Spinnaker, Terraform and custom tooling; developing software and APIs that let engineering teams provision and manage infrastructure, execute production changes and deploy code reliably; contributing to architectural design and hands on implementation of CD pipelines and Terraform based workflows; writing clean, well tested code with a focus on automation and self service; partnering with DevOps, SREs and product teams; and mentoring other engineers while influencing the team's technical roadmap. Location: Bengaluru. Worth knowing before you interview: the advertisement is titled Staff Software Engineer, but its own opening line says Okta is "seeking an experienced and technically influential Senior Software Development Engineer" and it refers to the role as Senior Software Development Engineer throughout the body. The years figure of 7 or more sits between the two levels. Worth clarifying with the recruiter which level the requisition is actually approved at, because it affects both compensation and scope. Honest fit note: this is infrastructure software engineering, not operations. If your experience is running pipelines rather than building the systems that run them, the gap will show. Okta states it is not looking for someone who checks every single box.
Who this is for: an infrastructure engineer with seven or more years who is comfortable being measured as a software engineer too. The bar is stated as 7 or more years of experience in infrastructure, DevOps or site reliability engineering, with at least 5 years focused on cloud native environments, so the second figure is the one that narrows the field. Required: 7 or more years in infrastructure, DevOps or SRE, with at least 5 years focused on cloud native environments. Designing and managing multi cloud environments across AWS and GCP using Terraform so infrastructure is versioned, reproducible and scalable. Operating production grade Kubernetes clusters with attention to cluster health, resource optimisation and application deployment. Building and maintaining specialised infrastructure for AI workloads. Maintaining a diverse data layer including vector search databases for AI retrieval, PostgreSQL, MySQL and MongoDB. Implementing deep stack monitoring and alerting with Datadog and Prometheus. Maintaining and evolving an active codebase in Python, Go or Bash to automate repetitive work, and integrating large language models into that workflow to speed up scripting, documentation and operational efficiency. Managing complex cloud networking and traffic. Locations: the requisition lists Bengaluru, Karnataka and Chennai, Tamil Nadu. How the team describes itself: the Infrastructure Engineering group says its size and the support it receives give it unusual latitude and agility, that staff are given autonomy and personal discretion, and that the work has direct and tangible impact. It operates as an international team in a fast paced environment. Honest fit note: the posting says directly that you will not be "keeping the lights on" but architecting foundations for AI products, and the vector database and LLM integration requirements back that up. If your DevOps experience is entirely traditional web infrastructure with no AI or ML workload exposure, expect that to come up. Note that ZoomInfo's careers site returns an error to automated requests, so we confirmed this posting is live through the employer's own applicant tracking system API before publishing it.
Who this is for: a senior data and applied AI practitioner who wants to stay hands on. The posting states twice and unusually clearly that this is an individual contributor role: "This is an individual contributor role, you will not manage people", and later that technical judgment is shared "through collaboration, not people management". Given how many staff and lead titles hide reporting lines, that is worth noting. Required: 7 or more years across data science, applied AI and machine learning, or advanced analytics, with a track record of staff level individual contributor technical ownership. The ability to own the technical build of AI powered analytics tools including RAG pipelines, LLM assisted querying, agent workflows and applied ML models. Data science methods such as forecasting, segmentation, anomaly detection and classification, applied where a problem genuinely calls for them. The ability to write the SQL and Python needed to support your own models and analysis. The day to day, from the posting: designing, building and deploying AI agents for analytics use cases; identifying and prioritising high value opportunities to automate manual analytics work, then prototyping, testing and productionising them independently; and proposing and maintaining a rolling technical roadmap for AI and data science in the analytics function, described as a living document rather than a fixed annual plan. The stack: Glean, Gemini, Claude Code and Snowflake Cortex today. The posting states plainly that it expects this to change and that it values how quickly you pick up new tools over whether you already know theirs. Office days: Everpure describes itself as primarily an in office environment, based in Bangalore. Honest fit note: the advertisement asks for someone "naturally ahead of the curve" who tests new tools before they are mainstream, and says the core of the role is LLM and agent based automation rather than classical modelling. If your strength is rigorous statistical modelling and you have little LLM engineering experience, the emphasis here runs the other way.
Who this is for: a senior SRE with eight or more years and real multi cloud depth. The bar is stated as "Experience: 8+ years in SRE, DevOps, or Infrastructure Engineering roles", supported by several specific sub requirements at 3 to 5 years each. Required: 8 or more years in SRE, DevOps or infrastructure engineering. 3 to 5 years with Kubernetes on EKS or GKE and the surrounding ecosystem including Helm and Karpenter, in production. 3 to 5 years with both AWS and GCP. 3 to 5 years using Terraform to manage multi cloud infrastructure. 5 or more years of coding in Python, Go or similar. Deep expertise in Kubernetes design, provisioning, scaling and advanced production troubleshooting. Proven experience leading ECS to EKS or GKE migrations and driving microservice enablement at scale. Proficiency with infrastructure as code tools such as Terraform across multiple providers, Ansible or CloudFormation. Advanced understanding of CI and CD pipelines including ArgoCD, GitLab CI and Spinnaker, Linux systems, and networking fundamentals covering Direct Connect or Interconnect, DNS, routing and load balancing. The day to day, from the posting: designing, building and operating scalable, reliable and secure infrastructure across AWS and GCP; leading reliability and modernisation initiatives; partnering with development teams to make microservice applications production ready; driving observability, performance and cost efficiency; championing SRE practice through SLOs and SLIs and blameless postmortems; leading complex technical projects across teams; mentoring engineers; working with security and compliance on IAM federation and workload identity; and taking part in the on call rotation. Location: Bengaluru. Worth knowing: Okta is currently advertising three separate roles in Bengaluru under this exact title. Two of them carry identical text to each other and state no experience requirement at all. This is the only one of the three that publishes a bar. If you are comparing Okta SRE listings, they are not interchangeable, and the other two tell you nothing about the level.
Who this is for: a DevOps or platform engineer, and the level is genuinely negotiable here. The posting states "5+ years of experience in DevOps, Site Reliability Engineering, Platform Engineering, infrastructure engineering, or a related role" and separately that "Staff-level candidates will typically have 8+ years of relevant experience". Netskope also states at the top that this team is hiring across multiple levels and that candidates are individually assessed and levelled based on their skills and experience. We have published the five year floor because that is the stated minimum, but if you are at five or six years, expect to be levelled below staff. Required: 5 or more years in DevOps, SRE, platform engineering, infrastructure engineering or a related role. Comfort working across Kubernetes, cloud infrastructure, CI and CD, observability, networking and distributed systems. The posting looks for engineers who enjoy solving complex infrastructure and production engineering problems through software development, automation and strong systems knowledge. The day to day, from the posting: building and operating the infrastructure, automation and engineering platforms that let the Data Security services deploy and run reliably at global scale; developing tools and automation that improve how engineering teams build, deploy and operate services; and working closely with development, SRE, platform engineering, operations, QA and cloud infrastructure teams. There are opportunities to use AI assisted development tooling. Location: Bengaluru, Karnataka. Honest fit note: the multi level hiring statement is the most useful sentence in this advertisement. It means a mid level engineer should apply rather than self reject on the staff title, and it also means the title on the advert is not a promise about the offer you would get. Ask early where in the band the requisition sits.
Who this is for: an experienced machine learning engineer who builds systems. The stated bar is 8 or more years of experience in machine learning, and the posting says outright that this is a hands on role where "experimentation, ownership, and shipping matter more than academic perfection". Required: 8 or more years in machine learning. Proficiency in either Go or Python. Experience designing, developing and deploying production ML models and AI services. Experience building end to end ML pipelines covering data ingestion, feature engineering, training, evaluation, deployment and monitoring. Experience implementing AI driven software systems with a focus on natural language processing and named entity recognition. Hands on Python with NumPy, Pandas and scikit-learn. Experience with a deep learning framework, TensorFlow or PyTorch. A deep understanding of current model architectures, especially language models. An understanding of data pipelines, feature stores and the model lifecycle. Performance engineering experience building high throughput, low latency systems. Continuous integration, testable code and test driven development. A deep understanding of algorithms, data structures, scalability and distributed systems. Privacy and authorisation or authentication engineering is described as a considerable plus. Good to have: natural language processing, recommendation systems or computer vision experience, and exposure to MLOps tools such as MLflow, Airflow, Kubeflow, SageMaker or Vertex. Location: listed as India. Skyflow is headquartered in Palo Alto, California and was founded in 2019. Benefits listed include a work from home expense, health insurance, generous paid time off and flexible hours, which suggests a distributed setup, though the posting does not state a remote policy in a full sentence, so confirm the arrangement with the recruiter rather than assuming. Honest fit note: Skyflow says plainly that great software engineers come from diverse backgrounds and that no single person may have all the desired skills on day one, and it frames the ideal candidate as someone who would have enjoyed building the Stripe or Twilio APIs. Read the eight years as an experience level rather than a checklist you must match line by line.
Who this is for: a principal level systems engineer with a networking specialism. The bar is stated as a Bachelor's or Master's in Computer Science or a related field with 10 or more years of experience in system engineering for high performance networking, so both the years and the domain are specified. Required: a Bachelor's or Master's degree in Computer Science or a related field. 10 or more years of experience in system engineering for high performance networking. Expertise in Go and Python. A history of integrating new technologies to enhance daily workflows and augment problem solving. The day to day, from the posting: designing, developing and optimising high performance network system architecture and security features supporting mission critical applications; partnering with engineering architects, product managers, solution architects and customers to understand complex use cases and review product requirement documents; authoring design and functional specifications while driving unit testing and automation for product quality; collaborating across teams to resolve system level issues, optimise data path performance and drive feature innovation; and applying advanced software design principles and troubleshooting expertise to coach junior team members and maintain compliance with federal security certifications. Reporting and location: the posting states this is a hybrid role based in Bangalore, India, reporting to the Director, Software Engineering in the Engineering department. Zscaler notes the platform has more than 100 patents. Honest fit note: coaching junior engineers appears in the responsibilities, but there are no direct reports, hiring duties or performance responsibilities anywhere in the advertisement, so this is a principal individual contributor seat. Zscaler describes a challenge culture with ongoing feedback and asks for people who thrive in ambiguity, which is a fair signal about how much structure to expect. Note that Zscaler publishes several similarly named engineering adverts at very different levels, including one Staff title this week that states no years at all, so read each one separately.
Who this is for: a senior backend engineer with ten or more years who wants technical ownership of a platform area. The bar is stated as "10+ years of strong hands-on software engineering experience, with significant experience in Java and backend/API development". Required: 10 or more years of hands on software engineering with significant Java and backend or API development experience. The ability to own architecture and technical direction for complex systems involving device telemetry, health monitoring, APIs, data pipelines and third party integrations. Experience designing and implementing REST APIs, webhooks, partner integrations, asynchronous workflows and event driven services. Experience defining and enforcing API standards including versioning, backward compatibility, authentication, authorisation, rate limiting, error handling and lifecycle management. Experience designing systems that process high volumes of real time data against performance, scalability and reliability requirements. Experience addressing distributed system challenges including retries, idempotency, fault tolerance, failure handling and data consistency. The day to day, from the posting: leading design and development of scalable device health, monitoring, platform, API and integration services; building highly available, reliable, secure backend services and customer facing APIs; building solutions for device status and health monitoring by processing telemetry; optimising data processing pipelines; working with product, architecture, QA, DevOps and partner teams; leading architecture reviews and technical discussions; identifying scalability, reliability, performance and security risks; driving projects from requirements through to production support; and investigating complex production issues to root cause. Location: Bengaluru, Karnataka. Honest fit note: the posting describes the role as combining hands on engineering with architecture, technical leadership, mentoring and cross functional execution, and calls for a senior technical leader. There are no direct reports, hiring or performance duties in it, so this is an individual contributor role with architecture ownership. Netradyne states it approaches candidates directly where there is a match and asks recruiting agencies not to contact it.
Who this is for: a staff engineer with a decade of experience. The bar is stated precisely as "Minimum 10+ years of software engineering experience, with 4+ years in Staff role focused on large-scale SaaS", so both the total and the time already spent at staff level are specified, which is stricter than a plain ten year requirement. Mandatory technical skills, quoting the posting's own headings. Java and Spring Boot: deep expertise building high scale microservices, including connection pooling, JVM tuning, asynchronous programming, cache management including tenant aware caching, and REST API design. Apache Kafka: a strong understanding of event driven architectures including consumer groups, partitioning strategies, tenant fan out, event sourcing patterns and exactly once processing. Data technologies: hands on experience with LDAP and OpenSearch for large scale identity and search workloads. Cloud platforms: strong experience designing and operating applications on AWS using cloud native services. The day to day, from the posting: leading the design of distributed systems that handle rapid global growth while maintaining low latency; partnering with SRE and DevOps to improve CI and CD pipelines, automated scaling and self healing infrastructure; driving rigorous design reviews and a culture of high quality, maintainable code; and driving technical adoption of AI across both product capabilities and the software development lifecycle. Location: Bengaluru, Karnataka. Ping Identity is headquartered in Denver, Colorado with offices worldwide. Honest fit note: the four years at staff level requirement is the unusual part and it is the sort of thing recruiters do screen on, so if you have ten years but have only recently been promoted to staff, be ready to make the case on scope rather than title. Note that Ping Identity is separately advertising a Principal Software Engineer role, so if you are past this level there is a higher seat on the same platform. This posting contains no reporting lines or hiring duties: the leadership described is technical.
Who this is for: a senior test engineer with deep network security domain knowledge. The bar is stated as "10+ years of hands-on experience in developing tests and automation in the area of Web Inline Network Security, with expertise in deep packet inspection (DPI) technologies", so the domain requirement is as specific as the years figure. Important context on level: the posting states at the top that this team is hiring across all levels and that candidates are individually assessed and appropriately levelled based on their skills and experience. So the ten year figure is a stated floor for the staff title rather than a hard gate on applying, and Netskope has used this same language on other listings we have published. Required: 10 or more years of hands on experience developing tests and automation in web inline network security, with expertise in deep packet inspection technologies. The ability to design test plans and test strategy documents and work closely with development to cover all aspects of features being built. The ability to design, implement and maintain automated test frameworks and scripts using Pytest, Robot Framework, Selenium or similar. The ability to own and make quality decisions for the solution as a whole. The day to day, from the posting: developing expertise in Netskope's cloud security solutions and using it to help design and qualify the solution; taking part in requirements gathering with product managers and in design discussions; understanding the use cases and workflows of secure web gateway products; and building the automation that tests them. Location: Bengaluru, Karnataka. Honest fit note: this is not general QA automation. The deep packet inspection and inline network security requirements mean a strong SDET from a web or mobile background will find the domain gap large. Conversely, if you have spent years testing proxies, firewalls or gateways, this is squarely aimed at you, and the individual levelling statement means it is worth applying even if you are somewhat short of ten years.
Who this is for: a backend engineer at intermediate level who wants to work remotely. GitLab publishes no years of experience requirement anywhere in this posting, which is its standard practice, so we have not invented a number. The level signal is in the title and in the description of the work: you take features from requirements through delivery with minimal guidance, but tenured engineers review your work and help you grow, which describes a mid level rather than a first job or a lead. Remote: this is the part worth reading carefully, because it is what several readers have asked us for specifically. GitLab states that "All of our roles are remote, however some roles may carry specific location-based eligibility requirements". This requisition is titled for India and lists its location as Remote, India. GitLab describes itself as a remote first, asynchronous organisation. What the posting asks for: the ability to work with minimal guidance, to know when to seek help, and to communicate clearly in a remote asynchronous environment. Strong written communication and effective collaboration are named as requirements rather than soft extras, which is what asynchronous work actually demands. GitLab also states that it treats AI as a core productivity multiplier and that all team members are expected to incorporate AI into their daily workflows, and this posting says you will develop the judgment to know when to trust it and when not to. The day to day: taking backend features and improvements from problem clarification through shipping and production follow up; partnering with product management, frontend, infrastructure and security to deliver predictably; and contributing to the quality, security, performance and maintainability of shared backend code and services. Honest fit note: because no years figure is published, this role appears in no experience band on our filters, and we would rather say that than guess. GitLab's engineering is largely Ruby on Rails and Go. Remote and asynchronous work suits people who write clearly and organise themselves, and it is genuinely harder for people who prefer to learn by tapping a colleague on the shoulder.
Who this is for: a staff level backend engineer. As with all GitLab postings, no years of experience requirement is published anywhere, so we have not assigned one. The level is described through scope instead: solving the highest scope and most complex problems in your area, leading large cross cutting initiatives, and setting standards other teams follow. Remote: GitLab states that "All of our roles are remote, however some roles may carry specific location-based eligibility requirements". This requisition is titled for India with its location listed as Remote, India, and the company describes itself as remote first and asynchronous. What the posting asks for: deep backend expertise combined with systems judgment, product judgment and influence across organisational boundaries. Notably, the posting states that you will exercise that influence "without relying on formal authority", which is an explicit statement that this is an individual contributor role rather than a management track. You would work with product, frontend, infrastructure, security, data, engineering managers and engineers across product groups. GitLab expects all team members to incorporate AI into their daily workflows. The day to day: leading large, cross cutting backend initiatives; driving the modular architecture strategy; defining the standards that let teams move faster without compromising quality, security, reliability or operability; leading the modernisation of a large monolith towards modular, reusable, appropriately independent systems; and shaping technical direction through clear written proposals and decision records. Honest fit note: monolith decomposition is slow, contested work that succeeds through persuasion as much as through code, and this posting is honest about that in describing influence without formal authority. If you want to be given a mandate, this is not it. Because no years figure is published, this role sits in no experience band on our filters. GitLab's backend is largely Ruby on Rails and Go.
Who this is for: a backend Java engineer working on identity. We cannot tell you the experience bar, because Zscaler does not state one. This posting contains no years of experience sentence anywhere in its text, so we have published it with no figure rather than inferring one from the Staff title. That is worth knowing for a specific reason. Zscaler is currently running a second advertisement in Bangalore under this exact same title, Staff Software Development Engineer, and that one does state a requirement, of 5 or more years on systems or distributed systems with a focus on networking and firewall technologies. The two adverts are different roles on different teams, and only one of them tells you the bar. If you are comparing Zscaler listings, do not assume the title carries a consistent level. What the posting does ask for: the ability to lead development of identity management products, to design and implement scalable, high performance backend services and APIs using Java, to ensure code quality by writing and maintaining unit, integration and performance tests, and to monitor, debug and optimise system performance. You would collaborate across teams and take part in Agile and Scrum ceremonies including sprint planning and retrospectives, and participate in an on call rotation supporting a highly available platform while ensuring compliance with federal guidelines. Reporting and location: the posting states this is a hybrid role based in Bangalore, reporting to the Senior Manager, Engineering in the Identity and Access Management department. Honest fit note: Zscaler's success profile asks for people who thrive in ambiguity, act like owners and operate across both high level strategy and hands on execution, and it describes a challenge culture with ongoing feedback. Because no years figure is published, this role appears in no experience band on our filters. If you are somewhere between senior and staff, the absence of a stated bar is arguably room to make your own case.
Who this is for: a QA or test engineer moving into AI evaluation, or someone already doing it. Elastic publishes no years of experience requirement anywhere in this advertisement, so we have not assigned one and the role sits in no experience band on our filters. The described scope, which blends strategic QA leadership with hands on validation across an organisation wide portfolio of generative AI solutions, suggests an experienced engineer rather than a first job. Required: proficiency in Python, TypeScript or other languages used in AI and test automation. The ability to design and implement comprehensive test strategies for AI and ML systems, including accuracy, bias, robustness and regression testing. The ability to design and implement self contained evaluation tasks including prompts, supporting files and detailed grading rubrics that assess AI performance on functional workflows. The day to day, from the posting: automating validation suites for agentic and multi agent systems, integration testing, and CI and CD pipelines for ML models; validating that AI and ML models consume accurate, authorised and properly structured data, and ensuring data quality across training and inference; observing and documenting AI agent behaviours and producing precise reports on model performance and hallucinations; validating prompt engineering outputs so responses are grounded in verified data sources; iterating on evaluation tasks and rubrics based on feedback; and ensuring AI data sources meet governance, regulatory and compliance standards. You would work across IT engineering, IT operations, data and integrations, the project management office, CRM, risk and compliance, and business technology, and be expected to stay current on new work in AI and make technical recommendations. Location: Bangalore, India. Honest fit note: this is an internal facing role validating AI systems used across Elastic, including third party SaaS offerings, rather than testing the customer product. The rubric design work is closer to structured evaluation research than to traditional test automation, so it suits someone who enjoys defining what correct even means for a language model. Because no years figure is published, treat the level as genuinely open and worth asking about.
Who this is for: a technical support engineer with about two years of experience who wants to specialise in endpoint security tooling. The requirement is stated as 2 or more years of relevant experience, with 1 or more years in a technical service oriented position listed as preferred, so this is one of the more accessible roles in today's edition. It is also a role type that readers have asked us for by name, so it sits in our customer facing group rather than the main engineering list. Required: a Bachelor's degree in a related field or equivalent business experience, and 2 or more years of relevant experience. Preferred: 1 or more years working in a technical service oriented position. Non negotiable skills, in the posting's own words: hands on experience with SentinelOne, Bitdefender and remote monitoring and management tools. The ability to work independently on projects and processes with general supervision, and practical knowledge of the applicable work area. The day to day, from the posting: providing support to partners with high attention to detail; researching, analysing and documenting findings; interacting with partners by email, phone, chat, cases and remote sessions; maintaining a knowledge base and providing high quality support in each interaction; discussing partners' operational challenges and evaluating business data to identify opportunities; providing guidance and performing regular queue review for junior team members; identifying and escalating trending issues and potential software defects; acting as an escalation point for complex issues; contributing written knowledge base articles; documenting interactions and reporting customer feedback to engineering; and managing a queue of support cases. Location: Mumbai. Honest fit note: the named security tools are described as non negotiable, so this is not a role where general helpdesk experience will substitute. Guiding junior team members and reviewing their queue is part of the job, but there are no reports or hiring duties. Support work is shift and queue driven by nature, and the partner base spans North America, EMEA and APAC.
Who this is for: a technical support engineer with three to six years who wants hardware and software troubleshooting rather than pure software support. The posting states the range as 3 to 6 years of technical support experience, preferably with SaaS or cloud based platforms. Note the role is described in the body as a first level, L1 liaison despite the Senior Technical Support Analyst title, so the title is more senior than the tier. Required: 3 to 6 years of technical support experience, preferably with SaaS or cloud platforms. Good experience of incident management process. Basic SQL knowledge and working experience with one or more databases such as Postgres or MySQL. Familiarity with ITSM tools such as ServiceNow, Jira or Salesforce. Good hands on experience with REST APIs and webhooks. Experience analysing and identifying the root cause of complex customer issues and communicating findings to the right group. Strong problem solving and communication skills, and the ability to work in shifts and under pressure. Strong English communication and prior experience supporting international customers, with US or UK preferred. Nice to have: exposure to cloud technologies and microservices, at least one scripting language such as Python or Shell, familiarity with monitoring tools, and an understanding of network protocols. Shift reality, stated plainly in the posting: this is a 24 hours a day, 7 days a week, 365 days a year operations centre, and candidates must be flexible to work any shift based on business needs, including weekends, Saturday and Sunday. That is disclosed up front and is the main thing to weigh before applying. The day to day: troubleshooting and resolving customer reported issues through Teams meetings, calls, chat and remote tools; root cause analysis and corrective action recommendations; collaborating with engineering, QA and product; supporting rotations including incident escalation handling; maintaining case documentation and timely follow ups; and escalating unresolved or critical issues with supporting technical detail. Location: Bengaluru, Karnataka.
Who this is for: an implementation or professional services engineer with three to six years. The bar is stated as "3-6 years of professional services experience". This sits in our customer facing technical group, which exists because readers asked us for technical account management and customer success roles by name. We should flag one thing plainly: HighRadius runs several other Forward Deployed Engineer advertisements that carry sales quota and target language, and we excluded those. This one, the Engineer I requisition, contains no quota or sales target language at all, which is why it is here. Required: 3 to 6 years of professional services experience. A Bachelor's or Master's degree, with the posting stating a preference for a top reputed university. The ability to write SQL scripts for data gathering and configuration. A good understanding of software development lifecycle processes and functional consulting experience. Very good communication, analytical, problem solving, presentation, organisational and collaboration skills. Exposure to international clients and projects, business analysis exposure and domain knowledge. Experience with order to cash processes. The day to day, from the posting: carrying out end to end client implementations of HighRadius cloud products for Fortune 2000 companies globally; running projects through requirement gathering, design, configuration, testing, cutover, go live and hypercare; building rapport with clients and managing them effectively; conducting user acceptance testing and support shadow sessions; collaborating with product management, engineering, technical teams and QA to deploy projects against agreed measures; testing end to end process flows and driving adoption through hands on end user training; and keeping the delivery manager or programme director informed of implementation risks. Location: Hyderabad, Telangana. HighRadius is India headquartered, reports a 3.1 billion dollar valuation and annual recurring revenue above 100 million dollars, and describes itself as pre IPO. Honest fit note: this is client facing delivery work with travel of attention if not always of distance, and the finance domain matters. If you want to build product, this is the wrong seat. If you like being the person who makes enterprise software actually work for a customer, it is a good example of the type.
Who this is for: a backup and data protection specialist with substantial experience. The bar is stated as a "Commvault or any other backup product experienced professional with 9+ years of relevant experience in Technical Support / Professional Services / Managed Services / Backup Administration". The phrasing matters: experience with any backup product counts, not only Commvault's own. This role sits in our customer facing technical group. Required: 9 or more years of relevant experience across technical support, professional services, managed services or backup administration. Experience troubleshooting infrastructure and product issues. The ability to install and configure backup hardware and software to design specifications meeting technical and business requirements. Experience performing data migrations from previous backup infrastructure. Experience installing and configuring backup agents to protect applications, databases and hypervisors. The day to day, from the posting: interacting with customers by phone and email to solve their problems; troubleshooting and resolving complex customer issues; onboarding new accounts alongside a data protection specialist or the professional services team; working with the customer and Commvault support or development to unblock technical issues; maintaining case ownership and keeping customers updated periodically; architecting Commvault solutions for customer needs and proposing them proactively; developing requirements and designs for software modifications and enhancements and working with developers to implement and test them; and developing subject matter expertise for assigned clients and partners. Location: Bangalore, India. A note on safety, from the posting itself: Commvault opens its advertisement with a recruitment fraud alert, warning that scammers are impersonating its team members over email and text, conducting fake interviews and asking for personal information. It states that Commvault does not conduct interviews by email or text and will never ask for sensitive documents such as banking information before your first day. Worth knowing whoever you are applying to. Honest fit note: this is hands on operational work inside customer environments, with case ownership and direct customer contact, so it suits someone who likes being the expert on call rather than building product. The nine year bar is high for a support oriented title, which tells you the depth expected.
Added September 2, 2026
Who this is for: students graduating in 2027 who want to write high performance systems code. Graviton does not state a years requirement, a degree class, or a minimum CGPA anywhere in this posting, and it does not name a specific language as mandatory. What the work actually is, taken from the posting: designing and building high performance, low latency systems in modern C++; building distributed systems that process and analyse large volumes of market data; designing systems where latency, throughput and reliability directly affect trading performance; working on Linux systems, networking, concurrency and multithreaded applications; profiling systems and optimising at both the hardware and software level; building infrastructure that supports quantitative research and live trading; debugging complex production systems where correctness is critical; designing internal platforms and developer tools; exploring AI assisted developer tools and automation; collaborating with quantitative researchers to turn models into production systems; and taking part in architecture discussions, design reviews and code reviews. What Graviton says it looks for in a person: detail oriented enough to care about edge cases, collaborative enough to challenge and learn from others, and ambitious enough to keep raising the bar. It describes itself as flat by design, with no layers between an idea and the people who can build it. Location and reality check: Gurugram. The firm was founded in 2014 and works across specialised trading teams of researchers and engineers. Because this is a 2027 batch role, expect the offer to be for a start date well after the interview, which is normal for campus hiring at trading firms and is worth confirming with the recruiter before you accept anything. Fit guidance: this suits someone who likes hard, well defined engineering problems (latency, concurrency, memory, throughput) more than product feature work. If your interest is web or mobile application development, the day to day here will not match what you want. No interview process is published in the advertisement.
Required, as printed: a Bachelors in Technology with 2 or more years of professional experience; an understanding of software QA methodologies, tools and processes; knowledge of DBMS and SQL queries, which the posting marks as a must; the ability to write clear, concise and comprehensive test plans and test cases; an understanding of both white box and black box testing; and experience of an Agile or Scrum development process. Good to have, as printed: knowledge of automated testing tools, a basic grasp of performance and security testing, and fundamental working knowledge of JavaScript or Python, which the posting calls a major plus. The real day to day: testing and proving that software meets its major architectural requirements and giving meaningful feedback; creating detailed and well structured test plans and test cases; designing, developing and executing automation scripts using open source tools; identifying, documenting and tracking bugs; performing thorough regression testing after bugs are resolved; developing testing processes for new and existing features to meet client needs; liaising with developers and product managers to identify system requirements; contributing debugging results; tracking quality assurance metrics such as defect densities and open defect counts; keeping up with new testing tools and strategies; and helping business analysts with the right set of data for analysis. Location: Bengaluru. The posting does not state office days or a shift pattern. Fit guidance: this is a good second job for a manual tester who wants to move into automation, because the automation requirement is listed under good to have rather than required, while the SQL and test design requirements are firm. If you have never written a SQL query against a real schema, close that gap before applying. Note on applying: the posting states that by submitting an application you consent to being contacted by the talent acquisition team by phone, email, SMS and WhatsApp.
Required, as printed: 2 to 3 years of experience in cloud networking, infrastructure automation, or DevOps. About the employer, from the posting: Zeta is a next generation banking technology company providing cloud native, fully stackable processing and core banking platforms for issuers, with a focus on scalability, compliance and innovation. It states more than 25 million cards live across 7 countries, a team of over 1,700, backing from SoftBank Vision Fund, Mastercard and other strategic investors, and a valuation of 2 billion dollars reached in 2025. It describes its current focus as modernising legacy systems and strengthening core fundamentals. Location: Hyderabad. The posting does not state office days or a shift pattern. Fit guidance: the band published here is unusually tight at 2 to 3 years, which in practice means the team wants someone who has already run cloud networking in production but is not looking for an architect. If you are at four or five years and applying anyway, expect to be measured against the top of that band rather than given credit for the extra time. If you are at one year, the honest answer is that this posting does not open at your level. What is not published: the advertisement does not name the cloud provider, the automation toolchain, or the interview process. Ask about all three in the first call, because cloud networking skills transfer unevenly between AWS, GCP and Azure.
Required, as printed: 2 or more years of experience in software testing or quality assurance; strong programming knowledge in Kotlin or Java; hands on experience creating and maintaining test plans, test cases and test documentation; a good understanding of software testing methodologies, the software development lifecycle and Agile practices; experience with defect tracking and test management tools; strong analytical, troubleshooting and problem solving skills; and excellent communication and collaboration abilities. Preferred, as printed: experience with CI/CD pipelines, particularly Jenkins; exposure to test automation frameworks and tools; familiarity with API testing tools and methodologies; understanding of version control systems such as Git; and experience working in Agile or Scrum environments. The real day to day: performing functional, integration, regression and end to end testing of applications; identifying, documenting, tracking and validating software defects through the development lifecycle; collaborating with developers and product teams to understand requirements and ensure test coverage; taking part in requirement reviews, sprint planning and release activities; contributing to test automation initiatives; analysing test results and reporting on product quality and release readiness; and supporting continuous improvement of QA processes and standards. Location and terms: the posting states Pune, experience of 2 or more years, and employment type full time, all printed in the job header. Fit guidance: the Kotlin or Java requirement is the filter that matters. Many testers at the two year mark have Python or JavaScript automation rather than JVM languages, and this posting asks for JVM. Automation experience itself sits under preferred, so a strong manual tester who can write Kotlin or Java has a real path here. Note: ConnectWise has a second Software Test Engineer II requisition open in Pune with a different emphasis, asking for 2 or more years of Python and test automation experience. If JVM is not your language, look for that one instead.
Required, as printed: 2 or more years of experience with ServiceNow administration, with CSA certification required, including security administration, creating reports and dashboards, and data configuration; proven ability to troubleshoot and resolve technical issues promptly, with strong communication skills to guide users through resolution; experience monitoring and resolving incidents and providing real time user support in a fast paced environment; the ability to analyse data, identify trends and recommend improvements to workflows, platforms and processes; a collaborative mindset across teams and departments; strong organisation, able to juggle multiple tasks and priorities; and a basic ability to read JavaScript. A plus, as printed: additional ServiceNow certifications beyond the CSA, especially in CMDB, CSM, HRSD, WSD or LSD modules; experience with ServiceNow integrations such as SAP, Workday and NICE InContact; experience testing integrations with tools like Postman; familiarity with Scrum and Program Increment planning frameworks; and experience writing a root cause analysis using the five whys method. The real day to day: managing and resolving L2 incidents, and the technical development and delivery of run the business enhancements and keep the lights on items. The posting describes the role as hands on and customer focused. Location: Bangalore, and the posting carries an onsite tag. Fit guidance: this is a platform support and administration role, not a ServiceNow developer role. If you want to build applications on ServiceNow rather than keep an instance healthy, Everpure has a separate ServiceNow Developer requisition open in the same office asking for 4 or more years. The certification requirement here is a hard gate, so do not apply hoping to pick it up later. One thing worth knowing: the employer trades under the name Everpure in this advertisement and its own applicant tracking record, while parts of the description still refer to Pure Storage. They are the same company.
Required, as printed: a degree in a highly analytical field such as engineering or computer science; 2 to 5 years of experience in Python and shell or bash scripting; experience with Linux and shell or bash command line tools; hands on experience with databases, both SQL and NoSQL; strong problem solving and analytical skills; excellent communication skills; and the ability to remain calm and analytical under production pressure. Good to have, as printed: familiarity with monitoring and alerting stacks such as Prometheus, Grafana and ELK; familiarity with distributed messaging (Kafka) and caching systems (Redis); experience with CI/CD pipelines and deployment automation; and prior experience in a support, SRE or production engineering role. The real day to day: monitoring production services and responding quickly to alerts, incidents and outages to keep operation smooth and downtime minimal; and monitoring trading systems specifically. The posting states that the ideal candidate has a strong background in technical support with a passion for problem solving. About the employer: Graviton Research Capital is a privately funded quantitative trading firm founded in 2014, trading across multiple asset classes and venues using time series analysis, stochastic models, machine learning and statistical inference. Location: Gurgaon, as printed in the advertisement. Fit guidance: read this as an SRE and production support role rather than a development role. If you want to build product features, this is not that. If you like incident work, monitoring and the discipline of keeping live systems up, it is a strong version of that job, and the two to five year band is genuinely open at the lower end. What is not published: shift pattern. Trading systems follow market hours, so ask early whether this seat carries a rota or on call, because the advertisement does not say.
Required, as printed: 2 to 5 years of hands on experience configuring and managing Akamai CDN and WAF solutions in a production environment; a strong understanding of web performance optimisation and security best practices; and a proven track record of implementing and troubleshooting Akamai services in production. The real day to day, taken from the posting: production support, meaning day to day operational support for Akamai CDN and WAF infrastructure, monitoring performance, identifying and resolving issues and implementing changes; performance optimisation, analysing website performance metrics and configuring Akamai features to improve speed and reduce latency; security implementation, managing WAF policies against threats including the OWASP Top Ten, bot attacks and DDoS; rule management, creating, reviewing and maintaining custom WAF rules and exceptions for specific applications and emerging threats; collaboration with development, security and operations teams to integrate Akamai into existing infrastructure and deployment pipelines; troubleshooting complex CDN delivery, caching behaviour and WAF blocking issues; configuring and maintaining monitoring and alerting for Akamai services; and maintaining documentation of configurations, deployment procedures and troubleshooting steps. Location: Noida. The posting does not state office days or a shift pattern. Fit guidance: the title says senior and the requirement says two years, so do not rule yourself out on the title alone. The narrow point is vendor experience. This is not a general infrastructure or security role; the employer is asking for someone who has actually worked in the Akamai control panel in production. If your CDN experience is Cloudflare or Fastly, be upfront about that rather than describing it as equivalent. About the employer, from the posting: Paytm is India's leading mobile payments and financial services distribution company, a pioneer of QR payments in India, building technology for small businesses, with a stated mission of bringing half a billion Indians into the mainstream economy.
Required, as printed: 3 or more years of professional experience in native iOS development, and 2 or more years of hands on experience building production interfaces in SwiftUI. The posting adds that the core qualifications are solid software engineering fundamentals, strong empathy for developers, and a collaborative mindset. The real day to day, taken from the posting: building modular UI, designing and developing composable, high quality UI components from the ground up using SwiftUI; SDK development, shaping and evolving the open source Universal Components iOS SDK and ensuring it integrates cleanly with core identity and authentication services; authoring developer resources, writing and polishing technical content including tutorials, guides, sample applications and documentation; community and advocacy, engaging directly with the open source developer community and providing technical support; code quality and domain expertise, contributing domain knowledge, reviewing code and upholding quality standards across iOS projects; knowledge sharing, representing the team at developer events, community forums or through technical blog posts; and maintenance and modernisation, troubleshooting and maintaining client libraries while keeping up with modern Apple frameworks. Location: Bengaluru, and the posting carries an onsite tag. Fit guidance: a large part of this job is writing for other developers. If you enjoy building an SDK that other engineers depend on and are willing to spend real time on documentation and community work, this is a good fit. If you want to own product screens in a consumer app, the balance here will frustrate you. One practical note: Okta states that a new joiner's journey begins with an immersive in person onboarding experience, so plan for travel or office time at the start regardless of the ongoing arrangement.
Required, as printed: 3 or more years of experience in QA automation or SDET roles. The posting frames the role as shaping and executing an automation first quality strategy across web, API and AI surfaces. Good to have, as printed: using AI agents or tools for day to day activities or to test AI powered features; familiarity with visual regression testing, cross browser testing and performance validation; experience designing or contributing to automation metrics and quality dashboards; exposure to cloud native, large scale SaaS platforms; and experience mentoring teams and driving adoption of quality standards across multiple squads. What HackerRank says you will thrive on: believing quality is a shared responsibility across engineering, QA and product; preferring to prevent defects through strong automation and release gates; enjoying building systems that scale rather than relying on manual effort; being comfortable enforcing 100 percent pass rate mandates for critical workflows; liking complex systems involving CI/CD, containers and AI driven logic; and caring about reliability, trust, accessibility and real world user experience. Location: the posting is listed as hybrid in Bangalore, so expect a set number of office days. The advertisement does not say how many, which is worth asking in the first call. Fit guidance: the 100 percent pass rate line is the one to think about. Teams that enforce that tend to have low tolerance for flaky tests, which is good engineering discipline and also real pressure, because you own the gate that blocks releases. If you like that accountability, this is a strong seat. If your automation experience is a suite that runs nightly and is quietly ignored when red, expect a step up in rigour. About the employer: HackerRank states that software has entered an era where humans and AI build side by side, and positions its products around identifying next generation developer skills.
Minimum qualifications, as printed: 3 or more years of experience at developer level Linux platform experience; strong programming skills in C, C plus plus, Python, Java, Go or other languages, with a solid understanding of object oriented programming; a strong foundation in data structures and algorithms and a strong understanding of threads, synchronisation and concurrent programming; excellent written and verbal communication skills, in order to communicate product architectures and design proposals and negotiate options across stakeholders; and a bachelors degree in computer science, information systems, computer engineering, electronics engineering, electrical engineering or a closely related discipline. Preferred, as printed: hands on development experience in the storage domain and related technologies; experience making strategic architectural decisions and driving design and architecture evolution through architecture forums; and an understanding of production systems and deployments, contributing to high availability and uptime of enterprise infrastructure deployments. The context, from the posting: this is described as an opportunity to be one of the seed members of a growing product team in the FlashBlade business unit, which the company calls one of its fastest growing, building a scale out all flash file and object store designed for the modern world. Location: Bangalore. Fit guidance: the title Member of Technical Staff tells you nothing about level at this company, and Everpure has MTS roles open in the same office at three years and at eight years. Check the requirement line on each one rather than the title. This particular seat is the accessible end of that range. Seed team caveat: joining early on a growing team usually means broader scope and less structure. If you need a defined ladder and an established codebase, weigh that. One thing worth knowing: the employer trades as Everpure in this advertisement while parts of the text still refer to Pure Storage. They are the same company.
Required, as printed: 3 to 5 years of experience in a systems engineering, procurement technology or related role; hands on experience with MCP and with APIs into procurement platforms, with NetSuite and SAP S/4HANA named; hands on experience with AI tools such as Gemini and Claude; comfort working with APIs, light scripting in Python or similar, and system integrations; experience with Google Workspace administration and Slack in a business operations context; strong analytical and troubleshooting instincts with high attention to detail; the ability to translate technical concepts for non technical stakeholders; and the ability to work independently in a remote, globally distributed team environment. Nice to have, as printed: familiarity with supplier management or intake tools such as Graphite Connect and LevelPath; prior experience implementing or administering AI and ML tools in an enterprise setting; exposure to procurement operations, sourcing workflows or indirect spend management; and experience working with or supporting a data science function. The real day to day: implementing, integrating and managing AI tools that improve how the sourcing organisation operates, and serving as a technical point of contact for the Global Indirect Sourcing team on AI tool questions, configuration requests and troubleshooting. Location and office days: the posting states that Everpure is primarily an in office environment and that you will be expected to work from the office in compliance with company policy except for leave or work travel. Note that the sentence still contains an unfilled template placeholder where the office name should appear, so confirm the exact site with the recruiter. Fit guidance: three names appear for one job. The advertisement title says Enterprise AI and Integrations Engineer, the body says Procurement Technology and AI Systems Engineer II, and the company is named both Everpure and Pure Storage in the same text. That is untidy but not a red flag; the requirements themselves are consistent. What matters is the function. This is integration engineering for an internal business team, so your work will be measured by how well procurement runs, not by product outcomes.
Minimum qualifications, as printed: demonstrated curiosity and active exploration of AI tools, with a history of integrating new technologies into daily workflows; a minimum of 4 or more years of relevant experience designing, analysing and troubleshooting large scale distributed systems; deep hands on experience with SRE best practices, Python, Terraform, Ansible, Python automation, networking, Kubernetes and AWS; a comprehensive understanding of web security and core protocols including HTTP, SSL/TLS, DNS, SQL and networking fundamentals; proven experience in observability, building complex dashboards, managing Grafana and a sharp understanding of SLIs, SLOs and error budgets; and strong DevOps skills across CI/CD pipelines, source control management, builds and releases, and continuous integration tooling. Preferred, as printed: advanced knowledge of virtualisation, cloud architecture, modern cloud services and automated deployment. What the company says about itself: Zscaler describes itself as an AI forward enterprise using the world's largest security data lake to power its cloud native Zero Trust Exchange platform, connecting users, devices and applications securely in any location. It states that impact in your role matters more than title and that it values constructive, honest debate. Location: Bangalore. Fit guidance: read the requirement, not the title. Zscaler uses Staff widely and its own postings in this batch range from four years to ten at the same label, so a four year SRE should not self reject here. What will actually be tested is depth: the requirement list is long and specific, and it expects both the infrastructure side (Terraform, Kubernetes, AWS) and the protocol side (TLS, DNS, HTTP) rather than one or the other. On the AI line: several Zscaler postings open with a requirement about curiosity for AI tools. Treat it as a genuine part of the screen and be ready to describe how you actually use them, rather than dismissing it as boilerplate.
Required, as printed: 4 or more years of professional experience in software development, with a strong focus on developing and maintaining automation tools, platforms or microservices for cloud environments; and 4 or more years of hands on experience in Java, Go, Python or similar backend languages, specifically building scalable and reliable platform components, tooling or automation. The real day to day, taken from the posting: leading the design and development of scalable microservices and tools that form the backbone of Okta's continuous delivery platform, including components for Spinnaker, Terraform and custom tooling; developing software solutions and APIs that let engineering teams provision and manage infrastructure, execute production changes and deploy code reliably; contributing to the architectural design and hands on implementation of CD pipelines and Terraform based infrastructure as code workflows, with attention to scalability, reliability and security; writing clean, well tested code primarily in Java, Python or Go for microservices with a focus on automation and self service; and partnering with DevOps, SRE and product teams to find operational bottlenecks and manual processes and then building automation to remove them. Location: Bengaluru. Fit guidance: this is a software engineering role that happens to serve infrastructure, not an operations role. If you are an SRE who mostly configures and scripts, the bar here is higher on software design than you may expect. If you are a backend engineer who is tired of feature work and wants to build platforms, this is the cleaner path in. Who it suits at four years: someone who has already built internal tooling or automation used by other teams. General backend experience without that platform angle will read as thin against this requirement list. One practical note: Okta states that a new joiner's journey begins with an immersive in person onboarding experience.
Required, as printed: a minimum of 4 years of experience working with C sharp and the .NET ecosystem; the ability to work with functional programming using F sharp, or a willingness to learn; very good knowledge of the Win32 APIs; solid knowledge of networking protocols such as HTTP, TLS and WebSockets; experience with different inter process communication mechanisms; writing clean and testable code; past experience working with distributed systems; the ability to use AI assisted code development tools for code generation, analysis and reviews; and having developed code for macOS or Linux. Bonus skills, as printed: knowledge and experience of development tools within the software development lifecycle such as Jira, GitHub and Jenkins; reactive programming experience; experience with AWS cloud infrastructure; and contributions to open source software. Office days: the posting states plainly that this is a hybrid role requiring onsite presence at the Pune office three days per week. About the employer, from the posting: Kaseya describes itself as the leading provider of AI powered IT management and cybersecurity software for managed service providers and internal IT organisations, backed by Insight Partners, founded in 2000, with sustained double digit growth, customers in more than 20 countries and over 15 million endpoints managed. It describes itself as a high growth, high performance organisation. Fit guidance: this is not a typical enterprise .NET job. Win32 APIs, IPC and cross platform work point at agent or endpoint software rather than business applications, which is consistent with what Kaseya sells. If your C sharp experience is ASP.NET web APIs and Entity Framework, the overlap with this list is smaller than the shared language suggests. If you have written Windows services, agents or desktop software, you are the target. One more thing: Kaseya has several engineering requisitions open in Pune at different levels using the same C sharp requirement structure, at 3 years for Software Engineer II and 7 years for Staff. If this one is a stretch or a step down, check the neighbours.
Required, as printed: 4 to 5 years building production frontend applications with strong ownership of what you shipped; deep React expertise covering hooks, rendering behaviour, state management at scale and performance profiling, described as knowing why a component re renders; strong TypeScript, using the type system to make bad states unrepresentable; real command of the browser platform including layout, events, memory and rendering, with comfort using Canvas or SVG for custom rendering; experience with complex, data dense product surfaces such as dashboards, editors, annotation or review tools rather than marketing pages; solid API integration instincts covering async state, caching, polling and streaming, and error and retry handling; and design sensibility, able to take a rough direction and ship something clean without a pixel perfect mock. Bonus points, as printed: experience with PDF rendering in the browser using PDF.js or equivalent, or with annotation and labelling tools; familiarity with WebSockets, server sent events or other streaming transports; exposure to AI and ML product surfaces such as human in the loop review, model output inspection and eval tooling; comfort dropping into a Python or Go backend when it unblocks you; and design systems ownership or strong accessibility practice. The team, from the posting: Sarvam's research teams build their own vision language models for OCR and structured extraction, and this team builds everything around them, described as the serving harness that turns an in house model into a production document intelligence platform, including routing, decomposition, retries, verification, ensembling, layout awareness and confidence calibration. Location: Bengaluru. Fit guidance: Sarvam adds a note that it is looking for people who can own the outcomes described rather than people who match every line of the specification, and invites applications from anyone excited by the problem. Take that at face value, but be honest with yourself about the two firm parts: data dense product surfaces and real browser platform depth. A CV of component libraries and CRUD screens will not carry this.
Basic qualifications, as printed: a bachelors degree in computer science, cybersecurity, engineering or a related field, with equivalent experience considered; 4 to 6 years of experience in security operations, security engineering, incident response or related roles; willingness and ability to work in a 24 by 7 SOC on a rotating shift schedule including night shifts, weekends and holidays; hands on experience with alert triage, investigation and incident response in a SOC environment; experience building and tuning detections in SIEM and EDR platforms and reducing false positives, with familiarity with MITRE ATT&CK; experience conducting threat hunts using endpoint, network, cloud and identity telemetry and translating findings into detections; and experience with malware analysis including static and dynamic analysis, sandboxing tools and IOC extraction, with familiarity with sandbox environments, YARA and disassemblers or debuggers. Other responsibilities named in the posting: contributing to threat modelling and risk assessments for new projects and technologies; supporting compliance requirements including SOC 2, ISO 27001 and NIST; creating and maintaining security documentation, runbooks, playbooks and knowledge bases to support consistent shift handoffs; providing guidance and mentorship to junior engineers and analysts including during shift operations; and staying current on emerging threats, detection techniques and AI driven security tooling. Shift reality: this is the part to weigh hardest. A rotating 24 by 7 roster with nights, weekends and holidays is stated twice in the advertisement. It is not an occasional on call arrangement. Location: Bangalore. Fit guidance: the II in the title is meaningful here, unlike at some employers. This is a mid level detection engineering role, not a level one alert triage seat, and it expects you to write detections rather than only work the queue. The mentoring line means juniors will look to you on shift. One practical note: Tekion states that current employees should apply through its internal job board rather than this posting.
Required, as printed: a BTech, BE or higher technical education in computer science, artificial intelligence, machine learning or a related field; a total of 4 or more years of relevant experience in design, development and implementation, with at least 1 year of experience in Workato specifically, which the posting marks as a must; proven experience in AI engineering with a focus on agent based systems; demonstrated ability to design and implement scalable AI driven workflows that enhance IT operations; knowledge of implementing integration projects, described as essential; hands on experience with automation technologies, middleware, integration architecture patterns, web services, enterprise messaging patterns, APIs, SOA, ESB, BPM, SDKs and databases; strong working knowledge of RESTful and SOAP/XML APIs; a solid understanding of JSON data structures; sound knowledge of any relational or NoSQL database; and hands on experience with Java, Python or Ruby. A plus, as printed: experience with integration platforms such as Workato, TIBCO, Dell Boomi or MuleSoft; experience with cloud technologies including iPaaS, SaaS applications and cloud infrastructure; a technical background in the application integration space; and experience with cloud business applications such as Workday, NetSuite and Salesforce. Location: Hyderabad. Read the numbers carefully: the four years is the requirement and the one year is a subset of it. Automated job parsers routinely get this backwards and publish this role as open to someone with a year of experience. It is not, and applying on that basis wastes your time and theirs. Fit guidance: forward deployed engineering is customer facing build work. You are writing real integrations for named enterprises, which means travel, meetings and requirements gathering alongside the engineering. If you want to sit with a codebase and no customers, this is not it. If you like solving a different company's problem every quarter, it is a good version of that. About the employer, from the posting: Workato describes itself as the control and execution platform for enterprise AI, unifying data, applications and processes so AI can orchestrate business processes at enterprise scale, built on more than a decade of running mission critical processes, turning over 14,000 enterprise systems into one governed execution layer.
Required, as printed: a BS or above in computer science or a related field, with an MS or PhD preferred; 5 or more years of experience developing search relevance systems at scale in production or in high impact research environments; experience applying LLMs to search relevance; experience in one or more of query understanding, NLP, text mining, recommendations, personalisation, discovery or conversational AI; a strong understanding of computer science fundamentals; and contributions to well used open source projects. The real day to day: driving the development and deployment of ML based search and discovery relevance models and systems integrated with Databricks products; and designing and implementing automated ML and NLP pipelines. The posting states the team is hiring multiple senior engineers to drive search quality improvements, and that the 2026 focus is enhancing search ranking, improving query understanding, building robust evaluations and growing asset coverage. Location: Bengaluru. The posting does not state office days. Fit guidance: read the requirement precisely. It is not five years of general backend or general machine learning; it is five years of search relevance specifically. Adjacent experience in recommendations, ranking or personalisation is explicitly accepted, and the alternative route through high impact research rather than production is unusual and genuinely open, so a strong research background counts here in a way it does not on most postings. The open source line: contributions to well used open source projects sits in the required list rather than the preferred list. That is worth noting because most postings put it under nice to have. If you have none, expect to be asked about it. About the employer: Databricks is headquartered in San Francisco with more than 30 offices, and its platform includes Genie, Lakebase, Agent Bricks, Lakeflow, Lakehouse and Unity Catalog.
Technical requirements, as printed: Python expertise, meaning 5 or more years of professional experience with deep knowledge of Python 3.x and its advanced concepts including decorators, generators and context managers; framework mastery, meaning extensive experience with Flask and its ecosystem including Flask SQLAlchemy, Flask Migrate and Flask RESTful or Marshmallow; solid programming fundamentals covering data structures, algorithms and object oriented programming; testing, meaning proficiency writing unit, integration and functional tests using PyTest or Unittest; asynchronous processing, meaning experience with Celery and message brokers such as RabbitMQ or Redis for background tasks; and database knowledge, meaning a deep understanding of ORMs and raw SQL, with experience of migrations and database design. Preferred, as printed: experience with architectural patterns such as microservices or domain driven design; familiarity with CI/CD pipelines including Jenkins, GitHub Actions and GitLab CI; and an understanding of authentication protocols such as OAuth2 and JWT. The role, in the posting's own framing: leading the design and development of robust, scalable web applications, responsible for server side logic and for ensuring high performance and responsiveness to requests from the front end. Location: Hyderabad. Fit guidance: the Flask requirement is the real filter. Flask has been less fashionable than FastAPI for new services for several years, so a lot of five year Python engineers have limited Flask time. If that is you, be straightforward about it; the underlying skills transfer, but do not claim mastery you do not have, because Flask SQLAlchemy and Flask Migrate specifics are easy to test in an interview. About the employer: HighRadius states a 3 to 6 month go live period for customers and says it guarantees operational improvements by mapping them to specific agents on the platform. It has been recognised as a market leader by Gartner, IDC and Forrester. What is not published: office days, shift pattern and the interview process do not appear in this advertisement. HighRadius states five days a week in the office on some of its other engineering postings, so confirm the arrangement for this team before you accept.
Required, as printed: typically 5 or more years of software development experience in fast paced environments; a demonstrated passion to learn how large scale software engineering projects work; the ability to lead and mentor junior team members; an ability to write, test and deploy well structured and performant code; experience developing data processing systems, preferably for an external facing product; strong technical communication skills in English, written and verbal; proficient level programming in an object oriented or systems language such as Java, Python or C sharp; experience with end to end systems profiling, performance and optimisation; experience troubleshooting problems with existing code and systems; and experience working in a cloud environment using AWS, GCP, Postgres, Kubernetes, Docker or similar. Bonus skills, as printed: experience with SQL Server, Oracle, Postgres, MySQL, MongoDB or CosmosDB; and having developed ETL or ELT pipelines. Technologies named: Java, SQL Server, SQL, Docker, AWS, GCP, BuildKite, DBeaver and Grafana. The real day to day: working through requirements, design, prototype, implementation, review, release and monitoring; reviewing and approving technical design documents and pull requests; improving engineering systems documentation and development processes; coaching and mentoring other software engineers; and contributing to hiring by taking part in interviews. Note that the hiring line means interviewing, not managing. Office days: the posting states a hybrid work model including two days in the office each week. The word remote appears in this advertisement only in the context of that hybrid flexibility, so do not read it as a remote role. Company change worth knowing: the posting states that Fivetran and dbt Labs are bringing together two companies with a shared mission, delivering the data infrastructure layer that helps organisations move, transform and trust their data. If you interview here, both brand names may come up. Benefits named: 100 percent employer paid medical insurance and a generous paid time off policy.
Required, as printed: a strong understanding of RAID, LVM, NFS, iSCSI, multipathing and file systems including ext4, XFS and ZFS; hands on experience with enterprise storage systems and clustering technologies; proficiency in shell scripting, with Python, Puppet or Ansible knowledge; experience with virtualisation technologies such as VMware or KVM; familiarity with cloud storage solutions such as AWS S3 and EBS; and experience with monitoring tools such as Nagios, Prometheus and Zabbix. Part of the work described is automating storage provisioning and management using scripting or infrastructure as code. Note on the text: the requirement line about file systems ends with an unfilled template placeholder in the published advertisement, where the word MANDATE appears in braces. It is a drafting artefact rather than a requirement. The team, from the posting: this team is part of Platform Engineering in India, whose stated purpose is to enable Adyen engineers to autonomously build and support secure, scalable and reliable applications at speed. Interview process, published in the advertisement: Adyen states it aims to respond to applications within 5 business days, and that the interview process tends to take about 4 weeks to complete. That is genuinely useful information and rare to see printed. Remote reality: Adyen states that it does not offer remote only roles. If you need fully remote work, this is a clear no rather than a maybe. Fit guidance: Adyen includes a note that studies show women and members of underrepresented communities apply only when they meet 100 percent of the qualifications, and encourages people who do not to apply anyway. The list above is broad, and few candidates will have all of Ceph, ZFS, VMware, KVM and the full monitoring set. Treat storage fundamentals plus Linux depth as the core, and the rest as things you can be taught. Location: Bengaluru.
Required, as printed: 5 or more years building large scale data, ML or platform systems. The posting also states that the role includes mentoring engineers and championing MLOps and AI safety best practices. About the employer and the data, from the posting: Tekion describes itself as having disrupted an industry that had not seen innovation in over 50 years, with the first and fastest cloud native automotive platform. Its products are Automotive Retail Cloud for retailers, Automotive Enterprise Cloud for manufacturers and other large automotive enterprises, and Automotive Partner Cloud for technology and industry partners. It states that the platform uses big data, machine learning and AI to bring together OEMs, retailers and consumers, and that it employs close to 3,000 people across North America, Asia and Europe. Location: Bangalore, listed as the company headquarters. Fit guidance: the phrase to weigh is large scale data or ML or platform systems. Tekion is asking for someone who has built the machinery around models, not only notebooks and experiments. If your experience is model training with someone else handling deployment, the MLOps and mentoring expectations here will stretch you. If you have owned a model from training through serving and monitoring, this reads directly onto your work. The domain angle: automotive retail is an unfashionable but data rich problem space, covering dealership operations, parts, service and customer engagement. If you want applied ML where the dataset is genuinely proprietary rather than a public benchmark, that is the argument for this role. One practical note: Tekion states that current employees should apply through its internal job board rather than this posting. Several other Tekion engineering roles are open in the same office at different levels, so check the requirement line rather than the title if this one does not fit.
Key skills, as printed: 5 to 8 years of experience; extensive experience with Go, Python or C plus plus; experience on operating systems, both Unix or Linux and Windows; experience leveraging AI tools in daily tasks; and hands on experience in networking and multithreading. Desirable, as printed: experience in cloud technologies and systems programming. Qualification, as printed: BTech, BE, ME or MTech in computer science or equivalent. The real day to day: playing a key role in the design and development of the Enterprise Workload product; responsibility for the complete software development cycle; gathering and understanding requirements; design, development and implementation independently; ensuring timely and quality delivery; and working on end to end features. The posting also states that you will guide and mentor junior team members by reviewing their code and designs, and that the role requires excellent communication skills because you will collaborate across teams. About the product, from the posting: Enterprise Workload is a unified server backup and archival product built on Druva's platform. The wider platform is described as the resilience foundation for the AI enterprise, powered by Dru MetaGraph, its graph based intelligence layer, connecting business context so customers can understand risk, respond faster and recover cleanly. Location: Pune. Fit guidance: the title reads far more senior than the requirement. Five to eight years is a mid to senior band, and the mentoring expectation is code and design review rather than people management, so this remains an individual contributor role. If you are at five years and the title put you off, apply anyway. Note on the AI requirement: experience leveraging AI tools in daily tasks appears in the required key skills list, not in the nice to haves. Be ready to describe how you actually use them and how you check their output. One more thing: Druva has several Senior Staff Software Engineer requisitions open across Pune and Hyderabad with different bands, including one at 6 to 9 years and one at 6 or more. Check the band on the specific posting rather than assuming they match.
Required, as printed: 6 or more years of experience in data engineering, data platforms and analytics, or software engineering; comfort writing code in Python, Scala or JavaScript and TypeScript and modern frameworks; working knowledge of two or more common cloud ecosystems (AWS, Azure, GCP) with expertise in at least one; deep experience with distributed computing using Apache Spark and knowledge of Spark runtime internals; familiarity with CI/CD for production deployments; working knowledge of MLOps, ML and AI models and AI APIs; design and deployment of performant production end to end data architectures and applications combining data pipelines, ML and AI models and user facing interfaces; experience with technical project delivery covering scope, timelines and measurable outcomes; documentation and whiteboarding skills; experience working with enterprise clients and managing conflicts across a broad stakeholder range; a willingness to build skills in new technical areas; travel to customers 20 percent of the time; and Databricks certification. The role, in the posting's framing: working with customers to build and productionise solutions to their data and AI challenges on the Databricks platform, owning architecture, leading design decisions and implementing end to end systems. It describes the work as cross functional with engineering, product and developer relations, and as hands on and customer facing for builders who thrive at the intersection of technology and business impact. Location: Bengaluru, with 20 percent customer travel stated. Fit guidance: this is a hybrid of consulting and engineering. If you want to go deep on one codebase for years, it will not suit you. If you like landing in a new problem domain repeatedly, shipping something that works and moving on, it is one of the better paid versions of that career. The Spark runtime internals requirement is the technical filter and is not satisfied by having written Spark jobs. On certification: Databricks certification appears in the requirement list. If you do not hold one, it is achievable before or shortly after joining, but raise it rather than ignoring it.
Required, as printed: 6 to 10 years of experience; a bachelors or masters degree in engineering, specifically computer science or information systems; excellent communication skills and a sense of ownership, with a systematic problem solving approach. About the employer, from the posting: Zeta is a next generation banking technology company providing cloud native, fully stackable processing and core banking platforms for issuers, focused on scalability, compliance and innovation. It states over 25 million cards live across 7 countries, more than 1,700 staff across India, the US, EMEA and Asia, backing from SoftBank Vision Fund, Mastercard and other strategic investors, and a 2 billion dollar valuation reached in 2025. It describes its current focus as addressing real customer pain points, modernising legacy systems and strengthening core fundamentals. Location: Hyderabad. What is not published, and should be asked: this advertisement is unusually light on technical specifics for a senior SRE role. It does not name the cloud provider, the orchestration platform, the observability stack, the on call rota or the interview process. None of that is a reason to avoid the role, but all of it is worth asking in the first conversation, because SRE work varies enormously depending on those answers and a payments platform will almost certainly carry an on call rotation. Fit guidance: Lead in this title should be read as senior individual contributor with technical direction rather than people management, since the posting describes no reports, no hiring and no performance responsibilities. If you are looking for a first management step, ask directly whether that path exists here rather than assuming the title implies it. Why the domain matters: banking infrastructure gives you scale and regulatory constraint at the same time. That combination is rarer than either alone, and it is the strongest argument for taking a reliability role here over one at a general SaaS company.
Required, as printed: 6 or more years of experience developing and debugging system level software in Golang or a similar language; familiarity with distributed systems managed via Kubernetes; a demonstrated ability to design and build highly reliable, high performance system software; experience working in environments where performance, scalability and reliability are critical; and a bachelors degree in computer science or equivalent practical experience. Preferred, as printed: experience building cloud native SaaS platforms; experience working with frontend web frameworks such as React; and a background with cloud based metering and billing and generally accepted accounting practices. The real day to day: turning requirements into robust technical solutions; investigating and resolving difficult issues in production and development environments while balancing multiple responsibilities; investigating, debugging and fixing issues with billing data synchronisation; contributing to data visualisation dashboards; and mentoring and guiding engineers on system design, coding standards and architectural best practices to raise the technical bar across the team. About the employer, from the posting: SingleStore engineers build the real time data platform behind demanding applications, with a cloud native architecture supporting high performance transactional and analytical workloads at scale. It states that teams ship production code continuously through the year and that engineers own their work end to end while partnering across product, sales and go to market. Location: the requisition lists United States, Portugal and India together, so confirm the India work location and any timezone overlap expectation early. Fit guidance: the title covers two levels, Senior and Principal, on one requisition, which usually means the level is decided by how you interview rather than fixed in advance. That is an advantage if you are between levels. The billing and metering detail in the responsibilities is worth noticing: this is not pure query engine work, and part of the surface is the commercial plumbing around the database.
Required, as printed: 7 or more years of experience as a backend developer with a strong focus on services development; proficiency in at least one backend programming language and its ecosystem, with Java, Node.js and Python named, plus a demonstrated ability to ramp up quickly in unfamiliar languages, frameworks and systems; a solid understanding of services architecture principles; proficiency in RESTful API design and development; strong proficiency in relational database querying and performance tuning, specifically the ability to reason about indexing strategies, shard key design, query execution plans and connection pool management; experience with both SQL databases (SingleStore, MySQL named) and NoSQL databases (MongoDB named), including designing efficient data models and caching strategies with Redis; hands on experience integrating with LLM and generative AI services, including prompt engineering, tools, agents and validating LLM generated outputs such as SQL query safety validation before execution in production; the ability to work independently and deliver in short timelines; the ability to technically lead and mentor juniors and drive planning and execution; experience with containerisation and orchestration tools; strong problem solving and debugging skills; experience with a public cloud platform; and excellent communication and collaboration skills. The real day to day: designing, developing and maintaining high quality services following best practices and coding standards, and collaborating with team members and stakeholders on design. Location: Bengaluru. Fit guidance: two requirements narrow this more than the years figure does. The database tuning list is specific enough that generic ORM experience will not pass it, and the LLM integration requirement asks for production experience rather than familiarity, including the safety validation step, which is a real engineering concern rather than a buzzword. If you have shipped an LLM feature and had to stop it doing something dangerous, say exactly that. Note on applying: this posting is served from a career page that blocks automated requests, so the link may behave oddly in some browsers. The role itself is live and confirmed open on the employer's applicant tracking system. One more thing: ZoomInfo has several similar senior requisitions open in Bengaluru and Chennai, including DevOps at 7 or more years and quality automation at 5 or more.
Required, as printed: at least 8 or more years of experience in software engineering; you have designed, built, scaled and maintained production services and know how to compose a service oriented architecture; you write high quality, well tested code; you possess strong technical skills for system design and coding; excellent written and verbal communication skills with a bias toward open, transparent cultural practices; a passion for building an open financial system; and responsible use of generative AI with human oversight to deliver business ready outputs. The team, from the posting: Coinbase states that it stores a large amount of digital currency, making it a top tier target on the internet, and that security is core to its mission and a key competitive differentiator as it scales. The Security Platform Engineering team builds platform capabilities for a variety of security use cases. Remote reality, stated by the employer: Coinbase describes itself as remote first but not remote only, and says to expect quarterly in person working sessions it calls surges. The role is listed as Remote in India and carries a remote tag. This is one of the few genuinely remote roles in this edition, and the caveat is quarterly travel rather than weekly office days. Pay, published in the advertisement: an annual base salary of 9,424,500 rupees, excluding equity and bonus. Coinbase states that total compensation may also include equity, bonus eligibility and benefits including medical, dental and vision. Published pay is rare enough in Indian job advertisements to be worth naming. Application limit, published: Coinbase states that candidates may submit a maximum of 3 applications within a 6 month period. Choose carefully rather than applying to everything open. Culture warning, in the employer's own words: the posting says the bar is high, the environment is intense, and that this is not a place for complacency but a place to be pushed past your perceived limits. Take that seriously as a description of pace and expectations rather than as marketing. Location: remote within India.
Must have, as printed: a minimum experience of at least 8 years; strong hands on programming skills in Golang; deep, practical knowledge of identity protocols OIDC, OAuth 2.0 and SAML 2.0 including token and assertion internals, standard flows and failure modes; working knowledge of Active Directory; applied cryptography and PKI experience covering X.509, JWT and JWKS, key rotation and TLS; strong security engineering discipline, comfortable reasoning about threat models and building software to protect mission critical systems rather than only making features work; a solid understanding of operating system fundamentals, networking and concurrency; working knowledge of Linux with comfort writing shell or bash scripts; and simple, effective written and verbal communication. Nice to have, as printed: directory internals covering schema and bind operations; HTTP internals and reverse proxying including TLS and header injection; build, release and cross platform packaging for Linux deb and rpm and Windows MSI; secret manager internals, Redis, Win32 and policy engines; and basic C sharp or .NET to maintain a companion application. The real day to day: designing, building and hardening identity and access flows that sit in front of mission critical systems; owning token and assertion lifecycle correctness including issuance, validation, expiry, rotation and failure mode handling; applying cryptography and PKI practice to keep the authentication path secure by default; building and maintaining reverse proxy and HTTP layer components including TLS termination and header handling; debugging customer facing identity and access issues alongside support; contributing to build, release and cross platform packaging; maintaining a small Windows companion application in C sharp; writing end to end tests covering authentication flows and edge cases such as clock skew, revoked tokens and malformed assertions; and documenting known issues and design decisions. Location: Bangalore. Fit guidance: identity protocol depth is the gate. Plenty of senior Go engineers can build services; far fewer can explain what happens when a SAML assertion arrives with clock skew, or why a JWKS rotation broke a client. If that is your area, this is a strong match. If it is not, the eight years alone will not carry you. Worth knowing: Rubrik has a second requisition on the same team in Pune, titled simply Software Engineer, with an almost identical must have list. The only substantive difference is that the Pune posting states no years requirement at all.
Required, as printed: cloud native application development experience using best practices and design patterns; strong debugging and troubleshooting skills across the entire technology stack; a deep understanding of AWS networking, compute, storage and managed services; competency with modern CI/CD tooling such as Kubernetes, Terraform, Ansible and Jenkins; experience with full lifecycle support of services from creation to production support; infrastructure as code practice using Terraform or CloudFormation; the ability to author production ready code in at least one of Java, Scala or Go; experience with Linux systems and comfort on the command line; an understanding of modern approaches to cloud native software security; experience with agile frameworks such as Scrum and Kanban; flexibility and willingness to step into new roles; a willingness to learn and use Sumo Logic products for solving reliability and security issues; a bachelors or masters degree in computer science, electrical engineering or another scientific or technical discipline; and 8 or more years of professional experience in an applied software security role. Desirable, as printed: experience using Sumo Logic products or other observability products for reliability and security; and experience with planet scale production systems. The real day to day: supporting engineering teams within your product area by maintaining and executing a reliability roadmap; working alongside a global SRE team; optimising operations and increasing efficiency in the use of cloud resources and developer time; hardening security posture; and working closely with multiple teams to optimise the operations of their microservices. Location: the job header states Noida or Bangalore, hybrid, while the posting is listed under Noida. Confirm which site applies. Fit guidance: the security framing of the years requirement is unusual and worth reading twice. If your background is pure SRE with limited security work, address that directly in your application rather than hoping it is a typo, because the desirable list also leans on security. Conversely, if you are a security engineer with strong infrastructure skills, this posting is more open to you than the title suggests. Global team note: this is described as a globally distributed SRE function, so ask about timezone overlap and on call rotation, neither of which the advertisement specifies.
Required, as printed: a bachelors or masters degree in computer science, information technology or a related field, with an educational background from a highly selective, premier engineering institution with a focus on computer science fundamentals stated as preferred; 10 or more years of professional software engineering experience; a strong understanding of data structures, algorithms, design patterns and both object oriented and functional programming; a proven track record of leading technical initiatives from conception to global production deployment; deep expertise in Java and modern web technologies; extensive experience building and scaling distributed systems in AWS cloud native environments and modernising applications and platforms; strong knowledge of enterprise application architecture; and experience managing large scale codebases where performance optimisation and bottleneck identification are critical. Preferred, as printed: experience in AI and ML integration, specifically implementing intelligent features such as retrieval augmented generation or agentic workflows into enterprise software; and experience using AI tools and models such as Amazon Q, Kiro and Claude. Technical skills named: expert level proficiency in Java or similar major languages, and hands on experience with Docker and Kubernetes for infrastructure and orchestration. The mission, in the posting's own framing: to be the technical anchor for the most ambitious engineering initiatives, ensuring the platform is fast, scalable and resilient regardless of the complexity customers demand, and leading the design and orchestration of high stakes systems. Location: Chennai. Fit guidance: note the preference for a premier engineering institution background. It is stated as preferred rather than required, so it is not a hard gate, but it is unusual to see it printed at all and it tells you something about how the team screens. Weigh that against the strength of your production track record, which is what the rest of the list actually measures. Lead here reads as individual contributor technical leadership, not people management: the responsibilities describe leading design and orchestration of systems, with no reports, hiring or performance duties mentioned.
Required, as printed: 10 or more years of software engineering experience, with 4 or more years in a principal or staff role focused on large scale SaaS; and a BS or MS in computer science or equivalent practical experience. The role, in the posting's framing: leading the evolution of Ping Identity's global, multi tenant SaaS platform, with responsibility for the high level design and technical roadmap of systems that power millions of identities, ensuring massive scalability and high velocity delivery. The responsibilities section is headed architecture and strategy. About the employer, from the posting: Ping Identity describes its goal as making digital experiences both secure and seamless, which it calls digital freedom. It is headquartered in Denver, Colorado, with offices and employees globally, and states it serves the largest enterprises worldwide including more than half of the Fortune 100. One of its stated core values is Respect Individuality. Location: Bengaluru. Fit guidance: the four years at principal or staff level is the clause to weigh honestly. Companies write this when they have been burned by hiring someone with long tenure but no architecture ownership. If your ten years are all senior engineer, expect that to be probed. If you have led platform architecture across teams, this posting is aimed squarely at you. What the company says about working there: a culture it describes as empowering people to do their best work, employee resource groups, regular company and team bonding events, competitive benefits, global volunteering and community initiatives, and a generous paid time off and holiday schedule. It describes itself as growing quickly while keeping startup values. What is not published: office days, the on call expectation and the interview process do not appear in this advertisement. Ping Identity has a second requisition open in the same office titled Staff Software Engineer with the same 10 or more years requirement and 4 or more years at staff level, so if the principal framing is a stretch, that one is worth comparing. Why identity is a good domain for this level: identity systems fail in ways that lock legitimate users out or let the wrong ones in, so architecture decisions carry weight that is easy to explain to any interviewer and hard to fake.
Required, as printed: 15 or more years of industry experience building and supporting large scale distributed systems; comfort working towards a multi year vision with incremental deliverables; motivation from delivering customer value and impact; a strong foundation in algorithms and data structures and their real world use cases; and experience driving company initiatives towards customer satisfaction. The level, in the posting's own words: as an executive engineering individual contributor at Databricks, you will have full ownership of the product or infrastructure direction in a major area, driving it from initial development to scalable solutions with clear business impact. You serve as a force multiplier by elevating stability, reliability and organisational processes while bringing deep expertise in large scale distributed systems. You mentor senior engineers, contribute to recruiting and lead high impact company projects, often tackling complex problems beyond their comfort zone. The posting states the role reports to an engineering leader. Location: Bengaluru. Fit guidance: the fifteen year figure is the highest in this edition by some distance and it is stated as a plain requirement rather than a preference. Unlike several other postings here where a senior sounding title hides a four or five year bar, this one means what it says. Contributing to recruiting means interviewing, not managing, so this remains an individual contributor track. Who this actually suits: someone who has already been the technical owner of a major system at a large company and wants the same scope without moving into management. The multi year vision line is a fair description of the work, so if you prefer quarterly deliverables and tight feedback loops, weigh that. About the employer: Databricks is headquartered in San Francisco with more than 30 offices worldwide. Its platform includes Genie, Lakebase, Agent Bricks, Lakeflow, Lakehouse and Unity Catalog, and customers named in the posting include adidas, AT&T, Bayer, Block, Mastercard, Rivian and Unilever.
What GitLab says you will bring, as printed: professional backend engineering experience delivering production features and components at scale, with clear ownership of outcomes rather than tasks; hands on PostgreSQL experience including query profiling and optimisation, indexing and schema design decisions, with an interest in growing into a domain expert; professional experience with Ruby on Rails, Go or Python, comfort working in Ruby on Rails day to day, and interest in working across languages and services; evidence of guiding peers through complex work or independently carrying out a delivery plan; the ability to collaborate with a range of partners and explain technical tradeoffs clearly; a self directed approach with proactive communication about decisions, progress and blockers; experience using security tooling for vulnerability triage and remediation, or building vulnerability management, dependency management or related security products; and fluency using artificial intelligence tools to improve delivery while applying sound engineering judgment. Experience with large monoliths is described as helpful. No years figure appears in this posting. GitLab describes capability instead. If you are trying to judge whether you are at the right level, the phrases to weigh are delivering production features at scale, clear ownership of outcomes rather than tasks, and guiding peers through complex work. The team, from the posting: Vulnerability Management owns the data layer behind GitLab's vulnerability and dependency management capabilities, including security report ingestion, storage, indexing and querying, and contributes to GitLab's move toward modular services. Remote reality, stated by the employer: GitLab states that all of its roles are remote, though some may carry specific location based eligibility requirements. This is a genuinely remote role, not a hybrid one described loosely. About the employer: GitLab describes itself as the intelligent orchestration platform for DevSecOps, with more than 50 million registered users and more than half of the Fortune 100 as customers. It states that all team members are expected to incorporate AI into their daily workflows. Fit guidance: the security domain experience is listed as one requirement among many, and GitLab explicitly welcomes transferable experience from outside security on its sibling posting for the same team. If you are a strong Rails and PostgreSQL engineer without security background, apply and let them judge.
What GitLab says you will bring, as printed: experience leading complex backend projects from idea through delivery while remaining hands on with design and development; strong PostgreSQL experience including evidence of query optimisation, table optimisation and write ahead log management in data intensive systems; strong professional experience with Ruby on Rails, Go or Python, and comfort working in Ruby on Rails day to day; experience with large monoliths, described as helpful, along with interest in working across languages and services; experience shaping delivery plans, guiding technical decisions and supporting the work of other engineers; the ability to collaborate with a range of partners and explain technical trade offs clearly; experience communicating with leaders, leading peers through complex delivery, identifying constraints and moving work forward; experience using security tooling for vulnerability triage and remediation, or professional experience building vulnerability management, dependency management or related security products; experience with large scale data systems or established software products; and fluency using artificial intelligence tools to improve delivery while applying sound engineering judgment. The posting explicitly welcomes transferable experience from outside the security domain, which is worth knowing if the vulnerability management framing is putting you off. No years figure appears in this posting either. The level is described through scope: leading complex projects, guiding technical decisions, supporting other engineers, and communicating with leaders. Note that supporting the work of other engineers here is technical leadership, not people management, and no reports or hiring responsibilities are mentioned. The team, from the posting: Vulnerability Management contributes to GitLab's move toward modular services and owns the data layer behind vulnerability and dependency management. Remote reality, stated by the employer: all GitLab roles are remote, with some carrying location based eligibility requirements. Fit guidance: if you are weighing this against the senior posting on the same team, the honest test is whether you have owned a project end to end including its plan, its trade offs and the other people working on it. If you have, apply here. If you have delivered strong features inside someone else's plan, apply to the senior one. Applying to both is reasonable, and the team is clearly hiring at more than one level.
What GitLab says you will bring, as printed: professional experience working in Ruby on Rails and PostgreSQL or similar relational databases in production environments; experience integrating with third party or enterprise APIs and designing REST and GraphQL contracts including versioning and backward compatibility; familiarity with event driven patterns such as webhooks and message based streaming; experience with data integrity and governance concepts; curiosity to understand how systems work as a whole, and experience owning a project from concept to production including proposal, discussion, execution and monitoring; the ability to communicate clearly and concisely about complex technical, architectural and organisational problems, in written and verbal English, in a remote and largely asynchronous environment; and the ability to collaborate effectively in that environment. Experience with NATS JetStream, or with subscription management or billing systems such as Zuora or Salesforce, is listed as a plus. No years figure appears in this posting. The team, from the posting: this role sits on the Monetization Platform Integrations team, which partners with sales, finance, IT and support to deliver secure and reliable purchasing, billing, provisioning and utilisation workflows. The wider Monetization section includes purchase, subscription lifecycle, billing engine, platform and infrastructure, observability, monitoring and integrations, and compliance teams. Remote reality, stated by the employer: all GitLab roles are remote, with some carrying location based eligibility requirements. Note that this posting lists asynchronous written communication as an actual requirement rather than a perk, which is a fair warning: in an all remote company with a wide timezone spread, writing clearly is part of the job rather than an adjacent skill. Fit guidance: do not dismiss billing as boring engineering. Subscription and provisioning systems combine third party integration, event driven architecture and strict correctness requirements, and the experience transfers well to any company that charges money. If you have worked with Zuora, Salesforce billing or similar, say so early, since the posting names them. About the employer: GitLab describes itself as the intelligent orchestration platform for DevSecOps, with over 50 million registered users.
What Smartsheet says you have, as printed: proven experience in system architecture and the design of scalable, high availability systems across multiple programming languages and frameworks, with Python, Go, Java, C and C plus plus and SQL named; deep hands on expertise in identity and access management including authentication protocols SAML, OIDC and OAuth 2.x, SCIM based provisioning, session management and multi factor enforcement at enterprise scale; demonstrated experience designing identity strategy for agentic and AI driven systems including machine identities, delegated authorization, token exchange, scoped agent credentials and auditability of autonomous actions; a deep understanding of distributed systems, event driven architectures and microservices; and strong experience in technical leadership. Fluency in English is stated as required. The real day to day: collaborating with product management and business stakeholders to balance market needs against technical constraints; driving the strategic integration of AI capabilities into complex multi system architectures, defining patterns and best practices and leading AI initiatives to address technical challenges and improve productivity across groups; and advocating for quality and operational excellence, ensuring systems are monitored, tested and maintained to high reliability standards. No years requirement appears anywhere in this posting. The only figure resembling one is the sentence stating that Smartsheet has empowered teams for over 20 years, which describes the company's age and not the job. Automated parsers frequently mistake that line for a requirement. Location, and a contradiction to resolve before applying: the job title states hybrid in Bangalore, and the location field says Bangalore, India. The body of the advertisement carries a remote tag. Those cannot both be true, and the title is the more specific statement, so plan for hybrid and ask the recruiter to confirm the office day expectation. About the team: Smartsheet describes its India Global Capability Center as having scaled rapidly into a hub delivering product innovation and enterprise capabilities, and says it is specifically looking for principal engineers with identity and access management expertise as it expands in India. Fit guidance: the agentic identity requirement is the differentiator. Very few engineers have shipped machine identity and delegated authorization for AI agents, because the problem is new. If you have done conventional enterprise IAM at scale and have thought seriously about how agents authenticate, that combination is currently scarce and worth putting at the top of your application. Accommodations: Smartsheet states that it will make preparations to ensure a comfortable interview experience if you let them know.
Responsibilities, as printed: developing, maintaining and extending test frameworks and infrastructure including system level regression and smoke tests; developing automated tests and identifying when and where tests should be written; implementing performance test plans; building custom testing applications in languages such as Java or Python using tools including WebDriver, Locust, BrowserStack, Appium, Selenium Grid and Postman; and developing automation that minimises fragility through architectural patterns. No experience requirement is published. This advertisement states no years figure, no degree requirement and no seniority band. The only years figure in the text is the sentence saying Appian has been automating processes for more than 25 years, which describes the company and not the candidate. Automated job parsers routinely read that line as a 25 year requirement, which would be absurd. What that means for you in practice: without a stated band, the level is genuinely ambiguous, so this is one of the few postings here worth applying to across a range of experience. The tool list is the real signal. If you can build and maintain a framework in Java or Python rather than only write tests inside someone else's, you are in scope. Location: Chennai. Fit guidance: pay attention to the phrase about minimising fragility through architectural patterns. That is a request for someone who has felt the pain of a flaky suite and fixed it structurally. If you have rebuilt a brittle test framework, lead with that story, because it maps directly onto what this posting is asking for. The performance testing element, with Locust named, is also worth flagging if you have it, since load testing is a less common skill among automation engineers than browser automation. About the employer, from the posting: Appian describes its values as intensity and excellence, says it sets high standards and lives up to them, and describes its platform as known for unique reliability and scale in automating complex processes for large enterprises and governments. It is listed on Nasdaq under APPN. Worth comparing: Appian has other engineering roles open in the same Chennai office at explicitly stated levels, including a Senior Software Engineer at 6 or more years and a Lead Software Engineer at 10 or more. If you want a role where the bar is published, look at those instead.
Must have, as printed: strong hands on programming skills in Golang; deep, practical knowledge of identity protocols OIDC, OAuth 2.0 and SAML 2.0 including token and assertion internals, standard flows and failure modes; working knowledge of Active Directory; applied cryptography and PKI experience covering X.509, JWT and JWKS, key rotation and TLS; strong security engineering discipline, comfortable reasoning about threat models and building software to protect mission critical systems rather than only making features work; a solid understanding of operating system fundamentals, networking and concurrency; working knowledge of Linux with comfort writing shell or bash scripts; and simple, effective written and verbal communication. Nice to have, as printed: directory internals covering schema and bind operations; HTTP internals and reverse proxying including TLS and header injection; build, release and cross platform packaging for Linux deb and rpm and Windows MSI; secret manager internals, Redis, Win32 and policy engines; and basic C sharp or .NET to maintain a companion application. No years requirement is published on this posting. The real day to day: designing, building and hardening identity and access flows including OIDC, OAuth 2.0, SAML 2.0 and Active Directory integrations that sit in front of mission critical systems; owning token and assertion lifecycle correctness; applying cryptography and PKI practice to the authentication path; building and maintaining reverse proxy and HTTP layer components; debugging customer facing identity and access issues with support; contributing to build, release and cross platform packaging; maintaining a small Windows companion application in C sharp; writing end to end tests covering authentication flows and edge cases such as clock skew, revoked tokens and malformed assertions; and documenting known issues and design decisions. Location: Pune. Fit guidance, said plainly: do not read the plain Software Engineer title as an opening for a beginner. The requirement list asks for deep, practical identity protocol knowledge, which takes years to acquire. What the missing years line does give you is room to argue your own case if you have that depth without the tenure, and that is a real opportunity if identity is genuinely your area. Worth comparing: the sibling posting in Bangalore, Senior Software Engineer CPD (IAM), asks for the same things plus a minimum of eight years.
Who this is for, as printed: a recent graduate or early career engineer with up to 3 years of relevant experience. The posting adds that strong candidates at the very start of their careers are encouraged to apply, which is rare enough to be worth quoting when so few postings open at this level. What HackerRank says helps, as printed: having built a project, script, bot or automation that solved a real problem; having worked with logs, observability tools, cloud platforms, single sign on protocols including SAML and OAuth, or third party integrations; having used AI coding tools such as Claude, Cursor or Copilot, with the ability to explain how you validated their output; and having contributed to an open source project, hackathon, internship or production codebase. Note how accessible that list is: a personal project, a hackathon or an internship all count. You do not need commercial employment to satisfy it. What HackerRank says you will thrive on: enjoying ambiguous technical problems and being persistent enough to find the real cause; caring equally about technical correctness and how the customer experiences the resolution; learning fast, seeking feedback and turning new knowledge into repeatable practice; and solving rather than routing, taking pride in leaving no loose ends. The role, in the posting's framing: customer experience engineering is where customers, product and engineering meet, and as a CXE 1 you investigate real technical problems. Note that the advertisement calls the level CXE 1 in the body and Customer Experience Engineer L1 in the title; they are the same role. Location: listed as hybrid in Bangalore. The advertisement does not state how many office days, so ask. Fit guidance: this is a customer facing technical role, not a pure engineering one, and it is worth being clear eyed about that. You will spend real time writing to customers and understanding their situation, alongside the debugging. For someone starting out, that combination builds a genuinely useful skill set and it is a common route into backend or platform teams later. If you would rather write code all day with no customer contact, this is not the right first job. On AI tools: the posting asks you to explain how you validated the output of AI coding tools, not merely that you used them. Prepare a specific example.
Mandatory skills, as printed: 3 to 6 years of technical support experience, preferably with SaaS or cloud based platforms. Qualifications and education requirements, as printed: a bachelors degree in a technology related field, specifically BE, BTech or MCA. The role, in the posting's framing: the senior technical support engineer acts as a key second level, described as L2, liaison between Netradyne and its customers. You are responsible for diagnosing and resolving technical issues reported by customers while collaborating with cross functional teams for timely resolution, and you engage directly with customers to troubleshoot in field hardware and software issues on Netradyne's connected vehicle platforms. Shift reality, stated in the posting: as a 24 by 7 by 365 operations centre, Netradyne requires candidates who are flexible to work any shift based on business needs, including weekends, Saturday and Sunday. Weigh this properly. It is not an occasional on call arrangement, it is a rota. About the employer: Netradyne describes itself as harnessing computer vision and edge computing to change the transportation ecosystem, and as a leader in fleet safety solutions with growth exceeding four times year on year. Location: Bengaluru. Fit guidance: the hardware element is what distinguishes this from ordinary SaaS support. Devices sit in moving trucks, so failures involve connectivity, power, mounting and environment as well as software. If you enjoy problems where the cause might be physical, this is more interesting than a typical support queue. If your background is purely web application support, expect a learning curve on the device side. A note on the neighbouring role: Netradyne has a second requisition open in the same office titled Senior Technical Support Analyst with the same 3 to 6 year requirement. The two postings are close, so if this one does not fit, compare them. Security warning included by the employer: Netradyne states that recruitment fraud targeting job seekers has increased, that it does not request sensitive personal data by text or instant message, does not promise advance payment for equipment setup, and does not use agencies that charge candidates a fee. It states that official communication comes only from addresses ending netradyne.com or us-greenhouse-mail.io. Worth reading twice, because this scam pattern is common in India.
Required, as printed: a solid technical foundation across areas such as operating systems, either Windows or Unix and Linux, and networking; proven technical experience and sound troubleshooting; and good communication skills with customer empathy. The published experience figure for this role is 3 or more years. The technology surface, as listed in the posting: on premises hypervisors VMware and Microsoft Hyper V; containerisation with Kubernetes; cloud hypervisors AWS, Azure, GCP, Nutanix AHV, OpenStack, OCI, OpenShift and RHEV; and Windows file systems. The posting states that engineers tackle issues end to end covering deployment, configuration, backups, archiving, restores, replication and performance benchmarking. A stated bonus: the opportunity to learn and work on IntelliSnap using storage arrays from vendors including NetApp, Nutanix, Dell EMC, HDS and HPE. What the employer offers, as printed: continuous professional development, product training and career pathing; annual health check ups; tuition reimbursement; an inclusive company culture with community guilds; and personal accident and term life cover. Location: Bangalore. Fit guidance: the Tier 1 in the title undersells the work. Read the technology list instead, because that is what you will actually be exposed to, and it is an unusually strong list for someone who wants infrastructure breadth. Enterprise backup support is a well established route into storage, virtualisation and cloud infrastructure careers, and the tuition reimbursement and product training suggest the employer expects people to grow rather than churn. Who it suits: someone with around three years of infrastructure or support experience who wants to go deeper into enterprise storage and virtualisation rather than sideways into another helpdesk. If you want to write software, this is not that role. Security warning included by the employer: Commvault states that scammers are impersonating its team members including HR and leadership by email or text, that it does not conduct interviews by email or text, and that it will never ask for sensitive documents such as banking information before your first day. Suspected scams can be reported to its recruiting team address given in the posting.
Required, as printed, and note the mismatch: 2 or more years experience in customer facing support roles; 3 or more years experience supporting or administering SaaS IT infrastructure monitoring products; 3 or more years experience in Linux, Windows or network administration; and 3 or more years experience with cloud platforms such as AWS and Azure. The posting also asks for the ability to follow a structured process and information entry, and the ability to work in a fast paced dynamic environment during tremendous growth. Why we published three rather than two: the lowest number in an advertisement is not the requirement. The two year figure applies only to the customer facing portion, while three separate technical requirements each ask for three or more years. Anyone applying at two years with no monitoring or administration background would be screened out on the following three lines. Location and working arrangement: the posting states the position is located in Pune, and describes LogicMonitor's offices as Centers of Energy, hubs where teams accelerate productivity and collaboration, with teams coordinating their time in those centres to reflect how they work best. That phrasing implies office attendance without specifying the number of days, so ask. About the employer: LogicMonitor describes itself as an AI first hybrid observability platform and its culture around trust, customer obsession and agility. AI in hiring, disclosed by the employer: LogicMonitor states that it uses AI tools in the hiring process to support but not replace human review, that all hiring decisions are made by its recruiting and hiring teams, and that you may opt out of AI processing at any time with your application still reviewed, by contacting an opt out address given in the posting. That disclosure is unusual and worth knowing about. Accommodations: the posting includes an accommodation request form for candidates who need adjustments during the application or interview process under applicable local law. Fit guidance: this suits someone who has administered infrastructure and wants to move toward a customer facing technical role without losing the technical content. Monitoring and observability knowledge is the strongest single signal you can bring, since it is named first among the three year requirements.
Minimum qualifications, as printed: a foundational understanding of AI and ML technologies and experience leveraging, securing or positioning AI driven solutions within your functional domain; a minimum of 8 or more years of experience in technical support, with at least 5 years focused on DLP and CASB solutions and escalations; experience with data loss prevention, securing SaaS, and cloud access security brokers; practical working knowledge of AWS, Azure or GCP paired with a strong understanding of Unix, Linux and Windows operating systems; and a deep understanding of data protection principles and practices. Preferred, as printed: experience deploying or supporting AI powered sensitive data discovery tools or automated data classification models to enhance DLP capabilities; experience with scripting and automation using Python or PowerShell; and knowledge of regulatory requirements and compliance standards such as GDPR, HIPAA and PCI DSS. Read the title against the requirement: Escalation Engineer sounds like a mid level support title and it is being used here for an eight year specialist role. That is the opposite of the more familiar trap where a senior title hides a junior requirement, and it means experienced DLP engineers may scroll past this listing without opening it. Location: the posting lists both Bangalore and Mohali, and carries a hybrid tag. About the employer: Zscaler describes itself as an AI forward enterprise using the world's largest security data lake to power its cloud native Zero Trust Exchange platform. It states that impact matters more than title and that it values constructive, honest debate. Fit guidance: the five years of DLP and CASB specifically is the clause that decides this. General security support experience will not substitute, because escalation work depends on knowing a product family deeply enough to diagnose what its own documentation does not cover. If you have that background at a competing DLP vendor, you are the target candidate. On the AI line: like other Zscaler postings in this edition, the first minimum qualification concerns AI tooling. Prepare a real answer rather than treating it as filler.
Required, as printed: a bachelors degree in computer science, engineering, information systems or mathematics; 8 or more years of progressive IT experience including 5 or more years of specialised experience in enterprise web application development, delivery and deployment; proven hands on experience developing, configuring, testing and deploying enterprise grade software applications in an agile delivery environment; deep technical expertise in Python and SQL supplemented by working knowledge of JavaScript or Java; strong experience designing relational data models using SQL Server, Oracle or MariaDB, custom APIs and middleware or ESB orchestration layers; and practical experience with web application infrastructure, containerisation using Kubernetes, DevSecOps concepts, test automation tools including Selenium, and performance and load testing methodologies. Preferred, as printed: experience operating within high velocity, cross functional engineering teams; hands on exposure to modern generative AI integrations, LLM application pipelines or vector databases; and experience with enterprise platforms such as Salesforce or ServiceNow, which the posting says translates well into its orchestration environment. The role, in the posting's own words: as an individual contributor you design complex architectures and lead the hands on engineering of enterprise grade automation platforms for global industry leaders. The posting states explicitly that top technical talent joins Appian in this role to maintain individual contributor focus on complex architectures, building low latency integrations, optimising database schemas and diagnosing deep performance bottlenecks, without people management responsibility. Location and work model, as printed: Chennai, India, with the work model stated as in office. That is unambiguous, unlike several other postings in this edition. About the team: the Chennai based customer success team is described as an elite engineering hub for global enterprises, specialising in platform architecture and delivering scalable, high throughput environments. Fit guidance: consultant titles often worry engineers who want to keep building, and this posting anticipates that objection directly by naming the individual contributor focus. Treat it as customer facing engineering rather than advisory work. The two numbers are also worth separating: eight years of IT overall, but five of those must be genuine enterprise web application development, so a career weighted toward operations or administration will not satisfy it. About the employer: Appian describes its values as intensity and excellence, and its platform as automating complex processes for large enterprises and governments.
Added August 29, 2026
The posting states no number of years. It describes the role as entry level and hands on, working on well defined tasks under senior guidance, so it is genuinely open to someone starting out. That is why we have published it at zero to one year rather than guessing a figure. What the job actually is, day to day: monitor, triage and investigate security alerts coming from SIEM, EDR, cloud, network and identity sources, and escalate anything suspicious or confirmed to senior engineers following an established procedure. Help cut false positives by spotting noisy alerts and documenting tuning recommendations. Assist in building and testing detection rules mapped to frameworks such as MITRE ATT&CK. Contribute to automation, including SOAR playbooks and AI agent driven workflows for alert enrichment, triage and response. Support SOC metrics tracking and reporting. The shift reality, stated plainly in the ad: this is a 24x7 SOC on a rotating shift schedule that includes night shifts, weekends and holidays. It is based at Tekion's Bangalore office. If you cannot do nights, this is not the role, and that is worth knowing before an interview rather than after. Who this is for: someone who wants into security operations and is willing to trade sociable hours for real alert handling experience early. Familiarity with SIEM or EDR tooling, an understanding of common attack techniques, and any scripting will help. The AI and SOAR automation work is a genuine differentiator, because a lot of first SOC jobs are pure alert clicking and this one explicitly includes building the automation. No interview process is published in the ad.
Stated requirement is 1 to 2 years of QA or testing experience with exposure to test automation. This is one of the few genuinely early career roles on the board today. Must have, as listed: one to two years in QA or testing with exposure to automation. Hands on experience or project exposure to Salesforce testing, ideally covering one or more of Sales Cloud, Salesforce CPQ, Revenue Cloud, Service Cloud or Commerce Cloud. Hands on Playwright automation using TypeScript or JavaScript. An understanding of automated testing concepts including test cases, test suites, locators, assertions and test execution. A basic understanding of Salesforce business processes and end to end application workflows. REST API testing with Playwright, Postman or similar. Working knowledge of JavaScript or TypeScript, with Java or Python a plus. Familiarity with CI/CD and exposure to Jenkins, GitHub Actions, Azure DevOps or GitLab CI/CD. Working knowledge of Git. Strong problem solving, troubleshooting and debugging. Good written and verbal communication, and the ability to work in an Agile cross functional team. Good to have: exposure to AI powered or AI assisted testing tools and Agentic AI, familiarity with Playwright AI capabilities or self healing automation, basic Salesforce Apex and Apex testing, performance testing with JMeter or LoadRunner, B2B SaaS experience, and a Salesforce certification or the willingness to work towards one. Location and working pattern: Chennai, and the posting carries a hybrid tag. Note that ZoomInfo has posted the same role separately in Bengaluru, so apply to the city you actually want. Who this is for: a QA engineer one or two years in who has some Playwright under their belt and is willing to specialise in enterprise Salesforce testing. The Salesforce angle is the thing to weigh. It is a genuinely marketable specialisation, but it is a narrower path than general product QA. No interview process is published in the ad.
Stated requirement is 1 to 2 years of QA or testing experience with exposure to test automation. Must have, as listed: one to two years in QA or testing with automation exposure. Hands on experience or project exposure to Salesforce testing across one or more of Sales Cloud, Salesforce CPQ, Revenue Cloud, Service Cloud and Commerce Cloud. Hands on Playwright automation in TypeScript or JavaScript. Understanding of automated testing concepts including test cases, test suites, locators, assertions and execution. Basic understanding of Salesforce business processes and end to end workflows. REST API testing using Playwright, Postman or a similar tool. Working knowledge of JavaScript or TypeScript, with Java or Python a plus. Familiarity with CI/CD concepts and tools such as Jenkins, GitHub Actions, Azure DevOps or GitLab CI/CD. Working knowledge of Git and version control. Strong debugging and troubleshooting. Good communication and the ability to work in an Agile cross functional team. Good to have: AI powered testing tools, AI assisted automation or Agentic AI exposure, Playwright AI capabilities and self healing automation concepts, basic Salesforce Apex and Apex testing, performance testing with JMeter or LoadRunner, B2B SaaS experience, and Salesforce certification or willingness to pursue one. Location and working pattern: Bengaluru, with a hybrid tag on the posting. The Chennai version of this role is a separate requisition and is also on this board. Who this is for: an early career QA engineer with Playwright experience who is willing to go deep on enterprise Salesforce testing. Weigh the specialisation honestly. It pays well and is in demand, but it is narrower than general product QA and it will shape the next few years of your CV. No interview process is published in the ad.
Stated requirement is 1 to 3 years of experience in a distributed, enterprise scale environment. That is a genuinely accessible band for systems level networking work, which normally starts higher. What you would do: develop and optimise network applications and protocols using C and C++. Design efficient data structures for network data processing and handle system level programming in Linux environments. Analyse network performance, identify issues and implement optimisations. Collaborate with other teams to define requirements, design architectures and integrate network solutions. Conduct code reviews, testing and debugging. Minimum qualifications as published: a foundational understanding of AI and ML technologies and experience using, securing or positioning AI driven solutions within your domain, alongside the one to three years in a distributed and enterprise scale environment. The ad also looks for strength in networking with a track record of proposing improvements to system reliability, scalability and network efficiency. Location and working pattern: this is stated as a hybrid role based in Bangalore, reporting to the Senior Manager, Engineering in the ZTNA department. The posting carries a hybrid tag and refers to in office perks, so do not read it as remote. Who this is for: someone one to three years in who genuinely wants systems and networking rather than application development, and is comfortable in C or C++ on Linux. If you have written packet handling code, worked on a proxy or a protocol stack, or done kernel adjacent work at university or in a first job, this is a strong opening at a company operating at very large scale. If your experience is web or backend service work, the datapath focus will be a hard change of direction rather than an adjacent step. No interview process is published in the ad.
Stated requirement is 1 to 3 years of experience in a customer facing technical role. The posting names the kinds of background it will accept: Technical Support Engineer, Support or Solutions Engineer, Implementation Engineer, junior DevOps or Security Engineer, or similar. Worth knowing before you apply: the board title says Customer Success Engineer, but the description itself is for an Associate Customer Success Engineer and calls the job a great next step for someone early in a customer facing technical career. The associate framing is in the body, not the title, so the seniority is lower than the title alone suggests. That is the opposite of the usual trap and it works in a junior applicant's favour here. The work: supporting Orca customers day to day alongside senior Customer Success Engineers and Customer Success Managers, helping them get value from the platform, and growing into cloud security and customer success engineering as a career. The ad frames this explicitly as a growth seat rather than a role that expects a finished cloud security specialist. Location and working pattern: the posting states India, Delhi, remote. We checked this against the text rather than trusting a tag, and it is a genuine remote listing. Remote roles have been the single most requested thing from readers of this list, and this is one of only three today that survive that check. Who this is for: someone one to three years into support, implementation or junior DevOps or security work who wants a route into cloud security without already having the cloud security title. Being comfortable talking to customers matters as much as the technical depth here. If you are a strong engineer who does not want customer contact, this will not suit you, and the ad is honest about that. No interview process is published in the ad.
Stated requirement is 2 years of experience with C Sharp and the .NET ecosystem. Note the mismatch worth knowing about: the title says Software Engineer I, which normally signals a first job, but the requirement is two years. The roman numeral is not a reliable guide to seniority, and today's edition has several examples of that in both directions. Required qualifications, as listed: two years of experience with C Sharp and the .NET ecosystem. Willingness to learn and develop with functional programming using F Sharp. Good knowledge of Win32 APIs. Basic familiarity with networking protocols such as HTTP and TLS. The ability to write clean and testable code. A general understanding of how distributed systems work. What the job actually is: design, develop, test and maintain software features for enterprise SaaS platforms. Build reliable and scalable services, APIs, platform components, integrations and customer facing capabilities. Take part in technical design, code reviews, troubleshooting and production support. Work with product management, QA, UX and operations to deliver roadmap commitments. Contribute to improvements in performance, reliability, security, maintainability, automation and observability. Follow and help improve agile development, CI/CD, automated testing and DevOps practice. Communicate progress, risks and technical trade offs clearly. Nice to have, from the ad: cloud infrastructure experience, contributions to open source software, and experience performing peer code reviews. Location and working pattern: the posting states this is a hybrid role requiring onsite presence at the Pune office three days per week. That is specific and it is in the ad, so plan for it. Who this is for: a Microsoft stack developer roughly two years in who wants enterprise product work rather than services or consulting. The F Sharp and Win32 elements are unusual and genuinely interesting if low level Windows work appeals. If your background is Java or Python, expect the C Sharp requirement to be taken literally. No interview process is published in the ad.
Stated requirement is 2 to 3 years of QA experience across manual and automation testing, with a B.Tech or BE in Computer Science, IT or an equivalent. Requirements as listed: 2 to 3 years of QA experience in manual plus automation testing. Experience with Selenium WebDriver and API testing tools including Postman and REST Assured. Good SQL skills for data validation. Familiarity with Agile and Scrum workflows. An understanding of the defect lifecycle and QA metrics. Good communication, problem solving and collaboration skills. What the job actually is: design, execute and maintain manual and automated test cases across web, API and database layers. Perform API testing using Postman or automation frameworks such as REST Assured. Maintain UI automation using Selenium WebDriver in Java or Python. Validate backend data using SQL queries. Manage defects through Jira and work with development to get them resolved. Take part in Agile ceremonies, QA sign offs and release readiness reviews. Integrate automated tests into CI/CD pipelines using Jenkins or GitHub Actions. Perform cross browser and responsive testing. Contribute to QA process improvements and expand automation coverage. Location: Hyderabad. Note that other HighRadius engineering postings in this same edition state five days a week in the office, and this ad does not state a working pattern either way, so it is worth asking. Who this is for: a QA engineer two to three years in who already writes Selenium and API tests and wants breadth across UI, API and database validation rather than a single narrow lane. The SQL requirement is real here, not decorative, because a good part of the job is checking that the data behind the screen is correct. No interview process is published in the ad.
Stated requirement is at least 3 or more years of experience in software engineering, plus a track record of having designed, built, scaled and maintained production services and an understanding of service oriented architecture. What you would do: architect and develop the platform for the security platform engineering organisation. Provide technical structure to teams and work with management and stakeholders on strategic roadmaps. Build new services in Go or Java to meet product and business needs. Design scalable systems using modern cloud technology. Manage your own project priorities, deadlines and deliverables. Mentor and train other team members on design technique and coding standards. Articulate a long term vision for maintaining and scaling backend systems. Write high quality, well tested code. Debug genuinely difficult technical problems and make systems easier to deploy, operate and diagnose. Review feature designs within your product area and across the company for cross cutting projects, taking ownership of security, safety, scale, operational integrity and architectural clarity. The functional areas the team covers, named in the ad: secrets and key management, identity and access management, onchain security, policy and risk management, and vulnerability management, serving product, compliance, security and services teams. Location and working pattern: the listing states Remote in India and carries a remote tag, and we confirmed that against the body rather than the tag alone. Read one caveat in the ad before you treat it as fully distributed: Coinbase describes itself as remote first but not remote only, and says to expect quarterly in person working sessions it calls surges. The ad is also blunt about culture, describing a high bar and an intense environment. Who this is for: a backend engineer three or more years in who wants security platform work rather than product features, and is comfortable in Go or Java. Prior security experience is not stated as mandatory, so a strong distributed systems engineer who wants to move into security has a real opening here. No interview process is published in the ad.
Stated requirement is 3 or more years building production software, including senior level ownership of projects that ran for months and involved several people. Before anything else, two things the ad tells you that change the picture. First, Fivetran and dbt Labs are merging, and the posting says so directly, warning that both names appear during recruiting. The role itself is on dbt surfaces. Second, do not read this as a remote job. The posting carries a hybrid tag, and the only mention of remote working is in the bonus skills list, where having worked asynchronously in a fully remote distributed team is listed as a nice to have. That is a description of a candidate's past, not an offer about this job. What you would do: own end to end delivery across dbt Studio in the browser, the dbt VS Code extension, and the CLI workspace runtime that powers both. Own parts of that runtime, including migrating users off the legacy IDE and enabling asynchronous background agent runs. Help build the AI native developer experience, including agent workflows, diff review, streaming tool calls, charts and rich outputs for conversational analytics, and MCP apps that bring dbt projects into tools such as Claude and Codex. Technologies named: Python, TypeScript, React and Kubernetes. The ad is explicit that this is genuinely full stack and that you are expected to carry a feature from schema and service design through to the finished interface without a handoff. Bonus skills listed: having shipped LLM or agent powered features to production with real opinions on evaluation, latency, cost and where models fall down, and having worked asynchronously in a fully remote distributed team. Location and working pattern: Bengaluru, with the posting also tagged APAC, and a hybrid tag on the listing. Who this is for: a product minded full stack engineer three or more years in who is comfortable moving between Python services and a React front end, and who wants to build developer tooling rather than end user features. If you already use dbt, that context is worth a lot here. No interview process is published in the ad.
Stated requirement is 3 or more years of professional software engineering experience, including building and operating production web applications. What you would do: own and develop data rich, consumer grade user interfaces and APIs that surface what Abnormal knows about a user's normal patterns and what might indicate something abnormal. Build the interface that lets customers and internal agents debug particular attacks. Build a framework and specification for quickly adding new data sources. Work directly with customers on feedback and iterate quickly, for example resolving false positive and false negative or integration issues. Work with distributed systems, cloud infrastructure and event driven or messaging based architectures. Collaborate with product managers, designers and partner engineering teams to define interfaces and make trade offs. Write maintainable code, automated tests, documentation and operational runbooks, and take part in code reviews and design discussions. Take part in on call and production support, investigate issues and improve reliability and observability. Use AI assisted development tools thoughtfully while keeping technical judgement and code quality. What the team owns: the identity graph and the data capturing relationships between people, groups, tenants and apps, plus platform capabilities used as intelligence by detection engine decisions, customer facing identity insights and cross product APIs. Location and working pattern: the posting states India, hybrid, and the listing itself is headed Hybrid, Bangalore. Treat the hybrid expectation as real. Who this is for: a full stack engineer three or more years in who genuinely enjoys frontend work but does not want to give up backend and distributed systems. The ad is clear that the frontend weighting is meaningful, so a backend only engineer would be stretching. On call is named explicitly, so factor that in. No interview process is published in the ad.
Stated requirement is 3 or more years of experience in Solution Engineering, Sales Engineering, Solutions Consulting, IT Operations, IT Service Management, or a related technical customer facing role. What the job actually is: partner with sales teams through the customer lifecycle to support new business, expansion and renewal opportunities. Conduct discovery sessions to understand customer business objectives, operational challenges, technical requirements and success criteria. Deliver product demonstrations of SolarWinds Service Desk and Web Help Desk tailored to what the customer said in discovery. Act as a technical advisor to prospective and existing customers evaluating and adopting the ITSM products. Work with Account Executives, Customer Success, Product Management and other teams to support customer success and feed market signals back into the product. What the role is not: this is a presales technical role, not a quota carrying sales job. It sits alongside sales and supports revenue, and the ad says so, but the responsibilities listed are discovery, demonstration and solution design rather than closing. We separate those deliberately, and we left another company's Solutions Engineer posting out of today's edition because its first stated objective was to exceed sales targets. This one reads differently. Location: Bangalore. The posting does not state a working pattern, so ask. Who this is for: someone with a few years in ITSM, IT operations, support or presales who is good in front of a customer and enjoys the puzzle of mapping a product onto somebody else's messy environment. Knowledge of service desk tooling and IT asset management is directly relevant. If you want to write code all day this is the wrong role, and if you want to sell without the technical depth it is equally wrong. No interview process is published in the ad.
Stated requirement is 3 to 6 years of professional software engineering experience. Read the title carefully before you skip or apply. The posting is listed as L2 Engineer, Coach, which reads like tier two product support. The body is headed L2 Engineer, GenAI Focused and opens by saying the team is seeking a mid level AI engineer. Coach is the Showpad product this sits on, not a support tier. The actual job is backend and applied AI engineering. Required qualifications as listed: 3 to 6 years of professional software engineering experience. Strong expertise in TypeScript and JavaScript. Hands on experience with AWS serverless services including API Gateway, Lambda, DynamoDB and VPC networking. Experience designing and building distributed backend systems. Strong understanding of REST APIs, microservices and event driven architectures. Experience with WebSockets and real time communication systems. Strong experience with unit testing and integration testing. Experience building and supporting production grade generative AI applications. Experience working with LLMs such as OpenAI, Anthropic, Gemini and open source models. Experience with prompt engineering and prompt optimisation. What you would do: design, develop and maintain scalable backend services in TypeScript and JavaScript. Build and operate cloud native applications on AWS serverless. Design and implement REST APIs and event driven architectures. Build and deploy production grade generative AI applications. Develop RAG based solutions using vector databases, embeddings and modern LLM frameworks. Engineer prompts and AI workflows. Conduct LLM evaluations, benchmarking and performance analysis. Implement AI observability, monitoring and quality evaluation. Build automated testing frameworks, maintain CI/CD pipelines, and contribute to architecture decisions. Location: Pune. The posting does not state a working pattern. Who this is for: a backend engineer three to six years in who has actually shipped an LLM feature to production, not just experimented. The serverless and TypeScript requirements are specific, so a Java or Python backend engineer without AWS serverless depth would be stretching. No interview process is published in the ad.
Stated requirement is 4 or more years of experience in platform engineering, infrastructure engineering, DevOps or SRE roles, with real ownership of production cloud infrastructure. The timezone is in the job title and it matters. This is the operations seat on a PST timezone, which from India means working United States Pacific hours. That is a night shift. It is disclosed openly in the title rather than buried, but it is the single biggest thing to weigh before applying. What you have, as listed: 4 or more years in platform, infrastructure, DevOps or SRE roles with genuine ownership of production cloud infrastructure. Strong software engineering skills in Go or Python, writing tested maintainable code and treating infrastructure automation as software rather than scripting. Deep hands on Kubernetes in production covering workload scheduling, networking, autoscaling and upgrades. Infrastructure as code tooling such as Terraform, Pulumi or OpenTofu. Solid experience with at least one major public cloud, with AWS, GCP and Azure all named and experience across all three called a strong plus given the multi cloud footprint. A track record of building tools or platforms other engineers use, such as internal CLIs, provisioning frameworks, self service portals or automation pipelines. What the job actually is: build and run the infrastructure behind a multi tenant, security sensitive B2B cloud product used by enterprise customers worldwide. The platform spans multi tenant environments and single tenant bring your own cloud deployments into customer accounts, so every environment has to be provisioned, upgraded, monitored and recovered the same way at scale with minimal manual work. You would also carry deep operational ownership including on call, incident response and root cause analysis on the systems you build. Location: listed as India. Benefits named include a work from home expense, flexible hours, generous PTO and equity, though the posting does not state the role as remote in so many words. Who this is for: an infrastructure engineer who writes real code and wants platform building rather than ticket handling, and who can genuinely work Pacific hours. If the night shift does not work for your life, skip it, because the ad is not hiding it. No interview process is published in the ad.
Stated requirement is 4 to 6 years of experience in security operations, security engineering, incident response or related roles, with equivalent experience considered. The shift pattern is explicit and non negotiable in the ad: this is a 24x7 SOC on a rotating shift schedule including night shifts, weekends and holidays. The posting also lists willingness and ability to work that roster as a requirement in its own right, not a footnote. What you would do: work in the 24x7 SOC providing continuous alert monitoring and response coverage. Triage, investigate and respond to security alerts from SIEM, EDR, cloud, network and identity sources, escalating confirmed incidents per procedure. Continuously tune detections and alert logic to reduce false positives and improve the signal to noise ratio across the alert pipeline. Build, test and maintain detection rules and use cases aligned to frameworks such as MITRE ATT&CK, based on emerging threats. Track and report SOC metrics. Automate response workflows using SOAR platforms and AI agents. Partner with IT, Engineering and Security Operations to identify risks, remediate vulnerabilities and strengthen security posture. How it differs from the Engineer I seat, in the ad's own framing: the Engineer II works on moderately complex projects with minimal supervision, while the Engineer I works on well defined tasks under senior guidance. Both are on the same roster and both are at Tekion's Bangalore office. If you are choosing between them, the years requirement is the clearer signal: this one asks four to six, the other asks none and says entry level. Hands on experience with alert triage is named in the requirements alongside the years. Who this is for: a SOC analyst or security engineer four to six years in who wants to move from consuming detections to writing and tuning them, and who is willing to keep working shifts to do it. The SOAR and AI agent automation work is the part that builds transferable skill fastest. No interview process is published in the ad.
Stated requirement is a minimum of 5 or more years of experience in backend technology using Java, Spring Boot, low level design, data structures and algorithms, multithreading and AWS. The working pattern is stated in the ad and it is worth reading twice: five days working from office, in Hyderabad. That is a full return to office, not hybrid, and HighRadius states the same on another engineering role in today's edition. What the job actually is: HighRadius runs an internal new products initiative described as an entrepreneurship programme, with products built in a startup ecosystem inside the company. You would join one of those and be responsible for designing and building the product in stealth mode. Responsibilities named include building the foundational elements of the product, taking responsibility for timely delivery as a senior engineer in a small team, providing scalable solutions for EI and payment products covering both backend processing and UI representation, contributing to technical design and implementation with engineering leaders, high quality development at speed, code reviews, and filling gaps in the product by building development processes and tools where needed. Requirements as listed: strong hands on knowledge of core Java, Spring, Hibernate and SQL, with the five or more years covering Java, Spring Boot, low level design, DSA, multithreading and AWS. Knowledge of front end development alongside the backend technologies. One line to weigh: the ad says you would manage and groom junior developers for a high performance culture. We read this as senior engineer mentoring rather than people management, because no direct reports, hiring or performance responsibilities are named and every technical requirement is hands on. If you want a pure individual contributor seat with no mentoring expectation, ask about it. Who this is for: a Java backend engineer five or more years in who wants greenfield product building and can genuinely commit to five days a week in a Hyderabad office. The zero to one framing is the appeal here, and the office requirement is the cost. No interview process is published in the ad.
Stated requirement is 5 or more years of experience as a software engineer, with strong general purpose coding skills and Go or Python preferred. One caution about the years. The description also mentions someone with 16 or more years of experience across Microsoft, Oracle and companies such as Freshworks. That sentence is a biography of an engineering leader in the team section, not a requirement, and an automated parser reading the highest or lowest number in this posting would get it wrong in both directions. The requirement is five or more. What the role is now, in the ad's own words: it has shifted from a traditional DevOps or developer infrastructure profile to one centred on general software engineering and applied AI. Most of the time goes on building and hardening AI powered developer tools such as automated code review, CI failure triage and agentic automation, rather than managing build systems or CI infrastructure in isolation. Working knowledge of CI/CD and developer workflows is still needed, but the emphasis is shipping product quality software whose customers happen to be engineers. Examples of the team's actual work, named in the posting: building the AI code review pipeline and migrating the major repositories including cockroach, pebble and cockroach cloud off third party review tools such as BugBot, GitHub Copilot and Claude Code Action onto an in house AI driven pull request review system, and adding observability to AI review so findings can be surfaced and measured. What the team values, as stated: providing high quality support to engineering teams, engaging with engineers to understand developer pain points, minimising and automating away toil including the toil of using AI safely, shipping incrementally, measuring quality with real data, and being honest about where AI tooling still needs a human in the loop. Location: Bangalore. The posting does not state a working pattern. Who this is for: an engineer five or more years in who wants to build internal developer tooling and is genuinely interested in putting AI agents into engineering workflows safely. If you were hoping for distributed database internals, note that this role is deliberately not that. No interview process is published in the ad.
Stated requirement is 5 or more years of professional experience in a data engineering or full stack role. What you would be doing, as listed: design and develop scalable data platforms using AWS, Snowflake, dbt and Databricks. Use Terraform to manage infrastructure as code so environments are consistent and reproducible. Develop and maintain CI/CD pipelines for data platform applications using GitHub and GitLab. Engineer robust data pipelines to support AI and ML infrastructure. Collaborate with data engineers, analysts, scientists and other engineers to ensure data availability, integrity and security. Build stable data layers and partner with analytics engineers to power AI and ML systems. Where the team sits: the Data Engineering team is part of the Technology Data and Intelligence organisation, and the platforms it builds are used across sales, marketing, engineering, finance, product and operations. The ad describes detailed technical design, development and implementation of applications on current technology stacks. Nice to have, named in the posting: experience with recent AI technologies, experience coaching and developing individuals for increased effectiveness, familiarity with cloud cost optimisation or FinOps, and a background in SaaS, security or identity. Location: Bengaluru. The posting does not state a working pattern in the text we can see, so ask. Who this is for: a data engineer five or more years in who has built pipelines on a modern warehouse stack and wants platform ownership rather than dashboard work. Snowflake and dbt experience is close to essential given how specifically they are named. Data engineering has been one of the two most requested categories from readers of this list, alongside backend, and this is a straightforward example of it at a large company. No interview process is published in the ad.
Stated requirement is 5 to 6 or more years in backend engineering, with meaningful time spent operating high throughput production systems you were on call for. What we are looking for, as listed: deep proficiency in Go or Python and the judgement to know which belongs where. Strong distributed systems design covering queues, workflow orchestration, idempotency, backpressure, retry and timeout semantics, consistency trade offs and graceful degradation. Production experience with Temporal or an equivalent durable execution engine on workflows that mattered. Kubernetes in production including autoscaling, resource management, rollouts and debugging under load, with GPU workload scheduling a strong plus. Demonstrable experience serving ML or LLM inference in production covering batching, caching, model versioning, A/B rollout and latency budgeting. Rigour about observability and reliability, including having designed SLOs, run incidents and shipped the fixes. Hard won cost intuition, having made a system materially cheaper without giving up quality. Bonus points: direct experience with OCR, intelligent document processing or document AI systems such as Textract, Document AI or Azure DI. GPU inference stacks including vLLM, TensorRT-LLM, Triton, SGLang or Ray Serve. Evaluation infrastructure for ML systems such as golden sets, regression gates and human in the loop review. Experience with BFSI, healthcare or public sector compliance and data residency constraints. On premise or air gapped deployment experience. What you would own: the architecture of the serving harness for Sarvam's vision models, including the accuracy work (multi pass extraction, ensembling, cross verification, schema constrained decoding, confidence calibration) and the hard trade off surface of accuracy against latency against rupees per page. Multi pass inference, model routing and cascades, self consistency and verification passes, confidence driven escalation, batching and caching strategy and GPU utilisation are named as the levers you would pull. You would also set the reliability bar for pipelines processing KYC, loan underwriting, claims and contracts. Stack named: Go, Python, Temporal, REST, Kubernetes, PostgreSQL, Redis, object storage and OpenTelemetry based observability. Location is Bengaluru. Who this is for: a backend or platform engineer who has run inference in production and cares about cost and latency as much as correctness. The ad closes by saying it wants people who can own the outcomes rather than people who match a checklist, which is a fair signal to apply if you are close but not exact.
Stated experience level is 5 to 8 years, written in the ad as a labelled field rather than buried in prose. The working pattern is stated just as plainly: five days working from office, in Hyderabad. HighRadius says the same on another engineering role in today's edition, so read it as a company policy rather than a one off. One oddity worth knowing: the published posting still contains an unfilled template placeholder where the cloud provider should be, listing the requirement as experience with AWS, Azure or GCP written inside square brackets in two separate places. The employer has shipped the template without choosing. In practice that means the specific cloud is probably negotiable, but it is worth asking which one the team actually runs on before you prepare. Key responsibilities as listed: architect and maintain complex infrastructure modules using Terraform for consistent environments across development, staging and production. Design and deploy scalable, highly available and fault tolerant systems on a major cloud. Build and optimise automated deployment pipelines using Jenkins, GitLab CI or GitHub Actions for containerised applications. Manage and orchestrate containerised workloads with Docker and Kubernetes on EKS, AKS or GKE. Use Ansible or Packer to automate server configuration and image creation. Implement security as code by integrating automated vulnerability scanning and IAM policy enforcement into the infrastructure as code workflow. Work with development teams to containerise applications and give them self service infrastructure. Required technical skills: expert level Terraform including state management, workspaces and reusable module development. Strong hands on cloud services covering VPC, IAM, compute, RDS and S3. Proficiency in Kubernetes and Docker including writing Dockerfiles and managing manifests or Helm charts. Advanced scripting in Python, Bash or Go. Expert Git knowledge including branching strategies and GitOps workflows. Experience with build tools such as Maven or Gradle for Java, Node or Python environments. Who this is for: an infrastructure engineer five to eight years in whose strength is Terraform and who wants a platform building role rather than a support rota, and who can commit to a full time office return in Hyderabad. If hybrid or remote matters to you, this is a clear no.
Stated requirement is 6 or more years of industry experience building and deploying machine learning systems in production, with clear end to end ownership. What we are looking for, as listed: a strong foundation in machine learning and applied statistics, with hands on depth in NLP, transformers, embeddings and retrieval based systems. Practical experience with modern generative AI tooling such as LangGraph, LangChain or Amazon Bedrock. Strong Python skills and experience building distributed ML pipelines on cloud infrastructure such as AWS or Databricks. A solid grasp of feature engineering, model evaluation and MLOps practice. A product mindset, wanting to build AI products customers use and measuring yourself on customer impact. Excellent communication, including explaining complex technical work clearly and holding your own with product and business partners. Comfort with ambiguity and the judgement to drive execution independently. Nice to have: experience with RAG architectures, vector databases and prompt engineering. Hands on work with PyTorch or TensorFlow. A background in B2B SaaS, enterprise AI products or forward deployed engineering, especially where you worked directly with complex customer data and delivered quickly. What you would own: machine learning problems end to end, from data exploration and modelling through deployment, monitoring and iteration in production. Building NLP, LLM and agentic systems at enterprise scale including retrieval based architectures and multi agent workflows. Developing ranking, recommendation, prediction and optimisation models that are explainable rather than black box. Partnering with product and go to market teams to turn ambiguous business problems into shipped capabilities. Improving performance, scalability and reliability of production ML systems and helping shape AI platform architecture. Location: Bengaluru. The team is distributed across the United States and India, though the posting does not state the role as remote. Who this is for: an ML engineer six or more years in who ships to production and wants the explainability problem specifically. The ad says plainly this is not a research role, so if you want to publish rather than deploy, look elsewhere.
Stated requirement is 6 to 10 years of experience in distributed systems, storage systems or databases, algorithms and data structures, or Unix and Linux systems internals such as filesystems and system calls, and administration. A Bachelor's or Master's degree in engineering, specifically computer science or information systems, is also listed. What makes this different from a general DevOps posting: the requirement is written around systems fundamentals rather than a tool list. Filesystems and system calls are named directly, as are algorithms and data structures. If your reliability experience is mostly pipeline and dashboard work, the interview will likely go somewhere you are not expecting. If you have debugged a kernel level or storage level problem in production, this is aimed at you. Also listed: excellent communication skills and a sense of ownership, with a systematic problem solving approach. Context on the platforms you would be keeping up, from the ad: Tachyon, the cloud native banking stack built for population scale systems. Cipher, a unified authentication platform for secure high volume banking environments. Digital Credit as a Service, letting banks launch credit lines on UPI. Elena, a conversational AI platform for banking. Pixel, described as India's first digital native credit card, launched with HDFC Bank, for whom Zeta also rebuilt the PayZapp app. Sparrow, a card experience for non prime cardholders in the United States. Location: Hyderabad. The posting does not state a working pattern. Who this is for: an SRE or systems engineer six to ten years in who wants financial infrastructure where failures are expensive and visible. Banking and payments work carries real compliance weight and real out of hours pressure, and the upside is depth you cannot easily get elsewhere. Note the title says Lead, but the requirements are all hands on engineering rather than people management.
Stated requirement is 6 or more years of professional software engineering experience. The ideal candidate, as listed: deep experience with at least one modern programming language, with Python, Go and Rust named as examples. Strong technical judgement and the ability to independently solve complex engineering problems. Excellent communication and comfort collaborating across teams and disciplines. Comfortable with modern infrastructure and delivery systems including containerised applications, Kubernetes and CI/CD tooling, with Drone.io named as an example. Collaborative, detail oriented and interested in building reliable, usable software. A bonus is experience building and maintaining full stack applications from front end interfaces through to backend APIs. Position expectations: own the implementation and long term maintenance of internal tools and platforms. Lead technical design discussions and contribute to architectural decisions. Write high quality maintainable code and set a strong engineering example for the team. Identify and proactively address technical debt, reliability risks and scalability concerns. Collaborate with engineers, product partners and other stakeholders to prioritise and deliver high impact work. The success measures published in the ad, which are worth noting because most postings do not commit to any: within three months, demonstrate strong ownership of one or more internal systems and contribute significantly to ongoing initiatives, and independently deliver meaningful improvements that reduce manual effort or operational friction. Within six months, have driven technical improvements or new tooling that measurably improves internal engineering efficiency, reliability or velocity. Location and working pattern: the posting says MongoDB is looking to speak to candidates based in Gurugram for its hybrid working model, so this is a hybrid role tied to that city. Who this is for: an engineer six or more years in who is happy that their users are colleagues rather than customers, and who wants the latitude of a team being built rather than one already running. Internal tooling work is often undervalued on a CV but the ownership here is broad and the success measures are unusually concrete.
Stated requirement is 6 to 8 years of technical support experience, preferably with SaaS or cloud based platforms. Two things to weigh, both stated in the ad rather than inferred. First, the title says Lead and the requirement is six to eight years, but the job summary describes the role as a key first level liaison between the company and its customers. First level at six to eight years is an unusual combination, so it is worth asking in interview what the Lead in the title actually confers. Second, this is a 24x7x365 operations centre and the posting states that candidates must be flexible to work any shift based on business needs, including Saturday or Sunday. Must have skills as listed: 6 to 8 years of technical support experience, preferably SaaS or cloud. Basic SQL knowledge and working experience with one or more databases such as Postgres or MySQL. Familiarity with ITSM tools such as ServiceNow, Jira or Salesforce. Good hands on experience with REST APIs and webhooks. Experience analysing, investigating and identifying the root cause of complex customer issues and communicating findings to the right group. Strong problem solving and communication skills. The ability to work in shifts and under pressure. A proven ability to collaborate in a fast paced team. The ad also asks for strong English communication, excellent customer relationship skills, and prior experience supporting international customers, with United States or United Kingdom experience preferred. Key responsibilities: troubleshoot and resolve customer reported issues by phone, chat and remote tools. Perform root cause analysis and recommend corrective actions. Collaborate with engineering, QA and product teams. Work support rotations including incident escalation handling. Maintain case documentation and follow up with customers. Escalate unresolved or critical issues with supporting technical detail. One clarification on the word remote in this posting: it refers to remote troubleshooting tools used to reach customer devices, not to remote working. The role is based in Bengaluru. Who this is for: an experienced support engineer who wants hardware plus software problems rather than pure SaaS tickets, and who can work a rotating international roster.
Stated requirement is 7 or more years of professional experience in software development, with a Bachelor's or Master's degree in Computer Science, Electrical Engineering or a related field. Qualifications as listed: a deep understanding of JVM internals including garbage collection, JIT compilation, class loading and the memory model. Proficiency in at least one JVM language with extensive experience of its runtime environment. Strong programming skills in Scala, Java, Rust or other systems level languages. Extensive experience with operating system concepts including processes, threads, concurrency, scheduling and I/O. A proven track record of building and optimising high performance, scalable and reliable systems. Experience with distributed systems concepts and technologies. Excellent problem solving, analytical and debugging skills. Strong communication and collaboration. Experience with performance profiling and tuning tools. Contributions to open source projects related to the JVM or systems software. Experience with RPC frameworks. What you would do: design, implement and maintain core system infrastructure and low level software components. Optimise system performance, reliability and scalability. Work with JVM internals, memory management, concurrency and distributed systems. Collaborate with senior engineers and architects to define technical strategy and roadmaps. Mentor junior engineers. Take part in code reviews, design discussions and architectural decisions. Troubleshoot complex system issues. The ad is explicit about scope, and it is worth quoting the shape of it: this is not a full stack role, and the expertise is meant to be focused on the intricate details of system internals, performance and efficiency. Applying with a general backend CV and hoping to learn JVM internals on the job is unlikely to work here. Location: Bengaluru. The posting does not state a working pattern. Who this is for: a systems engineer seven or more years in who has genuinely tuned a JVM in anger, profiled garbage collection pauses, or written performance critical Scala, Java or Rust. If that describes you, this is one of the more technically serious postings in today's edition.
Stated requirement is 7 or more years of experience in technical support, system administration or a related customer facing role, with a technical background in systems administration, network engineering or software engineering. What you bring, as listed: strong verbal and written communication in English. A customer oriented focus. A good understanding of cloud native and container based technologies, including cloud platforms such as AWS, GCP and Azure and frameworks such as Kubernetes and Docker. An understanding of the product lifecycle and future direction for the supported products. A strong understanding of cloud native and container based distributed systems such as Kubernetes. Advanced hands on generalist experience across Java including the JVM and its components, operating systems including Linux and Windows, and networks including LDAP, load balancers, proxies and SSL. Experience with APIs and REST calls. Experience with web and application servers such as Tomcat, Apache, IIS, NGINX and JBoss. Advanced troubleshooting in web technology systems including HTML, CSS and JavaScript. Experience with SSO, SAML and Active Directory. Bonus points: knowledge of databases or search software technologies, experience with SaaS or distributed systems, being a team player able to work in a fast paced environment, a proven strong technical understanding of software products, and collaboration with developer teams on escalation issues. The ad also says curiosity is key and suggests researching and downloading the products before applying, which is a reasonable hint about how the interview will go. What you would be doing: ensuring technical customer issues are serviced within contractual service level agreements and managed to resolution. Maintaining strong customer relationships for the delivery of technical support. Resolving customer problems by telephone, email, chat or remote access. Continuously improving support process efficiency and customer satisfaction. Working across multicultural and geographically distributed teams. Contributing to product documentation, the customer knowledge base and best practice guides. Location: Bangalore. The team is described as spread across 12 time zones and 15 countries working as one unit. Who this is for: an experienced support engineer who wants genuinely deep technical work and direct contact with product engineers, rather than a tiered script. The Java and Linux depth asked for here is closer to an engineering requirement than a typical support one.
Stated requirement is a minimum of 5 years of experience writing Kotlin and a minimum of 8 years of experience building software for the Android platform. Two separate minimums sit in the same must have list, and the higher one is the real gate. We have published 8 years for that reason. A parser taking the first or lowest number here would advertise this as a five year job, and a five year Android developer would be rejected on the second line. Must haves, as listed: minimum 5 years writing code in Kotlin. Minimum 8 years building software for the Android platform. Experience developing enterprise level SDKs. Expert level knowledge of Kotlin, the Android SDK, Jetpack Compose, Coroutines, Gradle and dependency injection. Taking ownership of features from design and implementation through deployment and maintenance. A high level of personal accountability with strong technical skills, creative problem solving and a collaborative spirit. Experience writing and maintaining a comprehensive suite of automated unit and integration tests. The ability and desire to mentor and grow other engineers through code reviews, design reviews and over the shoulder debugging. Excellent verbal and written communication in English. Good to haves: Kotlin Multiplatform for cross platform development. Additional programming experience in C, C++ or Python. Card payment knowledge covering EMV and ISO8583. Experience building libraries used by other engineers. Knowledge of security best practices and standards. Experience in the payments industry. What you would do: work on solutions for Adyen's payment terminals covering card payments, Apple Pay and Google Pay on mobile phones, and QR code payments, and communication with the Adyen backend. Develop the main business logic in Kotlin, deployed on both Android based terminals and mobile phones. Own features end to end from design and implementation through testing and monitoring. Location and working pattern: Bengaluru, and the ad states directly that Adyen is an office first company that values in person collaboration and does not offer remote only roles. That is unambiguous, so do not apply hoping to negotiate it. One line to weigh: the role description mentions driving technical strategy and building a high performing team. Every listed requirement is hands on engineering and no reports, hiring or performance duties are named, so we read this as senior individual contributor scope with mentoring attached. Who this is for: an Android engineer with eight or more years who wants low level payments and SDK work rather than app features.
Stated requirement is 8 or more years of experience in software engineering, with a strong record of technical leadership and end to end ownership. What you would do: lead full stack architecture and system design for features used by millions of customers across web and cross platform environments. Own complex end to end systems, taking responsibility for building, integrating and maintaining both frontend and backend components including the backend for frontend layer, which the ad calls out as critical. Mentor and guide high performing teams, providing technical leadership and supporting the growth of peers. Drive technical decisions and influence architecture and best practice across multiple squads. Collaborate with product and design to deliver features and experiments that affect business outcomes. How the company frames the level: the ad describes Staff Engineer as a key role working with individual contributors and senior leadership, says its lead engineers are heavily involved in hiring and mentoring, and expects the person to push Agoda forward technically by adopting new technologies and setting higher standards. Involvement in hiring here reads as interviewing and technical assessment rather than people management, since no reports or performance responsibilities are named and the role is described as designing and implementing systems. About the team: the Full Stack Engineering department has several front end focused teams covering accommodations, flights, payments, marketing and post booking. Teams work across the stack and build end to end systems including user interfaces, APIs, backend systems and database systems, with a high degree of automation, CI/CD and a modular approach, and products under continuous experimentation. Location and working pattern: the title itself specifies Gurugram based, so treat the location as fixed rather than flexible. The posting does not state office days. Who this is for: a senior engineer eight or more years in who wants architecture scope across both halves of a large consumer product, and is comfortable that the weighting is backend. If you want to specialise narrowly in one layer, the breadth expected here works against that. If you want influence across squads without moving into management, it fits well.
Stated requirement is 8 or more years of experience in customer facing technical roles, featuring 3 or more years driving value in Technical Account Management, Customer Success, Solutions Delivery or Sales Engineering, within cloud, web security, networking or infrastructure domains. We publish this as an eight year role. The three year figure is a subset requirement describing how much of the eight has to be in a specific discipline, and reading the smaller number as the entry bar would send a three year candidate into an application they cannot pass. Minimum qualifications as listed: the 8 or more years above. Strong technical acumen with the ability to align customer business challenges to the Zscaler portfolio for the security outcomes they want. A proven ability to analyse customer data to gain insights and develop tailored adoption strategies and risk mitigation plans. A foundational understanding of AI and ML technologies and experience using, securing or positioning AI driven solutions within your domain. A solid understanding of core networking protocols such as HTTP, DNS and SSL, and technologies including DLP, sandboxing, SD-WAN and CASB, with some ability to troubleshoot network issues using tools such as Ping, Traceroute and MTR. Preferred qualifications: experience using AI powered operational analytics or predictive health scoring dashboards to evaluate deployment health, uncover adoption blockages and mitigate customer risk, plus an in depth understanding of enterprise infrastructure and cloud security. Relevant industry certifications are named, including CISSP, CCNP, CCIE, Network Plus, AWS, Azure and Google Cloud. What you would do: serve as a strategic technical advisor, understanding customer goals and guiding them through their zero trust journey as the central post sales point of contact. Build and nurture deep relationships with key customer stakeholders. Provide proactive recommendations so customers adopt and get the most from the platform. Location and working pattern: the ad states this is a hybrid role based in Bangalore, reporting to the Manager, Technical Success within the Customer Success department. Despite Manager appearing in the job title, this is an individual contributor role managing customer accounts, not people. Who this is for: an experienced pre sales or post sales technical specialist in networking or security who wants ownership of customer outcomes. Readers of this list asked for technical account management and customer success roles by name, and this is a senior example of exactly that.
Stated requirement is 9 or more years of experience across software engineering, network security and AWS security. What you will bring, as listed: a proven track record as an experienced infrastructure security designer implementing secure cloud, networks and corporate IT infrastructure, and experience working at a SaaS product company. What you would be doing, grouped as the ad groups it. On strategy: develop and document comprehensive security policies, reference architectures, design patterns and the strategic roadmap for infrastructure security, and keep current with network and infrastructure security practice. Collaborate with engineering, AWS and architecture teams so proposed designs meet both business objectives and security requirements. On technical design and architecture: provide technical leadership to build security into all infrastructure and network designs across AWS cloud, SaaS applications and IT environments. Design and re architect the AWS infrastructure to implement network segmentation, deep packet inspection, firewalls, VPNs and VPC configurations. Design secure access and network solutions for production environments and own the overall access management framework. Act as the security point of contact for change management, reviewing new infrastructure designs. Own and implement security components including privileged access management, Access Analyzer, Identity Center and role based access control, GuardDuty and web application firewall. Design and architect integrations with security tools such as SIEM and cloud workload protection. On compliance and partnership: represent infrastructure security during regulatory and compliance audits including PCI, SOC, ISO and HITRUST. Work with corporate IT to implement and continuously improve network and security controls in the corporate environment. Work closely with security operations and incident response teams providing technical leadership, and mentor junior infrastructure security professionals. Location: Bengaluru. The posting does not state a working pattern. Who this is for: a senior cloud security engineer who wants design authority rather than alert handling, and is comfortable that the scope includes corporate IT and audit representation as well as production AWS. Reporting into the VP of Information Security means short lines and real influence, and it also means the gaps are yours to own.
Stated requirement is 10 or more years of professional software engineering experience. Education, as listed: a Bachelor's or Master's degree in Computer Science, Information Technology or a related field, with an educational background from a highly selective premier engineering institution focused on Computer Science fundamentals stated as preferred. That preference is in the ad, and it is worth knowing it is there. Experience and skills as listed: a strong understanding of data structures, algorithms, design patterns, and both object oriented and functional programming. A proven track record of leading technical initiatives from conception to global production deployment. Deep expertise in Java and modern web technologies with mastery of data structures, algorithms and complex design patterns. Extensive experience building and scaling distributed systems in AWS cloud native environments, and modernising applications and platforms. Strong knowledge of enterprise application architecture. Experience managing large scale codebases where performance optimisation and bottleneck identification are critical. Experience integrating AI and ML, specifically implementing intelligent features such as RAG or agentic workflows into enterprise software, is preferred, as is experience using AI tools and models such as Amazon Q, Kiro and Claude. Expert level proficiency in Java or a similar major language. Hands on experience with Docker, Kubernetes and advanced CI/CD automation. Deep familiarity with performance monitoring and observability. Key responsibilities: work with product leadership to turn long term business goals into scalable technical milestones and define the technical direction. Lead the design of distributed, event driven and cloud native systems, making high level decisions on system boundaries, data consistency and integration patterns. Drive adoption of AI native engineering, using AI tools to improve developer productivity and implementing AI features into the platform. Set and enforce the standard for system design and code quality, keeping the codebase maintainable. Location: Chennai. The posting does not state a working pattern. Who this is for: an architect level engineer ten or more years in who wants technical authority without moving into people management. The ad describes the role as the technical anchor and the architect of the team's success, so expect influence to be the main currency.
The posting states no number of years anywhere, and we have published it with no experience figure rather than inventing one. The requirements are written as capabilities instead, and they are substantial, so this is not an entry level role despite the absence of a number. What you will bring, as listed: experience owning complex customer facing technical cases from initial contact through triage, reproduction, bug reporting, resolution and clear customer communication, including difficult or escalated interactions. Strong experience with Linux systems administration, scripting, Git, and continuous integration and delivery in production or customer environments, with the ability to investigate issues at both infrastructure and application levels. The ability to mentor teammates on complex troubleshooting and customer communication through pairing sessions, case reviews and cross team collaboration. Experience collaborating with product, engineering and sales teams to turn customer feedback into product fixes, feature improvements and roadmap priorities. Familiarity with DevOps practices and technologies such as Kubernetes and serverless computing, and an understanding of how different GitLab implementations affect customers. A demonstrated ability to learn, collaborate across teams and apply transferable skills from related technical support or engineering roles. What the job actually is: sitting at the intersection of support and engineering, helping customers running GitLab in demanding environments. Working in the Engineering department directly with customers as they hit edge cases. Digging into Linux systems, logs and the Ruby on Rails codebase to troubleshoot performance issues, reproduce bugs and contribute merge requests that fix problems at source. Improving documentation and refining support processes in the issue tracker. Location and working pattern: GitLab states that all of its roles are remote, though it notes some roles carry location based eligibility requirements. The listing is attached to Bangalore, India. We checked the remote claim against the posting text rather than a tag. The team is described as globally distributed across the Americas, Europe, the Middle East, Africa and Asia Pacific, working asynchronously, with shifts structured to support personal lives while meeting customer needs. Who this is for: a support engineer who can read and write Ruby and wants to fix bugs rather than route them, and who wants genuinely remote work. The transferable skills line means adjacent engineering backgrounds are welcome.
That's the last 5 days. The rest of the 512 open roles stay in their editions: