No roles match that combination.
Added August 11, 2026
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 5 or more years in technical account management, professional services, senior support or project management roles, AND 5 or more years of relevant industry experience implementing, operating or supporting scalable, fault tolerant distributed database management systems. WHAT THE POSTING REQUIRES - Technical breadth and depth across DBMS, OLAP, cloud and SaaS platforms, distributed systems software engineering, Linux and Unix, Kubernetes, and system or network administration and big data. - Experience leading and shipping large scope technical projects with multiple experienced engineers. - Expertise with a public cloud provider and its infrastructure as a service offering. - Excellent communication and the ability to work customer facing alongside Support Services, Engineering and Sales. - Availability according to the scheduling required to deliver 24x7 support in a global distributed environment. WHAT THE JOB ACTUALLY IS DAY TO DAY Working with strategic and enterprise users on onboarding, production launches and proofs of concept; providing architectural, technical and migration guidance; leading projects, escalations and meetings; owning L3 support cases and escalations with the L1 and L2 team; partnering with Product Management, Engineering and Sales on roadmap and account plans; assisting with hiring and mentoring new team members; and contributing to docs, knowledge base articles, reference architecture and QA. LOCATION AND WORKING PATTERN Remote within India, but the posting is explicit that you must be open to regional travel for onsite customer visits, currently estimated at up to 35 percent of the time. There is also 24x7 scheduling to plan around. Treat both as firm. HONEST FIT GUIDANCE This is a genuinely remote role at a company where remote is normal, which matters if relocation is not affordable for you, and it is the exact TAM title readers have asked for by name. Balance that against the travel figure, which is high, and the fact that this is a new role at ClickHouse assembling functions the existing team performs in part, so the shape of the job may move in the first year.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 5 years of experience in a highly technical, customer facing role, and names the shapes that count: onboarding engineering, customer success engineering, DevOps or platform engineering, or technical consulting. WHAT THE POSTING REQUIRES - A bachelor's degree or equivalent practical experience. - Hands on experience with production workloads in at least one major cloud provider ecosystem across AWS, Azure or Google Cloud. - Deep technical proficiency in core networking infrastructure including VPC and VNet architectures, routing protocols, peering and PrivateLink or private endpoints. - A proven record implementing enterprise identity and access management including SSO with OIDC or SAML and role based access control design. NICE TO HAVE, NOT REQUIRED - Strong infrastructure as code with Terraform plus configuration management such as Ansible. - Linux administration, containerisation and orchestration with Docker or Kubernetes. - Hands on graph database experience, ideally Neo4j, with query and performance tuning including Cypher optimisation. - Familiarity with observability stacks such as Grafana and Prometheus, Datadog, CloudWatch or Splunk, and with ETL or CDC platforms. - Exposure to cloud compliance frameworks such as SOC 2, GDPR and HIPAA plus data residency deployment patterns. WHAT THE JOB ACTUALLY IS DAY TO DAY Leading technical discovery sessions with enterprise customers to agree success criteria, KPIs and milestones; guiding the creation of AuraDB environments or self managed clusters across the three major clouds with secure network architectures using private endpoints and IP allow lists; implementing system hardening, TLS termination and encryption at rest; and shaping onboarding blueprints that shorten time to value. LOCATION AND WORKING PATTERN Listed as Remote: India. HONEST FIT GUIDANCE Notice what this role does not require, namely graph database experience, which is only preferred. The hard requirements are cloud networking and enterprise IAM. That makes it genuinely open to a DevOps or platform engineer who has never touched Neo4j but can hold a technical conversation with an enterprise customer. If you want remote and your background is infrastructure rather than product engineering, this is the closest fit on today's list.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 6 or more years in software engineering or technical consulting roles with a focus on automation or integration platforms. WHAT THE POSTING REQUIRES - A background in information systems, computer science, engineering or equivalent industry experience. - Experience delivering end to end automation solutions on iPaaS platforms such as Workato, MuleSoft, Boomi or Snaplogic, with Workato experience strongly preferred. - Working experience with RESTful APIs and OAuth authentication. - Working experience with SQL in any relational database. - Experience with generative AI tools such as OpenAI or Anthropic and with vector databases. - Demonstrated experience on field related processes such as CRM, sales operations or customer success workflows. - Experience with agile methodologies and project management tools. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, implementing and maintaining scalable AI driven automations that improve productivity across field processes; identifying and removing inefficiencies in field workflows and documenting the standards that keep things healthy; leading discovery and solution design sessions with field teams; actively integrating AI capabilities into automation workflows; documenting solutions and processes for team learning and onboarding; dedicating time to self directed learning on AI and automation; and mentoring junior engineers. LOCATION AND WORKING PATTERN Hyderabad. HONEST FIT GUIDANCE Be clear that the customer for your work here is Workato's own field organisation, not external users. That suits people who like being close to the business and having their impact measured in hours saved, and frustrates people who want to ship product. The role is described as working independently across the full delivery lifecycle and raising the bar for the team, so autonomy is expected from the start rather than earned. If you have deep MuleSoft or Boomi experience but no Workato, the posting still counts you in.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 6 or more years of relevant experience, plus a bachelor's degree in a related field or equivalent business experience. An MBA is listed as preferred, as is 5 or more years in the SaaS industry. WHAT THE POSTING REQUIRES - The ability to manage large projects and processes independently with limited supervision. - Recognised subject matter expertise in industry standards. - The ability to adapt situationally and pick up new technology or processes as partners require. - Strong cross functional knowledge of business processes. - The ability to grasp and clearly explain technological and business concepts. - Strong knowledge of the IT service provider market. - Both technical acumen and business management skills. WHAT THE JOB ACTUALLY IS DAY TO DAY Making sure partners get maximum value from their ConnectWise investment, using all the licences they hold, and reaching a successful renewal; proposing solutions to partner problems based on the platform and an understanding of their business; developing an understanding of the business challenges partners typically face and mapping platform features to them; acting as an escalation point to drive resolution proactively; travelling to partner locations and IT Nation events; creating scalable playbooks and processes for partner interactions; and identifying processes that improve cross functional visibility for requests and escalations. LOCATION AND WORKING PATTERN Bangalore. Travel to partner locations and company events is part of the role. HONEST FIT GUIDANCE Two things to check before applying. The posting says the role may coach, review or delegate work to other team members, which reads as senior peer responsibility rather than line management, but it is worth confirming which it is. And renewal is named as an outcome, so ask early how success is measured and whether any part of it is commercial. If you want a customer success role that stays technical, the MSP domain here gives you something concrete to be expert in.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 7 or more years as an integration developer or in a similar role, plus a bachelor's degree in computer science, software engineering, information systems or a related field. WHAT THE POSTING REQUIRES - Strong experience with API integrations and API management across REST, SOAP, webhooks, OAuth and token based authentication. - Experience designing and managing APIs including lifecycle management, versioning, security and governance. - Proficiency in JavaScript for scripting hooks, transformations and custom logic. - Experience integrating ERP systems such as NetSuite, Acumatica, Microsoft Dynamics or SAP. - Hands on experience with cloud and SaaS platforms such as Salesforce, Shopify and Amazon. - Data transformation expertise across JSON, XML, CSV, EDI, mapping and normalisation. - An understanding of middleware and iPaaS architecture patterns. - Experience integrating and operationalising AI and LLM services. - Familiarity with agentic architectures and orchestration concepts including MCP servers. - Experience in consulting or professional services with direct client engagement. - Experience across the full delivery lifecycle from requirements to post go live support. WHAT THE JOB ACTUALLY IS DAY TO DAY Collaborating with clients to gather requirements and translate them into scalable technical solutions; building integrations across ERP, SaaS and on premise systems; designing data mappings and transformations that preserve data integrity; designing and managing APIs; end to end testing and validation; providing go live and ongoing support, advisory and knowledge transfer; building AI agents and deploying agentic services; mentoring junior developers; and training customers on the platform. LOCATION AND WORKING PATTERN Hyderabad. HONEST FIT GUIDANCE This is integration engineering, which is a real and durable specialism but is not product development. Your work will be shaped by other companies' data models and their deadlines. The upside is that the AI portion is unusually concrete for a job description: not familiarity with LLMs but building agents and running MCP orchestration for paying customers, which is genuinely useful experience to have on a CV right now.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for a minimum of 7 years of hands on experience in a technical support or engineering role related to the Databricks Data Intelligence platform, cloud data platforms or big data technologies. The posting repeats the figure as over 7 plus years in its own opening line. WHAT THE POSTING REQUIRES - A deep understanding of Databricks architecture and Apache Spark. - Experience with cloud platforms such as AWS, Azure or GCP. - Strong capability designing and managing data pipelines and distributed computing. - Proficiency in Unix and Linux administration. - Familiarity with DevOps practices. - Skills in log analysis and monitoring tools. - Demonstrated ability to diagnose and resolve complex technical issues methodically. - Exceptional written and verbal communication with technical and non technical stakeholders. - Proven experience managing high impact customer interactions. - A bachelor's degree in computer science, engineering or a related field, with an advanced degree or relevant certifications described as highly desirable. NICE TO HAVE, NOT REQUIRED - Additional big data tools such as Hadoop, Kafka or NoSQL databases. - Familiarity with automation tools and CI/CD pipelines. - An understanding of data governance and compliance requirements. WHAT THE JOB ACTUALLY IS DAY TO DAY Serving as the primary technical point of contact for escalated platform issues with expert level troubleshooting and diagnostics; engaging directly with customers; leading resolution of high priority incidents and running root cause analyses; working with engineering, product management and DevOps to drive platform improvements; maintaining documentation and internal knowledge bases; monitoring platform performance metrics to catch issues before they reach customers; and overseeing platform upgrades and patches. LOCATION AND WORKING PATTERN Bengaluru. HONEST FIT GUIDANCE Seven years of genuine Spark and Databricks depth is a high bar, and it is the requirement most candidates will miss rather than the communication one. If you have that depth, this is an unusually senior support role at a company where support engineers talk to engineering rather than through a ticket queue. If your Spark experience is using it rather than debugging it under load, this will be a stretch.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 7 or more years of overall IT experience, including 5 or more years of hands on Appian technical experience, or alternatively a record of leading architecture reviews and driving complex performance and reliability diagnoses. A B.Tech or B.E. in computer science, information systems or a related field is stated. WHAT THE POSTING REQUIRES - Python and SQL are required of all candidates. Beyond that the posting expects deep expertise in at least one named category, meaning extensive professional use rather than passing familiarity, and strongly prefers expertise across more than one. The categories are load testing and test execution (Locust, Apache JMeter, k6, Gatling). - Monitoring and observability (Grafana, Prometheus, InfluxDB or TimescaleDB, Elastic Stack, Dynatrace). - Database performance (SQL query analysis and execution plan reading with EXPLAIN and EXPLAIN ANALYZE, connection pool behaviour and tuning, index analysis and slow query diagnosis on MySQL, SQL Server, PostgreSQL or Oracle). - Programming and scripting (Python for Locust scripting, analysis automation and data pipelines, plus Bash). - Data analysis (the Python data stack of pandas, numpy, matplotlib and scipy, plus statistical analysis covering percentiles, standard deviation, confidence intervals and regression). NICE TO HAVE, NOT REQUIRED - An understanding of object oriented programming, relational database design and SQL deep enough to read execution plans and diagnose slow queries rather than only write them. - Experience building integrations using web services. - Comfort operating in cloud environments. LOCATION AND WORKING PATTERN Chennai, and this is not hybrid. The posting states that Appian was built on a culture of in person collaboration and that employees hired for this position are expected to be in the office five days a week. Take that at face value. HONEST FIT GUIDANCE The alternative route into the experience requirement is the useful detail. You do not need five years of Appian if you have led architecture reviews and driven complex performance diagnoses elsewhere, which opens the role to performance engineers from any stack. Appian's sibling Principal role in the same team asks 10+ overall and 7+ hands on, so there is a ladder here rather than a single rung.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 8 or more years of professional software engineering experience. WHAT THE POSTING REQUIRES - Extensive expertise in C# and .NET development. - Hands on Microsoft Azure, particularly AKS, Azure SQL and blob storage, plus Azure networking across VNet, NSG, Traffic Manager and Application Gateway. - Experience with containerised applications and cloud infrastructure. - Experience working across backend and frontend with Angular, React or similar. - A solid understanding of databases and Entity Framework. - A proven ability to debug complex production issues and lead incident response. - Strong communication and mentorship experience. NICE TO HAVE, NOT REQUIRED familiarity with Office or document generation systems and SDKs, and exposure to security and compliance practices such as OWASP and SOC 2. WHAT THE JOB ACTUALLY IS DAY TO DAY Maintaining, updating and optimising Azure infrastructure including AKS; owning end to end stability of the platform through bug fixes, small enhancements and system improvements; designing safe, incremental changes across .NET backend, database and Angular frontend; leading production incident triage, debugging and resolution; running root cause analysis and implementing preventative fixes; improving monitoring and telemetry through Application Insights; supporting controlled system wind down or migration; mentoring junior engineers; documenting architecture and operational procedures; and working with customer success on client specific issues. LOCATION AND WORKING PATTERN Pune. HONEST FIT GUIDANCE This is the most transparent job description in today's edition and it deserves credit for that, but read what it is telling you. Success is defined as the platform staying stable, incidents being resolved with clear root causes, and technical debt being reduced pragmatically. There is no roadmap here. For an engineer who wants deep ownership, incident leadership and a system they fully understand, that is a good trade and it is rare to be told so honestly. If you are optimising for feature work on a growing product, this is explicitly not that, and applying anyway wastes everybody's time.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 8 or more years of software engineering experience with deep expertise in React and modern frontend ecosystems. WHAT THE POSTING REQUIRES - Proven experience building frontend platforms or large scale UI systems. - Strong knowledge of TypeScript and modern JavaScript, React internals including hooks and the rendering lifecycle, and Next.js, server side rendering and edge architectures. - Experience with monorepos and build tooling and with design systems and component libraries. - Demonstrated experience influencing organisation wide architecture. The 2026 stack is listed as React 18+, TypeScript, design tokens, a GraphQL or backend for frontend layer, Storybook for component development, and Playwright and Jest for testing. WHAT THE JOB ACTUALLY IS DAY TO DAY Defining and evolving frontend platform architecture and establishing patterns for component architecture and state management, including build versus buy decisions on UI tooling; leading a scalable design system covering accessibility, internationalisation and theming, and maintaining reusable component libraries; building monorepo tooling, CLI and scaffolding generators and frontend CI/CD, and standardising linting and code quality; defining and enforcing performance budgets and leading optimisation of bundle size, runtime performance and rendering strategies with real user monitoring; acting as the technical authority for frontend decisions through architecture reviews and coding standards, and mentoring senior engineers; defining micro frontend strategy with Module Federation and shared dependency versioning; and enforcing frontend security practices including CSP, XSS prevention and secure OAuth and OIDC flows. LOCATION AND WORKING PATTERN Pune, hybrid, stated in the posting. HONEST FIT GUIDANCE The posting says the role should act as a multiplier across teams rather than purely as an individual contributor, and lists representing frontend engineering in executive level discussions. There are no direct reports named, so read this as a senior technical authority role, but expect a real share of your week to be influence, review and standard setting rather than code. Success is measured on adoption of platform components, build and deploy times, Core Web Vitals and developer productivity, which is a fair and unusually explicit set of metrics to be judged on.
THE EXPERIENCE THIS ROLE ASKS FOR States the experience band as 8 Years to 10 Years. WHAT THE POSTING REQUIRES - A bachelor's degree in computer science, information technology, engineering or a related field. - Experience in software testing and quality assurance. - A strong understanding of SDLC, STLC and Agile methodologies. - Experience testing web applications, mobile applications, APIs and database driven systems. - Strong defect tracking and troubleshooting skills. - Excellent analytical, problem solving and documentation abilities. NICE TO HAVE, NOT REQUIRED - Experience with test automation tools and frameworks. - CI/CD pipelines and DevOps practices. - API testing tools such as Postman, Rest Assured or Swagger. - Selenium, Cypress, Playwright, Appium or similar. - Familiarity with SQL and database testing. - Agile or Scrum experience. The key skills list names test automation, Python coding, API testing, web and mobile testing, regression and functional testing, Agile, CI/CD, defect management, SQL and database testing, root cause analysis, AI, and quality metrics and reporting. WHAT THE JOB ACTUALLY IS DAY TO DAY Creating, maintaining and executing manual and automated test cases; performing functional, regression, integration, system and end to end testing; designing and maintaining automation frameworks and wiring them into CI/CD so feedback is timely; producing test plans, cases, procedures and reports; planning testing schedules against delivery commitments; running root cause analysis with development teams; defining quality standards and release readiness criteria; and presenting testing insights that influence team decisions. LOCATION AND WORKING PATTERN The posting lists the work location as Mumbai or Pune and the work type as hybrid with three days in the office. The board itself tags the role to Pune, so confirm which city the requisition is actually for early in the process. HONEST FIT GUIDANCE Eight to ten years is a genuinely senior QA band and the responsibilities match it, including defining what done means with product and engineering. If you have that depth but your automation is Selenium era, note that Playwright and Cypress appear in the preferred list and Python is named as a key skill rather than Java.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 8 or more years of experience working on large scale systems or services. WHAT THE POSTING REQUIRES - Solid architectural and security knowledge backed by experience designing, implementing and evolving complex distributed systems. - Experience on projects requiring close collaboration with external teams. - Solid previous experience with Node.js in JavaScript or TypeScript building scalable backend services and creating and maintaining public and internal APIs. - Experience building full stack applications with an understanding of React. - A good understanding of SQL (PostgreSQL) and NoSQL (MongoDB) and how to optimise them under load. - Experience with Docker and cloud environments such as AWS and Azure. - Being a good mentor and communicator who can explain complex concepts simply. WHAT THE JOB ACTUALLY IS DAY TO DAY Helping drive the team's architectural vision and delivering new enterprise APIs and functionality; orchestrating and leading major technical projects across teams as needed; designing, architecting, coding and documenting large scale distributed systems; acting as a subject matter expert on scalable, reliable, maintainable distributed systems; mentoring and coaching less experienced engineers; collaborating with Product, Security and other engineering teams; balancing simplicity, flexibility, reliability and performance in technical decisions; and participating in the team's on call rotations. LOCATION AND WORKING PATTERN Bengaluru, tagged hybrid in the posting. Okta describes an immersive in person onboarding experience when you join. HONEST FIT GUIDANCE The useful context is what this team actually owns. Lifecycle management for B2B SaaS means the plumbing that creates, updates and deactivates users across customer organisations, which sounds routine and is in fact where the hard correctness and scale problems live. The on call expectation is explicit. If your Node.js experience is application servers rather than public APIs at this volume, expect the interview to focus there.
THE EXPERIENCE THIS ROLE ASKS FOR The experience section lists several figures and the real floor is 8 years. Published: 8+ years in SRE, DevOps or infrastructure engineering; 3 to 5 years with Kubernetes (EKS and GKE) and its ecosystem tools such as Helm and Karpenter in production; 3 to 5 years with AWS and GCP; 3 to 5 years using Terraform to manage multi cloud infrastructure; and 5+ years of coding experience in Python, Go or similar. Also required: a proven track record leading high impact migration projects specifically from ECS to EKS or GKE and enabling microservice architectures, plus experience implementing SLOs and SLIs and running root cause analyses. Technical requirements: strong hands on experience architecting and operating cloud native distributed systems across AWS and GCP; deep Kubernetes expertise covering design, provisioning, scaling and advanced production troubleshooting; proficiency with infrastructure as code such as Terraform multi provider, Ansible or CloudFormation; solid coding in Python, Go or Shell focused on automation; advanced understanding of CI/CD with ArgoCD, GitLab CI or Spinnaker, plus Linux and networking fundamentals including Direct Connect or Interconnect, DNS, routing and load balancing; experience managing databases and caching such as RDS or Cloud SQL, Redis or Memorystore, PostgreSQL and MySQL in cloud environments; observability tooling including Prometheus, Grafana, ELK, Loki and OpenTelemetry; and working knowledge of container security and secrets management with HashiCorp Vault or cloud secret managers. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, building and operating scalable, secure infrastructure across AWS and GCP; leading reliability and modernisation initiatives including the container platform migration; acting as a technical authority in Kubernetes, cloud infrastructure and GitOps; partnering with development teams on production readiness and observability; managing infrastructure as code; championing SRE practices including SLOs, blameless postmortems and improved incident response; mentoring engineers across teams; and participating in the on call rotation. LOCATION AND WORKING PATTERN Bengaluru, hybrid. HONEST FIT GUIDANCE Okta is running three separate Staff SRE requisitions in Bengaluru at the moment (this one for Core iDaaS, one for Ecosystem, one for Infrastructure), all at the same 8+ bar. If this specific migration brief does not fit, the others share the profile. The migration requirement is the real gate: it is asked for as a track record, not as an interest.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 8 or more years of experience in an object oriented language, preferably Java. Required knowledge and skills as published: hands on experience with cloud based distributed computing technologies across messaging systems such as Kinesis and Kafka, data processing systems such as Flink, Spark and Beam, storage and compute systems such as Snowflake and Hadoop, and coordinators and schedulers such as those in Kubernetes, Hadoop and Mesos; experience developing and tuning highly scalable distributed systems; and an excellent grasp of software engineering principles. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, implementing and owning data intensive, high performance, scalable platform components; working with engineering teams, architects and cross functional partners on project development, design and implementation; conducting and participating in design reviews, code reviews, analysis and performance tuning; coaching and mentoring engineers to help scale the engineering organisation; and debugging production issues across services and multiple levels of the stack. LOCATION AND WORKING PATTERN Bengaluru, hybrid. HONEST FIT GUIDANCE This is one of the clearest data engineering roles in this edition and it is genuinely platform work, meaning you build the systems other teams' pipelines run on rather than the pipelines themselves. The team describes itself as small, fast and ownership heavy, and the posting says it expects a lot from engineers and gives them significant new projects and equity in return, which is a claim to test rather than take. If your background is analytics engineering or dbt style transformation work, note that the requirement here is distributed systems in Java, not SQL.
THE EXPERIENCE THIS ROLE ASKS FOR Read the experience requirements carefully, because the headline figure is not the floor. Published: 5+ years of experience with Kubernetes, Helm, Karpenter and Istio; 8+ years of experience with infrastructure as code tools such as Terraform, Chef or Ansible; and 8+ years of experience with serverless computing (AWS Lambda, API Gateway) and microservices architecture. The Kubernetes number is the smallest one on the list and the real bar for the role is 8 years. Other required qualifications: proven experience with AWS across EKS, ECS, RDS, S3, CloudFormation and IAM plus a solid understanding of cloud native architectures; strong expertise in Kubernetes platform creation, management and optimisation including highly available clusters, networking and storage; hands on experience with Helm for application deployment and management; and practical experience with Karpenter for dynamic cluster scaling. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, implementing and maintaining highly available, scalable, fault tolerant Kubernetes platforms optimised for production workloads; building, managing and optimising AWS infrastructure with cost management, scaling and security best practices; creating and maintaining Helm charts for production ready deployments; implementing and managing Karpenter; configuring and managing Istio for traffic management, service discovery and policy enforcement; automating deployment, scaling and infrastructure management and working with CI/CD pipelines; responding to incidents and troubleshooting performance, availability and security issues; designing secure cloud infrastructure with access controls and compliance frameworks; and documenting platform setup and operational procedures. LOCATION AND WORKING PATTERN Bengaluru, hybrid. HONEST FIT GUIDANCE If you scan job descriptions for the first years figure you will read this as a 5 year role and be surprised in the screening call. It is an 8 year role with a 5 year Kubernetes specialisation inside it. That said, the reverse is also useful: if you have eight years of Terraform and serverless work and only five of Kubernetes, you meet this posting exactly as written.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 8 to 10 years of backend software engineering experience, plus a bachelor's or master's degree in computer science, engineering or a related field. WHAT THE POSTING REQUIRES - Strong expertise in Java, Spring Boot and object oriented design. - Hands on experience with microservices, distributed systems and cloud native architectures. - A strong understanding of system design, scalability, performance optimisation and fault tolerance. - Experience with AWS, Kafka, MongoDB, MySQL and the ELK stack. - Good knowledge of both relational and NoSQL databases. - Strong debugging, troubleshooting and performance tuning skills. - Experience building enterprise scale applications. - A proven ability to lead technical initiatives and mentor engineers. - Excellent communication, collaboration and ownership. NICE TO HAVE, NOT REQUIRED - Experience with large scale, high throughput cloud platforms. - Exposure to observability, monitoring and logging frameworks. - Experience with containerisation. - The ability to balance technical excellence with business impact. - Proven success in fast paced startup environments. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing and building scalable backend systems and distributed microservices; owning services end to end including design, development, testing, deployment and monitoring; developing solutions for complex business workflows and enterprise applications; collaborating with Product, QA, UI and UX and other engineering teams; driving system performance, scalability, reliability and operational excellence; leading architecture discussions; troubleshooting production issues and driving root cause resolution; and mentoring engineers. LOCATION AND WORKING PATTERN Bangalore HQ. HONEST FIT GUIDANCE This is a conventional senior backend brief, which on a day full of specialised postings is a feature rather than a criticism. If you have eight years of Java and Spring Boot at scale, you can read this requirement list and know immediately whether you qualify. One practical note: Tekion moved its job board from Greenhouse to Ashby, so older Tekion links you may have bookmarked will not resolve. Use the current posting.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 8 to 10 or more years of industry experience with a proven track record leading complex technical projects and cross team initiatives, plus a B.S. or M.S. in computer science or a related technical discipline. WHAT THE POSTING REQUIRES - Coding proficiency in Java, Scala or Golang sufficient to author production ready code, plus scripting in Groovy, Python or Bash, and experience running and tuning JVM workloads at scale. - Deep experience with quality engineering platforms focused on automating functional requirements and testing at scale. - Demonstrated experience applying AI reasoning, machine learning and predictive analytics to improve release processes, testing efficiency and risk identification across SDLC pipelines. - Expert knowledge of software delivery technologies such as Jenkins including writing complex pipelines, and build tools such as Make, Gradle or NPM. - Strong experience with AWS, Azure or GCP and infrastructure as code tools such as Terraform or Crossplane. - An advanced understanding of DevSecOps including automated security testing and policy as code. - Familiarity with agile frameworks such as Scrum and Kanban. WHAT THE JOB ACTUALLY IS DAY TO DAY Driving technical direction and design for a modern quality engineering platform; leading CI/CD modernisation to include automated security validation and compliance checks; owning the delivery pipeline and release automation framework for all Sumo Logic services, measured on developer productivity, deployment frequency and release reliability; collaborating with teams during design and development to embed verification practices; mentoring engineers; partnering with engineering leadership on architectural decisions and roadmap; writing detailed design documents; and participating in an on call rotation. LOCATION AND WORKING PATTERN Noida. HONEST FIT GUIDANCE The job board lists this as Staff Software Engineer but the posting itself is headed Staff Engineer, Release and Verification, and the second title is the accurate one. If you apply expecting product engineering you will be surprised. The AI and ML requirement here is not a nice to have; it asks for demonstrated experience applying predictive analytics to release risk, which is a genuinely uncommon background and probably the deciding factor in this hire.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 10 or more years of software engineering experience including SaaS platforms, distributed systems, enterprise applications, data intensive systems or similarly complex environments, plus a bachelor's degree in computer science, software engineering or equivalent practical experience. WHAT THE POSTING REQUIRES - Proven experience leading complex technical initiatives across multiple engineers or teams. - Strong experience with architecture, system design, code reviews, design reviews, application security, scalability and reliability. - Hands on experience with modern development practices including agile, DevOps, CI/CD, automated testing and production operations. NICE TO HAVE, NOT REQUIRED - Experience with enterprise software, SaaS platforms, IT management tools, automation platforms or cybersecurity software. - Experience with Java, C#, .NET, MySQL, SQL, AWS and enterprise scale SaaS platforms. - Familiarity with architecture patterns including cloud native platforms, N tier systems, MVC, client server and distributed systems. - Experience improving engineering processes and platform reliability. - A strong ability to mentor engineers and influence technical decisions without direct management authority. WHAT THE JOB ACTUALLY IS DAY TO DAY Leading architecture and technical design for major features, services and platform capabilities; driving implementation of secure, scalable software across cloud, data centre and hybrid environments; providing technical leadership for SaaS platform, automation and large scale integration initiatives; partnering with product management, engineering managers, QA, UX, operations and support; guiding teams through design reviews, code reviews, technical planning and production readiness; helping define engineering standards for quality, security, performance, observability and CI/CD; mentoring staff, senior and mid level engineers; and communicating status, risks and trade offs to engineering leaders. LOCATION AND WORKING PATTERN Pune. HONEST FIT GUIDANCE The phrase worth noticing is influence technical decisions without direct management authority, which is written into the preferred qualifications. That is an explicit statement that this is a senior individual contributor track role rather than a manager role with an engineering title, and it is the clearest such statement in today's edition. Kaseya describes itself as high growth and high performance with an emphasis on urgency, so expect pace.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 10 or more years of experience with the clouds, tools and languages in the team's stack, specifically AWS, Azure or GCP, Terraform, Kubernetes, Python and Bash. WHAT THE POSTING REQUIRES - Solid experience with declarative infrastructure as code, ideally Terraform, though it says explicitly it will take a willingness to learn if you bring a CloudFormation or ARM and Bicep background. - A love of automating tasks. - Experience working asynchronously as part of a fully remote, distributed team with excellent written communication. - Prior experience across multiple clouds. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, operating and supporting infrastructure systems with parity across tenancy models and public clouds, and working with engineering teams to get their services consistently deployed into those environments; bringing cloud infrastructure expertise as the platform's multi cloud capabilities expand; creating a good developer experience alongside partners in architecture, release engineering, product engineering and security; building automation to remove manual toil at scale; identifying infrastructure optimisations that reduce cloud spend without sacrificing reliability; and participating in a balanced on call rotation. LOCATION AND WORKING PATTERN Bengaluru, listed under APAC. WORTH KNOWING BEFORE YOU APPLY The posting states that Fivetran and dbt Labs are bringing two companies together and that during this transition you may see references to both Fivetran and dbt Labs throughout the recruiting process and career sites. That is unusually transparent, and it is worth asking in the interview which entity you would be employed by and how the platform roadmap is being consolidated. HONEST FIT GUIDANCE The Terraform clause is generous for a role at this level, since it accepts adjacent infrastructure as code experience. The harder requirement is genuine multi cloud depth: parity work across AWS, Azure and GCP is a different discipline from being excellent at one of them, and this team has already built the cell based architecture, so you are joining to extend it.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 10 or more years of professional Android development experience delivering production mobile applications at scale. WHAT THE POSTING REQUIRES - Strong Kotlin proficiency and deep experience with modern Android frameworks including Jetpack Compose and/or Views, Lifecycle, ViewModel and Navigation. - A proven ability to design and evolve Android app architecture for maintainability and long term team productivity. - A solid understanding of concurrency and async patterns on Android including coroutines, Flow, threading and structured concurrency. - Experience integrating REST APIs, handling offline and poor network scenarios and building robust data layers with SQLite and caching. - Strong testing discipline across unit and UI testing plus familiarity with release practices and Play Store deployment. - The ability to lead technical projects end to end through ambiguity. - A degree in computer science or engineering or equivalent practical experience. Team lead experience is listed under bonus points, not requirements. WHAT THE JOB ACTUALLY IS DAY TO DAY Owning the design and delivery of high impact Android features and platform improvements from concept to production; driving Android architecture decisions and documenting trade offs; building clean, testable code with modern practices; partnering with product and design to scope work into iterative milestones; ensuring quality through testing, code reviews and release readiness including crash monitoring and performance profiling; collaborating with backend and API teams on contracts and edge cases; improving developer velocity through tooling, CI/CD and build times; and mentoring other engineers. LOCATION AND WORKING PATTERN Bengaluru. The role reports to an engineering manager, which the posting states directly, confirming this is an individual contributor position. Check the requisition before you apply. Ping Identity currently has two Bengaluru postings with the identical title Staff Software Engineer at the same 10+ level, and only the body distinguishes them: one is backend Java and Spring Boot, this one is Android. If you are applying to both or tracking one, confirm which requisition you are actually in.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for a bachelor's, master's or PhD in computer science, engineering or a related field with 10 or more years of experience. WHAT THE POSTING REQUIRES - Comfort navigating the full AI toolchain from Python modelling code through compiler intermediate representations to performance profiling. - Strong debugging skills across performance, numerical accuracy and runtime integration. - Experience with deep learning frameworks such as PyTorch and TensorFlow and familiarity with model internals including attention, Mixture of Experts and diffusion. - Proficiency in C and C++ with experience in low level optimisation. - A strong background in optimisation techniques, particularly those involving NP hard problems. WHAT THE JOB ACTUALLY IS DAY TO DAY Contributing to end to end bring up of frameworks for reinforcement learning, inference serving and ML models on Cerebras CSX systems; working across the stack from model architecture translation through graph lowering, compiler optimisation, runtime integration and performance tuning; debugging performance and correctness issues spanning model code, compiler IRs, runtime behaviour and hardware utilisation; and proposing and prototyping improvements to tools, APIs and automation flows to speed up future bring ups. LOCATION AND WORKING PATTERN Listed as India Office. HONEST FIT GUIDANCE The word Lead here is a level, not a management title, and no direct reports appear anywhere in the responsibilities. The role also demands an unusual combination: real ML framework knowledge and real systems and compiler ability. Most candidates have one. If you have both, there are very few places to use it and this is one of them. Note also that Cerebras has moved its job board from Greenhouse to Ashby, so older Cerebras application links no longer resolve.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 15 or more years of software development in Java, preferably with significant experience in Hibernate and Spring Boot, plus 4 or more years of experience automating and deploying large scale production services in AWS, GCP or similar. What the posting describes as the ideal candidate: a hands on expert developer in Java who is deeply technical with a passion for building high quality, secure and performant applications and frameworks; demonstrable experience leading technical projects involving more than 20 engineers across multiple workstreams; someone excited by security and identity management problems who can drive technical strategy and mentor other engineers; a collaborative individual with excellent communication who can work with cross functional teams; and a force multiplier who creates frameworks and solutions that make other teams more productive, not only a builder. Experience building software systems to manage and deploy reliable, performant infrastructure and product code at scale on cloud infrastructure is required. WHAT THE JOB ACTUALLY IS DAY TO DAY Working with the senior engineering team on major development projects, design and implementation; leading architectural design and implementation of new features and services focused on scalability, performance and security; collaborating with product managers, architects and other engineering teams to define technical strategy and lead prototyping; directly overseeing and coordinating complex technical initiatives involving 20 or more engineers and ensuring alignment across sub teams; driving engineering excellence in testing, monitoring and operations; and partnering with product development, QA and SRE on scoping. LOCATION AND WORKING PATTERN Bengaluru, hybrid. HONEST FIT GUIDANCE This is the most senior role in today's edition and the 15 year requirement is real. Note the distinction the posting draws: coordinating 20+ engineers across workstreams is technical initiative leadership, not line management, and no direct reports are mentioned. If you have been looking for a route that keeps you technical past fifteen years rather than pushing you into management, that is exactly what this describes. Identity protocol knowledge such as SCIM, OAuth, OpenID Connect and SAML will help, but the primary gate is Java depth at scale.
THE EXPERIENCE THIS ROLE ASKS FOR This posting states no years of experience figure anywhere. We have published it with the experience field empty rather than guess a number, which means it will not appear under any band in the experience filter on this page. The title is Staff Engineer and the responsibilities are architecture ownership and mentoring, so read the level from that. WHAT THE POSTING REQUIRES - Strong computer science fundamentals in data structures, algorithms and system design. - Deep hands on backend experience with Java and Spring Boot. - A strong grounding in distributed systems concepts covering consistency, durability, retries, idempotency, backpressure, partitioning and resilience. - Practical experience with Kafka, Kinesis, Pulsar or similar. - Experience operating production systems including on call, incidents and postmortems. - Excellent communication and technical leadership ability. NICE TO HAVE, NOT REQUIRED - Experience building high throughput ingestion or streaming systems. - Exposure to compliance heavy or audit driven domains such as transportation, fintech or healthcare. - Experience with edge or intermittently connected devices. - Hands on work with observability tooling. WHAT THE JOB ACTUALLY IS DAY TO DAY Owning architecture, design and evolution of platform services within Native ELD and/or Ingestion; driving system design for large cross service features from ingestion through to downstream consumers; defining clean service boundaries, APIs and data contracts; designing scalable ingestion pipelines and streaming and batch workflows; translating hours of service and ELD regulatory requirements into robust system behaviour; defining and upholding SLOs for latency, availability and data accuracy; designing for backpressure, graceful degradation and recovery; designing data models and partitioning strategies for hot and cold data; and mentoring engineers on system design and distributed systems. LOCATION AND WORKING PATTERN Bengaluru. HONEST FIT GUIDANCE The interesting part of this role is the regulatory constraint. Electronic logging device rules mean data correctness is a legal matter, not just an engineering preference, which changes how you design retries and reconciliation. If you have built ingestion at volume but never in an audited domain, say so and treat it as the thing to learn rather than hide. Because no years figure is published, ask early where the role sits on their ladder.
THE EXPERIENCE THIS ROLE ASKS FOR This posting states no years of experience figure. We have left the experience field empty rather than infer one, so it will not appear under any band in this page's experience filter. The level is SDE 3, and the posting describes it as a senior engineer role that mentors SDE1 and SDE2 engineers, which at most Indian product companies means roughly five years and up. Confirm with the recruiter rather than trusting that estimate. WHAT THE POSTING REQUIRES strong hands on frontend expertise, solid design skills, and the ability to translate product requirements into clear, scalable technical solutions. WHAT THE JOB ACTUALLY IS DAY TO DAY Owning the design and development of complex, scalable frontend features and modules for the cybersecurity platform; partnering with product managers, UX designers and backend engineers to turn requirements into technical plans; contributing to and maintaining large scale component libraries, design systems and UI frameworks for consistency and reuse across CloudSEK products; following and improving frontend engineering standards and quality benchmarks; building and integrating AI workflows into both the product and the development process, including LLM powered features, AI assisted tooling and agentic automation; contributing to performance optimisation covering rendering strategies, caching, bundling and code splitting, asset optimisation and runtime monitoring; making technical decisions on data fetching patterns, state management, server versus client rendering, routing and modularity; collaborating with backend teams on API contracts; mentoring SDE1 and SDE2 engineers through code reviews, pairing and design discussions; and helping maintain frontend observability. LOCATION AND WORKING PATTERN Bengaluru. CloudSEK is headquartered in Singapore with operations across India, Southeast Asia and the Americas. HONEST FIT GUIDANCE Two things stand out. The AI workflow responsibility is written as building product features and internal tooling, not as using an assistant, which is more substantial than the usual mention. And the company is at a scale where a senior frontend engineer genuinely sets standards rather than inheriting them, which is a real opportunity if you have wanted that and a burden if you have not done it before.
THE EXPERIENCE THIS ROLE ASKS FOR This posting states no years of experience figure, so we have left the experience field empty rather than guess. The title says Senior and the requirements are described by role type rather than duration, so the bar is set by demonstrated depth. WHAT THE POSTING REQUIRES - Technical breadth and depth in ClickHouse open source or Cloud, or in adjacent domains such as SQL databases, OLAP, cloud native SaaS, distributed systems, Kubernetes and Docker. - Previous technical experience in roles such as support engineer, technical account manager, database administrator, site reliability engineer, solutions engineer, software engineer or systems engineer. - Availability according to the scheduling required to deliver 24x7 support in a global distributed environment. - Strong written and verbal English and the ability to work fully remote with reliable connectivity. - A mindset of teamwork, empathy and problem solving. NICE TO HAVE, NOT REQUIRED - Direct experience with ClickHouse. - Experience with open source technologies as a user, community member or contributor. - Experience with Azure, GCP or AWS. - Experience with data pipelines such as Kafka, Kinesis, Spark or RabbitMQ. WHAT THE JOB ACTUALLY IS DAY TO DAY Supporting and guiding users, customers and prospects through cases, chat, Slack, community forums and meetings; developing solutions on ClickHouse Cloud and open source that get shared through documentation, knowledge base, blogs, meetups, webinars and training; working with global support services, engineering, go to market and product management to define functionality users need; mentoring and sharing knowledge with colleagues and customers; and delivering first line technical response and on call coverage within service level agreements. LOCATION AND WORKING PATTERN Remote within India, with 24x7 scheduling to plan around. HONEST FIT GUIDANCE This is a genuinely remote role at a company that operates that way by default, which matters if relocating is not realistic for you. Note that the door is wider than the title suggests: the posting names seven different prior role types that qualify, and ClickHouse experience itself is only a bonus. If you are a DBA or an SRE who is good with people and wants out of a commuting job, this is worth a serious look.
THE EXPERIENCE THIS ROLE ASKS FOR This posting names no years figure at all. It asks for backend development experience with the ability to deliver maintainable production code, and nothing more specific, so we have left the experience field empty rather than invent a number. Intermediate is GitLab's own level name and sits between Junior and Senior on its published engineering ladder, so this is the most accessible role GitLab has open in India right now. WHAT THE POSTING REQUIRES - Backend development experience with the ability to deliver maintainable production code. - Solid proficiency in Go, Python or Ruby on Rails with strong PostgreSQL fundamentals. - Familiarity with Golang, or a willingness to learn and work across both Ruby on Rails and Go. - Strong testing discipline including RSpec or an equivalent framework. - Clear, direct written communication and experience collaborating with distributed teammates asynchronously. - The ability to manage scoped work independently and communicate progress. - Interest in package ecosystems such as npm, Maven, PyPI or OCI containers, or adjacent experience that helps you ramp. - Interest in software supply chain security, dependency management or DevSecOps. WHAT THE JOB ACTUALLY IS DAY TO DAY Implementing well scoped backend features across the supply chain security product, including package policy integrations, ingestion pipeline improvements, signing and verification support and reliability work; building and maintaining integrations with GitLab's existing software composition analysis scanning so findings appear accurately in merge request security reports; writing comprehensive automated test coverage with RSpec and integration tests; working as a generalist across feature areas as priorities shift; taking an active part in code review; writing clear internal documentation; and coordinating with adjacent teams including Dependency Firewall and Malware Database. LOCATION AND WORKING PATTERN This is the part worth reading twice. GitLab is all remote and async first, and states that all of its roles are remote though some carry location based eligibility requirements. The posting also notes occasional off hours overlap across global time zones. Clear written communication is treated as a core skill here rather than a soft one. HONEST FIT GUIDANCE This is the closest thing on today's list to a genuinely remote backend engineering job at an accessible level, which is the single most requested combination we get. The willingness to learn Go clause means you do not need production Go to apply if you have Rails. GitLab also states in the posting that it welcomes candidates with varying levels of experience and that many successful candidates do not meet every requirement, which on a day with almost nothing open below two years is worth taking literally.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 2 to 4 years of data engineering experience. WHAT THE POSTING REQUIRES - Working knowledge of at least one OLAP database (StarRocks, ClickHouse, Druid or similar). - Some experience with a data lake format (Hudi, Iceberg or Delta Lake), with the posting saying outright that deep expertise is not required and willingness to learn is. - Familiarity with distributed query engines such as Trino or Presto and with Spark, OR strong SQL and Python fundamentals and eagerness to pick those up. - A basic understanding of data security and access control concepts. - Comfort in an AWS plus open source environment or the ability to ramp quickly. - Clear communication, including asking for help when scoping is unclear. NICE TO HAVE, NOT REQUIRED - Any exposure to AI or LLM adjacent data work, explicitly including coursework or side projects with RAG, vector stores or LLM pipelines. - Interest in how data products get consumed by customer facing features. - Experience at a SaaS or B2B product company. WHAT THE JOB ACTUALLY IS DAY TO DAY Building and maintaining pipelines under guidance from senior engineers, supporting in product data features, helping prepare datasets that feed AI features, implementing access controls such as Apache Ranger as defined by senior engineers, reducing ad hoc data requests from internal teams by contributing to self service pipelines, writing documentation, taking part in code and design reviews, and troubleshooting data quality and pipeline issues while escalating architectural decisions upward. LOCATION AND WORKING PATTERN Hybrid in Bangalore. HONEST FIT GUIDANCE The posting is unusually direct about who it wants. It says you will thrive here if you like clearly scoped problems but want more ambiguity over time, if you care about doing reliable engineering work more than setting direction, and if you want to work closely with a senior mentor and level up quickly. If you are two years in and want a modern, production grade data stack to learn on, this is the opening on this list that is actually built for you. If you want to own architecture from day one, this is not that role and the posting says so.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 2 or more years of support and networking experience, which makes it one of the lowest bars in this edition. WHAT THE POSTING REQUIRES - 2+ years of support and networking experience including general firewalls and packet filtering troubleshooting. - A strong understanding of common network and application protocols and behaviours, enough to troubleshoot unexpected behaviour. - And, stated as a requirement rather than a bonus, demonstrated curiosity and active exploration of AI tools with a history of integrating new technologies into daily workflows. WHAT THE JOB ACTUALLY IS DAY TO DAY Second line phone and email consultation, independently debugging complex security and network problems, interfacing with Engineering to help customers test and troubleshoot, reproducing customer issues to verify them and reporting back to Engineering and Operations, documenting incident resolutions that are not in the knowledge base, and giving input on product and code changes through the product cycle. LOCATION AND WORKING PATTERN Hybrid, based in Bangalore or Mohali. Reports to the Manager, Global Focal Support within the Support department. HONEST FIT GUIDANCE Read the title carefully. It says Engineer II and asks only 2 years, but the posting describes the function as the highest level of technical support within the TAC, handling the most complex and critical escalated issues. That combination is unusual and it means the role will stretch you fast. It is a strong entry point into network security if your background is networking support rather than software development. It is not a coding role: expect protocol level debugging, customer calls and written case work.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for at least 2 to 4 years in technical support, customer success or technical account management within telecommunications or SaaS. WHAT THE POSTING REQUIRES - A bachelor's degree in computer science or equivalent. - Experience supporting or implementing APIs or SDKs. - Experience with IP based real time multimedia communication technologies and protocols including VoIP, SIP, RTP, WebRTC and WebSockets. - The ability to troubleshoot client and server side code. - And, listed as a requirement, proven experience using generative and agentic AI tools and LLMs to speed up complex technical troubleshooting, log analysis and script debugging. NICE TO HAVE, NOT REQUIRED - Other programming languages such as PHP, Python, Ruby or Node. - JavaScript, iOS or Android development experience. - A conceptual understanding of good software design. - Proficiency with Zendesk advanced AI features and virtual agents for ticket routing and automated responses. - Experience using Glean for technical troubleshooting. WHAT THE JOB ACTUALLY IS DAY TO DAY Investigating, troubleshooting, diagnosing and resolving technical issues in customer API and SDK implementations, communicating with customers and internal stakeholders in writing and on calls, contributing to knowledge bases, and collaborating with your team to identify bugs and escalate to next level support. LOCATION AND WORKING PATTERN Bangalore, with a fixed shift of 14:30 to 22:30 IST stated in the posting itself. That is not a rotation, it is the working day for this role, so treat it as a fixed condition rather than something to negotiate later. HONEST FIT GUIDANCE This is one of the genuinely accessible openings in this edition, and the protocol depth it asks for is learnable if you have supported any real time or telephony product. The AI tooling requirement is written as a proven track record, not curiosity, so have concrete examples of using LLMs on log analysis or debugging ready.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 2 or more years of experience in technical product and SaaS disciplines in a customer facing role. This is one of only two roles under three years in the whole edition, and it is the exact title a reader asked for by name. WHAT THE POSTING REQUIRES - Establishing and maintaining relationships with Super Enterprise Merchants and serving as the go to person for all technical and product discussions after go live. - Proactively engaging with customers to understand queries, conducting hands on troubleshooting and ensuring timely resolution. - Demonstrating a comprehensive understanding of the Razorpay product stack. - Reporting and escalating issues or bugs to product and software engineering using tools such as Jira and collaborating towards resolution. - Advocating for merchant behaviour that aligns with business outcomes. LOCATION AND WORKING PATTERN Bengaluru. WORTH KNOWING BEFORE YOU APPLY Razorpay states plainly in its own posting that it hires for attitude and hunger more than degrees, under the heading People over Pedigree. On a list where another employer this week explicitly prefers a premier engineering institution, that is a difference worth noticing if your degree is not from a name brand college. HONEST FIT GUIDANCE This is an account facing role, not a people management one, and it is not a software engineering role either. You will spend your time on merchant calls, reproductions, escalations and follow ups. If you want to stay close to a payments stack without writing production code, it is a genuinely good entry point at two years. If you want to be shipping features, look at the backend roles on this list instead.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 2 or more years of relevant experience, with 1 or more years in a technical service oriented role listed as preferred rather than required. Alongside the Zscaler and HackerRank openings, this is one of the three lowest bars in this edition. WHAT THE POSTING REQUIRES a bachelor's degree in a related field or equivalent business experience, 2+ years of relevant experience, and SQL scripting ability as the core technical skill named in the title. Preferred: 1+ years in a technical service oriented role. LOCATION AND WORKING PATTERN Pune, hybrid. ConnectWise states hybrid working across its Pune roles, and its other Pune postings this week specify three days in the office, so plan for a similar pattern here and confirm it during the process. HONEST FIT GUIDANCE Be clear eyed that this is technical services, not development. The ladder from here runs through ConnectWise's other engineering roles rather than starting in one. What makes it worth listing is the entry point: on a day where almost nothing on the board is open below three years, this asks two, names a concrete skill you can prove in an interview, and sits inside a company that is currently hiring six other technical roles in India, which means internal movement is a realistic path rather than a promise.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 3 or more years of frontend experience, with expert level React. WHAT THE POSTING REQUIRES - React and Next.js, specifically expert React including Server Components and Actions plus production Next.js App Router experience. - Deep TypeScript with advanced types, generics, conditional types and strict mode. - Modern CSS with Tailwind, ideally v4, plus responsive design and animation. - State management using Jotai atoms, TanStack Query for server state and caching, and React Hook Form with Zod. - Hands on monorepo experience with Turborepo, pnpm workspaces or similar. - Experience building design systems with shadcn/ui, Radix UI or another headless library. - A proven record optimising bundle size, render performance and Core Web Vitals. - API integration across REST, WebSockets and Server Sent Events for real time data. NICE TO HAVE, NOT REQUIRED - Experience building AI or ML product interfaces such as chat and streaming responses. - Motion and animation work with Framer Motion. - Browser automation and E2E testing with Playwright or Cypress. - Advanced TypeScript patterns including mapped, template literal and branded types. - CI/CD and containerisation with Docker and Kubernetes. - Monitoring with Sentry, DataDog or LogRocket. WHAT THE JOB ACTUALLY IS DAY TO DAY Architecting scalable frontend systems in the monorepo, designing and maintaining shared component libraries, building AI agent interfaces including conversational UI, optimising performance, implementing responsive and accessible designs across devices, and integrating with backend services that stream. LOCATION AND WORKING PATTERN Bengaluru. HONEST FIT GUIDANCE The required list is long and specific, and the named state management stack (Jotai, TanStack Query, Zod) is narrower than most React job descriptions. If you have three years of React but have never worked in a monorepo or shipped a design system, expect the gap to come up. The posting also asks for high autonomy and comfort with ambiguity, which is a fair warning that specifications will be thin.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 3 or more years in DevOps, SRE or platform and infrastructure engineering, with hands on ownership of systems you ran and improved rather than scripts that worked once. WHAT THE POSTING REQUIRES - Kubernetes fluency, meaning you can operate clusters day to day, understand the scheduler and API machinery well enough to debug failures, and have written or maintained operators, Helm charts or controllers. - Solid AWS across VPC, EC2, EKS, IAM, storage and networking with working knowledge of Azure equivalents, plus provisioning through Terraform or similar. - Networking depth covering CNI, ingress, service routing, network policies and VPN or tunnelling with IPsec, WireGuard or site to site. - CI/CD experience building and maintaining pipelines in GitLab CI, GitHub Actions, Argo CD, Flux or similar. - Comfort across container runtimes, Helm or Kustomize, Prometheus and Grafana, ELK or Loki. - Strong software engineering fundamentals with Python or Go preferred. - A product mindset toward internal users, measured by adoption and reduced toil. NICE TO HAVE, NOT REQUIRED - On premise infrastructure and deployments. - Operating in air gapped or restricted network environments including offline package management, image registries and disconnected cluster bring up. - Multi cluster or multi tenant Kubernetes in production with RBAC and isolation as self service. - Open source contributions to Kubernetes, CI/CD or infrastructure tooling. WHAT THE JOB ACTUALLY IS DAY TO DAY Kubernetes platform operations across upgrades, node lifecycle, RBAC and policy; owning build to production pipelines with canary, blue green and rollback patterns; provisioning cloud resources through infrastructure as code; managing CNI, ingress, network policies and secure cross cluster connectivity; building CLIs, scripts and operators to reduce toil; maintaining metrics, logging and tracing and taking part in incident response and postmortems. LOCATION AND WORKING PATTERN Bengaluru. HONEST FIT GUIDANCE The posting explicitly says this is not pure SRE on call and not pure platform product work. If you want a rota and a runbook, or if you want to build tooling and never operate it, this will not suit. The air gapped and on premise bonus items suggest some deployments run in restricted environments, which is worth asking about.
THE EXPERIENCE THIS ROLE ASKS FOR The posting says Sarvam is hiring across levels from 3 or more years of experience, and states directly that what matters more than years is whether you have built something real users depended on and kept it working. WHAT THE POSTING REQUIRES - You have shipped to production and owned it afterwards, including fixing it at 11pm and letting real usage change your assumptions. - You have worked with LLMs and agents seriously, covering context engineering, tool use, structured outputs, memory and the failure modes that only appear at scale, with both open and closed source models and agentic frameworks. - You bring engineering discipline to AI, thinking in versions, tests, regressions and reproducibility, and you are uncomfortable when behaviour depends on a prompt nobody can account for. - You take evals seriously and can define metrics, build the pipeline and tell signal from noise. - You have strong Python and range across backend services, data pipelines, APIs and cloud infrastructure. - You design for the long run so systems hold their behaviour over months. - You can sit with a customer's engineering team and reach a workable answer. WHAT THE JOB ACTUALLY IS DAY TO DAY Building production agents on the Sarvam stack across prompts, system design, workflows, tool integrations and evals; mapping the scenario space up front; building proofs of concept fast when a customer wants to see it work; integrating with core banking, CRM, ticketing and telephony; owning quality end to end by defining what good means and building the evals to prove it; tuning for accuracy, cost, reliability and performance under load; and taking a proven pattern into a new customer at pace. At senior levels you also own the technical build playbooks for a motion. LOCATION AND WORKING PATTERN Bengaluru. HONEST FIT GUIDANCE The senior level responsibilities mention bringing partner engineers up to a quality bar, which is mentoring rather than people management. This is a deployment facing engineering role, so expect customer contact and real deadlines. If your LLM experience is demos rather than something that stayed correct in production for months, the evals and regression parts of this interview will find that quickly.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 3 to 5 years. WHAT THE POSTING REQUIRES - Strong analytical and problem solving skills. - Hands on experience with SQL, Python, dashboards and modern AI tools. - Comfort working in a fast paced environment. - The ability to mentor team members and influence business decisions through data. WHAT THE JOB ACTUALLY IS DAY TO DAY Preparing, maintaining and improving MIS reports, dashboards and business performance trackers; analysing large datasets to identify business trends, growth opportunities, operational gaps and performance insights; automating reporting workflows; leading high impact analytical initiatives across business functions; and collaborating with multiple business stakeholders to support strategic initiatives. LOCATION AND WORKING PATTERN Bengaluru. WORTH KNOWING BEFORE YOU APPLY Razorpay's own posting states People over Pedigree, saying it hires for attitude, hustle and hunger more than degrees. It also describes a culture with no micromanagement and interns questioning CXOs, which is a claim rather than a guarantee but is at least a stated intent you can test in interview. HONEST FIT GUIDANCE The word Lead in the title is a seniority marker here, and the only leadership the posting names is mentoring team members and influencing decisions, not managing people. Read it as a senior individual contributor analytics role at 3 to 5 years. Be realistic that a significant share of the work is MIS and reporting rather than modelling or experimentation. If you want data science, look at the ML roles on this list. If you want to be the person who owns the numbers a fintech runs on, this fits.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 3 to 8 years supporting web based enterprise applications. WHAT THE POSTING REQUIRES - 3 to 8 years in supporting web based enterprise applications. - A technology centric background. - Previous advanced support experience with data driven, web based applications. - Strong logical, analytical and problem solving skills. - Excellent communication. - The ability to work night shifts. - Comfort in a fast paced, changing environment. WHAT THE JOB ACTUALLY IS DAY TO DAY Working with customers to solve issues in using Zenoti, owning reported issues through to resolution, consulting with customers so their business operations run effectively on the platform, following the team's defined processes, handling client reported issues through the ticketing system, and influencing product direction by feeding back the challenges customers hit. LOCATION AND WORKING PATTERN Hyderabad. This one needs reading carefully. The team works 24x7x365 and the posting says applicants need to be flexible because shift assignment is based on customer need. It also says that once you are assigned a shift, the company will work with you to keep your hours consistent over a long horizon. Night shifts are named as a requirement, not a possibility. HONEST FIT GUIDANCE The salary and the seniority band here are wide, 3 to 8 years, which usually means the level is set by the candidate rather than the requisition. Go in knowing which end you are at. The night shift is the real filter on this role: if that does not work for your life, no amount of technical fit will fix it, and it is better to know now than after three interview rounds.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 4 or more years of relevant experience, plus a bachelor's degree in a related field or equivalent business experience. WHAT THE POSTING REQUIRES - Advanced .NET development, covering design, build and deployment on the .NET framework. - ReactJS. - Strong object oriented programming with design patterns and clean architecture. - Relational database expertise with advanced Microsoft SQL Server including query optimisation and schema design. - Git version control with branching strategies, code reviews and collaborative workflows. - General software engineering strength in debugging production issues, building maintainable systems and writing tested, standards compliant code. The posting lists the stack explicitly as .NET, C#, ASP.NET, ReactJS, OOP, design patterns, clean architecture, SQL Server, query optimisation, database design, Git, code reviews, debugging, scalable systems and unit testing. NICE TO HAVE, NOT REQUIRED - Practical client side React backed by solid JavaScript and build tools such as Webpack and Babel, described as highly advantageous. - Proven use of Azure DevOps and cloud services for CI/CD. - Familiarity with AWS, called a distinct advantage. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, building and maintaining large scale production services, web applications, data pipelines and streaming systems; working on systems critical to current and future operations; debugging production issues across services and multiple levels of the stack; helping improve engineering standards, tooling and processes; and taking part in test review, analysis and software certification. LOCATION AND WORKING PATTERN Pune, hybrid. ConnectWise's other Pune postings this week specify three days in the office. HONEST FIT GUIDANCE At four years this is the most reachable pure engineering role ConnectWise has open in India right now, and the requirement list is conventional rather than exotic. The React element is described as practical exposure rather than expertise, so a backend heavy .NET engineer is a fair candidate here. If your SQL Server experience is writing queries rather than tuning them, close that gap before the interview, because it is named twice.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 4 or more years of professional software engineering experience including ownership of features or components from implementation through production operation, plus a bachelor's degree. WHAT THE POSTING REQUIRES - Proficiency in at least one modern programming language, with Go preferred and Python, Java or Rust accepted. - Experience building and operating non trivial production systems, including diagnosing issues and improving implementations based on real world behaviour. - The ability to translate loosely defined requirements into correct, maintainable systems. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, building and operating backend services supporting core platform capabilities such as control planes, user access management and backup workflows; owning features from implementation through production operation and improving them from operational signals and customer feedback; contributing to service design and API development with trade offs across correctness, scalability, cost and maintainability; spending most of your time writing and reviewing production code and diagnosing complex backend issues; participating in on call and operational responsibilities; and mentoring junior engineers. LOCATION AND WORKING PATTERN Bangalore. The role reports to an Engineering Director. WORTH KNOWING BEFORE YOU APPLY The posting explains why the domain is demanding. For many Clumio customers data protection is a compliance, audit and security mandate rather than a nice to have, so recovery performance, cost efficiency and reliable operation at scale are the differentiators the team is measured on. HONEST FIT GUIDANCE Four years plus Go, on a backend team inside a listed company, is an unusually clean brief for this list. The on call expectation is stated up front rather than buried, so treat it as real. Commvault also includes a recruitment fraud warning in its posting: it says it does not conduct interviews by email or text and will never ask for banking details or identity documents before your first day. Worth remembering generally, not just here.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 4 to 6 years building and deploying machine learning systems in production environments. WHAT THE POSTING REQUIRES - A strong foundation in machine learning, statistics, experimentation and applied data science. - Experience developing predictive models, recommendation systems, classification models, ranking models or related applications. - Hands on experience with NLP techniques, embeddings, transformer models and retrieval systems. - Python with common ML libraries such as scikit-learn, PyTorch, TensorFlow or XGBoost. - Experience with distributed data processing frameworks such as Spark or Databricks. - Familiarity with model deployment, monitoring and ML lifecycle management. - The ability to execute projects independently under moderate ambiguity. - Strong problem solving and communication. NICE TO HAVE, NOT REQUIRED experience with LLMs, prompt engineering, RAG systems or agentic AI workflows, and familiarity with LangGraph, LangChain, Amazon Bedrock, OpenAI, Anthropic or similar platforms. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, developing and deploying ML models and AI solutions for business and customer facing applications; building and optimising NLP and transformer based models for classification, ranking, recommendation, prediction and retrieval; contributing to GenAI and agentic initiatives including RAG pipelines, prompt engineering, tool usage and workflow orchestration; data exploration, feature engineering, training, evaluation and performance analysis; building scalable pipelines for training and inference; monitoring production model performance and contributing to retraining; and documenting and presenting to technical and non technical stakeholders. LOCATION AND WORKING PATTERN Bengaluru. HONEST FIT GUIDANCE This is a mid level ML engineering role that genuinely spans classical and generative work, which is less common than the job titles suggest. If your experience is entirely notebooks and offline metrics, the deployment and monitoring half is where interviews will press. 6sense elsewhere in its hiring publishes explicit expectations that engineers use AI coding tools daily, so expect that conversation.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 5 or more years in ML systems, with 2 or more years authoring production CUDA kernels, and states you should have a kernel in production that beat the prior baseline by a measurable margin. The posting labels the level as Senior. WHAT THE POSTING REQUIRES - CUDA at kernel authoring level, covering thread block sizing, shared memory layout, warp primitives, async copies including cp.async and TMA, and MMA selection. - CUTLASS and CuTe DSL at a modify and extend level with comfort in the layout algebra. - PTX at a debug and modify level, where you have inserted hand written PTX because the compiler missed. - Nsight Compute and Systems fluency, meaning you read a roofline plot and propose the fix. - Attention kernels, having authored or modified at least one from the FlashAttention family, paged, MLA, sliding window or sparse. - Multi architecture awareness of what changes from Hopper to Blackwell across TMA, WGMMA and tcgen05. NICE TO HAVE, NOT REQUIRED - Communication kernels including NCCL and NVSHMEM authoring, custom collectives, expert parallel dispatch and KV transfer, described as strongly desired with dedicated headcount expected later. - Open source kernel contributions to FlashAttention, CUTLASS, vLLM, SGLang, DeepEP, Mooncake or non trivial Triton work, which the posting calls the highest yield signal for this role. - Tcgen05, TMA, CTA cluster launch and distributed shared memory, async pipelining and the FP4 microscaling paths. - Grace side host path optimisation on GH200 or GB200. LOCATION AND WORKING PATTERN Bengaluru or Chennai, hybrid or on site. HONEST FIT GUIDANCE The posting describes this itself as a hard, narrow, high leverage role, and it is being hired as a vertical stack alongside a companion Inference role also on this list. It says that if your depth genuinely spans both you should apply to either and say so, but that most candidates are strongest in one and it hires for that depth. Since open source kernel work is called the highest yield signal, a public GitHub history will matter more here than a CV.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 5 or more years in ML systems, with 2 or more years on inference serving at production scale, and says your record should show concrete outcomes such as tokens per day, throughput wins or p99 reductions rather than deployed a model. Level is stated as Senior. WHAT THE POSTING REQUIRES - Experience serving 100B+ parameter models in production across multi node tensor, pipeline or expert parallelism. - Source level fluency in one of SGLang, vLLM, Dynamo or TensorRT-LLM where you have modified the scheduler, KV allocator or disaggregation path, plus reading level familiarity with the other three. - Distributed serving at operating and extending depth including a disaggregated prefill decode stack, distributed KV cache transfer such as Mooncake, and cross node routing and scheduling that you have run in production and modified. - Speculative decoding as a build and train competency, having trained your own draft models or speculators such as EAGLE or DFlash, distilled them from a target, and tuned acceptance rate against a real serving distribution. - Deep understanding of KV cache internals covering block tables, copy on write, prefix sharing and fragmentation. - Working command of tensor, pipeline and expert parallelism and NCCL primitives. - Multi tenant serving with model co-location and MIG or MPS isolation. - Profiling with Nsight Systems, framework tracing and py-spy or perf. - C++ and CUDA at read and modify level. - On call ownership of an inference SLO. NICE TO HAVE, NOT REQUIRED - Upstream contributions to SGLang, vLLM, Dynamo, llm-d, TensorRT-LLM or LMDeploy on non trivial code paths. - Direct production experience with Dynamo or llm-d at scale. - Having operated a forked runtime in production. - Published or shipped speculator work. - MoE serving, long context beyond 128K, multi model serving or Indic and multilingual workloads. LOCATION AND WORKING PATTERN Bengaluru or Chennai, hybrid or on site. On call ownership of an inference SLO is listed as a requirement, so the rota is part of the job. HONEST FIT GUIDANCE The bar here is specific in an unusually testable way. Having used vLLM is not what is being asked; having changed it is. Note also the speculative decoding requirement, which asks you to have trained speculators rather than enabled them, and is the single item most candidates will fail on.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 5 or more years of professional frontend development experience with a strong focus on complex web applications. That is worth pausing on: this is a Staff titled role at 5 years, while Okta's Staff Fullstack Engineer posting on the same board asks 8+. Same company, same level word, three years apart. Minimum requirements as published: 5+ years of professional frontend development; deep expertise in React including core principles, hooks, component lifecycle and state management; proficiency in TypeScript with a proven ability to use its features for maintainable codebases; a solid understanding of modern JavaScript (ES6+), HTML5 and CSS3; experience with frontend tooling such as Webpack, Babel, Vite and Yarn; and demonstrated experience consuming and integrating APIs. WHAT THE JOB ACTUALLY IS DAY TO DAY Leading the design and development of complex, high performance features in React and TypeScript; collaborating with product managers, UI and UX designers and backend engineers to turn requirements into frontend solutions; writing clean, modular, well tested and maintainable code; optimising for speed, scalability and responsiveness across devices and browsers; contributing to the evolution of the frontend architecture; reviewing code and giving constructive feedback; and proactively addressing technical debt and performance bottlenecks. LOCATION AND WORKING PATTERN Bengaluru. Okta's engineering postings in India are marked hybrid, and it describes an in person onboarding experience at the start. HONEST FIT GUIDANCE Okta says in the posting that it is not looking for someone who checks every box, which is boilerplate but is at least written down. The real reason to look at this one is the years figure. If you have five solid years of React and have been skipping roles labelled Staff on the assumption they need eight or ten, this is a counter example, and it is on the same careers page as the roles that do.
THE EXPERIENCE THIS ROLE ASKS FOR States the experience band directly as 5 Years to 8 Years. WHAT THE POSTING REQUIRES - Proven experience in Agile environments with iterative development alongside Product and QA. - Proficiency in Golang, with the posting adding that candidates with expert level Java or Python experience and a commitment to transitioning to Go will be considered. - Deep familiarity with microservices architecture and containerisation using Docker and Kubernetes. - Experience designing and maintaining distributed systems handling high traffic and large scale datasets. - Strong proficiency in both SQL and NoSQL databases. - A comprehensive understanding of the full software development lifecycle. NICE TO HAVE, NOT REQUIRED - Cybersecurity domain knowledge, with stated preference for candidates who have built or maintained security products, particularly SIEM and vulnerability management. - Familiarity with security protocols, encryption and common vulnerability frameworks. - Experience with Jira, Confluence and CI/CD pipelines. - Active participation in professional conferences or specialised tech groups. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, building and maintaining large scale production services, web applications, data pipelines and streaming systems; participating in sprint planning, stand ups, retrospectives and demos; debugging production issues across services and multiple levels of the stack; influencing others in the engineering team; helping improve engineering standards, tooling and processes; and evaluating code for validity and structure. LOCATION AND WORKING PATTERN Pune, hybrid, both stated in the posting. HONEST FIT GUIDANCE The Go clause is the useful detail here. Most Golang requisitions treat the language as a hard gate; this one names an explicit path in for strong Java and Python engineers who will commit to the switch. If you have been blocked out of Go roles for lack of production Go, this is the one on today's list to try. The security domain preference is a preference, not a requirement.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 5 or more years in Java, React and AWS with strong development proficiency and a solid foundation in object oriented programming. WHAT THE POSTING REQUIRES - 5+ years in Java, React and AWS. - A foundational understanding of generative AI and large language models and their application in enterprise software development. - The ability to write high quality, well tested code with comfort in object oriented programming. - Comfort with Agile methodologies such as Extreme Programming, Scrum or Kanban. - Awareness of TDD and continuous integration and delivery approaches and tools. NICE TO HAVE, NOT REQUIRED - Enjoying influencing others and advocating for technical excellence while staying open to change. - Presence in the external tech community through speaking, open source contributions or blogging. - Resilience in ambiguous situations. WHAT THE JOB ACTUALLY IS DAY TO DAY Adopting and advocating practices such as clean reusable code, TDD, pair programming and design patterns; using continuous delivery to ship value early; building large scale distributed systems out of microservices; collaborating on features, design concepts and interactive prototypes; applying thinking from the Technology Radar to client problems; using DevSecOps tooling and shifting security left; taking part in the full cycle of software consulting and delivery from ideation to deployment; and mentoring less experienced peers. LOCATION AND WORKING PATTERN Pune, and this is the part to read twice. The posting states you may be expected to work out of a Thoughtworks office or a client's office location for all five working days of the week, depending on business or client needs. On a list where most roles are hybrid, this is a five day expectation written into the job description. HONEST FIT GUIDANCE The external community presence item is genuine at Thoughtworks rather than decorative, so a blog, a talk or open source work is a real advantage. Consulting also means your client, city and domain can change between projects. If you want stability of codebase and team, weigh that against the breadth before applying.
THE EXPERIENCE THIS ROLE ASKS FOR Asks for 5 or more years of QA and test engineering experience testing complex product workflows, meaning multi step user journeys, cross surface interactions and end to end behaviour. WHAT THE POSTING REQUIRES - Deep expertise in functional, regression, exploratory, integration and end to end testing methodologies. - A strong developer mindset with comfort reading and writing code in Python, TypeScript or similar, navigating codebases and reasoning about systems. - A user first testing approach that tests from the perspective of real users rather than only against a specification. - Exceptional attention to detail and strong debugging instincts with clear, precise bug reports. - Familiarity with CI/CD and test automation frameworks. - Schedule flexibility. NICE TO HAVE, NOT REQUIRED - Experience testing AI powered products with non deterministic outputs and the ability to evaluate quality when responses vary. - Experience testing IDE plugins or extensions and developer tools such as VS Code extensions, CLIs and code review systems. - Familiarity with AI coding tools including Windsurf, Copilot, Cursor and Devin, with informed opinions on what good looks like. - A prior software engineering background with shipped production code. WHAT THE JOB ACTUALLY IS DAY TO DAY Owning end to end product quality across AI workflows; designing and executing functional, regression, integration, exploratory and E2E test plans; identifying edge cases, race conditions and state recovery failures; reproducing, documenting and debugging issues across layers; partnering with engineering and product to define done and set the quality bar for releases; and building QA playbooks, processes and automation where they give leverage. LOCATION AND WORKING PATTERN India, listed as APAC coverage. The posting states that overlap with US time zones is required and that release cycles may require weekend availability. Both are written into the qualifications rather than mentioned in passing. HONEST FIT GUIDANCE This is one of the more interesting QA roles you will see, because the core problem, defining correctness for a system that varies, is a real research flavoured question rather than script maintenance. The trade is the schedule. Cognition also describes its team as extremely talent dense and lists founding engineers from Scale AI, Palantir, Cursor, Waymo, Tesla and Google DeepMind, so expect a demanding bar.