No roles match that combination.
New today · August 5, 2026
Published requirements: 12+ years of experience in site reliability engineering or similar roles supporting production environments, with proven ability to mentor and guide technical teams; expertise in infrastructure as code tools including Pulumi, Terraform and CloudFormation; deep familiarity with observability tooling including Datadog and Sentry, and with incident response practice including PagerDuty and Incident.io; proficiency with cloud platforms across Azure, GCP and AWS; strong programming skills in Python, Bash, Go or similar; a proven track record of diagnosing complex system problems and implementing durable solutions; and a solid understanding of CI/CD, Kubernetes, containerisation, networking, databases and cloud security principles. Strong problem solving and meticulous attention to detail are also stated. Location is Bengaluru. The mentoring requirement appears in the experience line itself rather than as a separate management duty, and no reporting line, hiring responsibility or performance review duty is stated anywhere, so we have published this as a senior individual contributor role. Confirm if that distinction matters to you. What is genuinely useful about this posting: naming the actual tools removes the usual guesswork. If your background is AWS and Terraform and this team runs Azure and Pulumi, you can judge the gap yourself rather than discovering it in a screen. The phrase durable solutions is the one to prepare for in interview, since it signals they will probe how you prevented a class of incident from recurring rather than how quickly you restored service. Employer context: Harvey builds AI tools for legal work, and all three of its engineering roles today sit at 10+ or 12+ years, so this is a small senior team rather than a large mixed one. Expect broad ownership and real on call. Good fit for an SRE with twelve or more years who wants reliability ownership rather than a ticket queue.
Published requirement is a strong technical background including 12+ years of experience with system architecture and designing distributed systems that handle large amounts of data. The role is a Staff Engineer position in Bengaluru. Team and product context: Stripe's Revenue and Financial Management group builds products that extend the company's scope beyond payments into revenue management, financial operations and analytics. Named products include Billing, Invoicing, Revenue Recognition and Reconciliation, along with the underlying platform for batch and real time processing of large scale financial data that powers them. The posting states these solutions are key pillars for Stripe's growing software business and a major revenue stream. Responsibilities as published: help architect and design this system from the ground up; set technical direction across a variety of projects and initiatives while mentoring and growing others on the team; scope and lead large technical projects that form the foundational pillars for financial data management infrastructure; and scrutinise technical designs and decisions. What makes this domain harder than it sounds: financial data infrastructure has correctness requirements that ordinary data platforms do not. Revenue recognition and reconciliation must be auditable and reproducible, results have to reconcile exactly rather than approximately, historical restatement has to be handled without corrupting prior periods, and the batch and streaming paths must agree with each other. Engineers who have done this work well tend to find the experience transfers strongly, because relatively few people can reason about both distributed systems and accounting semantics. The mentoring element is stated as part of the staff remit rather than as management, and no reporting line is mentioned, so we have published this as an individual contributor role. Good fit for a distributed systems engineer with twelve or more years who wants greenfield architecture where correctness is the hard constraint.
Published requirement: a Bachelor's degree and 12+ years of experience, or alternatively 14+ years of experience, with an advanced degree in a quantitative field such as statistics, computer science, machine learning, economics or operations research strongly preferred. We have recorded twelve as the minimum so the role filters correctly, but note the fourteen year alternative route exists if you do not hold the degree, which is a genuinely useful detail that most postings omit. Further requirements as published: a track record of setting technical direction for applied ML and AI work that ships and matters, covering major initiatives, complex systems or new modelling paradigms taken from idea through to production impact; deep applied ML expertise across both traditional ML and deep learning, specifically naming gradient boosting, regularised linear models, transformer based sequence models, foundation model embeddings, causal ML, contextual bandits and offline reinforcement learning; and an architect level grasp of agentic AI systems including tool use, retrieval, multi step reasoning, evaluation and guardrails. Location is Bangalore. An office reality check you should not skip. Smartsheet tags its India roles as remote in its own job board metadata while several of its India job titles simultaneously say hybrid in Bangalore. That contradiction has appeared on this employer's postings on multiple days now. This particular requisition does not carry the hybrid wording in its title, but given the pattern we would not treat any remote tag from this employer as reliable. Confirm the office expectation in writing before you progress. Also worth knowing: this employer opens its postings with a line about having operated for over twenty years, which is a statement about the company and not an experience requirement, and it is exactly the kind of sentence that automated tools misread as a years figure. Good fit for a very senior applied scientist who wants breadth across classical and agentic ML.
Published requirement is 15+ years of industry experience building and supporting large scale distributed systems, which is the highest stated bar in today's edition. The team is Lakeflow Connect and the posting is direct that it wants engineers with experience in core database internals. What the team is solving: extracting data from OLTP systems while imposing minimal load on those production systems. The named techniques are incremental data capture and log parsing, which in practice means change data capture built on database write ahead logs and replication protocols rather than periodic query based extraction. Anyone who has run a query based extraction against a busy production database understands immediately why this matters, and it is a genuinely specialised problem that touches the internals of each source database differently. Stated impact and expectations: solve real business needs at large scale through software engineering; deliver a highly scalable, available and fault tolerant engine processing hundreds of terabytes of data daily across thousands of customers; and perform low level systems debugging and performance work. The posting also says it wants engineers who continue to be hands on and want to make a large impact on a problem important to the company, which reads as a deliberate signal that this is a building role rather than an architecture oversight role at this seniority. Location is Bengaluru. Honest fit guidance: fifteen years is a real filter and we would not encourage a stretch application at half that. But if your background is database engines, replication, storage engines or CDC systems, this is one of the few roles in India where that specific expertise is the central requirement rather than a nice to have, and those roles do not come up often. Good fit for a systems engineer with deep database internals experience who wants to stay technical.
Fivetran publishes no experience figure anywhere in this posting. We have written the field blank rather than invent one, which means this listing appears in no experience band on the page. The Senior title is the only seniority signal, so ask for the expected range in the first conversation. What the role covers: an infrastructure engineer with GCP, Azure or AWS expertise to help build a reliable platform for the dbt product across all three clouds. The team mission as published is creating a seamless developer experience by providing stable, observable and easy to use infrastructure. Recent context the posting supplies: over the past year the team designed and operationalised a next generation cell based architecture, scaling the dbt platform across all three cloud providers, and the current focus is automation, self service and improving developer velocity through better tooling, processes and infrastructure design. Why the cell based detail matters technically: cell architectures partition customers into independent slices so a failure or noisy tenant affects one cell rather than the whole platform. Running that across three clouds simultaneously multiplies the operational complexity, since each provider differs in networking, identity and managed service behaviour. It is genuinely interesting infrastructure work and it is unusual for a posting to state the architecture this plainly. Location is Bangalore. One employer specific check we recommend and perform ourselves: Fivetran publishes an internal hiring priority field on some of its job postings, and roles marked with statuses meaning future opening or internal resources only still load completely normally in a browser while not actually being open to outside applicants. We checked this requisition specifically and it carries no such flag, which is why it is in today's list. If you browse Fivetran's board directly, look for that field before applying to anything else there.
Fivetran publishes no experience figure anywhere in this posting, so we have left the field blank rather than guess, and this listing sits in no experience band on the page. Note also an internal inconsistency worth knowing about: the board title says Staff Software Engineer while the description text says the company is hiring a Senior Software Engineer. Clarify the level and band early, since that gap can be worth a lot in compensation. Published requirements: strong professional software engineering experience with a track record of shipping production systems; deep proficiency in Python including modern typing, testing practice and packaging; strong SQL fundamentals and a working understanding of how analytical query engines and data warehouses execute queries; and experience designing systems that involve parsing, compilation or transformation, with query planners, DSL compilers and type systems given as examples. The role is on the Semantic Layer team in Bangalore, as a core contributor to MetricFlow. Described as a high ownership role where you write production code, drive technical decisions and help shape long term direction, with responsibilities spanning feature design, query generation optimisation, hardening the open source codebase and partnering with the community of contributors and adopters around it. Why this is technically interesting: a semantic layer takes metric definitions expressed once and compiles them into correct SQL across different warehouses and query shapes, which is genuinely a compiler problem with all the usual concerns, an intermediate representation, correctness under composition, and generated output that must be both right and efficient. The open source element means your commits and design discussions are public. Same employer caution as our other Fivetran listing: this company flags some postings with an internal hiring priority status meaning they are not open externally even though the page loads normally. We checked this requisition and it carries no such flag.
Published requirement: 0 to 2 years of experience in a technical role, and the posting explicitly counts consulting, pre sales, technical support or an internship towards that. This is the lowest experience bar we have published in several weeks and the posting describes itself, in its own words, as an early career technical role, so the level is not our interpretation. Location is Pune, named in the job title. Desired technical knowledge as published: an understanding of TCP/IP and related network protocols including TCP, ARP, ICMP, DHCP, DNS, HTTP and SNMP, along with familiarity with protocol and packet analysis tooling; knowledge of information security protection, detection and authentication systems such as firewalls, intrusion detection and prevention systems and anti virus; knowledge of commonly accepted information security principles and practice, including the techniques attackers use to find vulnerabilities, gain unauthorised access and escalate privileges; in depth knowledge of current operating environments across Microsoft, Linux, other operating systems and cloud providers; and exceptional analytical ability. What the job actually involves: supporting the pre sales engineering function by demonstrating the technology, assisting with proofs of concept and contributing to customer success, while working directly with field solutions engineers, sales teams and clients. It is stated as a learning role, with the purpose being to develop into delivering performance and security solutions. Honest guidance for early career applicants. This is customer facing technical work, not software engineering, so you would spend your time explaining, demonstrating and troubleshooting rather than building product. That is a legitimate and well paid career track and solutions engineering pays strongly at senior levels, but it is a different path from software development and it is worth choosing deliberately. If you have solid networking fundamentals and enjoy explaining technical things to people, this is a genuinely rare opening. Apply quickly, entry level roles at this quality close fast.
Published requirements: customer centric with 3+ years in a customer success or account management role; able to manage a wide portfolio of accounts rolling up to large enterprise corporate accounts; knowledgeable in working with Fortune 1000 companies and global brands across all industries; a strong communicator with exceptional attention to detail and the ability to pitch to a specific audience including CTOs, VPs of Engineering and DevOps professionals; experienced in the business to business technology space or with SaaS companies; and able to travel for customer onsite visits and events as required. Responsibilities as published: partner with the enterprise account executive and solutions engineering teams to onboard, train and proactively drive adoption with enterprise customers; proactively build customer relationships to achieve loyalty and advocacy within their organisation; collaborate across internal Datadog teams including sales, support, enablement, product, finance and legal; and own and project manage the onboarding process. Location is Delhi, which is worth flagging because the overwhelming majority of roles on this board are Bangalore, and this is a rare senior opening in the National Capital Region. Why this is in the list: a reader asked specifically for customer success manager and technical account manager roles, so we search for them and group them separately so they do not dilute the backend and data listings that most readers come for. Fit guidance: this is not an engineering role and it does not become one, but it is technical enough that engineers do move into it successfully. The audience is DevOps and engineering leadership, so credibility depends on genuinely understanding monitoring, alerting and incident practice. The posting itself adds a note that it does not expect every candidate to meet all qualifications on day one, which is an unusually open invitation at the three year mark. Note travel is a stated requirement, not optional.
Published requirement is 3 to 5 years in a pre sales, solutions consulting, technical sales or product role. The position is based in Delhi, which along with the Datadog role makes it one of only two senior openings in the National Capital Region in today's edition. What the role is, in the posting's own framing: the solution architect is the trusted technical advisor bridging what Sarvam builds and what the client needs. You would work alongside the sales and go to market team to understand prospect requirements and translate them into technical narratives, and own the technical relationship with the customer's technology decision maker end to end through the pre sales cycle. The posting states plainly that this is not a support role and that you would be in client meetings from day one, shaping how enterprises understand and evaluate the platform. Concrete activities named: building demos, crafting proposals, running pilots, and working directly with product and engineering teams to close the gap between what a client asks for and what can actually be delivered. Technical domains you would work across: voice AI, document intelligence, multilingual agents and enterprise grade API platforms. That last set is the interesting part of this role. Indian language AI is a hard technical problem with genuine national relevance, and relatively few companies are working on it at depth, so the domain knowledge you would build is scarce and transferable. Fit guidance: the posting says it wants someone who can hold a technical conversation with an engineering lead and a business conversation with a commercial buyer in the same meeting. If you are an engineer who enjoys the customer side, three to five years is a low enough bar to make this a realistic move into solutions architecture, and the pre sales track pays well as it matures. If you want to build the models, this is not that role.
Published requirement is 5+ years of hands on industry machine learning experience in at least one of two named tracks. The ML engineer track: building and maintaining production grade cloud infrastructure on AWS, Azure or GCP that supports deployment of ML applications, including drift monitoring. The AI engineer track: experience with current techniques in large language models and agentic systems, including vector databases, fine tuning LLMs, AI guardrail systems, and deploying LLMs with tooling such as HuggingFace, LangChain and OpenAI. Also required: a graduate degree in a quantitative discipline such as computer science, engineering, statistics or operations research, or equivalent practical experience; and experience communicating or teaching technical concepts to both technical and non technical audiences. A preferred rather than required item is 2+ years of customer facing experience in a pre sales or post sales role, which is worth noting because it means deep customer experience is not a gate, so a strong ML engineer can move into this role without a solutions background. The posting states directly that this is a hybrid role based in Mumbai. Responsibilities: architect production level ML and AI workloads for customers on the platform, including agents, end to end ML pipelines, training and inference optimisation, integration with cloud native services and MLOps; and serve as a trusted practitioner for enterprise generative AI solutions covering RAG architectures, agentic systems with tool calling agents and multi agent orchestration, guardrails, and natural language querying of structured data. Mentorship and establishing yourself as an AI thought leader are also named. Fit guidance: this is the most technical customer facing role in today's edition and the closest thing to an engineering job among them. If you are an ML engineer who is tired of one narrow model and wants exposure to many enterprise architectures, it fits well. Mumbai is a rare location for a role of this seniority.
Published requirement is 7+ years of experience in a solutions engineer or similar role, managing relationships with large, global and complex customers. Location is Delhi, which is a rare posting location at this level and useful for anyone in the National Capital Region who does not want to relocate to Bangalore. Responsibilities as published: partner with customers to ensure they achieve tangible business value from the models through ChatGPT and the OpenAI API; work with senior business stakeholders to understand pre sales needs, guide their AI strategy and identify the highest value use cases and applications; work with business and technical teams to demonstrate the value of the solutions and recommend architectural approaches; demonstrate how the ChatGPT business product solves customer problems through demos, use case scoping and proofs of concept; serve as the first line of defence for security and compliance questions, explaining standardised collateral, guiding customers to relevant resources such as the trust portal and escalating complex requirements to the right teams; create and maintain documentation, guides and FAQs covering common questions found during pre sales; and develop customer relationships through evaluation and purchase, fostering advocacy and representing the voice of the customer internally. Fit guidance: the security and compliance element is a larger part of this role than the title suggests, and it is the part most solutions engineers underestimate. Enterprise AI adoption stalls on data handling, retention and regulatory questions far more often than on model capability, so being fluent there is what makes someone effective in this seat. If you have a solutions or pre sales background and have been fielding AI questions from customers already, this is a strong move while the speciality is still forming. If you want to build with the models rather than explain them, look at the engineering roles in today's list instead. This role is grouped with our other customer facing technical listings deliberately.
Published requirement is 7+ years of relevant experience as a solutions or systems engineer with a proven track record and demonstrable skill presenting technical information at business executive level or at architect level. Also required: strong empathy for customers alongside what the posting calls a passion for revenue and growth, and strong written, verbal and presentation communication. Location is listed simply as India without a named city. Responsibilities as published: articulate the high level benefits of the architecture to target audiences, typically senior security management up to CISO and CIO; construct best practice for presentations, demonstrations and proof of concept or proof of value exercises as well as overall win strategy; take an active role in regional customer success and help resolve customer issues; create evaluation test plans with customers and partners and manage the evaluation through to a successful conclusion; lead proofs of concept; provide insight on competitive solutions and differentiate between them; respond to requests for information and requests for proposal; present at conferences and seminars; and work trade shows as necessary. The disclosure that matters, quoted because it is unusual for a posting to be this direct: the responsibilities list opens by stating that objective number one is to exceed sales targets. Most solutions engineering roles are commercially aligned in practice, but few say so in writing. Read that as an honest signal about how success is measured, and expect compensation to include a variable component tied to regional sales performance. Ask about the quota structure and the split between base and variable before progressing. Fit guidance: this is a customer facing technical role and we group it separately from engineering positions for exactly that reason. It suits an experienced pre sales engineer in security who is comfortable being measured on numbers. It is not a route into product engineering.
Neo4j publishes no experience figure anywhere in this posting, so we have left the field blank rather than invent one, which means it appears in no experience band on the page. Ask for the expected range early. Location is listed as Remote India, and we could find no state restriction, office attendance clause or hybrid requirement anywhere in the body text. We check remote claims by reading the posting body rather than trusting the location tag, because tags are wrong often, and this one holds up. Responsibilities as published: serve as the primary technical point of contact for a portfolio of AI startups in the programme; guide teams in designing, building and deploying Neo4j based architectures; translate requirements into concrete graph centred architectures, patterns and implementation guidance; work with common AI frameworks and tooling including LangChain, LlamaIndex, PydanticAI or ADK, agent frameworks, vector search, and open source and commercial large language models; identify and promote repeatable graph and AI solution patterns across the portfolio; own the ongoing technical relationship with assigned startups, running regular check ins, tracking progress and proactively surfacing risks or blockers; help customers move from early experimentation to production adoption; and partner cross functionally inside Neo4j. Why this one is worth attention beyond the remote element: graph plus retrieval augmented generation is a genuinely current technical area, since knowledge graphs are one of the more credible answers to grounding language model output, and working across a portfolio of startups means unusually broad exposure in a short time. Fit guidance: this is a customer facing technical role, not a software engineering job, and we group it accordingly. But it is advisory and architectural rather than quota driven, and nothing in the posting mentions sales targets, which distinguishes it from some other solutions roles in today's list.
Neo4j publishes no experience figure anywhere in this posting, so the field is blank and the listing sits in no experience band on the page. The Senior in the title is the only seniority signal available, so establish the expected range in the first call. Location needs care. The posting is tagged Remote India, and we found no office attendance requirement in the body, but the title itself says Delhi based. Read that as remote working with an expectation that you are located in or near the capital, which makes sense for a public sector role where in person meetings with government stakeholders are unavoidable. If you are not in the National Capital Region, ask directly whether that is negotiable before investing time. Responsibilities as published: serve as the primary technical advisor for public sector opportunities across India; engage with senior government stakeholders; conduct deep technical and business discovery; support the sales process through value based selling; and collaborate with key partners including hyperscalers across AWS, Azure and GCP, strategic independent software vendors and systems integrators to drive joint go to market initiatives. Domain context: public sector technology sales in India runs through a distinctive procurement process involving tenders, empanelment, security and data residency requirements, and long approval cycles. Experience with that process is valuable and portable, and people who have it are scarce. It also means the sales cycle is measured in quarters rather than weeks, so patience is a genuine job requirement. Fit guidance: this is customer facing technical work and we group it separately from engineering roles. It is explicitly sales supporting, with value based selling named in the responsibilities, so expect commercial measurement alongside the technical advisory work. Ask about quota and variable compensation. Good fit for a solutions engineer with public sector experience who wants remote work and graph technology.
Zeta asks for 2 to 4 years of proven experience as a test engineer with substantial exposure to quality assurance and automation testing. The day to day: writing feature test plans from requirements, defining the test strategy and methodology for a feature, building detailed test cases, automating and running them with adequate coverage, analysing results and feeding defects back to developers, and building and maintaining the automated suites themselves so they stay reliable and fast. You are expected to work directly with the development team to prioritise and confirm issues, report on software quality regularly, and look for process improvements inside the QA function. Location is Hyderabad and the posting is tagged Full time under the Engineering team. Domain context worth knowing before you apply: Zeta is a banking technology company backed by SoftBank Vision Fund and Mastercard, valued at 2 billion dollars in 2025, with roughly 1,700 staff across India, the US, EMEA and Asia. Its products include Tachyon (cloud native banking stack), Cipher (authentication), Elena (conversational AI for banking), and Pixel, the credit card built with HDFC Bank. Testing here means testing regulated financial systems, so expect scrutiny on edge cases, compliance and audit trails rather than pure UI work. This is one of the lowest experience bars on the board today, so it suits someone with a couple of years of automation experience who wants to move into fintech.
The posting asks for 3 to 6 years and is explicit that it wants someone with a genuine interest in networking, security and troubleshooting. Responsibilities as published: deploy and maintain LANs, WANs and network segments; coordinate with equipment vendors for troubleshooting and configuration standardisation; own firewall configuration for both security and performance; hold a strong working command of LAN switching technologies including VLANs, RSTP, ACLs and Virtual Chassis; recommend network capacity planning strategies; plan and run proactive maintenance for disaster recovery; and monitor networks for security, reliability and availability. Job location is stated plainly as Noida, so treat this as an on site role in the National Capital Region and budget for that if you are not already there. Employer context: Paytm is India's leading mobile payments and financial services distribution company and the company that drove QR based mobile payments in India, so the networks you would be supporting carry live consumer payment traffic. That has two consequences worth thinking about. First, change windows and rollback discipline will be tighter than in a normal enterprise. Second, the operational load is real, and disaster recovery planning is listed as an actual responsibility rather than an aspiration. This is a good fit if you are a hands on network engineer who wants scale and does not want to move into software. It is not a fit if you are looking for cloud networking or SRE work, since the emphasis here is on physical and campus network operations.
Harvey does not publish a years figure anywhere in this posting, which is unusual given that its Staff Backend and Staff SRE listings today both state 12+ years. We have left the experience field blank rather than guess, so this role will not appear under any experience filter on this page. Treat the seniority signal as coming from the Staff title instead: at Harvey that implies deep frontend expertise, the ability to set technical direction on the client side, and comfort owning a surface end to end rather than picking up tickets. What the company is: Harvey builds AI for legal and professional services work, so the frontend is not a marketing site, it is a dense professional tool where lawyers read long documents, compare versions, and rely on the interface not to lose their place or misrepresent a citation. Expect the interesting problems to be in editor behaviour, document rendering at length, streaming AI output into a usable interface, and latency perception. Culture as published: three stated values, decisiveness (act on clear judgment rather than perfect information), simplicity (simplicity is what scales), and Job's Not Finished. The posting is candid that the team moves fast, operates with intensity and stays close to customers, which usually means shipping cadence is high and ownership is individual. Location is Bengaluru. Good fit if you are a senior frontend engineer who wants a product where interface quality is the product. Ask about the years expectation and the on call or support model in the first call, since neither is published.
Stated requirement is 5+ years, read from the opening line of the job description rather than inferred from the title. The role sits in Tekion's Security Engineering team and covers three distinct areas. Cloud security posture management: implementing and maintaining security configuration across AWS, Azure and GCP, using commercial tooling (Wiz and Valence are named) alongside native cloud services. Threat detection and response: building and running detection for toxic cloud risk combinations, public exposure and runtime threats, then working with the SOC and incident response teams to triage and remediate what fires. Secure SDLC: embedding security into CI/CD pipelines through static and dynamic analysis, dependency scanning and secrets detection, and supporting threat modelling and vulnerability assessment early, at design and release stages rather than after the fact. Location is Bangalore HQ, so treat it as an on site or hybrid Bangalore role. One operational note taken from the posting itself: it carries a line stating that from 4 August 2026 current Tekion employees should apply through the internal job board in Ashby, which confirms the requisition is live and externally open. Worth knowing about the employer: Tekion moved its entire job board from Greenhouse to Ashby in early August 2026, so any Tekion link you saved before then is probably dead even though the role may still be open. Good fit if you want multi cloud security engineering with genuine detection work attached, rather than a pure compliance or GRC seat.
Okta states 5+ years of data engineering experience, focused on building data pipelines, data models and working on data platforms. The team is the Enterprise Data Platform group and the role reports to the Senior Manager of that team. The posting is explicit that this is a hands on contributor position: you build and implement core components of the data infrastructure rather than only design it, and the stated objective is a platform that supplies AI ready data to Okta's internal AI use cases. Expect the usual pillars, ingestion, modelling, orchestration and quality, with an unusually heavy security and governance emphasis, because Okta's business is identity and the data flowing through this platform is sensitive by nature. Location is Bengaluru, named in the job title itself. Company context that matters for fit: Okta's stated mission is to let any organisation use any technology securely, it is the leading independent enterprise identity provider, and it is currently positioning AI and data capability as a central pillar of its next growth phase, which is why this platform exists. That is a reasonable signal that the team has budget and visibility rather than being a back office reporting function. A caution worth naming: Okta is running a very large India hiring push right now, with dozens of Bengaluru engineering requisitions open simultaneously and several near identical titles. Read the specific team on the posting rather than the title, because the same title at Okta today can mean quite different work. This one is data platform, not analytics and not business intelligence.
Stated requirement is 5+ years in professional software engineering. Skills as published: expert level Python for AI and ML orchestration, plus JavaScript or TypeScript or Java for the enterprise services layer; working knowledge of Salesforce Sales Cloud, where understanding the API and object model is mandatory and Apex is a bonus rather than a requirement; proven experience building AI agents with MCP (Model Context Protocol) and implementing RAG architectures; and deep expertise designing and consuming RESTful APIs including complex authentication and OAuth flows. Responsibilities: design and implement MCP servers that expose services such as Quote, Opportunity and Renewal to AI agents; rapidly decompose the data models of enterprise applications including Zuora, Salesforce and ServiceNow into schemas that AI can work with; and build and optimise RAG workflows and agents that execute multi step tasks with minimal supervision. Honest fit guidance, because the title undersells and the domain oversells in opposite directions. The technology is genuinely modern, MCP and RAG work in production is still rare, and five years is a reasonable bar for it. But the systems you are automating are the company's own commercial back office, so the users are internal sales and finance operations rather than external customers, and success is measured in process time saved rather than product shipped. If you want AI engineering experience on your CV and do not mind that the domain is quote to cash, this is a strong opportunity. If you want to build the storage product, this is not that team. Location is Bangalore.
The posting asks for 5+ years in SDET work for data engineering and data platforms, which is a narrower ask than general test automation and worth reading carefully before applying. The team is Tekion's Enterprise Data Platform group. That platform runs the organisation's data lake and is the foundation for data products, analytics, reporting, AI and ML workloads, and customer facing experiences, so a data correctness failure here surfaces in several directions at once. Core responsibility as published: build confidence in the quality, reliability and correctness of data across the platform. In practice that means defining robust validation strategies, automating the testing behind them, and working closely with data engineering, product management, analytics and AI teams so the definition of correct is agreed rather than assumed. The forward looking half of the role: as Tekion expands its AI powered Analytics Agent, you would help validate user intents, define evaluation frameworks, and make sure AI generated analytics outputs meet a measurable quality standard. That is an emerging discipline and genuinely useful experience to hold. Location is Bangalore HQ. The posting carries the same internal application note as Tekion's other current listings, effective 4 August 2026, which confirms the requisition is live. Fit guidance: this suits a test engineer who has already moved from application testing into data, and who is comfortable reasoning about schemas, pipelines and data drift rather than screens. If your automation background is entirely UI or API level, expect the data platform requirement to be the thing that decides the screen.
Published requirements: minimum 3+ years of professional experience in SAP ABAP development, including at least 2+ years specifically in SAP S/4HANA, and separately a minimum of 2+ years in SAP Fiori and UI5 development for S/4HANA. Read that as a genuine dual requirement rather than an either or, since the two are listed as separate mandatory lines. This is a Software Engineer II requisition based in Bengaluru. Honest framing so nobody wastes an application. The work is ERP engineering: you are building and extending the SAP systems that ZoomInfo runs its own business on, which means the users are internal finance and operations teams and the success measure is process reliability rather than customer facing product. That is a legitimate and well paid engineering track with strong job security, and ABAP plus Fiori is a scarce combination in India, but it is a different career path from product software engineering and it is hard to reverse later. Go in knowing that. Why it is on this list at all: it is a real software development role with a genuine three year bar, and three year roles have been extremely scarce on this board recently, so we would rather publish it with the caveat stated than pretend the supply is better than it is. One practical note: zoominfo.com returns 403 to automated requests, so we confirmed this posting is live directly against the Greenhouse jobs API rather than by loading the careers page. The apply link is correct and works in a normal browser.
Stated band is 5 to 8 years in SDET, quality engineering, ML engineering or data science, with hands on experience building evaluation or measurement systems. Note that the board title says Staff while the description opens by calling it a Senior SDET role, so the level naming is inconsistent inside the posting itself. The band is the reliable number. The team is Tekion's AI Platform group. The stated premise of the role is that evaluation is the backbone of trustworthy AI, and the concrete driver is scale: Tekion is going from a small number of AI agents to over a hundred across Service, Sales, F&I and Analytics, and every one of those teams needs a way to know whether its agent is improving or regressing. Your job is to build that capability once, as a shared platform service, rather than letting each team improvise. Day to day you would work with ML engineers, data scientists, the AI Platform team and product management to design evaluation datasets, build automated scoring pipelines, and define quality metrics that quantify accuracy, consistency and safety of AI generated output. Location is Bangalore HQ. Fit guidance: this is a genuinely emerging speciality and the experience transfers well, because almost every company shipping LLM features is about to discover it has no way to measure them. It suits someone who is comfortable being the person who defines what good means, and who can hold that line with ML teams who would rather ship. If you want conventional test automation, this is not that job.
Stated requirement is 6+ years of server side application development with Java, Spring Boot, microservices and AWS, plus demonstrated delivery of highly scalable products and a track record of shipping. The tech stack is listed separately as language Java or Golang, with relational and in memory databases. Preferred qualification is a Bachelor's or Master's degree in Computer Science or equivalent. What the role actually is: developing the detailed design structure, implementing best practice and coding standards, and leading a team of developers through delivery, while personally working on design, architecture and hands on coding. The posting is explicit that hands on coding is part of it, which is the main thing worth confirming for a lead title in India. The judgment call we are disclosing rather than hiding: among otherwise technical requirements, this posting also asks for an entrepreneurial spirit combined with strong programme and product management skills, and for proven success in building, motivating and retaining teams. That is people management language. There is no reporting line, headcount, hiring or performance review responsibility stated anywhere, so we have published it as an individual contributor lead role, but you should ask directly in the first call whether this position carries direct reports. If having reports is what you want, that is a positive. If you want to stay purely technical, get the answer before you invest in the process. Location is Noida and the role is on site. Employer context: Paytm pioneered QR based mobile payments in India and its stated mission is to serve half a billion Indians, so backend work here runs at genuine national scale.
Minimum qualifications as published: a Bachelor's degree in computer science, computer engineering or a related field, or equivalent, and 6+ years of progressive experience showing strong architecture, programming and engineering skills. Technical requirements: a firm grasp of data structures and algorithms with fluency in Java, Python or Scala; strong SQL including the ability to write complex queries; and solid hands on experience with an orchestration tool such as Airflow. The posting separately notes java or scala and SQL as the working languages. Responsibilities: design, develop and maintain scalable data pipelines covering ingestion, processing and storage; build integration that consolidates data from multiple sources into a centralised warehouse or data lake; work with data scientists and analysts to understand requirements and translate them into technical specifications; protect data quality and integrity with robust validation and cleansing; optimise pipelines for performance, scalability and reliability; and develop and maintain ETL processes. Two responsibilities that are easy to miss in the middle of the posting and that materially change the job. First, you maintain operations of the live service as issues arise on a rotational on call basis, so this is not a build only role. Second, you are responsible for verifying that the data architecture meets security and compliance requirements, which in a regulated payments business is a real workload rather than a checkbox. The posting also asks that you learn fast and adapt at pace, which is consistent with the volume. Location is Noida, on site. Good fit for a data engineer with six or more years who wants ownership of a large pipeline estate and is comfortable carrying an on call rotation for it.
Stated requirement is 6 to 10 years of backend engineering experience, with 2+ years of that in a tech lead or senior individual contributor role. That phrasing is worth noting because it defines the lead expectation as senior IC experience rather than people management experience, which resolves the usual ambiguity around Indian tech lead titles. What you would own: technical direction, architecture and delivery for Paytm Digital Gold, a high scale bullion platform serving both consumer and merchant use cases. The posting states the platform operates at lakhs of requests per minute, which is a specific and testable scale claim rather than the usual vague one. Key responsibilities as published: define and evolve the technical architecture for the Gold services across scalability, reliability, security and maintainability; lead delivery; architect solutions and unblock the team; own critical money path reliability; raise the bar on code quality; and mentor junior engineers. It also says you would partner with product and engineering leadership on roadmap and execution, so there is a planning component beyond pure build. Honest framing: money path reliability is the phrase to pay attention to. In a gold trading product the failure modes are financial rather than cosmetic, which means change control, reconciliation and incident discipline will be tighter than in a general consumer product, and the on call expectation is likely real even though the posting does not spell it out. Ask about it. Location is Noida, on site. Good fit for a senior backend engineer with six or more years who wants architectural ownership of a complete product line and is comfortable that the product is regulated financial trading.
Agoda publishes no experience figure anywhere in this posting. We have written the field as blank rather than guessing, so be aware this listing sits in no experience band on the page and the only seniority signal is the word Senior in the title. Ask for the expected band in the first conversation. What the role covers: contact centre technology inside Agoda's infrastructure organisation, based in Gurgaon. Contact centre platforms at this scale are a genuine systems engineering domain, typically covering telephony and voice infrastructure, routing and queueing logic, integration between the contact centre platform and internal customer and booking systems, capacity planning around demand peaks, and the observability needed to prove where a call actually failed. Because Agoda operates globally, expect multi region and multi language considerations and a follow the sun support pattern. Employer context: Agoda is one of the largest online travel booking platforms, with engineering hubs across Asia including Gurugram and Bangkok, and it is one of the few employers on this board with a meaningful non Bangalore India presence, which matters if you are in the National Capital Region and do not want to relocate. One thing we can say about Agoda from its other postings today: it is unusually specific about hands on expectations, with its Staff Backend listing stating outright what proportion of time is spent coding. It is reasonable to ask this team for the same clarity about the split between build work and operational support, since contact centre roles can lean heavily to the second. Good fit for a systems or infrastructure engineer who wants a defined platform to own rather than a general SRE remit.
Stated requirement is 7+ years of experience building Java based web applications. Team and product: the Okta Access Management Engineering team builds the foundation for authentication and authorisation across Okta protected resources. Its stated mission is enabling customers to reach those resources securely, and it develops both Okta cloud services and the client software that lets users log in to devices and use Okta authenticators to access applications. Responsibilities as published: collaborate across QA, product, support and UX for integration; contribute to technical designs, proposals and architectural decisions following established best practice; develop high quality maintainable software components with comprehensive unit and functional tests; participate in code review, giving feedback and holding the line on coding standards and security best practice; and contribute to technical documentation and knowledge sharing. Location is Bengaluru. Practical advice specific to Okta right now: the company has a very large number of near identical Bengaluru engineering titles open at once, including several other Staff Software Engineer requisitions with different teams behind them. The title alone will not tell you what you are applying to, so read the team paragraph, and if you are applying to more than one, keep track of which requisition is which. This one is Access Management, meaning core authentication and authorisation rather than a peripheral service. Good fit if you have seven or more years of Java and Spring backend experience and want the domain to be security critical infrastructure. Expect interviews to probe correctness, edge cases and threat thinking more than raw throughput, because the failure mode here is a security incident rather than a slow page.
Stated minimum requirement is 7+ years of progressive software development experience, with a proven track record of designing and building scalable, high performance systems. Note this is the published minimum for a Principal title, which is lower than many candidates expect and is a good example of why the years figure should be read from the posting rather than inferred from the level. Organisation and mission: the Device Identity and Access organisation sits inside Okta Research and Development and is described as being at the forefront of Okta's zero trust vision, with a mission to transform the device itself into a secure, trusted and effortless identity factor. In practice that domain covers device posture and attestation, cross platform agent work across macOS, Windows and mobile, secure enrolment, and the backend services that evaluate device trust at authentication time. Location is Bengaluru. What principal means here: expect to set technical direction that other teams build against, to be accountable for architectural decisions with a multi year horizon, and to spend real time on written design and cross team alignment rather than only on code. If you want a role where you personally ship features every sprint, principal at a company this size is usually not that. Fit guidance and a caution: Okta currently has an unusually large number of open Bengaluru engineering requisitions, several with nearly identical titles, so confirm which organisation and team a recruiter is actually screening you for before you invest time. This one is Device Identity and Access. Good fit for a backend systems engineer with seven or more years who wants a security domain with genuine technical depth.
Published experience line: a minimum of 7 years of development experience, but the posting states directly that it expects candidates would typically have 10+ years. We have recorded the minimum as seven so the role appears correctly in the experience filter, but read the ten as the realistic bar. Must have requirements as listed: strong experience writing device drivers or doing kernel development for Linux and Unix, with storage or networking drivers preferred; software development in C and C++ along with Python; experience writing Linux storage device drivers including some combination of Fibre Channel, NVMe, RoCE, block and multipath modules; and experience with performance analysis and optimisation for storage systems or protocols. The role is described as a staff engineer position for a group responsible for Linux and VMware initiator stack behaviour as well as Fibre Channel and NIC drivers on the company's storage arrays. Day to day the team covers several areas: working with middleware C++ modules, maintaining Linux kernels for internal testing, documenting supported configurations for customers, and evaluating Linux distributions and kernel behaviour. Location is Bangalore. Why this is worth a look even at a high bar: genuine kernel and driver roles are scarce in the Indian market, most systems jobs advertised as low level turn out to be application work, and this one is unambiguous about what it is. The skills are also durable, since driver and storage protocol expertise ages far more slowly than framework knowledge. Employer note: this company reposts live requisitions under fresh reference numbers fairly often, so if a listing looks familiar from a previous week it may genuinely be the same job. We body checked today's listings against everything we published earlier this week and this one is distinct.
Published qualifications: 8+ years of experience in DevOps, infrastructure automation or platform engineering; a Bachelor's or Master's degree in Computer Science, Engineering or a related technical field; expertise in cloud platforms such as AWS, GCP or Azure; infrastructure as code with Terraform or Pulumi; CI/CD tooling; deep experience with container orchestration including Kubernetes, service mesh and microservices infrastructure; a strong background in system observability, logging and incident response; and strong problem solving, mentorship and communication skills. Responsibilities as listed: architect and lead development of advanced CI/CD pipelines, infrastructure as code and automated deployment solutions; design cloud native infrastructure supporting high availability and fault tolerant applications; lead incident response, performance tuning and capacity planning across systems; work with engineering, product and security teams on platform scalability, security and compliance; and implement observability frameworks while improving monitoring. Note that mentorship appears in the requirements list. We read that as senior technical mentoring rather than people management, since no reporting line, hiring responsibility or performance review duty is mentioned anywhere in the posting, and we have published it as an individual contributor role on that basis. Confirm in the first call if it matters to you. Location is Bangalore HQ. The posting carries the note that from 4 August 2026 current Tekion employees should apply through the internal Ashby board, which confirms the requisition is live and open externally. Good fit for a platform engineer with eight or more years who wants architectural ownership across the full delivery stack rather than a narrow tooling remit.
Stated requirement is 8+ years building large scale data, ML or platform systems, with strong software engineering fundamentals in abstracted API design, concurrency and distributed systems. Technical requirements as published: production experience with Python plus one of Java, Scala or Go, and microservices and API design; MLOps at scale covering pipelines with Airflow or Kubeflow, tracking and registry with MLflow, CI/CD for models, A/B testing, shadow and canary releases, and online feature computation with Spark, Flink or Kafka; cloud and containers with AWS preferred plus Docker and Kubernetes, including performance, reliability and cost engineering in multi tenant SaaS; and practical ML knowledge across feature engineering, training, evaluation and drift detection, including experience deploying models. Responsibilities: build and operate the LLM control plane and gateway, covering smart routing, rate limits and quotas, failover, and token and cost tracking; ship a unified API and SDKs over REST and gRPC with normalised schemas, structured outputs, caching and full observability through traces, logs and metrics; enforce safety and privacy by default with content filtering, prompt and response validation and PII redaction; enable multi model and multi vendor use of LLMs with automated canarying and versioning; and own the agent runtime including the tool registry, permissions and function calling. A note on how the years were read: this posting opens by saying the automotive industry has not innovated in over 50 years. That is a statement about the industry, not a requirement, and automated parsers routinely mistake it for one. The real figure is the 8+ in the skills section. Location is Bangalore HQ. Good fit if you want to build AI infrastructure that other engineering teams consume, rather than train models.
Stated requirement is 8+ years of software development and operations experience with a focus on building platforms and distributable software infrastructure. The posting also lists 2+ years of experience leading, coaching and mentoring a team of engineers. We read that as technical mentorship rather than people management, because the posting describes the ideal candidate as a hands on technical leader who architects complex distributed systems, mentors engineers and collaborates with product teams, and it names no reporting line, hiring duty or performance review responsibility. We have published it as an individual contributor role on that basis, and you should confirm directly if the distinction matters to you. Location, and this is the important part: the posting states the role can be based out of the Gurgaon office or remotely in India. That makes it one of very few genuinely remote eligible engineering roles at this level in today's edition, and it is stated in the body of the posting rather than implied by a tag, which is the standard we hold remote claims to. Readers of this list ask for remote roles more than anything else, usually because relocation is not financially realistic, so it is worth applying even if the years bar is a stretch. What the team does: it is a new team architecting the platform foundation and infrastructure for a build once, run anywhere model, so that MongoDB's AI powered modernisation suite works consistently regardless of deployment target. The stated problems are distributed systems puzzles, minimising deployment friction, and satisfying customer compliance requirements. The posting describes it as a high visibility initiative. Good fit for a platform engineer with eight or more years who wants greenfield architecture and the option to work from anywhere in India.
Basic qualification as published: 8+ years of experience in data or analytics engineering with expertise in data architecture, pipelines and reporting. Responsibilities: build scalable data models and construct high quality ELT pipelines that act as the backbone of the core data lake, using Airflow, dbt and Databricks alongside visualisation tools including Sigma, Looker and Tableau; and build data pipelines and launch self serve analytics products spanning data consumption through to data discovery and enablement. The posting states plainly that what you build is tied to business outcomes and to identifying the root causes of trends, so expect to be close to the questions rather than only to the infrastructure. Company and location context: Coursera and Udemy are now a single company, described as building one of the world's most comprehensive skills development platforms, and this requisition is listed for India without naming a city. The posting describes a globally distributed team that comes together intentionally for collaboration, complex problem solving and key milestones, and mentions a virtual hiring and onboarding experience designed to let people start from anywhere. That language points towards genuine location flexibility, but the posting does not state a remote policy explicitly, so we have not tagged it as remote. Ask about the office expectation, the base city if any, and the time zone overlap requirement in the first call, since a US headquartered education company usually carries some evening overlap. Stated cultural expectations: customer first builders who move fast, simplify and iterate on the metrics that matter. Good fit for a data engineer with eight or more years who wants a modern stack, dbt and Databricks rather than legacy ETL, and who is comfortable owning analytics enablement as well as pipelines.
Stated requirement is 8+ years of professional software development experience, or equivalent. Team and product context: this is a new team inside Core Identity, the engineering organisation responsible for the very heart of the Auth0 application. That organisation owns the authentication pipeline, identity protocols, user sessions and the fundamental concepts underpinning the entire product, and it is also described as the steward of the platform's technical health, performance and efficiency. The new team is named Core Frontier. Auth0 itself is described as a developer first identity platform that simplifies authentication and authorisation, designed by developers for developers, and the posting states it serves more than 100 million daily logins and is a tier zero global service. Technology is Node.js, specifically JavaScript or TypeScript, as named in the job title. What that scale means in practice, and it is worth thinking about before applying: a tier zero authentication service has no acceptable downtime, so expect rigorous change management, progressive rollout, deep observability requirements and a genuine on call culture. Performance and efficiency work is explicitly part of this team's remit rather than someone else's, which suggests real appetite for optimisation projects rather than only feature delivery. Location is Bengaluru. Practical note on applying to Okta at the moment: there are many concurrently open Bengaluru requisitions with similar Staff Software Engineer titles across quite different organisations, including Access Management, Device Identity and FGA developer tooling. Read the team paragraph rather than the title, and track which requisition you applied to. Good fit for a backend engineer with eight or more years and real Node.js depth who wants identity infrastructure at very large scale.
Stated requirement is 8+ years of experience as a software engineer, with significant experience building developer tooling and platforms. Role overview as published: a highly experienced staff engineer to join the FGA Developer Tooling team and lead the evolution of the end to end developer experience across both open source and SaaS. Responsibilities: define and drive the technical direction for FGA SDKs, the CLI, IDE integrations and developer automation across both the open source project and the commercial service; and lead architectural decisions for multi language SDKs. The team owns SDKs in Go, JavaScript, .NET and Python among other languages, so breadth across language ecosystems matters more here than depth in one. Domain context, since fine grained authorisation is a speciality: FGA is about deciding what a given identity may do with a specific resource, rather than simply whether they are authenticated. It is modelled on relationship based access control, the same family of approach as Google's Zanzibar, and it is one of the harder problems in identity because the authorisation check sits in the hot path of every request. Building the developer platform for it means your users are other engineers, which changes what good looks like: API ergonomics, documentation quality, useful error messages and migration paths matter as much as throughput. Working partly in the open is a real differentiator on a CV, since public commits and community engagement are visible evidence of the work in a way most enterprise engineering is not. Location is Bengaluru. Good fit for an engineer with eight or more years who enjoys building for developers and is comfortable maintaining several language SDKs at once rather than owning a single service.
Required knowledge, skills and abilities as published: 8+ years of experience building modern web applications in a full stack environment. Product context: the Okta Recovery Vault is described as a critical new enterprise grade capability designed to protect against the accidental or malicious deletion of identity objects, and the posting states it is essential to the company's land big, grow fast strategy by giving customers a reliable safety net for their data. Responsibilities as listed: lead implementation of the Recovery Vault interface so authorised administrators get a coherent experience inside the Okta Admin Console; build interactive interfaces for granular and bulk recovery operations, including asynchronous job progress indicators and success notifications; and develop the captured data summary view using visual cues such as status icons. Why this is more interesting than a typical admin console role: bulk recovery of identity objects is a genuinely hard interface problem. The operations are long running and asynchronous, partially successful outcomes are normal, and the user is an administrator under pressure who has just lost something important. Getting progress, partial failure and confirmation right is the difference between a feature people trust and one they escalate to support. There is real design and state management depth here despite the modest sounding title. Location is Bengaluru, and the role is full stack rather than frontend only, so expect Java service work alongside the interface. Applying to Okta at the moment: many similar Bengaluru titles are open across different organisations, so read the team and product paragraph rather than the title and keep a record of which requisition this is. Good fit for a full stack engineer with eight or more years who wants a clearly scoped new product surface to own.
Stated requirement is 8+ years of experience with proficiency coding in Java, Golang or similar. The posting describes the position as a Sr. Staff Engineer role reporting to the Senior Manager of Software Engineering in the Federal and Sovereign Clouds department, and states directly that it is a hybrid role, so plan for regular office attendance in Bangalore rather than assuming flexibility. What you would do, as published: design and implement scalable high performance backend services and APIs; ensure code quality by writing and maintaining unit, integration and performance tests, and monitor, debug and optimise system performance; and mentor junior engineers, supporting their growth and upholding best practice through active participation. We read the mentoring line as senior technical mentorship rather than people management, since no headcount, reporting line or review responsibility is stated, and we have published it as an individual contributor role on that basis. The posting also says you would work with a team of cloud architects building scalable, high performance backend applications for the cloud engineering organisation, playing a pivotal role in enhancing the multi tenant architecture and global footprint of what it calls the world's largest cloud security platform. Domain note worth understanding before interviewing: federal and sovereign cloud environments are deployed separately from the commercial cloud, often with restricted access, separate release trains, and compliance regimes such as FedRAMP or national equivalents. That usually means slower release cadence, more documentation, stricter access controls on production, and sometimes citizenship or clearance requirements for specific environments. None of that is stated in this posting, so ask early whether any access restrictions apply to an India based engineer. Good fit for a backend engineer with eight or more years who wants very large scale multi tenant systems.
This posting publishes no experience figure anywhere in its text. We have written the field blank rather than guess, so the listing sits in no experience band on the page and you should ask for the expected range in the first conversation. Use the title as the signal instead: Member of Technical Staff at this company is the senior individual contributor track, and the Architect suffix on this particular requisition points to someone setting design direction for kernel and storage systems rather than implementing to a spec. What the domain involves, based on the company and the team this sits in: enterprise flash storage arrays, where the engineering problems are data path performance, kernel and driver behaviour, protocol handling across Fibre Channel, NVMe and related transports, failure and recovery semantics, and the architecture that keeps latency predictable under load. Adjacent roles at the same company today explicitly require C, C++ and Python plus Linux driver experience, so it is reasonable to expect a similar technical profile here. Location is Bangalore. Two honest cautions. First, because no years figure is published, there is a real chance the bar is higher than the title suggests, since a comparable kernel role at this employer today states a minimum of seven years while noting candidates typically have ten or more. Second, this employer reposts live requisitions under new reference numbers reasonably often. We compared today's listings against everything published earlier this week and confirmed this one is distinct, but if a listing looks familiar to you from a previous application, it may genuinely be the same job. Good fit for a systems engineer who wants architecture ownership at the kernel and storage layer.
Stated requirement is 8+ years of experience designing, developing and testing product components. The role is a backend lead engineer position on Portworx, the company's Kubernetes native storage and data management platform, based in Bangalore. Domain context, because the name alone does not explain it: Portworx provides persistent storage for containerised applications, so it solves the problem that Kubernetes was originally built for stateless workloads while databases and queues need durable, fast, correctly replicated storage that survives pods being rescheduled across nodes. The engineering underneath that involves distributed consistency, replication and resynchronisation, snapshotting and backup, volume lifecycle management, and performance work where the storage layer must not become the bottleneck for the application above it. It is a strong domain for anyone who wants distributed systems depth with a concrete product attached. A disclosure about this specific listing, because it affects how you apply. This employer currently has several Portworx related requisitions open simultaneously with substantially overlapping descriptions. We checked today's candidates against each other by comparing the full text of each posting, and found that this listing and another Portworx role at the same company were more than 98 percent identical, which means they are almost certainly the same underlying job advertised under two titles. We published only this one rather than counting the same role twice. Practically, that means if a recruiter contacts you about a differently titled Portworx backend role, it may well be this same position. Ask which requisition and which component before scheduling. Good fit for a backend or distributed systems engineer with eight or more years who wants storage infrastructure rather than application work.
Databricks publishes no experience figure anywhere in this posting. We have left the field blank rather than invent a number, so this listing appears in no experience band on the page. Treat the Staff title as the seniority signal: at Databricks that generally means deep technical ownership, the ability to set direction for a problem area, and influence beyond a single team. Ask for the expected band in the first call. What search quality means in this context: relevance and ranking work over the platform's own content surfaces, which for a lakehouse platform typically includes data assets, tables and catalogue objects, notebooks, documentation and internal search across a customer's workspace. The engineering split is usually part information retrieval (ranking models, query understanding, embeddings and hybrid retrieval) and part systems (indexing pipelines, latency, freshness, and the evaluation infrastructure that tells you whether a ranking change helped). The evaluation half is often the harder and more valuable one, because enterprise search has no equivalent of web scale click logs to lean on. Location is Bengaluru. Employer context that is genuinely relevant to fit: Databricks runs a very large India engineering presence and its Bengaluru requisitions today range from roles asking five years to one asking fifteen, so the seniority mix on this board is wide and the absence of a figure on this posting is not necessarily a signal that the bar is low. Good fit for an engineer with strong information retrieval instincts who wants to work on relevance where the corpus is structured enterprise data rather than open web text, and who is comfortable that a large part of the job is proving improvement rather than shipping features.
Published requirement is 8+ years of relevant work experience, and a computer science or related technical discipline degree is stated as required rather than preferred, which is worth noting because most postings on this board treat the degree as optional. The role is a Technical Lead position with a Databricks specialism, based in Bengaluru. What Sigmoid does and why that changes the job: Sigmoid enables business transformation using data and analytics, working as a services and consulting partner rather than shipping its own product. In practice that means your work lands inside client environments, often under a fixed timeline agreed commercially before you were involved, and the technical choices are constrained by what the client already runs. The good version of this is genuine breadth: in two years you may see more data architectures than a product engineer sees in five, and Databricks specialists with real delivery history are in demand. The harder version is less control over technical direction and more time spent on stakeholder alignment. Both are true and you should decide which matters more to you. Expect the technical scope to cover Databricks and Spark, lakehouse architecture, pipeline design and orchestration, performance and cost optimisation on cloud data platforms, and enough SQL and Python to be hands on rather than advisory. The Lead title here means technical leadership of a delivery team, so anticipate design ownership plus review responsibility. One thing to check before applying: Sigmoid also advertises roles that turn out to be fixed term contracts despite carrying full time employment metadata, so confirm the engagement type and duration in writing early. This particular requisition shows no contract language. Good fit for a data engineer with eight or more years who wants a Databricks specialist track.
Published requirement is 8 to 10 years of experience in information security across the technical arena, GRC, audit or compliance. Note the range is closed rather than open ended, which is a useful signal: the employer has a specific band in mind and both ends are real. This is a Principal Security Analyst requisition based in Bengaluru. How to read the scope: the posting groups technical security work together with governance, risk and compliance, audit and compliance in a single requirement, which usually means the role spans control design and assessment, security policy and standards, risk registers and treatment plans, evidence collection for external audits, third party and vendor risk, and the technical judgment to know when a control is genuinely effective rather than merely documented. In a company whose product is data about businesses, the compliance surface is meaningful, covering data protection obligations across multiple jurisdictions alongside the usual enterprise certifications customers ask for. Honest fit guidance. Analyst in the title undersells a principal level role at this band, but it does correctly signal that this is not a hands on keyboard engineering position building detections or tooling. If you want to write code and build security systems, look at the cloud security engineering roles elsewhere in today's list instead. If you have grown from a technical security background into the governance and assurance side and want a principal level seat where the technical depth still matters, this fits well and the band is honest about the seniority expected. One practical note on applying: zoominfo.com returns 403 to automated requests, so we verified this posting is live directly against the Greenhouse jobs API rather than by loading the careers page. The apply link works normally in a browser.
Published requirement is 9+ years of experience. The role is a Technical Lead position in Bengaluru with a named scope of Java, Spring Boot, microservices and DSA, which is how the posting itself abbreviates data structures and algorithms. The explicit mention of DSA in a lead level requisition is a signal worth acting on: expect the interview process to include algorithmic and system design rounds rather than only architecture discussion, which is not always true at this seniority. Employer context: Sigmoid is a data engineering and analytics services company, so engineering work is delivered inside client engagements rather than on a single in house product. The practical consequences are consistent across services firms and worth weighing honestly. You gain breadth, since you see multiple architectures, industries and problem framings in the time a product engineer spends on one system, and lead level people with a track record of delivering under commercial timelines are genuinely valued in the market. You give up some control, because technical direction is often constrained by what a client already runs and by scope agreed before you joined the engagement, and because the definition of done can be contractual rather than technical. What the lead expectation appears to be: technical leadership of a delivery team, design ownership, code review, and being the person accountable for the engineering quality of what ships. Nothing in the posting indicates direct reports, hiring or performance review duties, so we have published this as an individual contributor lead role. Confirm in the first call. One thing to verify in writing before accepting: Sigmoid also advertises roles that are fixed term contracts despite carrying full time metadata, so ask about engagement type and duration explicitly. This requisition carries no contract language.
Published requirement is 10+ years of what the posting calls solutions engineering mastery, with a proven track record in the discipline. It states the position is a hybrid role and names the hiring manager directly. Locations listed are Bangalore, Gurgaon and Mumbai, which gives unusual geographic choice for a single requisition. What the role actually is, stated plainly so nobody applies expecting engineering work: this is a field facing pre sales position. Responsibilities as published include partnering with enterprise account teams to own and execute the technical sales strategy, driving complex high value AI security opportunities from discovery through to close, and configuring and presenting tailored demonstrations and proofs of value. The posting describes it as a highly strategic, field facing role combining the consultative strengths of a solutions engineer with deep expertise in large language models, RAG architectures and data protection, serving as a trusted advisor to Fortune 500 executives. Technical depth expected: genuine understanding of how generative AI systems are built and where they leak, covering prompt and response handling, retrieval pipelines and the data exposure they create, model and vendor risk, and how enterprise data protection controls apply to AI traffic. This is a real speciality and currently a scarce one, which is why the band is ten years. Fit guidance. We include customer facing technical roles in this list because readers asked for them by name, and we group them separately so nobody mistakes them for backend or data engineering roles. This one suits a senior solutions engineer or security architect who enjoys the customer conversation and wants to specialise in AI security while that speciality is still forming. It does not suit someone who wants to build the product. Compensation in roles like this usually carries a variable component tied to sales outcomes, which the posting does not detail, so ask about the split early.
Published requirements: 10+ years of software engineering experience including building scalable backend systems or internal developer platforms; proficiency in Python or a similar language with deep knowledge of backend fundamentals and distributed systems; hands on experience with CI/CD systems, with Buildkite and GitHub Actions named, plus test frameworks and load and performance testing; hands on experience with container technologies including Docker and Kubernetes and infrastructure as code with Pulumi or Terraform; a track record of producing high quality, well tested code and following software development best practice consistently; proven technical leadership across the entire project lifecycle from ideation through design and implementation to productionisation; and experience mentoring other engineers. Location is Bengaluru. What developer experience work involves in practice: build and test performance, so how long an engineer waits between writing code and knowing whether it works; local development environment reliability; CI pipeline design and flakiness reduction; release and deployment tooling; and the internal platform abstractions that let product teams ship without needing to understand the whole infrastructure. Success is measured indirectly, through the productivity of other teams, which is both the appeal and the difficulty of the role. Employer context: Harvey builds AI tools for legal and professional services work, and publishes three stated values, decisiveness, simplicity and Job's Not Finished, along with candid language about moving fast, operating with intensity and staying close to customers. Its other two engineering roles today both ask for 12+ years, so the bar across this team is consistently senior. Good fit for a platform engineer with ten or more years who would rather multiply other engineers' output than own a product surface. Ask about on call, since the posting does not state the model.
Published requirements: 11+ years building and operating large scale backend systems in production environments; proven experience delivering complex distributed systems at scale; strong expertise in Java, Scala, Kotlin or Go; strong software architecture skills with a track record of driving architectural decisions within and across teams; proven experience leading technical initiatives, projects or engineering teams with end to end ownership; and recent and ongoing hands on coding experience in production, which the posting states is required rather than preferred. Deep expertise is expected in distributed systems and architecture, API design and microservices. The role is described as owning critical systems end to end, driving technical direction, leading large initiatives, combining architecture, execution and technical leadership, influencing engineering decisions beyond the immediate team, and mentoring engineers. Location is Gurugram, and the posting names it in the title as Gurugram based, so treat it as an on site expectation in the National Capital Region rather than flexible. That is worth flagging positively: most senior backend roles on this board are Bangalore, so a genuine Level 5 backend seat in the NCR is scarce. Employer note worth carrying into the interview: Agoda is unusually specific about hands on expectations. A comparable staff backend posting from the same company states outright what proportion of working time is spent on coding and system design, which is a number most companies leave vague at this level. Given this posting also makes hands on coding a stated requirement, it is entirely fair to ask the hiring manager for the same specificity here and to hold them to the answer. Good fit for a senior backend engineer with eleven or more years who wants architectural scope without giving up code, and who is in or willing to be in the NCR.
Published requirements: 12+ years of backend engineering experience building and operating production web applications or SaaS products; a track record of building fast growing SaaS products using progressive web application technologies; a track record of shipping highly intuitive products with strong attention to detail; strong programming skills in Python with experience of a modern web framework such as FastAPI or Flask; hands on experience with relational databases, with Postgres named; a solid understanding of API design, authentication and authorisation, background job patterns and robust error handling; experience building for cloud infrastructure on Azure, AWS or GCP; and comfort operating services in production using logs, metrics, dashboards and alerts, including participation in an on call rotation. The on call expectation is stated explicitly in the requirements rather than buried, which is honest and worth knowing before you apply. Location is Bengaluru. Domain context: Harvey builds AI tools for legal and professional services work, so the backend serves a product where users are lawyers acting on the output. That raises the bar on correctness, traceability and data handling compared with a general consumer product, and background job patterns appearing in the requirements is a hint about the workload shape, since document processing and model inference are long running rather than request response. Company culture as published: three stated values, decisiveness, simplicity and Job's Not Finished, with candid language about moving fast, operating with intensity and staying close to customers. Two of Harvey's three engineering roles today ask for 12+ years and the third asks for 10+, so this is a consistently senior team rather than a mixed one. Good fit for a backend engineer with twelve or more years who wants Python depth on an AI product and accepts a genuine on call rotation as part of the role.