{
"endpoint": "ats-jobs",
"count": 1,
"truncated": true,
"took_ms": 5653,
"items": [
{
"ats": "greenhouse",
"companySlug": "stripe",
"companyName": "Stripe",
"jobId": "8172508",
"title": "Abuse Investigator",
"department": "8611 Security Analytics",
"location": "Dublin",
"locations": [
"Dublin",
"Ireland Locations"
],
"isRemote": false,
"postedAt": "2026-09-03T17:32:53.000Z",
"updatedAt": "2026-10-29T14:42:09.000Z",
"jobUrl": "https://stripe.com/jobs/search?gh_jid=8172508",
"applyUrl": "https://stripe.com/jobs/search?gh_jid=8172508",
"descriptionText": "Who we are\n\nAbout Stripe\n\nStripe is a financial infrastructure platform for businesses. Millions of companies - from the world’s largest enterprises to the most ambitious startups - use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone's reach while doing the most important work of your career.\n\nAbout the team\n\nAbuse Operations is the front-line incident response and remediation function handling active product abuse and fraud impacting Stripe and its merchants. This multi-disciplinary group, spanning Incident Managers, Investigators, Forward Deployed Security Engineers, and Data Scientists, neutralizes active attacks, gathers requirements for operational tooling, and leads incidents. The team works directly with impacted merchants to resolve technical incidents and policy abuse rapidly. Operating primarily across Eastern, Pacific and Western European time zones, these team members regularly coordinate with global stakeholders across the world.\n\nWhat you’ll do\n\nYou'll play a critical role in safeguarding our financial ecosystem by investigating high-risk accounts and identifying complex patterns of fraud during incidents. You will lead incident response for product abuse and fraud events, conducting deep-dive analyses to identify root causes. By collaborating cross-functionally, you will drive improvements that enhance our fraud detection and prevention strategies at scale. Your expertise will be essential in automating response processes through agentic approaches, allowing us to safeguard merchants and neutralize threats with speed and precision.\n\nResponsibilities\n\n• Investigate, mitigate, and remediate urgent fraud incidents (e.g., ATO, card testing), utilizing FT3-mapped detection and signals enrichment to reduce uncertainty and accelerate response.\n\n• As part of incidents, analyze high-risk accounts to identify fraudulent merchants, card testing, account takeovers, and other fraud vectors, classifying them using FT3 (Fraud Taxonomy 3.0) to standardize threat intelligence.\n\n• Lead incident root cause analyses to identify gaps in current systems and strategies, leveraging the FT3 framework, data-driven model to drive enhancements and process improvements for emerging fraud risks.\n\n• Streamline incident response capabilities, ensuring the tooling and processes are clear, accurate and efficient\n\n• Work cross-functionally with security, fraud and data science teams to build agentic solutions for responding to abuse incidents at scale\n\n• Effectively communicate cross-functionally with legal and policy teams to assess and mitigate risks, while demonstrating strong problem-solving under pressure.\n\n• Collaborate effectively with teammates, leading projects, mentoring others, and developing and championing quality standards within the team\n\nWho you are\n\nWe're looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement.\n\nMinimum requirements\n\n• 3+ years of experience conducting incident response in security, product abuse or trust domains\n\n• 3+ years experience analyzing large data sets to solve problems and/or building models with a behavioral approach to fraud detection\n\n• B.S. or M.S. Computer Science or related field, or equivalent experience\n\n• Expert knowledge of Python and SQL, and familiarity with other programming languages\n\n• Existing experience with log analysis (e.g. first or third party applications, system / data access, event logs), network security, digital forensics, and incident response investigations\n\n• Ability to communicate results clearly and focus on impact\n\n• Ability to think creatively and holistically about reducing risk in a complex environment\n\nPreferred qualifications\n\n• An adversarial mindset, understanding the goals, behaviors, and TTPs of threat actors.\n\n• Experience with engineering, data processing and analysis tools (e.g. Databricks, Trino, etc.)\n\n• Familiarity with common open-source frameworks for big data processing and/or data science (PySpark, Pandas, Sci-kit Learn, etc.)\n\n• Experience with tactical threat intelligence and/or hunting for sophisticated threat actors in an enterprise environment\n\n• Ability to proactively challenge the status quo by leveraging data and taking a user-centric approach to address complex product integrity challenges",
"companyInput": "stripe",
"scrapedAt": "2026-11-11T16:07:12.668Z"
}
]
}
curl --location --request GET 'https://zylalabs.com/api/14933/applicant+tracking+system+jobs+api/39020/get+company+ats+job+postings?companies=stripe&postedWithinDays=OptionalremoteOnly=false&limit=2' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Applicant Tracking System Jobs API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime.
(Save 2 months with annual billing 🎉)
Live job postings from named company applicant tracking systems, as structured JSON.
Every response is JSON with a count, a took_ms field and an items array of flat records ready to store or query.
No. Requests are handled server-side; you only send your API key and the parameters described in this endpoint.
Each call reads the source live, so the records reflect the state of the upstream source at request time.
You receive an explicit error status instead of an empty result, so a failure is never mistaken for no data.
Yes, each endpoint caps the number of records per request; the maximum is stated in the limit parameter.
This endpoint returns live job postings from specified companies, including details such as job title, location, remote status, employment type, posting date, and department.
Key fields include `jobId`, `title`, `department`, `location`, `isRemote`, `postedAt`, `jobUrl`, and `applyUrl`, providing essential information about each job posting.
The response is structured as a JSON object containing a `count`, `took_ms`, and an `items` array, where each item represents a job posting with detailed attributes.
The endpoint provides information on job titles, locations, remote work options, employment types, posting dates, and department affiliations for each job listing.
Users can customize requests by specifying parameters such as company name or job title to filter the results according to their needs.
For example, `isRemote` indicates whether the job can be performed remotely, while `postedAt` shows when the job was listed, helping users assess job recency.
Typical use cases include job aggregation for job boards, recruitment analytics, and market research to understand hiring trends in specific industries or locations.
Data accuracy is maintained by directly reading from the applicant tracking systems of companies, ensuring that the information reflects the most current job postings available.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund