Job intelligence
Engineering Manager - EU
Ashby
Before relying on the listing: Confirm Application closing time with the employer or source. See verification questions
Executive opportunity brief
The decision in one screen
A compact evidence-first read of compensation, flexibility, mobility and what still needs verification. No universal quality score is used.
Fast read
Opportunity DNA
The available details do not point to a single standout advantage yet. The clearest issue to weigh is the salary benchmark is still shallow.
The range is usable, but the comparable sample is still too shallow for a strong relative-pay call.
Geographic eligibility is restricted to a country or region.
The listing does not make the minimum education or experience threshold clear enough yet.
Sponsorship and relocation support are not clear from the current listing.
Part of the application route can be assessed, but the full external process may contain additional steps.
At least one recent enabled source can still renew this vacancy.
This fingerprint summarizes what is clear, constrained or still unanswered in the current listing. It is a reading aid, not an overall job score.
Decision evidence check
4 of 5 core facts stated
This checks whether the listing states the facts that commonly change an employment decision. It measures disclosure completeness, not whether the opportunity is good or bad.
Facts already stated
- Compensation
- Work arrangement
- Advertised location
- Employment type
What to verify next
- Application closing time: Is there a firm application deadline, a rolling review window or no stated closing date?
Advertised location is not proof of work authorization, sponsorship, or legal eligibility. Unknown information is not a negative score; verify those questions separately.
Decision levers
What could make or break the fit?
Reasons to look closer
Nothing stands out strongly enough yet to call a clear advantage. The role may still be attractive for reasons the listing does not spell out.
Trade-offs to weigh
- The salary benchmark is still shallow: Pay is disclosed, but the current comparison pool is too small for a strong relative-pay conclusion.
- Location rules could change the fit: Geographic eligibility is restricted to a country or region.
Questions worth asking before you invest more time
- Confirm whether a degree is actually required, preferred, or replaceable with equivalent experience.
- Confirm the actual minimum experience requirement rather than assuming preferred background is mandatory.
- Ask whether visa sponsorship is available before investing significant time in the application.
These questions come from details the listing leaves open. An unanswered point is not treated as a disadvantage.
Salary transparency context
Is pay disclosure typical for this kind of role?
This listing states usable structured compensation, but the current role sample is still too small for a reliable disclosure-rate comparison.
Compensation counts only when amount, ISO currency and supported pay period are all known.
At least ten current comparable roles are required before HPJ publishes a disclosure percentage.
Employer-level comparison is withheld until enough current employer listings are available.
This compares salary-disclosure behavior in current visible listings. It does not compare raw salary amounts across currencies, infer undisclosed pay as zero, or rate employer quality.
Private offer & negotiation lab
Turn an offer into evidence, not guesswork
Enter an annual base offer and, if you want, your own target. HPJ compares only within one explicit currency and never chooses a target for you.
Negotiation evidence available: advertised pay range, strong decision evidence.
Enter an annual base offer to compare it with explicit same-currency evidence. HPJ will not suggest a target for you.
Review the full package · 10 terms
Mark what is confirmed, what needs clarification and what you want to prioritize. These choices and notes stay in this browser.
Usable advertised compensation is available.
Variable compensation is mentioned; verify amount, formula, target and eligibility.
Equity or long-term incentive language is mentioned; verify grant type, vesting and valuation basis.
Retirement or pension benefits are mentioned; verify employer contribution and vesting.
Health-benefit language is mentioned; verify coverage, dependants and employee cost.
Paid-leave language is mentioned; verify the exact entitlement and carry-over rules.
A work-arrangement signal is available; verify schedule details before relying on it.
Relocation support not established
Sponsorship not established
A review cycle is mentioned; verify timing and whether compensation can change at that review.
Questions worth taking into the offer conversation
- Is there a bonus, commission or other variable-pay component, and how is it calculated?
- What retirement or pension contribution does the employer provide?
- What health coverage is included and what costs remain with the employee?
- If relocation is relevant, what expenses, timing and repayment conditions are covered?
- What exact sponsorship or work-authorization conditions apply to this role?
- When is the first performance and compensation review after joining?
- Is there a firm application deadline, a rolling review window or no stated closing date?
Skill bridge
What does this role connect to?
The listing contains useful skill signals, while the current occupation sample is still too thin for a broader comparison.
Skills named in this listing
Shared with the current career sample
The occupation sample is still too thin for a reliable shared-skill comparison.
Application edge
- If these skills match your background, prepare one concrete example that shows how you used Node.js, PostgreSQL, and React rather than relying on a keyword-only claim.
Skill signals come from explicit text mentions. A mention is not automatically a requirement, and absence from the current top-skill list does not make a skill rare or unimportant.
Application Decision Lab
Turn the listing into a preparation plan
Separate what the listing actually states from what you still need to prepare or verify. Your selections and short notes stay in this browser and are never submitted to High Paid Job.
Node.js
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
PostgreSQL
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
React
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
Redis
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
TypeScript
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
Questions worth resolving before you rely on the opportunity
- Application closing time: Is there a firm application deadline, a rolling review window or no stated closing date?
- Work authorization / sponsorship: If sponsorship or work authorization matters to you, what exact immigration or employer-sponsorship conditions apply to this role?
- Application process: What interview, assessment, portfolio, reference or screening stages are part of the hiring process?
Decision analysis
What the listing really tells you
The headline alone does not tell the whole story for Engineering Manager - EU at Ashby. The clearest decision context comes from pay is visible, but the benchmark is still thin, work-location flexibility has usable detail, and the visible application effort can be estimated.
Pay is visible, but the benchmark is still thin
The EUR range can be compared directly within its currency, although the present comparison sample is too shallow for a confident relative-pay ranking.
Work-location flexibility has usable detail
Location flexibility can be assessed here: Remote with some uncertainty or restrictions, with a Remote Freedom reading of 62/100. One practical limit to notice is geographic eligibility is restricted to a country or region..
The visible application effort can be estimated
Provider-mediated application path. The external application may contain additional steps that are not visible from the listing itself.
Source continuity adds useful context
The opportunity currently has 1 renewable source path across 1 source classes. Multiple independent paths can strengthen continuity, but they are not a substitute for checking the application destination.
How this analysis is assembled
Built from the pay, location, qualification, mobility, application and source details available for this vacancy. Anything the listing leaves unresolved stays unresolved.
Analysis evidence coverage
How much analysis can the current evidence support?
This title does not yet fit a reliable comparison family, so a pay percentile is not shown.
Measures observable location flexibility and explicit restrictions; it does not determine whether remote work is personally desirable.
The salary is source-provided and normalizable, but the advertised range is broad enough to reduce comparison precision.
The listing was posted about 2 days ago.
At least one enabled source recently observed the vacancy. The source chain is traceable, but this is not independent employer verification.
There is no universal opportunity score because pay, flexibility and access matter differently to different people. Compare Jobs lets you weight the evidence around your own priorities.
Decision checklist
What is supported, uncertain or worth checking?
This checklist separates supported strengths, visible cautions and missing evidence. It is not an overall recommendation or guarantee that the job is suitable for you.
Supported strengths
No standout strength is supported strongly enough to list here. That is not a negative rating.
Visible cautions
- Geographic eligibility is restricted to a country or region.
- This is remote work with a geographic restriction, not a worldwide-remote vacancy.
Still unknown
- There is not enough comparable salary evidence to establish this job’s current pay position.
- Visa sponsorship is not established by the available listing data.
Pay vs. barriers
Opportunity Efficiency not assessed
The current pay position is not reliable enough to weigh compensation against the stated barriers.
1 explicit Remote Freedom restriction signal is present and is shown separately from qualification requirements.
- Current comparable pay position is unavailable.
- Education requirement is not established.
- Required prior-experience level is not established.
This section weighs pay context against clearly stated barriers without collapsing unlike requirements into one universal score. Degree, experience, licensing, clearance and location limits remain separate, and missing qualification details stay unknown.
Beyond the headline
Not enough evidence for a hidden-value finding
Potential hidden value appears only when several distinct non-pay advantages are actually supported. Missing requirements or benefits are never counted as positives.
Still check: The current application path is provider-mediated rather than directly classified as an employer-authorized or official route.
Hidden Value is an experimental evidence summary, not an investment-style score or guarantee of employability. It only uses explicit current listing evidence and does not infer that an unmentioned qualification is unnecessary.
Compensation intelligence
How competitive is this pay?
This title does not yet fit a reliable comparison family, so a pay percentile is not shown.
Why this analysis?
- This title does not yet fit a reliable comparison family, so a pay percentile is not shown.
- Salary confidence: Medium. The salary is source-provided and normalizable, but the advertised range is broad enough to reduce comparison precision.
- Range quality: Broad but usable range.
Employer compensation communication
Pay transparency at Ashby
Very strong current pay transparency
This score uses the employer’s current visible listings and combines how often pay is disclosed with how useful those ranges are. Bonus, equity and benefit mentions are shown separately and do not raise the score.
This pattern comes from the employer’s current visible vacancies. It describes hiring and pay transparency in those listings, not employee satisfaction or a permanent judgement of the employer.
Current employer intelligence
Ashby — current opportunity snapshot
Employer Evidence Profile
How often this employer’s current visible sampled vacancies state decision-critical information. These percentages describe evidence coverage, not employer quality.
Current sampled listings with advertised compensation evidence.
Current sampled listings whose work arrangement is clearer than unknown.
Current sampled listings with a supported country signal.
Current sampled listings with an explicit closing time.
Current sampled listings with a usable posting date.
Current sampled listings that explicitly indicate confirmed, possible or unavailable sponsorship evidence.
Current sampled listings with an explicit relocation signal.
Low coverage means the current visible listings state the information less often. It does not prove that the employer lacks the policy, benefit or support.
Common current occupation families: Customer success (17) · Sales (12) · Software engineering (9)
Visible seniority mix: Senior / lead (22) · Leadership (46)
Current employment-type mix: Full time (85)
Most visible hiring countries in this sample: United States (44) · United Kingdom (8) · Canada (4) · South Korea (3)
Other current roles from this employer
Mid-Market Customer Success Manager - EMEA (German speaking)
Europe
Seniority not clearly specified · Region-restricted remoteSenior Product Designer
USA
Senior / lead · Region-restricted remoteMid Market Account Executive - EMEA (French Speaking)
Europe
Leadership · Region-restricted remoteGTM Systems Analyst
Canada, Europe, USA
Seniority not clearly specified · Region-restricted remoteThese are other current vacancies visible from the same employer, not endorsements or evidence of future hiring plans.
Current disclosed salary medians by currency
- USD 195,000 median · 45 disclosed salaries
- EUR 132,500 median · 17 disclosed salaries
- GBP 136,000 median · 12 disclosed salaries
Questions worth asking this employer
- If work authorization matters to you, what sponsorship policy applies to this specific role and location?
- If a move is required, is relocation assistance available for this position?
- What is the expected application and interview timeline if the listing does not state a closing date?
These questions are prompted by missing or thin evidence in the employer’s current visible vacancies. Missing evidence is not treated as a negative judgement.
This employer snapshot uses the employer’s current visible listings. Remote and sponsorship rates use only vacancies with explicit evidence, while missing information stays unknown. Salary medians are shown separately by currency and need at least five disclosed salaries. Zero confirmed sponsorship means none was explicitly found in this sample, not that sponsorship is unavailable.
This snapshot describes the employer’s current visible vacancies—things such as pay disclosure and work arrangement. It is not an employee-satisfaction or hiring-quality rating, and different currencies stay separate.
Work-location intelligence
Remote Freedom
Remote with some uncertainty or restrictions
Why this score?
- The role is remote but the source identifies a country or regional restriction.
Location restrictions detected
- Geographic eligibility is restricted to a country or region.
Remote Freedom measures observable location flexibility only. Unknown work-location information remains unscored. Timezone wording is penalized only when it appears restrictive; general collaboration across time zones is not treated as a restriction. A score does not guarantee legal work eligibility, payroll availability or visa sponsorship.
International applicant intelligence
Visa & relocation signals
Sponsorship status is shown only when the listing provides clear enough wording. Employer history or headquarters location is not used to guess an answer.
The available listing details do not contain a clear enough sponsorship statement.
The available listing details do not contain a clear enough relocation statement.
Tradeoff check
What’s the catch?
These are visible conditions worth checking before treating the headline compensation as the whole story:
- This is remote work with a geographic restriction, not a worldwide-remote vacancy.
Application-path intelligence
What can we see about the application process?
Provider-mediated application path
The current application path comes through a publisher or aggregator. The destination may still lead to an employer-authorized hiring system, but that is not clear enough to assume.
Current destination: jobicy.com · HTTPS
No additional required application step is clear in the available listing text. This does not mean the external application is one-click or friction-free.
Application effort is estimated from visible listing and source details. Optional steps are kept separate from mandatory ones, and the external form may contain additional requirements that are not visible here.
Application safety context
Application safety check
Basic application-safety context available
The current application destination has a basic transport-safety signal such as HTTPS. This does not verify the employer, vacancy, recruiter or application process.
Evidence checked: Source provenance · Application destination · Listing wording
Observable transport-safety signals
- The available application destination uses HTTPS.
Before you share money or sensitive information
- Confirm the vacancy on the employer’s official careers site when practical, especially if a recruiter contacts you outside the listed application path.
- Check that recruiter email domains and application destinations are consistent with the employer or an identifiable recruiting provider.
- Do not pay application, processing, training or equipment fees merely to be considered for a job.
- Do not send cryptocurrency, gift cards, online-banking credentials or PINs as part of an application.
- Treat unusually fast offers or interviews conducted only through informal messaging channels as reasons to verify the employer independently.
This is a limited safety screen, not employer verification and not a fraud determination. Never send money, cryptocurrency, passwords or sensitive banking credentials merely because a listing appears on a job platform.
Original listing details
The section below comes from the listing source. The decision sections above use the job’s structured pay, location, qualification, mobility and application details to give you additional context.
Hi 👋 I’m Colin, 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.
To 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.
When 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).
To 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.
We’ve already gathered an experienced, talented, and collaborative team of 25+ engineers. You’ll help me manage the growing team of engineers in Europe.
In addition to working with engineers you’ll also get to work on projects yourselves. Some examples of work our engineering leaders have done:
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.
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.
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).
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.
Why be a manager?
I 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.
Since 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.
Despite 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.
I’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.
It 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...”
Why You Should or Shouldn’t Apply
Engineering 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:
You love being technical and can hold in-depth conversations with direct reports from infra to backend to frontend.
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
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.
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.
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.
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.
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.
Put another way, you shouldn’t apply if:
You don’t enjoy coding or don’t find time to stay up-to-date on technology.
You’ve gotten into management because it was the only growth path available
You want to make all the product decisions instead of empowering your team to make those calls.
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.
A staff or principal engineer to you is someone who spends most of their time project managing or doing architecture reviews.
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.
What We’re Building
Talent teams aspire to build a hiring process that identifies great candidates, moves them quickly through the interview process, and provides an excellent experience for the candidate. To accomplish this, recruiters perform thousands of daily tasks to coordinate and relay information between candidates, interviewers, and hiring managers. Teams struggle to keep up!
Scheduling a final round is an excellent example of our customers' challenges. A recruiter needs to collect availability from the candidate, identify potential interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and perform any last-minute adjustments as availability changes. They must perform this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵
Ashby provides talent teams with 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 put a lot of effort into designing products that are approachable to beginners but mastered and extended by power users. In many ways, spreadsheets set the bar here.
We have many customers, great revenue growth, years of runway, and amazing investors like YCombinator, Elad Gil, and Lachy Groom. I’ll share more once we meet.
Engineering Culture
Our engineering culture is motivated by Abhik and Benji’s (our co-founders) belief that a small talented team, given the right environment, can build high-quality software fast (and work regular hours!).
Collaboration is Natural, Communication is Deliberate
Our engineering team (and the team at large) consists of lifelong learners who are humble and kind (meet them here!). These attributes create an environment where collaboration happens naturally (we filter for it in interviews). 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 can focus 36h out of a 40h work week (Abhik wrote about it here). Even managers can rely on getting consistent time (and support to make, if necessary) to focus and do creative work without the demand of constant meetings.
Increase Leverage, not Team Size
We 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:
Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 5x a day. Everyone on the team has contributed to developer experience 💪🏾
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) which we are constantly improving. Each improvement to a common component cascades throughout our app (short video on it here).
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.
Here’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby:
And a demo of one of these building blocks:
Give Engineers Ownership & Autonomy
We, as engineers, find clever ways to solve problems, which amplifies when we deeply understand the problem. All of us in technical leadership did our best work as engineers when we had a deep understanding of the end-user and the business and ownership over the solution. Our engineering culture reflects this experience: engineers own projects end-to-end, from speaking with users to writing product specs to UX design. These are skills that we often don’t get to practice as engineers, and, as a manager at Ashby, you’ll provide mentorship and feedback to engineers to ensure they are successful when delivering projects.
Put Effort into Diversity
Diverse teams drive innovation and better outcomes. As the father of two young girls, I want to see them grow up in a world where all industries are open and welcoming to everyone, regardless of race, gender, or preferences. Helping to build a more diverse team at Ashby is my way of contributing to this change.
Today, 26% of engineers at Ashby are from underrepresented groups. It’s not great, and we are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more.
Interview Process
At 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:
Intro Call (30m) - Discuss your application questions, align on the responsibilities of the role, and answer questions about Ashby.
Past Experience Deep Dive (1h) - Discuss your past experience as an engineering leader.
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.
Coffee Chat with VP of Engineering (1h) - Spend time with our VP of Engineering and get to know each other.
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.
I will be your main point of contact and prepare you for interviews. If we don’t give an offer, we’ll provide feedback!
Technology Stack
I’m sharing our tech stack with the caveat that we don’t require previous experience: TypeScript (frontend & backend), Node.js, React, Apollo GraphQL, Postgres, Redis.
Benefits
Competitive salary and equity.
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.
Unlimited PTO, and we will encourage you to take it.
Generous equipment, software, and office furniture budget. Get what you need to be happy and productive!
$100/month education budget with more expensive items (like conferences) covered with manager approval.
Ashby’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.
Ashby 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.
Ashby 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.
Listing provenance
Where did this job come from?
See where this vacancy came from and whether more than one current source can still support it. Source names help with traceability and attribution; they are not endorsements or guarantees.
At least one enabled source recently observed the vacancy. The source chain is traceable, but this is not independent employer verification.
- Continuity
- One recent renewable source
- Source-class independence
- One renewable source class
- Last source observation
- Observed in the past 3 days
This records when High Paid Job last observed the vacancy in source evidence. It confirms source presence, not that the employer edited the vacancy at that time.
- 1 enabled source recently observed this vacancy.
Source confidence is about traceability and continuity. It is separate from application safety and should not be read as an employer reputation rating.
The vacancy is supplied by an external job publisher. Source information helps show where the listing came from; it is not a guarantee about the employer or vacancy.
Listing source: Jobicy. Destination: jobicy.com. The application opens in a new tab so you can keep this report open.
