No roles match that combination.
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.
Read this before you apply
- Two advertisements today do not tell you how much experience they want, and the only number in each is the company's own age. Smartsheet's Principal Software Engineer contains exactly one years figure: "For over 20 years, Smartsheet has empowered teams to manage work seamlessly." Appian's Test Automation Engineer contains exactly one: "We have been automating processes for more than 25 years." Neither sentence is a requirement, and any tool that reads the smallest or largest number in a posting will publish those as 20 and 25 years. Six of today's 46 roles state no experience requirement anywhere. Across every board we swept this morning, about one advertisement in five was the same. We have grouped those six under "Years not stated" rather than guessing a number, and where a posting says nothing we say nothing.
- The smallest number in an advertisement is rarely the bar, and today gave four examples. Workato's Forward Deployed Engineer says "a total of 4 or more years of relevant experience, with at least 1 years of experience in Workato". The bar is four, the one is a subset, and Workato posted that same role six times. LogicMonitor's Customer Success Engineer opens by asking for 2 or more years in customer facing support, then asks separately for 3 or more years supporting SaaS monitoring products, 3 or more in Linux, Windows or network administration, and 3 or more with cloud platforms. Three is the real floor, so that is what we published. Okta has a role titled simply Software Engineer, with no level attached, that wants 3 or more years of native iOS. And Zscaler's Escalation Engineer carries no seniority word at all while asking for 8 or more years, five of them in data loss prevention specifically.
- One employer posted the same job twice, and the only difference is the sentence about years. Rubrik is advertising Senior Software Engineer, CPD (IAM) in Bangalore and Software Engineer, IAM in Pune. The must have lists are the same: Golang, deep knowledge of OIDC, OAuth 2.0 and SAML 2.0 including token internals and failure modes, Active Directory, applied cryptography and PKI. The Bangalore posting adds "minimum experience of at least 8 years". The Pune one states nothing. So the plain Software Engineer title in Pune is almost certainly not an opening for a beginner, and the only honest thing to say is that Rubrik has not published where the bar sits. If identity work is genuinely your area, that missing line is room to argue your own case.
- A remote tag is not a remote job, and one advertisement today contradicts itself in a single screen. Smartsheet's posting is tagged remote in its body, while its own job title reads "Principal Software Engineer (Hybrid in Bangalore)". Both cannot be true and the title is the more specific claim, so we have not counted it as remote. Four roles here are genuinely remote and each says so in a full sentence: Coinbase lists the role as Remote in India and describes itself as remote first but not remote only, with quarterly in person sessions it calls surges, and all three GitLab roles carry the company's standing line that all of its roles are remote. Two more are the opposite: Adyen states plainly that it does not offer remote only roles, and Fivetran's hybrid model asks for two days a week in the office.
- Entry level is genuinely thin today, and we would rather say so than pad it. Two roles are open to someone at the start of their career. Graviton Research Capital is hiring a Software Engineer for the 2027 graduating batch, which is a campus hire: if you have already finished your degree, that one is not for you, and if you are still studying it is a rare chance at a quantitative trading firm with no years, no marks cut off and no degree class published. HackerRank's Customer Experience Engineer L1 asks for a recent graduate or early career engineer with up to three years, and adds that strong candidates with no professional experience are encouraged to apply. Two out of 105 boards swept is a poor day, not a good one. The whole board currently carries 20 open roles at one year or less, which is more than a single edition can show, and you can see all of them here: https://www.munotes.in/dailytechjobs?exp=0
- Office days, shifts and locations, taken from the postings themselves. Kaseya requires three days a week in its Pune office. Fivetran asks for two. Appian states in office for its Senior Technical Consultant in Chennai. Everpure describes itself as primarily an in office environment, and one of its advertisements still contains an unfilled template placeholder where the office name should appear. Tekion's SOC role runs on a rotating 24 by 7 roster including nights, weekends and holidays, and states it twice. Netradyne runs a 24 by 7 by 365 operations centre and asks for flexibility on any shift including Saturdays and Sundays. HackerRank and Smartsheet both say hybrid without saying how many days, which is worth asking before you interview.
- Three employers published things they did not have to. Coinbase prints the annual base salary for its Staff Software Engineer role, 9,424,500 rupees excluding equity and bonus, which almost no posting in India does, and also states that candidates may submit a maximum of three applications in any six month period, so choose carefully. Adyen prints its hiring timeline: a response within five business days and an interview process of about four weeks. LogicMonitor discloses that it uses AI tools to support human review in hiring, and gives an address for opting out with your application still reviewed. Two advertisements also went out with unfilled template placeholders still in the text, Everpure's office name and Adyen's requirement list, which is a drafting slip rather than anything sinister.
- Where one employer has more than one role here, they are different teams. Five employers have three roles each. Everpure's are storage systems on FlashBlade, a ServiceNow platform seat and an integrations role inside procurement. Okta's are iOS, QA automation and continuous delivery tooling. Databricks has search relevance, forward deployed engineering and a fifteen year backend seat. Appian has a lead engineer, a test automation role and a customer facing consultant. GitLab's three are all on or beside its vulnerability management team and all remote. Thirty employers in all, which is the widest spread we have had in a while.
We read every posting by hand before it goes on this page. The same write-up goes out to the daily email.