What this edition tells you
Today the checking earned its keep. LogicMonitor lists its jobs through Greenhouse, and the apply URL its own feed publishes returns a 404. All four of its roles would have gone out as dead links, including the only genuine entry level opening in this edition. The working link sits on a slightly different path on the same site. We found it, opened it, confirmed it loads that exact role, and published that instead.
On entry level, the honest number is one. Readers asked for more 0 to 1 year roles, and we looked properly: 99 job boards, 11,634 postings, 533 genuinely new. Exactly one asks for under two years. That is a thin day and we will not dress it up. The board itself is not thin though: 43 roles are live right now at one year or less, because a daily post only ever shows that day's additions. If you are early career, browse the board rather than only this email.
Here is today's complete edition in one place: https://www.munotes.in/dailytechjobs/2026-08-09
No roles match that combination.
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.
Read this before you apply
- The entry level role is one job, and the board has 43. LogicMonitor's Associate DevOps Engineer asks 1 to 2 years and lists Python as mandatory rather than preferred, so it is a coding job in an operations context. If it is not for you, use the experience filter on the page, because a single day's additions are not representative of what is live.
- Remote is four roles, and two restrict where you live. Sardine is genuinely remote India and genuinely backend, 7 or more years of Golang, but only for Bangalore, Delhi, Gurugram, Mumbai and Pune. Twilio's is remote across five states only. Grafana Labs is a fully remote company with no restriction stated, and MinIO's is listed remote from Bangalore. Read the location clause, not the tag.
- Appian asks for a premier institute on the junior role, not the senior one. Its Senior Software Engineer at 5 years prefers a highly selective premier engineering institution. Its Principal Software Engineer at 15 years names no institute at all. Same company, same city, same week. If the first rules you out, the harder one may not.
- Cerebras is four roles and several are hardware , running from manufacturing bring-up at 3 years to test engineering at 10, with physical design and RTL microarchitecture in between. If you studied electronics or VLSI rather than computer science, this is the most relevant employer here.
- Six roles publish no years figure at all. They sit in no experience filter on the page, and we would rather say so than invent a number. If you are on the lower side of experience, they are worth a look precisely because no bar is stated.
We read every posting by hand before it goes on this page. The same write-up goes out to the daily email.