Jobs by Ashby Search
Search for jobs by Ashby via API. Supply a board. Sample fields include creation times and links. Use it to surface relevant records in a search or discovery tool. The POST request schema also lists timeout. Use the results to organize a research workflow and cross-check the relevant source records.
- Selected price
- $0.00015 / callPublished pricing
- Sellers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
litescrapeCurrent Jobs by Ashby Search · POST | $0.00015 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
jobs_resultsobject[]apply_linkstringcompany_namestringcompensationobjectcompensationTierSummarystringcompensationTiersobject[]additionalInformationnullcomponentsobject[]compensationTypestringcurrencyCodestring | nullidstringintervalstringmaxValuenull | integerminValuenull | integersummarystring
idstringtierSummarystringtitlestring
scrapeableCompensationSalarySummarystringsummaryComponentsobject[]compensationTypestringcurrencyCodestring | nullintervalstringmaxValuenull | integerminValuenull | integer
departmentstringdescriptionstringemployment_typesstring[]is_remotebooleanjob_idstringlinkstringlocationstringpositionintegerposted_atstringsalaryobjecttextstring
secondary_locationsstring[]teamstringtitlestringworkplace_typesstring[]
litescrape_paginationobjectcurrentintegernextstringnext_pageinteger
paginationobjectcurrentintegernext_pageinteger
search_informationobjectjobs_results_statestringtotal_resultsinteger
search_metadataobjectcreated_atstringidstringjson_endpointstringprocessed_atstringstatusstringtotal_time_takennumber
search_parametersobjectboardstringinclude_compensationbooleanlimitintegerpageinteger
submit_feedback_for_this_response_herestring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
jobs_results?: Array<{
apply_link?: string;
company_name?: string;
compensation?: {
compensationTierSummary?: string;
compensationTiers?: Array<{
additionalInformation?: null;
components?: Array<{
compensationType?: string;
currencyCode?: string | null;
id?: string;
interval?: string;
maxValue?: null | number;
minValue?: null | number;
summary?: string;
}>;
id?: string;
tierSummary?: string;
title?: string;
}>;
scrapeableCompensationSalarySummary?: string;
summaryComponents?: Array<{
compensationType?: string;
currencyCode?: string | null;
interval?: string;
maxValue?: null | number;
minValue?: null | number;
}>;
};
department?: string;
description?: string;
employment_types?: Array<string>;
is_remote?: boolean;
job_id?: string;
link?: string;
location?: string;
position?: number;
posted_at?: string;
salary?: {
text?: string;
};
secondary_locations?: Array<string>;
team?: string;
title?: string;
workplace_types?: Array<string>;
}>;
litescrape_pagination?: {
current?: number;
next?: string;
next_page?: number;
};
pagination?: {
current?: number;
next_page?: number;
};
search_information?: {
jobs_results_state?: string;
total_results?: number;
};
search_metadata?: {
created_at?: string;
id?: string;
json_endpoint?: string;
processed_at?: string;
status?: string;
total_time_taken?: number;
};
search_parameters?: {
board?: string;
include_compensation?: boolean;
limit?: number;
page?: number;
};
submit_feedback_for_this_response_here?: string;
};- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/litescrape/api/ashby/search- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/litescrape/api/ashby/search' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"board": "ashby",
"q": "engineer"
}'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
timeout | URL query parametersquery | number | No | Total request execution budget in seconds, greater than 0 and at most 90. Supply in the query string for GET or POST. page_timeout cannot extend this budget. maximum: 90 |
board | JSON request bodybody | string | Yes | Employer board name from jobs.ashbyhq.com/{board}, for example ashby. pattern: ^[A-Za-z0-9][A-Za-z0-9_-]{0,127}$ |
city | JSON request bodybody | string | null | No | City from a primary or secondary postal address. All supplied address filters must match the same address. |
country | JSON request bodybody | string | null | No | Country from a primary or secondary postal address, for example USA. Exact case-insensitive match. |
department | JSON request bodybody | string | null | No | Case-insensitive department name. |
employment_type | JSON request bodybody | string | null | No | Employment type. |
include_compensation | JSON request bodybody | boolean | No | Include published compensation tiers and salary ranges. |
limit | JSON request bodybody | integer | No | Results per page. minimum: 1 · maximum: 100 |
location | JSON request bodybody | string | null | No | Case-insensitive phrase in primary or secondary locations. |
page | JSON request bodybody | integer | No | One-based results page. Use next_page from the response to continue. minimum: 1 |
q | JSON request bodybody | string | null | No | Case-insensitive phrase in title or description. |
region | JSON request bodybody | string | null | No | State or province from a primary or secondary postal address. Exact case-insensitive match. |
remote | JSON request bodybody | boolean | null | No | True selects remote jobs. False selects non-remote jobs. |
team | JSON request bodybody | string | null | No | Exact team name, case-insensitive. |
workplace_type | JSON request bodybody | string | null | No | Employer's workplace type. |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Example from the provider's documentation. Field values in your results will differ.
{
"jobs_results": [
{
"apply_link": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2/application",
"company_name": "ashby",
"compensation": {
"compensationTierSummary": "€110K – €185K • Offers Equity • Offers Bonus",
"compensationTiers": [
{
"additionalInformation": null,
"components": [
{
"compensationType": "Bonus",
"currencyCode": "EUR",
"id": "04679796-e0e4-4d9b-a5c0-0cad3ff8ae95",
"interval": "1 YEAR",
"maxValue": null,
"minValue": null,
"summary": "Offers Bonus"
},
{
"compensationType": "EquityPercentage",
"currencyCode": null,
"id": "da741ab6-ff38-4fc2-b7b7-c1ccd7260347",
"interval": "NONE",
"maxValue": null,
"minValue": null,
"summary": "Offers Equity"
},
{
"compensationType": "Salary",
"currencyCode": "EUR",
"id": "201b8495-aa7c-417d-923b-94fced49b246",
"interval": "1 YEAR",
"maxValue": 185000,
"minValue": 110000,
"summary": "€110K – €185K"
}
],
"id": "f1284fac-20e9-4ed0-9a10-776d526a636c",
"tierSummary": "€110K – €185K • Offers Equity • Offers Bonus",
"title": "EU"
}
],
"scrapeableCompensationSalarySummary": "€110K - €185K",
"summaryComponents": [
{
"compensationType": "Bonus",
"currencyCode": "EUR",
"interval": "1 YEAR",
"maxValue": null,
"minValue": null
},
{
"compensationType": "EquityPercentage",
"currencyCode": null,
"interval": "NONE",
"maxValue": null,
"minValue": null
},
{
"compensationType": "Salary",
"currencyCode": "EUR",
"interval": "1 YEAR",
"maxValue": 185000,
"minValue": 110000
}
]
},
"department": "Engineering",
"description": "Hi 👋 I’m Colin https://uk.linkedin.com/in/colinhoweuk, Director of Engineering, Europe. How do you feel about software engineers writing product specs, making product decisions, and not breaking down projects into individual tickets? If that sounds exciting (even if a bit scary), read on because I’m looking for an engineering manager to help us build a different type of engineering team and culture at Ashby.\n\nTo start, why do we need to be different? Time and again, I have witnessed engineers knowing what needs to be done yet being unable to get things done because of “the process” or because “more data is needed.” Some of the most effective projects have been skunkworks projects, where engineers have taken total ownership of a problem and driven it to completion. I want to normalize that at Ashby.\n\nWhen we think about how these processes came about, we realize they carry a pessimistic mindset. They box people into smaller roles to minimize the chance of not meeting a certain standard. At Ashby. we’re building an environment that is optimistic about what engineers can own and achieve and embraces the innovative engineers (and frankly, often stays out of their way).\n\nTo accomplish this, our engineering leaders need to think deeply about individual performance, process, and culture - not running sprint planning or driving product and technical decisions. You’ll focus on building your team, their skills to thrive with the ownership they’re given, and an environment that empowers them to do their best work consistently, with little distraction. For junior EMs we try to stay within 6 direct reports. This enables them to spend time with our teams observing, correcting, praising, and, yes, coding. We like our managers to be hands-on while also making sure they’re not on the critical path.\n\nWe’ve already gathered an experienced, talented, and collaborative team https://www.ashbyhq.com/team of 25+ engineers. You’ll help me manage the growing team of engineers in Europe.\n\nIn addition to working with engineers you’ll also get to work on projects yourselves. Some examples of work our engineering leaders have done:\n\n - Provide feedback on product and technical specs to help engineers identify where to cut scope or improve quality. You don’t make the final decisions, but you’ll influence and coach ICs to reach the right ones.\n\n - Grow engineers to the point where they can take large, loosely defined projects, and deliver them with little intervention. They still ask for help when needed - the difference is that they’re driving.\n\n - Jump into our systems and code to debug a customer issue, ship a small bug fix, or improve our developer experience. Engineering leaders at Ashby are great engineers and enjoy keeping their skills up-to-date (while staying off the critical path).\n\n - Improve how we generate and simulate data in demo accounts. It’s a project off the critical path, but it helps you keep up-to-date on our codebase while immensely impacting the business, from Engineering to QA to Sales.\n \n \n\n\nWHY BE A MANAGER?\n\nI had two experiences early in my career that set me on my path. I had a great manager who asked tonnes of questions about the decisions I was making and coached me without me realizing it. And I had a terrible manager - being told to work harder after a week of 3am finishes was not what I needed as a young engineer. The stark difference between these two experiences motivated me to become a manager: I wanted every engineer I worked with to have the support I had in the best case.\n\nSince then, as I’ve learned more, I’ve realized that I love the kind of problems I get to solve as a manager. Deeply complex problems with long-term impact both on the company and on people’s lives. One of my proudest achievements is creating a fully transparent pay system, and on the day it was revealed, everybody was happy with it. Nobody stormed out. By spending time thinking deeply about everybody’s pay and ensuring the mechanics of promotion were clear, I put the team in a place where they could see a peer was paid more than them, and it not be a problem.\n\nDespite all this, I love being technical. I sometimes indulge myself and spend a morning writing some code to improve tests or provide better abstractions. If I couldn’t be a manager, I’d be super happy to be an IC.\n\nI’m looking for someone who is passionate. Passionate about both management and being technical. Someone who spots a pattern amongst their team, figures out a better way for us to operate, and then builds the automation that powers it. I introduced a new process that enables engineers to merge 30% of PRs without a human review beforehand. I also built the automation that approves these PRs. I also built that automation with abstractions that make it easy for the engineers to improve the automation themselves.\n\nIt can be hard to find seasoned engineering leaders who haven’t succumbed to the status quo in some way or another. We're committed to giving all our people a total and utter lack of terrible managers, and that means we're willing to take a chance on someone early in their leadership journey who's courageous, principled, and has the drive to build themselves into a great leader who can say “Yah I know everyone is doing that, but we won't because...”\n\n\n\n\nWHAT WE’RE BUILDING\n\nAs engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition (TA) software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.\n\nScheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵 TA software didn’t help.\n\nAs hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are!\n\nAs we’ve set the standard for excellence in TA software, HR teams have pulled us into solving their problems in areas like onboarding and performance management.\n\n\n\n\nWHY YOU SHOULD OR SHOULDN’T APPLY\n\nEngineering leadership comes in many flavors, not all of which fit our model. I thought I’d outline some things I’m looking for to help you decide if this fits what you’re looking for:\n\n - You love being technical and can hold in-depth conversations with direct reports from infra to backend to frontend.\n\n - You enjoy management problems. We want people who get excited about driving people to be their best, giving difficult feedback, and building systems that make this easier\n\n - You hold your team to a high standard and don’t shy away from getting into the details and giving feedback, even to the best folks on your team.\n\n - You are an excellent and empathetic communicator. Facilitating change at both an individual and organization level requires understanding how to navigate the beliefs, opinions, and past experiences of engineers and figuring out how to both convince them of a new way of doing things while also leaving yourself open to feedback. \n\n - You know what exceptional engineers look like. You’ve thought deeply about what makes them tick, how to recruit them, and how to grow folks into them. I want to see depth here, the industry often regurgitates a vanilla description, but the reality is more nuanced.\n\n - You’re good at thinking about product, business, and maybe even design, but you’re not interested in calling the shots and are more interested in building a team that can make the best decisions without you.\n\n - You thrive in high-trust, high-autonomy environments. We're a young startup where leaders wear multiple hats, and you'll build your own (high-speed) on-ramp through developing strong feedback loops.\n \n \n\nPut another way, you shouldn’t apply if:\n\n - You don’t enjoy coding or don’t find time to stay up-to-date on technology.\n\n - You’ve gotten into management because it was the only growth path available\n\n - You want to make all the product decisions instead of empowering your team to make those calls.\n\n - You're happy with a team of engineers that are predominantly early-career, mid-career, or don't thrive with ownership or autonomy. With enough guardrails, the team can get things done.\n\n - A staff or principal engineer to you is someone who spends most of their time project managing or doing architecture reviews.\n\n - You’re not optimistic or convinced that we can build a large engineering team that functions differently than the status quo. You think, at some size, common processes need to be implemented to ensure consistent product delivery (e.g., sprint planning, product managers writing in-depth specifications). You might not say it out loud, but you think, at some size, compromises have to be made for the sake of hiring numbers.\n\n\n\n\nENGINEERING CULTURE\n\nOur engineering culture is motivated by Abhik https://www.linkedin.com/in/abhikpramanik/ and Benji https://www.linkedin.com/in/benjaminencz/’s (our co-founders) belief that a small talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:\n\n - Minimal process with ownership over decisions normally made by product and design\n\n - Natural collaboration and deliberate communication\n\n - Investing in tools and abstractions that give us leverage\n\n - Putting effort into building a diverse team\n\n \n \n\n\nMINIMAL PROCESS & LOTS OF OWNERSHIP\n\nThe best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise.\n\nTraditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.”\n\nAt Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive.\n\n \n\n\nCOLLABORATION IS NATURAL & COMMUNICATION IS DELIBERATE\n\nOur engineering team consists of lifelong learners who are talented but also humble and kind (meet them here https://www.ashbyhq.com/team!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here https://www.ashbyhq.com/blog/company/thoughtful-communication).\n\nTo drive it home, here's a recent calendar of an engineer who has been with us for over 4 years. ~34 hours of focus time, 2.5h of interviews, and 3.5 hours of meetings:\n\n \n[https://app.ashbyhq.com/api/images/user-content/4ea5f68e-c33e-4ac9-831a-e732bee4a303/d4679311-9dba-4031-bf5e-19ce78597ab1/calendar.png]\n \n\nWe also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region.\n\n \n\n\nINCREASE LEVERAGE, NOT TEAM SIZE\n\nWe built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We’ve done this through investment in:\n\n - Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience 💪🏾.\n\n - Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below).\n\n - AI-powered tooling. We think of AI as a way to automate the mundane parts of building and maintaining high-quality software. We use a combination of third-party and internally built tools that, for instance, auto-triage customer issues, suggest fixes, prototype ideas, generate production-ready code, and conduct code reviews. Engineers have an unlimited token budget (but are not measured on it). We write in detail about our philosophy, current use of AI, and future plans for AI in Engineering here https://www.ashbyhq.com/blog/engineering/ai-ashby-engineering-and-the-future.\n\nHere’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby:\n\n \n[https://app.ashbyhq.com/api/images/user-content/4ea5f68e-c33e-4ac9-831a-e732bee4a303/8d94727a-46d8-42a2-9627-ddcd7f822f95/arjun.png]\n \n\nAnd a demo of one of these building blocks:\n\n\n\n\nPUT EFFORT INTO DIVERSITY\n\nDiverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non-diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups.\n\nToday, 25% of engineers and 50% of our engineering leaders at Ashby are from underrepresented groups. We are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more.\n\n \n\n\nWORK-LIFE BALANCE: IT’S A MARATHON, NOT A SPRINT\n\nThe intensity of work at Ashby should feel like a marathon, not a sprint (nor speed-walking). We work with urgency and ambition to build excellent software, but we don’t need to prove out a new software category or product-market fit. That requires ingenuity and thoughtfulness, and that doesn’t happen with unrealistic deadlines or sleepless nights.\n\nOur remote, low-meeting, high-ownership culture gives you a lot of flexibility in how you structure your days and weeks. In practice, that means you keep your own hours, but there will be moments of intensity, like launching your feature at our annual user conference. We offer unlimited PTO, and you actually get to use it. Some of our most exceptional engineers take almost 30 days of vacation per year.\n\nThis way of working allows many of us on the team to be active parents, including Benji and Abhik. Abhik blocks off 1.5 hours every morning to spend with his daughter and drop her off at school. Mujda https://www.linkedin.com/in/mujdaalamzai/ (Product Engineer) puts it best in an article https://nextplayso.substack.com/p/should-you-join-ashby about us: “I can say that Ashby is a great place to be a mom… No one bats an eye if I have to take my kid to a doctor’s appointment or have to work weird hours because childcare fell through.”\n\n \n\n\nINTERVIEW PROCESS\n\nAt Ashby, our team and interview process want to help you show your best self. We’ll dive into past projects and simulate working together. Our interview process is six interviews in the following order: \n\n 1. Intro Call (30m) - Discuss your application questions, align on the responsibilities of the role, and answer questions about Ashby.\n\n 2. Past Experience Deep Dive (1h) - Discuss your past experience as an engineering leader.\n\n 3. Technical Screen (1h) - Add a feature back to Ashby. You'll spend most of your time understanding a specific part of our codebase and write less than 15 lines of code.\n\n 4. Coffee Chat with VP of Engineering (1h) - Spend time with our VP of Engineering and get to know each other.\n\n 5. Meet the Team (2h) - At this point, the engineering leadership team is excited about you and you'll meet our CEO, Engineers, Product Managers, and some other folks on the team.\n\nI will be your main point of contact and prepare you for interviews. If we don’t give an offer, we’ll provide feedback!\n\n\n\n\nTECHNOLOGY STACK\n\nI’m sharing our tech stack with the caveat that we don’t require previous experience in it (but a love of typed languages is helpful 😀): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.\n\nWhen they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben https://linkedin.com/in/benasher44/), platforms like iOS (Tom https://www.linkedin.com/in/tom-quist-0925a199/) and Windows (Adam https://www.linkedin.com/in/adam-lusch/). We care more about fundamentals (e.g., debugging, abstractions) and how fast you learn. For folks on the team who switched, it's nice seeing changes hot reload versus waiting for XCode to compile 😅.\n\n \n\n\nBENEFITS\n\n - Competitive salary and equity.\n\n - 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable.\n\n - Unlimited PTO, and we will encourage you to take it.\n\n - A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements.\n\n - Generous equipment, software, and office furniture budget. Get what you need to be happy and productive!\n\n - $100/month education budget with more expensive items (like conferences) covered with manager approval.\n\n - $250/month tool budget plus access to Claude, Cursor, and Codex with generous token budgets.\n\n - If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us.\n\nAshby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply.\n\nAshby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.\n\nAshby is committed to a fair and transparent hiring process. We confirm that this advertisement is for an active, existing vacancy within our organization. Please be advised that we may use artificial intelligence-driven tools to assist our recruitment team in screening, assessing, and selecting candidates for this position.",
"employment_types": [
"FullTime"
],
"is_remote": true,
"job_id": "7458d4e9-da2e-47bd-98cb-adfda43d42b2",
"link": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2",
"location": "Remote - European Union",
"position": 1,
"posted_at": "2024-03-04T14:29:08.532+00:00",
"salary": {
"text": "€110K - €185K"
},
"secondary_locations": [
"Spain",
"Italy",
"Germany",
"Switzerland",
"Denmark",
"Norway",
"Croatia",
"Ireland",
"Stockholm",
"Romania",
"Austria",
"Barcelona",
"Netherlands",
"Portugal",
"France",
"Berlin",
"Sweden",
"Hungary",
"Estonia"
],
"team": "EMEA Engineering",
"title": "Engineering Manager - EU",
"workplace_types": [
"Remote"
]
}
],
"litescrape_pagination": {
"current": 1,
"next": "https://api.litescrape.com/api/ashby/search?page=2&board=ashby&limit=20&include_compensation=True",
"next_page": 2
},
"pagination": {
"current": 1,
"next_page": 2
},
"search_information": {
"jobs_results_state": "Results found",
"total_results": 68
},
"search_metadata": {
"created_at": "2026-10-11T05:16:29.509549+00:00",
"id": "50f6b4bda78fccaa7a6944df",
"json_endpoint": "https://api.litescrape.com/api/ashby/search?page=1&board=ashby&limit=20&include_compensation=True",
"processed_at": "2026-10-11T05:16:29.891849+00:00",
"status": "Success",
"total_time_taken": 0.391
},
"search_parameters": {
"board": "ashby",
"include_compensation": true,
"limit": 20,
"page": 1
},
"submit_feedback_for_this_response_here": "https://ecll-litescrape-v3--site-api-web.modal.run/api/feedback/example-not-a-valid-token"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# Jobs by Ashby Search
Search for jobs by Ashby via API. Supply a board. Sample fields include creation times and links. Use it to surface relevant records in a search or discovery tool. The POST request schema also lists timeout. Use the results to organize a research workflow and cross-check the relevant source records.
## Available implementations
litescrape · Jobs by Ashby Search: https://openany.si/markets/apis/capabilities/ashby-jobs-by-ashby-search?offering=2763c03a-f8a4-4b31-96b3-aea3a36b4fd2 · $0.00015 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/ashby-jobs-by-ashby-search
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/litescrape/api/ashby/search
Price: $0.00015 / call
Provider: litescrape
Contract revision: 3
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/litescrape/api/ashby/search' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"board": "ashby",
"q": "engineer"
}'
```
## API contract
```json
{
"resource_type": "api",
"name": "Jobs by Ashby Search",
"endpoint": "https://api.openany.si/v1/agent-apis/litescrape/api/ashby/search",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Total request execution budget in seconds, greater than 0 and at most 90. Supply in the query string for GET or POST. page_timeout cannot extend this budget.",
"location": "query",
"maximum": "90",
"name": "timeout",
"nullable": false,
"required": false,
"type": "number"
},
{
"description": "Search jobs on a company's Ashby job board.",
"json_schema": {
"additionalProperties": false,
"examples": [
{
"board": "ashby",
"q": "engineer"
}
],
"properties": {
"board": {
"description": "Employer board name from jobs.ashbyhq.com/{board}, for example ashby.",
"pattern": "^[A-Za-z0-9][A-Za-z0-9_-]{0,127}$",
"title": "Board",
"type": "string",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-board",
"label": "Board",
"summary": "Employer board name from jobs.ashbyhq.com/{board}, for example ashby."
}
},
"city": {
"anyOf": [
{
"maxLength": 512,
"minLength": 1,
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "City from a primary or secondary postal address. All supplied address filters must match the same address.",
"title": "City",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-city",
"label": "City",
"summary": "City from a primary or secondary postal address. All supplied address filters must match the same address."
}
},
"country": {
"anyOf": [
{
"maxLength": 512,
"minLength": 1,
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Country from a primary or secondary postal address, for example USA. Exact case-insensitive match.",
"title": "Country",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-country",
"label": "Country",
"summary": "Country from a primary or secondary postal address, for example USA. Exact case-insensitive match."
}
},
"department": {
"anyOf": [
{
"maxLength": 512,
"minLength": 1,
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Case-insensitive department name.",
"title": "Department",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-department",
"label": "Department",
"summary": "Case-insensitive department name."
}
},
"employment_type": {
"anyOf": [
{
"enum": [
"FullTime",
"PartTime",
"Intern",
"Contract",
"Temporary"
],
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Employment type.",
"title": "Employment Type",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-employment_type",
"label": "Employment Type",
"summary": "Employment type."
}
},
"include_compensation": {
"default": true,
"description": "Include published compensation tiers and salary ranges.",
"title": "Include Compensation",
"type": "boolean",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-include_compensation",
"label": "Include Compensation",
"summary": "Include published compensation tiers and salary ranges."
}
},
"limit": {
"default": 20,
"description": "Results per page.",
"maximum": 100,
"minimum": 1,
"title": "Limit",
"type": "integer",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-limit",
"label": "Limit",
"summary": "Results per page."
}
},
"location": {
"anyOf": [
{
"maxLength": 512,
"minLength": 1,
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Case-insensitive phrase in primary or secondary locations.",
"title": "Location",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-location",
"label": "Location",
"summary": "Case-insensitive phrase in primary or secondary locations."
}
},
"page": {
"default": 1,
"description": "One-based results page. Use next_page from the response to continue.",
"minimum": 1,
"title": "Page",
"type": "integer",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-page",
"label": "Page",
"summary": "One-based results page. Use next_page from the response to continue."
}
},
"q": {
"anyOf": [
{
"maxLength": 512,
"minLength": 1,
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Case-insensitive phrase in title or description.",
"title": "Q",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-q",
"label": "Q",
"summary": "Case-insensitive phrase in title or description."
}
},
"region": {
"anyOf": [
{
"maxLength": 512,
"minLength": 1,
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "State or province from a primary or secondary postal address. Exact case-insensitive match.",
"title": "Region",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-region",
"label": "Region",
"summary": "State or province from a primary or secondary postal address. Exact case-insensitive match."
}
},
"remote": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"default": null,
"description": "True selects remote jobs. False selects non-remote jobs.",
"title": "Remote",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-remote",
"label": "Remote",
"summary": "True selects remote jobs. False selects non-remote jobs."
}
},
"team": {
"anyOf": [
{
"maxLength": 512,
"minLength": 1,
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Exact team name, case-insensitive.",
"title": "Team",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-team",
"label": "Team",
"summary": "Exact team name, case-insensitive."
}
},
"workplace_type": {
"anyOf": [
{
"enum": [
"OnSite",
"Remote",
"Hybrid"
],
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Employer's workplace type.",
"title": "Workplace Type",
"x-litescrape": {
"formGroup": 0,
"group": 0,
"id": "ashby-search-workplace_type",
"label": "Workplace Type",
"summary": "Employer's workplace type."
}
}
},
"required": [
"board"
],
"title": "Request",
"type": "object"
},
"location": "body",
"name": "body",
"nullable": false,
"pointer": "",
"required": true,
"type": "object"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "150",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Official example (abridged)",
"request": {
"body": {
"board": "ashby",
"q": "engineer"
},
"headers": {},
"path": {},
"query": {}
},
"response_body": {
"jobs_results": [
{
"apply_link": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2/application",
"company_name": "ashby",
"compensation": {
"compensationTierSummary": "€110K – €185K • Offers Equity • Offers Bonus",
"compensationTiers": [
{
"additionalInformation": null,
"components": [
{
"compensationType": "Bonus",
"currencyCode": "EUR",
"id": "04679796-e0e4-4d9b-a5c0-0cad3ff8ae95",
"interval": "1 YEAR",
"maxValue": null,
"minValue": null,
"summary": "Offers Bonus"
},
{
"compensationType": "EquityPercentage",
"currencyCode": null,
"id": "da741ab6-ff38-4fc2-b7b7-c1ccd7260347",
"interval": "NONE",
"maxValue": null,
"minValue": null,
"summary": "Offers Equity"
},
{
"compensationType": "Salary",
"currencyCode": "EUR",
"id": "201b8495-aa7c-417d-923b-94fced49b246",
"interval": "1 YEAR",
"maxValue": 185000,
"minValue": 110000,
"summary": "€110K – €185K"
}
],
"id": "f1284fac-20e9-4ed0-9a10-776d526a636c",
"tierSummary": "€110K – €185K • Offers Equity • Offers Bonus",
"title": "EU"
}
],
"scrapeableCompensationSalarySummary": "€110K - €185K",
"summaryComponents": [
{
"compensationType": "Bonus",
"currencyCode": "EUR",
"interval": "1 YEAR",
"maxValue": null,
"minValue": null
},
{
"compensationType": "EquityPercentage",
"currencyCode": null,
"interval": "NONE",
"maxValue": null,
"minValue": null
},
{
"compensationType": "Salary",
"currencyCode": "EUR",
"interval": "1 YEAR",
"maxValue": 185000,
"minValue": 110000
}
]
},
"department": "Engineering",
"description": "Hi 👋 I’m Colin https://uk.linkedin.com/in/colinhoweuk, Director of Engineering, Europe. How do you feel about software engineers writing product specs, making product decisions, and not breaking down projects into individual tickets? If that sounds exciting (even if a bit scary), read on because I’m looking for an engineering manager to help us build a different type of engineering team and culture at Ashby.\n\nTo start, why do we need to be different? Time and again, I have witnessed engineers knowing what needs to be done yet being unable to get things done because of “the process” or because “more data is needed.” Some of the most effective projects have been skunkworks projects, where engineers have taken total ownership of a problem and driven it to completion. I want to normalize that at Ashby.\n\nWhen we think about how these processes came about, we realize they carry a pessimistic mindset. They box people into smaller roles to minimize the chance of not meeting a certain standard. At Ashby. we’re building an environment that is optimistic about what engineers can own and achieve and embraces the innovative engineers (and frankly, often stays out of their way).\n\nTo accomplish this, our engineering leaders need to think deeply about individual performance, process, and culture - not running sprint planning or driving product and technical decisions. You’ll focus on building your team, their skills to thrive with the ownership they’re given, and an environment that empowers them to do their best work consistently, with little distraction. For junior EMs we try to stay within 6 direct reports. This enables them to spend time with our teams observing, correcting, praising, and, yes, coding. We like our managers to be hands-on while also making sure they’re not on the critical path.\n\nWe’ve already gathered an experienced, talented, and collaborative team https://www.ashbyhq.com/team of 25+ engineers. You’ll help me manage the growing team of engineers in Europe.\n\nIn addition to working with engineers you’ll also get to work on projects yourselves. Some examples of work our engineering leaders have done:\n\n - Provide feedback on product and technical specs to help engineers identify where to cut scope or improve quality. You don’t make the final decisions, but you’ll influence and coach ICs to reach the right ones.\n\n - Grow engineers to the point where they can take large, loosely defined projects, and deliver them with little intervention. They still ask for help when needed - the difference is that they’re driving.\n\n - Jump into our systems and code to debug a customer issue, ship a small bug fix, or improve our developer experience. Engineering leaders at Ashby are great engineers and enjoy keeping their skills up-to-date (while staying off the critical path).\n\n - Improve how we generate and simulate data in demo accounts. It’s a project off the critical path, but it helps you keep up-to-date on our codebase while immensely impacting the business, from Engineering to QA to Sales.\n \n \n\n\nWHY BE A MANAGER?\n\nI had two experiences early in my career that set me on my path. I had a great manager who asked tonnes of questions about the decisions I was making and coached me without me realizing it. And I had a terrible manager - being told to work harder after a week of 3am finishes was not what I needed as a young engineer. The stark difference between these two experiences motivated me to become a manager: I wanted every engineer I worked with to have the support I had in the best case.\n\nSince then, as I’ve learned more, I’ve realized that I love the kind of problems I get to solve as a manager. Deeply complex problems with long-term impact both on the company and on people’s lives. One of my proudest achievements is creating a fully transparent pay system, and on the day it was revealed, everybody was happy with it. Nobody stormed out. By spending time thinking deeply about everybody’s pay and ensuring the mechanics of promotion were clear, I put the team in a place where they could see a peer was paid more than them, and it not be a problem.\n\nDespite all this, I love being technical. I sometimes indulge myself and spend a morning writing some code to improve tests or provide better abstractions. If I couldn’t be a manager, I’d be super happy to be an IC.\n\nI’m looking for someone who is passionate. Passionate about both management and being technical. Someone who spots a pattern amongst their team, figures out a better way for us to operate, and then builds the automation that powers it. I introduced a new process that enables engineers to merge 30% of PRs without a human review beforehand. I also built the automation that approves these PRs. I also built that automation with abstractions that make it easy for the engineers to improve the automation themselves.\n\nIt can be hard to find seasoned engineering leaders who haven’t succumbed to the status quo in some way or another. We're committed to giving all our people a total and utter lack of terrible managers, and that means we're willing to take a chance on someone early in their leadership journey who's courageous, principled, and has the drive to build themselves into a great leader who can say “Yah I know everyone is doing that, but we won't because...”\n\n\n\n\nWHAT WE’RE BUILDING\n\nAs engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition (TA) software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.\n\nScheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵 TA software didn’t help.\n\nAs hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are!\n\nAs we’ve set the standard for excellence in TA software, HR teams have pulled us into solving their problems in areas like onboarding and performance management.\n\n\n\n\nWHY YOU SHOULD OR SHOULDN’T APPLY\n\nEngineering leadership comes in many flavors, not all of which fit our model. I thought I’d outline some things I’m looking for to help you decide if this fits what you’re looking for:\n\n - You love being technical and can hold in-depth conversations with direct reports from infra to backend to frontend.\n\n - You enjoy management problems. We want people who get excited about driving people to be their best, giving difficult feedback, and building systems that make this easier\n\n - You hold your team to a high standard and don’t shy away from getting into the details and giving feedback, even to the best folks on your team.\n\n - You are an excellent and empathetic communicator. Facilitating change at both an individual and organization level requires understanding how to navigate the beliefs, opinions, and past experiences of engineers and figuring out how to both convince them of a new way of doing things while also leaving yourself open to feedback. \n\n - You know what exceptional engineers look like. You’ve thought deeply about what makes them tick, how to recruit them, and how to grow folks into them. I want to see depth here, the industry often regurgitates a vanilla description, but the reality is more nuanced.\n\n - You’re good at thinking about product, business, and maybe even design, but you’re not interested in calling the shots and are more interested in building a team that can make the best decisions without you.\n\n - You thrive in high-trust, high-autonomy environments. We're a young startup where leaders wear multiple hats, and you'll build your own (high-speed) on-ramp through developing strong feedback loops.\n \n \n\nPut another way, you shouldn’t apply if:\n\n - You don’t enjoy coding or don’t find time to stay up-to-date on technology.\n\n - You’ve gotten into management because it was the only growth path available\n\n - You want to make all the product decisions instead of empowering your team to make those calls.\n\n - You're happy with a team of engineers that are predominantly early-career, mid-career, or don't thrive with ownership or autonomy. With enough guardrails, the team can get things done.\n\n - A staff or principal engineer to you is someone who spends most of their time project managing or doing architecture reviews.\n\n - You’re not optimistic or convinced that we can build a large engineering team that functions differently than the status quo. You think, at some size, common processes need to be implemented to ensure consistent product delivery (e.g., sprint planning, product managers writing in-depth specifications). You might not say it out loud, but you think, at some size, compromises have to be made for the sake of hiring numbers.\n\n\n\n\nENGINEERING CULTURE\n\nOur engineering culture is motivated by Abhik https://www.linkedin.com/in/abhikpramanik/ and Benji https://www.linkedin.com/in/benjaminencz/’s (our co-founders) belief that a small talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:\n\n - Minimal process with ownership over decisions normally made by product and design\n\n - Natural collaboration and deliberate communication\n\n - Investing in tools and abstractions that give us leverage\n\n - Putting effort into building a diverse team\n\n \n \n\n\nMINIMAL PROCESS & LOTS OF OWNERSHIP\n\nThe best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise.\n\nTraditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.”\n\nAt Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive.\n\n \n\n\nCOLLABORATION IS NATURAL & COMMUNICATION IS DELIBERATE\n\nOur engineering team consists of lifelong learners who are talented but also humble and kind (meet them here https://www.ashbyhq.com/team!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here https://www.ashbyhq.com/blog/company/thoughtful-communication).\n\nTo drive it home, here's a recent calendar of an engineer who has been with us for over 4 years. ~34 hours of focus time, 2.5h of interviews, and 3.5 hours of meetings:\n\n \n[https://app.ashbyhq.com/api/images/user-content/4ea5f68e-c33e-4ac9-831a-e732bee4a303/d4679311-9dba-4031-bf5e-19ce78597ab1/calendar.png]\n \n\nWe also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region.\n\n \n\n\nINCREASE LEVERAGE, NOT TEAM SIZE\n\nWe built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We’ve done this through investment in:\n\n - Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience 💪🏾.\n\n - Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below).\n\n - AI-powered tooling. We think of AI as a way to automate the mundane parts of building and maintaining high-quality software. We use a combination of third-party and internally built tools that, for instance, auto-triage customer issues, suggest fixes, prototype ideas, generate production-ready code, and conduct code reviews. Engineers have an unlimited token budget (but are not measured on it). We write in detail about our philosophy, current use of AI, and future plans for AI in Engineering here https://www.ashbyhq.com/blog/engineering/ai-ashby-engineering-and-the-future.\n\nHere’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby:\n\n \n[https://app.ashbyhq.com/api/images/user-content/4ea5f68e-c33e-4ac9-831a-e732bee4a303/8d94727a-46d8-42a2-9627-ddcd7f822f95/arjun.png]\n \n\nAnd a demo of one of these building blocks:\n\n\n\n\nPUT EFFORT INTO DIVERSITY\n\nDiverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non-diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups.\n\nToday, 25% of engineers and 50% of our engineering leaders at Ashby are from underrepresented groups. We are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more.\n\n \n\n\nWORK-LIFE BALANCE: IT’S A MARATHON, NOT A SPRINT\n\nThe intensity of work at Ashby should feel like a marathon, not a sprint (nor speed-walking). We work with urgency and ambition to build excellent software, but we don’t need to prove out a new software category or product-market fit. That requires ingenuity and thoughtfulness, and that doesn’t happen with unrealistic deadlines or sleepless nights.\n\nOur remote, low-meeting, high-ownership culture gives you a lot of flexibility in how you structure your days and weeks. In practice, that means you keep your own hours, but there will be moments of intensity, like launching your feature at our annual user conference. We offer unlimited PTO, and you actually get to use it. Some of our most exceptional engineers take almost 30 days of vacation per year.\n\nThis way of working allows many of us on the team to be active parents, including Benji and Abhik. Abhik blocks off 1.5 hours every morning to spend with his daughter and drop her off at school. Mujda https://www.linkedin.com/in/mujdaalamzai/ (Product Engineer) puts it best in an article https://nextplayso.substack.com/p/should-you-join-ashby about us: “I can say that Ashby is a great place to be a mom… No one bats an eye if I have to take my kid to a doctor’s appointment or have to work weird hours because childcare fell through.”\n\n \n\n\nINTERVIEW PROCESS\n\nAt Ashby, our team and interview process want to help you show your best self. We’ll dive into past projects and simulate working together. Our interview process is six interviews in the following order: \n\n 1. Intro Call (30m) - Discuss your application questions, align on the responsibilities of the role, and answer questions about Ashby.\n\n 2. Past Experience Deep Dive (1h) - Discuss your past experience as an engineering leader.\n\n 3. Technical Screen (1h) - Add a feature back to Ashby. You'll spend most of your time understanding a specific part of our codebase and write less than 15 lines of code.\n\n 4. Coffee Chat with VP of Engineering (1h) - Spend time with our VP of Engineering and get to know each other.\n\n 5. Meet the Team (2h) - At this point, the engineering leadership team is excited about you and you'll meet our CEO, Engineers, Product Managers, and some other folks on the team.\n\nI will be your main point of contact and prepare you for interviews. If we don’t give an offer, we’ll provide feedback!\n\n\n\n\nTECHNOLOGY STACK\n\nI’m sharing our tech stack with the caveat that we don’t require previous experience in it (but a love of typed languages is helpful 😀): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.\n\nWhen they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben https://linkedin.com/in/benasher44/), platforms like iOS (Tom https://www.linkedin.com/in/tom-quist-0925a199/) and Windows (Adam https://www.linkedin.com/in/adam-lusch/). We care more about fundamentals (e.g., debugging, abstractions) and how fast you learn. For folks on the team who switched, it's nice seeing changes hot reload versus waiting for XCode to compile 😅.\n\n \n\n\nBENEFITS\n\n - Competitive salary and equity.\n\n - 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable.\n\n - Unlimited PTO, and we will encourage you to take it.\n\n - A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements.\n\n - Generous equipment, software, and office furniture budget. Get what you need to be happy and productive!\n\n - $100/month education budget with more expensive items (like conferences) covered with manager approval.\n\n - $250/month tool budget plus access to Claude, Cursor, and Codex with generous token budgets.\n\n - If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us.\n\nAshby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply.\n\nAshby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.\n\nAshby is committed to a fair and transparent hiring process. We confirm that this advertisement is for an active, existing vacancy within our organization. Please be advised that we may use artificial intelligence-driven tools to assist our recruitment team in screening, assessing, and selecting candidates for this position.",
"employment_types": [
"FullTime"
],
"is_remote": true,
"job_id": "7458d4e9-da2e-47bd-98cb-adfda43d42b2",
"link": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2",
"location": "Remote - European Union",
"position": 1,
"posted_at": "2024-03-04T14:29:08.532+00:00",
"salary": {
"text": "€110K - €185K"
},
"secondary_locations": [
"Spain",
"Italy",
"Germany",
"Switzerland",
"Denmark",
"Norway",
"Croatia",
"Ireland",
"Stockholm",
"Romania",
"Austria",
"Barcelona",
"Netherlands",
"Portugal",
"France",
"Berlin",
"Sweden",
"Hungary",
"Estonia"
],
"team": "EMEA Engineering",
"title": "Engineering Manager - EU",
"workplace_types": [
"Remote"
]
}
],
"litescrape_pagination": {
"current": 1,
"next": "https://api.litescrape.com/api/ashby/search?page=2&board=ashby&limit=20&include_compensation=True",
"next_page": 2
},
"pagination": {
"current": 1,
"next_page": 2
},
"search_information": {
"jobs_results_state": "Results found",
"total_results": 68
},
"search_metadata": {
"created_at": "2026-10-11T05:16:29.509549+00:00",
"id": "50f6b4bda78fccaa7a6944df",
"json_endpoint": "https://api.litescrape.com/api/ashby/search?page=1&board=ashby&limit=20&include_compensation=True",
"processed_at": "2026-10-11T05:16:29.891849+00:00",
"status": "Success",
"total_time_taken": 0.391
},
"search_parameters": {
"board": "ashby",
"include_compensation": true,
"limit": 20,
"page": 1
},
"submit_feedback_for_this_response_here": "https://ecll-litescrape-v3--site-api-web.modal.run/api/feedback/example-not-a-valid-token"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Official example (abridged)
Example from the provider's documentation. Field values in your results will differ.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 2
Review these request fields before running. Keep the published provider and request method unchanged.
timeout- Total request execution budget in seconds, greater than 0 and at most 90. Supply in the query string for GET or POST. page_timeout cannot extend this budget.
body- Search jobs on a company's Ashby job board.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/litescrape/api/ashby/search' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ --data-raw '{ "board": "ashby", "q": "engineer" }'Check the response
Sample response · Documented HTTP 200
Sample response{ "jobs_results": [ { "apply_link": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2/application", "company_name": "ashby", "compensation": { "compensationTierSummary": "€110K – €185K • Offers Equity • Offers Bonus", "compensationTiers": [ { "additionalInformation": null, "components": [ { "compensationType": "Bonus", "currencyCode": "EUR", "id": "04679796-e0e4-4d9b-a5c0-0cad3ff8ae95", "interval": "1 YEAR", "maxValue": null, "minValue": null, "summary": "Offers Bonus" }, { "compensationType": "EquityPercentage", "currencyCode": null, "id": "da741ab6-ff38-4fc2-b7b7-c1ccd7260347", "interval": "NONE", "maxValue": null, "minValue": null, "summary": "Offers Equity" }, { "compensationType": "Salary", "currencyCode": "EUR", "id": "201b8495-aa7c-417d-923b-94fced49b246", "interval": "1 YEAR", "maxValue": 185000, "minValue": 110000, "summary": "€110K – €185K" } ], "id": "f1284fac-20e9-4ed0-9a10-776d526a636c", "tierSummary": "€110K – €185K • Offers Equity • Offers Bonus", "title": "EU" } ], "scrapeableCompensationSalarySummary": "€110K - €185K", "summaryComponents": [ { "compensationType": "Bonus", "currencyCode": "EUR", "interval": "1 YEAR", "maxValue": null, "minValue": null }, { "compensationType": "EquityPercentage", "currencyCode": null, "interval": "NONE", "maxValue": null, "minValue": null }, { "compensationType": "Salary", "currencyCode": "EUR", "interval": "1 YEAR", "maxValue": 185000, "minValue": 110000 } ] }, "department": "Engineering", "description": "Hi 👋 I’m Colin https://uk.linkedin.com/in/colinhoweuk, Director of Engineering, Europe. How do you feel about software engineers writing product specs, making product decisions, and not breaking down projects into individual tickets? If that sounds exciting (even if a bit scary), read on because I’m looking for an engineering manager to help us build a different type of engineering team and culture at Ashby.\n\nTo start, why do we need to be different? Time and again, I have witnessed engineers knowing what needs to be done yet being unable to get things done because of “the process” or because “more data is needed.” Some of the most effective projects have been skunkworks projects, where engineers have taken total ownership of a problem and driven it to completion. I want to normalize that at Ashby.\n\nWhen we think about how these processes came about, we realize they carry a pessimistic mindset. They box people into smaller roles to minimize the chance of not meeting a certain standard. At Ashby. we’re building an environment that is optimistic about what engineers can own and achieve and embraces the innovative engineers (and frankly, often stays out of their way).\n\nTo accomplish this, our engineering leaders need to think deeply about individual performance, process, and culture - not running sprint planning or driving product and technical decisions. You’ll focus on building your team, their skills to thrive with the ownership they’re given, and an environment that empowers them to do their best work consistently, with little distraction. For junior EMs we try to stay within 6 direct reports. This enables them to spend time with our teams observing, correcting, praising, and, yes, coding. We like our managers to be hands-on while also making sure they’re not on the critical path.\n\nWe’ve already gathered an experienced, talented, and collaborative team https://www.ashbyhq.com/team of 25+ engineers. You’ll help me manage the growing team of engineers in Europe.\n\nIn addition to working with engineers you’ll also get to work on projects yourselves. Some examples of work our engineering leaders have done:\n\n - Provide feedback on product and technical specs to help engineers identify where to cut scope or improve quality. You don’t make the final decisions, but you’ll influence and coach ICs to reach the right ones.\n\n - Grow engineers to the point where they can take large, loosely defined projects, and deliver them with little intervention. They still ask for help when needed - the difference is that they’re driving.\n\n - Jump into our systems and code to debug a customer issue, ship a small bug fix, or improve our developer experience. Engineering leaders at Ashby are great engineers and enjoy keeping their skills up-to-date (while staying off the critical path).\n\n - Improve how we generate and simulate data in demo accounts. It’s a project off the critical path, but it helps you keep up-to-date on our codebase while immensely impacting the business, from Engineering to QA to Sales.\n \n \n\n\nWHY BE A MANAGER?\n\nI had two experiences early in my career that set me on my path. I had a great manager who asked tonnes of questions about the decisions I was making and coached me without me realizing it. And I had a terrible manager - being told to work harder after a week of 3am finishes was not what I needed as a young engineer. The stark difference between these two experiences motivated me to become a manager: I wanted every engineer I worked with to have the support I had in the best case.\n\nSince then, as I’ve learned more, I’ve realized that I love the kind of problems I get to solve as a manager. Deeply complex problems with long-term impact both on the company and on people’s lives. One of my proudest achievements is creating a fully transparent pay system, and on the day it was revealed, everybody was happy with it. Nobody stormed out. By spending time thinking deeply about everybody’s pay and ensuring the mechanics of promotion were clear, I put the team in a place where they could see a peer was paid more than them, and it not be a problem.\n\nDespite all this, I love being technical. I sometimes indulge myself and spend a morning writing some code to improve tests or provide better abstractions. If I couldn’t be a manager, I’d be super happy to be an IC.\n\nI’m looking for someone who is passionate. Passionate about both management and being technical. Someone who spots a pattern amongst their team, figures out a better way for us to operate, and then builds the automation that powers it. I introduced a new process that enables engineers to merge 30% of PRs without a human review beforehand. I also built the automation that approves these PRs. I also built that automation with abstractions that make it easy for the engineers to improve the automation themselves.\n\nIt can be hard to find seasoned engineering leaders who haven’t succumbed to the status quo in some way or another. We're committed to giving all our people a total and utter lack of terrible managers, and that means we're willing to take a chance on someone early in their leadership journey who's courageous, principled, and has the drive to build themselves into a great leader who can say “Yah I know everyone is doing that, but we won't because...”\n\n\n\n\nWHAT WE’RE BUILDING\n\nAs engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition (TA) software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.\n\nScheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵 TA software didn’t help.\n\nAs hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are!\n\nAs we’ve set the standard for excellence in TA software, HR teams have pulled us into solving their problems in areas like onboarding and performance management.\n\n\n\n\nWHY YOU SHOULD OR SHOULDN’T APPLY\n\nEngineering leadership comes in many flavors, not all of which fit our model. I thought I’d outline some things I’m looking for to help you decide if this fits what you’re looking for:\n\n - You love being technical and can hold in-depth conversations with direct reports from infra to backend to frontend.\n\n - You enjoy management problems. We want people who get excited about driving people to be their best, giving difficult feedback, and building systems that make this easier\n\n - You hold your team to a high standard and don’t shy away from getting into the details and giving feedback, even to the best folks on your team.\n\n - You are an excellent and empathetic communicator. Facilitating change at both an individual and organization level requires understanding how to navigate the beliefs, opinions, and past experiences of engineers and figuring out how to both convince them of a new way of doing things while also leaving yourself open to feedback. \n\n - You know what exceptional engineers look like. You’ve thought deeply about what makes them tick, how to recruit them, and how to grow folks into them. I want to see depth here, the industry often regurgitates a vanilla description, but the reality is more nuanced.\n\n - You’re good at thinking about product, business, and maybe even design, but you’re not interested in calling the shots and are more interested in building a team that can make the best decisions without you.\n\n - You thrive in high-trust, high-autonomy environments. We're a young startup where leaders wear multiple hats, and you'll build your own (high-speed) on-ramp through developing strong feedback loops.\n \n \n\nPut another way, you shouldn’t apply if:\n\n - You don’t enjoy coding or don’t find time to stay up-to-date on technology.\n\n - You’ve gotten into management because it was the only growth path available\n\n - You want to make all the product decisions instead of empowering your team to make those calls.\n\n - You're happy with a team of engineers that are predominantly early-career, mid-career, or don't thrive with ownership or autonomy. With enough guardrails, the team can get things done.\n\n - A staff or principal engineer to you is someone who spends most of their time project managing or doing architecture reviews.\n\n - You’re not optimistic or convinced that we can build a large engineering team that functions differently than the status quo. You think, at some size, common processes need to be implemented to ensure consistent product delivery (e.g., sprint planning, product managers writing in-depth specifications). You might not say it out loud, but you think, at some size, compromises have to be made for the sake of hiring numbers.\n\n\n\n\nENGINEERING CULTURE\n\nOur engineering culture is motivated by Abhik https://www.linkedin.com/in/abhikpramanik/ and Benji https://www.linkedin.com/in/benjaminencz/’s (our co-founders) belief that a small talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:\n\n - Minimal process with ownership over decisions normally made by product and design\n\n - Natural collaboration and deliberate communication\n\n - Investing in tools and abstractions that give us leverage\n\n - Putting effort into building a diverse team\n\n \n \n\n\nMINIMAL PROCESS & LOTS OF OWNERSHIP\n\nThe best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise.\n\nTraditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.”\n\nAt Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive.\n\n \n\n\nCOLLABORATION IS NATURAL & COMMUNICATION IS DELIBERATE\n\nOur engineering team consists of lifelong learners who are talented but also humble and kind (meet them here https://www.ashbyhq.com/team!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here https://www.ashbyhq.com/blog/company/thoughtful-communication).\n\nTo drive it home, here's a recent calendar of an engineer who has been with us for over 4 years. ~34 hours of focus time, 2.5h of interviews, and 3.5 hours of meetings:\n\n \n[https://app.ashbyhq.com/api/images/user-content/4ea5f68e-c33e-4ac9-831a-e732bee4a303/d4679311-9dba-4031-bf5e-19ce78597ab1/calendar.png]\n \n\nWe also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region.\n\n \n\n\nINCREASE LEVERAGE, NOT TEAM SIZE\n\nWe built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We’ve done this through investment in:\n\n - Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience 💪🏾.\n\n - Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below).\n\n - AI-powered tooling. We think of AI as a way to automate the mundane parts of building and maintaining high-quality software. We use a combination of third-party and internally built tools that, for instance, auto-triage customer issues, suggest fixes, prototype ideas, generate production-ready code, and conduct code reviews. Engineers have an unlimited token budget (but are not measured on it). We write in detail about our philosophy, current use of AI, and future plans for AI in Engineering here https://www.ashbyhq.com/blog/engineering/ai-ashby-engineering-and-the-future.\n\nHere’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby:\n\n \n[https://app.ashbyhq.com/api/images/user-content/4ea5f68e-c33e-4ac9-831a-e732bee4a303/8d94727a-46d8-42a2-9627-ddcd7f822f95/arjun.png]\n \n\nAnd a demo of one of these building blocks:\n\n\n\n\nPUT EFFORT INTO DIVERSITY\n\nDiverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non-diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups.\n\nToday, 25% of engineers and 50% of our engineering leaders at Ashby are from underrepresented groups. We are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more.\n\n \n\n\nWORK-LIFE BALANCE: IT’S A MARATHON, NOT A SPRINT\n\nThe intensity of work at Ashby should feel like a marathon, not a sprint (nor speed-walking). We work with urgency and ambition to build excellent software, but we don’t need to prove out a new software category or product-market fit. That requires ingenuity and thoughtfulness, and that doesn’t happen with unrealistic deadlines or sleepless nights.\n\nOur remote, low-meeting, high-ownership culture gives you a lot of flexibility in how you structure your days and weeks. In practice, that means you keep your own hours, but there will be moments of intensity, like launching your feature at our annual user conference. We offer unlimited PTO, and you actually get to use it. Some of our most exceptional engineers take almost 30 days of vacation per year.\n\nThis way of working allows many of us on the team to be active parents, including Benji and Abhik. Abhik blocks off 1.5 hours every morning to spend with his daughter and drop her off at school. Mujda https://www.linkedin.com/in/mujdaalamzai/ (Product Engineer) puts it best in an article https://nextplayso.substack.com/p/should-you-join-ashby about us: “I can say that Ashby is a great place to be a mom… No one bats an eye if I have to take my kid to a doctor’s appointment or have to work weird hours because childcare fell through.”\n\n \n\n\nINTERVIEW PROCESS\n\nAt Ashby, our team and interview process want to help you show your best self. We’ll dive into past projects and simulate working together. Our interview process is six interviews in the following order: \n\n 1. Intro Call (30m) - Discuss your application questions, align on the responsibilities of the role, and answer questions about Ashby.\n\n 2. Past Experience Deep Dive (1h) - Discuss your past experience as an engineering leader.\n\n 3. Technical Screen (1h) - Add a feature back to Ashby. You'll spend most of your time understanding a specific part of our codebase and write less than 15 lines of code.\n\n 4. Coffee Chat with VP of Engineering (1h) - Spend time with our VP of Engineering and get to know each other.\n\n 5. Meet the Team (2h) - At this point, the engineering leadership team is excited about you and you'll meet our CEO, Engineers, Product Managers, and some other folks on the team.\n\nI will be your main point of contact and prepare you for interviews. If we don’t give an offer, we’ll provide feedback!\n\n\n\n\nTECHNOLOGY STACK\n\nI’m sharing our tech stack with the caveat that we don’t require previous experience in it (but a love of typed languages is helpful 😀): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.\n\nWhen they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben https://linkedin.com/in/benasher44/), platforms like iOS (Tom https://www.linkedin.com/in/tom-quist-0925a199/) and Windows (Adam https://www.linkedin.com/in/adam-lusch/). We care more about fundamentals (e.g., debugging, abstractions) and how fast you learn. For folks on the team who switched, it's nice seeing changes hot reload versus waiting for XCode to compile 😅.\n\n \n\n\nBENEFITS\n\n - Competitive salary and equity.\n\n - 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable.\n\n - Unlimited PTO, and we will encourage you to take it.\n\n - A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements.\n\n - Generous equipment, software, and office furniture budget. Get what you need to be happy and productive!\n\n - $100/month education budget with more expensive items (like conferences) covered with manager approval.\n\n - $250/month tool budget plus access to Claude, Cursor, and Codex with generous token budgets.\n\n - If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us.\n\nAshby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply.\n\nAshby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.\n\nAshby is committed to a fair and transparent hiring process. We confirm that this advertisement is for an active, existing vacancy within our organization. Please be advised that we may use artificial intelligence-driven tools to assist our recruitment team in screening, assessing, and selecting candidates for this position.", "employment_types": [ "FullTime" ], "is_remote": true, "job_id": "7458d4e9-da2e-47bd-98cb-adfda43d42b2", "link": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2", "location": "Remote - European Union", "position": 1, "posted_at": "2024-03-04T14:29:08.532+00:00", "salary": { "text": "€110K - €185K" }, "secondary_locations": [ "Spain", "Italy", "Germany", "Switzerland", "Denmark", "Norway", "Croatia", "Ireland", "Stockholm", "Romania", "Austria", "Barcelona", "Netherlands", "Portugal", "France", "Berlin", "Sweden", "Hungary", "Estonia" ], "team": "EMEA Engineering", "title": "Engineering Manager - EU", "workplace_types": [ "Remote" ] } ], "litescrape_pagination": { "current": 1, "next": "https://api.litescrape.com/api/ashby/search?page=2&board=ashby&limit=20&include_compensation=True", "next_page": 2 }, "pagination": { "current": 1, "next_page": 2 }, "search_information": { "jobs_results_state": "Results found", "total_results": 68 }, "search_metadata": { "created_at": "2026-10-11T05:16:29.509549+00:00", "id": "50f6b4bda78fccaa7a6944df", "json_endpoint": "https://api.litescrape.com/api/ashby/search?page=1&board=ashby&limit=20&include_compensation=True", "processed_at": "2026-10-11T05:16:29.891849+00:00", "status": "Success", "total_time_taken": 0.391 }, "search_parameters": { "board": "ashby", "include_compensation": true, "limit": 20, "page": 1 }, "submit_feedback_for_this_response_here": "https://ecll-litescrape-v3--site-api-web.modal.run/api/feedback/example-not-a-valid-token" }
Common questions
Do I need a separate key for every provider?
Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.
Are these providers interchangeable?
No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.
How is this API billed?
API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.
Where do the price and contract come from?
The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.
How do OpenAny Balance and x402 differ?
OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.
Does Playground send a paid request?
Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.
Use Jobs by Ashby Search with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.