No roles match that combination.
Added August 8, 2026
Required - 4 to 6 years of experience. The posting states this directly as Experience Required: 4 to 6 Years. - Strong hands on experience with Informatica and SQL programming. - Experience with cloud based data platforms and modern data engineering tools. - Good analytical and problem solving skills. - Strong communication and collaboration abilities. Key skills named in the posting - Informatica - SQL - Python - PySpark SQL - Databricks - Azure Data Factory (ADF) - Azure Data Lake Storage (ADLS) - Airflow (listed as good to have) - dbt (listed as good to have) The day to day - Designing, developing and maintaining ETL workflows using Informatica. - Building and optimising data pipelines using Databricks, ADF and ADLS. - Working on SQL, Python and PySpark based data transformation processes. - Collaborating with cross functional teams to gather and understand data requirements. - Troubleshooting, performance tuning and optimisation of ETL jobs and SQL queries. - Supporting deployment, testing and validation for data solutions. - Ensuring data accuracy, integrity and timely delivery. Location and working style Bengaluru, Karnataka. No remote arrangement is stated. A note on the application The posting includes a consent line stating that by submitting your application you agree to be contacted by the talent acquisition team via phone, email, SMS, WhatsApp or other channels. Worth knowing before you apply if you are careful about which channels recruiters use. Honest fit guidance The Informatica requirement is the deciding factor. It is an established enterprise ETL tool, and if you have worked with it the rest of this list is a natural extension. If you have only done cloud native data engineering with Spark and dbt and have never touched Informatica, the requirement is stated as strong hands on experience, so treat it as a real gate. This is a services company, which shapes the work: you build for clients rather than for one internal product, projects change, and exposure is broad but sometimes shallower than product engineering. Many engineers use exactly this to build range early, then move into product roles. Sigmoid has three roles in this edition at different levels: this one at 4 to 6 years, a DataOps Lead at 8 to 12 and a BI Solution Architect with no published years.
Required - 5+ years of QE experience, preferably at an enterprise SaaS company. - 3+ years of experience in quality engineering for enterprise level software. - 5+ years of experience in Python or Java based automation development. - Familiarity with Selenium, TestCafe, Postman, JMeter, Locust, Splunk, AWS and Kubernetes. - Expertise in test planning and cross team collaboration. - Experience working with distributed systems at large scale. - Able to write and review designs and code with other team members. - Able to deliver well designed, high quality code on time. - Experience with non HTTP based protocols: SSH, RDP, TLS, LDAP and similar. - Experience with networking: IP addressing, routing, firewalls. Preferred - Performance testing experience, which the posting describes as a huge plus. The day to day Quality engineering for Okta's identity platform: designing and building automation, planning test coverage across teams, and working at the protocol and network level rather than only through a browser. The requirement to review designs and code with other engineers indicates a role embedded in the engineering team rather than a separate QA function. Location and working style Bengaluru, India, tagged hybrid. Okta describes an immersive in person onboarding experience at the start of employment, and recent Okta postings on this board have specified two days on site per week plus travel to the Bengaluru office during the first week. Confirm both at the first screen. Honest fit guidance Read the protocol and networking requirements carefully, because they are what make this role different and they are where applications will fall down. Plenty of automation engineers have five years of Selenium and Python. Far fewer have debugged an LDAP bind or reasoned about TLS handshakes and firewall rules, and that is precisely the gap Okta is hiring into. If you have that background, this is a strong role: staff level, protocol depth, large scale distributed systems, and an explicit expectation that you write real code. If you do not, be honest about the distance. It is learnable, but the posting lists it as a requirement rather than a nice to have, so a targeted application that shows relevant networking or security exposure will do more than a generic automation CV. Okta has four roles in this edition at levels from 3+ years to 7+, across web platform, internal IT, quality engineering and security.
Required - BS in Computer Science, a related field, or equivalent industry experience. - 5+ years of experience in backend software development or automation using Node.js, Python or similar. - Strong experience with AWS services, especially Lambda, S3, SQS and SNS, EventBridge and DynamoDB. - Expertise in database design, schema modelling and query optimisation. DynamoDB and Snowflake preferred. - Strong grasp of integration design patterns, secure API development (REST and SOAP) and system interoperability. - Ability to develop and maintain GitLab based CI/CD pipelines for tests, linting and deployment. - Experience managing infrastructure as code with Terraform or CloudFormation. - Demonstrated experience building and maintaining integrations with Salesforce, NetSuite, Workday, Coupa, Stripe and Snowflake. Preferred - Familiarity with data validation, schema evolution and cross system reconciliation. The day to day - Designing, building and maintaining backend integrations using AWS serverless services. - Developing API based automations and orchestrating data flows between major SaaS platforms. - Refactoring legacy integration logic toward modern architecture standards. - Owning code from design through CI/CD and deployment. - Collaborating with US based engineers on shared initiatives, sprint planning, code reviews and technical handoffs. - Participating in a shared production support rotation, resolving critical integration and data pipeline issues. - Partnering with architects and business systems analysts on integration design and testing strategy. - Supporting both ETL style batch pipelines and real time event streaming using CDC and platform events. Location and working style Bangalore, India. The job title itself says Hybrid in Bangalore. Note a contradiction worth knowing about: the posting also carries an #LI-Remote tag in its metadata, which conflicts with the Hybrid in Bangalore text in the title. The specific statement in the title is the one to trust, and this is listed here as a Bangalore based hybrid role. Ask at the first screen if remote matters to you, because the tag is not a commitment. The posting also mentions collaboration with US based engineers, which usually implies some overlap with US hours. Worth confirming how much. Honest fit guidance Do not let Business Systems Engineer in the title mislead you in either direction. The requirements are backend engineering: serverless architecture, event driven systems, infrastructure as code and database design. But the domain is enterprise system integration, so you will spend your time on Salesforce, NetSuite and Workday data rather than on a customer facing product. For a backend engineer who enjoys distributed systems and event driven design and does not mind that the consumers are internal, this is a solid five year level role with a modern AWS stack. The production support rotation is real and should factor into your decision.
Required - 5+ years of hands on experience in Technical Support, or in data recovery and backup and recovery solutions, with a focus on one or more cloud platforms such as Azure, AWS or GCP. - Strong understanding of technology and cybersecurity basics, computer networking fundamentals, OSI layers and OSI layer protocols, Active Directory and DNS basics, TCP and UDP. - Hands on configuration and troubleshooting level knowledge of networking, storage systems, hypervisors and container solutions such as VMware, Hyper-V, Nutanix AHV, Kubernetes, OpenStack and OpenShift. - Cloud platforms such as Azure and AWS, with SaaS, PaaS and IaaS infrastructure exposure. - Databases including MSSQL, MySQL, Oracle, SAP, PostgreSQL and MongoDB. - Prior customer facing experience demonstrating, delivering a pilot or POC, and running technical demos of cybersecurity solutions, with strong interpersonal skills. - Excellent written and spoken English, and the ability to build and present PowerPoint decks. Good to have - Proficiency onboarding CRM applications such as Salesforce or D365. - Hands on exposure to Commvault, Rubrik, Veeam, Cohesity, Dell, NetApp or Pure Storage technologies. - Industry certifications in cloud (AWS, Azure) and AI. - Additional spoken languages such as French, German or Spanish. The working hours, stated by the employer The posting says that for AMER Centre of Excellence hires, prior experience with US based customers is preferred and flexibility to work in permanent night shifts is expected. The role title itself carries US Shift. This is a permanent night shift, not occasional on call, and it should be the first thing you weigh. The day to day Remotely supporting Sales Engineering Managers and Sales Engineers in the US market on pre sales engagements, focused on proofs of concept and demos, plus documentation, RFI and RFP responses, discovery, requirement gathering and technical research. Location and working style Bangalore, India, working US hours. A note on recruitment fraud Commvault opens its postings with a warning that it never conducts interviews by email or text message and never asks for banking details or identity documents before your first day. That scam targets exactly this audience, so it is repeated here. Honest fit guidance The night shift is the decision. Everything else about this role is attractive for an infrastructure generalist: broad technology exposure, customer facing skills that raise your ceiling, and a five year bar that is reachable. But permanent US hours reshape your life, and no amount of career upside changes that. Decide on the shift first and the technology second. If the hours do not work, Commvault has a Senior Sales Engineer role in Mumbai in this same edition at 8+ years with no night shift requirement stated.
Required - 5+ years of experience in quality engineering, test engineering or a closely related role, with substantial individual contributor experience on large scale distributed systems or cloud infrastructure. - The ability to reason through the full stack: client SDK, API, gateway, inference software, driver and hardware, well enough to debug from any layer. - Genuine self direction. The posting states you will frequently work without complete product specifications and must decide under ambiguity. - Clear written communication and effectiveness across timezones in an async first setting. The day to day - Release quality ownership: driving weekly cloud release qualification end to end, reading every PR in the release branch, understanding what changed, deciding where the risk is and designing qualification that exercises it. Being the final voice before a release ships. - Test infrastructure at scale: building and evolving functional, integration, performance and fault testing for the Inference Cloud platform, designed for twenty times growth in coverage, environments and traffic. - Code review with intent: reading developer PRs with real understanding of what each change does and its blast radius, then testing actual impact rather than surface area. - Automation expansion: continuously increasing coverage, fixing flaky tests rather than tolerating them, and using AI tooling to accelerate. Location and working style Listed as India Office. A sibling Cerebras posting names Bengaluru and another states hybrid working is possible, so confirm the office and on site expectation at the first screen. The async first, cross timezone description suggests meaningful overlap with United States teams; ask what hours that implies. Honest fit guidance This is a quality role for someone who thinks like an engineer, and the posting is refreshingly honest that it wants pushback rather than compliance. The line about being the final voice before a release ships means real authority and real accountability. If you have been frustrated by QA roles that are a downstream gate, this is the opposite of that. The flip side is that it is demanding. Weekly releases, no complete specifications, deciding under ambiguity and reading every PR in a release branch is a heavy load, and the full stack requirement down to driver and hardware is unusual for a test engineer. Five years is the stated bar, but the substantial individual contributor experience on distributed systems clause is doing real work in that sentence. Applications that show ownership rather than execution will land better.
Required - 5+ years of software engineering experience building large scale backend applications and distributed systems. Highly desirable - Experience with data pipelines, aggregations and large scale data processing, since many platform capabilities depend on transforming and serving data at scale. The day to day - Designing, building and maintaining core platform services that support multiple product and feature teams. - Developing highly scalable, reliable and fault tolerant backend systems for large workloads. - Architecting distributed services, APIs and foundational frameworks that enable rapid feature development across the organisation. - Building and optimising systems for high throughput data ingestion, aggregation, processing and retrieval. - Driving improvements in platform performance, reliability, observability and operational excellence. - Working with Product, Data and Engineering teams to define and deliver platform capabilities. - Contributing to technical architecture, engineering standards and long term platform strategy. - Mentoring engineers and taking part in design and code reviews. - Investigating and resolving complex production issues. Location and working style Bengaluru, Karnataka, India. No remote arrangement is stated for this particular role, although 6sense does list a separate security engineering role in this edition as India, Remote, so remote working exists at the company for some teams. Honest fit guidance This is a platform engineering role rather than a feature engineering one, and the difference matters. Your customers are other engineering teams, your work is judged on whether it lets them move faster, and the satisfaction comes from leverage rather than from shipping something a user can see. If you like designing the layer everyone else builds on, that is a good trade. The requirement list is short and honest: 5+ years of backend and distributed systems. There is no long list of named technologies to disqualify yourself against, which means the interview will test depth in fundamentals such as system design, concurrency, data modelling and failure handling. Prepare accordingly. 6sense has three roles in this edition: this one at 5+ years, a remote security engineering role at 5+, and a staff data engineering role at 10+. They are different teams.
Required - 5+ years of experience being part of a Security Operations or similar team. - 3+ years of experience developing automation. - 2+ years of experience conducting adversary emulation exercises. The day to day - Executing milestones for end to end SecOps and threat initiatives against the security roadmap. - Identifying and responding to complex security incidents including system compromise, intrusion attempts and denial of service, through continuous monitoring, vulnerability assessment and log analysis. - Engaging vendors and the Infrastructure, IT, GRC, Cloud and Application Security teams to validate alerts, resolve incidents and perform root cause analysis. - Researching emerging threats, disclosed vulnerabilities and attack vectors, and pushing mitigating controls into products and services. - Performing security forensics. - Building security tools and advanced automation so the security team operates at speed and scale. - Proposing, planning, leading and executing threat exercises based on security trends, advisories and academic research. - Mentoring engineers across information security to drive controls and risk remediation. - Communicating risk and mitigation to audiences with different levels of sensitivity. How the role is measured, per the posting Maintaining current knowledge of the product and architecture, preparing for weekly one to ones and monthly skip levels, taking part in the Security Operations on call rotation, mitigating exposures, driving incidents to closure within SLAs, and maintaining handbook pages, runbooks, workflows and dashboards, with weekly project status updates. Location and working style India, Remote. This is one of only three remote roles in this edition, and the only remote security role. Note the on call rotation: remote does not mean unstructured here, and incident response work carries real out of hours weight. Honest fit guidance The three part experience requirement is more specific than most security postings and it is worth reading as a whole. Five years in security operations is the base, but the three years of automation development and two years of adversary emulation are what separate this from a monitoring role. If you have run a SOC queue but never written tooling or run purple team exercises, expect that gap to come up. The mentoring line asks you to mentor engineers across information security, not to manage them, which is consistent with a staff level individual contributor role. For readers who have asked repeatedly for remote roles: this is a real one, stated in the location field rather than implied by a tag. Confirm at the first screen whether remote means anywhere in India.
Required - 5 to 8 years of experience in AI or machine learning, SaaS, or workflow automation. - A proven track record of working successfully with enterprise customers. - Strong foundational understanding of customer journeys and core business processes. - Technical familiarity with APIs, system integrations and complex enterprise software architectures. - Exceptional communication skills, with the ability to bridge technical engineers and business stakeholders. The day to day - Customer journey and workflow design: mapping end to end journeys across sales, support and operations, identifying high impact automation opportunities and designing agent driven workflows across systems and teams. - Solution architecture: designing agentic AI systems including orchestration, APIs and integrations, and combining large language models, rules and enterprise systems into scalable architectures. - Business value articulation: translating solutions into measurable outcomes such as cost reduction and conversion uplift, and supporting deal teams with return on investment narratives. - Proof of concept and deployment: leading POC engagements with clear success metrics and ensuring they convert to production deployments. - Stakeholder engagement: working with both business and technical stakeholders, and handling scepticism arising from prior enterprise AI failures. - Reusable playbooks: building repeatable solution frameworks across industries and enabling sales teams with structured use cases. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance Compare this against Paytm's other presales posting in this edition before applying. The Presales Manager role at 3 to 6 years publishes a hard requirement for a Bachelor's degree from a named Tier 1 institution. This Solution Architect posting, at 5 to 8 years, publishes no such requirement. If the institute line ruled you out of the other one, this is the door that is still open. The role is genuinely architectural rather than presentational. Designing agent orchestration, integration patterns and production paths is engineering thinking, even though the seat sits beside sales. The measure of success stated in the posting is POC conversion to production, which is a fair thing to be judged on and a hard thing to achieve. The scepticism line deserves attention. Many Indian enterprises have already run AI pilots that went nowhere. Being able to speak honestly about what agentic systems cannot yet do will serve you better in this job than enthusiasm.
Required - 6 to 9 years of experience in software engineering. - Bachelor's or Master's degree in Computer Science, Engineering or a related field. - Proven experience leading development of distributed systems, cloud native applications or large scale platforms. - Deep proficiency in programming languages, development frameworks and cloud infrastructure, with AWS, GCP and Kubernetes named. - Strong problem solving, architecture design and technical mentoring skills. - Excellent communication, collaboration and leadership capabilities. The day to day - Leading end to end technical execution for major projects, from design through deployment and monitoring. - Developing and enforcing engineering standards, coding practices and architectural guidelines across teams. - Working with product, UX and architecture teams to define scalable technical solutions. - Mentoring engineers at various levels and supporting development through code reviews and knowledge sharing. - Investigating production issues and leading root cause analysis and long term fixes. - Championing innovation, system improvements and performance optimisation. On scope and supervision, as published Tekion sets these out as separate fields. Job complexity: leads projects with cross functional dependencies and significant technical complexity, guides technical strategy and drives execution. Required supervision: functions independently and provides technical leadership to multiple engineers, accountable for design decisions and engineering quality. Expertise: strong technical depth in system architecture, application development and software design. Read together, this is a hands on lead. Technical leadership of multiple engineers is stated, direct reports are not. Location and working style Chennai Regional Office. Most engineering roles in this edition are in Bengaluru, so a genuine Chennai posting at this level is worth flagging. Application note The posting states that, effective 4 August 2026, current Tekion employees should apply through the internal job board in Ashby rather than externally. Honest fit guidance The 6 to 9 year band with a Lead title is a common point of confusion, so be clear: this is the individual contributor track. If you want to move into people management, this posting does not offer it. If you want to stay technical and take on architectural ownership, it does exactly that. Tekion has published a large number of near identical engineering requisitions across recent weeks at different levels, so read the specific posting rather than assuming from the title, and check which team and product area you would join before the interview.
Required - 7+ years of development experience designing and implementing software systems in Java, building highly reliable and mission critical software. - 3+ years of work experience designing and implementing security solutions for applications and distributed systems. The day to day - Acting as a liaison between the engineering and security organisations to develop requirements for the security roadmap. - Evangelising security best practices across the engineering organisation. - Researching, designing, implementing and owning security oriented frameworks and features with the goal of protecting Okta's customers. - Routinely participating in cross vertical code reviews with an emphasis on security. - Breaking down complex problems into sub tasks, prototyping rapidly and iteratively using agile practices. - Coaching and mentoring junior engineers on the team. Location and working style Bengaluru, India, tagged hybrid. Okta describes an immersive in person onboarding experience at the start of employment, and recent Okta postings on this board have specified two days on site per week and travel to the Bengaluru office during the first week. Confirm both at the first screen. Honest fit guidance The split in the requirements is the thing to focus on. Seven years of Java is the base, and three years of applied security design is the differentiator. Application security engineers who have not done deep Java, and Java engineers who have never designed a security control, both sit slightly outside the stated bar. If you have both, there are not many roles that ask for exactly that combination. The liaison and evangelism responsibilities mean a meaningful share of the job is persuading other engineers, writing things down and reviewing other people's code. Some engineers find that the most valuable work they do; others find it draining compared with building. Ask in the interview what the split looks like across a typical quarter. Working on identity means the security work is genuinely consequential: the failure mode is somebody else's authentication. That raises both the interest and the pressure. Okta has four roles in this edition, from a 3+ year AEM engineering role up to this one at 7+.
Required - A strong engineering background with 7+ years of experience in backend or infrastructure engineering. - Proficiency in one or more of Go, Python, Node, Rust or C++. - Comfort working across APIs, SDKs, distributed systems and cloud infrastructure. - Experience building or integrating developer platforms or real time systems. - Ability to quickly understand complex systems and debug issues in real world environments. - Strong communication, collaborating directly with customer engineering teams and internal product teams. - Comfort in fast paced, low process environments where ownership and initiative matter. - Genuine interest in hands on customer work solving complex implementation challenges. Nice to have - Experience with WebRTC, real time media systems or telephony. The day to day - Working directly with customer engineering teams, remotely or on site when necessary, to design and implement real time applications on LiveKit. - Designing scalable architectures for voice AI, real time media and developer platform use cases. - Building prototype integrations, reference implementations and sample applications. - Helping customers navigate SDKs, APIs, infrastructure and deployment strategies for production systems. - Debugging and troubleshooting complex technical issues in production. - Leading technical workshops and architecture sessions with developers and product teams. - Translating customer needs into insights that inform product and platform direction. - Partnering with Product and Engineering on developer experience, documentation and tooling. - Contributing code, examples or improvements to LiveKit's open source ecosystem. Location and working style Remote, India. The posting notes on site work with customers when necessary, so expect some travel. This is one of three remote roles in this edition and the only one that is primarily backend engineering. Honest fit guidance Be clear about what forward deployed means before you apply. You are an engineer, you write code, and the requirement list is a backend engineer's list. But your working day is shaped by customer problems, their timelines and their codebases, not by an internal sprint board. Engineers who want to own a product surface for years will find that frustrating. Engineers who like variety, debugging unfamiliar systems and being the person who makes it actually work will find it excellent. The domain is a genuine advantage. Real time media and voice AI is where a lot of current product energy sits, and WebRTC expertise is scarce and well paid. The posting lists it as nice to have rather than required, so this is a realistic way in for a strong backend engineer without that specific background. Note the low process description honestly: LiveKit is a small company, and that means less structure than a large employer.
Required - 7 to 10 years of overall experience, with a minimum of 2 years of experience as a Sales Engineer. That split is stated in the posting and it matters: the sales engineering portion required is small relative to the total. The day to day - Providing technical thought leadership and advice to enterprise customers on transforming their digital experience. - Taking total ownership of the technical sale and associated processes. - Identifying and qualifying technical opportunities while developing and maintaining trusted advisor relationships with key customer stakeholders. - Delivering sales pitches, technical presentations and whiteboard sessions, and helping ensure deployments succeed. Reporting and team The posting places this role in the SE India department, reporting to the Senior Manager, Sales Engineering, and describes joining a global group working on cloud security. Location and working style Mumbai, India, described in the posting as a hybrid role and tagged #LI-Hybrid. Zscaler points to its published hybrid working model. Confirm the number of office days at the first screen. Honest fit guidance The two year sales engineering minimum inside a seven to ten year total is the most useful line in this posting. If you have spent most of a decade in network or security infrastructure and only a couple of years in a customer facing technical role, you are inside the stated requirement even though the title reads senior. That is a genuinely open door for engineers who have discovered they enjoy the customer conversation more than the console. Understand the trade honestly. Sales engineering pays well and often carries variable compensation tied to the region's number, which means your income depends partly on outcomes you influence but do not control. Your technical depth stays useful but stops growing in the way it would in a build role. Zscaler has three roles in this edition and they are very different: this one, an internal end user computing engineering role in Bangalore, and a threat researcher in Pune with weekend night shift requirements.
Required - 7 to 10+ years of sales engineering experience, or customer facing consulting experience, with large enterprise clients, preferably in a software or data centre environment. - Technical leadership and subject matter expertise across distributed architectures, file systems and competitive storage offerings in the SAN product space. - The drive the posting describes as a need for success. The day to day - Providing technical leadership and direction to customers and internal staff in developing integrated technology solutions supporting pre sales activity. - Assisting in the analysis, design and development of integrated technology solutions. - Acting as technical expert and consultant, proposing solutions that meet customers' technology and business requirements. - Making technical and sales presentations to customers' technical staff and senior management. - Serving as a trusted technology advisor and an internal resource on technical issues within the assigned market segment. - Building relationships with the account team, partners and customers, and marshalling corporate resources appropriately. - Leading technical sales calls. - Qualifying opportunities in terms of technical requirements, competition, decision making process and funding. Commercial framing, stated in the posting The role is described as accountable for regional revenue goals through driving technical programmes and overseeing day to day account level activity. That is unusually direct for a pre sales listing and you should factor it into how the role will be measured. Location and working style Mumbai, India. No remote arrangement is stated. Link verification note, published for transparency Rubrik's careers site returns an automated blocking response to direct link checks, so this posting could not be confirmed by opening the apply URL in the usual way. It was instead confirmed live through the applicant tracking system's own interface, which returned the posting with a matching title and location on the morning of publication. Every other role in this edition was confirmed by a direct successful request. Honest fit guidance This is the most commercially framed of the customer facing roles in today's list, and that is neither good nor bad, it is simply what you should know before applying. Revenue accountability is stated up front rather than buried. The technical bar is genuinely high and specific: distributed architectures, file systems and SAN storage competitive knowledge. Generic SaaS pre sales experience will not substitute. If you come from storage, backup or data centre infrastructure, that specialism is exactly what is being paid for. Commvault has a comparable Senior Sales Engineer role in Mumbai in this same edition at 8+ years, in the same competitive space. Worth comparing both.
Required - BS, BE, B.Tech, MS or M.Tech in Electrical Engineering, Electronics and Communication Engineering, Computer Science, or equivalent work experience. - 7 to 10+ years of industry experience. - 3 to 5 years of experience in pre silicon and post silicon ASIC hardware. - Good understanding of computer architecture and networking. - Excellent coding in languages such as Python, Verilog, SystemVerilog and C. - Proficiency in hardware and software co design and layered architectures. - Excellent debugging, analytical and problem solving skills. - Proficiency in large scale testing and automation using pytest and Python. - Good presentation skills, able to refine diverse information and put forward optimisation strategies. The day to day - Developing and debugging flows that embed well tested, deployable optimisations into production processes to reduce time and cost on Wafer Scale Engines. - Refining AI systems across hardware and software design constraints such as di/dt, voltage and frequency characterisation space, and current and temperature limits, in relation to performance optimisation. - Developing and enhancing infrastructure that enables silicon for real world workload testing. - Developing self checking metrics and instrumentation for debug and coverage. - Working with silicon architects and designers, performance engineers and software engineers to improve Wafer Scale Engine performance. - Working across software, design, verification, emulation and validation. - Working with CI/CD tooling, git, GitHub, GitHub Actions or Jenkins, and merge and release flows. Location and working style Listed as India Office. Sibling Cerebras postings name Bengaluru and mention hybrid working, so confirm the location and on site expectation at the first screen. Honest fit guidance Note the two part experience requirement, because the second part is the real filter. Seven to ten or more years of industry experience is the headline, but the specific ask is three to five years of pre silicon and post silicon ASIC hardware work. General embedded or firmware experience is not the same thing. This is one of the strongest roles on this board for electronics and VLSI graduates who have built a career in silicon and assumed the AI boom had nothing to offer them. It has: the hardware is the product. The physical constraints named in the posting, di/dt and thermal and voltage frequency characterisation, tell you how close to the metal this sits. If those terms are familiar, you are the audience. If they are not, one of the other Cerebras roles in this edition may fit better, including an ML Research Engineer role open at 1 to 3 years.
Required - 5+ years in data protection or cloud experience. - A minimum of 8+ years of experience serving in a pre sales systems engineer role. Read those two lines together: the pre sales systems engineering requirement is the higher of the two at eight years, which is why this role is grouped at 8+ here. The day to day - Working as part of the account team to produce territory plans, account strategies and sales plans, engaging specialist resources as determined by the Sales and SE Manager, and developing new opportunities in the assigned territory. - Anticipating technology trends and building relationships with partners and internal departments including sales, support, business units, product management, marketing and development. - Calling on senior IT leadership, often without the account executive present, to qualify and understand the technical, financial, operational and business issues Commvault products can address. - Building relationships with technical decision makers in end user accounts and driving detailed, executable technical account plans. - Driving or supporting complex sales opportunities by translating business requirements into technical requirements, coordinating technical expertise, sizing and scoping, defining delivery and deployment approach, timeline and resources, coordinating demonstrations and proofs of concept, and supporting internal deal acceptance. On the wording in the posting The description says the senior sales engineer should be a team leader who mentors, teaches and contributes to overall success. Nothing in the posting establishes direct reports, and the responsibilities are individual contributor pre sales work throughout, which is how it is grouped here. Location and working style Mumbai, India. Tagged hybrid in the posting. A note on recruitment fraud Commvault opens its postings with a warning that it never conducts interviews by email or text message and never asks for banking details or identity documents before your first day. Repeated here because that scam targets this audience directly. Honest fit guidance Eight years of pre sales systems engineering is a firm bar and this is a senior seat, so treat the requirement as literal rather than aspirational. The data protection and cyber resilience specialism is the thing that transfers. Rubrik has a comparable Senior Sales Engineer role in Mumbai in this same edition at 7 to 10+ years, competing in the same space. If you are in this market you are probably a candidate for both, and it is worth comparing the two on team, territory and compensation structure rather than on the job description alone. Commvault also has an Inside Sales Engineer role in Bengaluru in this edition at 5+ years, but note that one is a permanent night shift supporting United States customers.
Required - 8+ years of experience designing and building enterprise scale SaaS applications using Microsoft technologies. - 5+ years of experience building highly available, massively scalable, distributed cloud services on AWS or Azure. - Strong system design, analytical thinking and problem solving skills, with the ability to own complex technical problems. The day to day - Owning end to end development and technical success of one or more product modules. - Designing, building and evolving highly scalable SaaS applications using .NET and C#, REST APIs, SQL and NoSQL, and Flutter or React, capable of supporting two to four times annual business growth. - Working closely with product managers, designers and other engineers to deliver customer centric features in an agile environment. - Owning the complete software lifecycle: design, implementation, code reviews, testing, deployment, monitoring and continuous improvement. - Using modern AI assisted development tools such as Claude Code and Cursor throughout the work, and building engineering assets including prompts, workflows, templates and automation that improve productivity across the wider engineering team. Location and working style Hyderabad, Telangana, India. No remote arrangement is stated. About the company, for context on scale Zenoti reports passing a one billion dollar valuation, an eighty million dollar investment from TPG, and customers including European Wax Center, Hand and Stone, Massage Heights, Hair Cuttery and TONI&GUY. The product is vertical SaaS: deep software for one industry rather than general purpose tooling. Honest fit guidance The Microsoft stack requirement is the deciding factor. Eight years on .NET and C# is specific, and engineers from Java or Python backgrounds will find this a harder sell than the generic Lead Engineer title suggests. If .NET is your background, the combination of eight years of enterprise SaaS with five years of distributed cloud services is a coherent and reachable profile. Lead here means technical ownership of modules, not people management. The responsibilities are all build and own, with no reporting line mentioned. The AI tooling expectation is worth taking seriously rather than treating as decoration. The posting asks you to build reusable prompts, workflows and automation for the wider engineering team, which suggests it will come up in the interview. Having a real opinion about where these tools help and where they do not will serve you well. Vertical SaaS is a genuine career consideration: you learn one industry deeply, which makes you valuable inside it and less obviously portable outside it.
Required - 8 to 12 years track record of relevant work experience, with a Computer Science or related technical discipline required. - Proven track record of building and shipping large scale engineering products, or knowledge of cloud infrastructure such as GCP or AWS, described as preferred. - Experience in Shell, Python or another scripting language. The day to day - Designing, managing and deploying highly scalable and fault tolerant distributed components using big data technologies. - Evaluating and choosing technology stacks that fit a client's data strategy and constraints. - Driving automation and large scale deployments, and driving good engineering practice from the bottom up. - Developing CI/CD, monitoring and support practices inside the team. - Writing scripts to automate devops processes and reduce team effort. - Supporting terabyte scale pipelines and performing root cause analysis for production errors. - Supporting developers in day to day devops operations, and designing the roster and escalation matrix for the team. - Interfacing daily with Fortune 500 customers to understand strategic requirements, connecting regularly with VP and director level clients, and travelling to client locations. - Providing technical leadership day to day, guiding devops engineers on design, automation and support tasks. - Playing a key role in hiring technical talent, and running training on the technology stack. On the scope, stated plainly This posting mixes hands on engineering with team direction. It asks you to design the on call roster and escalation matrix, guide other engineers day to day, take part in hiring and run training. It also says explicitly that you must be able to be both a leader and a hands on doer. There is no reporting line stated, so it reads as a senior technical lead rather than a people manager, but go into the interview with a direct question about whether anyone reports to you, because the boundary here is thinner than in most postings on this list. Location and working style Bengaluru, Karnataka. Travel to client locations is part of the role. No remote arrangement is stated. Honest fit guidance This is a services company role and that shapes everything. You work on client platforms rather than one product, priorities shift with engagements, and client contact is a core skill rather than an occasional demand. Engineers who like variety and are comfortable in front of senior stakeholders do very well in this environment. Engineers who want to own one system for years generally do not. The client travel and the VP level contact are stated up front, so factor both into the decision. Sigmoid has three roles in this edition: an Informatica Developer at 4 to 6 years, this one at 8 to 12, and a BI Solution Architect with no published years figure.
Required - A Bachelor's degree in Computer Science or equivalent, with 8 to 11 years of hands on experience in database management and optimisation across relational databases, with PostgreSQL as the primary skill set. - Expertise in one or more relational database management systems. - In depth knowledge of database security principles and compliance requirements. - Advanced skills in monitoring and optimising database performance. - Proven experience managing complex database projects. - Effective collaboration with cross functional teams, and experience engaging vendors. The day to day - Using deep expertise in database management and optimisation to ensure high performance and reliability of data systems. - Identifying bottlenecks and performance issues in data pipelines, and optimising query performance, data access and overall processing. - Designing, deploying and managing complex data systems in cloud environments such as AWS, Azure or GCP using tools including Terraform, following the AWS Well Architected Framework. - Developing complex automation using tools such as Jenkins and scripting to streamline data operations. - Architecting and managing enterprise high availability and disaster recovery solutions for business continuity. - Ensuring adherence to cloud security best practice and compliance standards. - Managing complex incidents, troubleshooting and implementing solutions to maintain data integrity and system reliability. - Mentoring junior team members and fostering a collaborative team environment. On the title The posting is titled Lead or Manager, Data Reliability Engineering, and the opening line says the role is accountable for designing, deploying and managing complex cloud based data systems. The management language throughout attaches to systems, projects and incidents. People appear once, as mentoring and guiding junior team members. No direct reports are stated. Ask about this specifically at the first screen, because the title genuinely is ambiguous. Location and working style Hyderabad. Zeta describes itself as an engineering first organisation with more than seventeen hundred people across India, the United States, EMEA and Asia. No remote arrangement is stated. Honest fit guidance PostgreSQL as the primary skill set is the clearest signal in this posting. If your depth is MySQL, Oracle or SQL Server and you have only touched Postgres occasionally, the eight to eleven year band means they are expecting real specialist knowledge: query planning, replication, tuning and failure behaviour. Fintech infrastructure carries compliance weight and genuine consequences when something breaks. The disaster recovery and high availability responsibilities are not theoretical here. For readers who asked for backend and data roles, this is one of the strongest on the list: it is database engineering at depth, not analytics work wearing an engineering title.
Required - 8 to 10+ years working at the intersection of design and frontend engineering. The posting states your portfolio must show both sides of the craft, so a code only or design only portfolio is unlikely to clear the first screen. - Production level proficiency in React, TypeScript and CSS. The posting says you can write code that ships but can also produce a quick experiment or demo. - Deep Figma fluency: component architecture, variables, auto layout and Dev Mode. - Hands on experience building and maintaining a design system in a product company. - Strong command of motion, micro interactions and visual polish. - Comfort using AI coding tools such as Cursor, Claude Code and v0 as part of everyday workflow. - Solid understanding of accessibility (WCAG), responsive and mobile design, and performance trade offs. - Clear communication of design and technical trade offs to varied audiences. The day to day - Building high fidelity interactive prototypes covering motion, data states and edge cases for web and mobile. - Using AI coding tools to accelerate prototype velocity without sacrificing craft. - Owning and evolving the UI component library, maintaining parity between Figma components and production front end code. - Defining and governing design tokens, theming and accessibility standards across the design system. - Participating in design reviews and giving implementation aware feedback early. - Exploring emerging UI patterns and AI native UX paradigms. - Creating proofs of concept that push what is possible in the product experience. - Raising the design team's technical capability by sharing learnings. Location and working style Pune, Maharashtra. No remote arrangement is stated. Honest fit guidance Design engineer is still a rare title in India, and this posting is a good example of what it actually means: you are an engineer, you write React and TypeScript that ships, but your remit is the design system and the quality of the interface rather than product features or backend integration. The dual portfolio requirement is the real filter and it is stated explicitly. If you are a frontend engineer who has never owned visual craft, or a designer who prototypes but does not ship production code, the posting says plainly that both are expected. Note where the role sits: the responsibilities describe raising the design team's technical capability, which suggests you are embedded with designers rather than with product engineers. That is a meaningfully different daily experience from a standard frontend seat, and worth asking about. Mindtickle is the only design engineering role in this edition.
Required - 10+ years of experience in DevOps Engineering. - Strong practical knowledge of managing AWS infrastructure, specifically EC2, load balancers, CloudFront, ElastiCache, EBS, S3, IAM, CloudWatch, Auto Scaling and Lambda. - Understanding of open source server software such as Tomcat, HBase, Kafka, MySQL, Redis and Elasticsearch. - Strong experience in infrastructure automation using Ansible, Terraform, CloudFormation or similar. - Hands on experience with Kubernetes, EKS, Docker and ECS. - Hands on experience writing automation in Shell, Python or PowerShell. - Strong experience with Jenkins, Maven, Gradle or similar. - Experience in DevOps and CI/CD pipelines using Jira, Confluence, Jenkins and Git. - Experience in configuration management, DevOps, CI/CD and agile practice. Described as a big plus - Hands on experience with big data technologies: Hadoop, Kafka, EMR, Ranger, Spark, Hive, Starburst, Looker, TigerGraph or Neo4j. The day to day Senior DevOps and infrastructure engineering on Paytm's cloud platform. The posting describes a cloud first company running some of the largest AWS workloads, with scale stated as petabytes of data, millions of requests per minute and a few thousand microservices on a few hundred thousand cores, plus an in house observability system handling tens of millions of events per second. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance Paytm currently has a DevOps ladder open at several distinct levels, and they are separate requisitions rather than one job posted repeatedly. This is the most senior of them at 10+ years. If you are earlier in your career, look for the more junior DevOps openings from the same employer rather than applying to this one. The scale claims are the genuine attraction. Very few employers in India operate infrastructure at this size, and the specific engineering described, a large in house CI platform, custom AWS cost management and non disruptive EBS autoscaling, is the kind of work that is hard to get exposure to anywhere else. Note that despite Engineering Lead in the title, the requirement list is entirely hands on technical with no people management experience requested, which is what places it in the individual contributor group here. Confirm at the first screen, since the title pairs Lead with Principal Engineer and those can mean different things.
Required - 10+ years of professional software development experience. - Experience working in remote or globally distributed teams. - Hands on technical expertise, rapid prototyping ability and the capability to develop innovative solutions as part of an incubation team. The day to day - Architect and deliver: designing, developing and owning end to end implementation of high stakes prototypes and robust, production ready solutions. - Spearheading AI research and development: driving technical direction and working with cross functional teams to experiment with, validate and integrate AI, machine learning and frontier technologies. - Championing engineering excellence: establishing governance for code reviews and driving continuous improvement in engineering standards, mentoring peers to lift code quality. - Influence and evangelism: explaining complex technical concepts, architectural decisions and project velocity to executive stakeholders and engineering peers. - Working in partnership with the Emerging Tech Initiatives tech lead to enable rapid experimentation. Location and remote terms, stated precisely The posting says the role will be remote and based in India, and then names the permitted states: Karnataka, Tamil Nadu, Telangana, Maharashtra and Delhi. That is a real restriction, not a formality. If you live outside those five states you are not eligible as written. Twilio describes itself as a remote first company, while also noting you may be asked to report in person on an ad hoc basis for team gatherings, functional offsites or customer meetings. The employer also discloses that it uses artificial intelligence to help make its hiring process efficient, while stating that every hiring decision is made by a person. Honest fit guidance Tech Lead in the title does not mean management here. The responsibilities are architecture, hands on delivery and mentoring, with no reporting line stated, which is why it sits in the individual contributor group. Understand what incubation work is before you commit to it. Building prototypes that may never ship is intellectually excellent and professionally risky, and success is measured by learning velocity as much as by launches. Engineers who need to see their work in customers' hands should weigh that carefully. The five state restriction is the single most important practical detail. Check it against where you live before anything else. For readers who have asked for remote engineering roles: this is one of three remote listings in this edition, alongside a LiveKit backend role and a 6sense security role.
Required - 10+ years of experience building backend or data intensive systems. The day to day - Leading large scale data systems: designing, building and evolving high throughput batch and streaming pipelines that process billions of records, and owning core datasets that power product features, analytics and machine learning. - Building systems that handle enrichment, deduplication, identity resolution and confidence scoring at scale. - Driving architecture and technical direction: defining long term architecture for foundational data platforms, and leading multi quarter initiatives such as platform migrations, major refactors and new data foundations. - Balancing data correctness, freshness, cost and performance in production. - Ensuring reliability and data quality: owning SLAs and SLOs for freshness, accuracy and completeness, designing data quality frameworks, reconciliation mechanisms and observability, and leading root cause analysis and long term fixes. - Collaborating with Product, Analytics, Data Science, Platform and go to market teams, and acting as technical point of contact for third party data integrations and vendors. - Mentoring senior engineers and influencing technical standards across the organisation, and leading by example in design reviews, operational ownership and incident response. On the level, in the employer's own words The posting opens by calling this a senior individual contributor role for engineers who enjoy owning complex systems end to end and influencing technical direction across teams, and says the problems do not have obvious answers. Mentoring senior engineers is included; managing them is not. Location and working style Bengaluru, Karnataka, India. No remote arrangement is stated for this role, though 6sense lists a separate security engineering role in this edition as India, Remote. Honest fit guidance The requirement is a single line, ten or more years of backend or data intensive systems, which means the interview will carry all the weight. Expect deep system design: how you would handle late arriving data, how you would resolve identity across sources without a shared key, how you would trade freshness against cost, and how you would migrate a platform without breaking downstream consumers. The phrase to take seriously is influencing technical direction across teams. At staff level the job is as much about persuading other engineers and writing durable design documents as it is about code. If you want a role where you mostly build, this may frustrate you. For readers asking for data engineering depth, this is the most substantial data role in this edition.
The working hours, stated by the employer This posting requires working flexible schedules including weekend night shifts to meet global operational demands, and includes on call support. That is stated twice in the description. It is not an occasional expectation and it should be the first thing you weigh. Required - Extensive experience in threat hunting, incident response, security operations, malware analysis or network defence. No specific number of years is published anywhere in this posting, which is why it appears in the years not stated group. - A Bachelor's or graduate degree in Computer Science, Engineering or a related discipline, paired with the ability to work flexible schedules including weekend night shifts. - Strong scripting and automation skills in Python, with advanced analytical reporting and experience authoring IDS or IPS and YARA signatures. - Foundational understanding of AI and machine learning technologies, and experience using them within your domain. Preferred - Experience using machine learning models or large language models to accelerate threat intelligence synthesis, automate pattern recognition across large datasets, or optimise anomaly detection. The day to day - Analysing emerging threats, adversarial behaviours and TTPs to improve detection capability. - Conducting proactive and retroactive threat hunting using Zscaler telemetry and behavioural methodologies. - Researching, analysing, validating and documenting threat hunting findings with high precision. - Responding to customer needs independently while managing flexible operational shifts and on call support. - Identifying detection gaps and working with the wider team to improve security posture. Reporting and team The posting places this in the Zscaler Threat Hunting department, reporting to a Senior Manager, and describes it as a hybrid India role. Location and working style Pune, India, hybrid. Weekend night shifts and on call, as above. Honest fit guidance Because no years figure is published, the practical bar is set by the phrase extensive experience plus the specific skills: YARA and IDS signature authoring, malware analysis and Python automation. Those are not entry level skills, but if you have them and only three or four years of experience, the absence of a stated number works in your favour. It is worth applying and letting them decide. The shift pattern is the real trade. Threat hunting is genuinely interesting work with excellent visibility into live attacks, and Zscaler's telemetry is a rare asset. Weekend night shifts are a significant and ongoing cost. Do not talk yourself past that line because the technical work appeals.
Required - Experience in web and mobile testing across Android and iOS, and device testing methodologies. - Ability to analyse business requirements to determine the test strategy covered by manual testing. - Strong knowledge of Java. - Experience working on automation scripts, and the ability to establish an automation framework. - Experience with Maven, Jenkins and TestNG. - Basic concepts of database testing. - Familiarity with both Linux and Windows environments. - Knowledge of BDD or Cucumber frameworks. - Knowledge of API testing tools. - Knowledge of Jira. - Experience working in agile methodology. Preferred - Experience with Selenium WebDriver. No years figure is published Paytm publishes no experience requirement anywhere in this posting, which is why it sits in the years not stated group. This is worth flagging rather than glossing over: it means the skills list is the entire bar as written, and the Technical Lead title is the only signal of seniority. The day to day Hands on quality engineering for Paytm products across web and mobile: designing test strategy, building and maintaining automation frameworks, and working within an agile delivery process. On the title The posting is titled Technical Lead, QA. Nothing in the description mentions direct reports, team management or hiring. The responsibilities are entirely technical, which is why it is grouped as an individual contributor role here. Confirm at the first screen. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance The absence of a years figure is the most useful thing about this posting for readers earlier in their careers. Most Technical Lead QA roles in India ask for six to eight years. This one asks for a skill list. If you can genuinely establish an automation framework in Java rather than only write tests inside an existing one, that is the capability being described, and it is worth applying even if your years are on the lower side. The framework establishment line is the part that separates this from a mid level automation role. Note that this is a comparatively short job description with no team or product area named. Ask which business line you would support, because Paytm spans payments, lending, commerce and advertising, and the testing problems differ considerably. Paytm has five roles in this edition across engineering, QA, onboarding and presales.
No years figure is published Sigmoid publishes no experience requirement in this posting, which is why it sits in the years not stated group. The only experience line is a reference to having built accelerators in the past. Architect in the title implies seniority, but the employer has not put a number on it. What the posting asks for - Experience building reusable accelerators. - Deep Power BI capability, including Power BI Service and workspace optimisation rather than only dashboard building. - Migration experience from legacy BI platforms: Tableau, Qlik, Cognos, Business Objects, SSRS, MicroStrategy and Excel. - Ability to build utilities using PowerShell, Power Automate, REST APIs and Microsoft Fabric. - Solution architecture for enterprise scale Power BI, optimising DirectQuery, Import, Composite Models and Hybrid Tables. - Governance frameworks and best practice, including row level security. The day to day - BI practice innovation: developing reusable accelerators, optimising Power BI Service and workspaces, and speeding up end to end development. - Leading programmes that migrate thousands of dashboards within a few months, assessing existing reporting environments and defining migration strategy. - Developing migration frameworks, templates and automation utilities, and optimising migrated reports for performance, usability and maintainability while minimising business disruption. - Building and maintaining accelerators: Power Query transformation libraries, deployment automation scripts, report validation and testing frameworks, governance toolkits, metadata documentation generators, performance optimisation checklists, migration accelerators and row level security templates. - Identifying opportunities to automate repetitive BI development work, and exploring Copilot and AI driven features to improve productivity. Location and working style Bengaluru, Karnataka. Sigmoid's other roles mention client interaction and travel to client sites; this posting does not state it explicitly, so ask. No remote arrangement is stated. Honest fit guidance Read this as an automation and tooling role that happens to be in the BI domain. If you are a dashboard developer looking for the next rung, the accelerator and utility building described here is a different skill: PowerShell, REST APIs and framework design. That is the gap to close. The migration workload is the honest picture of the job. Moving thousands of dashboards off legacy platforms is valuable, well paid and repetitive, and the accelerators exist precisely because the work would be unbearable otherwise. Some engineers enjoy the systematisation. Be sure you are one of them. Because no years figure is published, the interview will set the level. Come with concrete examples of tooling you built to make other people's work faster.
No years figure is published CloudSEK states no experience requirement anywhere in this posting, which is why it appears in the years not stated group. Combined with the Associate title, this reads as an early career role. What the posting asks for - Excellent communication skills. - Strong technical skills. - Cybersecurity exposure, listed explicitly as an added advantage rather than a requirement. - Strong customer service skills. - Organisation skills and the ability to work independently. - Ability to multitask and handle multiple customer enquiries at once. - Patience and the ability to stay calm under pressure. - Problem solving skills. - Ability to upsell and cross sell products and services. - Adaptable, detail oriented and organised, with the ability to work with cross functional teams to troubleshoot and resolve complex problems. The day to day - Being the first point of contact for customers and handling all customer enquiries. - Building relationships with customers and ensuring they are satisfied with the products and services. - Assisting customers with issues or problems. - Providing customer support by phone, email and live chat. - Answering questions and providing information about the products. - Making recommendations to customers about products and services. - Recording customer feedback and suggestions. The products you would support CloudSEK XVigil maps a customer's digital assets, identifies threats, enriches them with cyber intelligence and provides workflows to manage and remediate them including takedown support. BeVigil is an attack surface monitoring tool using mobile, web, network and encryption scanners. SVigil identifies software supply chain risks by monitoring software, cloud services and third party dependencies. Location and working style Bengaluru, Karnataka, India. The posting mentions flexible working hours and food and snacks at the office, which implies an office based role. No remote arrangement is stated. Honest fit guidance Two things should be said plainly. First, this is a customer support role, not an engineering or security analyst role. You will be answering enquiries and resolving issues, not hunting threats. Second, the requirement list includes the ability to upsell and cross sell, so there is a commercial element alongside the support work. Neither is a criticism, but both should be clear before you apply, because the cybersecurity framing can make the job sound more technical than the responsibilities describe. What makes it worth listing is the entry point. No years required, cybersecurity knowledge welcome but not required, at a real Indian security product company with named funding and awards. For someone who wants to get into the security industry and is willing to start on the customer side, that is a legitimate route, and product knowledge gained here transfers into solutions and technical account roles later.
Graviton publishes NO years of experience requirement for this role, which is why it is grouped as entry level here. What it asks for instead: Required - A degree in a highly analytical field such as Engineering, Mathematics or Computer Science, from what the posting calls top tier global institutes. - Basic familiarity with Linux and command line tools. - Foundational programming skills in C or C++, plus scripting in Perl, Python or Shell. - Strong problem solving with advanced mathematical and quantitative reasoning. - Clear communication, specifically the ability to explain complex technical ideas. - A strong quantitative mindset and genuine interest in data driven problem solving. Good to have (explicitly optional) - Experience with high frequency trading systems and infrastructure. - Knowledge of market microstructure and HFT strategies. - Familiarity with low latency programming and optimisation techniques. The day to day - Working alongside senior traders to implement and improve automated trading strategies. - Analysing production trades and proposing strategy enhancements from what you find. - Designing monitoring tools that surface problems in live strategies early. - Writing scalable C++ and Python scripts for risk attribution and performance breakdowns. - Building post trade systems that compute statistics across every production strategy. - Building centralised market data analysis tooling across exchanges. - Overseeing deployment and release cycles with a senior trader. Location and working style Gurugram, Haryana. The posting describes cubicle free offices and a non hierarchical culture, and lists fully covered commuting expenses, catered breakfast and lunch, four weeks of annual leave plus market holidays, gym and sports club memberships and an annual international team outing. Nothing in the posting offers remote work. Honest fit guidance Read the institute line carefully before you spend an evening on the application. Graviton is a selective prop shop and this posting names top tier global institutes explicitly, so it is a real filter rather than boilerplate. The compensating fact is the skills bar: no years demanded, and the programming ability asked for is described as foundational rather than expert. If you are a strong CS, maths or engineering graduate who enjoys C++, Linux and probability, this is one of the very few genuinely open doors into quant trading in India. If your background is web or app development with little maths depth, the Quantitative Analyst - Risk posting from the same firm asks for 3+ years and is a closer match.
Graviton publishes NO years of experience requirement here either, and says explicitly that market knowledge is not expected. Required - A degree in a highly analytical field such as Engineering, Mathematics or Computer Science. The posting names IITs. - A quantitative bent of mind. - Working knowledge of Linux or Unix. - Programming experience, preferably in C++ or C. - No prior knowledge of financial markets is needed, but a strong interest in learning about them is required. That sentence is quoted from the posting because it is the whole reason this role is worth an application from outside finance. - A strong work ethic. The day to day - Developing new trading models and improving existing ones on in house platforms. - Using advanced mathematical techniques to model and predict market movements. - Analysing large financial datasets to identify trading opportunities. - Providing real time analytical support to experienced traders. Location and working style Gurugram, Haryana. Same benefits package as the firm's other openings: covered commuting, catered breakfast and lunch, four weeks annual leave plus market holidays, gym and sports memberships, regular social events and an annual international team outing. No remote option is offered. Honest fit guidance Two roles from this firm sit in the entry level group today and they are not the same job. This one is model building and prediction, weighted toward mathematics and research. The Quantitative Analyst role is production facing: monitoring, tooling and release management for strategies already trading. Pick by which half of that appeals, because the interview will go deep on it. The institute filter is real and named. Set against that, the posting asks for zero years and zero finance background, which almost nothing else at this level does. If you have done well in probability, statistics, linear algebra or algorithms and you write C++, you meet the stated bar. Do not self reject on the finance gap: the posting says outright that it is not expected.
Required - 1 to 3 years of experience in software engineering or machine learning in a similar capacity. The posting adds, in the same sentence, that internships count. That is unusual and it is why this role leads the entry level group today. - Machine learning and inference work, with the optimisation focus described in the posting. - Software engineering fundamentals: this is an engineering seat, not a pure research seat. The day to day Inference focused machine learning engineering: getting models to run efficiently on Cerebras hardware, working on model optimisation and the serving path, and evaluating performance. Cerebras designs wafer scale chips, so the work sits unusually close to the hardware for an ML role, and the neighbouring openings on the same board (ML systems performance, post silicon bring up, physical design) show how deep that stack goes. Location and working style The posting lists the India office, and Cerebras states elsewhere on its board that it can work in a hybrid environment. Confirm the exact office and the number of days on site at the first screen, because the listing gives the location as India Office rather than naming a city. Honest fit guidance This is the most accessible genuine engineering role on today's list, and the internships clause is the reason. Treat "1 to 3 years" as the real bar rather than a formality, but do not add imaginary requirements on top of it: the company wrote down that project and internship work counts. Be clear eyed about the domain. This is inference and systems work at an AI chip company, so comfort with performance, profiling and low level thinking will matter more than familiarity with the latest model architectures. If your ML experience is entirely notebooks and fine tuning APIs, expect the interview to push toward engineering fundamentals. Cerebras has five roles on this edition across very different levels, from this one at 1 to 3 years up to a 10+ year full stack ML lead. They are separate teams, not one requisition posted five times, and applying to the level that matches you is worth more than applying to all of them.
Required - A degree in a highly analytical field such as Engineering, Mathematics or Computer Science, from top ranked universities. - 3+ years of experience in Python and Shell or Bash scripting. - Basic knowledge of Linux and shell command line tools. - Basic programming and scripting skills in Python or Shell. - Strong problem solving and analytical skills. - Excellent communication skills. - A strong work ethic. - Mentorship experience guiding junior developers. The day to day - Working as a team with senior traders to operate and improve automated trading strategies. - Analysing production trades and developing ideas to improve those strategies. - Implementing monitoring tools that highlight potential issues in production strategies. - Writing comprehensive, scalable C++ and Python scripts analysing production strategies for risk attribution and performance break ups along various buckets. - Building scalable post trade systems that analyse statistics across all production strategies. - Implementing tools for centralised market data analysis across exchanges. - Managing deployments and the release cycle alongside a senior trader. Location and working style Gurugram, Haryana. Cubicle free offices, non hierarchical culture, covered commuting, catered meals, four weeks annual leave plus market holidays, gym and sports club memberships, and an annual international team outing. No remote option is offered. Honest fit guidance Note the mismatch inside the requirement list, because it works in your favour. The title says Risk and the responsibilities describe C++ and Python analytics over live trading strategies, but the stated experience line asks only for 3+ years of Python and shell scripting plus basic Linux. The C++ appears in the responsibilities rather than the requirements. If you have three years of solid Python data work and can read C++, you are closer to this than the title suggests. The mentorship line is worth reading properly: it asks for experience guiding junior developers, not for managing them. This is an individual contributor seat. If you have less than three years, the other two Graviton postings in today's entry level group state no years requirement at all.
Required - BS in Computer Science or another technical degree, plus 3+ years of related overall technology experience. - Experience in Adobe Experience Manager. The posting marks this one as required. - Core web technologies: XML, HTML5, CSS, and client or server side scripting such as JavaScript, preferably using single page application patterns, plus web services development using RESTful implementations. - Proficiency in Day CQ and Adobe AEM foundational concepts, including core frameworks such as Apache Sling and Apache Felix, a solid understanding of templates, components, dialogs and widgets, and the AEM development and deployment process. - Proficient knowledge of the end to end content lifecycle: web content management, content publishing, deployment and delivery. - Strong understanding of SDLC methodologies (Agile, Scrum). - Highly self directed, able to multi task given incomplete and sometimes conflicting information. Preferred - Understanding of AEM WCM capabilities including Multi Site Manager and Blueprinting, and online marketing components such as advanced targeting, personalisation and multivariate testing. - Understanding of integration patterns and content centric application development using AEM with or without a Portal, Search or Commerce package. - Experience in at least one of Adobe Analytics, Campaign, Commerce, Marketo Engage or Target, or equivalent technologies. The day to day - Leading development and implementation of custom solutions and integrations within Adobe Experience Cloud. - Architecting scalable, high performance systems against business and technical requirements. - Developing and maintaining integrations with internal and third party systems, and optimising existing systems for performance and reliability. - Working with product managers, solution architects and other stakeholders to scope and deliver. - Participating in sprint planning, stand ups and retrospectives. - Providing technical support, troubleshooting defects and performance problems. - Maintaining documentation for design, development process and system configuration. Location and working style Bengaluru, India. The posting carries Okta's hybrid tag. Okta roles on this board have recently specified two days on site per week and in person onboarding in the first week, so confirm both at the first screen. Honest fit guidance Be clear about what this is. It is web platform engineering on Adobe's stack, not work on Okta's identity product, and AEM experience is listed as required rather than preferred. If you have that specific background, the 3+ years bar makes this one of the few senior titled Okta roles a mid level engineer can actually clear. If you have general Java and web experience but have never touched AEM, the required line is a real obstacle and the other Okta openings on today's list will fit better. Okta has four separate roles in this edition across different teams and levels. The titles do not track the years: this one asks 3+ while others on the same board ask 7+.
Required - 3+ years as a ServiceNow Developer with deep expertise in Flow Designer, Script Includes, ACLs and UI Policies. - Hands on implementation experience in at least one core product: ITSM, CSM, ITOM, HR or IRM. - Proficiency managing complex data migrations and building robust integrations with third party systems using REST and SOAP APIs and Transform Maps. - Ability to translate abstract business requirements into technical roadmaps, managing multiple high priority deliverables while keeping systems maintainable and well documented. - Strong interpersonal skills to partner with global stakeholders and give technical reviews that lift the wider development team. The day to day - Leading design and development of workflows, business rules and integrations to automate manual processes. - End to end delivery of enhancements across ITSM, CSM or HR, from Client Scripts through Flow Designer, against global performance and security standards. - Identifying trends through root cause analysis and prioritising preventive action for platform stability. - Participating in a shared on call rotation supporting 24x7 Customer Service Management. - Consulting with cross functional delivery teams on technical designs and conducting code reviews. Location and working style Bengaluru, India. The posting is explicit and worth quoting in substance: Everpure describes itself as primarily an in office environment and expects you to work from the Bengaluru office in line with company policy, except for approved leave or work travel. Treat this as an onsite role, not a hybrid one. Note also the shared on call rotation, which is a real commitment on a 24x7 service. Honest fit guidance This is enterprise platform development, so be honest with yourself about whether that is the career you want. It is not product engineering on the storage systems Everpure sells, and the work is measured by internal process automation rather than customer facing features. In exchange, ServiceNow is a durable and well paid specialisation with demand across most large Indian employers, and 3+ years is a genuinely mid level bar. One note specific to this employer. Everpure titles have repeatedly hidden team lead responsibilities behind individual contributor sounding names on this board, so read any future posting from them by its role summary rather than its title. This particular posting is a clean individual contributor role: it mentions technical mentorship and code reviews, but no reports.
Required - 3+ years of Design Verification experience. - 3+ years of hands on Design Verification experience. The posting states the requirement twice in slightly different words, which is worth knowing so you are not looking for a second, higher figure that is not there. - Verification of complex hardware designs, which at Cerebras means wafer scale AI silicon. The day to day Design verification work on Cerebras processors: building verification environments, writing and running tests against RTL, chasing down failures and proving out functionality ahead of silicon. The neighbouring openings on the same board show the surrounding stack: physical design, post silicon bring up, microarchitecture front end design and manufacturing bring up. Location and working style The posting gives the location as India Office. A sibling Cerebras posting names Bengaluru explicitly and another states you can work in a hybrid environment, so ask which office and how many days on site at the first screen rather than assuming. Honest fit guidance This is one of the few roles on this board aimed squarely at electronics, electrical and VLSI graduates rather than computer science ones, so if that is your degree it deserves a longer look than the software listings around it. SystemVerilog and UVM are the standard toolkit for this discipline; the posting itself does not name them, which is unusual, so expect the interview rather than the advertisement to establish the specifics. The 3+ year bar is real but modest for verification, where many roles start at five. If you have done verification at a semiconductor firm or a design services company in India for three years, you are in band. Cerebras carries five roles in this edition at levels from 1 to 3 years up to 10+. They are different teams. Apply to the one that matches your discipline rather than to all five.
Required - 3+ years of experience in a relevant domain. The posting names those domains explicitly: Computer Architecture, CPU or GPU Performance, Kernel Optimisation, or HPC (high performance computing). - Performance engineering for machine learning systems on Cerebras hardware. The day to day Making machine learning workloads run fast on wafer scale silicon. In practice that means performance analysis and profiling, kernel level optimisation, and reasoning about the interaction between model execution and the underlying architecture. The role sits alongside Cerebras openings in post silicon bring up, design verification and physical design, so the performance work has real hardware underneath it rather than a cloud abstraction. Location and working style Listed as India Office. Cerebras states on a sibling posting that the role can work in a hybrid environment, and another names Bengaluru. Confirm the city and the on site expectation at the first screen. Honest fit guidance This is a genuinely specialised role and the specialisation is the point. If you have spent three years on GPU kernels, CUDA, compiler backends, HPC codes or CPU microarchitecture performance, there are not many employers in India competing for exactly that, and this is one of the more interesting ones. If your background is applied machine learning, training models and running experiments, this is probably not your role even though the title contains ML. The requirement names architecture and kernel optimisation, not modelling. Cerebras has an ML Research Engineer opening at 1 to 3 years on this same edition that is much closer to applied ML work. The posting gives a short requirement list, so expect the interview to establish depth rather than the advertisement. Be ready to talk concretely about a performance problem you diagnosed and what the fix actually changed.
Required - 3+ years of experience building production grade software systems in Java, Scala or Python. Note the phrasing: production grade software systems, not model prototypes. This is an engineering bar first. - Machine learning engineering work at CRED, which operates a large consumer fintech product. The day to day Machine learning engineering on production systems. CRED publishes a deliberately terse job description, so the specifics of team, model domain and stack are not in the advertisement. Its sibling postings in this edition (a data scientist role at 4+ years and a consumer web developer role at 3+) suggest an engineering organisation split along conventional lines, with this seat on the ML systems side. Location and working style Hyderabad. The posting does not state a remote or hybrid arrangement, so assume office based and confirm at the first screen. Honest fit guidance The short description cuts both ways. It means less to prepare from, but it also means the one stated requirement carries all the weight: three years of production software in Java, Scala or Python. If you meet that and have genuine ML exposure, do not let the absence of a long skills list put you off applying. Ask early what the team actually works on. Machine learning at a fintech spans credit risk, fraud detection, recommendation and collections, and those are very different jobs with different regulatory pressure. A posting this brief will not tell you, and it is a fair first question. CRED has two other roles in this edition, a data scientist at 4+ years and a web developer at 3+ years, all in Hyderabad. If you are more analysis than engineering, the data scientist posting is the closer fit.
Required - 3+ years of experience building scalable, consumer facing web applications. - Web development for Prefr, the lending product within the CRED group. The day to day Building and shipping consumer facing web applications at scale. CRED writes short job descriptions and this one is no exception, so the framework, the exact stack and the team shape are not published. What is published is the domain, consumer lending, and the scale expectation implied by consumer facing. Location and working style Hyderabad. No remote or hybrid arrangement is stated in the posting, so assume office based and confirm at the first screen. Honest fit guidance This is one of the few genuinely frontend weighted roles in this edition, and at 3+ years it is reachable. If you have been writing React, TypeScript and CSS for a product company for three years, you meet the stated bar and should apply rather than waiting for a posting that spells out a longer stack list. Because the description is brief, prepare questions rather than answers. Worth asking: which framework, whether the role includes mobile web, how much of the work is new product versus maintaining existing flows, and how the team splits responsibility with design and backend. One thing to be aware of: this posting is for Prefr, a lending business, rather than for the main CRED app. If you assumed you were applying to work on the flagship product, clarify that early, because it changes both the work and the team. CRED has three roles in this edition, all in Hyderabad: this one, a machine learning engineer at 3+ years and a data scientist at 4+ years.
Required - 3 to 5 years of experience as a ServiceNow Developer. - At least 2 of those years with deep focus on SAM (Software Asset Management) and HAM (Hardware Asset Management). This is the specific part of the requirement and it is the part that will decide your application. The day to day Business application development on ServiceNow inside Okta's internal IT organisation, centred on the asset management modules. Expect configuration and custom development against SAM and HAM, integration with the systems that feed asset and licence data, and the reporting that makes it usable. Location and working style Bengaluru, India. Okta postings on this board have specified hybrid working, with recent listings naming two days on site per week and in person onboarding during the first week of employment. Confirm the current arrangement at the first screen. Honest fit guidance The two year SAM and HAM requirement is the real gate here. General ServiceNow experience across ITSM or CSM will not substitute, because asset management has its own data model, discovery integrations and licence compliance logic. If you have that background, this is a well paid specialisation at a large employer and the 3 to 5 year band is honest about the level. If you are a ServiceNow developer without the asset management depth, Everpure has a ServiceNow Developer opening in this same edition at 3+ years that asks for ITSM, CSM, ITOM, HR or IRM instead, which is a wider door. Be clear that this is internal enterprise IT rather than work on Okta's identity products. That is a legitimate and stable career track, but it is a different job from the engineering roles Okta also has open in this edition, and the interview loop will reflect that.
Required - 3 to 6 years of experience in Pre Sales, Solution Consulting, Solutions Engineering, Product Consulting or Enterprise Technology roles. - Strong understanding of APIs, integrations, SaaS platforms, enterprise applications and solution design. - Experience supporting demos, POCs, RFPs, technical workshops and enterprise sales cycles. - Good understanding of APIs, CRM platforms, databases, cloud technologies and enterprise integrations. - Ability to create solution designs, integration workflows, POCs, demos and technical proposals. - Excellent communication and presentation skills, able to engage technical and business stakeholders. - Ability to simplify complex AI and automation concepts for enterprise clients. - Strong analytical and problem solving skills with a consultative approach. - Hands on experience with productivity, CRM and collaboration tools. Education requirement, stated explicitly by the employer - Must have: a Bachelor's degree from a Tier 1 institution. The posting names IITs, SRCC, St. Stephen's, BITS Pilani and NITs. - Preferred: an MBA from a Tier 1 institution, naming IIM Ahmedabad, Bangalore, Calcutta and ISB. This is published as a hard requirement rather than a preference, and it is reproduced here so nobody spends an evening on an application that the employer has already ruled out. It is the single most restrictive line in this edition. The day to day - Partnering with enterprise sales to understand client requirements and map them to Paytm AI solutions. - Running discovery sessions, identifying business challenges and building solution recommendations. - Delivering customised product demos, solution walkthroughs and proofs of concept. - Acting as technical advisor on product, integration, architecture and implementation questions. - Producing solution documents, proposal inputs, RFP responses, technical FAQs and sales enablement assets. - Collaborating with product, engineering, onboarding and business teams on delivery. - Capturing client feedback to improve product capability. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance Read the education line first. Everything else about this role is a normal presales brief at a reasonable 3 to 6 year band, but the institute requirement is written as must have and will decide most applications before the experience is considered. If you clear it, this is a good presales seat: enterprise AI is where the budget is moving, and doing discovery and POC work now builds a scarce skill. If you do not, Paytm has a Client Onboarding role and a Pre Sales AI Solution Architect role in this same edition, and neither publishes an institute requirement.
Required - 2 to 5 years of experience in Client Onboarding, Implementation, Customer Success or Solutions Engineering. - Good understanding of APIs, integrations, CRM systems and enterprise workflows. - Strong project management, problem solving and stakeholder management skills. - Excellent communication and client facing abilities. - Bachelor's degree in Engineering, Business or a related field. Unlike Paytm's presales posting in this same edition, no Tier 1 institution requirement is published here. Preferred - Experience in SaaS, fintech, enterprise technology or AI products. The day to day - Owning client onboarding from sales handover through to go live. - Understanding client workflows, systems and integration requirements. - Coordinating product, engineering and client teams for deployment. - Managing onboarding timelines, milestones and stakeholder communication. - Running client training sessions and driving product adoption. - Tracking onboarding KPIs, client satisfaction and implementation success. - Gathering client feedback to feed product improvement. About the team The posting describes the Inference and Agentic AI group as a cross functional unit spanning engineering, product, data science, business management and sales, owning the full lifecycle of AI solutions from opportunity discovery through deployment and scale. That breadth is a genuine advantage early in a career: you see how an enterprise AI product is actually sold, built and adopted. Location and working style Noida, Uttar Pradesh. No remote arrangement is stated. Honest fit guidance This is a customer facing implementation role, not an engineering role, and you should apply with that clearly in mind. You will not be building the platform. You will be making it work inside somebody else's company, which means integration troubleshooting, timelines and training rather than writing production code. For a reader two or three years into a support, implementation or solutions role, it is a good step up, and the API and integration requirement means technical skill is genuinely used rather than decorative. Paytm has five separate openings in this edition across engineering, QA and customer facing work. They are different teams at different levels, and the customer facing ones vary a lot in how restrictive their education requirements are, so compare before applying.
Required - 4+ years of Salesforce development experience with extensive knowledge of Sales Cloud, Apex, Visualforce, Lightning Web Components and the Force platform. - Understanding of Salesforce design and development best practices, and the ability to apply them to delivering business solutions. - A combination of analytical, technical, business and communication skills. The posting calls this out directly, because the role works across many functions. The day to day - Designing and developing secure, scalable technical solutions on Salesforce. - Analysing business processes and system implementations to identify inefficiencies and critical metrics. - Evaluating existing code and developing plans to reduce technical debt over time. - Working with technical and cross functional business teams to implement enhancements and projects, and to resolve incidents. - Building tools that scale revenue generating operations and improve sales efficiency. Location and working style Bengaluru. The posting states this is a hybrid position requiring 2 days per week in the Bengaluru office, and states plainly that relocation assistance will not be provided for this role. If you are not already in Bengaluru or willing to move at your own cost, that second sentence matters. Elsewhere the posting describes a flexible, employee led remote model and support for remote work where it aligns with operational requirements, which sits awkwardly beside the explicit two days per week line. Treat the two day requirement as the operative one, since it is the role specific statement. Honest fit guidance Salesforce development divides opinion among engineers, so decide honestly which side you are on. It is platform work, constrained by Salesforce's model and release cycle, and you will spend time on business process rather than pure computer science. Against that, it is well paid, in constant demand across India, and unusually portable between employers and industries. This posting is stronger than most Salesforce listings because it names technical debt reduction and architecture as part of the job rather than only feature configuration, and because the internal customer is revenue operations at a company with real scale. If you want Salesforce work with a different flavour, Okta has a Business Application Developer role on ServiceNow in this same edition at 3 to 5 years.
Required - 4+ years in enterprise end user computing, endpoint management or desktop engineering within cloud first environments. The day to day - Deploying, configuring and maintaining corporate managed endpoints across Windows, macOS, BYOD and mobile, in line with Zscaler security baselines, least privilege standards and automated lifecycle workflows. - Executing vulnerability management workflows using CrowdStrike and Zscaler UVM (Avalor), then triaging, prioritising and tracking remediation through Jira, ServiceNow and executive compliance dashboards. - Monitoring system performance and user satisfaction using Zscaler Digital Experience (ZDX) and Omnissa, and implementing self healing policies and proactive automation. - Working complex endpoint issues and security threats, conducting root cause analysis and documenting SOPs and runbooks for support teams. - Contributing to platform upgrades, virtualisation pilots and security tool rollouts across IT Operations, Security and business stakeholders. Reporting and team The posting places this in the IT Digital Employee department, reporting to the Manager, End User Engineering. Location and working style Bangalore, India, described in the posting as hybrid. Zscaler tags the role #LI-Hybrid and points to its published hybrid working model. Confirm the number of office days at the first screen. Honest fit guidance Be clear that this is corporate IT engineering, not work on the Zscaler security product that customers buy. That distinction decides whether this is the right career step for you. It is genuine engineering: automation, vulnerability management and endpoint architecture at global scale, and the Zero Trust framing means the security thinking is real rather than cosmetic. But it is internal IT, and progression runs toward IT engineering leadership rather than product security. The posting is candid that you will balance operational escalations against engineering projects. Ask in the interview roughly how that split lands week to week, because the answer varies enormously between companies and it is the single biggest factor in whether you will enjoy the job. Zscaler has three roles in this edition across very different functions: this one, an enterprise sales engineer in Mumbai and a threat researcher in Pune.
Required - 4+ years of experience in the machine learning domain, with expert level Python skills and deep familiarity with the standard data science toolkit: PyTorch, TensorFlow, XGBoost or LightGBM, Pandas and Scikit-learn. - Proficiency across the end to end ML lifecycle, from building robust pipelines on big data (Spark, SQL, Trino) through deploying and maintaining models in production using MLOps practices. - Hands on experience with ML infrastructure and orchestration tools such as Kubernetes, Docker, Airflow and Argo. - Software and data engineering best practices, applied in partnership with international MLOps and platform teams. The day to day - Developing and maintaining full lifecycle production ML pipelines, and acting as a technical anchor adapting global frameworks to India localised requirements. - Designing and productionising recommendation and classification models integrated directly into merchant facing products. - Identifying and resolving performance bottlenecks in training and inference across memory, latency and throughput. - Owning reusable AI components that form the foundation for scaling generative AI applications. - Partnering with international MLOps and platform departments to adopt internal tooling. Location and working style Bengaluru. Adyen states its position without ambiguity: it is an office first company that values in person collaboration and does not offer remote only roles. Take that at face value. If remote is what you need, this is not the posting for you, and the LiveKit and 6sense roles in this same edition are genuinely remote. Honest fit guidance The phrase to focus on is production ML services, not model research. Adyen wants an engineer who can own pipelines, deployment and performance, and the requirement list is weighted accordingly: MLOps tooling, Kubernetes, Airflow and Spark sit alongside the modelling libraries. If your experience is training models in notebooks and handing them over, this role will stretch you in the infrastructure direction. The India localisation thread is worth asking about. The posting describes adapting global frameworks for India specific requirements, which suggests genuine ownership rather than following a specification written elsewhere, but it also implies coordination with teams in other timezones. Ask how that works in practice. Payments is a demanding domain: high throughput, low tolerance for error and meaningful regulatory weight. That is what makes the engineering interesting.
Required - 4 to 6 years of experience in AI, automation, data science or analytics. - Bachelor's degree in Computer Science Engineering or a related technical field. - Proficiency in Python (Pandas, NumPy, Scikit-learn), able to write scripts for data processing, ELT pipelines, API calls and automation logic. - Strong SQL and data skills: writing queries and working with data structures, joins and aggregations. - Experience using AI to build agents that solve real world use cases, using frameworks or custom tooling. - Hands on experience with automation tools such as n8n, Zapier, Make, Workato or custom built automation. - Strong systems thinking: considering data flow, scalability and downstream impact rather than only the immediate output. - Experience using Claude Code or a similar AI coding assistant to build or configure MCP servers. - Experience integrating third party systems through APIs and webhooks. Preferred - Background in SaaS, particularly working with cross functional teams. The day to day - Building and refining AI agents to automate knowledge retrieval, extract intelligence and support decisions. - Designing and building automation pipelines that eliminate manual, repetitive processes. - Writing Python and SQL to extract, transform and analyse data from internal systems including Salesforce and the data warehouse, including scoring and prioritisation models. - Engaging cross functional teams to understand pain points and translate them into structured problem statements. - Identifying workflow inefficiencies and driving implementation end to end. - Independently scoping, sequencing and delivering technical projects. - Guiding or mentoring junior team members and acting as the go to resource for AI and automation capability across the organisation. On the title The posting says you will be overseeing the AI Center of Excellence and working directly with executive leadership. It describes mentoring junior team members, not managing them, and every technical requirement is hands on. Read this as a senior individual contributor role with organisational visibility, which is how it is grouped here. Location and working style Bangalore. No remote arrangement is stated. Honest fit guidance This is one of the more genuinely modern job descriptions in this edition. If you have been building agent workflows, wiring up MCP servers and automating internal processes, there are still relatively few roles that ask for exactly that, and fewer that put it in writing. The trade off is that it is internal tooling rather than customer facing product. Your users are colleagues, the problems come from stakeholder interviews, and success is measured in friction removed. Some engineers find that unusually satisfying because the feedback loop is short. Others miss shipping to customers. Know which you are. Executive visibility cuts both ways too: high leverage, but the work is shaped by what leadership considers a priority this quarter.