No roles match that combination.
Added July 24, 2026
What the posting asks for: - Professional experience with Ruby on Rails. - A background in site reliability or observability engineering: monitoring, alerting, SLOs, SLIs, runbooks, incident handling, and tools such as Prometheus, Grafana and OpenTelemetry. - Experience building anomaly detection, monitoring or risk management tooling. - Exposure to reporting data stores, especially ClickHouse, and the change data capture and event streaming pipelines that feed them (Siphon, NATS JetStream). - Experience with billing, financial or other business critical systems. - Experience owning a project from concept to production, including proposal, discussion, execution and monitoring. - Clear written communication in English, because the team is remote and largely asynchronous. Counts as a bonus: - Working knowledge of Python for anomaly detection and data work. - Hands on experience with Zuora or Salesforce. The day to day: designing metrics, logs and traces across the Monetization stack, building automated detection for billing and event anomalies and routing those alerts to the right feature team, writing reconciliation and data integrity checks across usage and billing pipelines, defining SLOs and SLIs, writing runbooks, taking part in incident handling, and reviewing other engineers' merge requests. You would report to the Engineering Manager for Observability, Monitoring and Integrations. Experience: GitLab publishes no years figure anywhere in this posting, so we have left it blank rather than guess. What the posting does say is that the role is open at both the Senior Software Engineer and Staff Software Engineer levels, and that GitLab welcomes candidates with varying levels of experience because many successful hires do not meet every requirement. Location: fully remote. GitLab states that all of its roles are remote, though some carry location based eligibility rules, so confirm yours with the recruiter early. Who should apply: a backend engineer who is comfortable in Rails and genuinely enjoys observability work. This is a greenfield team, so you would help set its operating rhythm and quality bar rather than inherit one. If you want a tightly specified ticket queue, this is not that.
What the posting asks for: - Professional experience working with Ruby on Rails. - Experience integrating with third party or enterprise APIs, including billing, CRM or automation platforms. - Strong API design skills: REST, GraphQL, contracts, versioning and backward compatibility. - Familiarity with event driven patterns such as webhooks and message based streaming. - Familiarity with PostgreSQL or a similar relational database, and with data integrity and governance concepts in production. - Systems thinking, and experience owning projects from concept through production. - Ability to communicate clearly in a remote, largely asynchronous environment. Counts as a bonus: - Familiarity with NATS JetStream. - Experience with subscription management or billing systems such as Zuora or Salesforce. The day to day: building and maintaining the integrations between CustomersDot, Monetization services and enterprise applications, defining and evolving API contracts, tracking failure rates and retry success and data integrity incidents, keeping data consistent across integrated financial systems, reviewing merge requests, and working with Product, Finance, IT, Sales and Support to turn cross system needs into reliable integrations. Experience: no years figure is published, so we left it blank rather than invent one. The posting states GitLab is hiring this role at the Software Engineer and Senior Software Engineer levels, and GitLab's standard note applies: they welcome candidates with varying levels of experience and many successful candidates do not meet every requirement. Of the four GitLab roles in today's list this is the one aimed lowest. Location: the posting lists Bangalore, but GitLab is a fully remote company and states that all of its roles are remote, with some carrying location based eligibility rules. Who should apply: a Rails engineer a few years in who wants API and integration depth rather than feature work, and who is comfortable being careful because the data is financial.
What the posting asks for: - Expert knowledge of cloud infrastructure security (AWS, GCP or Azure), container orchestration with Kubernetes, and related infrastructure and data security topics. - Proficiency in multiple programming languages (Go, Python, Ruby) with a track record of shipping production quality security tooling. - Extensive experience with Infrastructure as Code security (Terraform, Ansible, CloudFormation), policy as code and automated compliance. - Hands on experience applying AI to security workflows, with a view on where it creates real leverage. - A track record of leading multi team technical initiatives from an ambiguous problem statement to a measurable outcome, setting direction that peer teams adopt. - Strong written and verbal communication, including explaining security tradeoffs to senior leadership. - Familiarity with security certifications and frameworks: FedRAMP, ISO 27001, SOC 2, PCI DSS. The day to day: setting architectural patterns, reference implementations and foundational security automation; leading security initiatives from problem framing through delivery; running security reviews and threat modelling for complex infrastructure; setting the team's approach to AI assisted security engineering; acting as the authoritative technical voice for Infrastructure Security with stakeholders; and mentoring engineers. GitLab also expects the team to secure GitLab's own infrastructure using GitLab, which they call dogfooding. Experience: no years figure is published anywhere in the posting, so we left it blank. Staff at GitLab is a senior individual contributor level, and the responsibilities listed (multi quarter ambiguous initiatives, setting direction other teams follow) point well above entry level even though no number is given. Location: remote, and open to India, Israel, the United Kingdom and the United States. GitLab notes some roles carry location based eligibility rules. Who should apply: an experienced infrastructure or cloud security engineer who wants scope over a platform rather than a queue of findings, and who is comfortable writing the tooling instead of only reviewing it. This is a leadership role without direct reports.
What the posting asks for: - A proven track record of delivering actionable intelligence that measurably improved an organisation's security. - Experience working with a Threat Intelligence Platform and managing ingested and exported threat feeds. - Experience researching adversaries using OSINT and structured analytical techniques. - The ability to automate tasks by writing scripts or programs, preferably in Python. - Excellent written and verbal communication, with the ability to make complex topics clear. Counts as a bonus: - Experience reverse engineering malware, particularly macOS and Linux malware and malware delivered through code repositories. - Public blogs or open source work related to threat intelligence. The day to day: monitoring the threat landscape and raising ad hoc Flash Reports, administering the Threat Intelligence Platform and extending the open source, proprietary and internal collection pipeline, supporting incident response through malware analysis and threat actor tracking, collaborating on Purple Team Flash Operations where an emerging threat becomes a live exercise, building relationships with industry peers to share intelligence, and writing code and automation to make the team more efficient. Experience: GitLab publishes no years figure, so we left it blank. The posting describes the person as a seasoned threat intelligence engineer and the level is Senior, but no number is given and we will not invent one. Location: remote, open to Canada, India and the United States. Note the manager sits in Australia, so expect some meetings shifted towards Asia Pacific hours rather than a purely India schedule. Team context worth reading carefully: you would be the only dedicated person on this team, supported by Security Operations engineers who spend part of their time on threat intelligence. That is a lot of autonomy and also a lot of solitude. Security Operations at GitLab also covers SIRT, Trust and Safety, Signal Engineering, Red Team and Security Logging. Who should apply: someone who already does threat intelligence and wants to own a programme end to end rather than be one analyst among many. If you need a senior peer in the same specialism sitting next to you, read the team note again first.
What the posting asks for: - 7+ years of experience building campus or data centre network infrastructure, AWS cloud services and networking. - 5+ years with Cisco LAN, WAN and WiFi and Palo Alto Networks firewalls. - 3+ years with AWS cloud services and networking. - Advanced knowledge of IEEE 802 standards and core IETF protocols, including the 802.11 suite, TCP/IP, DNS, DHCP, and routing and switching protocols. - Hands on network monitoring knowledge. - Knowledge of network security, enough to implement security policy for compliance. - Client networking on Windows, Mac and Linux. - Experience troubleshooting network problems across different OSI layers. - A university degree in computer science or equivalent experience. Counts as a bonus: - Cisco CCNA or CCNP certification, and AWS certification. - Zscaler Zero Trust Systems experience or certification. - A scripting language with API automation, and Terraform for infrastructure as code. - Knowledge of ITIL, and project management skills. The day to day: building and supporting the global IT network, tracking network assets, reporting performance and availability metrics to IT leadership, working with stakeholder teams on future network needs, prioritising work using the Scaled Agile Framework, building tools to test and roll out new LAN and WAN systems, responding to incidents, and maintaining network design and standards documentation. Experience: the posting states 7+ years for the primary requirement. Read the three requirements together, because they stack: 7+ years overall on network infrastructure, of which 5+ on Cisco and Palo Alto and 3+ on AWS. Location and travel: remote within India, but restricted to Karnataka, Tamil Nadu, Telangana, Maharashtra and Delhi. Roughly 15 percent travel is expected. Who should apply: a network engineer with real data centre and campus experience who wants to stay hands on. Note this is corporate and internal infrastructure, not Twilio's carrier or product network, so it is closer to enterprise IT engineering than to telecom product work.
What the posting asks for: - Twilio product experience. The posting states this as a must, so it is the hard filter on this role. - 5+ years in Technical Support, Product Operations, Technical Account Management or Engineering, focused on complex technical products such as APIs, SaaS or telecommunications. - Experience in the technology industry, including APIs and VOIP, in either a development or a support capacity. Familiarity with customer or consumer trust applications is preferred. - Proven analytical skills using data tools such as Splunk, Datadog, Snowflake, SQL or Tableau to turn customer feedback and support trends into insight. - Excellent communication and influencing skills, since the job is largely persuading engineering to prioritise supportability work. Counts as a bonus: - Project management experience, or experience running programmes and product launches. - Proficiency in Python, Java or Node.js, enough to understand the developer experience. - Knowledge of design thinking or UX principles for spotting friction in customer journeys. The day to day: embedding supportability requirements into the earliest stages of the product development lifecycle by joining design reviews and technical planning with R&D, analysing support data to build business cases, specifying proactive product features such as clearer error messages and diagnostic tools, orchestrating global operations readiness for new features, and translating complex customer use cases into requirements. Experience: the posting states 5+ years, and accepts that experience from four different directions (support, product operations, technical account management or engineering), which makes it more open than the title suggests. Location: remote within India, restricted to Karnataka, Tamil Nadu, Telangana, Maharashtra and Delhi. Who should apply: someone who has done deep technical support or technical account management on an API product, is tired of fixing the same issue repeatedly, and wants to attack the cause upstream instead. Twilio also says openly that it values non traditional career paths for this role. The Twilio product experience requirement is the real gate, so if you have never used Twilio in anger, expect a hard time.
What the posting asks for: - 15+ years of experience designing and scaling distributed systems and platforms. - A demonstrated ability to set technical vision and strategy at enterprise or company wide level. - Expertise in system design, reliability, scalability, security and cost optimisation for large scale architectures. - Experience leading cross functional initiatives and resolving highly complex, ambiguous technical problems. - A proven record of mentoring senior engineering talent and raising organisational standards. - Exceptional written and verbal communication, influence and leadership skills. - A bachelor's degree in computer science, engineering or a related field, or equivalent practical experience. Counts as a bonus: - Cloud native, multi region systems and architecture patterns. - A history of driving engineering standards across multiple business units or product lines. - Experience with observability, platform capabilities and data architecture at scale. - Open source project leadership or significant external technical impact. - Prior experience at a high growth SaaS, communications or platform company. The day to day: setting and communicating long term architectural vision, leading cross product architecture reviews, standardising engineering practices, driving foundational technical investments, solving the hardest platform wide problems, mentoring principal and staff engineers, and partnering with product, engineering and executive leaders on strategic direction. Experience: the posting states 15+ years explicitly. This is genuinely a senior role and the number is not padding. Location and travel: remote within India, restricted to Karnataka, Telangana, Maharashtra, Delhi and Tamil Nadu. Occasional travel for project or team meetings. Who should apply: a principal or staff engineer with well over a decade of distributed systems work who wants architecture scope across an entire company and does not want to move into management to get it. If you are earlier in your career, the other two Twilio roles in today's list sit far lower.
What the posting asks for: - 15+ years with big data technologies such as Apache Spark, Kafka, cloud native services and data lakes, in a customer facing post sales, technical architecture or consulting role. - 6+ years working on big data architectures independently. - 2+ years on AI based implementations including RAG, MCP and context engineering. - Strong experience within the Databricks ecosystem. - Comfortable writing code in either Python or Scala. - Experience across cloud platforms: GCP, AWS or Azure. - Documentation and whiteboarding skills. - Excellent problem solving and critical thinking, turning business problems into reliable technical products. - Strong stakeholder management, working with both technical people and domain experts. The day to day: collaborating on customer big data projects, creating reference architectures and how to guides, building production ready tooling, advising strategic customers on transformational initiatives including third party migrations, providing architecture and design expertise, partnering with Engineering and Customer Support to feed issues back into the product, and running several diverse client projects at once while managing risk and building trust. Experience: the posting states 15+ years as the headline requirement. Read the three numbers as a stack rather than alternatives: 15+ years overall in a customer facing big data role, 6+ years on big data architectures independently, and 2+ years specifically on AI implementations. The AI requirement is the newest and probably the one most people will fail, not the 15. Location: remote within India. This is one of very few remote senior data roles on the board today. Who should apply: a senior data architect or consultant who genuinely likes customer facing delivery. If you want to build product rather than deliver projects, this is the wrong side of Databricks. Note also that the AI expectation is concrete, not decorative: they want RAG and MCP work you have actually shipped.
What the posting asks for: - 5+ years in a data engineering, data science, technical architecture or similar pre sales or consulting role. - 5+ years with big data technologies including Apache Spark, AI, data science, data engineering, Hadoop and Cassandra. - Strong consulting and customer facing experience with external clients across a variety of industry markets. - Coding experience in Python, R, Java, Apache Spark or Scala. - Experience building distributed data systems. - Solutions built on a public cloud: AWS, Azure or GCP. - Availability to travel to customers in your region. Counts as a bonus: - Databricks certification. The day to day: partnering with the sales team and giving technical leadership so customers understand how Databricks solves their problem, helping develop the book of business and define account strategies, consulting on big data architectures, implementing proofs of concept for strategic projects, validating integrations with cloud services and home grown tools, supporting fellow Solutions Architects, and promoting and recruiting contributors for Databricks backed open source projects such as Spark, Delta Lake and MLflow. Experience: the posting states 5+ years, twice, once for the pre sales or consulting side and once for big data technologies. Compare before you apply: Databricks currently has the same job title live in Delhi at 5+, Bengaluru at 8+ and Pune at 12+. The title alone tells you nothing about the bar. Location: hybrid, based in Delhi, with travel to customers in the region. Who should apply: a data engineer or data scientist who enjoys the customer conversation and wants to move into pre sales without waiting until 10 years in. Be clear eyed that this is a commercial role attached to a sales team, with a book of business and account strategy, so it is not a pure engineering job.
What the posting asks for: - 15+ years of experience in a hands on software engineering role. - A bachelor's or master's degree, preferably in computer science, or equivalent experience. - Experience building, leading and architecting production systems or features with broad impact. - Demonstrated technical leadership: leading project teams, setting technical direction and strategy, prototyping to iterate on ideas, and working across Product, Design and Operations. - Strong communication and collaboration with both technical and non technical partners, including driving initiatives across teams, departments and leadership. - A track record of levelling up the people around you. - Proven experience defining product or technical strategy and getting cross functional leaders aligned behind it. The day to day: working with other senior leaders to define long term technical strategy and architecture, establishing technical vision and leading the work to architect and launch reliable and scalable systems, giving a balanced critical view of new and existing technologies, influencing cross functional partners, leading multi team technical initiatives, aligning technical effort with business outcomes, and raising engineering quality through design and code reviews, mentorship and hands on implementation. Experience: the posting states 15+ years in a hands on software engineering role. Airbnb is explicit that this stays hands on, so it is not an architecture role that has drifted away from code. Location: remote and eligible anywhere within India. The role may include occasional work at an Airbnb office or attendance at offsites, agreed with your manager. Remote roles at this level and in payments are uncommon, which is the main reason this one is worth a look. Who should apply: a very experienced engineer who wants payments scale and cross team architectural ownership while staying an individual contributor. If you are below roughly a decade of experience this is not a stretch application, it is the wrong role, and there are lower bands elsewhere in today's list.
What the posting asks for: - A bachelor's or master's degree or equivalent in computer science or a related field. - 2 to 5 years of relevant work experience. - Proficiency in one or more general purpose programming languages: Java, C, C++, Scala, Python or C#. - Rubrik describes its engineers as self starters who manage themselves, which is worth taking at face value in a distributed systems team. Counts as a bonus: - Prior experience with C++ specifically. - Google Cloud Platform, AWS, Azure or other public cloud technologies. - Experience with two or more of: Unix or Linux environments, Windows environments, distributed systems, networking, developing large software systems, file systems, storage systems, hypervisors, databases, or security software development. The day to day: designing, developing, testing, deploying and improving the software; managing your own projects, priorities, deadlines and deliverables; identifying and fixing bottlenecks in the software stack; and diagnosing and resolving problems inside complex customer environments. Experience: the posting states 2 to 5 years, which is the real floor and ceiling. Of everything in today's edition this is the closest thing to a role a recent graduate can grow into, though it is not a fresher posting and we are not going to pretend otherwise. Location: Bengaluru. A note on the link: rubrik.com blocks automated requests, so this posting was verified live through the Greenhouse jobs API rather than by fetching the page. It was published on 23 July 2026 and is open. The link works normally in a browser. Who should apply: someone two to five years in who wants file systems, storage and distributed systems rather than application or web work. If you have C++ and Linux and you have been stuck on CRUD services, this is the kind of role that changes the shape of your career. Expect systems design and debugging to dominate the interview.
What the posting asks for: - 2 to 5 years of experience, stated plainly at the end of the posting. - Python and SQL. The posting marks both as required for this role. - Hands on experience with Windows, Linux or Mac environments. - Knowledge of at least one programming language such as PHP, Java or ASP.Net, and of the Android and iOS platforms. - The ability to diagnose and troubleshoot technical issues and give step by step technical help. - Familiarity with remote desktop applications. - Excellent problem solving and communication skills. - A good grasp of general IT terminology and concepts. The day to day: managing merchant accounts during integration, working with the product and technology teams to understand different product flows, attending meetings and calls with merchants' technical and business teams, understanding a merchant's flow and requirements and proposing a solution, researching and diagnosing integration issues through to resolution, asking targeted questions to find the root of a problem quickly, and automating the recurring problems so they stop coming back. Experience: the posting states 2 to 5 years directly. This is one of the lower bars in today's list and one of only a handful under three years. Location: Bangalore, at PhonePe's office. Benefits worth knowing, since PhonePe lists them in detail for full time employees: medical, critical illness, accident and life insurance; an employee assistance programme and an onsite medical centre; maternity, paternity, adoption and day care support; relocation and transfer support; provident fund, gratuity, NPS and leave encashment; and higher education assistance. Who should apply: someone with two to five years who likes solving other people's integration problems and wants fintech scale on their CV. Be honest with yourself about the customer facing half: a large share of this job is calls with merchants, not heads down coding. If you want pure backend work, PhonePe's engineering roles are a different queue.
What the posting asks for: - Up to 5 years of experience building end to end applications. Read that carefully: it is an upper bound, not a minimum, which is why this role is open to people early in their careers. - A strong understanding of AI and machine learning fundamentals: NLP, LLMs, embeddings and prompt engineering. - Proficiency in Python and working with REST or GraphQL APIs. - Experience with prototyping frameworks such as Flask, FastAPI or Streamlit. - Familiarity with go to market systems such as Salesforce, HubSpot or Marketo, or BI tools such as Tableau or Looker. - Strong problem solving skills and the ability to prototype quickly. Abilities the posting calls out separately: - Turning messy go to market data into usable inputs for AI models. - Mapping AI outputs back into real workflows and processes. - Explaining technical solutions clearly to non technical people. - Balancing fast experimentation against reliability and compliance. The day to day: building internal applications on LLMs and AI APIs such as OpenAI and Anthropic, integrating AI into go to market tools, writing scripts and automations for data enrichment and reporting, rapidly testing new models and APIs and building MVPs, documenting performance and accuracy for each use case, working with Marketing, Sales and BizOps to find their pain points, running demos and training for internal users, and maintaining what you deploy. How success is measured, which the posting states unusually clearly: two or three working AI prototypes that go to market teams actively use, at least two workflows automated or optimised, documentation good enough to make the work transferable, and measurable gains in productivity. Experience: up to 5 years, with no minimum stated anywhere in the posting. Location: Bangalore. Who should apply: anyone from roughly zero to five years who can actually build with LLM APIs and wants a role where shipping a working prototype counts more than pedigree. The honest caveat is that these are internal tools for sales and marketing teams, not customer facing product engineering, so weigh that against the low bar to entry.
What the posting asks for: - 2 to 6 years of experience in cyber security, pre sales or consulting. Partner or channel experience is preferred but not required. - A strong understanding of cyber security fundamentals: web, cloud, SIEM, IDS and IPS, SOAR, email security, and threat intelligence or dark web work. - Familiarity with the cyber security ecosystem and how tools fit together in a SOC, across small, medium and large enterprises. - The ability to deliver demos and proofs of concept and explain solutions clearly. - Strong communication for both technical and business audiences, and good presentation skills. - A self driven, proactive approach. - Comfort working across sales, product, research and marketing. Counts as a bonus: - Certifications such as CompTIA Security+ or CISSP. The day to day: prospecting, onboarding and managing partner companies and helping them generate leads, training partners to understand and position the product, managing RFP and RFI responses and writing solution documents and sales proposals, running product demos, proofs of concept and customer presentations, working with sales teams and partners to close deals, organising workshops and webinars, sharing research and threat intelligence with partners, and representing partner feedback back inside CloudSEK. Experience: the posting states 2 to 6 years. That band is wide on purpose and the lower end is real. Location: Bengaluru, with travel as required to meet partners and customers. CloudSEK lists flexible working hours and food at the office. Company context worth knowing: founded 2015, headquartered in Singapore, Series A of 7 million dollars in 2021 led by MassMutual Ventures, and 19 million dollars raised in 2025 led by Tenacity Ventures and Commvault. It won the NASSCOM DSCI Security Product Company of the Year award in 2020. Who should apply: someone with a security background who is good in front of people and wants the commercial side without leaving the technology behind. This is a customer facing and partner facing job, so if you want to be heads down in a SOC, it is not for you.
What the posting asks for: - 3+ years of hands on experience in applied machine learning and data science, with a master's or PhD in computer science, machine learning, data science, statistics or a related field, or appropriate experience in place of the degree. - A strong background in machine learning, deep learning and NLP, with proven experience training and fine tuning large scale models such as LLMs, transformers and diffusion models. - Hands on expertise with parameter efficient fine tuning: LoRA, prefix tuning, adapters and quantization aware training. - Proficiency in PyTorch, TensorFlow and the Hugging Face ecosystem. - A basic understanding of MLOps: experiment tracking, model versioning, CI and CD for ML pipelines, and production deployment. - Experience with large datasets, feature engineering and data pipelines using Spark, Databricks or cloud native ML services such as AWS SageMaker, GCP Vertex AI or Azure ML. - Knowledge of GPU and TPU optimisation, mixed precision training and scaling ML workloads. - Excellent communication, including explaining complex ML concepts to non technical audiences. Marked mandatory in the posting: - Demonstrated success adapting foundation models to domain specific applications through fine tuning or transfer learning. - A strong ability to design, evaluate and improve models using robust validation strategies, bias and fairness checks, and performance optimisation. Counts as a bonus: - Distributed training frameworks such as DeepSpeed, PyTorch Lightning or Ray. - Proven ability to mentor junior applied scientists and ML engineers. Experience: the posting states 3+ years. Note the degree expectation is unusually explicit here, and the two mandatory skills are about fine tuning and evaluation rather than years served. Location: Bengaluru. CommerceIQ is headquartered in Mountain View with teams across the US, India, Canada and the UK. Who should apply: someone three or more years into applied ML who has actually fine tuned models rather than only called APIs. If your experience is dashboards and reporting, the mandatory requirements will screen you out, and MongoDB's data analyst role in today's list is a better fit.
What the posting asks for, at 3+ years of experience: - Knowledge of client server architectures and network design. - Solid knowledge of Cisco IOS and NxOS and other network operating systems. - Routing protocols including static routing, BGP and OSPF. - NAT, PAT and PBR. - Strong knowledge of L2 protocols. - WAN, LAN and data centre network architectures. - Network design, network operation or network automation. - Multicast configuration (PIM, IGMP). - Firewall and VPN technology including site to site VPN and GRE. - Knowledge of Unix or Linux. - Knowledge of data centre installation and cabling standards. Counts as a bonus: - Basic scripting, for example Python. - CCNA or higher. - Systems administration experience. The day to day: working with traders to add or change network connectivity to financial exchanges, troubleshooting and analysing network performance problems, helping design networks for new offices and data centres, finding low latency solutions in existing networks, supporting production, office and end user environments, performing market connectivity tests and circuit migrations, assisting with data centre migrations, liaising with third parties over communication lines and data centre infrastructure, and coordinating with remote hands technicians globally. Experience: the posting states the ideal candidate has 3+ years, and the skill list that follows is what those years should contain. Location: Gurugram, in office. Graviton describes cubicle free offices and a non hierarchical culture. Benefits listed in the posting: competitive compensation, an annual international team outing, fully covered commuting expenses, best in class health insurance, catered breakfast and lunch, four weeks of annual leave plus market holidays, gym and sports club memberships, and regular social events. Who should apply: a network engineer around three years in who wants low latency and exchange connectivity work rather than a corporate IT network. Trading firms pay well and expect precision, and the feedback loop when something is slow is immediate.
What the posting asks for: - 3+ years of software development experience in fast paced environments and modern stacks. - A strong technical foundation across any of frontend, backend, cloud, AI and ML, or DevOps. The posting names React, Angular, Node, Spring Boot, AWS, Jenkins and generative AI as examples. - A strategic but hands on product thinker, able to drive execution from concept to delivery. - Skill at working closely with engineers, speaking their language, and turning complex technical problems into clear product direction. - Comfort with tools such as GitHub, JIRA, Slack and analytics platforms. Counts as a bonus: - Contributions to open source. - Exposure to open source communities and other developer ecosystems. - Familiarity with AI driven workflows for scaling products. The day to day: building and managing a global network of experts who create coding challenges, owning the product roadmap for the coding challenge platform and content ecosystem, building tools that scale content delivery and support emerging technologies, partnering with customers to understand their workflows, using data and automation and AI to streamline content creation and review, and making sure everything shipped holds up on fairness, validity and developer experience. HackerRank says you will thrive here if you are a builder who likes creating scalable systems from scratch, are not slowed down by ambiguity, care about developer experience, and are energised by collaboration. Experience: the posting states 3+ years of software development experience. Location: hybrid in Bangalore, so factor in office days. Company context: HackerRank is used by over 2,500 companies including NVIDIA, Amazon and Microsoft, and positions itself around skills rather than pedigree. Who should apply: an engineer around three years in who is drawn to product and content work and wants ownership of a platform millions of developers touch. The honest caveat is that this is not a coding heavy role: the technical foundation is there so you can direct the product credibly, and the day to day is roadmap, tooling and expert network management.
What the posting asks for: - A BS or MS in computer science or a closely related technical field, or equivalent demonstrated experience. - 3+ years building ML training infrastructure or large scale distributed systems. The posting adds that exceptional early career candidates with a strong systems background will be considered, which is worth noting if you are under three years. - Hands on experience training large models with distributed training frameworks: Megatron LM, DeepSpeed, FSDP, NeMo or equivalent. The posting says you should have been on call for a real pretraining run. - Deep working knowledge of GPU architecture, the CUDA programming model, and profiling tools such as Nsight and the PyTorch profiler. - Strong PyTorch internals knowledge, comfortable reading and modifying low level training code rather than only using high level APIs. - Meaningful open source contributions in the training infrastructure ecosystem: Megatron, DeepSpeed, PyTorch, vLLM, Triton, NCCL or similar. Counts as a bonus: - Custom CUDA or Triton kernel development with measurable wins on real workloads. - Direct experience training models at 10B+ parameters or on 1000+ GPU clusters. - Cluster orchestration and job scheduling at scale (Slurm, Kubernetes). - Mixed precision (BF16, FP8), quantization aware training or similar numerical work in production runs. - First author papers or technical reports on training systems, scaling or model efficiency. The day to day: building and pushing the limits of the distributed training stack across large GPU clusters, designing parallelism strategies and reasoning about which combinations suit which architectures and scales, profiling and optimising end to end throughput including kernel performance, communication overlap, memory layout, checkpointing and data loading, writing and tuning custom GPU kernels, owning the reliability of long running jobs through fault tolerance and checkpoint integrity and deterministic restarts, and partnering with researchers and the data team. Experience: the posting states 3+ years, with an explicit exception for exceptional early career systems engineers. Location: Bengaluru. Who should apply: a systems engineer who wants frontier model training work without leaving India. Sarvam is direct that the bar is high and the cost of mistakes is measured in weeks. If you have real distributed training experience, very few Indian employers can offer this problem.
What the posting asks for: - 5+ years building infrastructure or platform software, with a track record of systems you designed and shipped. The posting is pointed about this: services and control planes others built on, not scripts and glue. - Strong software engineering in Go or Python, with the judgement to build maintainable systems and the depth to debug them in production. - Kubernetes at the controller and internals level. You should have written operators or controllers, understand the scheduler and API machinery, and know where the abstractions leak. - Working literacy in GPU specific platform constraints: MIG and GPU sharing, gang scheduling, topology and fabric aware placement, and why training and serving contend for the same hardware. - A product mindset toward internal users, measuring the platform by adoption and self service rather than tickets closed. - The range to own a capability end to end, from design through rollout to the documentation that makes it self serve. Counts as a bonus: - Having built a serving, inference or training platform: routing, autoscaling and rollout for model endpoints at scale. - GPU scheduling systems in multi tenant production (Kueue, Volcano, Slurm, Run:ai or custom). - Multi tenant isolation (MIG, MPS, time slicing) shipped as a self service capability. - Deep Kubernetes networking: CNI internals, custom network components, or RDMA and SR-IOV in pods. - On premise GPU platform work, including multi vendor or Indian NCP environments. - Open source contributions to Kubernetes, scheduling or GPU platform projects. The surface area, from the posting: the serving platform control plane with routing, canary and blue green rollouts and traffic splitting; the scaling and elasticity layer for both training and serving; scheduling and orchestration with gang scheduling, priority and preemption and quota enforcement; multi tenancy, RBAC and isolation; platform networking; observability and cost tooling; the storage and data path; developer experience through CLI, SDK and APIs; and provisioning through Terraform, Crossplane or operators. You would take one capability and build it end to end rather than own all of it at once. Experience: the posting states 5+ years. Location: Bengaluru. Who should apply: a platform engineer who has built control planes rather than maintained them, and who wants GPU scale problems. If your Kubernetes experience is writing manifests rather than controllers, the bar here is above you.
What the posting asks for: - A bachelor's degree in computer science, engineering or a related technical field. - 3+ years in conversational AI, solution engineering, system integration, or delivering AI and LLM based applications in customer environments. - Strong ability to lead customer facing discussions, from deep technical troubleshooting to weekly project demos, and to explain complex concepts to non technical audiences. - Strong hands on skills in prompt design, workflow building and API integration (SIP, Twilio, Amazon Connect and similar). - Familiarity with LLMs (GPT, Claude, Gemini), vector databases, and orchestration frameworks such as LangChain and LlamaIndex. - Working knowledge of retrieval augmented generation: concepts, implementation patterns and performance optimisation. - Programming experience in Python, JavaScript or similar for scripting and integrations. - A strong problem solving mindset, finding workarounds and adapting to each customer's ecosystem. Counts as a bonus: - Integration platforms such as n8n or Zapier, and proficiency in API integration and data flow management. - Familiarity with telephony or voice systems (SIP, CCaaS, PSTN). The day to day: owning AI agent implementation including prompt design, workflow configuration, integrations, telephony setup and evaluation frameworks; acting as the primary technical partner for customers through demos and feedback; configuring API integrations with authentication, data mapping and error handling; setting up SIP, CCaaS and PSTN routing and troubleshooting call quality; refining prompts and monitoring performance against automation and containment targets; and escalating platform gaps to product and engineering. Experience: the posting states 3+ years, and accepts several entry paths into that (conversational AI, solution engineering, system integration or software engineering with AI delivery). Location: Bengaluru. Benefits listed: medical insurance for self and family with free online doctor consultations, accident and group term life insurance, privilege and sick leave, parental leave, an annual learning and development allowance, and flexible tax benefits including meal cards. Who should apply: someone three or more years in who wants applied LLM work with a real deployment target and does not mind that the customer is in the room. If you want to train models, this is the wrong role and Sarvam's postings in today's list are the right ones.
What the posting asks for: - A bachelor's degree, with a technical major such as engineering preferred. An advanced degree is a plus. - 4+ years of experience in a similar role. - A solid technical background with a demonstrable understanding of AI and machine learning. - SaaS experience, which the posting marks as essential. - Experience with tools such as Zendesk, Confluence and JIRA. - Excellent client facing and internal communication skills. - Excellent written and verbal English. Counts as an advantage: - Python or other scripting experience. The day to day: front ending all customer reported issues, reviewing and troubleshooting them within the agreed SLA, managing customer expectations as the point of contact for service issues, proactively diagnosing and analysing problems on the platform, researching alternative solutions and workarounds, escalating internally and owning issues through to resolution, running regular tool upgrades and monitoring the platform, documenting issues and solutions into the knowledge base including SOPs and service notes and recorded videos, and becoming a subject matter expert on the platform. Experience: the posting states 4+ years in a similar role. Location: Bengaluru. What the posting offers beyond the work, in its own words: hands on exposure to real technical problems, a contribution to pre release testing and product quality, ownership, and compensation and benefits closer to a larger established company than the stage would suggest. Benefits listed include medical insurance for self and family with free online doctor consultations, accident and group term life cover, privilege and sick leave, parental leave, an annual learning and development allowance, and flexible tax benefits. Who should apply: a support engineer with four or more years on a SaaS product who wants to move towards AI products and eventually towards solutions or product roles. Readers asked for customer facing technical roles by name, and this is one of the more technical ones in that group.
What the posting asks for: - 3 to 5 years of hands on experience with IAM technologies and solutions. The header states the band as 3 to 6 years, and the posting adds that senior level candidates with broader security expertise will also be considered. - Demonstrated expertise in Microsoft Entra ID, including administration and configuration. - A solid understanding of AWS IAM: identity federation, cross account access and policy management. - Experience with at least one privileged access management solution: Delinea Secret Server, BeyondTrust, CyberArk or similar. - Strong understanding of authentication and authorisation protocols: OAuth, SAML, LDAP and Kerberos. - Knowledge of compliance frameworks: Zero Trust, NIST, SOC 2 and ISO 27001. - Excellent communication and documentation skills. Counts as a bonus: - SC-300 (Microsoft Certified Identity and Access Administrator Associate) or similar. - Experience designing and securing AI agent architectures and autonomous workflows, and hands on work with Copilot Studio agent security. - Knowledge of Model Context Protocol and agent to service authentication patterns. - RBAC model design across complex application ecosystems. - Automating provisioning and deprovisioning with Okta, ServiceNow or Microsoft Identity Manager. - Multi cloud experience (Azure, AWS, GCP), Zero Trust architecture, scripting in PowerShell, Python or Bash, and identity first incident response. The day to day: designing and maintaining identity governance in Entra ID including provisioning, authentication policies and conditional access; managing AWS IAM policies and roles across accounts on least privilege; running PAM to monitor and audit privileged activity; configuring MFA, SSO and federation across hybrid environments; running security audits and access reviews; integrating IAM with enterprise and SaaS applications; managing access for AI agents including scope limits, token management and service principal governance; designing RBAC models; automating provisioning and deprovisioning; and responding to identity compromise incidents. Experience: the posting gives 3 to 6 years in the header and 3 to 5 years in the required qualifications. We have published the wider band because the posting also invites more senior applicants. Location: Bengaluru. Who should apply: an IAM or cloud security engineer around three to six years in. The AI agent identity work is the differentiator: it is early enough that few candidates will have it, so a strong IAM background plus genuine curiosity about agent authentication is likely to be competitive.
What the posting asks for: - 4+ years, stated in the header, with total industry experience of around 4 to 7 years stated in the body. - A BTech, MTech or MS in computer science or a related field from a reputed university. - Programming experience in Python, Ruby, Perl or equivalent, which the posting marks as a must. - Good knowledge and experience of a configuration management tool such as Ansible. - Good knowledge and experience of provisioning tools such as Terraform. - Good knowledge and experience with AWS. - Experience setting up CI and CD pipelines. - Experience, in an individual capacity, managing multiple live SaaS applications with high volume, high load, low latency and 24x7 availability. - Experience setting up web servers such as Apache, application servers such as Tomcat or WebSphere, and both relational and NoSQL databases. - Good knowledge of UNIX and Linux administration tools. - Good knowledge of security best practices and tools such as firewalls and VPNs. - Good knowledge of networking concepts. - The ability to troubleshoot quickly. The day to day: writing scripts to build the infrastructure that keeps Netradyne's services available 24x7, setting up monitoring and alerting, troubleshooting issues reported across multiple environments, and triaging production issues with timely responses to customers. Experience: the posting states 4+ years in its header and around 4 to 7 years in the body, so we published the band. Location and work model, both stated explicitly in the posting: on site, five days a week in the office, at HM Tech Park in Whitefield, Bangalore, on a general shift. If you are looking for remote or hybrid, this one is neither, and today's list has nine remote roles instead. Company context: Netradyne is headquartered in San Diego with offices in San Francisco, Nashville, the UK and Bangalore, was founded in 2015, and reports growth exceeding four times year over year. Who should apply: a DevOps or SRE engineer with four to seven years who has personally carried production SaaS availability and lives near enough to Whitefield for a five day office week.
Mandatory skills from the posting: - Strong computer science fundamentals across data structures, algorithms and system design. - Deep hands on backend experience with Java and Spring Boot. - Strong grounding in distributed systems concepts: consistency, durability, retries, idempotency, backpressure, partitioning and resilience. - Practical experience with Kafka, Kinesis, Pulsar or similar. - Experience operating production systems, including on call, incidents and postmortems. - Excellent communication and technical leadership. Preferred: - Experience building high throughput ingestion or streaming systems. - Exposure to compliance heavy or audit driven domains such as transportation, fintech or healthcare. - Experience with edge or intermittently connected devices. - Hands on work with observability stacks. - Prior experience with ELD, HOS or telematics. The day to day, grouped as the posting groups it. Architecture and technical ownership: owning the architecture, design and evolution of platform services, driving system design for large cross service features from ingestion to downstream consumers, and defining clean service boundaries, APIs and data contracts. Platform and systems development: designing scalable high throughput ingestion pipelines for logs, telematics and event data, building streaming and batch workflows, translating regulatory requirements into system guardrails, and ensuring correctness, ordering, idempotency and fault tolerance. Reliability and observability: defining and upholding SLOs for latency, availability and data accuracy, championing logging, monitoring, tracing and alerting, and designing for backpressure, graceful degradation and recovery. Data modelling and storage: designing data models and partitioning strategies for hot and cold data and selecting between SQL, NoSQL, time series and object storage on scale, performance and cost. Plus cross team collaboration, design reviews and RFCs, and mentoring engineers. Experience: the posting states 6+ years in its header. Staff here is a senior individual contributor role with mentoring attached, not a management position. Location and work model: on site five days a week at HM Tech Park, Whitefield, Bangalore, general shift. Who should apply: a backend engineer with six or more years in Java who wants genuine scale and ownership of a domain rather than a feature team. The five day office requirement is the main thing to weigh.
What the posting asks for: - 3+ years of hands on analytics experience, with a focus on people or HR analytics preferred. - Advanced SQL, comfortable manipulating very large datasets. - Proficiency in Python or R with a strong focus on data wrangling and analysis. - Extensive experience with Tableau or another leading visualisation tool, which the posting marks as required. - Familiarity with data architecture fundamentals and data warehousing. - Proficiency with data modelling and data quality best practices. - Demonstrated ability to communicate and set priorities with stakeholders at all levels. - Highly collaborative and organised with strong attention to detail. - Comfort with ambiguity and the ability to work in a self guided way. Preferred but explicitly not required: - Experience analysing complex people data such as headcount, attrition, recruiting metrics and compensation. - Exposure to modern cloud data warehouses. The day to day: partnering with People teams across compensation, recruiting and talent development to understand their questions and turn analyses into recommendations, helping build the roadmap for people data investments, working with data engineering and HRIS to create and manage a curated central repository, designing automated dashboards so stakeholders can self serve, triaging analytical and reporting requests from across the People team, developing data governance and quality processes, and communicating findings to non technical audiences. Experience: the posting states 3+ years of hands on analytics experience. The domain preference is soft; the SQL, Python or R and Tableau requirements are the hard ones. Location: Gurugram, hybrid. MongoDB states it is looking to speak to candidates based in Gurugram for this model. Who should apply: an analyst three or more years in with strong SQL who wants a well defined stakeholder group and a chance to build the data foundation rather than inherit it. Be clear that this is people and HR data, not product or revenue analytics, which is a genuine specialisation and not everyone's interest. If the domain does not appeal, MongoDB's engineering roles in today's list are a different path.
What the posting asks for: - 5+ years of experience building distributed systems or foundational cloud services at scale, with an interest in working with Python, Go and Java. - A strong background building core components for high scale compute and data distributed systems. - Proven success designing, writing, testing, debugging and performance tuning, with a strong grip on computer science fundamentals, in large and long lived codebases. - A track record of identifying problems, implementing solutions and delivering complex projects in distributed systems or databases. - Good verbal and written technical communication and a desire to collaborate. - Eagerness to learn. Counts as a bonus: - Containerisation and orchestration platforms such as Kubernetes. - AI frameworks and tools. The day to day: working with research, product management, product engineering, product design and other teams to define the first version and future evolution of the service; designing, building and delivering well tested core pieces of the platform; contributing to architecture, code reviews, development practices and developer experience as the team and product grow; and mentoring other engineers while owning projects outright. Experience: the posting states 5+ years. Location: Gurugram, hybrid. MongoDB states it is looking to speak to candidates based in Gurugram for this working model. Company context: MongoDB has over 60,000 customers including 75 percent of the Fortune 100, and MongoDB Atlas runs across AWS, Google Cloud and Azure. Who should apply: a backend or distributed systems engineer with five or more years who wants greenfield work on a real product inside a large company, which is a rarer combination than it sounds. If you want the operational side of the same platform instead, MongoDB's Senior Site Reliability Engineer role is in today's list and sits on the same team.
What the posting asks for: - 6+ years of experience building and operating distributed systems, with proficiency in Python, Go or a similar language. - A strong background in software development and operating distributed systems. - Experience operating Kubernetes in production and debugging below the abstraction layer, including scheduling, cluster networking and node level issues. - Expertise in cloud infrastructure platforms: AWS, Google Cloud or Azure. - A strong understanding of Linux internals and networking concepts such as TCP/IP, DNS, TLS and routing. - A customer focused mindset and strong technical communication. - A strong bias for efficient processes, operational simplicity and automation over manual work. Counts as a bonus: - Kubernetes networking such as Istio or Cilium, service mesh or edge load balancing in production. - Secure multi tenant runtime environments at scale. - Multi cloud infrastructure management. - Virtualisation or workload isolation technologies. The day to day: operating and improving the multi tenant Kubernetes infrastructure that runs customer workloads, building for reliability so services and infrastructure are available, resilient, fault tolerant and self healing, identifying and configuring the key metrics that detect incidents and quantify service health and performance, taking part in a 24/7 on call rotation to resolve platform infrastructure issues, and mentoring early career SREs while shaping the team's operational practices. Experience: the posting states 6+ years. On call: a 24/7 rotation is stated explicitly in the posting. Factor that in rather than discovering it at offer stage. Location: Gurugram, hybrid. MongoDB states it wants candidates based in Gurugram for this model. Who should apply: an SRE with six or more years who wants Kubernetes at multi tenant scale and is comfortable being early on a platform team, which means writing the operational practices rather than following them. If you would rather build the platform than run it, the Senior Software Engineer role on the same team is in today's list.
What the posting asks for: - A bachelor's degree in computer science, information technology, business or a related technical discipline. - 4 to 8 years of progressive, deep technical experience in IT infrastructure, system engineering and workplace operations. - Subject matter expertise in Jamf Pro, Apple Business Manager and corporate device enrolment profiles. Active Jamf certifications (200, 300 or higher) are highly preferred. - Master level administrative knowledge of corporate Google Workspace and Microsoft 365. - Deep technical understanding of IDaaS, single sign on integrations, SAML and OIDC protocols, and lifecycle provisioning through Okta or Azure AD. - Exceptional troubleshooting on modern macOS and Windows, with the ability to write Bash and PowerShell scripts to automate repetitive work. - A proactive, consultative approach, with the presence to mentor junior peers and explain complex systems to non technical stakeholders. The day to day: acting as the subject matter expert for internal infrastructure and handling advanced L3 escalations and complex architectural challenges, administering and tuning Google Workspace and Microsoft 365 at global configuration level, owning and scaling endpoint device management as the technical authority for Jamf Pro and Intune, designing and deploying automated identity provisioning and access governance integrations with Okta and Entra ID, leading user lifecycle automation for onboarding and offboarding and role changes, partnering with information security on endpoint compliance and threat isolation and conditional access and data classification, writing technical runbooks and SOPs to upskill junior helpdesk engineers, and driving automation with scripting and cloud platforms. Experience: the posting states 4 to 8 years. Location: Pune, on Mindtickle's growing infrastructure team. Company context: Mindtickle is recognised as a market leader by industry analysts, won an AI Breakthrough award for AI based sales solution of the year, and holds a Gold Stevie award for sales and customer service. Who should apply: an IT infrastructure engineer four to eight years in who has outgrown a helpdesk queue and wants ownership of endpoint and identity platforms globally. This is a good fit if you enjoy automation and being the last escalation, and a poor fit if you are aiming at product engineering, since the customers here are Mindtickle's own employees.
What the posting asks for: - 5+ years of experience with PHP, Node.js and relational databases such as MySQL or Postgres, plus Kafka, RabbitMQ and React. - Profound experience in backend development. - Experience with object oriented programming. - Experience designing APIs. - Experience with event based distributed applications. - A focus on clean and readable code. - Source code management with Git. - The ability to work in a team and a willingness to take part in an open feedback culture. The day to day: working with other developers to align on project goals, architecture and delivery timelines; implementing and maintaining scalable software in PHP while balancing technical excellence against pragmatic delivery; using GitOps, Kubernetes and related tools to streamline deployment and infrastructure management; and taking part in architecture discussions, bringing new ideas and constructively challenging others. You would report to a Software Engineering Manager. Experience: the posting states 5+ years, and lists the specific technologies inside that same requirement rather than separately, so the years are expected to include PHP and Node.js. Location: Bangalore. A note on the title: the posting is listed as Software Engineer but the description opens with "As a PHP Developer", so the role is squarely backend PHP work. If PHP is not a language you want on your next CV line, that is worth knowing before you apply rather than after. Company context: ChargePoint has focused solely on electric mobility since 2007 and trades on the NYSE as CHPT. The posting frames electric vehicles as heading toward more than half of new vehicle sales by 2040. Who should apply: a backend engineer with five or more years in PHP and Node who wants scale and a sector with a long runway. Charging networks are real infrastructure work with genuine reliability requirements, which makes this more interesting than a generic PHP posting.
What the posting asks for: - 10+ years of software engineering experience with significant exposure to distributed systems and cloud native architectures. - Strong expertise in observability: monitoring, logging, distributed tracing, telemetry pipelines and incident management. - Experience operating large scale production systems with a focus on reliability, scalability and performance. - Deep understanding of system debugging, root cause analysis, performance optimisation and production operations. - Strong programming experience in one or more of Go, Java, Python, Node.js or similar. - Experience with observability technologies such as OpenTelemetry, Prometheus, Grafana, Elasticsearch, Datadog, New Relic, Splunk or Honeycomb. - The ability to influence technical direction across teams without direct authority. - Strong communication and a data driven approach. Counts as a bonus: - Building internal developer platforms or observability platforms at scale. - Exposure to AIOps, intelligent alerting, anomaly detection or AI powered operational tooling. - Driving reliability initiatives across multiple engineering organisations. - A background in SRE, platform engineering, infrastructure engineering or developer productivity. The day to day: driving the technical vision and architecture for Postman's observability platform, designing scalable solutions for metrics, logging, tracing, alerting and operational analytics, investigating complex production issues and driving long term corrective action, partnering with engineering teams on reliability and operational maturity, establishing observability standards and instrumentation frameworks, building tooling and automation for faster incident detection and resolution, using telemetry to find performance bottlenecks and capacity risks, and mentoring senior engineers. Experience: the posting states 10+ years. This is the clearest title mismatch in today's list: the role is advertised as Senior Engineer, but the opportunity section says "We are looking for a Staff Engineer" and the requirement is 10+ years. Do not rule yourself in or out on the title. Location and office days, stated explicitly: Postman values in person collaboration. Bangalore based employees currently work in the office three days a week and will move to five days a week by the end of the year. That is a material change and worth weighing now rather than later. Who should apply: an experienced platform, SRE or infrastructure engineer who likes diagnosis and wants company wide scope. If you are a senior engineer at six or seven years, the title will tempt you but the stated bar will not stretch that far.