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.
Added August 10, 2026
WHAT THE POSTING ASKS FOR - 2+ years of relevant experience, plus a bachelor's degree in a related field or equivalent business experience. - Strong Python or Ruby, and experience writing and maintaining automated tests in a Behaviour Driven Development framework such as Behave. - Solid Git: branching strategies, pull request workflows and Git submodules. - Hands on experience integrating, running and troubleshooting automated suites inside CI, specifically Jenkins or GitLab Runners. - Practical experience configuring or managing virtualised environments, particularly VMware ESXi. - Working knowledge of Linux, Windows and macOS, including basic administration and command line use. - IP networking fundamentals: TCP/IP, routing, subnets, and a grasp of basic firewall configuration. - Object oriented programming applied inside an automation framework, plus knowledge of QA methodology and the software development lifecycle. WHAT THE JOB ACTUALLY IS DAY TO DAY Creating and maintaining automated test cases, executing suites, diagnosing reported bugs and signing off on system quality before a customer release. You derive testing requirements as development proceeds, write test plans, cases, procedures and reports, plan test schedules against delivery dates, and review documentation for technical accuracy. A real part of the role is reproducing and isolating problems and verifying fixes, so debugging skill matters as much as authoring tests. LOCATION AND WORKING PATTERN Pune. ConnectWise states working conditions as on site or hybrid depending on location. The posting says you will work independently on projects with close supervision, which is consistent with the level. HONEST FIT GUIDANCE This is one of the two lowest experience bars in today's edition. It is a genuine coding job: if your testing background is manual only, the Python, BDD and CI requirements are the gap to close first. The ESXi and networking asks are unusual for a test role at this level and are worth reading as the real differentiator.
MINIMUM REQUIREMENTS, AS PUBLISHED - 2+ years of hands on Python programming. - Hands on experience developing, maintaining and troubleshooting test automation. - A good understanding of object oriented programming and the ability to work in an existing Python codebase. PREFERRED, AND THE POSTING SAYS YOU DO NOT NEED ALL OF THEM ConnectWise writes, in its own words, that you do not need to meet all the qualifications below and that it will consider your overall experience, technical knowledge and ability to learn. Those preferred items are: backend and API testing including REST, HTTP, JSON and database validation; Python testing tools such as pytest, unittest or Behave (it says BDD and Behave are valuable but not required); Git, pull requests, code reviews, Jenkins, GitLab CI/CD or GitLab Runners; Linux command line, logs, processes and services; networking including TCP/IP, DNS, ports, routing, subnets and firewalls; working with virtual machines; and troubleshooting test failures from API responses, logs, database records and network information. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, implementing and maintaining Python automated tests for backend services, REST APIs, system integrations and infrastructure applications. Alongside that: executing suites, diagnosing bugs, reproducing and isolating problems, verifying fixes, writing test plans and reports, planning test schedules against delivery dates, and feeding usability and functionality findings back to engineering. LOCATION AND WORKING PATTERN Pune. Working conditions are stated as on site or hybrid depending on location. HONEST FIT GUIDANCE Of everything published today, this posting has the lowest stated floor and the most explicitly forgiving language about the rest of the list. If you are early in a Python or QA automation career and have shipped real automation, this is the one to read closely.
THE YEARS CONTRADICTION, STATED PLAINLY This posting gives three different figures. The opening summary calls it "The Senior AI Engineer (4 + years of experience)". The skills list asks for "2-5 years of experience in AI/ML engineering". The education line asks for "2+ years of relevant experience". We have published it at 4 because that is the highest stated figure and we would rather not understate a bar, but if you have two or three years of real AI or ML engineering, two of the three statements in this posting include you. Apply and let them level you. WHAT THE POSTING ASKS FOR - Familiarity with AI and ML concepts and application development using generative AI. - Strong Python with a solid foundation in object oriented programming and software engineering principles. - Hands on experience with LangChain, LlamaIndex, Haystack or Hugging Face. - CI/CD tools and workflows: Git, Docker, Jenkins, Airflow. - Exposure to AWS, Azure or GCP and services such as S3, SageMaker or Vertex AI. - Understanding of vector databases (OpenSearch, Pinecone, Weaviate) and embedding techniques. - SQL and NoSQL databases and data manipulation. - A bachelor's or master's degree in computer science or a related field. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing and deploying AI applications using RAG and agentic frameworks, building and optimising machine learning models, maintaining scalable data pipelines behind AI workflows, and implementing REST APIs in FastAPI or Flask for model integration. You will work with embeddings and LLMs including GPT-4, Claude and Mistral for retrieval and reasoning, debug AI systems across the stack, validate components with pytest or unittest, and document designs and research findings. LOCATION AND WORKING PATTERN Bengaluru. The posting states work type as hybrid. HONEST FIT GUIDANCE This is a build role, not a research role. If you have shipped a RAG or agent system into production in Python and can reason about retrieval quality and latency, the title's "Senior" is less of a wall than it looks.
MUST HAVE SKILLS, AS PUBLISHED - Backend: Golang (stated as mandatory) or Java, plus REST APIs, microservices and event driven architecture. - Frontend: React.js (stated as mandatory) with Material UI. - Databases: PostgreSQL or another RDBMS, with caching in Redis or Memcached. - Cloud and DevOps: AWS, Docker, Kubernetes, CI/CD. - Messaging: Kafka or similar. - Strong system design, performance optimisation and debugging skills. EXPERIENCE AND EDUCATION - 5+ years of relevant experience. - Bachelor's degree in a related field or equivalent business experience. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, building and maintaining large scale production services, web applications, data pipelines and streaming systems. Debugging production issues across services and multiple levels of the stack. Contributing to engineering standards, tooling and processes. Participating in test review, analysis and certification of software. Evaluating code for structure, standards alignment and operating system compatibility. The posting notes you will work independently with general supervision and may influence others in the engineering team by explaining facts, policies and practices. LOCATION AND WORKING PATTERN Listed for Mumbai and Pune. Working conditions are stated as on site or hybrid depending on location. The posting also notes the environment is fast paced and multi tasking, and asks for the ability to work constructively under pressure. HONEST FIT GUIDANCE The two mandatory skills are Golang and React together. If you are strong in one and thin in the other, expect that to be the conversation. The Kafka and event driven requirement is real rather than decorative, given the platform's streaming systems.
REQUIRED QUALIFICATIONS - 6+ years of professional software development experience. - Strong Python for backend applications and services, with hands on REST API design. - Experience developing and deploying cloud native applications on AWS. - Working knowledge of React and Angular. - Strong understanding of software architecture, distributed systems and application design patterns. - SQL databases, data modelling and performance optimisation. - CI/CD pipelines, automated testing and Agile methodologies. - Demonstrated proficiency using AI powered development tools such as Cursor, Claude or GitHub Copilot, including applying them to code generation, debugging, testing, documentation, code review and solution design. - Strong engineering judgement to validate AI generated solutions for quality, security, scalability and maintainability. PREFERRED - Microservices and event driven architectures. - Experience modernising legacy applications and platforms. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing and maintaining backend services and APIs in Python; building cloud native applications on AWS with attention to reliability, performance and security; contributing React and Angular front end work; participating in architecture discussions and design reviews; optimising performance and observability; troubleshooting production issues and doing root cause analysis; and mentoring teammates through code review and technical guidance. LOCATION AND WORKING PATTERN Bengaluru. ConnectWise states on site or hybrid depending on location. HONEST FIT GUIDANCE Read the AI tooling requirement literally. This is one of eight employers in today's edition that put AI assistant fluency into the requirement list, and ConnectWise words it most strongly. Being able to describe how you use these tools, and where you overrule them, is likely to come up.
MUST HAVES, AS PUBLISHED - 3+ years of professional software engineering experience with a track record of shipping and operating production systems. - Strong fundamentals: data structures, algorithms, system design basics, testing, debugging and clean maintainable code. - Strong Python, and comfort picking up new languages and frameworks. - Solid data analysis instincts, comfortable with SQL and reasoning over large datasets. - A detection or adversarial mindset: reading real attack samples and asking how you would get past a defence. - Genuine fluency with AI native development. The posting states you should already use AI coding agents daily and want to build LLM powered detection, not merely consume AI tools. - Demonstrated ability to own projects that start ambiguous: scope them, make trade offs explicit, deliver on time. - Excellent written communication. The posting says decisions are made in writing. NICE TO HAVE Distributed systems, high throughput pipelines or large scale stores (PostgreSQL, DynamoDB, Redis, RocksDB, Kafka, Spark, OpenSearch or Elasticsearch), and a background in security, threat detection, anti abuse or fraud detection. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, building and operating detection end to end, from design through rollout, monitoring and maintenance. Writing and tuning detection logic using scored signals, adding new signals across the pipeline, and driving changes to launch with a strong focus on minimising false positives. Building and evaluating LLM based detection agents. Surfacing detections as reusable intelligence for other teams. You will join the on call rotation for your detection surfaces and debug customer escalations. LOCATION AND WORKING PATTERN Hybrid in Bangalore. The team is async first and distributed, and the posting repeatedly emphasises written communication. HIRING PROCESS NOTE, DISCLOSED BY THE EMPLOYER Abnormal states that it uses AI assisted tools to help recruiters prepare for interviews by analysing resume content and role requirements to suggest questions. It states explicitly that these tools do not make hiring decisions or screen candidates automatically, and that every decision is made by a person. HONEST FIT GUIDANCE Security domain experience is a nice to have, not a requirement, so a strong Python engineer with real curiosity about attacker behaviour is in scope. The AI native requirement is stated firmly enough that it is worth preparing concrete examples.
MUST HAVES, AS PUBLISHED - A BS in computer science, applied sciences, information systems or a related engineering field. - 3+ years of industry experience in backend development and distributed systems. - Experience building features and components from scratch and operating them in production, balancing feature work against operational reliability. - Experience working with distributed teams, and proficiency in asynchronous and written communication. - Experience improving service reliability, resiliency and observability in production. - Strong fundamentals in computer science, data structures and system design. NICE TO HAVE - The team's stack: Python, Go, AWS, Kubernetes, Django. - Search systems, remediation workflows or operational tooling used by SOC teams. - SIEM or SOAR integrations, or platform APIs. - Exposure to email security and authentication standards such as DMARC and DKIM. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing and building backend services behind search, remediation and quarantine across multi tenant enterprise email environments. Scoping and delivering features end to end with the tech lead, engineering manager and product manager. Owning reliability of what you build, including unit tests, integration testing and production observability. Contributing to API design for customer facing REST endpoints used by security operations teams. Participating in on call and providing technical support to resolve customer issues. Mentoring junior engineers through code review. LOCATION AND WORKING PATTERN Hybrid in Bangalore, with an async first culture and on call rotation. HIRING PROCESS NOTE, DISCLOSED BY THE EMPLOYER Abnormal states that AI assisted tools help recruiters prepare interview questions, that they do not screen candidates automatically, and that a person makes every decision. HONEST FIT GUIDANCE The degree requirement is stated as a must have here, which is worth knowing if you came through a non traditional route. Everything about the specific domain, email security and SOC tooling, sits in the nice to have list, so general backend depth is what is really being tested.
MUST HAVES, AS PUBLISHED - 4+ years of hands on backend engineering designing, building and operating production grade distributed systems. - Strong Python, the primary language for Airflow DAGs, platform services and automation tooling. - Working proficiency in Go, used for high performance infrastructure components and metric pipelines. - Experience building systems that process data at scale, whether metric ingestion, stream or batch processing, or high throughput APIs. - Demonstrated end to end ownership of a service or platform, from technical design through deployment, monitoring and iteration. - Comfort balancing feature development with operational responsibility. - Experience writing technical design documents that articulate trade offs and win buy in from peers and tech leads. - A track record of breaking ambiguous problems into concrete milestones. - Experience with fault tolerance patterns such as retries, circuit breakers and graceful degradation. WHAT THE JOB ACTUALLY IS DAY TO DAY Owning one to three key services within Observability or Data Infrastructure. Designing, developing and delivering platform features from technical design docs through production rollout across multiple environments (US, EU, GovCloud). Participating in on call: triaging, diagnosing and resolving production issues independently. Improving resilience by automating runbooks, refining SLAs and SLOs and identifying failure modes. Building platforms, tooling and APIs that make other engineering teams faster. Mentoring junior engineers on service operations. LOCATION AND WORKING PATTERN Hybrid in Bangalore, async first, with an on call rotation. HIRING PROCESS NOTE, DISCLOSED BY THE EMPLOYER Abnormal states AI assisted tools help recruiters prepare interviews, do not screen automatically, and that a person makes every decision. HONEST FIT GUIDANCE Both Python and Go are asked for, which narrows the field more than the four year figure suggests. If you have run Airflow or a Prometheus based stack in production and can talk about an incident you owned, that is the strongest thing you can bring.
MUST HAVE SKILLS, AS PUBLISHED - 4+ years of industry experience as a software engineer with strong engineering fundamentals. - Strong experience writing production code in Python and/or Go, and working with SQL and NoSQL databases. - System design experience building reliable, scalable applications with an emphasis on operational excellence. - Proven ability to own complex, multi component features end to end, with a growing ability to influence across teams. - Ability to make practical trade offs, balancing customer impact, system complexity and long term maintainability. - Ability to write technical design documents and contribute to design and architecture reviews. - Strong understanding of service health, monitoring, fault tolerance and incident response. - Strong communication and proven ability to work autonomously and asynchronously with remote collaborators. NICE TO HAVE - Experience designing data access layers, APIs or platforms that other engineering teams build on. - Experience treating an internal platform as a product. - Familiarity with ChatGPT, Cursor and similar AI development tools. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing and iterating on the APIs and services that make up the data access layer. Driving adoption of API gated data sources. Designing standard labelling for data ownership and building the validation logic behind it. Owning reliability of what you build, contributing to architectural decisions, writing design docs for your areas, and joining code reviews, design reviews and the team on call rotation. Collaborating with product managers, designers and the engineering teams adopting the shared layer. LOCATION AND WORKING PATTERN Hybrid in Bangalore, async first, with an on call rotation. HIRING PROCESS NOTE, DISCLOSED BY THE EMPLOYER Abnormal states AI assisted tools help recruiters prepare interviews, do not screen automatically, and that a person makes every decision. HONEST FIT GUIDANCE This is platform work where influence matters as much as code: the hard part is getting other teams to adopt your layer. If you have shipped an internal API that other teams actually used, lead with that story.
WHAT YOU BRING, AS PUBLISHED - 4+ years in technical support roles, ideally in cybersecurity, enterprise SaaS or API driven platforms. - Strong knowledge of email security fundamentals, SaaS platforms and cloud ecosystems such as Microsoft 365, Google Workspace, Slack, Okta, Splunk, CrowdStrike, Cortex SOAR, REST APIs or Zoom. - Proven ability to debug complex technical issues, analyse logs and collaborate with engineering and product. - Excellent written and verbal communication, including explaining technical concepts to non technical stakeholders. - Familiarity with Zendesk, Salesforce, Jira and Confluence. - Experience using AI tools such as GPT based assistants or AI powered support platforms for troubleshooting is called a strong plus. WHAT THE JOB ACTUALLY IS DAY TO DAY Acting as trusted L1 technical advisor for enterprise customers on Cloud Email Security, AI Security Agents and SaaS Security. Owning and resolving inbound tickets including configuration issues, API questions, behavioural false positives and threat investigations. Giving customers clear updates, root cause insights and recommendations. Working with engineering on timely resolutions and post mortem documentation. Supporting onboarding alongside Customer Success Managers. Creating and maintaining internal and external knowledge base content. Spotting patterns in support interactions to drive product improvements. LOCATION AND WORKING PATTERN Hybrid in Bangalore. HIRING PROCESS NOTE, DISCLOSED BY THE EMPLOYER Abnormal states AI assisted tools help recruiters prepare interviews, do not screen candidates automatically, and that a person makes every decision. HONEST FIT GUIDANCE This is explicitly an L1 seat, so it is a support role rather than a disguised engineering one. It carries no people management. If you want to move from generic SaaS support toward security, the ecosystem list is the syllabus worth working through.
WHAT YOU WILL BRING, AS PUBLISHED - 5+ years of professional software engineering experience, with at least 3+ years in marketing technology platforms, enterprise integrations or CRM driven systems. - Strong backend and application development in Python or Java, plus JavaScript or TypeScript. - Strong experience designing cloud native solutions on AWS including Lambda, S3, RDS, API Gateway and CloudWatch, with scalability, resilience and security in mind. - Proven experience integrating LLMs and generative AI into production applications, ideally with Amazon Bedrock, LangChain or similar. - Experience building AI backed backend services such as prompt orchestration layers, RAG workflows and retrieval pipelines. - Strong fundamentals: distributed systems design, API development, testing strategy, code quality and maintainable architecture. - CI/CD pipelines and automated deployment with tools such as GitHub and Gearset. - Ability to lead architecture discussions and influence technical strategy across systems and stakeholders. - Demonstrated experience mentoring engineers. - Strong working knowledge of Agile and Scrum delivery. NICE TO HAVE Deep hands on Salesforce architecture and development (Apex, Lightning, Flow, APIs, data models); advanced prompt engineering and evaluation strategies; vector databases, embeddings and RAG architectures; LangGraph, LangSmith or agentic workflow frameworks; Docker and Kubernetes; advanced AWS services such as SageMaker and event driven architectures. LOCATION AND WORKING PATTERN Bengaluru. Okta describes an in person onboarding experience and operates across more than 20 offices. HONEST FIT GUIDANCE The three years in martech, integrations or CRM systems is the narrowing requirement, not the five year headline. Generic backend experience without that context is the likeliest reason to be passed over, while the Salesforce depth people assume is required is explicitly only preferred.
MINIMUM REQUIREMENTS, AS PUBLISHED - 7+ years of progressive software development experience with a proven track record of designing and building macOS or iOS features using Swift. - Deep expertise with macOS or iOS software environments, including design, performance optimisation and security considerations. - Proven expertise in advanced debugging and performance optimisation using Xcode, LLDB and Instruments to resolve complex memory issues and concurrency bugs. - Experience in fast paced agile environments with a strong understanding of CI/CD and automated testing. - Excellent communication skills, with the ability to articulate complex technical concepts and influence technical direction. - Proficiency in leveraging AI coding assistants such as GitHub Copilot to accelerate the development lifecycle. Note this sits in the minimum requirements, not the nice to haves. - Strong conceptual understanding of macOS or iOS security features. NICE TO HAVE - Security domain expertise: cryptography, endpoint security concepts such as Secure Enclave, device management and MDM protocols, endpoint detection. - Identity and access management protocols: FIDO, OIDC, OAuth or similar modern authentication frameworks. - Cybersecurity principles, secure coding practices, and certifications such as CISSP or Security+. EDUCATION Bachelor's degree in computer science or equivalent experience. LOCATION AND WORKING PATTERN Bengaluru, tagged hybrid in the posting. Okta describes an immersive in person onboarding experience. HONEST FIT GUIDANCE This and Okta's Windows role are the same shape at the same level on different platforms, so pick by where your native depth actually is. The security nice to haves are how you separate yourself once the Swift bar is met, because the seven year requirement will be common to everyone in the pile.
MINIMUM REQUIREMENTS, AS PUBLISHED - 7+ years of progressive software development experience with a proven track record of designing and building Windows features using C++, C# and the .NET framework. - Deep expertise with Windows software environments including design, performance optimisation and security considerations. - Solid understanding of advanced debugging and performance optimisation on Windows, the Win32 API, inter process communication, Windows services and secure credential handling. - Experience in fast paced agile environments with a strong understanding of CI/CD and automated testing. - Excellent communication skills, with the ability to articulate complex technical concepts and influence technical direction. - Proficiency in leveraging AI coding assistants such as GitHub Copilot. As on the macOS role, this is a minimum requirement rather than a preference. - Strong conceptual understanding of Windows security features. NICE TO HAVE - Security domain expertise: cryptography, endpoint security concepts such as Trusted Platform Module, device management and MDM protocols, endpoint detection. - Identity and access management protocols: FIDO, OIDC, OAuth or similar. - Cybersecurity principles, secure coding practices, certifications such as CISSP or Security+. EDUCATION Bachelor's degree in computer science or equivalent experience. LOCATION AND WORKING PATTERN Bengaluru, tagged hybrid. Okta runs an in person onboarding programme. HONEST FIT GUIDANCE Win32, IPC and Windows services are systems level asks, so application level C# alone is unlikely to clear the bar. If you have shipped a Windows agent or service that had to survive hostile conditions on a managed fleet, that is the experience being looked for.
REQUIREMENTS, AS PUBLISHED - 8+ years of experience as a software engineer, with significant experience building SDKs, developer platforms or tooling. - Proficiency in at least one, ideally several, of Go, JavaScript or TypeScript, C# .NET, Python or Java. - Strong understanding of SDK design principles, API ergonomics and cross language consistency. - Experience designing or maintaining code generation systems such as OpenAPI Generator, and templating frameworks. - Experience designing authentication flows, retry strategies, rate limiting and resilient client side systems. WHAT THE JOB ACTUALLY IS DAY TO DAY Defining the technical direction for FGA SDKs, CLI, IDE integrations and developer automation. Leading architectural decisions for multi language SDKs and evolving the generator that sits underneath all of them. Establishing cross SDK standards for authentication, error mapping, retry logic and method level configuration. Ensuring advanced capabilities such as BatchCheck, ListRelations and non transactional writes are implemented consistently with appropriate parallelisation and performance safeguards. Owning release and versioning strategy. Improving CLI workflows, GitHub Actions, CI pipelines and developer documentation. Leading development fully in open source, reviewing community pull requests and guiding contributors to a mergeable state. Partnering with FGA Core on API design and mentoring engineers. LOCATION AND WORKING PATTERN Bengaluru. Okta describes an in person onboarding experience. HONEST FIT GUIDANCE This is a rare posting: public open source work is a core deliverable, so your GitHub history is directly relevant evidence rather than a nice extra. If you have maintained a client library that other developers depended on, that is the closest thing to a match. Note it is an individual contributor staff role with mentoring, not people management.
REQUIREMENTS, AS PUBLISHED - Experience: 8+ years architecting and running complex cloud networking and infrastructure. - GCP expertise: a minimum of 3+ years of deep hands on experience securing GCP, including GKE, GCE and Shared VPC. - Infrastructure as code: 10+ years using Terraform and Chef to manage complex cloud resources and OS hardening. Note this figure is higher than the headline experience requirement, which is worth raising with the recruiter rather than self selecting out. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing and developing security solutions that harden cloud infrastructure at scale. Prescribing defence in depth measures, applying industry security standards and enforcing least privilege. Acting as a liaison between the security and engineering organisations to build technical leverage and influence the security roadmap. Identifying gaps, proposing solutions and contributing to roadmaps while driving alignment across multiple teams. Providing technical mentorship to junior team members. TEAM CONTEXT, IN THE EMPLOYER'S WORDS The Infrastructure Security team is described as balancing security domain expertise with the ability to design, implement and roll out infrastructure across multiple cloud environments without adding friction to product functionality or performance. The posting describes a security centric, fast paced organisation. LOCATION AND WORKING PATTERN Bengaluru. Okta runs an in person onboarding programme and has offices in more than 20 locations. HONEST FIT GUIDANCE The internally inconsistent years figures matter here: 8+ overall but 10+ on Terraform and Chef. Read that as a wish list rather than three separate walls, and apply if your GCP security depth is genuine. This is an individual contributor staff role with mentoring responsibility, not a management seat.
QUALIFICATIONS, AS PUBLISHED - 3+ years of software engineering experience through full time work, internships, or equivalent practical experience. The wording is the employer's own and is unusually inclusive of non permanent experience. - Proficiency in one or more programming languages such as Java, Go, Python or similar. - Strong understanding of data structures, algorithms and object oriented design principles. - Experience with version control, debugging, testing and modern software development practices. - Familiarity with APIs, databases and distributed application fundamentals. - Ability to break down tasks, estimate work and deliver quality code with limited supervision. - Strong communication skills and the ability to collaborate effectively in a team. - Bachelor's degree in computer science, engineering, or equivalent practical experience. Note that here too the posting allows equivalent practical experience in place of the degree. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, developing, testing and maintaining software components and services. Delivering well scoped features, enhancements and bug fixes. Participating in code reviews and contributing to engineering best practices. Writing and maintaining unit and automated tests to support stable releases. Troubleshooting defects and production issues and implementing durable fixes. Collaborating with product managers, designers and engineers. LOCATION AND WORKING PATTERN Bengaluru. The posting does not state office days. HONEST FIT GUIDANCE On a day when nothing in this edition asks for under two years, this is the most realistic opening for somebody early in their career, precisely because of how the experience line is written. There is no specific framework gate and no institute requirement anywhere in the posting. If you are around three years in and solid on fundamentals, apply.
QUALIFICATIONS, AS PUBLISHED - Bachelor's degree in computer science, engineering or a related field, with 5+ years of industry experience building backend or platform systems, or equivalent practical experience. - Strong experience developing backend services and APIs using Go in production. - Hands on experience with distributed systems, including designing services for scale, reliability and performance. - Experience with streaming or messaging systems such as Kafka. - Familiarity with analytical or OLAP databases such as ClickHouse, or strong experience with similar stores and a willingness to ramp up quickly. - Ability to independently design and deliver complex features end to end. - Solid understanding of cloud native and microservices architecture in SaaS. - Comfort working across teams and raising the engineering bar through code and design reviews. STATED AS A PLUS RATHER THAN REQUIRED - Observability, monitoring or performance analysis systems. - Anomaly detection, data analytics or AI and ML concepts. The posting says explicitly that deep ML expertise is not required. - DevOps practices, CI/CD pipelines and operating production systems. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, prototyping and implementing backend microservices for a cloud SaaS platform in Go. Building and evolving data pipelines and streaming solutions on Kafka and ClickHouse. Applying distributed system design principles for scalability and resilience. Contributing to anomaly detection use cases. Owning features from design through testing and production deployment. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE ClickHouse specifically is negotiable, since the posting accepts similar analytical stores plus willingness to learn. Go in production is the harder requirement. This is one of three SolarWinds senior seats today at similar levels but different stacks, so read all three before choosing.
QUALIFICATIONS, AS PUBLISHED - 5+ years of software engineering experience building and supporting production software applications or services. - Strong proficiency in one or more of Java, C#, Go, Python or similar. - Solid understanding of data structures, algorithms, object oriented design and software design principles. - Experience designing, developing, testing and debugging medium complexity systems collaboratively. - Familiarity with APIs, databases, distributed systems concepts and modern development practices. - Ability to independently break down work, estimate tasks and deliver high quality code with minimal supervision. - Strong communication skills and the ability to partner with cross functional stakeholders. - Bachelor's degree in computer science, engineering, or equivalent practical experience. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, building, testing and maintaining components and services for platform capabilities. Owning medium complexity features and enhancements from technical design through delivery and support. Driving code quality through design, review, testing and engineering best practice. Troubleshooting product and production issues, identifying root causes and implementing durable fixes. Collaborating with product managers, architects and engineers. Contributing to technical discussions and implementation planning. LOCATION AND WORKING PATTERN Bengaluru. The posting does not state office days. HONEST FIT GUIDANCE The absence of a named stack is the point: this is the SolarWinds role to apply for when your experience is solid but does not match the Go, Kafka and ClickHouse seat or the .NET one. The degree line allows equivalent practical experience, and no institute preference appears anywhere in the posting.
QUALIFICATIONS, AS PUBLISHED - Bachelor's degree with 6+ years of industry experience, or a master's degree with 4+ years. The master's route is a real reduction in the bar and is stated by the employer. - Strong .NET and C# with design and architecture depth. - Ability to research and solve complex technical issues, including understanding the current product portfolio. - Ability to build pragmatic solutions on a mature platform and to upskill the engineering organisation by example. - Ability to transform complex requirements and customer needs into modern cloud native applications architected for high scale, reliability, security and performance. A CONTRADICTION WORTH KNOWING The job title says Senior Software Engineer. The body says "We are seeking a Staff Software Engineer for our Observability Self Hosted team." We have published the role at the stated six year figure, but the internal levelling is ambiguous and is worth clarifying early in the process, because it affects both scope and compensation. WHAT THE JOB ACTUALLY IS DAY TO DAY Working with product managers, cross functional engineering teams, architecture, UX and product owners on the Observability Self Hosted portfolio. Reinventing how organisations understand complexity in their environments while providing real time visibility to detect and remediate security issues. Research heavy problem solving on an established codebase rather than greenfield work. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE If you hold a master's degree and have four years of solid .NET experience, this posting explicitly includes you despite the senior framing. The work is platform modernisation on a mature product, so comfort reading and improving existing systems matters more than greenfield speed.
QUALIFICATIONS, AS PUBLISHED - Bachelor's degree with 15+ years of industry experience, or a master's degree with 13+ years. - Proven experience as a principal engineer, architect or senior technical leader for complex SaaS or enterprise software products. - Strong proficiency in Ruby on Rails and deep experience building and scaling backend services in production. - Strong experience architecting and delivering complex features across both backend and frontend layers. - Strong hands on AWS cloud architecture, designing reliable, scalable and secure distributed systems. - Experience with LLM frameworks or modern AI tooling. - Deep knowledge of relational databases, especially MySQL, including schema design, performance tuning and operational considerations. - Experience working across multiple teams and influencing architecture beyond a single codebase or service boundary. - Strong communication skills, able to explain technical direction to engineers, product managers and leadership. - Experience in ITSM, service desk, workflow, ticketing or operational SaaS products is listed as a plus. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE This is a principal individual contributor and technical leadership role rather than a people management one: the posting describes influencing architecture across teams, not managing them. The Ruby on Rails requirement is the real filter. If you have fifteen years but no Rails depth, this is not the seat, and if you have Rails depth at scale, the domain knowledge in ITSM is only a plus rather than a gate.
REQUIRED QUALIFICATIONS, AS PUBLISHED - Bachelor's degree in computer science, software engineering or equivalent practical experience. - 5+ years of software engineering experience building SaaS platforms, distributed systems, business applications or similar enterprise software products. - Strong hands on programming with Java, C#, .NET or similar technologies. - Experience with MySQL, SQL or related relational database technologies. - Experience with modern engineering practice including agile development, CI/CD, automated testing, code review and production support. PREFERRED QUALIFICATIONS - Enterprise SaaS platforms, IT software, business management applications, integration platforms or cybersecurity software. - AWS, cloud hosted platforms, data centre hosted applications or hybrid software environments. - Understanding of application security, scalable system design, APIs, distributed systems and operational reliability. - Experience with data collection, event driven systems, background services or integrations. - Ability to mentor less experienced engineers and contribute to team wide technical improvements. - Strong debugging, troubleshooting, communication and collaboration skills. LOCATION AND WORKING PATTERN Pune. The posting does not state office days. HONEST FIT GUIDANCE The requirement list is short and the preferred list is long, which usually means the team will consider a range of backgrounds. Java or .NET plus relational databases is the actual gate. Mentoring appears only in the preferred list and is framed as helping teammates rather than managing them, so this is an individual contributor role. Kaseya has four openings in this edition spanning five to twelve years, so check the others if the level is not right.
REQUIRED QUALIFICATIONS, AS PUBLISHED - 8+ years of software engineering experience with significant experience building distributed systems, platform services or security infrastructure. - Deep expertise in identity and access management: authentication, authorization and federation. WHAT THE JOB ACTUALLY IS DAY TO DAY Technical leadership: defining the long term architecture and technical roadmap for the IAM platform, leading identity, authentication, authorization and access governance initiatives across multiple products and engineering teams, establishing standards and reference architectures, and driving platform adoption and migration for existing products. Hands on engineering: designing, implementing and operating core IAM platform services; building integrations between identity providers, API gateways, authorization systems, secrets management platforms and SaaS products; developing services for user lifecycle management, machine identity, delegated administration, access reviews and compliance reporting; implementing secure token exchange, service to service authentication and federated identity workflows; building APIs and self service capabilities for onboarding, provisioning and access governance. Security and governance: designing authorization models supporting RBAC, ABAC, delegated administration and multi tenancy; defining controls for least privilege, separation of duties, credential management and privilege escalation prevention; ensuring full auditability of access grants, modifications, reviews and revocations; partnering with security and compliance teams on regulatory and customer requirements. Platform engineering: evaluating and leveraging open source IAM technologies, extending them where needed, and defining operational requirements for availability, disaster recovery, observability and security. LOCATION AND WORKING PATTERN Pune. Office days are not stated. HONEST FIT GUIDANCE Despite the "technical leadership" framing, the posting keeps a large hands on engineering section and names no direct reports, so read it as a senior individual contributor architecture role. Real IAM depth is non negotiable here; general backend experience without identity work is unlikely to clear it.
REQUIREMENTS, AS PUBLISHED - 10+ years of software engineering experience with strong backend development expertise. PREFERRED QUALIFICATIONS - Experience building AI or ML powered SaaS products, or customer facing AI features. - Experience with LLM powered workflows: recommendations, automation, categorisation or intelligent routing. - Experience with Kafka and event driven architectures, and distributed systems. - Knowledge of MLOps, model serving, telemetry, feedback loops and AI guardrails. - Experience with Terraform or infrastructure as code. - Familiarity with Prometheus, Grafana, OpenTelemetry or similar observability tooling. - Strong system design and architecture experience at large scale. REMOTE DETAIL, WHICH IS THE POINT OF THIS LISTING The location is published as India, remote, with no state or city restriction stated anywhere in the posting. That is worth calling out, because most remote India roles this month have carried a list of eligible states or cities. Two of the three remote roles in today's edition are unrestricted in this way, and this is one of them. Confirm the arrangement in writing during the process, since terms sometimes differ from the advertisement. LOCATION AND WORKING PATTERN Remote within India. HONEST FIT GUIDANCE The ten year requirement is the hard part and the AI and ML items are all preferred rather than required, so a strong backend engineer at that level without a formal ML background is still in scope. If relocation is what has been blocking you, this and the Ping Identity principal role are the two openings here worth prioritising. Kaseya has three other roles in this edition at five, eight and twelve years, all in Pune.
REQUIRED QUALIFICATIONS, AS PUBLISHED - Bachelor's degree in computer science, software engineering or equivalent practical experience. - 12+ years of software engineering experience, including significant experience with SaaS platforms, distributed systems, installable agents, enterprise platforms or large scale data collection. - Proven experience serving as a technical leader across multiple teams, products or major platform initiatives. - Deep expertise in software architecture, system design, application security, scalability, reliability, observability and operational excellence. - Hands on experience reviewing architecture, design and code for complex enterprise scale software systems. PREFERRED QUALIFICATIONS - Enterprise SaaS platforms, IT management platforms, cybersecurity software or large scale enterprise software. - Java, C#, .NET, MySQL, SQL and AWS. - Experience modernising legacy platforms, integrating acquired products, or aligning multiple products into a broader platform strategy. - Strong understanding of agent based software, SaaS platform security, distributed data collection and enterprise scale platform architecture. - Demonstrated ability to influence technical direction across engineering, product, operations, support and executive stakeholders. - Track record of mentoring senior technical talent and raising engineering standards. - Ability to balance long term architecture strategy against urgent business and customer delivery needs. LOCATION AND WORKING PATTERN Pune. Office days are not stated. HONEST FIT GUIDANCE The distinguishing experience here is integration work: if you have taken several acquired products and made them behave like one platform, that is exactly the story this posting is written around. Mentoring senior talent is listed, but no direct reports are named, so this reads as a principal individual contributor role.
REQUIREMENTS, AS PUBLISHED - 4 to 6 years of front end engineering experience in a product environment. - Deep expertise in HTML5, CSS3 and JavaScript. - Hands on experience with React. - Experience with component libraries or design systems. - Strong understanding of web accessibility (WCAG) and responsive design principles. - A clear communicator who works well in a collaborative, cross functional setting. WHAT THE JOB ACTUALLY IS DAY TO DAY Building and maintaining front end experiences across multiple products and tech stacks. Translating design intent into accessible, responsive and performant UI. Contributing to the design system and React component library. Working with designers, product managers and backend engineers. Identifying and resolving cross browser compatibility and performance issues. BENEFITS AND CULTURE, AS PUBLISHED Ping lists generous paid time off and holidays, parental leave, healthcare options, retirement programmes, education reimbursement and a commuter offset in specific locations. It describes a flexible, collaborative environment and employee resource groups. LOCATION AND WORKING PATTERN Bengaluru. The posting describes a flexible, collaborative work environment but does not state office days. HONEST FIT GUIDANCE The four to six year band means this genuinely is a mid level seat rather than a senior one in disguise, and the upper bound suggests they are not looking for a principal engineer. Design system and accessibility experience is what will separate candidates, since React alone is common. Ping has three other openings in this edition at six to nine and ten plus years, including a remote principal role.
REQUIREMENTS, AS PUBLISHED - 6 to 9 years of experience in software engineering, focusing on site reliability engineering or DevOps principles. WHAT THE JOB ACTUALLY IS DAY TO DAY Taking the technical lead on projects and mentoring team members. Automating everything. Building and maintaining production infrastructure hosted on AWS via code. Designing and building pipelines to deploy and manage global infrastructure. Analysing complex system behaviour, performance and application issues. Developing observability, alerts and runbooks. Capacity analysis and planning, traffic routing and security policies for Ping's single sign on SaaS applications. THE ON CALL COMMITMENT, STATED BY THE EMPLOYER The posting says directly that this position is part of an on call rotation of eight hours by seven days a week. That is disclosed here because an on call pattern covering weekends materially changes what the job is like, and it is the kind of detail that is often left out. BENEFITS AND CULTURE, AS PUBLISHED Generous paid time off and holidays, parental leave, healthcare options, retirement programmes, education reimbursement and a commuter offset in specific locations. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE The stated upper bound of nine years means very senior SRE candidates may be levelled elsewhere. "Take the technical lead on projects" and "mentor team members" are the only leadership items and no reports are mentioned, so this is an individual contributor role. If weekend on call does not work for your circumstances, that is a real reason to skip this one rather than something to discover later.
REQUIREMENTS, AS PUBLISHED - 10+ years of backend engineering experience with Java and Spring Boot, building and operating production systems. WHAT THE JOB ACTUALLY IS DAY TO DAY Building and operating the services that power Ping's core product experiences. Designing reliable APIs and event driven systems. Writing and reviewing production code. Improving performance and scalability over time. Working closely with product, data, infrastructure and SRE, and security teams to deliver well scoped solutions that are safe to run in production. Helping strengthen backend engineering practice through design reviews, mentoring and technical guidance. ⚠️ TWO IDENTICAL TITLES, TWO DIFFERENT JOBS Ping Identity is running two Bengaluru postings both titled Staff Software Engineer at the same ten year level. This one is backend Java and Spring Boot. The other is Android development delivering production mobile applications at scale, and that one also mentions team lead experience. Check which requisition you are applying to, because the titles are indistinguishable from the outside. BENEFITS AND CULTURE, AS PUBLISHED Generous paid time off and holidays, parental leave, healthcare options, retirement programmes, education reimbursement, commuter offset in specific locations, employee resource groups and regular team events. LOCATION AND WORKING PATTERN Bengaluru. Ping describes a flexible, collaborative environment; office days are not stated. HONEST FIT GUIDANCE The posting explicitly calls this a hands on role, so it is an individual contributor staff seat rather than a management track. Identity domain experience is not required anywhere in the requirement, which makes it more open than Ping's principal role.
QUALIFICATIONS, AS PUBLISHED - 10+ years of hands on software engineering experience, with 4+ years at principal or staff level building large scale security or identity products, as an individual contributor who writes and ships production code daily. The employer's own wording. - Security and identity expertise: deep working knowledge of IAM and PAM covering privileged access, secrets and key management, session brokering, least privilege and zero trust architectures, with hands on depth in OAuth2, OIDC and PKI. - Tech stack: expert level Go, or a strong systems language background with willingness to work in Go; cloud native technologies across AWS, Azure or GCP with Kubernetes; and distributed data stores such as Cassandra or similar NoSQL. Workflow engines such as Temporal are a plus. - AI systems, preferred: experience building or securing LLM based systems, agent frameworks, MCP, model based threat detection or AI guardrails. - Leadership: influence through code and design rather than title, with proven ability to drive cross team technical decisions while staying in the critical path of delivery. - Education: BS or MS in computer science or equivalent practical experience. REMOTE DETAIL Published as India, remote, with no state or city restriction stated in the posting. Alongside the Kaseya senior backend role, it is one of two unrestricted remote openings in today's edition. Confirm the arrangement in writing during the process. LOCATION AND WORKING PATTERN Remote within India. HONEST FIT GUIDANCE The line about staying in the critical path of delivery is the most useful sentence in the posting: this is not an architecture role that has left the codebase. Go is negotiable if your systems background is strong, but the IAM and PAM depth is not. For readers who need remote because relocation is not affordable, this is the most senior of the three remote roles here.
QUALIFICATIONS, AS PUBLISHED - 6+ years of industry experience. - 4+ years of experience providing technical leadership on large projects, including ETL frameworks and similar systems described in the posting. WHAT THE JOB ACTUALLY IS DAY TO DAY Helping build the Data Intelligence Platform that allows Databricks to automate decision making across the entire company, in collaboration with Databricks product teams, data science and applied AI. Developing tools spanning logging, orchestration, data transformation, metric store, governance platforms and data consumption layers, using the latest Databricks product and other tools in the data ecosystem. THE SCALE, IN THE EMPLOYER'S OWN TERMS Databricks describes operating a fleet consisting of millions of virtual machines, generating terabytes of logs and processing exabytes of data per day, and says that at that scale it observes cloud hardware, network and operating system faults that its software must gracefully shield customers from. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated in the posting. HONEST FIT GUIDANCE Read the second requirement carefully: four or more years providing technical leadership on large projects is a substantial ask on top of the six year headline, and it is about scope and influence rather than managing people. This is one of four Databricks openings in this edition ranging from six to ten years. If your background is data engineering and platform tooling rather than product features, this is the closest fit of the four.
WHAT WE LOOK FOR, AS PUBLISHED - 6+ years of production level experience in one of Python, Java, Scala, C++ or a similar language. - 3+ years of experience developing large scale distributed systems from scratch. - A networking background, stated as a specific requirement for this team. WHAT THE JOB ACTUALLY IS DAY TO DAY Building new backend connectivity services that power millions of virtual machines running on Databricks. Leading the design and development of new services powering connectivity between the control plane and the compute plane, a platform that lets Databricks increase compute plane scalability while using cloud resources efficiently. Working with product management, operations and other engineering teams to deliver robust, scalable networking systems. A DETAIL THAT CHANGES THE ROLE The posting states that Databricks is setting up this team from scratch in Bengaluru and that you would be one of the seed members of the Bangalore site. It describes the opening as an excellent opportunity for a hands on leader who thrives in a fast paced environment and enjoys novel multi cloud and distributed systems challenges. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE Networking depth is the differentiator, not general backend experience: understanding cloud connectivity, private networking and data exfiltration controls is what the team is being built around. Joining as a seed member carries the usual trade off, more influence over how things are done and less existing structure to lean on. The "hands on leader" wording refers to technical leadership; the posting names no direct reports.
QUALIFICATIONS, AS PUBLISHED - Bachelor's or master's degree in computer science, electrical engineering or a related field. - 7+ years of professional experience in software development. - Deep understanding of Java Virtual Machine internals including garbage collection, JIT compilation, class loading and the memory model. - Proficiency in at least one JVM language and extensive experience with its runtime environment. - Strong programming skills in Scala, Java, Rust or other systems level languages. - Extensive experience with operating system concepts including processes, threads, concurrency, scheduling and I/O. - Proven track record building and optimising high performance, scalable and reliable systems. - Experience with distributed systems concepts and technologies. - Excellent problem solving, analytical and debugging skills. - Experience with performance profiling and tuning tools. - Contributions to open source projects related to the JVM or systems software. - Experience with RPC frameworks. WHAT THE JOB ACTUALLY IS DAY TO DAY Optimising the core of the platform at a systems level. The posting closes by saying that if you are a systems level expert with a passion for optimising the core of technology and a deep understanding of JVM internals, they encourage you to apply. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE Seven years of general Java is not what this asks for. The question it is really posing is whether you have debugged a garbage collection pause or a JIT deoptimisation in production and understood why. If you have, this is an unusually good match; if not, one of the other three Databricks roles in this edition will fit better.
QUALIFICATIONS, AS PUBLISHED - 10+ years of industry experience. THE IMPACT YOU WILL HAVE, IN THE EMPLOYER'S WORDS - Build simple workflows covering multiple user journeys in the Databricks control plane. - Build self serve, modular UI flows to help product teams across Databricks build standard customer user journeys. - Collaborate with global cross functional teams including product management and backend engineers. - Participate in planning and executing complex projects involving multiple teams and stakeholders. - Create, deploy, test and upgrade complex data pipelines with features to visualise data graphs. - Provide a SQL centric data exploration and dashboarding experience. - Set the foundation for how robust, scalable and delightful products get built. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE The requirement list here is short, which cuts both ways: there is no long checklist to fail, but that also means the interview will do the filtering. The posting's emphasis on owning product and user experience beyond the implementation is the real signal, so an engineer who has only worked to handed down specifications may find the framing a poor match. This is one of four Databricks roles in today's edition, and the only one at ten years and the only front end leaning one.
ABOUT YOU, AS PUBLISHED - A bachelor's degree in information technology, computer science or software engineering, plus 5+ years of full stack or front end heavy software engineering experience. - Exceptional skills in Angular and React, paired with modern CSS frameworks. - Comfort working in a strictly typed backend environment (TypeScript). - Deep empathy for the user, and an understanding of how to build UIs that gracefully handle asynchronous operations and external network lag. - Well versed in modern testing frameworks including Cypress or Playwright and Jest, and CI/CD automated gating. - Working knowledge of application security and authentication, covering sessions, JWTs and OAuth. - Working knowledge of using AI first coding assistants. WHAT THE JOB ACTUALLY IS Building and maintaining the integration surface of Showpad's sales enablement platform, where the front end has to stay usable while depending on third party systems whose latency and failure modes you do not control. The authentication requirement covering sessions, JWTs and OAuth reflects that integrations are where credentials and tokens get handled. LOCATION AND WORKING PATTERN Pune. Office days are not stated in the posting. HONEST FIT GUIDANCE Both Angular and React are asked for, which is a less common combination than either alone and is likely the practical filter. The degree requirement is stated rather than offered as an equivalent experience alternative, so it is worth knowing if you came through a non traditional route. Showpad has three openings in this edition at five, six and ten years, and the six year one is the backend counterpart to this role.
ABOUT YOU, AS PUBLISHED - A bachelor's degree in information technology, computer science or software engineering, plus 6+ years of software engineering experience. - Deep expertise in TypeScript and Go. - Extensive experience with AWS, specifically serverless architectures, CDK, EventBridge, SQS and Secrets Manager. - Expert in designing decoupled, event driven architectures, with an understanding of the critical trade offs of distributed systems. - Highly proficient in application observability: Datadog, OpenTelemetry, structured logging and distributed tracing. - Working knowledge of using AI first coding assistants. WHAT THE JOB ACTUALLY IS Owning the backend of Showpad's integration platform, which connects its sales enablement product to the other systems customers run. The named AWS services point at a serverless, event driven design where SQS and EventBridge carry the work and Secrets Manager holds third party credentials. A NOTE ON THE TITLE VERSUS THE YEARS The title says Staff Engineer but the stated bar is six years, only one more than the company's Senior Engineer role in the same team. Titles are local convention rather than a universal level, and this is a clear example: do not rule yourself out of a staff title on years alone. LOCATION AND WORKING PATTERN Pune. Office days are not stated. HONEST FIT GUIDANCE TypeScript and Go together is the real gate, as is genuine AWS serverless depth rather than general AWS familiarity. If you have run an event driven integration platform and can talk about how you handled retries, idempotency and poison messages, that is the conversation this posting is inviting.
QUALIFICATIONS, AS PUBLISHED - 10+ years of experience in software engineering. - Strong .NET and .NET Core (C#), ASP.NET Core and Entity Framework. - TypeScript, described as a key skill, with Angular or React. - Microservices, distributed systems and event driven architecture. - AWS, preferred, with serverless native and cloud native services. INFRASTRUCTURE AND TOOLS NAMED IN THE POSTING AWS serverless services (Lambda, API Gateway, Step Functions, EventBridge); AWS container services (ECS, EKS, Fargate); AWS RDS or Aurora, DynamoDB and NoSQL databases; messaging via SQS, SNS, Kafka or RabbitMQ; and CI/CD through AWS CodePipeline or GitHub Actions. WHAT THE JOB ACTUALLY IS DAY TO DAY Leading system level architecture and design for complex distributed systems. Developing AI powered features that use large language models to enhance user workflows. Translating business requirements into scalable, secure and maintainable solutions. Defining and implementing microservices architecture, API first design and event driven systems. Producing and maintaining high level designs, low level designs, architecture diagrams and technical documentation. Ensuring systems meet non functional requirements including scalability. THE CROSS SITE DETAIL The posting states the role merges technical expertise with strategic leadership and facilitates communication between the Pune and Boston teams. Expect meetings that straddle the India and US East Coast working day. LOCATION AND WORKING PATTERN Pune. Office days are not stated. HONEST FIT GUIDANCE This is the only .NET principal seat in today's edition. The posting describes overseeing complex team initiatives and setting architectural direction rather than managing people, so read it as a senior individual contributor role with real influence and real documentation duties.
PRIMARY QUALIFICATIONS, AS PUBLISHED - 6 to 9 years of strong working experience with Android and iOS frameworks and mobile application development workflows. - Familiarity with mobile build systems including Fastlane, Xcode and Gradle, and with code signing workflows. - Proficiency in Python, with experience in Ruby, Bash or Go being a plus. WHAT THE JOB ACTUALLY IS DAY TO DAY Leading the redesign and evolution of the Mobile Branding framework, the system enabling customers to create custom branded versions of the Appian mobile application for both iOS and Android. Driving architectural modernisation of the end to end branding pipeline, from the customer facing Forum application and provisioning tools to the backend build service running on Mac EC2 runners in AWS. Using microservices, CI/CD automation and cloud native infrastructure to make the system more reliable, scalable and maintainable and to reduce manual intervention. TRAINING AND DEVELOPMENT, AS PUBLISHED Appian describes department specific onboarding training, dedicated mentorship and a First Friend programme for new hires, plus a range of growth and development opportunities. LOCATION AND WORKING PATTERN Chennai. Office days are not stated in the posting. HONEST FIT GUIDANCE This is not a standard mobile app development job. If you have only built app features and never touched code signing, provisioning profiles or CI for mobile artifacts, the interesting part of this role is exactly the part you have not done. Conversely, if you have owned a mobile build and release pipeline, this is a rare posting that treats that as the main skill rather than a chore. Appian has three openings in this edition, and this one publishes no institute preference, unlike its general senior engineering seat.
EDUCATION, AS PUBLISHED - Bachelor's or master's degree in computer science, information technology or a related field. - An educational background from a highly selective, premier engineering institution with a focus on computer science fundamentals is stated as preferred. Disclosed here because it is a preference candidates deserve to see up front. Appian's Engineering Enablement and Demo Engineer postings in this same edition state no such preference. BASIC QUALIFICATIONS - 6+ years of experience in software engineering, applying data structures, algorithms and design patterns in a full stack Java and web technology environment. - Proven track record building and scaling distributed systems, preferably cloud native. - Experience identifying bottlenecks and optimising performance of large codebases. - Experience with AI and ML adoptability and integrating intelligent features into standard workflows. - Experience leading technical initiatives or small project groups, and strong knowledge of enterprise application architecture. TECHNICAL SKILLS Deep understanding of software engineering, algorithms and data structures. Proficiency in at least one major language such as Java or Python. Hands on experience with Docker, Kubernetes and CI/CD pipelines. Grafana and Prometheus experience preferred. AWS, GCP or Azure plus modern databases preferred. Experience using AI tools and models such as Amazon Q, Kiro and Claude is preferred. LOCATION AND WORKING PATTERN Chennai. Office days are not stated. HONEST FIT GUIDANCE "Leading technical initiatives or small project groups" is the only leadership item and no reports are named, so this is an individual contributor role. If the institute preference rules you out on paper, Appian's other Chennai posting in this edition asks for no institute at all, which is a pattern worth knowing: the pedigree ask is not consistent across the same company's own roles.
WHO YOU ARE, AS PUBLISHED - Strong experience with Appian or a similar low code application development platform, including design, development and debugging of applications. - Excellent technical and programming skills are stated as a must, with concrete examples of times you have applied them to deliver polished work. - Attention to detail and a focus on delivering high quality output. - Excellent organisational skills and the ability to prioritise in a high volume, dynamic environment. The posting describes hundreds of demos per year flowing through your pipeline. - Comfortable on a cross functional team collaborating with global stakeholders across multiple time zones, with solid verbal, written, presentation and interpersonal communication skills. - Familiarity with interactive demo platforms such as Storylane, Reprise, Navattic or Walnut is a strong plus. - Familiarity with video recording and editing tools for walkthrough content is a plus. - A BS or MS in engineering, computer science, economics, maths, physics, or equivalent work experience. NO YEARS FIGURE IS PUBLISHED This posting states no years of experience requirement anywhere. We have written the experience field as not stated rather than inventing a number, which means this role will not appear under any experience filter on our board. If you are early in your career, roles with no stated bar are worth a look precisely because no floor has been set. REPORTING CONTEXT The posting says you will be coached and guided by the Lead Demo Engineer based in Chennai, reporting into the SPEAR team leadership in the US, which it frames as strong local support with visibility into the wider organisation. LOCATION AND WORKING PATTERN Chennai, with global stakeholders across time zones. HONEST FIT GUIDANCE This is presales work, so it sits closer to the commercial side than a product engineering seat, and no quota or sales target appears anywhere in the posting. If you have built on a low code platform and enjoy showing work rather than only shipping it, it is a real technical role.
WHAT THE POSTING ASKS FOR - 3 to 5 years of experience building modern web applications, SaaS products, analytics platforms, developer tools or workflow products. - Production web application development using React, TypeScript, JavaScript, HTML and CSS. - The ability to independently deliver front end features and contribute to technical design, testing and production quality. WHAT THE JOB ACTUALLY IS DAY TO DAY Building front end experiences for AI assisted incident investigation, root cause analysis, alert correlation, recommendations and remediation. Working with product, design, AI platform, backend, AIOps and SRE teams to make complex observability data and AI generated insights easy to understand and act on. Implementing interactive interfaces on top of that data. ⚠️ AN APPLY LINK WARNING, VERIFIED TODAY LogicMonitor publishes its jobs through Greenhouse, and the apply URL its own job feed hands out returns a 404 page. The working link uses a slightly different path on the same site. We found it, opened it and confirmed it loads this exact role before publishing, so the link on this page works. This is the second consecutive day we have found and corrected the same fault on this employer's feed. If you reach LogicMonitor roles from anywhere else and hit a not found page, that is why, and the job is very likely still open. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated in the posting. HONEST FIT GUIDANCE This is a front end role that needs comfort with dense data display: charts, correlations and machine generated explanations rather than forms. If you have built an analytics or monitoring interface, that experience counts for more than the AI framing suggests, because the AI work sits behind the API you consume.
WHAT THE POSTING ASKS FOR - 5 to 6 years of software development experience in commercial or enterprise application development. - Backend implementation, design and architecture skill, with responsibility for quality control across business integrations and general development. - The ability to troubleshoot bugs and implement new features in existing backend applications, and to build new components as required. - Designing scalable cloud native architectures. WHAT THE JOB ACTUALLY IS DAY TO DAY Working on the customer facing product application and on internal tools used by development technical operations. The posting says a successful backend developer produces required functionality in a timely manner and communicates with colleagues to solve problems and improve the systems they work with, which is a plain description of a delivery focused senior engineering seat. ⚠️ AN APPLY LINK WARNING, VERIFIED TODAY LogicMonitor's Greenhouse feed publishes apply URLs that return a 404. The working link is on a slightly different path on the same site. We found it, opened it and confirmed it loads this exact role before publishing, so the link here works. This is the second consecutive day the same fault has appeared on this employer's feed. If you find a LogicMonitor role elsewhere and hit a not found page, the job is probably still open. LOCATION AND WORKING PATTERN Pune. Office days are not stated. HONEST FIT GUIDANCE The five to six year band means candidates well beyond that may be levelled differently, and it is one of the narrower windows in this edition. LogicMonitor has two openings here, this one in Pune and a front end AI role in Bengaluru at three to five years, so check both against your city as well as your experience.
REQUIREMENTS, AS PUBLISHED - At least 3 years of experience working as a backend developer. - Working knowledge of distributed systems. - Experience with one or more of Java, Go, C, C++ or similar. - A bachelor's degree in computer science, engineering or a related field, or equivalent experience. BONUS POINTS - Past experience working on the internals of a database. WHAT THE JOB ACTUALLY IS DAY TO DAY Building scalable and performant ingestion plugins to get data into Lumi. Building new functions and expressions to query that data. Working on making the query engine highly performant. Supporting the team through code and design reviews. Being on call for escalations relating to the ecosystem team. REMOTE AND BENEFITS DETAIL The role is listed as remote with the location given as Bengaluru, and the posting carries an LI-Remote tag. Imply lists an employer matched provident fund contribution, private medical insurance, paid time off, a phone and internet allowance, and home office equipment reimbursement, the last two of which are meaningful signals that remote is genuinely supported rather than tolerated. AN ENCOURAGEMENT THE EMPLOYER PUTS IN WRITING The posting notes that studies show some groups are less likely to apply unless they meet every qualification, and says directly that if you are excited about the role but your experience does not align perfectly with every requirement, you should apply anyway. LOCATION AND WORKING PATTERN Remote, with Bengaluru given as the location. Confirm the exact arrangement in writing during the process. HONEST FIT GUIDANCE Three years for query engine work is an unusually low bar for that depth, and the codebase question is worth raising: Apache Druid is open source, so you can read the project before you apply and arrive with informed questions. On call is part of the role and is stated up front.
QUALIFICATIONS AND REQUIREMENTS, AS PUBLISHED - Java mastery: demonstrated command of core Java syntax, data types, control structures and object oriented principles including inheritance, polymorphism, encapsulation and abstraction. - API and networking: solid understanding of REST API architecture, HTTP communication and URL formatting, with hands on experience using Java HTTP clients. - Modern developer tooling: practical experience using Cursor, GitHub Copilot or similar IDE assistants in a daily software development workflow. - Prompt engineering and workflows: the ability to formulate precise technical prompts and break down instructions for multi step AI task execution. - Excellent verbal and written communication, with the ability to present complex technical information clearly to a variety of audiences. - Past experience with startups and fast paced environments is listed as an added advantage. THE YEARS PhonePe puts the range in the job title itself, 2 to 4 years, which removes the usual guesswork. It is the lowest experience band published in this edition. BENEFITS, PUBLISHED IN FULL BY THE EMPLOYER PhonePe lists these for full time employees: medical, critical illness, accidental and life insurance; a wellness programme with an employee assistance programme, onsite medical centre and emergency support system; parental support covering maternity, paternity, adoption assistance and day care; mobility benefits including relocation, transfer support and travel policy; retirement benefits covering employee provident fund contribution, flexible provident fund contribution, gratuity, NPS and leave encashment; plus higher education assistance, car lease and a salary advance policy. Very few employers publish this level of detail. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE The AI tooling requirement is not decoration: it sits in the qualifications list alongside Java itself. If you have not used an AI coding assistant seriously, that is the gap to close before applying. The Java and REST fundamentals asked for are otherwise standard for the level.
REQUIRED SKILLS AND EXPERIENCE, AS PUBLISHED - 6 to 9 years of software development experience with enterprise grade software. - Experience building scalable, high performance cloud services. - Expert coding skills in Scala or Java on the backend. - Deep knowledge of databases, and optimisation of queries and views. - Development on cloud platforms including AWS. - Expertise building scalable event based asynchronous systems on a microservices architecture. - Experience working with Docker and Kubernetes. - Expertise building REST APIs. - Cybersecurity experience and adversarial thinking. - Willingness to learn, challenge yourself and share ideas with the team, and the ability to multitask in a fast paced environment. EDUCATION A BSCS or equivalent is required, and an MSCS or equivalent is strongly preferred. WHAT THE JOB ACTUALLY IS DAY TO DAY The posting describes wearing many hats: leading the design of a new feature one week, then fixing a critical bug or improving CI infrastructure the next. That is an honest description of a senior seat on a growing product rather than a narrow specialism. APPLICATION WINDOW, STATED BY THE EMPLOYER Netskope says the application window for this position is expected to close within 50 days of posting, which is a rare and useful piece of information. Most employers publish no timeline at all. LOCATION AND WORKING PATTERN Listed for India without a specific city. Confirm the location expectation early, since the posting does not name an office. HONEST FIT GUIDANCE Scala expertise is unusual to find and is listed first, so if you have production Scala this is a strong match. The stated six to nine band with an upper bound suggests candidates well beyond nine years may be levelled differently.
WHAT YOU WILL BRING, AS PUBLISHED - Experience managing customer facing technical cases from first contact through triage, reproduction, bug reporting and resolution. - Strong Linux systems administration knowledge, stated as comparable to LFCE or RHCE certification. - Ability to use scripting languages such as Ruby or Bash and work with MVC frameworks such as Ruby on Rails. - Hands on experience with Git and CI/CD in production or customer environments. - Skill in writing clear, accurate support content and documentation based on real customer scenarios. - Ability to explain complex technical concepts clearly. WHAT THE JOB ACTUALLY IS DAY TO DAY Supporting a mix of self managed and GitLab.com SaaS customers, resolving complex issues through Zendesk tickets, merge requests, email and video calls. Investigating and troubleshooting using Linux tools, logs and the GitLab codebase, creating merge requests where needed. Creating and updating reusable documentation. Pairing with other support team members on challenging cases. Contributing to improving support processes, tools and automation. Participating in hiring by reviewing applications and joining interviews. ON CALL, STATED PLAINLY The posting says you would participate in regular weekday and weekend on call rotations, daytime only, providing emergency support for self managed and SaaS customers and coordinating incident communications with the SaaS production team. The daytime only qualifier is a meaningful limit and is worth noting, since weekend on call without it would be a heavier commitment. NO YEARS FIGURE IS PUBLISHED GitLab does not publish a years of experience figure on this or any of its postings. We have recorded the experience as not stated rather than inventing one, so this role appears in no experience filter on our board. The word Intermediate in the title is the only level signal the company gives. LOCATION AND WORKING PATTERN Bengaluru. HONEST FIT GUIDANCE If you can read Ruby and are comfortable at a Linux command line, this is a genuinely technical customer facing role at a company known for working transparently. It carries no people management.
SKILLS WE ARE LOOKING FOR, AS PUBLISHED - Strong professional software engineering experience with a track record of shipping production systems. No years figure is given. - Deep proficiency in Python, including modern typing, testing practices and packaging. - Strong SQL fundamentals and a working understanding of how analytical query engines and data warehouses execute queries. - Experience designing systems involving parsing, compilation or transformation, for example query planners, DSL compilers, type systems or rule based engines. - Solid grasp of software design principles: clean APIs, modularity, testability and backwards compatibility. - Excellent written and verbal communication, including explaining complex trade offs to engineers, product managers and external community members. - Experience collaborating in a distributed, asynchronous team environment. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing, building and maintaining core MetricFlow features including metric definitions, query compilation, dimensional modelling and SQL generation across multiple data warehouses. Owning MetricFlow as an open source project: triaging issues, reviewing external pull requests, managing releases and engaging the community on GitHub and Slack. Ensuring MetricFlow integrates with dbt Cloud, dbt Core and the Semantic Layer service. Improving performance, reliability and observability of metric query execution at scale. Writing technical documentation, RFCs and design docs. Mentoring engineers through code review and pairing. NO YEARS FIGURE IS PUBLISHED Fivetran asks for strong professional experience without stating a number, so we have recorded the experience as not stated rather than guessing. That means this role sits in no experience filter on our board. Where no floor is set, it is worth applying if the skills match even when you would not clear a typical senior bar. LOCATION AND WORKING PATTERN Bengaluru, described within an APAC structure. The team works distributed and asynchronously. HONEST FIT GUIDANCE The compilation and parsing requirement is the real filter and it is a genuinely specialised skill. Because MetricFlow is open source, you can read the codebase and its open issues before applying, which is the strongest preparation available for this particular role.
TECHNICAL SKILLS, AS PUBLISHED - Experience using Java, React and AWS, with experience in object oriented programming. - Experience with AI skills. - 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. - Good awareness of test driven development, continuous integration and continuous delivery approaches and tools. - Bonus points for working knowledge of cloud technology such as AWS, Azure, Kubernetes and Docker. WHAT THE JOB ACTUALLY IS DAY TO DAY Learning and adopting practices such as writing clean reusable code using TDD, pair programming and design patterns. Advocating for continuous delivery to get value to end customers early. Working in collaborative, value driven teams building customer experiences for clients. Creating large scale distributed systems out of microservices. Collaborating with teammates on features, design concepts and interactive prototypes. Applying technology thinking from the company's Technology Radar to client problems. Using DevSecOps tools and practices and shifting security left. Overseeing or taking part in the entire cycle of software consulting and delivery, from ideation to deployment. Acting as a mentor for less experienced peers. NO YEARS FIGURE IS PUBLISHED Thoughtworks states no years of experience requirement in this posting, so we have recorded it as not stated rather than inferring one from the Senior title. It therefore appears in no experience filter on our board. LOCATION AND WORKING PATTERN Bengaluru. Note that Thoughtworks postings have carried a remote tag in the past that contradicted the stated city; this one is published for Bangalore and we have recorded it that way. Confirm the arrangement during the process. HONEST FIT GUIDANCE Consulting is the variable here rather than the technology. If you want deep ownership of one product over years, this is not that. If you want variety, strong engineering practice and exposure to many domains, it is one of the better places to get it. The mentoring is of peers, not direct reports.
CORE TECHNICAL REQUIREMENTS, AS PUBLISHED - Java at expert level: 9+ years of production Java. The posting says you should not just write Java but define how it should be written on the team. - Deep expertise in JVM tuning, concurrency primitives, garbage collection behaviour and framework internals including Spring Boot and reactive stacks. - The ability to diagnose and resolve problems at that level. THE AI EXPECTATIONS, WHICH ARE STATED AS THREE DISTINCT ROLES 6sense sets out staff level AI expectations in three parts. Practitioner: uses AI assistants such as Claude Code and Copilot daily across the full software development lifecycle, covering design, implementation, testing, code review, incident response and documentation. Multiplier: establishes team wide AI workflows and prompt libraries, runs internal sessions on effective AI augmented engineering, and makes the team better at using AI rather than only themselves. Evaluator: assesses new AI tooling critically. This is the most detailed AI expectation published by any employer in today's edition. WHAT THE JOB ACTUALLY IS Setting the direction for how integrations are built across the team, championing AI native engineering practices across the organisation, and ensuring the platform scales with the business. The posting describes the staff role as a technical multiplier rather than only a strong individual contributor. LOCATION AND WORKING PATTERN Bengaluru. Office days are not stated. HONEST FIT GUIDANCE Nine years of Java is a real floor and the JVM internals requirement makes it a genuine one rather than a formality. Note that "multiplier" here means influence and enablement, not people management: no direct reports appear anywhere in the posting. If you have tuned a JVM under production load and can explain the decision, that is exactly the evidence this posting asks for.
Added August 9, 2026
What the posting asks for: 1 to 2 years of hands-on experience in DevOps, Platform Engineering or Cloud Engineering. Strong Python programming is listed as mandatory, including experience building automation tools and scripts in Python. Hands-on experience with modern DevOps tooling, Kubernetes, Infrastructure as Code and CI/CD pipelines. The team is building automation powered by generative and agentic AI on top of its cloud infrastructure, so interest in applying AI to operational problems is part of the pitch. The actual day to day: help maintain uptime of the SaaS service and implement process improvements that raise it, deploy production applications, help keep the production environment secure, begin writing code that automates infrastructure maintenance and deployments, support developers and work with more senior teammates to understand why architecture and design decisions get made, and write good documentation and runbooks. The posting also asks you to build an understanding of the whole product, and describes the goal as developing TechOps skills to become a core member of the operations team. Location and office reality: Pune, India. The posting does not describe this as a remote role and does not state office days. Honest fit guidance: this is the most accessible role in today's edition and the only one that names a 1 to 2 year band. It suits someone out of a first DevOps or cloud job, or a strong graduate who has genuinely written Python automation rather than only studied it. If you have no production Python, the mandatory line will be a real filter. If you already have four or more years in SRE work, this will be a step down in scope. Note on the link: LogicMonitor's own careers page returns an error on the URL its job feed publishes. The working link, which we checked and which loads this exact role, uses the plural careers path.
What the posting asks for: at least 2 years of relevant work experience. A solid background in algorithms, data structures and system design. Experience building scalable and fault tolerant distributed systems. Knowledge of distributed model training and inference, for example tensor parallelism and pipeline parallelism, is preferred rather than required. Knowledge of GPU programming is also preferred. The actual day to day: developing open source software that makes distributed programming simpler, identifying and evaluating architectural improvements to Ray Core, and improving Ray's testing process so releases go out smoothly. Named example projects include optimising the performance of large scale workloads on Ray, building stability and stress testing infrastructure, and improving fault tolerance and high availability. The posting also asks you to communicate your work publicly through talks, tutorials and blog posts, which is unusual and worth knowing if writing in public does not appeal to you. The team, in the posting's own words, splits its time between new features and distributed libraries, test infrastructure improvements, debugging, and longer term architectural work on Ray. Location and office reality: Bengaluru, Karnataka. The posting does not state office days or describe the role as remote. Honest fit guidance: the 2 year floor is real, but the subject matter is not junior. You need genuine comfort with concurrency, memory and scheduling, and ideally some C++. Someone with two years of web application work and no systems exposure would find this hard. Someone with two years of systems or infrastructure work, or a strong open source track record, is exactly who this is written for. Because Ray is open source, you can read the codebase before you apply, which is a rare advantage.
What the posting asks for: a minimum of 2 years of IT support experience in a fast paced startup or technology environment. Strong troubleshooting across macOS, Windows and mobile devices on both iOS and Android. Experience with Google Workspace, Okta including single sign on and multi factor authentication, Slack and other SaaS tools. A strong customer service mindset, described as friendly, patient and proactive. The actual day to day: hands-on IT support for employees in the Bengaluru office. Supporting onboarding and offboarding, including provisioning and deprovisioning accounts and setting up new hire equipment. Troubleshooting problems with applications, laptops, access, peripherals, printers, video conferencing and networking. Assisting with meeting room technology and corporate events so hybrid meetings and audio visual setups work properly. Managing user accounts, access and security settings across the company's SaaS tools. Maintaining IT asset inventory and coordinating hardware repairs, upgrades and procurement. Helping enforce IT policies and basic security practices. Collaborating with the IT team on automation, documentation and process improvement. The company describes itself as scaling fast with strong product market fit, and names three values it operates by: decisiveness, simplicity, and the idea that the job is not finished. The posting is explicit that the pace is high. Location and office reality: Bengaluru. This is an in-office role by its nature, since it covers physical equipment, meeting rooms and events for that office. Honest fit guidance: apply if you have done IT support in a startup and enjoy being the person who unblocks everybody. This is not a software engineering role and will not become one automatically, though the automation and documentation work is a real path toward IT engineering. If you want to write product code, this is not the door.
What the posting asks for: a Bachelor's degree in Computer Science or Engineering, or equivalent practical experience. 3 or more years writing high quality production code. Hands-on experience building and maintaining highly available, scalable and performant distributed systems. Expertise in cloud native technologies across AWS, Azure or GCP, and Kubernetes based deployments. A deep understanding of networking, security and authentication in cloud environments. Familiarity with observability stacks such as Prometheus and Grafana. Proficiency in Go and Python. Knowledge of low level operating system foundations including the Linux kernel, file systems and containers. The actual day to day: designing, building and scaling services that orchestrate Ray clusters across cloud and on-premises environments, supporting both virtual machine based and Kubernetes based deployments. Optimising control plane components for large scale distributed AI and ML workloads. Building scheduling and resource management systems for heterogeneous compute clusters. Improving the reliability, performance, scalability and observability of Anyscale managed Ray workloads. Supporting and optimising accelerator integration for GPUs and TPUs. Handling container image management and dependency resolution. Taking part in code reviews and architecture discussions. Providing on-call support and working with customer and field teams to troubleshoot infrastructure issues. Location and office reality: Bengaluru, Karnataka. The posting does not state office days or describe the role as remote. Honest fit guidance: three years is the stated floor but the requirement list is broad, asking for Go and Python, Kubernetes, cloud networking and Linux internals together. If you have run Kubernetes in production and written infrastructure services rather than only used them, you are the target. If your Kubernetes experience is deploying applications onto a cluster someone else operates, expect the interview to go deeper than that.
What the posting asks for, in full: a Bachelor's degree in Computer Science, Information Technology or a related technical field. A minimum of 3 years of professional software engineering experience. A strong foundation in programming and software design principles, with excellent coding skills in any of the major programming languages such as Java, Python or JavaScript, plus a solid understanding of object oriented principles. A solid understanding of data structures and algorithms. The posting does not publish a separate responsibilities list for this level, and it does not name a specific product team, stack or framework beyond the languages above. What the company says about joining: onboarding includes department specific training, and Appian names a mentorship scheme and a First Friend programme for new hires. It also lists tuition reimbursement and internal training through what it calls Appian University, and eight employee led affinity groups. Location and office reality: Chennai, India. The posting does not state office days or describe the role as remote. Honest fit guidance: a short requirement list cuts both ways. It means you are not screened out for missing a named tool, and it usually means the interview leans hard on fundamentals instead. Expect data structures and algorithms to carry real weight, because the posting mentions them explicitly and mentions almost nothing else. This is a good fit for a strong three to five year engineer who interviews well on core computer science and is comfortable being placed on a team after hiring rather than before. Appian has six roles in today's edition across very different levels, and they are separate requisitions, not one job posted repeatedly.
What the posting asks for: a BS or MS in Electrical Engineering, Electronics and Communication Engineering, Computer Science, or equivalent work experience. 3 or more years of industry experience in an operations environment. Experience in hardware bring-up and debug of complex systems. Working knowledge of ASIC bring-up and test processes. Working knowledge of scripting in languages such as Python or Perl. Proven experience in system bring-up and validation of complex computer systems or equivalent. An understanding of computer system architecture and hardware components. Proficiency with scripting and automation tools for system bring-up. Strong problem solving and communication skills, and strong coordination skills, which the posting stresses because the workflow is business critical and tied to customer demand. Preferred: familiarity with creating test and software infrastructure at large scale, and comfort working across global time zones. The actual day to day: supporting the bring-up process that configures, tests and validates system performance before customer shipment. Working across ASIC, software, diagnostics and QA teams to automate and streamline that workflow. Troubleshooting technical issues during system bring-up. Designing processes to track bring-up status and progress. Reporting on bring-up metrics. Adding software automation so the process scales with the manufacturing roadmap. Location and office reality: the posting lists Bangalore, India alongside Toronto, Canada and Sunnyvale, California as locations for the role. Cerebras publishes its India roles under a single India Office location label on its job board. Honest fit guidance: this is one of the few roles on this board aimed at hardware and systems people rather than application developers. If you studied electronics or worked in hardware validation, test or manufacturing engineering, three years is a realistic entry point here. If you are a pure software engineer with no hardware bring-up exposure, the ASIC and debug requirements are the real gate.
What the posting asks for: 3 to 4 years of software development experience in commercial or enterprise applications. A BS or higher in computer science or a related field. Familiarity with current Java, Go or Python development frameworks and open source tooling. Named required skills are Java (preferred), Go or Python, object oriented design, REST APIs, multithreading and concurrency, data structures and algorithms, Kubernetes, and AWS. The actual day to day: designing and developing cloud native applications in Java, Go or Python. Building Kubernetes native monitoring components and agents. Developing features for metrics, logs, events and trace collection using OpenTelemetry. Working with Kubernetes APIs to discover and monitor cluster resources. Building scalable microservices for telemetry ingestion and processing. Building and maintaining Helm charts and containerised deployments. Optimising for performance, scalability and reliability. Troubleshooting production issues across distributed systems. Working with product management, QA and SRE teams. Contributing to architecture discussions, code reviews and engineering practices. The posting also describes the wider remit of the backend developer on this team as covering implementation, design, architecture and quality control for integrations within the customer facing product and the internal tools used by technical operations. Location and office reality: Pune, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the band is narrow and honest, 3 to 4 years. The Kubernetes and OpenTelemetry expectations are concrete, so hands-on exposure matters more than the number. If you have three years of Java backend work and have genuinely operated services on Kubernetes, you fit. If Kubernetes to you means a deployment file someone else wrote, expect that to be probed. Note on the link: LogicMonitor's job feed publishes a careers URL that returns an error. The working link we verified uses the plural careers path and loads this role.
What the posting asks for: a Bachelor's degree in Computer Science, Engineering or a related field. 3 to 5 years of backend software development experience. A strong understanding of data structures, algorithms and core computer science fundamentals. Proficiency in one or more backend languages such as Java, Kotlin, Node.js, Python or Go. Experience designing and building REST APIs and backend services in a distributed or service oriented environment. Familiarity with relational or NoSQL databases. Experience with Git, code reviews, testing practices and standard development workflows. The ability to debug application and production issues. Good communication and the ability to work in cross functional teams. Preferred: experience with microservices architecture and distributed systems, familiarity with backend frameworks such as Spring Boot, Express or NestJS, or Django, and working knowledge of platform concepts. The actual day to day: designing, building and maintaining backend services behind entitlements, usage tracking, integrations and platform APIs. Owning small to medium features end to end, from design through production support. Developing scalable and secure APIs for internal and external consumers. Building service to service integrations across identity, billing, metering and tenant management. Breaking requirements into technical tasks and surfacing risks and tradeoffs. Debugging production issues and taking part in incident response. Contributing to code reviews, testing and documentation. Improving observability through logging, monitoring and tracing. Working with product managers, QA and peer engineering teams. Location and office reality: Bangalore, India. The posting does not state office days or describe the role as remote. Honest fit guidance: this is a straightforward mid level backend role with an unusually clear scope, which is a good sign. The language list is broad, so you are not locked out for using Node.js instead of Java. Billing, metering and entitlements work is less glamorous than product features but it is genuinely hard at scale and transfers well to any SaaS company.
What the posting asks for: 3 to 6 years building software as a technical product manager or a user focused product engineer. Product sense, described as asking why before how. Deep expertise in one domain with breadth across others. The ability to read code and fix CI/CD configurations when needed. A track record of shipping rather than only building. The skills it says you should have depth across: customer backward thinking, product solutioning, prototyping and designing, building and taking products live, and taking solutions to market including driving adoption and measuring impact. It expects good competence in the ones that are not your strength, and says that in past roles you have juggled multiple hats. On AI tooling, the posting is specific: it expects more than a year of using AI tools, with Claude Code or Cursor as your default environment, orchestrating agents, and building with skills and MCPs. It describes AI assistance as muscle memory and expects you to be a polyglot because AI shortens the ramp on new stacks. Who the posting says will not fit, in its own framing: people who need detailed specifications handed to them, who prefer deep specialisation over breadth, who are uncomfortable with ambiguity, who optimise for code elegance over customer outcomes, or who thrive living in a two week sprint. Location and office reality: Bengaluru. The posting does not state office days or describe the role as remote. Honest fit guidance: read the not-a-fit list first, because it is the clearest part of the posting. This suits a generalist who has shipped products end to end and genuinely works AI-first day to day. If you are a specialist backend or frontend engineer who wants a deep technical track, this is not that role, and the posting says so itself rather than hiding it.
What the posting asks for: 4 or more years of hands-on experience in data science or analytics roles solving real business problems. A Bachelor's or Master's degree in a quantitative field such as engineering, statistics or mathematics. Strong analytical skills and the ability to translate insight into solutions for specific business challenges. Strong proficiency in Python or SQL, with experience handling large datasets and working with distributed computing tools. Effective communication and enjoyment of cross functional collaboration with product, business and risk teams. The actual day to day: analysing multi dimensional data to find user patterns, emerging trends and risk signals that inform lending and growth strategy. Developing and maintaining churn and propensity models to detect disengaged users and recommend data driven interventions that improve retention. Leading campaign analytics, building user segments and evaluating communication effectiveness with a focus on targeting, engagement and in-funnel conversion. Partnering with product teams on feature development using cohort analysis, funnel diagnostics and retention trends. Collaborating across product, risk, technology, compliance and business. Owning strategic analytical initiatives end to end, from problem framing and hypothesis design through stakeholder communication and impact tracking. Supporting and mentoring junior analysts and promoting good practice in data hygiene, modelling and experimentation. Location and office reality: Hyderabad. The posting does not state office days or describe the role as remote. CRED writes its job postings in lower case, which is a house style rather than an error. Honest fit guidance: this is applied decision science, not research or deep machine learning. If you want to train novel models, this is the wrong seat. If you like being the person whose analysis decides what gets built and who gets targeted, and you are comfortable talking to risk and business stakeholders, four years of solid analytics work is enough to be competitive here.
What the posting asks for: 4 to 5 years of experience in AI and ML engineering with a focus on generative AI, AI driven automation and natural language processing. Strong proficiency in Python, Java or similar languages for model development and deployment. Hands-on experience with large language models, retrieval augmented generation and prompt engineering. Expertise in embedding based search and semantic retrieval. The actual day to day: building and optimising LLM based solutions that generate human readable incident reports, root cause explanations and remediation suggestions. Using retrieval augmented generation to surface relevant documentation, logs and knowledge base insights for IT teams. Developing semantic search and context aware retrieval so teams can find relevant data, logs and metrics quickly. Optimising AI models for real time performance in distributed cloud native environments including AWS, GCP and Kubernetes. Working across platform engineering, product and data science to align AI features with customer needs. The posting also asks you to stay current with AI and ML advances, which it labels an AI first attitude. Location and office reality: Bangalore, India. The posting does not state office days or describe the role as remote. Note that LogicMonitor's other roles in today's edition are in Pune, so this is the Bangalore seat. Honest fit guidance: the distinguishing requirement here is production LLM work, not research. If you have built a RAG pipeline that real users depend on and have had to make it fast and cheap enough to run continuously, you are the target. A portfolio of notebook experiments will read thinner than one shipped feature. Domain knowledge of observability is not required and is not asked for. Note on the link: LogicMonitor's job feed publishes a careers URL that returns an error. The link we verified uses the plural careers path and loads this role.
What the posting asks for, with three items marked mandatory: 5 or more years of Linux systems administration with a focus on storage such as Ceph (mandatory). Proven experience with enterprise storage systems, with Pure Storage, NetApp, EMC, Dell, IBM and Hitachi named (mandatory). A strong understanding of RAID, LVM, NFS, iSCSI, multipathing and file systems including ext4, XFS and ZFS (mandatory). Hands-on experience with enterprise storage systems and clustering technologies. Proficiency in shell scripting. Python, Puppet or Ansible knowledge, and experience with virtualisation such as VMware or KVM. Familiarity with cloud storage including AWS S3 and EBS. Experience with monitoring tools such as Nagios, Prometheus or Zabbix. The actual day to day: designing and deploying storage infrastructure across SAN and object storage. Monitoring and maintaining storage systems for performance, availability and reliability. Capacity planning and forecasting. Developing backup, replication and disaster recovery strategies. Troubleshooting storage issues. Maintaining configuration and procedure documentation. Working with other platform engineering teams on upgrades, migrations and integrations. Automating storage provisioning and management. Hiring process, which Adyen publishes: it aims to respond to applications within 5 business days, and says the interview process tends to take about 4 weeks, varying by role. Location and office reality: this one is unusually clear and worth reading before you apply. The posting states the role is based out of the Bengaluru office, that Adyen is an office first company that values in person collaboration, and that it does not offer remote only roles. That is a plain statement rather than a tag, and it is the honest opposite of the postings that carry a remote label the body then contradicts. Honest fit guidance: this is for a storage specialist. If Ceph, multipathing and iSCSI are your daily vocabulary, five years is a fair entry point. If your infrastructure experience is entirely managed cloud services, the mandatory lines will rule you out. Adyen also adds a note encouraging people who do not meet every qualification to apply anyway.
What the posting asks for: at least 5 years of relevant work experience. A solid background in algorithms, data structures and system design. Experience building scalable and fault tolerant distributed systems. Experience with data processing and database internals, with Spark or Dask named specifically, and streaming experience listed as a plus. The actual day to day: developing open source software that simplifies distributed programming. Identifying, implementing and evaluating architectural improvements to Ray Core and Ray Datasets. Improving Ray's testing process so releases go smoothly. Communicating your work publicly through talks, tutorials and blog posts. Named example projects: performance of Ray Datasets at large scale, including using Arrow primitives and optimising the Ray object manager. Integration with machine learning training and data sources. Stability and stress testing infrastructure. Leading future work to integrate streaming workloads into Ray, with Beam on Ray given as the example. Differentiating data operations in Anyscale's hosted Ray service. Location and office reality: Bengaluru, Karnataka. The posting does not state office days or describe the role as remote. Honest fit guidance: this is the data engineering seat of the three Anyscale roles in today's edition, and the most senior at five years. It suits someone who has worked on the internals of a data processing system rather than only used one. If you have optimised Spark jobs but never looked inside the engine, expect the interview to head toward memory layout, shuffle behaviour and scheduling. As with the other Ray roles, the codebase is open source, so you can judge the work for yourself before applying.
What the posting asks for: a Bachelor's or Master's degree in Computer Science, Information Technology or a related field. An educational background from a highly selective premier engineering institution with a focus on computer science fundamentals is stated as preferred. 5 or more years of experience in software engineering. Knowledge of data structures, algorithms and design patterns applied in a full stack Java and web technology environment. A proven track record building and scaling distributed systems, preferably cloud native. Experience identifying bottlenecks and optimising performance in large codebases. Experience with AI and ML adoption and integrating intelligent features into standard workflows. Experience leading technical initiatives or small project groups. Strong knowledge of enterprise application architecture. The actual day to day: setting and enforcing the standard for clean, maintainable, documented code across the repository. Leading high level design sessions and choosing architectural patterns such as microservices, serverless and event driven designs. Creating internal tooling and paved paths that abstract infrastructure complexity for feature teams. Mentoring junior engineers and running rigorous code reviews. Driving features from requirement analysis through deployment, including breaking business goals into technical tasks. Debugging hard production problems, handling outages and optimising performance bottlenecks. Collaborating with product owners and across teams. The posting also mentions system orchestration and AI integration specifically, naming retrieval augmented generation, agentic workflows and MCP. Location and office reality: Chennai, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the institution preference is the line worth reading twice. It is written as preferred, not required, and Appian's other Chennai roles in today's edition publish no such preference at all. If you are five years in with strong Java and real distributed systems work, apply and let them decide rather than screening yourself out. If mentoring and standard setting do not appeal, note that they are a large part of how this role is described.
What the posting asks for: 5 or more years of Salesforce development experience covering Apex, process and flow automation, and Lightning Web Components. 3 or more years of general software engineering, with significant experience in Java, Python or JavaScript. In-depth knowledge and practical experience in Sales Cloud and Configure, Price, Quote, described as essential. Expertise in modern AI agent or Agentforce frameworks, orchestration techniques, retrieval augmented generation pipelines and vector search. Hands-on CI/CD experience specifically with Jenkins and Salesforce DX. A deep understanding of Salesforce security features, data privacy compliance and secure development practice. The actual day to day: translating user stories into scalable technical designs and owning features end to end. Architecting secure, scalable solutions on the Salesforce platform, particularly in Sales and CPQ. Ensuring 100 percent unit test coverage for new logic and maintaining an automated regression suite. Running thorough pull request reviews and giving feedback to junior and mid level developers. Managing the deployment cycle, including change documentation, approvals, resolving environment specific test issues and final production validation. Working with cross functional global teams. Location and office reality: Bengaluru, India. The posting does not state office days or describe the role as remote. Honest fit guidance: note the two separate experience numbers. Five years is on Salesforce specifically, three years is general software engineering, and they are additive requirements rather than alternatives. If you are a Salesforce developer who has never worked outside the platform, the general engineering line matters. CPQ experience is the hardest thing to fake here and is called essential. The AI agent requirement is new enough that few candidates will have deep experience, so treat it as a differentiator rather than a wall.
What the posting asks for: 5 or more years in application security, secure software engineering or related security engineering roles. Strong knowledge of web and API security including the OWASP Top 10, authentication and session management, input validation, access control, SSRF, XSS, SQL injection and CSRF. Hands-on experience with SAST, DAST and SCA tools and integrating them into CI/CD pipelines. Proficiency with secure coding and threat modelling methodologies. Experience with at least one programming language such as Java, Python, Go, JavaScript or TypeScript, or C Sharp, and the ability to conduct security code reviews. A solid understanding of cryptography basics, authentication and authorisation models, logging and monitoring, and secure configuration. Experience with vulnerability management processes covering triage, prioritisation, risk acceptance and verification. Preferred: cloud security experience across AWS, Azure or GCP and containerised environments. Familiarity with OWASP ASVS, SAMM or similar maturity frameworks. Security automation experience including custom scripts, policy as code and security dashboards. Certifications such as OSCP, eJPT or eWPT, or AppSec focused certifications, listed as optional. The actual day to day: designing and scaling application security programmes across requirements, design, development, testing and release. Performing security assessments. Building security test automation. Reviewing architecture and code changes and giving actionable remediation guidance. Leading remediation of high severity vulnerabilities and validating fixes. Defining security standards and guardrails. Working with DevOps, platform and product engineering on secure deployment and runtime configuration. Creating security documentation and developer training. Monitoring security posture and reporting on it. The posting names who you work with: product engineering, DevOps and platform, QA and security leadership, and says you take part in design reviews, incident response as needed, and security roadmap planning. Location and office reality: Bangalore, India. The posting does not state office days or describe the role as remote. Honest fit guidance: five years is the floor and the list is broad but not exotic. If you have run appsec in a product company and can review code rather than only read tool output, you fit. The certifications are explicitly optional, so do not let their absence stop you.
What the posting asks for: 5 to 7 years of significant hands-on coding experience with Golang, preferably in a product development environment. Strong programming and design fundamentals with excellent problem solving and coding skills. Strong analytical and reasoning ability. A solid understanding of concurrency and multi threading. Experience architecting microservices and developing RESTful APIs. Listed as a plus: prior experience with high throughput and low latency storage, cloud computing, NoSQL databases, big data analytics, machine learning services or large scale systems. The actual day to day: designing, developing, testing and debugging components for distributed systems that operate at large scale and high speed. Owning non functional requirements such as scalability, availability and security. Developing and maintaining unit and integration tests with robust code and functional coverage. Producing documentation for internal and external collaboration. Breaking complex tasks into manageable components and planning and executing them. Working with the team to raise technology standards and apply best practice. Working in an agile environment. The posting also says you would mentor junior engineers. What the company says about the culture, in its own framing: it hires people who move fast, think critically, act like owners and care about solving customer problems precisely, and it states directly that people who want predictability or narrow scope will not enjoy it. Location and office reality: the job board lists this as Hybrid, India. The posting body does not name a specific city or state how many days a week are in office, so ask before you assume which office you would be attached to. Honest fit guidance: Golang depth is the requirement that matters, and the 5 to 7 band is stated clearly. Fraud and identity work suits people who like correctness under pressure, since a false decision has a real cost on both sides. Socure has a second engineering role in today's edition, an SRE seat, and the two are different teams.
What the posting asks for: 5 to 7 years in IT systems engineering or enterprise platform administration. A Bachelor's or Master's in Information Technology, Computer Science or a related field. Hands-on expertise with MDM platforms for macOS and Windows, with Jamf and Microsoft Intune strongly preferred and Workspace ONE or Kandji considered equivalent. Expert level proficiency in Microsoft 365, Entra ID, single sign on and identity platforms, and SaaS administration. Deep familiarity with macOS and Windows device management covering enrollment, compliance policies, configuration profiles, app deployment and patch workflows. Strong scripting and automation across PowerShell, Python or Bash, including automation against the Jamf API and Graph API. Demonstrated experience with security hardening, compliance readiness and endpoint monitoring. Strong documentation and cross functional communication. Mentorship experience. Relevant certifications preferred, with Jamf Certified Admin named. The actual day to day: leading implementation and optimisation of enterprise platforms including Entra ID, Microsoft 365, identity solutions and endpoint management tooling. Owning device management policy design, configuration and enforcement across macOS and Windows fleets. Designing and automating workflows for provisioning, access lifecycle management and endpoint standardisation. Owning root cause analysis on complex system and endpoint issues. Working with cybersecurity, infrastructure and application teams. Leading platform upgrades, integrations and migrations including MDM consolidations. Maintaining architectural documentation and change procedures for audit readiness. Mentoring junior engineers. The posting also publishes its own complexity and supervision framing: it leads technically complex projects across multiple platforms and large endpoint environments, and operates independently with minimal direction. Location and office reality: Tekion labels this Bangalore HQ on its board. The posting does not state office days, though an HQ label and the hands-on nature of fleet management both point to on site work. Honest fit guidance: this is corporate IT engineering, and it pays to be honest with yourself about whether that is the career you want. It is not a route into product engineering. It is, however, a strong specialism with genuine depth, and the scripting requirement means it rewards people who automate rather than click.
What the posting asks for: 5 to 8 years in automation engineering or SDET roles. Strong hands-on experience with Playwright in TypeScript, API automation across REST and GraphQL, and behaviour driven frameworks using Cucumber or Gherkin. Experience working in AWS based environments. A strong understanding of distributed systems and microservices testing. Experience integrating automation into CI/CD pipelines. Working knowledge of performance testing with K6. Strong coding, debugging and analytical skills. Experience collaborating in cross functional agile teams. Considered a plus: Docker, Kubernetes or EKS. Familiarity with contract testing tools. Exposure to telecom or communications platforms. Mobile automation with Appium. Contributing to shared cross team automation frameworks. The actual day to day: designing and maintaining scalable test automation frameworks, building UI automation in Playwright, implementing behaviour driven practice, generating structured reporting with Serenity, and developing API automation for REST and GraphQL. Contributing to mobile automation with Appium. Keeping frameworks modular and optimised for parallel execution, and integrating them into CI/CD across Jenkins, GitHub Actions, GitLab CI or CircleCI. Validating distributed systems across microservices with contract testing, schema validation, authentication and authorisation testing and failure scenarios. Contributing to service level agreement and objective validation. Developing and maintaining performance and load tests in K6 and analysing metrics through Grafana, Prometheus, CloudWatch and Datadog. Working with SRE and platform teams to find bottlenecks and reliability risks. Taking part in agile ceremonies and maintaining documentation in Confluence and Jira. Location and office reality: Bangalore, India. The posting lists hybrid work among its benefits but does not state how many days a week are in office. Honest fit guidance: the word Lead here appears to describe technical seniority, not a team to manage, since the posting contains no people management duties at all. Vonage also adds that there is no perfect candidate and you do not need every preferred qualification. If you are a strong automation engineer who has never done load testing, the K6 requirement is the gap most worth closing before applying.
What the posting asks for: 6 or more years hands-on experience with AWS services, specifically naming EC2, EKS, RDS, S3, VPC, IAM, MSK and CloudFormation or Terraform. Experience with datacentre to cloud migration methodologies including re-host, re-platform and re-architect. Virtualisation and container technologies including Docker and Kubernetes. Programming and scripting in Python or shell. The actual day to day: maintaining uptime of the SaaS service and driving technical and process improvements that raise it. Designing and migrating new infrastructure from datacentre to AWS. Writing code to automate infrastructure maintenance and deployment. Supporting development and working closely with developers to drive operational and architectural change. Owning and executing large, technically complex cross team projects. Setting the example on documentation and runbooks. Managing a global network of hybrid cloud computing services and providing guidance on organising, securing and automating systems. On FedRAMP: the posting states LogicMonitor intends to operate its platform in a FedRAMP compliant manner, with the goal of expanding its customer base and improving security for all customers, and it asks applicants to help uplift the platform to meet that standard and to keep the production environment secure. Location and office reality: Pune, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the differentiator is migration experience specifically. Plenty of engineers run workloads that were born in AWS; far fewer have moved a datacentre into it and dealt with what breaks. If you have done that, say so prominently. LogicMonitor has four roles in today's edition spanning 1 to 2 years up to this one, and they are different teams and levels rather than the same job repeated. Note on the link: LogicMonitor's job feed publishes a careers URL that returns an error. The link we verified uses the plural careers path and loads this role.
What the posting asks for: 6 to 9 years of professional backend experience, with a significant portion spent in high scale environments, with ad tech, data heavy SaaS or fintech named. Mastery of Python and the Django ecosystem, including asynchronous task processing with Celery and Redis, and database optimisation. Hands-on experience with distributed data processing frameworks such as Flink, Spark or Hive, including handling data drift and optimising large scale joins. Advanced SQL, with the ability to optimise complex analytical queries and an understanding of database internals such as indexing and partitioning. Familiarity with front end system design such as React and JavaScript event loops, and how client side tracking affects backend data integrity, listed as good to have. Practical experience or strong interest in deploying AI models into production. The actual day to day: leading development and maintenance of mission critical backend services with high throughput and low latency APIs. Writing performant Python and Django, and being the person who solves complex concurrency problems and optimises service performance. Designing and optimising data workflows and tuning complex queries in Hive, Flink or Trino. Working with front end engineers so client facing features are built for data fidelity and backend compatibility. Implementing AI and ML driven features such as automated anomaly detection or predictive data cleaning in production pipelines. Providing code reviews and technical guidance to mid level engineers. Location and office reality: Bengaluru, Karnataka, India. The posting does not state office days or describe the role as remote. Honest fit guidance: this is a genuine backend and data role rather than a general full stack seat, and the Python plus distributed data combination is the thing to match against. 6sense has four roles in today's edition at 6 to 9, 10, 10 and 12 years, all different teams. The posting also carries a recruitment fraud warning: all real emails come from the 6sense.com domain, initial contact is never by text message, and payment is never requested.
What the posting asks for: 6 to 9 years of software engineering experience with strong exposure to cloud native platforms. Strong programming in Java, Python or Go. Proficiency in infrastructure as code using Terraform or equivalent. Hands-on Kubernetes experience covering deployment, troubleshooting and scaling. Experience with CI/CD pipelines and deployment automation. Familiarity with observability tools such as CloudWatch and logging and monitoring systems. A good understanding of distributed systems and microservices architecture. Strong debugging and problem solving skills. Solid hands-on AWS experience across compute (EC2, Auto Scaling, EKS or ECS, Lambda), networking (VPC, ALB and NLB, Route 53), storage (EBS, EFS, S3) and security (IAM, KMS, Secrets Manager). Exposure to cloud cost optimisation is listed as a plus. Preferred: Kubernetes on EKS and containerised workloads, familiarity with GitOps workflows, experience supporting regulated environments such as SOC 2, FedRAMP and HIPAA, a strong understanding of cost optimisation and cloud economics, and prior experience in platform engineering or developer enablement teams. The actual day to day: leading development of reusable, versioned infrastructure as code modules and frameworks, and defining practice for scalability, availability, security and cost. Designing and owning AWS infrastructure architectures. Reviewing architecture designs and code. Building and maintaining infrastructure with Terraform, CloudFormation or CDK, and Ansible where applicable. Implementing CI/CD pipelines for infrastructure provisioning and change management. Driving immutable infrastructure and automated environment lifecycle management, and enabling self service provisioning for internal teams. The posting also includes general platform engineering duties such as code reviews that address design as well as code quality, identifying refactoring and performance opportunities, and mentoring junior engineers. Location and office reality: Chennai, India. The posting does not state office days or describe the role as remote. Honest fit guidance: if your background is application development rather than infrastructure, the Terraform and AWS depth here is substantial and the interview will find gaps quickly. If you have built a platform team's paved path, this is written for you. Note that Appian has six roles in today's edition, all separate requisitions at different levels and on different teams.
What the posting asks for: 6 to 9 years with an in-depth understanding of networking protocols, technologies and concepts including TCP/IP, VLANs, routing, switching and subnetting. Experience designing, implementing and maintaining wireless infrastructure, including troubleshooting wireless issues and optimising coverage, capacity and performance. Strong hands-on experience with RADIUS, identity providers such as SAML, OAuth and OpenID Connect, LDAP and other authentication, authorisation and accounting systems. An understanding of security principles including multi factor authentication, encryption and vulnerability management. Experience with scripting and automation tools that manage network and infrastructure configuration changes, preferably under source control, with Python, Ansible and Terraform named as significant pluses. Experience with network monitoring and troubleshooting tools. A BS in Computer Science or a related degree, or equivalent experience. The posting also asks for two softer qualities in its own words: an ability to approach problems from unconventional angles and offer unique perspectives, and a forward thinking mindset that forecasts potential problems and follows developing technology trends. The actual day to day: planning and leading LAN, WAN, network security and systems projects across diverse platforms, including multi vendor wired networks (enterprise switches, routers and firewalls), wireless networks, VPNs and voice over IP, across a hybrid global infrastructure footprint. Internal certificate and certificate authority management. Configuring and managing RADIUS servers in a high availability environment. Location and office reality: Chennai, India. The posting does not state office days or describe the role as remote. Note that hands-on network and wireless work usually implies site presence, so ask. Honest fit guidance: this is a network and infrastructure engineering role, not software engineering, and it sits in the security organisation. If you hold networking certifications and have run enterprise wireless and RADIUS, six years is a fair entry point. The automation requirement is the part most network engineers under-invest in, and it is where this posting says it will differentiate.
What the posting asks for: 7 or more years of physical design or verification experience. Strong experience in block and subsystem timing closure. Strong knowledge of block level and full chip physical verification methodology. Expertise in optimising for power, performance and area. Experience with block physical design, physical design verification and IR analysis. Expert use of ICV or Calibre tools to resolve block and full chip design rule check and layout versus schematic issues. Expertise in IR drop and electromigration analysis and resolution. A good understanding of full chip floorplanning and integration. Strong scripting in Tcl and Python, with the ability to make flow enhancements. Demonstrated ability to work with RTL teams to optimise for physical design. The ability to take on a leadership role after ramping up on wafer scale design. BSEE, MSEE or PhD in Electrical Engineering preferred. Preferred: experience with the complete physical design flow, knowledge of the Synopsys tool suite, and synthesis and static timing analysis. The actual day to day: performing physical design tasks including synthesis, place and route, timing and block closure and signoff, being involved in all aspects of physical design and implementation, and working closely with the RTL team and on full chip integration of blocks. Location and office reality: Cerebras publishes its India roles under a single India Office label, and this posting names Bengaluru in its title. Honest fit guidance: this is a VLSI role in the truest sense, and it is one of the few on this board. If you have done timing closure and signoff on complex designs, seven years is the stated floor. If you are a software engineer, none of this transfers. The posting's repeated emphasis on being coachable and a strong learner is worth taking at face value: wafer scale is genuinely different, and they seem to expect the ramp.
What the posting asks for: 7 or more years of proven experience as a software engineer specialising in web backend development. Proficiency in Golang is described as a significant advantage rather than mandatory. Additional experience in data engineering is highly desirable. A track record of delivering high quality production services and systems. A customer centric approach with empathy toward users. Relevant industry experience, particularly banking or fintech, with domain knowledge in fraud prevention or compliance. Proficiency in English across everything from casual conversation to formal reports. The technologies the posting says the team uses: TypeScript with React and Node, Golang, Ruby, Bigtable, Postgres, GCP Dataflow on Apache Beam, BigQuery, Python, Java and Terraform. The actual day to day: designing, creating and maintaining backend services. Working with business stakeholders to architect and implement new services from inception to delivery. Contributing to new features and capabilities. Coordinating with engineering and product teams. Writing and maintaining user facing technical documentation. Contributing to engineering culture and standards across the organisation. Location and office reality, which matters here: the posting says Remote, India, and then states that to be considered you must reside in one of five cities: Bangalore, Delhi, Gurugram, Mumbai or Pune. Sardine describes itself as remote first with a globally distributed team and hubs in the Bay Area, New York, Austin, Toronto and Sao Paulo, and says you can work from anywhere, but the eligibility list above is what the posting actually requires. If you live outside those five cities, this is not open to you despite the remote label, and that is exactly the kind of detail that costs people an application. Benefits the posting names: compensation in cash and equity, early exercise for all options including pre-vested, remote first working, and flexible paid time off with a year end break. Honest fit guidance: seven years of backend work is the bar, and Golang plus fintech is the strongest combination. Fraud and compliance domain knowledge is listed but framed as relevant experience rather than a hard requirement.
What the posting asks for: 8 or more years of professional experience in legal technology or enterprise SaaS implementation, preferably in a technology company or a law firm technology function. A minimum of 2 years demonstrably using AI in workflows and to support customers. A proven track record architecting and building AI powered applications including multi agent workflows, retrieval systems and LLM integrations. A proven track record in forward deployed, embedded or client centric technical positions. Experience researching and implementing custom applications from marketplace research through design and implementation. An advanced degree such as an MS or MBA in Business, Computer Science or related fields is preferred rather than required. Demonstrated experience designing and implementing custom business solutions and integrations on enterprise platforms. Skill at stakeholder engagement in large global organisations. Experience leading complex projects and simplifying technical concepts. Excellent written and verbal communication, especially in critiquing technical designs, leading workshops and engaging senior leadership. The actual day to day: partnering with practice group leads, paralegals and in-house counsel to identify workflow automation and AI opportunities. Acting as the technical directly responsible individual for legal AI tools from intake through deployment. Building, testing and deploying legal AI workflows, multi agent workflows, RAG pipelines and AI copilots powered by Claude Enterprise, with building MCPs described as an add on. Running discovery workshops and translating business requirements into engineering ready specifications. Navigating internal governance processes for security and privacy on behalf of legal stakeholders. Maintaining the legal technology project portfolio. Building relationships with deputy general counsels, legal operations leads and partners in BizTech, security and engineering. Designing and delivering Claude Enterprise training for legal teams covering prompting, workflow integration and responsible AI use. Creating adoption playbooks and enablement material. Tracking usage and adoption metrics and reporting to legal technology and chief legal officer leadership. Location and office reality: Bangalore, India. The posting does not state office days or describe the role as remote. Honest fit guidance: note the two experience figures, 8 years overall and at least 2 years using AI in production workflows. This is not a core product engineering role and will not look like one on your CV. It is, however, one of the clearest examples on this board of applied LLM engineering with real users, and the domain expertise in legal technology is genuinely portable.
What the posting asks for: a Master's degree in Computer Science, Electrical Engineering or equivalent. 8 or more years of experience delivering complex, high performance, high quality RTL designs. Experience with front end chip integration and third party IP integration. Demonstrated experience in networking, high performance computing, machine learning or related fields. A proven track record of multiple silicon success. Experience collaborating with external vendors. Networking stack experience including TCP/IP, RDMA and Ethernet. Knowledge of PCIe, CPU interfaces and SerDes technology. Working knowledge of scripting tools including Python and Tcl. The posting also states you should be able to work in a hybrid work environment. Listed as assets: experience with the FPGA development toolchain including place and route, floorplanning and timing analysis, and experience managing an external ASIC vendor through a product development cycle. The actual day to day: driving all aspects of chip design including functional specification, microarchitecture, RTL development and synthesis. Working with physical design team members on design closure to meet power, performance and area goals. Working with design verification and DFT teams to achieve functional and test coverage. Working with software and system teams to understand where to deliver optimal performance and features. Debugging silicon level functional, timing and power issues during bring up. Location and office reality: the posting names Bangalore, India as the location and mentions a hybrid work environment, though it does not state how many days a week that means. Cerebras publishes India roles under a single India Office label on its board. Honest fit guidance: multiple silicon success is the real filter. If you have taped out more than once and worked on high speed interfaces, eight years is fair. This is one of four Cerebras roles in today's edition spanning manufacturing bring-up at 3 years to test engineering at 10, and several of them are hardware rather than software, which is unusual for this board and genuinely useful if you studied electronics or VLSI.
What the posting asks for: 8 or more years of experience in production cloud infrastructure engineering, systems engineering or core cloud networking roles. 5 or more years of hands-on experience with deep enterprise cloud networking constructs, naming AWS Transit Gateway, VPC peering, AWS Global Accelerator, Direct Connect and GCP networking equivalents. The posting describes the ideal candidate as someone who automates anything done more than once and can rapidly self educate on new network topologies, multi cloud ecosystems and agentic engineering models. The actual day to day: designing next generation traffic entryways using Cloudflare for SaaS, driving migration toward decentralised edge infrastructure, removing legacy hardware routing bottlenecks and shifting compute to edge workers. Building, scaling and maintaining the multi cloud backbone across AWS and GCP, including hub and spoke models using AWS Transit Gateway, Global Accelerator and GCP Network Connectivity Center. Implementing cryptographic controls at scale, enforcing TLS 1.3 externally and mutual TLS mesh architectures internally across Envoy and Nginx proxies. Designing deterministic playbooks and automated telemetry ingestion pipelines using AI models and agents, moving from reactive debugging toward autonomous anomaly detection and self healing. Providing first line technical triage during volumetric and application layer denial of service attacks during India datacentre hours, analysing proxy and VPC flow logs and implementing rapid web application firewall mitigations. Championing infrastructure as code and eliminating configuration drift with Terraform. The posting also describes the role as a key technical anchor in India working with global counterparts to maintain high availability service levels. Location and office reality: Bengaluru, India. The posting does not state office days or describe the role as remote, but it does state that denial of service triage happens during India datacentre hours. Honest fit guidance: this is networking depth, not general SRE. If you have run production traffic across two clouds and understand certificates and proxies at the level of implementing them, eight years is fair. Note the on-call and attack response duty, because it is a real part of the job and the posting does not hide it. Okta has 31 roles already live on our board, and this is a distinct team from the others.
What the posting asks for: 8 or more years of experience in DevOps, platform engineering, site reliability or related roles. Strong hands-on experience with CircleCI or a comparable SaaS CI/CD platform such as GitHub Actions or GitLab CI. A strong understanding of CI/CD design patterns, build systems, release workflows and automation practice. A software engineering background with the ability to write, maintain and review production quality code. Experience with Go, or a willingness to work with Go and AI assisted coding tools day to day. Strong experience with cloud native infrastructure, containers, Kubernetes and infrastructure as code. A solid understanding of CI/CD security concepts including identity and access management, OIDC, secrets management and secure software supply chain practice. Strong communication and the ability to influence technical direction across teams. The actual day to day: supporting and optimising CircleCI and hybrid continuous integration environments including self hosted runners and executors. Working with software engineering and SRE teams to improve build, test and deployment workflows. Developing automation, platform tooling and internal services in Go or similar languages. Implementing CI/CD security practice including secrets management, image signing, policy enforcement and vulnerability scanning. Contributing to platform architecture decisions and engineering standards. Improving build performance, reliability and developer productivity through automation and self service. Mentoring engineers. Location and office reality: Bangalore, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the Go requirement is softened deliberately, since the posting accepts a willingness to work with Go rather than demanding existing depth. That makes this more accessible than the years suggest for a strong DevOps engineer coming from Python. Build and release engineering is a specialism that people often fall into rather than choose, and it transfers well: every company has this problem. SolarWinds has four roles in today's edition from 3 years to this one, all different teams.
What the posting asks for: 10 or more years of professional software engineering experience, including at least 2 years in a staff level role. Strong proficiency in Java or Golang. Experience building platforms, frameworks, libraries or SDKs at scale. A strong understanding of software engineering practice including code quality, testing, CI/CD and observability. Experience with cloud native architectures, containerisation with Docker and orchestration with Kubernetes. Solid experience with SQL and NoSQL databases and caching strategies. A proven ability to lead technical initiatives and influence without direct authority. Familiarity with CI/CD pipelines and modern DevOps practice. An understanding of AI native software development including automated code generation, AI driven testing and human in the loop review systems. A proven ability to adopt and drive modern engineering paradigms, particularly integrating AI into development workflows. Strong communication with non technical stakeholders. Proven leadership experience including mentoring engineers and leading technical initiatives. Good to have: experience with Python and Django, experience building scalable external or partner facing APIs, and experience acting as a technical evangelist through talks, documentation and internal advocacy. The actual day to day: leading design and development of frameworks that support scalable customer facing APIs. Influencing architecture and design across multiple teams and acting as technical advisor and escalation point. Aligning engineering initiatives with business goals. Championing engineering practice across teams. Improving developer productivity through tooling, documentation and onboarding. Mentoring senior engineers. Using generative AI and AI coding tools to accelerate developer productivity and automate repetitive work. Location and office reality: Bengaluru, Karnataka, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the 2 years at staff level inside the 10 is a real requirement and worth addressing directly in an application. Platform work suits people who get satisfaction from other engineers moving faster, which is a genuinely different motivation from shipping user facing features. The posting carries 6sense's recruitment fraud warning: real emails come only from the 6sense.com domain, first contact is never by text, and payment is never requested.
What the posting asks for as minimum qualifications: 10 or more years in a software engineering role or equivalent experience, and 5 or more years specifically in infrastructure engineering. Strong hands-on experience with Amazon Web Services, Kubernetes, and Terraform or Pulumi. A strong understanding of networking covering VPC, routing, DNS and connectivity, and of identity and access management and access control. Experience automating infrastructure workflows and building high availability, scalable systems. Proficiency in Python, Go or Bash. Preferred: experience with multi region or multi account architectures, automating infrastructure migrations and upgrades with EKS upgrades named as the example, and secrets management platforms such as HashiCorp Vault. Familiarity with policy as code such as Open Policy Agent, and observability systems including Prometheus, Grafana and Datadog. Exposure to data infrastructure including Hadoop, Trino and Spark, and to service mesh such as Istio. The actual day to day: architecting, building and scaling core infrastructure systems. Automating the infrastructure lifecycle to minimise human intervention. Designing secure connectivity across services, VPCs, accounts and regions. Debugging and resolving complex production issues across the stack. Writing production quality code, tools and frameworks. Working with engineering teams to standardise how infrastructure is used. Location and office reality: Bengaluru, Karnataka, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the two experience numbers matter, 10 years overall and 5 in infrastructure specifically, so a decade of application development with light infrastructure exposure will not clear it. The data infrastructure and service mesh items are preferences rather than requirements. This is one of four 6sense roles in today's edition, all different teams, and the company publishes a recruitment fraud warning: real emails come only from the 6sense.com domain and payment is never requested.
What the posting asks for: a Bachelor's or Master's degree in engineering in computer science, electrical engineering, AI, data science or a related field. 10 or more years of experience testing in one of these areas: enterprise software, distributed systems, or datacentre hardware and software. Experience working in large enterprise or cloud networking infrastructure including high speed switches, routers and firewalls. Experience qualifying networking vendor platforms such as Juniper, Arista or Cisco, and network test equipment such as Ixia or Spirent. Experience with datacentre technology including BGP, ECN and PFC. Experience testing networking security, compliance and firewalls. Strong coding skills in one of Python, Golang or C and C++. Strong debugging skills for large distributed systems, hardware and software, with gdb, strace and network monitors named. A strong understanding of operating system internals including memory management, file system behaviour, security basics and performance. A strong understanding of datacentre layout and device performance characteristics across PCIe, networking and storage. Listed as a huge plus rather than required: experience with cloud technologies including AWS, Kubernetes and Docker, and monitoring tools such as Grafana and Prometheus. An understanding of machine learning model training and inference. An understanding of ML hardware accelerators including GPUs and custom accelerator ASICs. Location and office reality: Cerebras publishes its India roles under a single India Office label. This posting does not state office days. Honest fit guidance: this is a test engineering role at a level and depth that most SDET postings never reach, and the networking requirement is the real gate. If you have qualified switching and routing platforms and driven Ixia or Spirent, ten years is the stated floor. If your test experience is web and mobile automation, this is a different discipline despite the shared job title, and the interview will establish that quickly.
What the posting asks for: a Bachelor's or Master's degree in Computer Science, Engineering or a related field. 12 or more years of experience in software engineering with significant focus on system architecture and design. Proven experience designing and evolving large scale, distributed, cloud based systems, with a deep understanding of distributed systems, scalability and fault tolerance, microservices and event driven architectures, and API design, data modelling and integration patterns. Strong experience with cloud platforms such as AWS, Azure or GCP. The ability to influence without authority and drive alignment across teams. Excellent communication with both technical and non technical stakeholders. Preferred: experience in data intensive, AI and ML or big data platforms. A strong understanding of DevOps, CI/CD, infrastructure as code and cloud cost optimisation. Familiarity with Docker and Kubernetes. Prior experience as a Principal Architect, Staff Architect or equivalent. Experience in fast scaling SaaS or enterprise platforms. The actual day to day: owning overall system architecture across multiple domains for scalability, reliability, security and performance. Defining the long term architectural vision and technical roadmap. Designing and reviewing high level system designs, data flows, integration patterns and technology choices. Acting as technical authority on complex architectural decisions and design reviews. Partnering with principal engineers, engineering managers and product managers. Establishing architecture standards and best practice. Identifying architectural risks and driving mitigation. Providing reference architectures and design frameworks, which the posting explicitly distinguishes from day to day coding ownership. Driving adoption of microservices, event driven systems, cloud native patterns and data platforms. Evaluating emerging technologies. Supporting performance optimisation, resiliency and cost work. Taking part in architecture councils. Contributing to hiring and mentoring senior engineers. What the posting says success looks like: clear scalable architecture supporting rapid product growth, alignment between engineering execution and architectural vision, and reduced technical debt with improved reliability over time. Location and office reality: Bengaluru, Karnataka, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the not-day-to-day-coding line is the most useful sentence in the posting. If you want to keep writing production code, this is not the seat, and 6sense has a Staff Software Engineer role in today's edition that is. If you want to shape systems across teams and are comfortable that influence is your main tool, this is a well described version of that job.
What the posting asks for: 12 or more years of progressive experience in software engineering with a strong foundation in systems design, cloud architecture and developer tooling. Strong programming in Go, which is preferred, or Python, with the posting stressing you should be comfortable owning production grade services, command line tools and automation pipelines rather than only scripts. Expert level experience designing and operating large scale, high traffic, multi tenant Kubernetes environments on AWS EKS, including networking, storage and security layers. Broad hands-on experience across the AWS ecosystem, with an emphasis on building software that integrates with and extends cloud services. Experience implementing and maintaining observability stacks such as Prometheus, Grafana, VictoriaMetrics or Thanos, ideally by owning the tooling around them. A proven track record in cost optimisation, balancing cluster topology and platform architecture against efficiency goals. A history of measurable platform outcomes, with reducing developer onboarding time given as an example. The actual day to day: working with the architecture team to scope, size and execute large platform initiatives, and serving as primary technical authority and escalation point for the India engineering team. Writing production quality Go or Python for internal tooling, automation frameworks, bots and self service developer platforms. Foreseeing architectural bottlenecks and designing for future scale. Mentoring junior and senior engineers. Driving infrastructure as code practice with Terraform and Crossplane toward a Kubernetes native model. Responding to service failures across AWS, EKS, Linux and ArgoCD, leading blameless root cause analysis and implementing fixes that prevent recurrence. Owning the transition from legacy pipelines to GitHub Actions workflows, custom actions and self hosted runner infrastructure. Location and office reality: Bengaluru, India. The posting does not state office days for this role. Honest fit guidance: this is a platform engineering role that genuinely expects software engineering, not a senior operations title. The Go preference plus multi tenant EKS at scale is the combination that will decide applications. Mentorship is described as a large part of the job, framed as being a multiplier, so it suits someone who wants influence without moving into management.
What the posting asks for: a Bachelor's or Master's degree in Computer Science, Information Technology or a related field. 15 or more years of software engineering experience with significant experience architecting large scale distributed systems. A strong understanding of data structures, algorithms and design patterns. Proven transformational leadership in technology migrations or strategies. Expertise in Java and cloud native ecosystems. Experience with AI and ML at scale and managing AWS multi region deployments. Expert level proficiency in Java or similar languages. Hands-on experience with Docker, Kubernetes and CI/CD automation. Knowledge of high performance SQL, NoSQL and vector databases. An understanding of enterprise grade security and compliance. Soft skills the posting names: the ability to influence without authority and gain buy-in for technical shifts, business acumen connecting technical decisions to financial outcomes, skill in navigating complex technical debates and building consensus, and a passion for building a thriving engineering organisation. The actual day to day: defining long term architectural vision and governance for the platform. Identifying systemic technical risks and leading task forces to resolve architectural bottlenecks. Developing internal tools and SDKs that simplify infrastructure and improve developer productivity. Conducting deep dive troubleshooting on complex production issues. Promoting AI native engineering practice and integrating AI features into the platform. Leading development of core platform libraries and high risk prototypes. Taking part in the Architectural Guild and reviewing high impact design documents. Mentoring lead and senior engineers and representing Appian in the technical community. Ensuring operational resilience through self healing and highly available systems. Location and office reality: Chennai, India. The posting does not state office days or describe the role as remote. Honest fit guidance: this is an individual contributor role at a level where many companies would offer management instead, which is worth knowing if you want to stay technical. Appian has six roles in today's edition ranging from 3 years to this one, and they are separate requisitions on different teams rather than one job reposted. Note that only the Senior Software Engineer role in that set mentions a preference for a premier institution background; this one does not.
What the posting asks for: 15 or more years of software development in Java, preferably with significant experience in Hibernate and Spring Boot. A deep understanding of design patterns, scalability patterns, security engineering and object oriented principles. 4 or more years of experience automating and deploying large scale production services in AWS, GCP or similar. A deep understanding of infrastructure level technologies including caching, stream processing and resilient architectures. Experience with relational databases, ideally MySQL, PostgreSQL or a graph database. Strong communication across functions and distributed teams. Experience leading and mentoring junior engineers. A B.E. in Computer Science or equivalent. Nice to have: experience with server side technologies including caching, asynchronous processing and multi threading. Experience with security best practice and threat modelling. Knowledge of identity and access management protocols including OAuth, OpenID Connect, SAML and SCIM. The actual 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 with a focus on scalability, performance and security. Working with product managers, architects and other engineering teams to define technical strategy and lead prototyping of software components. Directly overseeing and coordinating complex technical initiatives involving more than 20 engineers and ensuring alignment across sub teams. Driving a culture of engineering excellence with robust testing, monitoring and operational excellence. Keeping current with industry trends in identity, security and distributed systems. Partnering with product development, QA and site reliability engineering on scoping. Location and office reality: Bengaluru, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the identity protocol knowledge is listed as nice to have rather than required, so a strong Java architect from another domain is not ruled out. The 20 plus engineer coordination line is the one to think about honestly: it is technical leadership without formal authority, which some people find the best of both worlds and others find the worst. Okta has 31 roles already live on our board, and this is a distinct team.
What the posting asks for: 18 or more years of software development experience, with at least 8 years setting technical direction and architecting large scale enterprise software with a primary focus on the macOS and iOS ecosystem. Expert level proficiency in Swift and Objective-C, AppKit and SwiftUI for user interface work, iOS and macOS internals, system extensions and OSQuery. A strong complementary understanding of the Android platform. A proven track record architecting and delivering large scale enterprise or consumer products, primarily on the Apple platform. Comfort leading cross functional and cross organisational alignment on complex technical strategies and setting best practice for other engineering teams. The actual day to day: defining the long term technical vision and architectural roadmap for Okta's mobile products, including Okta Verify, FastPass, Device Assurance and public SDKs. Providing technical guidance and mentorship to senior engineers across teams. Leading architectural review and decision making for foundational components and core platform initiatives. Working with product management, security and other engineering leaders to translate high level requirements into architectural designs. Evaluating new architectural approaches, tools and platforms in the mobile space. Contributing high level technical designs, architectural proposals and documentation. Overseeing and taking part in critical code reviews for adherence to architecture, security and performance standards. The posting places the role within Okta's Workforce Identity Cloud engineering organisation and describes a high degree of technical responsibility, ownership and strategic impact. Location and office reality: Bengaluru, India. The posting does not state office days or describe the role as remote. Honest fit guidance: the two numbers are both real, 18 years total and 8 of them setting technical direction on Apple platforms, so this is a narrow search. If you have architected macOS software specifically, and not only iOS apps, you are in a small pool: the posting's emphasis on system extensions and macOS internals points at desktop security software rather than consumer app development. Note that this is an architecture seat rather than an engineering management line, which is the distinction worth confirming early if you are choosing between tracks.
What the posting asks for: this posting states no years of experience requirement anywhere, and no formal degree requirement either. What it does specify is the work and the tools. The actual day to day: developing, maintaining and extending test frameworks and infrastructure including system level regression and smoke tests. Developing automated tests, identifying when and where tests should be written, and implementing performance test plans. Building custom testing applications in languages such as Java or Python using tools including WebDriver, Locust, BrowserStack, Appium, Selenium Grid and Postman. Developing automation that minimises fragility through architectural patterns that isolate coupling to the system under test. Developing and executing test automation for mobile use cases and offline functionality. Assessing the impact of changes across the codebase through code reviews. Explaining features clearly including intent, impact and value, with working knowledge of at least one Appian subsystem preferred. Being proficient with an IDE, build processes, Git, Jira and continuous integration. Breaking features into story tickets, identifying edge cases and technical risk, and troubleshooting defects to a single module. Distinguishing test error from application error. Contributing to technical documents, challenging decisions with healthy debate, and maintaining a high quality standard. Understanding priorities, surfacing blockers quickly and completing work with minimal prompting. What the company says about joining: department specific training during onboarding, a mentorship scheme and a First Friend programme for new hires, internal training through Appian University, tuition reimbursement, and eight employee led affinity groups. Location and office reality: Chennai, India. The posting does not state office days or describe the role as remote. Honest fit guidance: because no years figure is published, this role will not appear under any experience filter on this page, and we would rather say that than invent a number. Judge it by the tool list instead. If you have built a test framework rather than only written tests inside someone else's, you are the target, and that is a skill people often acquire in three or four years. Appian has six roles in today's edition at different levels, and this is the only one aimed at test engineering.
What the posting asks for: deep hands-on expertise building production grade software in Go, Java or Python, with a proven ability to deliver robust, maintainable code in a Linux based environment. A strong commitment to quality, evidenced by experience owning both the development of complex features and the creation of comprehensive test automation frameworks. A technical foundation in distributed systems or container orchestration such as Kubernetes, with the desire to work on enterprise storage mobility and provisioning problems. The posting publishes no years of experience requirement anywhere, and no degree requirement. The actual day to day: architecting, developing and delivering scalable features across Kubernetes including OpenShift, OpenStack and Nutanix stacks for FlashArray and FlashBlade, so that virtualised platforms get enterprise grade storage performance. Owning the full lifecycle of your features from design and implementation through writing rigorous test automation, for reliability on mission critical production workloads. Partnering with engineering teams across geographies on design reviews, troubleshooting complex distributed system problems, and improving engineering practice, code quality and test coverage. Location and office reality: Bangalore, India. This employer states in a related posting that it is primarily an in-office environment and expects attendance at the office in line with company policy unless you are on leave or travelling for work. This posting includes that clause with the office location left as an unfilled placeholder in the published text, so confirm which site and how many days before you accept. Honest fit guidance: with no years published, this role appears in no experience filter on this page, and we will not invent a figure to fix that. Read the requirements instead: production Go, Java or Python plus Kubernetes internals is a mid to senior profile in practice. Storage systems work is a genuine specialism with a long shelf life, and this posting is one of the more clearly written examples of it in today's edition.
What the posting asks for: extensive expertise building scalable data pipelines, optimising ingestion workflows and managing complex data transformations in enterprise business to business environments. Advanced technical proficiency with SQL, Snowflake architectures, dbt and REST API design, combined with deep database management and query performance optimisation skills. A proven ability to manage complex data integration, data quality frameworks and enterprise data governance practice tailored to go to market operations. A track record of translating technical challenges into clear business solutions while working across highly technical and non technical business units in an agile environment. The posting publishes no years of experience requirement and no degree requirement. The actual day to day: designing, developing and scaling high throughput data ingestion and transformation pipelines within the customer data platform so marketing and sales environments have real time access to data. Building and managing data integration processes and REST API workflows with external data vendors, and optimising synchronisation rules. Authoring and executing technical frameworks that improve the health of core data domains including account hierarchies, firmographics and contact records, and embedding marketing requirements into enterprise master data management strategy. Partnering with IT, business intelligence and product engineering teams to design data flows that unify customer touchpoints. Who you report to: the posting states this role reports to the senior customer data platform leader within marketing technology and data strategy. Location and office reality: Bangalore, India. This employer describes itself elsewhere as primarily an in-office environment, so confirm the expected office days. Honest fit guidance: with no years figure published, this role sits in no experience filter on this page, and we have written none rather than guessing. The honest trade here is domain: the engineering is real data engineering with a modern stack, but the stakeholders are revenue operations, and career paths from this seat lean toward marketing technology and analytics engineering rather than product infrastructure. If that suits you, the Snowflake and dbt experience is highly portable. If you want to build data platforms for a product, note the difference before applying.
What the posting asks for, organised as it publishes them. Cloud and infrastructure: deep AWS expertise across networking, compute, identity and access management, scaling and security. Strong experience managing infrastructure with Terraform at scale. Kubernetes and platform engineering: very strong Kubernetes fundamentals covering internals, scheduling, networking and storage. Hands-on experience operating Amazon EKS in production. Experience troubleshooting complex multi layer Kubernetes issues. Coding and automation: the ability to write clean, maintainable, production quality code in Go or Python, and a strong automation mindset aimed at eliminating toil through code. CI/CD and GitOps: proven experience building and operating CI/CD pipelines, with hands-on experience of GitHub Actions or integrations, and ArgoCD and GitOps based deployment workflows. Observability and reliability: a strong understanding of metrics, logs, traces and alerting. Hands-on experience with Datadog or similar for infrastructure and Kubernetes monitoring, application performance monitoring, alerting, dashboards and incident detection. Experience defining and using service level indicators and objectives to drive reliability decisions, and turning observability data into operational improvements. The posting publishes no years of experience requirement anywhere and no degree requirement. What you would own: end to end ownership of highly available, scalable AWS infrastructure. Design, operation and continuous improvement of Kubernetes platforms on EKS. Production reliability through observability, automation and service level objectives. CI/CD systems enabling safe, fast, repeatable deployment. Infrastructure defined and enforced through Terraform and GitOps. Incident response, root cause analysis and long term remediation. Raising operational standards through automation and documentation. Location and office reality: the job board lists Hybrid, India. The posting body does not name a city or state how many days a week are in office, so ask which office you would be attached to. Honest fit guidance: no years figure means this role appears in no experience filter on this page. Judge it on the requirement list, which is demanding: EKS in production plus Terraform at scale plus Go or Python is a genuinely senior profile. Socure also has a Golang backend role in today's edition at 5 to 7 years, which is a different team.
What the posting asks for: strong knowledge of Zuora SaaS billing, usage and subscriptions, product and pricing configuration, and cash application and revenue processes integrated with upstream usage systems and downstream systems. The ability to understand and manage Twilio's entire invoice to cash landscape in partnership with global accounting and billing teams. The ability to conduct design workshops with the business and build a prototype for demonstration before development starts. The posting also describes the person it wants as a self starter with a solid analytical mindset, excellent interpersonal communication, diligent time management, team orientation and a strong work ethic, able to work under pressure against overlapping deadlines. It states you should be able to mentor a couple of junior consultants. The posting publishes no years of experience requirement anywhere. The actual day to day: leading end to end architecture and complex product catalogue design within Zuora Billing, including charge models, subscription lifecycle management and scalable order to cash and order to revenue design aligned to finance processes. Driving advanced Zuora configuration including custom workflows covering automation, integrations and error handling, mediation and data transformation pipelines, advanced billing rules, custom rating logic, multi entity and multi currency global setups, custom reports and data sources, and billing performance optimisation. Designing, building and supporting integrations between Zuora and enterprise systems including Oracle ERP, tax engines, payment gateways, CRM and data platforms. Gathering requirements, designing, configuring, developing, testing and maintaining Zuora billing. Location and office reality, and this is the important part: the posting states the role will be remote and based in India, and then names the eligible states as Karnataka, Tamil Nadu, Telangana, Maharashtra and Delhi. That is a genuine restriction, not boilerplate. Twilio describes itself as remote first but adds that you may be asked to attend in person on an ad hoc basis for team gatherings, offsites or customer meetings. The posting also discloses that Twilio uses AI to help make its hiring process efficient, while stating that every hiring decision is made by a person. Honest fit guidance: no years figure is published, so this role appears in no experience filter on this page and we have not guessed one. This is enterprise applications work, closer to finance systems engineering than to product development, and Zuora experience specifically is the thing that will get you shortlisted. If you have it, the remote arrangement makes this one of the more valuable roles in today's list for anyone who cannot relocate and lives in one of those five states.
What the posting asks for as minimum qualifications: hands-on experience in threat hunting, incident response, security operations, malware analysis or network defence. Practical experience using SIEM tools such as Splunk, Microsoft Sentinel or ElasticSearch. Deep familiarity with the MITRE ATT&CK framework and modern tactics, techniques and procedures. A proven ability to analyse adversary behaviour and malware campaigns and translate findings into detection logic, supported by a Bachelor's or graduate degree in Computer Science, Engineering or equivalent security experience. A foundational understanding of AI and ML technologies and experience using, securing or positioning AI driven solutions within your domain. Preferred: experience using AI and ML models, large language models or natural language processing to automate threat intelligence synthesis, accelerate hunt hypothesis generation or streamline analysis of large scale telemetry. Significant experience as a senior threat hunter leading complex investigations. No years of experience figure appears anywhere in this posting. The actual day to day: analysing emerging threats, adversarial behaviours and techniques to understand attacker methodology and improve detection. Conducting proactive and retroactive threat hunting using Zscaler telemetry and behavioural methods. Researching, analysing, validating and documenting threat hunting findings. Independently hunting and responding to customers while managing flexible operational schedules and on-call support. Identifying and translating adversary behaviour into actionable hunt hypotheses and detection logic. Location and office reality: Pune, India. The posting mentions flexible operational schedules and on-call support, so hours will not always be standard. Note that Zscaler published a separate senior threat research role in an earlier edition of this list that required weekend night shifts; this posting does not repeat that requirement, so ask rather than assume either way. Honest fit guidance: with no years published, this role appears in no experience filter on this page, and we have written none rather than inferring one from the Staff in the title. The requirement list points at a genuinely experienced hunter, since it asks for detection engineering output rather than alert triage. If your background is SOC analysis and you want to move into research, this is the kind of role worth stretching for.
What the posting asks for: 3 to 7 years of experience in cybersecurity, threat intelligence, security operations, customer success, technical account management, security consulting or security operations. A strong understanding of security incidents and business risk. The ability to communicate with both analysts and CISOs. Strong written and verbal communication. Curiosity to investigate and understand threats. An ownership mindset. The ability to use AI tools responsibly to improve investigation, summarisation and reporting. The subject areas the posting says you should have interest or experience across: threat intelligence, dark web and deep web threats, credential leaks and stealer logs, brand impersonation, data leaks, infrastructure vulnerabilities, attack surface exposures, cloud and internet facing risks, AI security risks, and third party and vendor risks. The actual day to day, in three parts as the posting sets them out. Owning customer threat outcomes: reviewing threat intelligence findings for assigned accounts, identifying high priority incidents, explaining business impact, sharing critical updates with CISOs and security teams, and following up until there is action or closure. Conducting weekly incident triage: reviewing critical and high severity incidents with analysts, prioritising on customer context and business impact, preparing customer ready summaries, and tracking what was reported, acknowledged and actioned. Acting as a security consultant: understanding the customer environment, asking the right questions, investigating with analysts, simplifying complex threats, connecting findings to business risk and advising on next actions. The posting names its main success metric as the number of incidents successfully triaged and reported to customers. Location and office reality: Bengaluru, Karnataka, India. The posting does not state office days or describe the role as remote. Honest fit guidance: a reader asked this list specifically for technical account management and customer success roles, and this is one of them. The unusually wide 3 to 7 year band and the acceptance of customer success or SOC backgrounds make it genuinely accessible from more than one direction. If you are a SOC analyst who is better at explaining findings than most, this is a realistic move that keeps the technical content.
What the posting asks for: 5 or more years of experience in a technical support, technical account management, consulting, solutions engineering or professional services role within the technology industry. 5 or more years of technical sales, technical account management or other post sales technical experience, ideally with open source technologies or in the observability space. First class written and oral communication to work with remote first internal teams and worldwide customers, including the ability to articulate technical value. The actual day to day: serving as the primary technical point of contact for a portfolio of customers. Designing the observability maturity journey of customers and guiding them along it. Providing expert level troubleshooting and guidance to drive adoption. Conducting regular technical reviews and health checks, and assisting in root cause analysis of issues affecting customer satisfaction and retention. Advising clients on best practice and strategy. Developing and executing technical roadmaps with customers. Identifying opportunities to optimise cost and expand use of the product. Building long term relationships with key stakeholders. Owning the customer lifecycle with support from engagement managers and onboarding solutions architects. Driving adoption across your portfolio. Acting as the voice of the customer internally, shaping product feedback and roadmap priorities with engineering and product management. Location and office reality: this is genuinely remote. The job board lists India (Remote), and the posting states that Grafana Labs is a 100 percent remote company with more than 1,600 team members across over 40 countries, describing itself as remote only. Unlike several remote tagged roles this list has seen, the body supports the tag rather than contradicting it, and no state or city restriction is stated. Honest fit guidance: this is post sales, which the posting says plainly, so it is a customer facing role rather than an engineering seat. It suits someone with real systems depth who prefers breadth across many environments to depth in one codebase. Grafana Labs also adds that you may not meet every requirement and encourages applying anyway. For readers who have said remote is what makes a job possible rather than a perk, this is one of four genuinely remote roles in today's edition.
What the posting asks for: 10 or more years of experience in a senior customer facing technical role such as Field Architect, Solutions Architect, Sales Engineer, Systems Engineer or Technical Consultant. Experience with public cloud and hybrid cloud environments including AWS, Azure, GCP, OCI or private cloud platforms. Deep technical curiosity, hands-on architecture skills and strong communication. The actual day to day, as the posting groups it. Technical leadership and architecture: leading technical discovery with customers and partners to understand business goals, application requirements, data architecture, infrastructure constraints and success criteria, then defining scalable architectures that map to them. Defining and validating architectures for AI and ML training and inference, analytics platforms, data lakehouse environments, high performance data pipelines, large object workloads and modern application data services. Serving as subject matter expert in object storage, S3 compatible architectures, distributed systems, metadata, replication, erasure coding, security, performance tuning and large scale namespace design. Customer engagement and advisory: building trusted relationships with infrastructure, platform, analytics, AI, security, application and operations stakeholders, and guiding architecture decisions. Leading technical evaluations, system configuration, performance testing, interoperability validation and proof of value engagements. Partnering with customer engineering, product management and engineering to move customers from evaluation to production and on to broader adoption. Ecosystem and enablement: providing technical leadership on Kubernetes, containers, automation and cloud native deployment patterns across hybrid cloud, private cloud, public cloud and edge infrastructure. Location and office reality: the job board lists this as Remote, Bangalore, India. The posting body does not restate the remote arrangement or name office days, and field roles of this kind usually involve customer travel even when the base is remote, so confirm both. Honest fit guidance: this is a pre and post sales architecture role, so it is customer facing by design, but the technical bar is real: erasure coding and namespace design are not talking points you can pick up in a week. If you have been a solutions architect or systems engineer in storage, data or infrastructure for a decade, this is a strong fit. If you want to write product code, it is not.
What the posting asks for as minimum qualifications: 15 or more years of experience as a Sales Engineer or systems integrator. Hands-on experience installing, configuring and managing routers, switches and network security technologies. A Bachelor's degree or an equivalent combination of education and professional experience. A foundational understanding of AI and ML technologies and experience using, securing or positioning AI driven solutions within your domain. Preferred: experience demonstrating or architecting enterprise cloud security platforms using AI powered threat prevention, automated anomaly detection or predictive data defence. Proficiency with group policy, Active Directory and LDAP, and single sign on and SAML protocols. A deep understanding of HTTP and web security technologies including proxies and firewalls, and direct experience managing macOS, UNIX and Linux, and Windows systems. The actual day to day: providing technical thought leadership and advice to enterprise customers on transforming their digital experience. Taking total ownership of the technical sale and the associated processes. Identifying and qualifying technical opportunities while developing and maintaining trusted advisor relationships with key customer stakeholders. Delivering sales pitches, technical presentations and whiteboard sessions to support successful deployments. Location and office reality: Mumbai, India. The posting carries a hybrid tag in its metadata but does not state how many days a week that means, so ask. Honest fit guidance: this is a sales engineering role and we list it as customer facing rather than pretending otherwise. It is included because the requirement list demands genuine hands-on network and security depth rather than only commercial skill, which is the line this list has drawn consistently: technical customer facing roles are in scope, purely sales framed ones are not. If you are a network or security engineer who enjoys the customer conversation, 15 years of practice is what this asks for. Zscaler has 50 roles already live on our board across engineering and customer facing teams.
Added August 8, 2026
Required - 4 to 6 years of experience. The posting states this directly as Experience Required: 4 to 6 Years. - Strong hands on experience with Informatica and SQL programming. - Experience with cloud based data platforms and modern data engineering tools. - Good analytical and problem solving skills. - Strong communication and collaboration abilities. Key skills named in the posting - Informatica - SQL - Python - PySpark SQL - Databricks - Azure Data Factory (ADF) - Azure Data Lake Storage (ADLS) - Airflow (listed as good to have) - dbt (listed as good to have) The day to day - Designing, developing and maintaining ETL workflows using Informatica. - Building and optimising data pipelines using Databricks, ADF and ADLS. - Working on SQL, Python and PySpark based data transformation processes. - Collaborating with cross functional teams to gather and understand data requirements. - Troubleshooting, performance tuning and optimisation of ETL jobs and SQL queries. - Supporting deployment, testing and validation for data solutions. - Ensuring data accuracy, integrity and timely delivery. Location and working style Bengaluru, Karnataka. No remote arrangement is stated. A note on the application The posting includes a consent line stating that by submitting your application you agree to be contacted by the talent acquisition team via phone, email, SMS, WhatsApp or other channels. Worth knowing before you apply if you are careful about which channels recruiters use. Honest fit guidance The Informatica requirement is the deciding factor. It is an established enterprise ETL tool, and if you have worked with it the rest of this list is a natural extension. If you have only done cloud native data engineering with Spark and dbt and have never touched Informatica, the requirement is stated as strong hands on experience, so treat it as a real gate. This is a services company, which shapes the work: you build for clients rather than for one internal product, projects change, and exposure is broad but sometimes shallower than product engineering. Many engineers use exactly this to build range early, then move into product roles. Sigmoid has three roles in this edition at different levels: this one at 4 to 6 years, a DataOps Lead at 8 to 12 and a BI Solution Architect with no published years.
Required - 5+ years of QE experience, preferably at an enterprise SaaS company. - 3+ years of experience in quality engineering for enterprise level software. - 5+ years of experience in Python or Java based automation development. - Familiarity with Selenium, TestCafe, Postman, JMeter, Locust, Splunk, AWS and Kubernetes. - Expertise in test planning and cross team collaboration. - Experience working with distributed systems at large scale. - Able to write and review designs and code with other team members. - Able to deliver well designed, high quality code on time. - Experience with non HTTP based protocols: SSH, RDP, TLS, LDAP and similar. - Experience with networking: IP addressing, routing, firewalls. Preferred - Performance testing experience, which the posting describes as a huge plus. The day to day Quality engineering for Okta's identity platform: designing and building automation, planning test coverage across teams, and working at the protocol and network level rather than only through a browser. The requirement to review designs and code with other engineers indicates a role embedded in the engineering team rather than a separate QA function. Location and working style Bengaluru, India, tagged hybrid. Okta describes an immersive in person onboarding experience at the start of employment, and recent Okta postings on this board have specified two days on site per week plus travel to the Bengaluru office during the first week. Confirm both at the first screen. Honest fit guidance Read the protocol and networking requirements carefully, because they are what make this role different and they are where applications will fall down. Plenty of automation engineers have five years of Selenium and Python. Far fewer have debugged an LDAP bind or reasoned about TLS handshakes and firewall rules, and that is precisely the gap Okta is hiring into. If you have that background, this is a strong role: staff level, protocol depth, large scale distributed systems, and an explicit expectation that you write real code. If you do not, be honest about the distance. It is learnable, but the posting lists it as a requirement rather than a nice to have, so a targeted application that shows relevant networking or security exposure will do more than a generic automation CV. Okta has four roles in this edition at levels from 3+ years to 7+, across web platform, internal IT, quality engineering and security.
Required - BS in Computer Science, a related field, or equivalent industry experience. - 5+ years of experience in backend software development or automation using Node.js, Python or similar. - Strong experience with AWS services, especially Lambda, S3, SQS and SNS, EventBridge and DynamoDB. - Expertise in database design, schema modelling and query optimisation. DynamoDB and Snowflake preferred. - Strong grasp of integration design patterns, secure API development (REST and SOAP) and system interoperability. - Ability to develop and maintain GitLab based CI/CD pipelines for tests, linting and deployment. - Experience managing infrastructure as code with Terraform or CloudFormation. - Demonstrated experience building and maintaining integrations with Salesforce, NetSuite, Workday, Coupa, Stripe and Snowflake. Preferred - Familiarity with data validation, schema evolution and cross system reconciliation. The day to day - Designing, building and maintaining backend integrations using AWS serverless services. - Developing API based automations and orchestrating data flows between major SaaS platforms. - Refactoring legacy integration logic toward modern architecture standards. - Owning code from design through CI/CD and deployment. - Collaborating with US based engineers on shared initiatives, sprint planning, code reviews and technical handoffs. - Participating in a shared production support rotation, resolving critical integration and data pipeline issues. - Partnering with architects and business systems analysts on integration design and testing strategy. - Supporting both ETL style batch pipelines and real time event streaming using CDC and platform events. Location and working style Bangalore, India. The job title itself says Hybrid in Bangalore. Note a contradiction worth knowing about: the posting also carries an #LI-Remote tag in its metadata, which conflicts with the Hybrid in Bangalore text in the title. The specific statement in the title is the one to trust, and this is listed here as a Bangalore based hybrid role. Ask at the first screen if remote matters to you, because the tag is not a commitment. The posting also mentions collaboration with US based engineers, which usually implies some overlap with US hours. Worth confirming how much. Honest fit guidance Do not let Business Systems Engineer in the title mislead you in either direction. The requirements are backend engineering: serverless architecture, event driven systems, infrastructure as code and database design. But the domain is enterprise system integration, so you will spend your time on Salesforce, NetSuite and Workday data rather than on a customer facing product. For a backend engineer who enjoys distributed systems and event driven design and does not mind that the consumers are internal, this is a solid five year level role with a modern AWS stack. The production support rotation is real and should factor into your decision.
Required - 5+ years of hands on experience in Technical Support, or in data recovery and backup and recovery solutions, with a focus on one or more cloud platforms such as Azure, AWS or GCP. - Strong understanding of technology and cybersecurity basics, computer networking fundamentals, OSI layers and OSI layer protocols, Active Directory and DNS basics, TCP and UDP. - Hands on configuration and troubleshooting level knowledge of networking, storage systems, hypervisors and container solutions such as VMware, Hyper-V, Nutanix AHV, Kubernetes, OpenStack and OpenShift. - Cloud platforms such as Azure and AWS, with SaaS, PaaS and IaaS infrastructure exposure. - Databases including MSSQL, MySQL, Oracle, SAP, PostgreSQL and MongoDB. - Prior customer facing experience demonstrating, delivering a pilot or POC, and running technical demos of cybersecurity solutions, with strong interpersonal skills. - Excellent written and spoken English, and the ability to build and present PowerPoint decks. Good to have - Proficiency onboarding CRM applications such as Salesforce or D365. - Hands on exposure to Commvault, Rubrik, Veeam, Cohesity, Dell, NetApp or Pure Storage technologies. - Industry certifications in cloud (AWS, Azure) and AI. - Additional spoken languages such as French, German or Spanish. The working hours, stated by the employer The posting says that for AMER Centre of Excellence hires, prior experience with US based customers is preferred and flexibility to work in permanent night shifts is expected. The role title itself carries US Shift. This is a permanent night shift, not occasional on call, and it should be the first thing you weigh. The day to day Remotely supporting Sales Engineering Managers and Sales Engineers in the US market on pre sales engagements, focused on proofs of concept and demos, plus documentation, RFI and RFP responses, discovery, requirement gathering and technical research. Location and working style Bangalore, India, working US hours. A note on recruitment fraud Commvault opens its postings with a warning that it never conducts interviews by email or text message and never asks for banking details or identity documents before your first day. That scam targets exactly this audience, so it is repeated here. Honest fit guidance The night shift is the decision. Everything else about this role is attractive for an infrastructure generalist: broad technology exposure, customer facing skills that raise your ceiling, and a five year bar that is reachable. But permanent US hours reshape your life, and no amount of career upside changes that. Decide on the shift first and the technology second. If the hours do not work, Commvault has a Senior Sales Engineer role in Mumbai in this same edition at 8+ years with no night shift requirement stated.
Required - 5+ years of experience in quality engineering, test engineering or a closely related role, with substantial individual contributor experience on large scale distributed systems or cloud infrastructure. - The ability to reason through the full stack: client SDK, API, gateway, inference software, driver and hardware, well enough to debug from any layer. - Genuine self direction. The posting states you will frequently work without complete product specifications and must decide under ambiguity. - Clear written communication and effectiveness across timezones in an async first setting. The day to day - Release quality ownership: driving weekly cloud release qualification end to end, reading every PR in the release branch, understanding what changed, deciding where the risk is and designing qualification that exercises it. Being the final voice before a release ships. - Test infrastructure at scale: building and evolving functional, integration, performance and fault testing for the Inference Cloud platform, designed for twenty times growth in coverage, environments and traffic. - Code review with intent: reading developer PRs with real understanding of what each change does and its blast radius, then testing actual impact rather than surface area. - Automation expansion: continuously increasing coverage, fixing flaky tests rather than tolerating them, and using AI tooling to accelerate. Location and working style Listed as India Office. A sibling Cerebras posting names Bengaluru and another states hybrid working is possible, so confirm the office and on site expectation at the first screen. The async first, cross timezone description suggests meaningful overlap with United States teams; ask what hours that implies. Honest fit guidance This is a quality role for someone who thinks like an engineer, and the posting is refreshingly honest that it wants pushback rather than compliance. The line about being the final voice before a release ships means real authority and real accountability. If you have been frustrated by QA roles that are a downstream gate, this is the opposite of that. The flip side is that it is demanding. Weekly releases, no complete specifications, deciding under ambiguity and reading every PR in a release branch is a heavy load, and the full stack requirement down to driver and hardware is unusual for a test engineer. Five years is the stated bar, but the substantial individual contributor experience on distributed systems clause is doing real work in that sentence. Applications that show ownership rather than execution will land better.
Required - 5+ years of software engineering experience building large scale backend applications and distributed systems. Highly desirable - Experience with data pipelines, aggregations and large scale data processing, since many platform capabilities depend on transforming and serving data at scale. The day to day - Designing, building and maintaining core platform services that support multiple product and feature teams. - Developing highly scalable, reliable and fault tolerant backend systems for large workloads. - Architecting distributed services, APIs and foundational frameworks that enable rapid feature development across the organisation. - Building and optimising systems for high throughput data ingestion, aggregation, processing and retrieval. - Driving improvements in platform performance, reliability, observability and operational excellence. - Working with Product, Data and Engineering teams to define and deliver platform capabilities. - Contributing to technical architecture, engineering standards and long term platform strategy. - Mentoring engineers and taking part in design and code reviews. - Investigating and resolving complex production issues. Location and working style Bengaluru, Karnataka, India. No remote arrangement is stated for this particular role, although 6sense does list a separate security engineering role in this edition as India, Remote, so remote working exists at the company for some teams. Honest fit guidance This is a platform engineering role rather than a feature engineering one, and the difference matters. Your customers are other engineering teams, your work is judged on whether it lets them move faster, and the satisfaction comes from leverage rather than from shipping something a user can see. If you like designing the layer everyone else builds on, that is a good trade. The requirement list is short and honest: 5+ years of backend and distributed systems. There is no long list of named technologies to disqualify yourself against, which means the interview will test depth in fundamentals such as system design, concurrency, data modelling and failure handling. Prepare accordingly. 6sense has three roles in this edition: this one at 5+ years, a remote security engineering role at 5+, and a staff data engineering role at 10+. They are different teams.
Required - 5+ years of experience being part of a Security Operations or similar team. - 3+ years of experience developing automation. - 2+ years of experience conducting adversary emulation exercises. The day to day - Executing milestones for end to end SecOps and threat initiatives against the security roadmap. - Identifying and responding to complex security incidents including system compromise, intrusion attempts and denial of service, through continuous monitoring, vulnerability assessment and log analysis. - Engaging vendors and the Infrastructure, IT, GRC, Cloud and Application Security teams to validate alerts, resolve incidents and perform root cause analysis. - Researching emerging threats, disclosed vulnerabilities and attack vectors, and pushing mitigating controls into products and services. - Performing security forensics. - Building security tools and advanced automation so the security team operates at speed and scale. - Proposing, planning, leading and executing threat exercises based on security trends, advisories and academic research. - Mentoring engineers across information security to drive controls and risk remediation. - Communicating risk and mitigation to audiences with different levels of sensitivity. How the role is measured, per the posting Maintaining current knowledge of the product and architecture, preparing for weekly one to ones and monthly skip levels, taking part in the Security Operations on call rotation, mitigating exposures, driving incidents to closure within SLAs, and maintaining handbook pages, runbooks, workflows and dashboards, with weekly project status updates. Location and working style India, Remote. This is one of only three remote roles in this edition, and the only remote security role. Note the on call rotation: remote does not mean unstructured here, and incident response work carries real out of hours weight. Honest fit guidance The three part experience requirement is more specific than most security postings and it is worth reading as a whole. Five years in security operations is the base, but the three years of automation development and two years of adversary emulation are what separate this from a monitoring role. If you have run a SOC queue but never written tooling or run purple team exercises, expect that gap to come up. The mentoring line asks you to mentor engineers across information security, not to manage them, which is consistent with a staff level individual contributor role. For readers who have asked repeatedly for remote roles: this is a real one, stated in the location field rather than implied by a tag. Confirm at the first screen whether remote means anywhere in India.
Required - 5 to 8 years of experience in AI or machine learning, SaaS, or workflow automation. - A proven track record of working successfully with enterprise customers. - Strong foundational understanding of customer journeys and core business processes. - Technical familiarity with APIs, system integrations and complex enterprise software architectures. - Exceptional communication skills, with the ability to bridge technical engineers and business stakeholders. The day to day - Customer journey and workflow design: mapping end to end journeys across sales, support and operations, identifying high impact automation opportunities and designing agent driven workflows across systems and teams. - Solution architecture: designing agentic AI systems including orchestration, APIs and integrations, and combining large language models, rules and enterprise systems into scalable architectures. - Business value articulation: translating solutions into measurable outcomes such as cost reduction and conversion uplift, and supporting deal teams with return on investment narratives. - Proof of concept and deployment: leading POC engagements with clear success metrics and ensuring they convert to production deployments. - Stakeholder engagement: working with both business and technical stakeholders, and handling scepticism arising from prior enterprise AI failures. - Reusable playbooks: building repeatable solution frameworks across industries and enabling sales teams with structured use cases. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance Compare this against Paytm's other presales posting in this edition before applying. The Presales Manager role at 3 to 6 years publishes a hard requirement for a Bachelor's degree from a named Tier 1 institution. This Solution Architect posting, at 5 to 8 years, publishes no such requirement. If the institute line ruled you out of the other one, this is the door that is still open. The role is genuinely architectural rather than presentational. Designing agent orchestration, integration patterns and production paths is engineering thinking, even though the seat sits beside sales. The measure of success stated in the posting is POC conversion to production, which is a fair thing to be judged on and a hard thing to achieve. The scepticism line deserves attention. Many Indian enterprises have already run AI pilots that went nowhere. Being able to speak honestly about what agentic systems cannot yet do will serve you better in this job than enthusiasm.
Required - 6 to 9 years of experience in software engineering. - Bachelor's or Master's degree in Computer Science, Engineering or a related field. - Proven experience leading development of distributed systems, cloud native applications or large scale platforms. - Deep proficiency in programming languages, development frameworks and cloud infrastructure, with AWS, GCP and Kubernetes named. - Strong problem solving, architecture design and technical mentoring skills. - Excellent communication, collaboration and leadership capabilities. The day to day - Leading end to end technical execution for major projects, from design through deployment and monitoring. - Developing and enforcing engineering standards, coding practices and architectural guidelines across teams. - Working with product, UX and architecture teams to define scalable technical solutions. - Mentoring engineers at various levels and supporting development through code reviews and knowledge sharing. - Investigating production issues and leading root cause analysis and long term fixes. - Championing innovation, system improvements and performance optimisation. On scope and supervision, as published Tekion sets these out as separate fields. Job complexity: leads projects with cross functional dependencies and significant technical complexity, guides technical strategy and drives execution. Required supervision: functions independently and provides technical leadership to multiple engineers, accountable for design decisions and engineering quality. Expertise: strong technical depth in system architecture, application development and software design. Read together, this is a hands on lead. Technical leadership of multiple engineers is stated, direct reports are not. Location and working style Chennai Regional Office. Most engineering roles in this edition are in Bengaluru, so a genuine Chennai posting at this level is worth flagging. Application note The posting states that, effective 4 August 2026, current Tekion employees should apply through the internal job board in Ashby rather than externally. Honest fit guidance The 6 to 9 year band with a Lead title is a common point of confusion, so be clear: this is the individual contributor track. If you want to move into people management, this posting does not offer it. If you want to stay technical and take on architectural ownership, it does exactly that. Tekion has published a large number of near identical engineering requisitions across recent weeks at different levels, so read the specific posting rather than assuming from the title, and check which team and product area you would join before the interview.
Required - 7+ years of development experience designing and implementing software systems in Java, building highly reliable and mission critical software. - 3+ years of work experience designing and implementing security solutions for applications and distributed systems. The day to day - Acting as a liaison between the engineering and security organisations to develop requirements for the security roadmap. - Evangelising security best practices across the engineering organisation. - Researching, designing, implementing and owning security oriented frameworks and features with the goal of protecting Okta's customers. - Routinely participating in cross vertical code reviews with an emphasis on security. - Breaking down complex problems into sub tasks, prototyping rapidly and iteratively using agile practices. - Coaching and mentoring junior engineers on the team. Location and working style Bengaluru, India, tagged hybrid. Okta describes an immersive in person onboarding experience at the start of employment, and recent Okta postings on this board have specified two days on site per week and travel to the Bengaluru office during the first week. Confirm both at the first screen. Honest fit guidance The split in the requirements is the thing to focus on. Seven years of Java is the base, and three years of applied security design is the differentiator. Application security engineers who have not done deep Java, and Java engineers who have never designed a security control, both sit slightly outside the stated bar. If you have both, there are not many roles that ask for exactly that combination. The liaison and evangelism responsibilities mean a meaningful share of the job is persuading other engineers, writing things down and reviewing other people's code. Some engineers find that the most valuable work they do; others find it draining compared with building. Ask in the interview what the split looks like across a typical quarter. Working on identity means the security work is genuinely consequential: the failure mode is somebody else's authentication. That raises both the interest and the pressure. Okta has four roles in this edition, from a 3+ year AEM engineering role up to this one at 7+.
Required - A strong engineering background with 7+ years of experience in backend or infrastructure engineering. - Proficiency in one or more of Go, Python, Node, Rust or C++. - Comfort working across APIs, SDKs, distributed systems and cloud infrastructure. - Experience building or integrating developer platforms or real time systems. - Ability to quickly understand complex systems and debug issues in real world environments. - Strong communication, collaborating directly with customer engineering teams and internal product teams. - Comfort in fast paced, low process environments where ownership and initiative matter. - Genuine interest in hands on customer work solving complex implementation challenges. Nice to have - Experience with WebRTC, real time media systems or telephony. The day to day - Working directly with customer engineering teams, remotely or on site when necessary, to design and implement real time applications on LiveKit. - Designing scalable architectures for voice AI, real time media and developer platform use cases. - Building prototype integrations, reference implementations and sample applications. - Helping customers navigate SDKs, APIs, infrastructure and deployment strategies for production systems. - Debugging and troubleshooting complex technical issues in production. - Leading technical workshops and architecture sessions with developers and product teams. - Translating customer needs into insights that inform product and platform direction. - Partnering with Product and Engineering on developer experience, documentation and tooling. - Contributing code, examples or improvements to LiveKit's open source ecosystem. Location and working style Remote, India. The posting notes on site work with customers when necessary, so expect some travel. This is one of three remote roles in this edition and the only one that is primarily backend engineering. Honest fit guidance Be clear about what forward deployed means before you apply. You are an engineer, you write code, and the requirement list is a backend engineer's list. But your working day is shaped by customer problems, their timelines and their codebases, not by an internal sprint board. Engineers who want to own a product surface for years will find that frustrating. Engineers who like variety, debugging unfamiliar systems and being the person who makes it actually work will find it excellent. The domain is a genuine advantage. Real time media and voice AI is where a lot of current product energy sits, and WebRTC expertise is scarce and well paid. The posting lists it as nice to have rather than required, so this is a realistic way in for a strong backend engineer without that specific background. Note the low process description honestly: LiveKit is a small company, and that means less structure than a large employer.
Required - 7 to 10 years of overall experience, with a minimum of 2 years of experience as a Sales Engineer. That split is stated in the posting and it matters: the sales engineering portion required is small relative to the total. The day to day - Providing technical thought leadership and advice to enterprise customers on transforming their digital experience. - Taking total ownership of the technical sale and associated processes. - Identifying and qualifying technical opportunities while developing and maintaining trusted advisor relationships with key customer stakeholders. - Delivering sales pitches, technical presentations and whiteboard sessions, and helping ensure deployments succeed. Reporting and team The posting places this role in the SE India department, reporting to the Senior Manager, Sales Engineering, and describes joining a global group working on cloud security. Location and working style Mumbai, India, described in the posting as a hybrid role and tagged #LI-Hybrid. Zscaler points to its published hybrid working model. Confirm the number of office days at the first screen. Honest fit guidance The two year sales engineering minimum inside a seven to ten year total is the most useful line in this posting. If you have spent most of a decade in network or security infrastructure and only a couple of years in a customer facing technical role, you are inside the stated requirement even though the title reads senior. That is a genuinely open door for engineers who have discovered they enjoy the customer conversation more than the console. Understand the trade honestly. Sales engineering pays well and often carries variable compensation tied to the region's number, which means your income depends partly on outcomes you influence but do not control. Your technical depth stays useful but stops growing in the way it would in a build role. Zscaler has three roles in this edition and they are very different: this one, an internal end user computing engineering role in Bangalore, and a threat researcher in Pune with weekend night shift requirements.
Required - 7 to 10+ years of sales engineering experience, or customer facing consulting experience, with large enterprise clients, preferably in a software or data centre environment. - Technical leadership and subject matter expertise across distributed architectures, file systems and competitive storage offerings in the SAN product space. - The drive the posting describes as a need for success. The day to day - Providing technical leadership and direction to customers and internal staff in developing integrated technology solutions supporting pre sales activity. - Assisting in the analysis, design and development of integrated technology solutions. - Acting as technical expert and consultant, proposing solutions that meet customers' technology and business requirements. - Making technical and sales presentations to customers' technical staff and senior management. - Serving as a trusted technology advisor and an internal resource on technical issues within the assigned market segment. - Building relationships with the account team, partners and customers, and marshalling corporate resources appropriately. - Leading technical sales calls. - Qualifying opportunities in terms of technical requirements, competition, decision making process and funding. Commercial framing, stated in the posting The role is described as accountable for regional revenue goals through driving technical programmes and overseeing day to day account level activity. That is unusually direct for a pre sales listing and you should factor it into how the role will be measured. Location and working style Mumbai, India. No remote arrangement is stated. Link verification note, published for transparency Rubrik's careers site returns an automated blocking response to direct link checks, so this posting could not be confirmed by opening the apply URL in the usual way. It was instead confirmed live through the applicant tracking system's own interface, which returned the posting with a matching title and location on the morning of publication. Every other role in this edition was confirmed by a direct successful request. Honest fit guidance This is the most commercially framed of the customer facing roles in today's list, and that is neither good nor bad, it is simply what you should know before applying. Revenue accountability is stated up front rather than buried. The technical bar is genuinely high and specific: distributed architectures, file systems and SAN storage competitive knowledge. Generic SaaS pre sales experience will not substitute. If you come from storage, backup or data centre infrastructure, that specialism is exactly what is being paid for. Commvault has a comparable Senior Sales Engineer role in Mumbai in this same edition at 8+ years, in the same competitive space. Worth comparing both.
Required - BS, BE, B.Tech, MS or M.Tech in Electrical Engineering, Electronics and Communication Engineering, Computer Science, or equivalent work experience. - 7 to 10+ years of industry experience. - 3 to 5 years of experience in pre silicon and post silicon ASIC hardware. - Good understanding of computer architecture and networking. - Excellent coding in languages such as Python, Verilog, SystemVerilog and C. - Proficiency in hardware and software co design and layered architectures. - Excellent debugging, analytical and problem solving skills. - Proficiency in large scale testing and automation using pytest and Python. - Good presentation skills, able to refine diverse information and put forward optimisation strategies. The day to day - Developing and debugging flows that embed well tested, deployable optimisations into production processes to reduce time and cost on Wafer Scale Engines. - Refining AI systems across hardware and software design constraints such as di/dt, voltage and frequency characterisation space, and current and temperature limits, in relation to performance optimisation. - Developing and enhancing infrastructure that enables silicon for real world workload testing. - Developing self checking metrics and instrumentation for debug and coverage. - Working with silicon architects and designers, performance engineers and software engineers to improve Wafer Scale Engine performance. - Working across software, design, verification, emulation and validation. - Working with CI/CD tooling, git, GitHub, GitHub Actions or Jenkins, and merge and release flows. Location and working style Listed as India Office. Sibling Cerebras postings name Bengaluru and mention hybrid working, so confirm the location and on site expectation at the first screen. Honest fit guidance Note the two part experience requirement, because the second part is the real filter. Seven to ten or more years of industry experience is the headline, but the specific ask is three to five years of pre silicon and post silicon ASIC hardware work. General embedded or firmware experience is not the same thing. This is one of the strongest roles on this board for electronics and VLSI graduates who have built a career in silicon and assumed the AI boom had nothing to offer them. It has: the hardware is the product. The physical constraints named in the posting, di/dt and thermal and voltage frequency characterisation, tell you how close to the metal this sits. If those terms are familiar, you are the audience. If they are not, one of the other Cerebras roles in this edition may fit better, including an ML Research Engineer role open at 1 to 3 years.
Required - 5+ years in data protection or cloud experience. - A minimum of 8+ years of experience serving in a pre sales systems engineer role. Read those two lines together: the pre sales systems engineering requirement is the higher of the two at eight years, which is why this role is grouped at 8+ here. The day to day - Working as part of the account team to produce territory plans, account strategies and sales plans, engaging specialist resources as determined by the Sales and SE Manager, and developing new opportunities in the assigned territory. - Anticipating technology trends and building relationships with partners and internal departments including sales, support, business units, product management, marketing and development. - Calling on senior IT leadership, often without the account executive present, to qualify and understand the technical, financial, operational and business issues Commvault products can address. - Building relationships with technical decision makers in end user accounts and driving detailed, executable technical account plans. - Driving or supporting complex sales opportunities by translating business requirements into technical requirements, coordinating technical expertise, sizing and scoping, defining delivery and deployment approach, timeline and resources, coordinating demonstrations and proofs of concept, and supporting internal deal acceptance. On the wording in the posting The description says the senior sales engineer should be a team leader who mentors, teaches and contributes to overall success. Nothing in the posting establishes direct reports, and the responsibilities are individual contributor pre sales work throughout, which is how it is grouped here. Location and working style Mumbai, India. Tagged hybrid in the posting. A note on recruitment fraud Commvault opens its postings with a warning that it never conducts interviews by email or text message and never asks for banking details or identity documents before your first day. Repeated here because that scam targets this audience directly. Honest fit guidance Eight years of pre sales systems engineering is a firm bar and this is a senior seat, so treat the requirement as literal rather than aspirational. The data protection and cyber resilience specialism is the thing that transfers. Rubrik has a comparable Senior Sales Engineer role in Mumbai in this same edition at 7 to 10+ years, competing in the same space. If you are in this market you are probably a candidate for both, and it is worth comparing the two on team, territory and compensation structure rather than on the job description alone. Commvault also has an Inside Sales Engineer role in Bengaluru in this edition at 5+ years, but note that one is a permanent night shift supporting United States customers.
Required - 8+ years of experience designing and building enterprise scale SaaS applications using Microsoft technologies. - 5+ years of experience building highly available, massively scalable, distributed cloud services on AWS or Azure. - Strong system design, analytical thinking and problem solving skills, with the ability to own complex technical problems. The day to day - Owning end to end development and technical success of one or more product modules. - Designing, building and evolving highly scalable SaaS applications using .NET and C#, REST APIs, SQL and NoSQL, and Flutter or React, capable of supporting two to four times annual business growth. - Working closely with product managers, designers and other engineers to deliver customer centric features in an agile environment. - Owning the complete software lifecycle: design, implementation, code reviews, testing, deployment, monitoring and continuous improvement. - Using modern AI assisted development tools such as Claude Code and Cursor throughout the work, and building engineering assets including prompts, workflows, templates and automation that improve productivity across the wider engineering team. Location and working style Hyderabad, Telangana, India. No remote arrangement is stated. About the company, for context on scale Zenoti reports passing a one billion dollar valuation, an eighty million dollar investment from TPG, and customers including European Wax Center, Hand and Stone, Massage Heights, Hair Cuttery and TONI&GUY. The product is vertical SaaS: deep software for one industry rather than general purpose tooling. Honest fit guidance The Microsoft stack requirement is the deciding factor. Eight years on .NET and C# is specific, and engineers from Java or Python backgrounds will find this a harder sell than the generic Lead Engineer title suggests. If .NET is your background, the combination of eight years of enterprise SaaS with five years of distributed cloud services is a coherent and reachable profile. Lead here means technical ownership of modules, not people management. The responsibilities are all build and own, with no reporting line mentioned. The AI tooling expectation is worth taking seriously rather than treating as decoration. The posting asks you to build reusable prompts, workflows and automation for the wider engineering team, which suggests it will come up in the interview. Having a real opinion about where these tools help and where they do not will serve you well. Vertical SaaS is a genuine career consideration: you learn one industry deeply, which makes you valuable inside it and less obviously portable outside it.
Required - 8 to 12 years track record of relevant work experience, with a Computer Science or related technical discipline required. - Proven track record of building and shipping large scale engineering products, or knowledge of cloud infrastructure such as GCP or AWS, described as preferred. - Experience in Shell, Python or another scripting language. The day to day - Designing, managing and deploying highly scalable and fault tolerant distributed components using big data technologies. - Evaluating and choosing technology stacks that fit a client's data strategy and constraints. - Driving automation and large scale deployments, and driving good engineering practice from the bottom up. - Developing CI/CD, monitoring and support practices inside the team. - Writing scripts to automate devops processes and reduce team effort. - Supporting terabyte scale pipelines and performing root cause analysis for production errors. - Supporting developers in day to day devops operations, and designing the roster and escalation matrix for the team. - Interfacing daily with Fortune 500 customers to understand strategic requirements, connecting regularly with VP and director level clients, and travelling to client locations. - Providing technical leadership day to day, guiding devops engineers on design, automation and support tasks. - Playing a key role in hiring technical talent, and running training on the technology stack. On the scope, stated plainly This posting mixes hands on engineering with team direction. It asks you to design the on call roster and escalation matrix, guide other engineers day to day, take part in hiring and run training. It also says explicitly that you must be able to be both a leader and a hands on doer. There is no reporting line stated, so it reads as a senior technical lead rather than a people manager, but go into the interview with a direct question about whether anyone reports to you, because the boundary here is thinner than in most postings on this list. Location and working style Bengaluru, Karnataka. Travel to client locations is part of the role. No remote arrangement is stated. Honest fit guidance This is a services company role and that shapes everything. You work on client platforms rather than one product, priorities shift with engagements, and client contact is a core skill rather than an occasional demand. Engineers who like variety and are comfortable in front of senior stakeholders do very well in this environment. Engineers who want to own one system for years generally do not. The client travel and the VP level contact are stated up front, so factor both into the decision. Sigmoid has three roles in this edition: an Informatica Developer at 4 to 6 years, this one at 8 to 12, and a BI Solution Architect with no published years figure.
Required - A Bachelor's degree in Computer Science or equivalent, with 8 to 11 years of hands on experience in database management and optimisation across relational databases, with PostgreSQL as the primary skill set. - Expertise in one or more relational database management systems. - In depth knowledge of database security principles and compliance requirements. - Advanced skills in monitoring and optimising database performance. - Proven experience managing complex database projects. - Effective collaboration with cross functional teams, and experience engaging vendors. The day to day - Using deep expertise in database management and optimisation to ensure high performance and reliability of data systems. - Identifying bottlenecks and performance issues in data pipelines, and optimising query performance, data access and overall processing. - Designing, deploying and managing complex data systems in cloud environments such as AWS, Azure or GCP using tools including Terraform, following the AWS Well Architected Framework. - Developing complex automation using tools such as Jenkins and scripting to streamline data operations. - Architecting and managing enterprise high availability and disaster recovery solutions for business continuity. - Ensuring adherence to cloud security best practice and compliance standards. - Managing complex incidents, troubleshooting and implementing solutions to maintain data integrity and system reliability. - Mentoring junior team members and fostering a collaborative team environment. On the title The posting is titled Lead or Manager, Data Reliability Engineering, and the opening line says the role is accountable for designing, deploying and managing complex cloud based data systems. The management language throughout attaches to systems, projects and incidents. People appear once, as mentoring and guiding junior team members. No direct reports are stated. Ask about this specifically at the first screen, because the title genuinely is ambiguous. Location and working style Hyderabad. Zeta describes itself as an engineering first organisation with more than seventeen hundred people across India, the United States, EMEA and Asia. No remote arrangement is stated. Honest fit guidance PostgreSQL as the primary skill set is the clearest signal in this posting. If your depth is MySQL, Oracle or SQL Server and you have only touched Postgres occasionally, the eight to eleven year band means they are expecting real specialist knowledge: query planning, replication, tuning and failure behaviour. Fintech infrastructure carries compliance weight and genuine consequences when something breaks. The disaster recovery and high availability responsibilities are not theoretical here. For readers who asked for backend and data roles, this is one of the strongest on the list: it is database engineering at depth, not analytics work wearing an engineering title.
Required - 8 to 10+ years working at the intersection of design and frontend engineering. The posting states your portfolio must show both sides of the craft, so a code only or design only portfolio is unlikely to clear the first screen. - Production level proficiency in React, TypeScript and CSS. The posting says you can write code that ships but can also produce a quick experiment or demo. - Deep Figma fluency: component architecture, variables, auto layout and Dev Mode. - Hands on experience building and maintaining a design system in a product company. - Strong command of motion, micro interactions and visual polish. - Comfort using AI coding tools such as Cursor, Claude Code and v0 as part of everyday workflow. - Solid understanding of accessibility (WCAG), responsive and mobile design, and performance trade offs. - Clear communication of design and technical trade offs to varied audiences. The day to day - Building high fidelity interactive prototypes covering motion, data states and edge cases for web and mobile. - Using AI coding tools to accelerate prototype velocity without sacrificing craft. - Owning and evolving the UI component library, maintaining parity between Figma components and production front end code. - Defining and governing design tokens, theming and accessibility standards across the design system. - Participating in design reviews and giving implementation aware feedback early. - Exploring emerging UI patterns and AI native UX paradigms. - Creating proofs of concept that push what is possible in the product experience. - Raising the design team's technical capability by sharing learnings. Location and working style Pune, Maharashtra. No remote arrangement is stated. Honest fit guidance Design engineer is still a rare title in India, and this posting is a good example of what it actually means: you are an engineer, you write React and TypeScript that ships, but your remit is the design system and the quality of the interface rather than product features or backend integration. The dual portfolio requirement is the real filter and it is stated explicitly. If you are a frontend engineer who has never owned visual craft, or a designer who prototypes but does not ship production code, the posting says plainly that both are expected. Note where the role sits: the responsibilities describe raising the design team's technical capability, which suggests you are embedded with designers rather than with product engineers. That is a meaningfully different daily experience from a standard frontend seat, and worth asking about. Mindtickle is the only design engineering role in this edition.
Required - 10+ years of professional software development experience. - Experience working in remote or globally distributed teams. - Hands on technical expertise, rapid prototyping ability and the capability to develop innovative solutions as part of an incubation team. The day to day - Architect and deliver: designing, developing and owning end to end implementation of high stakes prototypes and robust, production ready solutions. - Spearheading AI research and development: driving technical direction and working with cross functional teams to experiment with, validate and integrate AI, machine learning and frontier technologies. - Championing engineering excellence: establishing governance for code reviews and driving continuous improvement in engineering standards, mentoring peers to lift code quality. - Influence and evangelism: explaining complex technical concepts, architectural decisions and project velocity to executive stakeholders and engineering peers. - Working in partnership with the Emerging Tech Initiatives tech lead to enable rapid experimentation. Location and remote terms, stated precisely The posting says the role will be remote and based in India, and then names the permitted states: Karnataka, Tamil Nadu, Telangana, Maharashtra and Delhi. That is a real restriction, not a formality. If you live outside those five states you are not eligible as written. Twilio describes itself as a remote first company, while also noting you may be asked to report in person on an ad hoc basis for team gatherings, functional offsites or customer meetings. The employer also discloses that it uses artificial intelligence to help make its hiring process efficient, while stating that every hiring decision is made by a person. Honest fit guidance Tech Lead in the title does not mean management here. The responsibilities are architecture, hands on delivery and mentoring, with no reporting line stated, which is why it sits in the individual contributor group. Understand what incubation work is before you commit to it. Building prototypes that may never ship is intellectually excellent and professionally risky, and success is measured by learning velocity as much as by launches. Engineers who need to see their work in customers' hands should weigh that carefully. The five state restriction is the single most important practical detail. Check it against where you live before anything else. For readers who have asked for remote engineering roles: this is one of three remote listings in this edition, alongside a LiveKit backend role and a 6sense security role.
Required - 10+ years of experience building backend or data intensive systems. The day to day - Leading large scale data systems: designing, building and evolving high throughput batch and streaming pipelines that process billions of records, and owning core datasets that power product features, analytics and machine learning. - Building systems that handle enrichment, deduplication, identity resolution and confidence scoring at scale. - Driving architecture and technical direction: defining long term architecture for foundational data platforms, and leading multi quarter initiatives such as platform migrations, major refactors and new data foundations. - Balancing data correctness, freshness, cost and performance in production. - Ensuring reliability and data quality: owning SLAs and SLOs for freshness, accuracy and completeness, designing data quality frameworks, reconciliation mechanisms and observability, and leading root cause analysis and long term fixes. - Collaborating with Product, Analytics, Data Science, Platform and go to market teams, and acting as technical point of contact for third party data integrations and vendors. - Mentoring senior engineers and influencing technical standards across the organisation, and leading by example in design reviews, operational ownership and incident response. On the level, in the employer's own words The posting opens by calling this a senior individual contributor role for engineers who enjoy owning complex systems end to end and influencing technical direction across teams, and says the problems do not have obvious answers. Mentoring senior engineers is included; managing them is not. Location and working style Bengaluru, Karnataka, India. No remote arrangement is stated for this role, though 6sense lists a separate security engineering role in this edition as India, Remote. Honest fit guidance The requirement is a single line, ten or more years of backend or data intensive systems, which means the interview will carry all the weight. Expect deep system design: how you would handle late arriving data, how you would resolve identity across sources without a shared key, how you would trade freshness against cost, and how you would migrate a platform without breaking downstream consumers. The phrase to take seriously is influencing technical direction across teams. At staff level the job is as much about persuading other engineers and writing durable design documents as it is about code. If you want a role where you mostly build, this may frustrate you. For readers asking for data engineering depth, this is the most substantial data role in this edition.
The working hours, stated by the employer This posting requires working flexible schedules including weekend night shifts to meet global operational demands, and includes on call support. That is stated twice in the description. It is not an occasional expectation and it should be the first thing you weigh. Required - Extensive experience in threat hunting, incident response, security operations, malware analysis or network defence. No specific number of years is published anywhere in this posting, which is why it appears in the years not stated group. - A Bachelor's or graduate degree in Computer Science, Engineering or a related discipline, paired with the ability to work flexible schedules including weekend night shifts. - Strong scripting and automation skills in Python, with advanced analytical reporting and experience authoring IDS or IPS and YARA signatures. - Foundational understanding of AI and machine learning technologies, and experience using them within your domain. Preferred - Experience using machine learning models or large language models to accelerate threat intelligence synthesis, automate pattern recognition across large datasets, or optimise anomaly detection. The day to day - Analysing emerging threats, adversarial behaviours and TTPs to improve detection capability. - Conducting proactive and retroactive threat hunting using Zscaler telemetry and behavioural methodologies. - Researching, analysing, validating and documenting threat hunting findings with high precision. - Responding to customer needs independently while managing flexible operational shifts and on call support. - Identifying detection gaps and working with the wider team to improve security posture. Reporting and team The posting places this in the Zscaler Threat Hunting department, reporting to a Senior Manager, and describes it as a hybrid India role. Location and working style Pune, India, hybrid. Weekend night shifts and on call, as above. Honest fit guidance Because no years figure is published, the practical bar is set by the phrase extensive experience plus the specific skills: YARA and IDS signature authoring, malware analysis and Python automation. Those are not entry level skills, but if you have them and only three or four years of experience, the absence of a stated number works in your favour. It is worth applying and letting them decide. The shift pattern is the real trade. Threat hunting is genuinely interesting work with excellent visibility into live attacks, and Zscaler's telemetry is a rare asset. Weekend night shifts are a significant and ongoing cost. Do not talk yourself past that line because the technical work appeals.
Required - Experience in web and mobile testing across Android and iOS, and device testing methodologies. - Ability to analyse business requirements to determine the test strategy covered by manual testing. - Strong knowledge of Java. - Experience working on automation scripts, and the ability to establish an automation framework. - Experience with Maven, Jenkins and TestNG. - Basic concepts of database testing. - Familiarity with both Linux and Windows environments. - Knowledge of BDD or Cucumber frameworks. - Knowledge of API testing tools. - Knowledge of Jira. - Experience working in agile methodology. Preferred - Experience with Selenium WebDriver. No years figure is published Paytm publishes no experience requirement anywhere in this posting, which is why it sits in the years not stated group. This is worth flagging rather than glossing over: it means the skills list is the entire bar as written, and the Technical Lead title is the only signal of seniority. The day to day Hands on quality engineering for Paytm products across web and mobile: designing test strategy, building and maintaining automation frameworks, and working within an agile delivery process. On the title The posting is titled Technical Lead, QA. Nothing in the description mentions direct reports, team management or hiring. The responsibilities are entirely technical, which is why it is grouped as an individual contributor role here. Confirm at the first screen. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance The absence of a years figure is the most useful thing about this posting for readers earlier in their careers. Most Technical Lead QA roles in India ask for six to eight years. This one asks for a skill list. If you can genuinely establish an automation framework in Java rather than only write tests inside an existing one, that is the capability being described, and it is worth applying even if your years are on the lower side. The framework establishment line is the part that separates this from a mid level automation role. Note that this is a comparatively short job description with no team or product area named. Ask which business line you would support, because Paytm spans payments, lending, commerce and advertising, and the testing problems differ considerably. Paytm has five roles in this edition across engineering, QA, onboarding and presales.
No years figure is published Sigmoid publishes no experience requirement in this posting, which is why it sits in the years not stated group. The only experience line is a reference to having built accelerators in the past. Architect in the title implies seniority, but the employer has not put a number on it. What the posting asks for - Experience building reusable accelerators. - Deep Power BI capability, including Power BI Service and workspace optimisation rather than only dashboard building. - Migration experience from legacy BI platforms: Tableau, Qlik, Cognos, Business Objects, SSRS, MicroStrategy and Excel. - Ability to build utilities using PowerShell, Power Automate, REST APIs and Microsoft Fabric. - Solution architecture for enterprise scale Power BI, optimising DirectQuery, Import, Composite Models and Hybrid Tables. - Governance frameworks and best practice, including row level security. The day to day - BI practice innovation: developing reusable accelerators, optimising Power BI Service and workspaces, and speeding up end to end development. - Leading programmes that migrate thousands of dashboards within a few months, assessing existing reporting environments and defining migration strategy. - Developing migration frameworks, templates and automation utilities, and optimising migrated reports for performance, usability and maintainability while minimising business disruption. - Building and maintaining accelerators: Power Query transformation libraries, deployment automation scripts, report validation and testing frameworks, governance toolkits, metadata documentation generators, performance optimisation checklists, migration accelerators and row level security templates. - Identifying opportunities to automate repetitive BI development work, and exploring Copilot and AI driven features to improve productivity. Location and working style Bengaluru, Karnataka. Sigmoid's other roles mention client interaction and travel to client sites; this posting does not state it explicitly, so ask. No remote arrangement is stated. Honest fit guidance Read this as an automation and tooling role that happens to be in the BI domain. If you are a dashboard developer looking for the next rung, the accelerator and utility building described here is a different skill: PowerShell, REST APIs and framework design. That is the gap to close. The migration workload is the honest picture of the job. Moving thousands of dashboards off legacy platforms is valuable, well paid and repetitive, and the accelerators exist precisely because the work would be unbearable otherwise. Some engineers enjoy the systematisation. Be sure you are one of them. Because no years figure is published, the interview will set the level. Come with concrete examples of tooling you built to make other people's work faster.
No years figure is published CloudSEK states no experience requirement anywhere in this posting, which is why it appears in the years not stated group. Combined with the Associate title, this reads as an early career role. What the posting asks for - Excellent communication skills. - Strong technical skills. - Cybersecurity exposure, listed explicitly as an added advantage rather than a requirement. - Strong customer service skills. - Organisation skills and the ability to work independently. - Ability to multitask and handle multiple customer enquiries at once. - Patience and the ability to stay calm under pressure. - Problem solving skills. - Ability to upsell and cross sell products and services. - Adaptable, detail oriented and organised, with the ability to work with cross functional teams to troubleshoot and resolve complex problems. The day to day - Being the first point of contact for customers and handling all customer enquiries. - Building relationships with customers and ensuring they are satisfied with the products and services. - Assisting customers with issues or problems. - Providing customer support by phone, email and live chat. - Answering questions and providing information about the products. - Making recommendations to customers about products and services. - Recording customer feedback and suggestions. The products you would support CloudSEK XVigil maps a customer's digital assets, identifies threats, enriches them with cyber intelligence and provides workflows to manage and remediate them including takedown support. BeVigil is an attack surface monitoring tool using mobile, web, network and encryption scanners. SVigil identifies software supply chain risks by monitoring software, cloud services and third party dependencies. Location and working style Bengaluru, Karnataka, India. The posting mentions flexible working hours and food and snacks at the office, which implies an office based role. No remote arrangement is stated. Honest fit guidance Two things should be said plainly. First, this is a customer support role, not an engineering or security analyst role. You will be answering enquiries and resolving issues, not hunting threats. Second, the requirement list includes the ability to upsell and cross sell, so there is a commercial element alongside the support work. Neither is a criticism, but both should be clear before you apply, because the cybersecurity framing can make the job sound more technical than the responsibilities describe. What makes it worth listing is the entry point. No years required, cybersecurity knowledge welcome but not required, at a real Indian security product company with named funding and awards. For someone who wants to get into the security industry and is willing to start on the customer side, that is a legitimate route, and product knowledge gained here transfers into solutions and technical account roles later.
Graviton publishes NO years of experience requirement for this role, which is why it is grouped as entry level here. What it asks for instead: Required - A degree in a highly analytical field such as Engineering, Mathematics or Computer Science, from what the posting calls top tier global institutes. - Basic familiarity with Linux and command line tools. - Foundational programming skills in C or C++, plus scripting in Perl, Python or Shell. - Strong problem solving with advanced mathematical and quantitative reasoning. - Clear communication, specifically the ability to explain complex technical ideas. - A strong quantitative mindset and genuine interest in data driven problem solving. Good to have (explicitly optional) - Experience with high frequency trading systems and infrastructure. - Knowledge of market microstructure and HFT strategies. - Familiarity with low latency programming and optimisation techniques. The day to day - Working alongside senior traders to implement and improve automated trading strategies. - Analysing production trades and proposing strategy enhancements from what you find. - Designing monitoring tools that surface problems in live strategies early. - Writing scalable C++ and Python scripts for risk attribution and performance breakdowns. - Building post trade systems that compute statistics across every production strategy. - Building centralised market data analysis tooling across exchanges. - Overseeing deployment and release cycles with a senior trader. Location and working style Gurugram, Haryana. The posting describes cubicle free offices and a non hierarchical culture, and lists fully covered commuting expenses, catered breakfast and lunch, four weeks of annual leave plus market holidays, gym and sports club memberships and an annual international team outing. Nothing in the posting offers remote work. Honest fit guidance Read the institute line carefully before you spend an evening on the application. Graviton is a selective prop shop and this posting names top tier global institutes explicitly, so it is a real filter rather than boilerplate. The compensating fact is the skills bar: no years demanded, and the programming ability asked for is described as foundational rather than expert. If you are a strong CS, maths or engineering graduate who enjoys C++, Linux and probability, this is one of the very few genuinely open doors into quant trading in India. If your background is web or app development with little maths depth, the Quantitative Analyst - Risk posting from the same firm asks for 3+ years and is a closer match.
Graviton publishes NO years of experience requirement here either, and says explicitly that market knowledge is not expected. Required - A degree in a highly analytical field such as Engineering, Mathematics or Computer Science. The posting names IITs. - A quantitative bent of mind. - Working knowledge of Linux or Unix. - Programming experience, preferably in C++ or C. - No prior knowledge of financial markets is needed, but a strong interest in learning about them is required. That sentence is quoted from the posting because it is the whole reason this role is worth an application from outside finance. - A strong work ethic. The day to day - Developing new trading models and improving existing ones on in house platforms. - Using advanced mathematical techniques to model and predict market movements. - Analysing large financial datasets to identify trading opportunities. - Providing real time analytical support to experienced traders. Location and working style Gurugram, Haryana. Same benefits package as the firm's other openings: covered commuting, catered breakfast and lunch, four weeks annual leave plus market holidays, gym and sports memberships, regular social events and an annual international team outing. No remote option is offered. Honest fit guidance Two roles from this firm sit in the entry level group today and they are not the same job. This one is model building and prediction, weighted toward mathematics and research. The Quantitative Analyst role is production facing: monitoring, tooling and release management for strategies already trading. Pick by which half of that appeals, because the interview will go deep on it. The institute filter is real and named. Set against that, the posting asks for zero years and zero finance background, which almost nothing else at this level does. If you have done well in probability, statistics, linear algebra or algorithms and you write C++, you meet the stated bar. Do not self reject on the finance gap: the posting says outright that it is not expected.
Required - 1 to 3 years of experience in software engineering or machine learning in a similar capacity. The posting adds, in the same sentence, that internships count. That is unusual and it is why this role leads the entry level group today. - Machine learning and inference work, with the optimisation focus described in the posting. - Software engineering fundamentals: this is an engineering seat, not a pure research seat. The day to day Inference focused machine learning engineering: getting models to run efficiently on Cerebras hardware, working on model optimisation and the serving path, and evaluating performance. Cerebras designs wafer scale chips, so the work sits unusually close to the hardware for an ML role, and the neighbouring openings on the same board (ML systems performance, post silicon bring up, physical design) show how deep that stack goes. Location and working style The posting lists the India office, and Cerebras states elsewhere on its board that it can work in a hybrid environment. Confirm the exact office and the number of days on site at the first screen, because the listing gives the location as India Office rather than naming a city. Honest fit guidance This is the most accessible genuine engineering role on today's list, and the internships clause is the reason. Treat "1 to 3 years" as the real bar rather than a formality, but do not add imaginary requirements on top of it: the company wrote down that project and internship work counts. Be clear eyed about the domain. This is inference and systems work at an AI chip company, so comfort with performance, profiling and low level thinking will matter more than familiarity with the latest model architectures. If your ML experience is entirely notebooks and fine tuning APIs, expect the interview to push toward engineering fundamentals. Cerebras has five roles on this edition across very different levels, from this one at 1 to 3 years up to a 10+ year full stack ML lead. They are separate teams, not one requisition posted five times, and applying to the level that matches you is worth more than applying to all of them.
Required - A degree in a highly analytical field such as Engineering, Mathematics or Computer Science, from top ranked universities. - 3+ years of experience in Python and Shell or Bash scripting. - Basic knowledge of Linux and shell command line tools. - Basic programming and scripting skills in Python or Shell. - Strong problem solving and analytical skills. - Excellent communication skills. - A strong work ethic. - Mentorship experience guiding junior developers. The day to day - Working as a team with senior traders to operate and improve automated trading strategies. - Analysing production trades and developing ideas to improve those strategies. - Implementing monitoring tools that highlight potential issues in production strategies. - Writing comprehensive, scalable C++ and Python scripts analysing production strategies for risk attribution and performance break ups along various buckets. - Building scalable post trade systems that analyse statistics across all production strategies. - Implementing tools for centralised market data analysis across exchanges. - Managing deployments and the release cycle alongside a senior trader. Location and working style Gurugram, Haryana. Cubicle free offices, non hierarchical culture, covered commuting, catered meals, four weeks annual leave plus market holidays, gym and sports club memberships, and an annual international team outing. No remote option is offered. Honest fit guidance Note the mismatch inside the requirement list, because it works in your favour. The title says Risk and the responsibilities describe C++ and Python analytics over live trading strategies, but the stated experience line asks only for 3+ years of Python and shell scripting plus basic Linux. The C++ appears in the responsibilities rather than the requirements. If you have three years of solid Python data work and can read C++, you are closer to this than the title suggests. The mentorship line is worth reading properly: it asks for experience guiding junior developers, not for managing them. This is an individual contributor seat. If you have less than three years, the other two Graviton postings in today's entry level group state no years requirement at all.
Required - BS in Computer Science or another technical degree, plus 3+ years of related overall technology experience. - Experience in Adobe Experience Manager. The posting marks this one as required. - Core web technologies: XML, HTML5, CSS, and client or server side scripting such as JavaScript, preferably using single page application patterns, plus web services development using RESTful implementations. - Proficiency in Day CQ and Adobe AEM foundational concepts, including core frameworks such as Apache Sling and Apache Felix, a solid understanding of templates, components, dialogs and widgets, and the AEM development and deployment process. - Proficient knowledge of the end to end content lifecycle: web content management, content publishing, deployment and delivery. - Strong understanding of SDLC methodologies (Agile, Scrum). - Highly self directed, able to multi task given incomplete and sometimes conflicting information. Preferred - Understanding of AEM WCM capabilities including Multi Site Manager and Blueprinting, and online marketing components such as advanced targeting, personalisation and multivariate testing. - Understanding of integration patterns and content centric application development using AEM with or without a Portal, Search or Commerce package. - Experience in at least one of Adobe Analytics, Campaign, Commerce, Marketo Engage or Target, or equivalent technologies. The day to day - Leading development and implementation of custom solutions and integrations within Adobe Experience Cloud. - Architecting scalable, high performance systems against business and technical requirements. - Developing and maintaining integrations with internal and third party systems, and optimising existing systems for performance and reliability. - Working with product managers, solution architects and other stakeholders to scope and deliver. - Participating in sprint planning, stand ups and retrospectives. - Providing technical support, troubleshooting defects and performance problems. - Maintaining documentation for design, development process and system configuration. Location and working style Bengaluru, India. The posting carries Okta's hybrid tag. Okta roles on this board have recently specified two days on site per week and in person onboarding in the first week, so confirm both at the first screen. Honest fit guidance Be clear about what this is. It is web platform engineering on Adobe's stack, not work on Okta's identity product, and AEM experience is listed as required rather than preferred. If you have that specific background, the 3+ years bar makes this one of the few senior titled Okta roles a mid level engineer can actually clear. If you have general Java and web experience but have never touched AEM, the required line is a real obstacle and the other Okta openings on today's list will fit better. Okta has four separate roles in this edition across different teams and levels. The titles do not track the years: this one asks 3+ while others on the same board ask 7+.
Required - 3+ years as a ServiceNow Developer with deep expertise in Flow Designer, Script Includes, ACLs and UI Policies. - Hands on implementation experience in at least one core product: ITSM, CSM, ITOM, HR or IRM. - Proficiency managing complex data migrations and building robust integrations with third party systems using REST and SOAP APIs and Transform Maps. - Ability to translate abstract business requirements into technical roadmaps, managing multiple high priority deliverables while keeping systems maintainable and well documented. - Strong interpersonal skills to partner with global stakeholders and give technical reviews that lift the wider development team. The day to day - Leading design and development of workflows, business rules and integrations to automate manual processes. - End to end delivery of enhancements across ITSM, CSM or HR, from Client Scripts through Flow Designer, against global performance and security standards. - Identifying trends through root cause analysis and prioritising preventive action for platform stability. - Participating in a shared on call rotation supporting 24x7 Customer Service Management. - Consulting with cross functional delivery teams on technical designs and conducting code reviews. Location and working style Bengaluru, India. The posting is explicit and worth quoting in substance: Everpure describes itself as primarily an in office environment and expects you to work from the Bengaluru office in line with company policy, except for approved leave or work travel. Treat this as an onsite role, not a hybrid one. Note also the shared on call rotation, which is a real commitment on a 24x7 service. Honest fit guidance This is enterprise platform development, so be honest with yourself about whether that is the career you want. It is not product engineering on the storage systems Everpure sells, and the work is measured by internal process automation rather than customer facing features. In exchange, ServiceNow is a durable and well paid specialisation with demand across most large Indian employers, and 3+ years is a genuinely mid level bar. One note specific to this employer. Everpure titles have repeatedly hidden team lead responsibilities behind individual contributor sounding names on this board, so read any future posting from them by its role summary rather than its title. This particular posting is a clean individual contributor role: it mentions technical mentorship and code reviews, but no reports.
Required - 3+ years of Design Verification experience. - 3+ years of hands on Design Verification experience. The posting states the requirement twice in slightly different words, which is worth knowing so you are not looking for a second, higher figure that is not there. - Verification of complex hardware designs, which at Cerebras means wafer scale AI silicon. The day to day Design verification work on Cerebras processors: building verification environments, writing and running tests against RTL, chasing down failures and proving out functionality ahead of silicon. The neighbouring openings on the same board show the surrounding stack: physical design, post silicon bring up, microarchitecture front end design and manufacturing bring up. Location and working style The posting gives the location as India Office. A sibling Cerebras posting names Bengaluru explicitly and another states you can work in a hybrid environment, so ask which office and how many days on site at the first screen rather than assuming. Honest fit guidance This is one of the few roles on this board aimed squarely at electronics, electrical and VLSI graduates rather than computer science ones, so if that is your degree it deserves a longer look than the software listings around it. SystemVerilog and UVM are the standard toolkit for this discipline; the posting itself does not name them, which is unusual, so expect the interview rather than the advertisement to establish the specifics. The 3+ year bar is real but modest for verification, where many roles start at five. If you have done verification at a semiconductor firm or a design services company in India for three years, you are in band. Cerebras carries five roles in this edition at levels from 1 to 3 years up to 10+. They are different teams. Apply to the one that matches your discipline rather than to all five.
Required - 3+ years of experience in a relevant domain. The posting names those domains explicitly: Computer Architecture, CPU or GPU Performance, Kernel Optimisation, or HPC (high performance computing). - Performance engineering for machine learning systems on Cerebras hardware. The day to day Making machine learning workloads run fast on wafer scale silicon. In practice that means performance analysis and profiling, kernel level optimisation, and reasoning about the interaction between model execution and the underlying architecture. The role sits alongside Cerebras openings in post silicon bring up, design verification and physical design, so the performance work has real hardware underneath it rather than a cloud abstraction. Location and working style Listed as India Office. Cerebras states on a sibling posting that the role can work in a hybrid environment, and another names Bengaluru. Confirm the city and the on site expectation at the first screen. Honest fit guidance This is a genuinely specialised role and the specialisation is the point. If you have spent three years on GPU kernels, CUDA, compiler backends, HPC codes or CPU microarchitecture performance, there are not many employers in India competing for exactly that, and this is one of the more interesting ones. If your background is applied machine learning, training models and running experiments, this is probably not your role even though the title contains ML. The requirement names architecture and kernel optimisation, not modelling. Cerebras has an ML Research Engineer opening at 1 to 3 years on this same edition that is much closer to applied ML work. The posting gives a short requirement list, so expect the interview to establish depth rather than the advertisement. Be ready to talk concretely about a performance problem you diagnosed and what the fix actually changed.
Required - 3+ years of experience building production grade software systems in Java, Scala or Python. Note the phrasing: production grade software systems, not model prototypes. This is an engineering bar first. - Machine learning engineering work at CRED, which operates a large consumer fintech product. The day to day Machine learning engineering on production systems. CRED publishes a deliberately terse job description, so the specifics of team, model domain and stack are not in the advertisement. Its sibling postings in this edition (a data scientist role at 4+ years and a consumer web developer role at 3+) suggest an engineering organisation split along conventional lines, with this seat on the ML systems side. Location and working style Hyderabad. The posting does not state a remote or hybrid arrangement, so assume office based and confirm at the first screen. Honest fit guidance The short description cuts both ways. It means less to prepare from, but it also means the one stated requirement carries all the weight: three years of production software in Java, Scala or Python. If you meet that and have genuine ML exposure, do not let the absence of a long skills list put you off applying. Ask early what the team actually works on. Machine learning at a fintech spans credit risk, fraud detection, recommendation and collections, and those are very different jobs with different regulatory pressure. A posting this brief will not tell you, and it is a fair first question. CRED has two other roles in this edition, a data scientist at 4+ years and a web developer at 3+ years, all in Hyderabad. If you are more analysis than engineering, the data scientist posting is the closer fit.
Required - 3+ years of experience building scalable, consumer facing web applications. - Web development for Prefr, the lending product within the CRED group. The day to day Building and shipping consumer facing web applications at scale. CRED writes short job descriptions and this one is no exception, so the framework, the exact stack and the team shape are not published. What is published is the domain, consumer lending, and the scale expectation implied by consumer facing. Location and working style Hyderabad. No remote or hybrid arrangement is stated in the posting, so assume office based and confirm at the first screen. Honest fit guidance This is one of the few genuinely frontend weighted roles in this edition, and at 3+ years it is reachable. If you have been writing React, TypeScript and CSS for a product company for three years, you meet the stated bar and should apply rather than waiting for a posting that spells out a longer stack list. Because the description is brief, prepare questions rather than answers. Worth asking: which framework, whether the role includes mobile web, how much of the work is new product versus maintaining existing flows, and how the team splits responsibility with design and backend. One thing to be aware of: this posting is for Prefr, a lending business, rather than for the main CRED app. If you assumed you were applying to work on the flagship product, clarify that early, because it changes both the work and the team. CRED has three roles in this edition, all in Hyderabad: this one, a machine learning engineer at 3+ years and a data scientist at 4+ years.
Required - 3 to 5 years of experience as a ServiceNow Developer. - At least 2 of those years with deep focus on SAM (Software Asset Management) and HAM (Hardware Asset Management). This is the specific part of the requirement and it is the part that will decide your application. The day to day Business application development on ServiceNow inside Okta's internal IT organisation, centred on the asset management modules. Expect configuration and custom development against SAM and HAM, integration with the systems that feed asset and licence data, and the reporting that makes it usable. Location and working style Bengaluru, India. Okta postings on this board have specified hybrid working, with recent listings naming two days on site per week and in person onboarding during the first week of employment. Confirm the current arrangement at the first screen. Honest fit guidance The two year SAM and HAM requirement is the real gate here. General ServiceNow experience across ITSM or CSM will not substitute, because asset management has its own data model, discovery integrations and licence compliance logic. If you have that background, this is a well paid specialisation at a large employer and the 3 to 5 year band is honest about the level. If you are a ServiceNow developer without the asset management depth, Everpure has a ServiceNow Developer opening in this same edition at 3+ years that asks for ITSM, CSM, ITOM, HR or IRM instead, which is a wider door. Be clear that this is internal enterprise IT rather than work on Okta's identity products. That is a legitimate and stable career track, but it is a different job from the engineering roles Okta also has open in this edition, and the interview loop will reflect that.
Required - 3 to 6 years of experience in Pre Sales, Solution Consulting, Solutions Engineering, Product Consulting or Enterprise Technology roles. - Strong understanding of APIs, integrations, SaaS platforms, enterprise applications and solution design. - Experience supporting demos, POCs, RFPs, technical workshops and enterprise sales cycles. - Good understanding of APIs, CRM platforms, databases, cloud technologies and enterprise integrations. - Ability to create solution designs, integration workflows, POCs, demos and technical proposals. - Excellent communication and presentation skills, able to engage technical and business stakeholders. - Ability to simplify complex AI and automation concepts for enterprise clients. - Strong analytical and problem solving skills with a consultative approach. - Hands on experience with productivity, CRM and collaboration tools. Education requirement, stated explicitly by the employer - Must have: a Bachelor's degree from a Tier 1 institution. The posting names IITs, SRCC, St. Stephen's, BITS Pilani and NITs. - Preferred: an MBA from a Tier 1 institution, naming IIM Ahmedabad, Bangalore, Calcutta and ISB. This is published as a hard requirement rather than a preference, and it is reproduced here so nobody spends an evening on an application that the employer has already ruled out. It is the single most restrictive line in this edition. The day to day - Partnering with enterprise sales to understand client requirements and map them to Paytm AI solutions. - Running discovery sessions, identifying business challenges and building solution recommendations. - Delivering customised product demos, solution walkthroughs and proofs of concept. - Acting as technical advisor on product, integration, architecture and implementation questions. - Producing solution documents, proposal inputs, RFP responses, technical FAQs and sales enablement assets. - Collaborating with product, engineering, onboarding and business teams on delivery. - Capturing client feedback to improve product capability. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance Read the education line first. Everything else about this role is a normal presales brief at a reasonable 3 to 6 year band, but the institute requirement is written as must have and will decide most applications before the experience is considered. If you clear it, this is a good presales seat: enterprise AI is where the budget is moving, and doing discovery and POC work now builds a scarce skill. If you do not, Paytm has a Client Onboarding role and a Pre Sales AI Solution Architect role in this same edition, and neither publishes an institute requirement.
Required - 2 to 5 years of experience in Client Onboarding, Implementation, Customer Success or Solutions Engineering. - Good understanding of APIs, integrations, CRM systems and enterprise workflows. - Strong project management, problem solving and stakeholder management skills. - Excellent communication and client facing abilities. - Bachelor's degree in Engineering, Business or a related field. Unlike Paytm's presales posting in this same edition, no Tier 1 institution requirement is published here. Preferred - Experience in SaaS, fintech, enterprise technology or AI products. The day to day - Owning client onboarding from sales handover through to go live. - Understanding client workflows, systems and integration requirements. - Coordinating product, engineering and client teams for deployment. - Managing onboarding timelines, milestones and stakeholder communication. - Running client training sessions and driving product adoption. - Tracking onboarding KPIs, client satisfaction and implementation success. - Gathering client feedback to feed product improvement. About the team The posting describes the Inference and Agentic AI group as a cross functional unit spanning engineering, product, data science, business management and sales, owning the full lifecycle of AI solutions from opportunity discovery through deployment and scale. That breadth is a genuine advantage early in a career: you see how an enterprise AI product is actually sold, built and adopted. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance This is a customer facing implementation role, not an engineering role, and you should apply with that clearly in mind. You will not be building the platform. You will be making it work inside somebody else's company, which means integration troubleshooting, timelines and training rather than writing production code. For a reader two or three years into a support, implementation or solutions role, it is a good step up, and the API and integration requirement means technical skill is genuinely used rather than decorative. Paytm has five separate openings in this edition across engineering, QA and customer facing work. They are different teams at different levels, and the customer facing ones vary a lot in how restrictive their education requirements are, so compare before applying.
Required - 4+ years of Salesforce development experience with extensive knowledge of Sales Cloud, Apex, Visualforce, Lightning Web Components and the Force platform. - Understanding of Salesforce design and development best practices, and the ability to apply them to delivering business solutions. - A combination of analytical, technical, business and communication skills. The posting calls this out directly, because the role works across many functions. The day to day - Designing and developing secure, scalable technical solutions on Salesforce. - Analysing business processes and system implementations to identify inefficiencies and critical metrics. - Evaluating existing code and developing plans to reduce technical debt over time. - Working with technical and cross functional business teams to implement enhancements and projects, and to resolve incidents. - Building tools that scale revenue generating operations and improve sales efficiency. Location and working style Bengaluru. The posting states this is a hybrid position requiring 2 days per week in the Bengaluru office, and states plainly that relocation assistance will not be provided for this role. If you are not already in Bengaluru or willing to move at your own cost, that second sentence matters. Elsewhere the posting describes a flexible, employee led remote model and support for remote work where it aligns with operational requirements, which sits awkwardly beside the explicit two days per week line. Treat the two day requirement as the operative one, since it is the role specific statement. Honest fit guidance Salesforce development divides opinion among engineers, so decide honestly which side you are on. It is platform work, constrained by Salesforce's model and release cycle, and you will spend time on business process rather than pure computer science. Against that, it is well paid, in constant demand across India, and unusually portable between employers and industries. This posting is stronger than most Salesforce listings because it names technical debt reduction and architecture as part of the job rather than only feature configuration, and because the internal customer is revenue operations at a company with real scale. If you want Salesforce work with a different flavour, Okta has a Business Application Developer role on ServiceNow in this same edition at 3 to 5 years.
Required - 4+ years in enterprise end user computing, endpoint management or desktop engineering within cloud first environments. The day to day - Deploying, configuring and maintaining corporate managed endpoints across Windows, macOS, BYOD and mobile, in line with Zscaler security baselines, least privilege standards and automated lifecycle workflows. - Executing vulnerability management workflows using CrowdStrike and Zscaler UVM (Avalor), then triaging, prioritising and tracking remediation through Jira, ServiceNow and executive compliance dashboards. - Monitoring system performance and user satisfaction using Zscaler Digital Experience (ZDX) and Omnissa, and implementing self healing policies and proactive automation. - Working complex endpoint issues and security threats, conducting root cause analysis and documenting SOPs and runbooks for support teams. - Contributing to platform upgrades, virtualisation pilots and security tool rollouts across IT Operations, Security and business stakeholders. Reporting and team The posting places this in the IT Digital Employee department, reporting to the Manager, End User Engineering. Location and working style Bangalore, India, described in the posting as hybrid. Zscaler tags the role #LI-Hybrid and points to its published hybrid working model. Confirm the number of office days at the first screen. Honest fit guidance Be clear that this is corporate IT engineering, not work on the Zscaler security product that customers buy. That distinction decides whether this is the right career step for you. It is genuine engineering: automation, vulnerability management and endpoint architecture at global scale, and the Zero Trust framing means the security thinking is real rather than cosmetic. But it is internal IT, and progression runs toward IT engineering leadership rather than product security. The posting is candid that you will balance operational escalations against engineering projects. Ask in the interview roughly how that split lands week to week, because the answer varies enormously between companies and it is the single biggest factor in whether you will enjoy the job. Zscaler has three roles in this edition across very different functions: this one, an enterprise sales engineer in Mumbai and a threat researcher in Pune.
Required - 4+ years of experience in the machine learning domain, with expert level Python skills and deep familiarity with the standard data science toolkit: PyTorch, TensorFlow, XGBoost or LightGBM, Pandas and Scikit-learn. - Proficiency across the end to end ML lifecycle, from building robust pipelines on big data (Spark, SQL, Trino) through deploying and maintaining models in production using MLOps practices. - Hands on experience with ML infrastructure and orchestration tools such as Kubernetes, Docker, Airflow and Argo. - Software and data engineering best practices, applied in partnership with international MLOps and platform teams. The day to day - Developing and maintaining full lifecycle production ML pipelines, and acting as a technical anchor adapting global frameworks to India localised requirements. - Designing and productionising recommendation and classification models integrated directly into merchant facing products. - Identifying and resolving performance bottlenecks in training and inference across memory, latency and throughput. - Owning reusable AI components that form the foundation for scaling generative AI applications. - Partnering with international MLOps and platform departments to adopt internal tooling. Location and working style Bengaluru. Adyen states its position without ambiguity: it is an office first company that values in person collaboration and does not offer remote only roles. Take that at face value. If remote is what you need, this is not the posting for you, and the LiveKit and 6sense roles in this same edition are genuinely remote. Honest fit guidance The phrase to focus on is production ML services, not model research. Adyen wants an engineer who can own pipelines, deployment and performance, and the requirement list is weighted accordingly: MLOps tooling, Kubernetes, Airflow and Spark sit alongside the modelling libraries. If your experience is training models in notebooks and handing them over, this role will stretch you in the infrastructure direction. The India localisation thread is worth asking about. The posting describes adapting global frameworks for India specific requirements, which suggests genuine ownership rather than following a specification written elsewhere, but it also implies coordination with teams in other timezones. Ask how that works in practice. Payments is a demanding domain: high throughput, low tolerance for error and meaningful regulatory weight. That is what makes the engineering interesting.
Required - 4 to 6 years of experience in AI, automation, data science or analytics. - Bachelor's degree in Computer Science Engineering or a related technical field. - Proficiency in Python (Pandas, NumPy, Scikit-learn), able to write scripts for data processing, ELT pipelines, API calls and automation logic. - Strong SQL and data skills: writing queries and working with data structures, joins and aggregations. - Experience using AI to build agents that solve real world use cases, using frameworks or custom tooling. - Hands on experience with automation tools such as n8n, Zapier, Make, Workato or custom built automation. - Strong systems thinking: considering data flow, scalability and downstream impact rather than only the immediate output. - Experience using Claude Code or a similar AI coding assistant to build or configure MCP servers. - Experience integrating third party systems through APIs and webhooks. Preferred - Background in SaaS, particularly working with cross functional teams. The day to day - Building and refining AI agents to automate knowledge retrieval, extract intelligence and support decisions. - Designing and building automation pipelines that eliminate manual, repetitive processes. - Writing Python and SQL to extract, transform and analyse data from internal systems including Salesforce and the data warehouse, including scoring and prioritisation models. - Engaging cross functional teams to understand pain points and translate them into structured problem statements. - Identifying workflow inefficiencies and driving implementation end to end. - Independently scoping, sequencing and delivering technical projects. - Guiding or mentoring junior team members and acting as the go to resource for AI and automation capability across the organisation. On the title The posting says you will be overseeing the AI Center of Excellence and working directly with executive leadership. It describes mentoring junior team members, not managing them, and every technical requirement is hands on. Read this as a senior individual contributor role with organisational visibility, which is how it is grouped here. Location and working style Bangalore. No remote arrangement is stated. Honest fit guidance This is one of the more genuinely modern job descriptions in this edition. If you have been building agent workflows, wiring up MCP servers and automating internal processes, there are still relatively few roles that ask for exactly that, and fewer that put it in writing. The trade off is that it is internal tooling rather than customer facing product. Your users are colleagues, the problems come from stakeholder interviews, and success is measured in friction removed. Some engineers find that unusually satisfying because the feedback loop is short. Others miss shipping to customers. Know which you are. Executive visibility cuts both ways too: high leverage, but the work is shaped by what leadership considers a priority this quarter.
Added August 7, 2026
Zscaler asks for 1 to 3 years of software development experience, and states plainly that equivalent experience through internships, co-ops or substantial project work counts. That wording is why this role sits at the bottom of today's list: it is one of the few postings on the board that tells a recent graduate they are eligible. What you will actually do: build, test and maintain custom Jira Data Center apps, plugins and scripted extensions using Java, Groovy and the Atlassian SDK. Build and maintain integrations between Jira and Confluence, ServiceNow, Slack, CI/CD pipelines and SSO using REST APIs and webhooks. Work directly with business and engineering stakeholders to turn raw requirements into workflows, schemes, permissions, automation rules and reporting. Contribute to the Jira Data Center to Cloud migration through app compatibility assessments, data mapping, migration tooling, dry runs and post migration validation. Support platform operations alongside the team: upgrades, patching, performance tuning and troubleshooting production issues on AWS. Location and office: hybrid, based in Bangalore. Honest fit guidance. Be clear eyed about what this is. The artifact is Zscaler's internal engineering tooling, not the security product, so if your goal is to work on the Zero Trust Exchange itself this is the wrong door. What you get instead is genuine Java and Groovy development, real API integration work, AWS operations exposure and a platform migration to put on a CV, at an experience bar almost nothing else on this board will accept. Zscaler also states it expects candidates to actively use AI tools in their work, and lists that as a minimum qualification rather than a nice to have.
Meesho asks for a Bachelor's or Master's in Computer Science and at least 1 to 3 years of professional experience, plus 1+ years each with big data systems (Kafka, Spark or EMR, Hive or Impala, Delta Lake, Presto, Airflow), hands on implementation and performance tuning of Spark, Delta Lake or Presto at terabyte scale, and building streaming solutions with Flink, Spark Streaming or Samza. You need to have written code in at least one of Java, Scala or Python and to understand the AWS big data stack. Nice to have: contributor or committer history on the big data stack, data modelling and end to end pipelining, OLAP cubes and BI tools, working knowledge of ELK, Redis and MySQL, and RxJava, Java Spring Boot and microservices. Location: Bangalore. ⚠️ Read the responsibilities section with care, because it contradicts the experience bar. Under About the role the posting says you will oversee your entire team's work, plan long term strategies for junior engineers, monitor project progress and provide management mentorship. That language cannot be describing a 1 to 3 year job, and it reads as copy paste from a more senior template, which Meesho has left in place. The requirement list underneath it is unambiguously an individual contributor data engineering list. We have published it at the stated 1 to 3 years and flagged the contradiction rather than quietly picking one. If the split matters to you, ask on the first call which version of the role is being hired. Honest fit guidance: this suits someone who has already touched Spark or Kafka in a first job or a serious internship and wants volume and scale rather than greenfield. If you have never run a pipeline in production, the 1+ years of specific big data experience is a real gate, not a soft preference.
Observe.AI asks for 2+ years building large scale products, expertise in Java or Golang, good knowledge of at least one SQL or NoSQL database (Postgres, MongoDB, Cassandra, Redis), and hands on experience with telecom protocols (SIP and SDP, RTP), plus SIPREC, REST APIs, WebSockets, WebRTC and gRPC, and tools like Wireshark and Postman. Container management (Docker Swarm, Kubernetes) is listed as a plus. The day to day is a genuine mix of engineering and customer contact: driving technical discovery calls with clients, running feasibility studies on a customer's CCaaS offering, writing the design document and execution plan, building a proof of concept to validate the integration, then coding, unit testing and deploying it to production. You will also guide junior engineers on technical questions, handle customer escalations, join live troubleshooting sessions, and work with pre sales, customer success and implementation managers. Location: Bengaluru. Benefits named in the posting include medical insurance with free online doctor consultations, privilege and sick leave per the Karnataka Shops and Establishments Act, national and festival holidays, and parental leave. Honest fit guidance: the telecom protocol list is the real filter here, not the years. Two years is a genuinely accessible bar, but SIP, RTP and SIPREC are specialist knowledge that most 2 year backend engineers will not have, and the posting lists them as requirements rather than preferences. If you have worked anywhere near voice, telephony or contact centre infrastructure this is a strong fit. If you have not, expect to make the case on protocol fundamentals. Note also that this is not a heads down coding seat: direct client calls and escalations are in the job.
MongoDB asks for 3+ years of professional software engineering experience building and supporting production systems, strong coding in a modern language such as JavaScript or Python, and experience building web applications, backend services, APIs, data pipelines or internal platforms. It also wants solid fundamentals (testing, debugging, code quality, maintainability), experience with cloud services and CI/CD, the ability to work across systems with cross functional partners, strong written and verbal communication, and specifically experience partnering with marketing, sales and revenue operations teams to turn business requirements into technical specifications. Nice to have: go to market platforms such as Marketo, Salesforce, Segment or ad platforms, analytics or experimentation platforms, the ability to map a lead's path from website through to opportunity, familiarity with data pipelines, event instrumentation or web performance optimisation, and experience integrating AI or ML capabilities into products or developer tooling. How success is measured, published by MongoDB: in the first 3 months, understand the team's systems and standards, contribute code and take ownership of scoped work. In the first 6 months, independently deliver meaningful features across one or more team owned systems and improve at least one area of reliability, automation, documentation or developer workflow. Location and office: MongoDB states it is looking to speak to candidates based in Gurugram, for its hybrid working model. Not remote. Honest fit guidance: this is martech engineering, and you should want that. The systems are internal and the stakeholders are marketing and revenue operations, so a large part of the job is translating their requirements. If you want to work on database internals at MongoDB, this is the wrong requisition. If you want a 3 year bar, real backend ownership and a company that has written down what good looks like at 3 and 6 months, it is a strong one.
Zscaler asks for 3 to 4 years of software engineering experience, including ownership of complex production systems and a demonstrated ability to lead technically ambiguous, cross functional projects. Note the gap between that figure and the title: this is posted as a Senior Software Development Engineer and reports to a Director of Software Engineering, but the stated bar is 3 to 4 years. Job titles mislead in both directions on this board, and this is today's clearest example in the accessible direction. What the role expects: lead the design and delivery of major product capabilities, owning projects from problem definition through implementation, rollout and production operation. Design secure, reliable, scalable systems with clearly defined trust boundaries. Lead complex investigations while improving engineering practices, testing and operational readiness. Mentor engineers and give direction through design and code reviews. Partner with product and research teams and contribute to technical strategy and longer term architecture. Location and office: hybrid, based in Bangalore, with Mohali also listed on the requisition. Honest fit guidance: the domain is the draw. Securing AI applications and agents is new enough that nobody has a decade of experience in it, which is plausibly why the years bar is set where it is. Zscaler's culture section is unusually specific about wanting people who work in ambiguity and use AI tooling actively, and it lists AI fluency as a minimum qualification. If you are three years in, have shipped something you owned end to end, and want a senior title on a product that is being defined right now, this is one of the best value roles in today's list.
CloudSEK asks for 3+ years of experience in threat intelligence, malware analysis, threat hunting or digital investigations, and a strong working grasp of MITRE ATT&CK, MITRE Engage, the Diamond Model and the Cyber Kill Chain applied in operational and strategic research contexts. The stated responsibilities: conduct ransomware initial access vector mapping to understand infiltration patterns, affiliate ecosystems and monetisation structures. Perform e-crime and underground forum research to identify, profile and map threat actors, their infrastructure, tools and tradecraft. Execute infrastructure hunting campaigns against APT and e-crime command and control frameworks using passive DNS, TLS certificates and web fingerprinting. Develop and maintain cyber HUMINT sources for early warning, infiltration and intelligence collection. Correlate and analyse global threat campaigns across ransomware, APT and e-crime activity. Location: Bengaluru. Company context worth knowing: CloudSEK won the NASSCOM DSCI Excellence Award for Security Product Company of the Year in 2020 and the NASSCOM Emerge 50 Cybersecurity Award, joined the NVIDIA Inception Program, raised a $7M Series A led by MassMutual Ventures in 2021, and secured $19 million in 2025 led by Tenacity Ventures and Commvault. Honest fit guidance: this is a specialist seat and the 3 year bar is doing less work than the skills list. If your background is SOC alert handling you are not automatically a match, because the job is proactive hunting and source development rather than responding to what a tool surfaces. If you already read threat reports critically, have tracked an actor's infrastructure yourself, and are comfortable operating in underground communities, this is one of the more genuinely interesting security roles on the board.
Tekion asks for 4+ years of experience in manual and automation testing of web applications. The duties as published: design, develop, execute and maintain test cases and scripts for functional, regression, integration and system testing. Create and enhance automated test scripts for recurring scenarios and critical workflows. Analyse product requirements, technical specifications and user stories to ensure coverage. Identify, document, prioritise and track defects through resolution, partnering with developers on root cause analysis. Validate new features, enhancements, bug fixes and release candidates across web, mobile, APIs and platform applications. Participate in sprint planning, backlog grooming, stand ups, retrospectives and release readiness discussions. Collaborate with engineering, product and DevOps on test strategy, environments and release quality. Maintain test documentation, test data and traceability. Support API, database and end to end testing. Contribute to QA process, framework and standards improvement. Mentor junior test engineers on execution, defect documentation and quality practice. Tekion also publishes its own levelling notes for the role: job complexity is moderately complex testing across multiple features or components, balancing manual and automated work and identifying risks proactively. Required supervision is general, with the ability to manage routine testing activities independently. Location: Bangalore HQ. Honest fit guidance: if you want to move to pure automation, read the duties again. Manual testing is explicitly half of this job and Tekion does not hide it, describing automation expertise as growing rather than expert. That honesty is useful. As a 4 year role with clear scope, defined supervision and a real product behind it, it is a solid step, but it is not an SDET role in the sense of building frameworks all day. Tekion's own SDET postings at 5 to 8 and 8+ years are the ones that do that.
Tekion asks for a Bachelor's degree in Computer Science, Cybersecurity, Engineering or a related field (equivalent experience considered) and 4 to 6 years of experience in security engineering, IT security or related roles. Required knowledge: strong understanding of network, application and cloud security principles. Experience with security tools including SIEM, IDS and IPS, vulnerability scanners and endpoint protection. Knowledge of cloud platforms (AWS, GCP, Azure) and their security services. Familiarity with compliance and security frameworks (NIST, ISO 27001, SOC 2, CIS). Scripting or automation experience in Python, Bash or equivalent is preferred. Strong analytical and problem solving skills and good written and verbal communication. Industry certifications such as CISSP, GSEC or CEH are preferred, not required. Day to day: implement, configure and maintain security tools, monitoring systems and access controls. Support vulnerability management including scanning, analysis and remediation coordination. Participate in incident detection, response and root cause analysis. Work with engineering and IT to embed security practice into development and infrastructure. Help maintain compliance with SOC 2, ISO 27001 and NIST. Perform security assessments and testing of applications, systems and cloud environments. Contribute to threat modelling and risk assessments. Maintain security documentation, runbooks and knowledge bases. Provide guidance and mentorship to junior engineers. Location: Bangalore HQ. Honest fit guidance: this is a broad generalist security seat, not a specialist one. You touch tooling, compliance, incident response and assessment rather than going deep on any single one, which suits someone who wants range at the 4 to 6 year mark and suits a specialist less well. The certifications are preferred rather than required, so do not self reject over them.
Commvault asks for a Bachelor's degree and 4+ years of experience in backend software development, with strong proficiency in C++ and SQL. It also wants a solid understanding of algorithms, data structures, multithreading and system design, experience with Linux development and performance optimisation, and strong ownership, problem solving, communication and mentoring skills. Security and SaaS experience is strongly preferred. What you will do: build scalable systems with a focus on performance, concurrency and efficiency. Design and optimise SQL queries and database schemas for large scale workloads. Drive technical design and end to end delivery of complex features. Use AI assisted and agentic coding tools to improve development productivity and code quality. Mentor engineers through code reviews, design discussions and technical guidance. Location: Bangalore and Pune are both listed on this requisition. Benefits named in the posting: employee stock purchase plan, continuous professional development and product training with career pathing, annual health check ups, a car lease programme, tuition reimbursement, personal accident cover and term life cover, and internal Community Guilds. ⚠️ Worth reading before you apply: Commvault opens this posting with a recruitment fraud warning. It states that Commvault does not conduct interviews by email or text and will never ask for sensitive documents such as banking information or national ID numbers before your first day, and gives wwrecruitingteam@commvault.com for reporting suspected scams. Apply through the official link on this page and treat any off channel approach as suspect. Honest fit guidance: modern C++ plus SQL at depth is a narrower skill set than generic backend, so the 4 year bar is generous only if you actually have the C++. If your background is Java or Python services, this is a harder sell than the years suggest.
Okta asks for 5+ years of experience working on large scale systems or services, previous experience using Node.js (TypeScript or JavaScript) to build backend services and create and maintain public or internal APIs, experience with SQL (PostgreSQL) and NoSQL (MongoDB), and experience with containerisation (Docker) and cloud environments (AWS or Azure preferred). Full stack background is a plus rather than a requirement: the role is backend focused but a portion of the work involves React. Okta also asks for someone who communicates and mentors well, and who works autonomously while knowing when to ask for help. What you will be doing: collaborate with engineers inside and outside the team to design and deliver new APIs and features for B2B customers. Drive technical improvements to the codebase and architecture for reliability, maintainability and scalability. Mentor and coach other engineers on engineering practice and testing. Work with the Product Manager and Product Designer to define new features and review customer feedback. Participate in the team's on call rotation. Location and office: Bengaluru, hybrid. ⚠️ Okta currently has many near identical Bengaluru engineering titles open at once, several of them called simply Senior Software Engineer. They are different teams with different stacks and different experience bars. This one is Auth0 Enablement: Node.js, TypeScript, PostgreSQL, MongoDB, B2B enterprise APIs, 5+ years. Check the team paragraph on the posting matches the one described here before you apply. Honest fit guidance: on call for a Tier 0 service is a real commitment and the posting is upfront about it. If you want Node and TypeScript at genuine scale with clear enterprise customers on the other end, this is a good fit at five years.
Okta asks for 5 to 8 years of software development experience. Beyond that: proficiency in Go or a genuine desire to learn it (the posting allows both), experience managing infrastructure with Terraform, experience with Kubernetes and CI/CD, comfort working with data storage systems at scale in a team environment using PostgreSQL, MongoDB, Redis and DynamoDB, comfort with datastore reliability work (standard configurations, latency, throughput, availability, utilisation indicators, performance analysis), and experience with Azure or AWS. Okta also asks for someone who delivers work incrementally to get feedback and iterate. What you will do: develop the large, distributed, highly available infrastructure. Implement platform tools that let feature teams deploy and manage the datastores for their services. Research new technologies to accelerate new environment creation. Carry cross team initiatives end to end, covering code reviews, design reviews, operational robustness and security hygiene. Participate in the team's on call rotation. Location and office: Bengaluru, hybrid. ⚠️ As with Okta's other Bengaluru listings, the title on the board is just Senior Software Engineer. This is the Datastores Engineer seat on Platform Infrastructure at 5 to 8 years, which is a different job from the Auth0 Enablement role also in today's edition. Confirm the team paragraph before applying. Honest fit guidance: this is a platform and infrastructure role, not product engineering, so your users are other engineers. The posting is unusually welcoming on language, allowing a desire to learn Go rather than demanding years of it, which widens the door for strong infrastructure people coming from other stacks. The real requirements are the datastore and Terraform experience. Cross organisation coordination is named as something you should not be intimidated by, which is a fair warning that influence is part of the work.
Okta asks for 5+ years of professional expertise in native Android development using Kotlin and Java, and 3+ years of hands on expertise building production interfaces with Jetpack Compose. The posting names the most vital qualifications explicitly: deep Android engineering expertise, strong empathy for developers, self direction and a collaborative mindset. What you will be doing: architecting and developing composable, production ready UI components from the ground up using Jetpack Compose, and traditional XML views where necessary. Directly shaping, developing and maintaining the open source Universal Components Android SDKs and client libraries. Writing, curating and polishing technical content including tutorials, guides, sample applications and comprehensive API documentation. Engaging directly with the open source developer community, providing domain knowledge and technical assistance. Serving as the go to technical expert internally, working across developer relations, onboarding, growth, dashboard and core SDK teams. Location and office: Bengaluru, hybrid. Honest fit guidance: read the content and community half of this job as real work, not garnish. Roughly speaking you are a library maintainer with a public audience, which means writing documentation and answering developers in open channels is part of the week, not an interruption to it. That suits some Android engineers very well and frustrates others. If your satisfaction comes from shipping user facing app features on a product surface, this is the wrong seat. If you have ever been the person on your team who owns the shared UI module and cares how the API reads, it is a strong one. The 3+ years of production Jetpack Compose is the tighter of the two experience gates.
Tekion asks for 5+ years building large scale data, ML or platform systems, with strong software engineering fundamentals covering abstracted API design, concurrency and distributed systems. Responsibilities as published: build and run the LLM control plane and gateway (smart routing, rate limits and quotas, failover, token and cost tracking). Ship a unified API and SDKs over REST and gRPC with normalized schemas, structured outputs, caching and full observability across traces, logs and metrics. Enforce safety and privacy by default through content filtering, prompt and response validation and PII redaction. Enable multi model and multi vendor LLM use with automated canarying and versioning. Operationalise a graph based contextual ecosystem so agents retrieve the right context and enforce policy. Maintain and enhance the platform to support classical supervised and unsupervised ML models. What Tekion says makes it distinctive: end to end ownership of an LLM control plane serving multi tenant workloads under SLAs with quality and cost guardrails, and a rich vertical dataset and domain graph spanning sales, service, parts, finance and insurance, accounting and consumer touchpoints. Improvements in latency, reliability, evaluation quality and safety map to dealer outcomes such as upsell, cycle time, customer satisfaction and service revenue. Explicitly valued: having built or operated an LLM gateway or control plane before, including provider adapters, routing policies, caching, quota and rate limiting, and cost and token accounting. Location: Bangalore HQ. Honest fit guidance: this is platform engineering that happens to serve AI, so the skills that matter are distributed systems, API design and observability rather than model training. If your AI experience is fine tuning and prompt work but you have never run a gateway or thought about tail latency and cost attribution, expect the interview to go somewhere you are not ready for. Conversely, a strong backend or platform engineer with limited LLM exposure is a better fit here than the title suggests.
Tekion asks for 5 to 8 years in SDET, quality engineering or software engineering with a strong track record building test automation frameworks, plus strong programming in Python (preferred for ML tooling) or Java, with the ability to write production quality automation code. Also required: hands on experience testing data intensive or ML and AI systems, or a strong software testing background with demonstrated ML and LLM fluency. A solid understanding of ML concepts including model training and inference, evaluation metrics such as precision, recall and F1, and the non deterministic nature of model outputs. Experience designing evaluation frameworks or working with eval datasets, benchmarks or LLM as judge approaches. Familiarity with LLM and agent concepts covering prompting, RAG, embeddings and vector search, and with generative failure modes including hallucination, drift and prompt sensitivity. Experience with CI/CD, test orchestration and API and integration testing. Strong analytical and debugging skills, comfortable with root cause analysis across model, data and code layers. Location: Bangalore HQ. Honest fit guidance: note the deliberate either/or in the requirements. Tekion will take a strong traditional SDET who has built ML fluency, not only someone who has already tested ML systems, and that is a real opening because very few people have five years of ML testing experience. If you are an experienced automation engineer who has been reading about evals and wants a way into AI work without retraining as a data scientist, this is one of the cleaner routes on today's board. The Python preference is worth taking seriously even though Java is allowed, because the ML tooling ecosystem is Python.
Commvault asks for a Bachelor's degree in Computer Science, Cybersecurity, Information Technology or a related field, and 5+ years of experience in application security testing or offensive security. Required: deep understanding of the OWASP Top 10, CWE and SANS Top 25 and other security best practice. Hands on experience testing applications hosted in AWS, Azure or GCP. Familiarity with RESTful APIs, microservices architecture and container security (Docker, Kubernetes). Experience testing GenAI solutions. Strong command of scripting in Python, Bash or PowerShell for custom testing and automation. Solid understanding of secure SDLC and DevSecOps. Experience with security testing tools across three categories: static analysis (Fortify, Checkmarx, Veracode), dynamic analysis (Burp Suite Pro, OWASP ZAP, AppSpider) and software composition analysis (Snyk, Black Duck, WhiteSource). Preferred: security certifications such as OSCP, GWAPT, GPEN, CISSP or CSSLP, infrastructure as code scanning experience (Terraform, CloudFormation), and working knowledge of compliance frameworks such as PCI DSS. Day to day: perform detailed application security testing, lead threat modelling and assessments across the SDLC, use automated tooling to find vulnerabilities, manually validate and prioritise findings, collaborate with DevOps, engineering and cloud teams, provide remediation guidance and validate fixes, conduct secure code review as necessary, stay current on emerging threats, document findings clearly, and mentor junior security staff. Location: Bangalore. ⚠️ Commvault opens this posting with a recruitment fraud warning: it does not conduct interviews by email or text and will never request banking details or national ID before your first day. Apply through the official link only. Honest fit guidance: the tool list is long but the certifications are preferred rather than required, so an OSCP is not a gate. The GenAI testing requirement is the one most candidates will not have, and it is listed as a requirement rather than a preference, so be ready to talk about how you would approach prompt injection and model abuse even if you have not done it professionally.
Okta asks for 7+ years of progressive software development experience with a proven track record designing and building Windows features using C++, C# and the .NET framework. Required depth: deep expertise with Windows software environments including design and performance optimisation and security considerations. Solid understanding of advanced debugging and performance optimisation on Windows, the Win32 API, inter process communication, Windows services and secure credential handling. Experience in fast paced agile environments with a strong understanding of CI/CD and automated testing. Excellent communication, with the ability to explain complex technical concepts to varied audiences and influence technical direction. Proficiency using AI coding assistants such as GitHub Copilot to accelerate development. Strong conceptual understanding of Windows security features in a cross platform context. Nice to have: security domain expertise such as cryptography and endpoint security concepts (Trusted Platform Module, device management and MDM protocols, endpoint detection), and an understanding of identity and access management. What you will do: partner with product management, engineering directors and principal architects to turn business objectives into technical roadmaps. Drive cross functional collaboration with product, design and QA. Lead design and implementation of new features and services from conception to deployment. Act as a force multiplier across teams, mentoring staff and senior engineers and guiding design reviews. Raise the bar through code standards, automated testing and modernised CI/CD. Maintain high quality technical documentation. Location and office: Bengaluru, hybrid. Honest fit guidance: 7+ years for a principal title is on the accessible side, but the Windows systems depth is not negotiable. Win32, IPC and secure credential handling are specialist skills that a general full stack background will not cover. If you have spent years on Windows client software, the title is likely a promotion in name; if you have not, the years figure will not save you.
Everpure asks for 8+ years of experience designing, developing and testing product components, with Python and Go preferred among the languages listed. What you will do: design and develop microservices and integrate new features into Portworx products. Bring focus to design, development, unit and functional testing, code reviews, documentation and continuous integration and deployment. Collaborate with peers and stakeholders to take solutions from initial design through to production. Take full ownership of design and development activity, adapting to customer feedback and handling issues found in unit testing, system testing and customer environments. Product context: Everpure acquired Portworx in October 2020, its largest acquisition at the time, to build what it describes as the industry's most complete Kubernetes data services platform for cloud native applications. The team's stated remit is a secure, consistent experience for customers buying and using the Portworx offerings. Location: Bangalore. Note that Everpure states elsewhere in its postings that it is primarily an in office environment and expects attendance at the Bangalore office in line with company policy, other than PTO, work travel or approved leave. ⚠️ Naming caution, worth knowing if you search for this company. Everpure is the former Pure Storage and its postings still refer to Pure Storage and Pure in places, including on this requisition. It is the same employer. Honest fit guidance: Kubernetes depth is what actually gets tested here, not just Go. Portworx work means operators, custom resource definitions, controllers and CSI, and a candidate who knows Go but has never built against the Kubernetes API will struggle. If you have run stateful workloads on Kubernetes in anger, this is one of the more technically interesting storage roles in today's edition.
Tekion asks for 8 to 11+ years in ML engineering and MLOps, or backend and platform engineering with production ML. The published qualification list is long and specific: Experience with LLMs, retrieval systems, vector stores and graph or knowledge stores. Strong software engineering fundamentals: Python plus one of Java, Go or Scala, API design, concurrency and testing. Hands on with orchestration frameworks and libraries such as LangChain, LlamaIndex, OpenAI function calling and AgentKit. Knowledge of agent architectures (reactive, planning, retrieval augmented) and safe execution patterns. Pipelines and data: Airflow or Kubeflow or similar, Spark or Flink, Kafka or Kinesis, with strong data quality practices. Microservices and runtime: Docker and Kubernetes, service meshes, REST and gRPC, plus performance and reliability engineering. Model ops: experiment tracking, registries such as MLflow, feature stores, A/B and shadow testing, and drift detection. Observability: OpenTelemetry, Prometheus and Grafana, including debugging latency, tail behaviour and memory or CPU hotspots. Cloud: AWS preferred (IAM, ECS and EKS, S3, RDS and DynamoDB, Step Functions and Lambda) with cost optimisation experience. Security and compliance: secrets management, RBAC and ABAC, and PII handling. Location: Bangalore HQ. Honest fit guidance: this is an engineering role with ML in it, not a modelling role. Nothing in the requirement list asks you to design novel architectures or publish; almost all of it is about running models reliably and affordably in production. Data scientists who want to move into engineering will find the operational half unfamiliar. Platform and backend engineers who have shipped ML systems are, by Tekion's own wording, explicitly welcome, since it accepts backend or platform engineering with production ML as an alternative to an ML engineering title.
Fivetran asks for 8+ years in the software industry with a focus on building test automation frameworks, tools and infrastructure at scale. The expectations are written as a staff level scope: defining and driving code quality for tests including review processes, efficiency and maintainability. Writing critical or common code shared across multiple teams. Identifying and designing fixes for critical issues in core parts of the product. Contributing to and enforcing department wide coding standards. Identifying major improvements to product quality and resilience. Finding and fixing performance, scalability and reliability gaps in tests and test frameworks. Defining testing efficiency and reporting strategies. Defining guidelines for product releases including quality gates and readiness criteria. Expert application of design principles to test architecture. Technical requirements: strong knowledge of object oriented programming, preferably Java. Hands on experience with cloud platforms (AWS, GCP or Azure). Experience with CI/CD systems (Buildkite, Jenkins, GitHub Actions, CircleCI), modern build tools (Bazel, Maven, Gradle) and observability platforms (New Relic, Datadog, Prometheus, Grafana). SQL and NoSQL databases such as Postgres and MongoDB. Location and office: Bengaluru, listed as India and APAC on the requisition, hybrid. Benefits named: 100 percent employer paid medical insurance, generous paid time off plus sick time, inclusive parental leave, holidays including a year end global week of rest, volunteer days, RSU stock grants and professional development. ⚠️ Standing check on this employer: Fivetran sometimes ships requisitions carrying internal priority flags such as P3 (Future Open) or P2 (Internal Resources), meaning the role may not be actively funded. We checked this posting explicitly and no such flag is present. Honest fit guidance: the influence half is as large as the engineering half. If you want to write automation code and be left alone, the standards setting and cross team persuasion in this role will chafe.
Everpure asks for 10+ years of proven development experience in cloud architecture across AWS, Azure or GCP. What you will do: lead the design, development and deployment of Portworx's Kubernetes native backup and restore solution, serving as a technical anchor for the team. Design and build cloud native services that operate reliably at scale, with emphasis on performance, quality and efficiency in both design and implementation. Deeply leverage Kubernetes constructs including operators, custom resource definitions, controllers and CSI to build production grade data protection capabilities. Ensure security, resilience, stability and high availability are first class considerations in every design decision. Design robust, well defined APIs that integrate with the frontend and web UI. Drive architectural decisions and technical direction for the product, mentor engineers, and set the engineering quality bar through design and code reviews. Product context: Everpure acquired Portworx in October 2020, its largest acquisition at the time, expanding into multi cloud data services for Kubernetes and containers. Location: Bangalore. Everpure states in its postings that it is primarily an in office environment and expects work from the Bangalore office in line with company policy. ⚠️ Two cautions on this employer. First, Everpure is the former Pure Storage and its postings still say Pure Storage in places, including this one. Second, Everpure publishes some team lead roles under individual contributor sounding titles such as Member of Technical Staff, and we rejected two of those from today's edition for exactly that reason. This posting is the reverse case: the title says Lead but the responsibilities are architecture, mentoring and code review with no people management, so we have published it as an IC role. If that distinction matters to you, confirm it on the first call. Honest fit guidance: the CSI and operator experience is the real gate at this level, not the ten years.
Okta asks for 12+ years in software engineering with a strong emphasis on backend systems design and development, 8+ years in Python preferred, and separately 6+ years with modern front end frameworks such as React, Next.js and TypeScript, including principles of accessibility and the ability to collaborate with product and design. Also required: proven experience building and deploying production grade AI applications and services. A strong background building distributed systems, microservices and resilient APIs (REST and GraphQL) on AWS, GCP or Azure. Demonstrated ability to influence technical strategy and lead architecture decisions across global teams. Excellent communication with experience working across time zones and cultures. Experience with agentic frameworks such as LangChain, LangGraph and LangSmith is called a strong plus rather than a requirement. What you will do: drive architecture and design of AI solutions, leading cross functional initiatives across product, design and data science. Design, build and refine the core backend services powering AI solutions, including LLM orchestration, RAG pipelines and generative AI features. Build high performance agentic experiences for web and mobile engineered for streaming responses and low latency. Champion observability and operational excellence so AI services meet enterprise reliability and performance standards. Enable delivery of key AI projects through technical leadership and hands on execution. Mentor engineers. Location and office: Bengaluru, hybrid, on a cross geo team. Honest fit guidance: this is the highest experience bar in today's edition and the requirement set is genuinely wide. The 6+ years of React alongside 12+ years of backend Python is the part most candidates will fail on, and it is not written as a preference. If your last six years have been purely backend, read that line carefully before investing in the application.
GitLab publishes no years of experience figure anywhere in this posting, which is consistent across its listings, so we have left the experience field blank rather than invent one. What it asks for instead is specific: Significant professional experience with Go and building command line interfaces or systems level tools, including thoughtful command and flag design, clear terminal experiences, scripting friendly output, backwards compatibility and distribution across Linux, macOS and Windows. A sustained history of open source contributions through issues, merge requests and reviews, ideally including project triage or maintainership. Proven ability to operate as a self directed owner who can absorb multiple and frequently changing inputs, re-prioritise with discretion and continue delivering. Strong product and user experience instincts for developer workflows. Experience setting technical direction and influencing work across teams in an individual contributor role. Experience collaborating transparently in a remote, asynchronous environment. Additional experience with TypeScript or JavaScript developer tools, AI powered developer tools or agents, and plugin or extensibility architectures. What you will do: guide the technical direction of glab, owning architecture, implementation and evolution. Design and ship terminal first features and workflows in Go. Absorb changing inputs from product, the open source community and internal teams, re-prioritise and keep shipping. Partner with product management to shape and execute the roadmap. Steer the open source project and community by triaging issues, reviewing and merging contributions and upholding a quality bar. Team: about nine engineers in the Developer Clients group, part of the roughly 20 engineer AI Clients stage, working across the GitLab CLI, GitLab Duo CLI and the JetBrains and VS Code extensions, with a weekly sync. ⚠️ Location: the posting states the role is based in Bangalore. GitLab is an all remote company and its listings often are remote, but this specific requisition names Bangalore, so do not assume remote here. Honest fit guidance: the public open source contribution history is a real gate. GitLab asks for a sustained record, ideally including maintainership, and that is not something you can assemble during a notice period. If you already maintain something, this is a rare seat where that history is the qualification.
Fivetran states no years of experience requirement anywhere in this posting. We have left the experience field blank rather than infer a number from the Staff title, which means this role will not appear under any experience filter on this page. The skills asked for are: Strong experience building and operating production services in Python or Go. Experience with at least one cloud provider (AWS, Azure or GCP) and core primitives including IAM, networking and compute. Experience building developer productivity tooling such as CI systems, build tooling, developer portals and workflow automation. A track record leading ambiguous, cross team technical projects to completion. Strong communication and engineering judgment. You will have an edge with: Kubernetes and platform abstractions, infrastructure as code using Terraform or OpenTofu including reusable modules, safe state practices and modernisation of shared platform foundations, and experience building internal developer platforms or developer portals. What you will do: lead end to end projects that improve developer tooling, environments and operational workflows for speed, reliability and safety. Design and operate internal tooling and services in Python or Go. Build tooling for the internal developer platform covering self service workflows, shared patterns and developer facing interfaces. Help develop AI based workflows for productivity and efficiency, including automation that improves infrastructure operations such as faster triage and automated runbook steps. Location and office: Bengaluru, listed as India and APAC, hybrid. Benefits named: 100 percent employer paid medical insurance, generous paid time off plus sick time, inclusive parental leave, holidays including a year end global week of rest, volunteer days, RSU stock grants and professional development. ⚠️ Standing check: Fivetran sometimes ships requisitions with internal priority flags such as P3 (Future Open). We checked this posting and no flag is present. Honest fit guidance: with no years figure published, the gate is the portfolio. If you have built an internal developer platform that people actually adopted, say so early, because adoption is the outcome this team is measured on.
Everpure publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess a number from the Member of Technical Staff title. The requirements are stated as capabilities instead. What you will do: design and deliver automated validation suites that stress test PCIe, NVMe and OCP compliance, ensuring firmware maturity and hardware robustness for the Everpure platform. Drive technical root cause analysis for complex failures across firmware and system layers, using telemetry and logs to resolve performance or data integrity bottlenecks. Own and scale the regression infrastructure, improving test repeatability and coverage to accelerate the qualification cycle for next generation NAND technologies. Collaborate with cross functional engineering teams to provide clear risk assessments and quality metrics that directly influence product readiness and release timelines. Develop custom validation tools and scripts in Python to automate characterisation of drive level behaviour under power loss, snapshot and high volume scenarios. What you bring: deep technical expertise in storage validation, with proficiency across the areas above. Location: Bangalore. Everpure states in its postings that it is primarily an in office environment and expects attendance at the Bangalore office in line with company policy, other than PTO, work travel or approved leave. ⚠️ Two cautions on this employer. Everpure is the former Pure Storage and its postings still refer to Pure Storage in places. Separately, Everpure sometimes publishes team lead roles under this same Member of Technical Staff title, and we rejected two such roles from today's edition. This posting describes an individual contributor: it opens by calling the role a key contributor and names no reports. Read the role summary line rather than the title at this employer. Honest fit guidance: this is a genuinely specialist seat. PCIe, NVMe and OCP compliance work does not transfer easily from general software testing, and Python automation alone will not carry an application. If you have worked on storage, firmware or hardware validation, the competition here is much thinner than for a generic backend role.
Everpure publishes no years of experience figure on this posting, so we have left the experience field blank rather than infer one from the title. The stated requirements: Strong skills using Linux command line environments alongside Python, Go or C and C++ to build automated triage and analysis tooling. Exceptional communication with a proven ability to translate complex log evidence, metrics and test outputs into high quality bug reports and cross team alignment. A continuous improvement mindset, using large scale test environments and CI/CD pipelines to share system level validation best practice. What you will do: lead root cause investigations as a core member of the Everpure Forensics team, maximising reliability and performance of the flagship storage platforms at hyperscale. Look beyond surface level symptoms to solve complex technical puzzles where firmware intersects the broader storage stack. Collaborate with cross functional engineering, hardware and platform teams to turn critical escalations into systemic engineering improvements. ⚠️ Location, stated explicitly in this posting: Everpure is primarily an in office environment and you will be expected to work from the Bangalore office in compliance with company policy, other than PTO, work travel or other approved leave. Everpure is one of the few employers in today's edition that states its office expectation in writing rather than leaving it to be discovered. ⚠️ Naming: Everpure is the former Pure Storage and its postings still refer to Pure Storage in places. Same employer. Honest fit guidance: debugging is the job, not a phase of it. Some engineers find deep root cause work across firmware and storage the most satisfying thing available, and others find the absence of feature building draining. Be honest with yourself about which you are before applying, because the posting is honest about which this is. Note also that this employer publishes team lead roles under the same Member of Technical Staff title; this one is an individual contributor seat, described as a core member rather than a lead.
Sarvam publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess. It asks for capabilities and evidence instead: Deep understanding of vision language models covering training dynamics, architecture tradeoffs and failure modes. A track record of good research, demonstrated through publications, technical reports or impactful shipped work. Rigorous experimental design, specifically the ability to isolate variables and draw defensible conclusions. Strong PyTorch skills, with the ability to run experiments end to end. Intellectual range, meaning a willingness to work across data, training and evaluation problems. Bonus points: a PhD or Master's with relevant research experience in ML, computer vision, NLP or a related field. Research papers published at A or A star venues. Experience with multilingual or low resource language modelling. Familiarity with document understanding, OCR or structured visual prediction. Experience with large scale data curation and its effect on model quality. What you will do: work across the full lifecycle of vision language model development, from data through training and evaluation to production. Research vision language architectures including encoders and their tradeoffs. Location: Bengaluru. Honest fit guidance: note that the advanced degree and the publications sit under bonus points, not requirements, and "impactful shipped work" is offered as an alternative to papers. That is a deliberately wider door than most research postings, and it means a strong engineer with real model training experience and no PhD should not self reject. What is not optional is the PyTorch depth and the experimental rigour: Sarvam wants someone who designs an experiment properly rather than someone who runs training scripts. If your ML work has been fine tuning with off the shelf recipes, this is a step up rather than a lateral move.
Databricks states the ideal experience three ways, and any of them qualifies: 2+ years as a Deployment Strategist, or 2+ years at a high growth startup in a builder or founder capacity, or alternatively 5+ years in a senior client facing product or delivery role at a top tier technology company or consultancy. We have recorded the bar as 2+ years because that is the floor the posting sets. Also required: demonstrated experience in value based scoping (total cost of ownership and return on investment), managing agile software projects and writing PRDs. Strong communication skills, described as opinionated and humble, able to build rapport and drive decisions in days rather than weeks. A product and systems thinking mindset, able to perform a SWOT analysis and understand a competitive landscape. Relentless execution with a hands on mentality, expert at escalation. What you will do: partner with Account Executives to build C-suite trust, perform deep discovery to map the customer's political and technical landscape, scope the value, define the minimum viable product for a pilot, write the PRD that guides the engineering team, and manage delivery. ⚠️ Two things to weigh carefully. First, location is listed as Remote, India, which makes this one of very few genuinely remote roles on today's board. Second, and directly against that, the posting requires the ability and interest to travel up to 50 percent. Remote here means no fixed office, not staying at home. If relocation is your constraint this role helps; if travel is the constraint it does not. Honest fit guidance: this is not an engineering role and we have grouped it with the customer facing listings for that reason. There is no coding requirement anywhere in the posting. What it wants is someone who can sit with a large enterprise, work out what is worth building, write it down precisely and push it through. The founder or early startup route in is genuine and rare, so if you have built something from nothing for two years without a conventional title, this posting was written with you in mind.
Zenoti asks for 2 to 5 years of experience implementing software systems, with hands on experience in data transformation, system validation and migration tasks. Required skills: deep knowledge of features in Microsoft Excel, with working knowledge of database systems a plus. The ability to use tools and scripts to transform data for setting up customer sites. The ability to innovate and develop tools to enhance the migration process. Experience with data migrations and data mapping. The ability to adhere to and develop quality checks that demonstrate the integrity of data migration from legacy systems into Zenoti. A technology centric background. Strong logical, analytical and problem solving skills. Excellent communication skills. The ability to work in a fast paced environment across multiple projects. Knowledge of web design using HTML is listed as good to have. What you will do: solution and configure Zenoti to meet each customer's business processes, work with customers to define requirements, and manage customer expectations through the implementation. Location: Hyderabad, Telangana. Honest fit guidance: be clear that this is a consulting and configuration role, not a software engineering one. You will write scripts and transform data, and the posting genuinely rewards people who automate rather than click, but you are not building the product. That makes it a good fit for someone with a technical background who likes customer contact and project variety, and a poor fit for someone who wants to grow as a developer, because the code you write is throwaway migration tooling rather than shipped software. The Excel requirement is not a joke and appears above the database line, which tells you something about the day to day. At 2 to 5 years with a genuine technology requirement, it is a real door into a product company for people whose first job was support or operations.
ElevenLabs asks for 3+ years of experience working with customers in a technical capacity, with direct enterprise customer experience preferred. Also required: experience in product development, delivery and change management. Commercial instinct, described as comfort engaging in deal conversations, structuring value propositions and navigating enterprise sales cycles alongside go to market partners. Basic proficiency in Python and familiarity with API integration, sufficient to prototype, demo and communicate credibly with engineering teams. Excellent communication and problem solving, particularly the ability to simplify complex technical concepts. A proven track record taking ownership of complex, ambiguous projects and delivering results. Adaptability across different customer environments, industries and technical use cases. Technical aptitude and familiarity with common LLM tooling and AI agent frameworks. The ability to creatively map enterprise use cases and workflows to AI systems. ⚠️ Location, read carefully. The posting states this role is remote and can be executed globally, and adds that if you prefer you can work from the ElevenLabs offices in Bangalore, Dublin, London, New York, San Francisco, Tokyo and Warsaw. The requisition is titled for India and Bangalore is among the offices, so India is clearly in scope, but the remote wording is global boilerplate rather than an India specific commitment. Confirm your own eligibility and expected hours before assuming. Benefits named in the posting: an annual discretionary stipend for learning and development, an annual discretionary stipend for social travel to meet colleagues, and an annual company offsite. Honest fit guidance: the commercial instinct requirement is the one to weigh. This is not a role where you can stay purely technical, because deal conversations are named in the requirements list. If you are an engineer who wants customer contact but not commercial exposure, look at the support and solutions architecture roles in this group instead. If you like being the person who can talk to both the buyer and the engineers, the Python bar here is genuinely basic and the door is wider than most AI company postings.
Druva states experience as 3 to 6 years, and separately asks in the same requirement list for a Bachelor's degree preferably in a technical field and 4+ years of relevant work experience or an equivalent combination of training and experience. Those two figures do not quite agree, which is worth knowing before you rule yourself out at the low end. We have published the stated 3 to 6 year band. Required knowledge: excellent written and verbal communication with prior experience communicating with enterprise, service provider or SMB customers. Good understanding of backup and recovery concepts including backup types and replication. Administrative experience in Windows, Linux, Unix and Solaris. Knowledge and understanding of AWS cloud infrastructure. Administration and maintenance knowledge of Microsoft 365, Entra ID, Dynamics 365, PowerApps, Google Workspace and Salesforce. Working knowledge of Active Directory and APIs. Proficiency troubleshooting a wide variety of applications using standard tools including Wireshark, tcpdump, procmon, perfmon and OpenSSL. Fundamental knowledge of storage technologies (tape devices, SCSI, SAN, iSCSI, NAS) and networking concepts (routers, firewalls, proxies). System integration and identity and access management knowledge including LDAP. Location: Pune, Maharashtra. Honest fit guidance: the title says Associate but the requirement list does not read like an entry level job, and that gap is the single most useful thing to know here. This is a broad infrastructure knowledge test more than a years test, so a candidate at three years who has genuinely administered Windows and Linux, touched AWS and debugged with Wireshark is a better fit than someone at six years who has only worked one product. Customer support at an enterprise backup vendor also means escalations under pressure when a customer cannot recover their data, which is a specific kind of stress worth being honest with yourself about. In return you learn a very wide surface quickly, and it is a well known route into cloud and storage engineering.
Hevo Data asks for 5 to 8 years in sales engineering, solutions engineering, pre sales or solution architecture within B2B SaaS, plus strong experience handling technical discovery conversations for global customers. Required understanding: SQL and NoSQL databases, REST APIs and integrations, data architectures and system design, and cloud and SaaS ecosystems. Excellent communication and stakeholder management. Hevo marks strong database expertise with excellent technical problem solving as a must have. Ideal but not required: experience with ETL and ELT, data warehouses or analytics platforms, and exposure to Snowflake, BigQuery, Redshift or Databricks. What you will do: drive the technical side of the sales cycle for US mid market and enterprise customers, partner with account executives to lead technical discoveries, understand customer architectures, uncover integration challenges and influence technical decision making. Collaborate with product and engineering to relay customer feedback. ⚠️ Working hours and location, stated in the requirements: comfortable working US hours from the Bengaluru or Pune office. This is a night shift in practice and it is a requirement, not a preference. Weigh it before applying. ⚠️ This is a commercially measured role and we have grouped it with the customer facing listings rather than the engineering ones for that reason. Hevo describes itself as entering hyper growth with ambitious revenue targets. Most pre sales roles carry a number even when the posting does not say so, so assume this one does. Honest fit guidance: Hevo's flexibility on ETL background is the genuinely useful detail here. It states that deep database expertise with strong solutioning can substitute for data pipeline specific experience, which opens the role to database engineers, solution architects and support engineers who have never worked at a data infrastructure vendor. If you can run a discovery conversation and reason about someone else's architecture out loud, the domain knowledge is learnable and Hevo says as much.
Databricks asks for 8+ years in a data engineering, data science, technical architecture or similar pre sales or consulting role, and separately 8+ years of experience with big data technologies including Apache Spark, AI, data science, data engineering, Hadoop and Cassandra. Also required: strong consulting and customer facing experience working with external clients across a variety of industry markets. Coding experience in Python, R, Java, Apache Spark or Scala. Experience building distributed data systems. Experience building solutions with public cloud providers such as AWS. What you will do: work with sophisticated data engineering and data science teams to help them achieve data driven outcomes on the Databricks platform, integrating it into their enterprise ecosystem. Act as technical advisor internally to the sales team and work with the product team as an advocate for your customers in the field. Become an expert in, promote and recruit contributors for Databricks inspired open source projects (Spark, Delta Lake, MLflow) across the developer community. Location: Bengaluru. ⚠️ Commercial framing, stated plainly so you can judge it. The posting says you will work directly with the sales team to develop your book of business, define account strategies and execute them. We publish technically demanding customer facing roles and reject ones that are sales jobs with a technical title, and this one clears that line on the strength of its 8+ years of hands on data engineering and coding requirements. But the book of business language is in the posting and you should read it as meaning your work will be measured commercially as well as technically. Honest fit guidance: this is one of the more technically credible pre sales roles you will see, and the open source advocacy element makes it a genuinely good platform for building a public profile in the data community. It suits a senior data engineer who has realised they enjoy the customer conversations more than the pipeline maintenance. It does not suit someone looking to avoid commercial pressure, and it does not suit someone who wants to keep building product.
MongoDB asks for 10+ years of experience in customer and market facing roles at the principal or Field CTO level. Required: a recognised technical leader with deep hands on experience with enterprise scale applications. Demonstrated success in scaling technical influence and earned credibility, with experience speaking at major technology conferences, hosting technical webinars, or contributing deeply to the developer community through technical blogs, open source contributions or whitepapers described as highly desired. A deep portfolio and history of published content, presentations at events, and interviews or quotes in the press and media. Executive presence, meaning the ability to command a room with credibility, deliver compelling keynote presentations and influence at senior level. What you will do: work closely with account teams to engage C-suite executives and senior technical leaders at MongoDB's most strategic customers. Bridge complex data architectures and AI to power business transformation, positioning MongoDB as the platform for modernising legacy systems and building next generation AI applications. Shape industry perspectives as a recognised technical thought leader. ⚠️ Location: the posting states plainly that this role can be based remotely in India. That is an explicit statement in the body rather than a tag on the listing, which is why we count it as genuinely remote. It is one of only two such roles in today's edition. Honest fit guidance: the public profile requirement is the real gate and it cannot be assembled quickly. If you have never spoken at a conference or published technical writing, the 10 years alone will not carry an application, because MongoDB has listed the portfolio as a qualification rather than a preference. Equally, if you are a well known engineer in the Indian data community who has been wondering what the commercial route looks like without moving into people management, this is that route: it is an individual contributor seat with no reports named anywhere in the posting.
ClickHouse publishes no years of experience requirement anywhere in this posting, so we have left the experience field blank rather than infer one. That means this row will not appear under any experience band filter on this page. What it asks for instead: Strong technical and communication skills, capable of bridging business objectives with technical solutions, and the ability to serve as a trusted advisor guiding clients on how to use ClickHouse for real time analytics, cloud native applications and enterprise scale workloads. What you will be doing: translate complex business and technical requirements into scalable solution designs, covering architecture, migrations, workflows and data visualisation. Work directly with stakeholders across every level, from the C-suite to data scientists and developers, to enable customer success. Evangelise ClickHouse's vision and capabilities, driving adoption and securing strategic commitments. Apply a solution based approach to demonstrate and deliver customer value. Lead new initiatives as the India presence grows. Location: Bangalore. Company context worth knowing, as stated in the posting: recognised on the 2025 Forbes Cloud 100, more than 4,000 customers, annual recurring revenue growth over 250 percent year on year, and a $400M Series D financing round. It names Capital One, Lovable, Decagon, Polymarket and Airwallex among customers that recently adopted or expanded deployments. Honest fit guidance: with no years figure published, the assessment will rest on what you can demonstrate rather than what your CV says, which cuts both ways. Someone with genuine analytics database depth and customer facing experience should apply regardless of the number of years they have, because there is no stated bar to fall short of. Note that this is an early India seat at a company scaling quickly, described as leading new initiatives, so expect ambiguity and breadth rather than a defined patch. Familiarity with ClickHouse itself is not stated as a requirement, but competing on this without it would be difficult given the open source community around the product.
Temporal publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess one from the Staff title. The stated requirements are capability based: Reside within Bangalore, India. This is listed as the first requirement, not a preference. Exceptional technical communication skills including presenting, whiteboarding and writing. Deep understanding of distributed system technologies, design principles and best practices. Proficiency building application prototypes and providing design, development, build and deployment guidance using one or more of Temporal's supported languages: Java, Go, TypeScript, Python, C# or PHP. A firm grasp of operational considerations in production environments such as security, reliability, performance, cost management and operations. The ability to give insightful advice on architectural topics including application patterns and platform architectures. Experience with at least one major cloud provider. What you will do: collaborate with prospects to determine whether their applications fit Temporal's platform well. Educate customers and prospects on the technical benefits and limitations of the platform and cloud service. Position Temporal as a leading solution against competing technologies and architectural patterns. Foster an environment within customer engineering organisations to increase adoption and expansion of Temporal in production. Partner closely with account executives to develop and execute account plans. Manage and nurture technical relationships. Location: Bengaluru, Karnataka, with residence in Bangalore required. Honest fit guidance: the banking specialisation in the title matters. Financial services buyers ask about correctness, audit and failure semantics in ways other industries do not, so distributed systems depth is genuinely load bearing here rather than decorative. This is a strong fit for a senior backend or platform engineer who has run into workflow orchestration problems personally and can therefore speak about them with conviction. It is a weak fit for a generalist pre sales professional, because the prototype building requirement means you will be writing code in front of customers.
Cursor publishes no years of experience figure on this posting, so we have left the experience field blank rather than infer one. That means this row appears in no experience band filter on this page. What you will do: partner with account executives to lead technical discovery, demos and proof of concept engagements. Build trusted relationships with engineering leaders, architects and developers, serving as their technical advisor. Translate customer requirements into solution designs, guiding them on best practices for rollout, prompt strategy and context configuration. Develop and deliver technical presentations, whiteboard sessions and hands on workshops tailored to customer needs. Act as the customer's technical advocate internally, influencing roadmap priorities and escalating feedback to product and engineering. Collaborate with post sales teams to ensure smooth handoff. The posting describes this as a highly customer facing role combining deep technical fluency with strong communication skills, working hand in hand with sales, product and engineering to scope solutions and demonstrate capabilities. Location: India. Note on the employer name: the posting refers to Anysphere, which is the company that builds Cursor. Same employer. Honest fit guidance: this is a pre sales role and we have grouped it with the customer facing listings accordingly. The difference between this and Cursor's Solutions Architect role, also in today's edition, is the stage: Field Engineer works with prospective customers before they buy, Solutions Architect is embedded post sale in strategic accounts. If you are choosing between them, that is the distinction to weigh, and the Field Engineer role is the more commercially exposed of the two. You should be a working engineer or recent one, because the audience is engineering leaders and architects who will know immediately whether you have shipped code. With no published years bar, evidence of that carries the application.
Cursor publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess. The requirements are stated as background rather than duration. You may be a fit if: you have a strong technical background in software engineering, infrastructure, DevOps, platform engineering or developer tooling. You have experience in customer facing technical roles such as Solution Architect, Solutions Engineer, Forward Deployed Engineer, Technical Account Manager, Enterprise Architect or similar. You have the ability to work hands on with engineering teams while also operating strategically with technical leadership. You have a strong understanding of developer workflows, SDLC tooling, integrations, CI/CD systems, governance and enterprise requirements. What you will do: work directly with engineering teams inside strategic enterprise accounts to roll out high impact workflows and accelerate adoption. Help organisations move from initial excitement to deeply integrating AI into how they build software. Help shape new capabilities through lighthouse customers and design partnerships. Turn successful customer workflows into reusable playbooks and reference patterns. Location: India. Note on the employer name: the posting refers to Anysphere, the company that builds Cursor. Same employer. Honest fit guidance: the explicit list of accepted backgrounds is the most useful line in this posting. Technical Account Manager and Forward Deployed Engineer are named directly, which is worth knowing if you have one of those titles and have been unsure whether solutions architecture roles are open to you. This is the post sale seat, so it is less commercially exposed than the Field Engineer role Cursor also has open today, and more about long horizon adoption inside accounts that have already bought. If you like seeing a rollout through rather than winning the deal, this is the better of the two. Expect the work to be genuinely undefined: nobody yet knows what AI native development looks like at enterprise scale, which is precisely the job.
Zscaler publishes no years of experience figure on this posting, so we have left the experience field blank rather than guess one. That means this row appears in no experience band filter on this page. Role expectations as published: drive opportunity acceleration in GSI partner led large sales scenarios, providing technical expertise to expand account sales engineer efforts and highlight the potential of the Zscaler Zero Trust Exchange. Lead strategic enablement by collaborating with GSI sales engineers to develop their technical capabilities, so they can independently deliver high quality demonstrations, architecture workshops and proofs of value. Elevate industry visibility as a technical thought leader through reference architectures, whitepapers, blogs and public speaking. Provide technical advisory support, education and mentorship to the global partner engineering team, explicitly without direct people management responsibilities. Zscaler's stated success profile: acting like an owner, navigating between high level strategy and hands on execution. Being a high trust collaborator who gives candid, respectful feedback. Approaching complex challenges with constructive energy. Operating with urgency and a focus on execution. Being driven by innovation and technical curiosity, constantly seeking more secure and scalable approaches. Zscaler also states across its postings that it expects candidates to actively use AI tooling to amplify their impact. Location: Bangalore. Honest fit guidance: the without direct people management line is genuinely useful and worth reading twice. Senior customer facing titles routinely hide a reporting line, and candidates who want to stay individual contributors have no way to tell from the outside. Zscaler has said it in writing here. What you should weigh instead is that this is a partner facing rather than customer facing seat: your audience is other engineers at integrators like the large consultancies, and success looks like their competence rather than your own delivery. That is a genuinely different satisfaction model, and enablement work suits people who enjoy teaching. If you want to architect for end customers directly, a straight solutions architect seat fits better.
Commvault asks for a Bachelor's degree and 4 or more years of software development experience. Note the phrasing: the posting writes it as "4 or more years" rather than "4+ years", which is the kind of wording automated parsers miss entirely. Read by hand, the bar is 4 years. Required: strong experience in C++, C#, object oriented design and .NET. Good knowledge of operating systems (Windows and Linux), multithreading and concurrency, data structures and algorithms, networking concepts and distributed systems. Experience with debugging and performance optimisation. Strong analytical and problem solving abilities. Excellent communication. Ability to work in Agile development environments. Security and SaaS experience strongly preferred. What you will do: design, develop and maintain core server side components. Build scalable, high performance enterprise software. Participate in architecture discussions and technical design reviews. Write clean, maintainable, well tested code. Debug complex production issues and improve system performance. Collaborate with globally distributed engineering teams. Locations: Bangalore, Hyderabad and Pune are all listed on this requisition, which gives more geographic choice than almost anything else in today's edition. Benefits named: employee stock purchase plan, continuous professional development and product training with career pathing, annual health check ups, car lease programme, tuition reimbursement, personal accident cover, term life cover and internal Community Guilds. ⚠️ Commvault opens this posting with a recruitment fraud warning: it does not conduct interviews by email or text and will never ask for banking details or national ID before your first day. Apply only through the official link. Honest fit guidance: the C++ and C# combination with real operating system and concurrency depth is a narrower profile than the 4 year bar suggests, and it is the requirement that will decide the interview. Backup and recovery is not a fashionable domain, but the engineering is genuinely hard and the systems are long lived, which tends to make for good technical mentorship.
Zenoti asks for 3 to 8 years of experience in implementation and support of enterprise products. That is a deliberately wide band and suggests the level is set after assessment rather than by the number itself. What you will be doing: work with customers to define requirements and help them adopt Zenoti solutions to streamline operations and increase revenue. Drive demos, walk throughs and solution reviews with customers. Solution, design and set up proof of concepts and pilots for high priority and large customers, ensuring successful implementations. Configure Zenoti to meet customer business scenarios. Identify risks based on current product capabilities, and define and implement mitigation plans. Address customer issues and concerns in a timely fashion. Stay current with product knowledge, business flow, sales process and market dynamics. ⚠️ Working hours, stated in the posting: this is a customer facing role and you will need to align your working hours to overlap the customer timezone in order to build relationships and provide timely service. Zenoti's customers are largely international, so treat this as a shift commitment rather than a formality. Location: Hyderabad, Telangana. Honest fit guidance: this is consulting and configuration work rather than software engineering, and we have grouped it with the customer facing roles for that reason. The difference from Zenoti's more junior implementation seat, also in today's edition, is real: this one leads solution design and pilots for the largest accounts, where the junior one is weighted towards data transformation and migration. If your strength is scripting and data work, the other posting fits better. If your strength is running a room, scoping what is achievable and being straight with a customer about what the product cannot do yet, this is the one. Note that risk identification is written into the responsibilities, which means the company expects you to say no to customers sometimes, and that is a healthier implementation culture than it sounds.
That's the last 5 days. The rest of the 821 open roles stay in their editions: