工作
工作
探索 418 工作 · Software Engineering
- USD 190,000–235,000 yearly加拿大Software Engineering
Staff Software Engineer
Juniper Square
📍 Remote · Canada, USA
全職
職缺詳情
About Juniper Square
Private markets are one of the largest, most complex, and most underserved corners of global finance. Our mission at Juniper Square is to unlock their full potential. We’re the Operations Partner trusted by 2,300+ GPs, unifying technology, data, and fund administration services into a single platform that helps GPs move faster, make better decisions, and scale with precision. With $300B+ under administration and 700,000+ LPs on platform, we’ve built the scale to match our ambition. And with JunieAI, our purpose-built AI platform, we’re reimagining how private markets operate, embedding intelligence across every workflow. Founder-led since 2014, backed by $350M+ in funding, and now 1,000+ employees strong, we’re building a company designed to shape the future of private markets for decades to come.
Our culture is built for people who want to do ambitious, meaningful work alongside exceptionally talented teammates. We think like owners, move with urgency, and take pride in solving hard problems that truly matter to our customers and the future of private markets. We believe the best ideas come from open debate, deep collaboration, and diverse perspectives, which is why we believe transparency is the default and feedback makes us stronger. If you’re energized by high standards, rapid growth, and the opportunity to help define a category at a pivotal moment, come join us!
Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time.
About your role
As a Staff Software Engineer at Juniper Square, you are a technical leader - setting technical direction, driving architectural decisions, and raising engineering quality across your team. This is a player-coach role: you lead through code and architecture, not just direction. You'll write production code as a hands-on individual contributor while owning your team's technical strategy, roadmap, and growth, and you'll collaborate closely with product, design, and QA to turn complex workflows into delightful, intuitive experiences.
We're hiring a Staff Software Engineer for the following team:
Treasury: Join the team building Juniper Square's Treasury platform, the system that brings transactions, balances, and bank data into and across the platform. You'll work on expanding bank integrations, a visualization and reporting layer for payments and treasury data, and vendor exports that connect treasury data to accounting, on a team that has already processed $500M+ in transactions.
What you'll do
Own Technical Direction & Architecture
Set the technical direction and own the architecture for your domain's systems, from design through production
Lead technical design for ambiguous, cross-functional initiatives - evaluating tradeoffs, aligning stakeholders, and driving implementation
Be instrumental in your team's transition from monolith to service-oriented architecture
Evaluate and select technologies with a bias toward what ships well and scales sustainably
Build & Deliver
Write production code as a hands-on individual contributor - this is not a role that delegates implementation to others
Own end-to-end delivery of roadmap projects: design, coding, testing, and production
Manage your team's short-term roadmap (spanning the next two quarters), proactively surfacing execution, cost, and technical risks and driving pragmatic mitigation
Lead the development of complex, full-stack workflows, working across frontend and backend engineers
AI Fluency & AI-Native SDLC
Practice AI Fluency across the full software development lifecycle - deliberately choosing where AI versus traditional software is the right tool, and defending those tradeoffs against real criteria (latency, accuracy, cost, data sensitivity, explainability)
Champion and embed AI-native development practices and tools (e.g., Cursor, Augment) to drive significant productivity gains across your team
Adapt code review and testing practices for an AI-assisted SDLC - catching AI-specific failure modes (hallucinated dependencies, overconfident but incorrect logic) before they ship
Build and evaluate agentic workflows and AI-assisted systems where they add real value, with clear human-in-the-loop boundaries and monitoring for failure
Guard against over-reliance on AI tooling, in your own work and in the code you review, balancing velocity with system comprehension and accountability for outcomes
Foster a culture of rapid iteration, high velocity, and quality, and help raise AI fluency across the team
Lead & Grow the Team
Mentor engineers, raise the quality of technical decision-making, and help the team execute with consistency
Establish coding standards, review practices, and architectural documentation that scale as the team grows
Partner with recruiting to build and grow the team
Collaborate Cross-Functionally
Work closely with product, design, QA, and customer support to translate requirements into executable technical plans
Participate actively in design reviews and roadmap discussions with a grounded, implementation-level perspective
Handle most cross-team conflicts and technical decisions autonomously
Operational Excellence
Own monitoring, diagnosing, and resolving production issues within your team's services
Use observability tooling to measure and improve system performance and reliability
Implement and uphold best practices that maximize developer productivity across the team
Domain Expertise
Grow into a subject-matter expert in your domain, with an in-depth understanding of customer needs and the value your systems deliver
Qualifications
Required
12+ years of experience in backend and/or full-stack software engineering, with a clear trajectory of increasing technical leadership, architectural responsibility, and mentorship
A portfolio of shipped production systems - be ready to walk through specific technical decisions you personally made and code you personally wrote; this is not a role for someone whose primary contribution has been directing others
Deep expertise in at least one server-side language (Python preferred, Node/TS, Java, C++, C#, or similar) and strong proficiency building production-grade backend services
Experience with modern front-end frameworks (React preferred) and comfort working full-stack when the problem calls for it
Experience with relational/NoSQL databases, including schema design, performance tuning, and data modeling
Experience building and operating cloud-native systems using AWS (or equivalent), Docker, Kubernetes, and infrastructure as code
Strong understanding of CI/CD, observability, reliability, and operational excellence in production environments
Deep understanding of service-oriented architecture and experience evolving systems from monolith toward SOA
Demonstrated ability to raise engineering quality through technical standards, design reviews, mentoring, and reusable platform patterns
Hands-on experience with AI-native development tools (e.g., Cursor, Augment) and a track record of using them to accelerate personal and team velocity
Demonstrated AI Fluency: hands-on experience building AI-assisted or agentic systems with a deliberate, defensible point of view on when AI is (and isn't) the right tool; adapted code review practices to catch AI-specific failure modes; and concrete safeguards against over-reliance on AI tooling
Ability to work through ambiguity, break down complex problems, and drive alignment across engineering, product, and design
Bachelor's degree in Computer Science or equivalent work experience
Nice to Have
Reporting: experience with data integration platforms, ETL/ELT processes, business intelligence tools, or financial data
Production experience building AI/LLM-powered systems (RAG pipelines, agentic workflows, evaluation frameworks)
Background in financial document processing or fintech data pipelines
Prior experience in a technical lead or TLM capacity on a new or early-stage product team
At Juniper Square, we believe building a diverse workforce and an inclusive culture makes us a better company. If you think this role sounds like a fit, we encourage you to apply even if you don't meet every qualification.
Compensation
Compensation for this position includes a base salary, equity, and a variety of benefits. The U.S. base salary range for this role is $190,000 – $235,000 USD and the Canadian base salary range is $180,000 - $225,000 CAD. Actual base salaries will be based on candidate-specific factors, including experience, skillset, and location, and local minimum pay requirements as applicable.
Benefits include:
• Health, dental, and vision care for you and your family
• Life insurance
• Mental wellness coverage
• Fertility and growing family support
• Flex Time Off in addition to company-paid holidays
• Paid family leave, medical leave, and bereavement leave policies
• Retirement saving plans
• Allowance to customize your work and technology setup at home
• Annual professional development stipend
Your recruiter can provide additional details about compensation and benefits.來源: Jobicy — Canada查看職缺/前往原網站應徵 ↗
已發布: - 英國Software Engineering
Senior System Engineer (CloudGate)
Nebius
📍 Remote · Europe
全職
職缺詳情
About Nebius:
Nebius is leading a new era in cloud infrastructure for the global AI economy. We are building a full-stack AI cloud platform that supports developers and enterprises from data and model training through to production deployment, without the cost and complexity of building large in-house AI/ML infrastructure.
Built by engineers, for engineers. From large-scale GPU orchestration to inference optimization, we own the hard problems across compute, storage, networking and applied AI.
Listed on Nasdaq (NBIS) and headquartered in Amsterdam, we have a global footprint with R&D hubs across Europe, the UK, North America and Israel. Our team of 1,500+ includes hundreds of engineers with deep expertise across hardware, software and AI R&D.
The role
Our CloudGate team is responsible for the software side of external network connectivity in our Cloud. We're building a traffic delivery system for a variety of scenarios: IPv4 connectivity, Cloud Interconnect, Egress NAT, and a network load balancer. They serve tens of millions of packets per second.
We have a control plane microservice architecture with gRPC transport and our own Database as our data warehouse.
What we do:
Increase service scalability
Developing service functionality with support for service endpoints and expansion of health check types
Improve the internal architecture, optimizing interaction with related services
In this position, your responsibility will be to:
Developing a data plane for Nebius Cloud network services
Improve service performance and reliability
Automate complex cross-service interaction scenarios
Perform load testing for services
We expect you to have:
Capable of writing reliable, high-performance code
Proficient in C and ready to learn Go/C++
Familiar with routing network traffic
It would be an added bonus if you had:
Worked with VPP, DPDK, and the Linux kernel network subsystem
Well-versed in virtual networks and overlays, SDN, NFV, DPI, network protocols, routing and tunneling, BGP, and MPL
We conduct coding interviews as part of the process.
#LI-JS1
Benefits & Perks:
Competitive compensation
Career growth and learning opportunities
Flexibility and ownership
Collaborative and innovative culture
Opportunity to work on impactful AI projects
International environment and talented teams
What's it like to work at Nebius:
Fast moving - Bold thinking - Constant growth - Meaningful impact - Trust and real ownership - Opportunity to shape the future of AI
Equal Opportunity Statement:
Nebius is an equal opportunity employer. We are committed to fostering an inclusive and diverse workplace and to providing equal employment opportunities in all aspects of employment. We do not discriminate on the basis of race, color, religion, sex (including pregnancy), national origin, ancestry, age, disability, genetic information, marital status, veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by applicable law.
Applicants must be authorized to work in the country in which they apply and will be required to provide proof of employment eligibility as a condition of hire.
If you need accommodations during the application process, please let us know.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: - 英國Software Engineering
Full-Stack Engineer (Frontend Leaning) - Studio
Elevenlabs
📍 Remote · Bulgaria, Poland, UK, USA
全職
職缺詳情
About ElevenLabs
ElevenLabs is an AI research and product company transforming how we interact with technology.
We launched in January 2023 with the first human-like AI voice model. Today, we serve millions of users and thousands of businesses - from fast-growing startups to large enterprises like Deutsche Telekom and Meta. Our investors are some of the world's most prominent, including Andreessen Horowitz, ICONIQ Growth and Sequoia. We've raised $781M in funding and our last valuation was $22B - multiples of 11, always.
We have expanded from voice into three main platforms:
ElevenAgents enables businesses to deliver seamless and intelligent customer experiences, with the integrations, testing, monitoring, and reliability necessary to deploy voice and chat agents at scale.
ElevenCreative empowers creators and marketers to generate and edit speech, music, image, and video across 70+ languages.
ElevenAPI gives developers access to our leading AI audio foundational models.
Everything we do is the result of the creativity and commitment of our team - builders doing the best work of their lives. We are researchers, engineers, and operators. IOI medalists and ex-founders. If you want to work hard and create lasting positive impact, we want to hear from you.
How we work
High-velocity: Rapid experimentation, lean autonomous teams, and minimal bureaucracy.
Impact not job titles: We don’t have job titles. Instead, it’s about the impact you have. No task is above or beneath you.
AI first: We use AI to move faster with higher-quality results. We do this across the whole company—from engineering to growth to operations.
Excellence everywhere: Everything we do should match the quality of our AI models.
Global team: We prioritize your talent, not your location.
What we offer
Innovative culture: You’ll be part of a generational opportunity to define the trajectory of AI, surrounded by a team pushing the boundaries of what’s possible.
Growth paths: Joining ElevenLabs means joining a dynamic team with countless opportunities to drive impact - beyond your immediate role and responsibilities.
Learning & development: ElevenLabs proactively supports professional development through an annual discretionary stipend.
Social travel: We also provide an annual discretionary stipend to meet up with colleagues each year, however you choose.
Annual company offsite: Each year, we bring the entire team together in a new location - past offsites have included Croatia and Italy.
Co-working: If you’re not located near one of our main hubs, we offer a monthly co-working stipend.
About the roleYou’ll build the tools that make Studio a video editor people want to live in. These include transitions, color grading and elements libraries all built on top of our in-house engine. You’ll also build presets, so a user can get the effect they want without tweaking 20 individual controls.The work mixes greenfield features with polish on the existing editor. An example of the polish is letting editors coming from Premiere Pro or Final Cut Pro rebind their keyboard shortcuts in one step. You’ll write proposals, get fast feedback, and own features through launch, including the marketing moment.You’re a product-minded, frontend-leaning full-stack engineer. Deep backend skills aren’t required.
Requirements
Strong frontend engineer who has built complex, interactive UIs.
Enough full-stack ability to work across the stack, but deep backend expertise isn’t needed.
Evidence of product responsibility: side projects, open source, or product-facing work.
Thrives in a fast-moving, startup-style environment, and takes ownership with minimal hand-holding.
We are an equal opportunity employer and do not discriminate on the basis of race, religion, national origin, gender, sexual orientation, age, veteran status, disability or other legally protected statuses.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: - 英國Software Engineering
Senior Software Engineer (YDB Team)
Nebius
📍 Remote · Europe
全職
職缺詳情
About Nebius:
Nebius is leading a new era in cloud infrastructure for the global AI economy. We are building a full-stack AI cloud platform that supports developers and enterprises from data and model training through to production deployment, without the cost and complexity of building large in-house AI/ML infrastructure.
Built by engineers, for engineers. From large-scale GPU orchestration to inference optimization, we own the hard problems across compute, storage, networking and applied AI.
Listed on Nasdaq (NBIS) and headquartered in Amsterdam, we have a global footprint with R&D hubs across Europe, the UK, North America and Israel. Our team of 1,500+ includes hundreds of engineers with deep expertise across hardware, software and AI R&D.
The role
The YDB Development Team at Nebius is hiring mid- and senior-level software developers with C++ expertise.
YDB is an open-source platform with two roles within Nebius:
Providing the binary object storage foundation for S3 Object Storage, Shared Filesystems and Network Block Storage
Serving as a distributed relational database and message broker for services such as IAM, billing, audit trails and logging
We operate YDB clusters in more than 10 regions using HDD and NVMe storage. Individual clusters span tens of thousands of nodes, manage hundreds of petabytes of data and deliver terabytes per second of throughput. Our infrastructure includes x86 and Arm-based systems, including NVIDIA GB300 nodes.
What you’ll work on
Evolve YDB’s architecture for new hardware, redesigning core components when incremental optimization is insufficient:
QLC NVMe drives: increase storage density while controlling RAM/CPU consumption and write amplification
Dual 800 Gb/s network adapters: reduce CPU overhead and memory bandwidth consumption to utilize the available NIC bandwidth
NVIDIA GB300-based systems: ensure efficient operation on Arm-based hosts and offload storage and networking processing to BlueField DPUs
Support high-capacity SMR HDDs by designing data placement, sequential writes, garbage collection and recovery around zoned-write constraints
Develop wide erasure-coding schemes to reduce space aplimfication while maintaining durability and availability
Reduce recovery and rebalancing times after device outages while limiting the impact on foreground workloads
Prevent, detect and recover from silent data corruption across memory, networking and storage
Provide the system capabilities and interfaces required by fleet-wide automation so that hundreds of production clusters can be deployed, configured, upgraded, diagnosed and operated consistently
We move quickly and focus on delivering practical value. Features and optimizations merged into the production branch are typically deployed within weeks. You’ll see your work solving real problems in live clusters—not waiting years to make an impact.
Requirements:
5+ years of professional experience developing high-load systems in C or C++. Candidates with 3+ years will also be considered if their experience includes relevant work on distributed storage systems
Experience developing high-performance, low-latency software components
Understanding of core dumps, flame graphs and sanitizer-enabled builds
Understanding of CPU caches, atomic operations and NUMA architectures
Nice to have:
Experience designing and developing production-grade distributed storage systems and/or databases
Experience with on-disk data structures such as LSM trees and B+ trees, and storage algorithms such as erasure coding and checksumming
Understanding of NVMe, conventional HDD and SMR HDD internals
Experience with debugging and profiling tools such as perf, VTune, bpftrace and gdb
Familiarity with the Linux kernel, SPDK/DPDK, libaio and io_uring
Knowledge of IP, TCP, UDP and DNS, and ideally InfiniBand or RoCE/RDMA
Experience with Kubernetes and Grafana
Experience responding to production incidents
Knowledge of availability and durability calculations
For Senior candidates, we offer hybrid working or the flexibility to work remotely within EU.
Benefits & Perks:
Competitive compensation
Career growth and learning opportunities
Flexibility and ownership
Collaborative and innovative culture
Opportunity to work on impactful AI projects
International environment and talented teams
What's it like to work at Nebius:
Fast moving - Bold thinking - Constant growth - Meaningful impact - Trust and real ownership - Opportunity to shape the future of AI
Equal Opportunity Statement:
Nebius is an equal opportunity employer. We are committed to fostering an inclusive and diverse workplace and to providing equal employment opportunities in all aspects of employment. We do not discriminate on the basis of race, color, religion, sex (including pregnancy), national origin, ancestry, age, disability, genetic information, marital status, veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by applicable law.
Applicants must be authorized to work in the country in which they apply and will be required to provide proof of employment eligibility as a condition of hire.
If you need accommodations during the application process, please let us know.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: - 英國Software Engineering
Senior Software Engineer (Agentic Search) – Web Rendering (Chromium)
Nebius
📍 Remote · Europe, Israel
全職
職缺詳情
About Nebius:
Nebius is leading a new era in cloud infrastructure for the global AI economy. We are building a full-stack AI cloud platform that supports developers and enterprises from data and model training through to production deployment, without the cost and complexity of building large in-house AI/ML infrastructure.
Built by engineers, for engineers. From large-scale GPU orchestration to inference optimization, we own the hard problems across compute, storage, networking and applied AI.
Listed on Nasdaq (NBIS) and headquartered in Amsterdam, we have a global footprint with R&D hubs across Europe, the UK, North America and Israel. Our team of 1,500+ includes hundreds of engineers with deep expertise across hardware, software and AI R&D.
The Product
In a rapidly evolving world, trust in AI depends on AI agents being grounded in fresh, verified real-world data. Search is the foundation that makes this possible. We are building an agent-native search platform designed specifically for AI systems rather than human users. Our product provides programmatic, low-latency, and observable search APIs that AI agents use to retrieve, filter, and reason over real-world information at scale.
The Role
We are looking for a Senior Software Engineer to work on the rendering infrastructure of a novel search engine tailored for agentic AI consumption.
In this role, you will focus on loading modern web pages in a browser that we patch and build ourselves, so that content is rendered completely and reliably at a cost that works across billions of pages. You will work inside Chromium to remove what we do not need, make the rest faster and cheaper, and keep our build current as Chromium moves. Your work ensures that high-quality content is consistently available to the indexing and retrieval systems downstream.
In this position, your responsibility will be to
Change Chromium in its heavy core (Blink, the V8 integration, the compositor, the network service) to cut CPU, memory and startup cost per page
Strip Chromium down for agent workloads: skip what nobody needs, such as image and media decoding, web font downloads, and rasterization and GPU work where no one needs pixels, while keeping what page scripts depend on to run correctly (style, layout, animation frames, observers), and work out what breaks, or renders differently, when you do
Keep the browser compatible with the web: make sure that what we remove does not change how the sites we load behave or render
Profile and tune fleets of browsers: the process model, memory per renderer, startup, isolation and crash handling
Build the production system around it: how browsers are launched, pooled, recycled and monitored
You may be a good fit if you
Have 5+ years of experience building production systems, and are an expert in several of the following areas.
Inside the browser
Strong C++ in a large, performance-critical codebase, ideally Chromium, Blink or V8, or a comparable browser engine (Rust is a plus)
Chromium architecture: the process model, Mojo IPC, the rendering pipeline (DOM, style, layout, paint, compositing), and the network service
Building, debugging and shipping custom Chromium builds: the build system, tracing, crash analysis, and maintaining patches across releases
Performance and systems
Profiling CPU, memory and I/O for browser fleets, with tools such as perf, tracing and flame graphs
Linux process isolation and resource management, concurrency, and memory management
Have run browsers in production, or built the infrastructure that does, and can describe where the time and memory went
Strong candidates may also have experience with
Contributions to Chromium, Blink, V8, Firefox, WebKit or another browser engine
Building or maintaining a patched browser that you wrote the patches for
Browser instrumentation, including the Chrome DevTools Protocol
Working familiarity with how modern frontend frameworks render (SSR, CSR, streaming, hydration)
Distributed systems, Kubernetes, and Go or Python
The kind of problems you will work on
Cut the cost of loading a page in half. Where do CPU and memory go, and what would you change in the browser?
Turn off the GPU and image decoding for agent workloads. What breaks, and what changes in how pages load and render?
A page runs a script that never yields. How do we detect and stop it without help from the page?
Chromium ships a new version. How do we bring a large set of patches forward in days, not weeks?
Decide when a page is finished, for pages with analytics beacons, long polling and endless scrolling.
We conduct coding interviews as part of the process.
Benefits & Perks:
Competitive compensation
Career growth and learning opportunities
Flexibility and ownership
Collaborative and innovative culture
Opportunity to work on impactful AI projects
International environment and talented teams
What's it like to work at Nebius:
Fast moving - Bold thinking - Constant growth - Meaningful impact - Trust and real ownership - Opportunity to shape the future of AI
Equal Opportunity Statement:
Nebius is an equal opportunity employer. We are committed to fostering an inclusive and diverse workplace and to providing equal employment opportunities in all aspects of employment. We do not discriminate on the basis of race, color, religion, sex (including pregnancy), national origin, ancestry, age, disability, genetic information, marital status, veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by applicable law.
Applicants must be authorized to work in the country in which they apply and will be required to provide proof of employment eligibility as a condition of hire.
If you need accommodations during the application process, please let us know.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: - GBP 123,000–149,000 yearly英國Software Engineering
Senior Software Engineer, Product Engineering - UK
Ashby
📍 Remote · UK
全職
職缺詳情
Hi I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for an ambitious full-stack engineer who is laser-focused on solving customer problems and making the right long-term investments to solve them not only today but in our future features and products.
What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature.
We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet.
You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner).
About the Role and How We Work
Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software.
I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings.
I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation.
Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning. In those companies, I felt like a JIRA jockey.
At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have:
Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem I talk about in "What We're Building."
Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it.
Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features.
What We’re Building
As 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 software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.
Scheduling 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.
As 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!
Why You Should or Shouldn’t Apply
Software engineers come in many flavors, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for:
You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team).
You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems.
You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team.
You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it).
You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here!
You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc.
Put another way, you shouldn’t apply if:
You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges.
You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs.
You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront.
You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them.
You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited.
To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off.
Engineering Culture
Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:
Minimal process with ownership over decisions normally made by product and design
Natural collaboration and deliberate communication
Investing in tools and abstractions that give us leverage
Putting effort into building a diverse team
Minimal Process & Lots of Ownership
The 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.
Traditional 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.”
At 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.
Collaboration is Natural & Communication is Deliberate
Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). 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).
To 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:
We 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.
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 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our 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) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below).
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:
Put Effort into Diversity
Diverse 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.
Today, 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.
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 via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises.
Our interview process is three rounds:
Introduction call with Hiring Manager (15 to 30m, live)
A technical screen where we pair in our actual codebase (1h, live)
Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days)
Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter.
Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback!
Your First Three Months at Ashby
We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together.
It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture.
Technology Stack
I’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.
When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Adam). 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 .
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.
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.
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.
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.
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.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: - GBP 151,000–184,000 yearly英國Software Engineering
Staff Software Engineer, Product Engineering - UK
Ashby
📍 Remote · UK
全職
職缺詳情
Hi I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for an ambitious full-stack engineer who is laser-focused on solving customer problems and making the right long-term investments to solve them not only today but in our future features and products.
What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature.
We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet.
You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner).
About the Role and How We Work
Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software.
I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings.
I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation.
Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning. In those companies, I felt like a JIRA jockey.
At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have:
Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem I talk about in "What We're Building."
Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it.
Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features.
What We’re Building
As 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 software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.
Scheduling 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.
As 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!
Why You Should or Shouldn’t Apply
Software engineers come in many flavors, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for:
You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team).
You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems.
You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team.
You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it).
You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here!
You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc.
Put another way, you shouldn’t apply if:
You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges.
You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs.
You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront.
You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them.
You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited.
To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off.
Engineering Culture
Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:
Minimal process with ownership over decisions normally made by product and design
Natural collaboration and deliberate communication
Investing in tools and abstractions that give us leverage
Putting effort into building a diverse team
Minimal Process & Lots of Ownership
The 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.
Traditional 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.”
At 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.
Collaboration is Natural & Communication is Deliberate
Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). 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).
Today, 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.
We 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.
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 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our 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) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below).
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:
Put Effort into Diversity
Diverse 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.
Today, 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.
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 via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises.
Our interview process is three rounds:
Introduction call with Hiring Manager (15 to 30m, live)
A technical screen where we pair in our actual codebase (1h, live)
Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days)
Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter.
Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback!
Your First Three Months at Ashby
We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together.
It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture.
Technology Stack
I’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.
When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Adam). 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 .
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.
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.
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.
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.
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.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: - EUR 154,000–188,000 yearly英國Software Engineering
Staff Software Engineer, Product Engineering - EU
Ashby
📍 Remote · Europe
全職
職缺詳情
Hi I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for an ambitious full-stack engineer who is laser-focused on solving customer problems and making the right long-term investments to solve them not only today but in our future features and products.
What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature.
We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet.
You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner).
About the Role and How We Work
Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software.
I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings.
I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation.
Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning. In those companies, I felt like a JIRA jockey.
At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have:
Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem I talk about in "What We're Building."
Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it.
Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features.
What We’re Building
As 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 software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.
Scheduling 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.
As 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!
Why You Should or Shouldn’t Apply
Software engineers come in many flavors, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for:
You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team).
You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems.
You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team.
You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it).
You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here!
You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc.
Put another way, you shouldn’t apply if:
You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges.
You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs.
You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront.
You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them.
You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited.
To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off.
Engineering Culture
Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:
Minimal process with ownership over decisions normally made by product and design
Natural collaboration and deliberate communication
Investing in tools and abstractions that give us leverage
Putting effort into building a diverse team
Minimal Process & Lots of Ownership
The 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.
Traditional 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.”
At 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.
Collaboration is Natural & Communication is Deliberate
Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). 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).
To 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:
We 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.
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 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our 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) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below).
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:
Put Effort into Diversity
Diverse 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.
Today, 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.
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 via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises.
Our interview process is three rounds:
Introduction call with Hiring Manager (15 to 30m, live)
A technical screen where we pair in our actual codebase (1h, live)
Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days)
Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter.
Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback!
Your First Three Months at Ashby
We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together.
It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture.
Technology Stack
I’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.
When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Adam). 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 .
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.
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.
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.
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.
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.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: - EUR 119,000–145,000 yearly英國Software Engineering
Senior Software Engineer, Product Engineering - EU
Ashby
📍 Remote · Europe
全職
職缺詳情
Hi I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for an ambitious full-stack engineer who is laser-focused on solving customer problems and making the right long-term investments to solve them not only today but in our future features and products.
What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature.
We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet.
You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner).
About the Role and How We Work
Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software.
I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings.
I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation.
Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning. In those companies, I felt like a JIRA jockey.
At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have:
Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem I talk about in "What We're Building."
Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it.
Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features.
What We’re Building
As 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 software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.
Scheduling 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.
As 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!
Why You Should or Shouldn’t Apply
Software engineers come in many flavors, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for:
You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team).
You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems.
You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team.
You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it).
You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here!
You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc.
Put another way, you shouldn’t apply if:
You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges.
You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs.
You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront.
You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them.
You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited.
To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off.
Engineering Culture
Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:
Minimal process with ownership over decisions normally made by product and design
Natural collaboration and deliberate communication
Investing in tools and abstractions that give us leverage
Putting effort into building a diverse team
Minimal Process & Lots of Ownership
The 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.
Traditional 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.”
At 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.
Collaboration is Natural & Communication is Deliberate
Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). 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).
To 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:
We 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.
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 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our 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) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below).
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:
Put Effort into Diversity
Diverse 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.
Today, 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.
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 via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises.
Our interview process is three rounds:
Introduction call with Hiring Manager (15 to 30m, live)
A technical screen where we pair in our actual codebase (1h, live)
Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days)
Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter.
Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback!
Your First Three Months at Ashby
We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together.
It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture.
Technology Stack
I’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.
When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Adam). 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 .
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.
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.
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.
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.
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.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: - EUR 122,000–144,000 yearly英國Software Engineering
Senior Full Stack Product Engineer (TypeScript)
Maze
📍 Remote · Canada, Ireland, Netherlands, Portugal, Spain, UK
全職
職缺詳情
About Maze
Maze is the user research platform that helps companies build the right products faster by making user insights available at the speed of product development.
In most companies, research demand far exceeds supply. Time, cost, and lack of access to expertise hold teams back. In today’s AI-powered world, anyone can build a product fast. The real challenge? Deeply understanding user needs and building the right product. That’s where Maze comes in.
We believe companies shouldn’t have to choose between building fast and building right. Maze makes research accessible, intuitive, and fast so product teams can put user insights at the center of every decision.
Our platform enables researchers, designers, and product managers to quickly recruit participants, run studies autonomously, and surface insights that actually drive product decisions. Our AI capabilities automate the busywork and add depth and direction to the insights themselves.
That’s why Maze was recently named the #1 user research platform in UX Tools’ Design Tools Survey—and why we’re scaling fast across industries like B2B SaaS, e-Commerce, Financial Services, Retail, and Automotive, supporting world class customers such as Uber, Amazon, Atlassian, Anthropic & more.
Maze is a Series B company backed by top-tier investors (Felicis, Emergence & Amplify). We operate a global remote workforce driven by our core values.
Location: Remote, preference for Netherlands, United Kingdom, Ireland, Spain or Portugal. Key engineering and product teams are based in these locales.
The Role
As a Senior Full Stack Software Engineer on the Product Engineering team, you'll design and deliver high impact features, working closely with product, design, and other engineers to solve complex problems, build scalable solutions, and ensure our systems are maintainable and performant.
You’ll take ownership of projects from concept to production, contribute to architectural decisions, write high quality code, and help raise the technical bar by sharing knowledge and best practices with your teammates.
You'll work on:
Building elegant features for user researchers to analyze and extract compelling insights from qualitative data, using both classical techniques and large language models
Expanding audience management to help researchers connect with and reward participants from across the world
Integrating video and scheduling tools to provide a streamlined experience for managing and booking user interviews
As a product engineer at Maze, you will:
Partner closely with product managers, designers and other engineers to design, build, and ship new features
Establish best practices, frameworks, and repeatable processes that enable us to measure the impact of every feature that we ship
Evaluate and improve the performance, maintainability, and security of applications in production
Work in a collaborative and open team, which places high value on feedback, continuous learning and trust.
You should apply if:
You're proficient with modern full-stack JavaScript (Node.js and React) and relational databases (PostgreSQL)
You're enthusiastic about well-tested code and strive to improve your work environment
You have excellent written and spoken English skills
You thrive in a remote environment
Bonus points:
You have Next.js, NestJS, GraphQL, and/or TypeScript experience
You have experience with AWS and/or Kubernetes
You're interested in UX, UI design, and the research field
Inclusivity and Pay
At Maze, we are dedicated to building an equitable, inclusive, and authentic workspace. Unique and diverse perspectives are welcomed, and continuous growth is encouraged. We believe that people are more than their resumes, so if your past experience looks different than the criteria listed, we'd still love to hear from you. We appreciate and celebrate non-traditional life routes and encourage you to apply should you connect with a job description or the Maze culture.
Maze values transparency and it enables us to approach compensation equitably across the world. We are informed by data and regularly check our salary ranges (either United States or Rest of World) against other venture backed companies. Additionally, we are proud of our holistic and generous benefits offerings, included in every compensation package.
Your salary is dependent upon many factors, including years of experience, expertise, etc. During your first interview, you can expect to have an open conversation with your recruiter regarding your compensation expectations.
Why Maze is unique
Early-stage startup: You will join an early-stage startup with less than 150 team members. This means you'll have the unique opportunity to directly impact success and help shape the future of Maze.
Market disruption: We believe that the way companies build products is fundamentally broken and the user research market is ripe for disruption. For too long, companies have been forced to choose between rapid development without user insights or investing months into research before bringing products to market. But there's finally a groundswell building around a path forward that eliminates this compromise - and Maze is leading the charge.
Product-market Fit: Maze is used by 100,000+ brands across 4,000 companies, from SMB to enterprises, and in the last fiscal year, we saw 6.5M questions answered, supporting 25K decisions
Benefits
Health insurance with international coverage, vision, and dental: 100% of the team member premium paid
For some locations, coverage options vary, please see our benefits pages for more information
Free access to proper mental health care, unlimited virtual therapy sessions (with a human) and 24/7 access to resources
Life and Disability Insurance, 100% of the team member premium paid
Flexible time off
Meaningful equity
Company retreats, fully paid for by Maze
New MacBook (laptop), paid for by Maze
Paid Family leave: 16 weeks for birth or adoptive parents
$500/month to be used for dependent health insurance coverage
If you don't have dependents to add to your plan, you will still get access to this money to be used at your discretion to get the benefits that matter to you with our flexible a-maze-ing benefits - gym memberships, co-working spaces, food, travel, whatever!
$1,500 remote work setup fund to ensure you can set up a productive work space
Flexible work schedule where you manage your own working hours
Monthly Bonus.ly points that are awarded to others to recognize teamwork, dedication and helpfulness - points can be cashed out for gift cards and more
Virtual social engagements randomly throughout the year
SWAG, we have some really cool swag
Open, transparent culture that includes virtual: coffee chats, bi-weekly all-hands meetings, and more
Check out all of our a-maze-ing benefits here.
Outreach Notice
We understand you might be excited about the job you’re applying for, we are excited you are interested! However, please refrain from reaching out to our current team members on LinkedIn for referrals. Our policy is that referrals can only be provided by team members who personally know the candidate. With the high volume of interest in our roles, contacting our team members who are not involved in recruitment can be overwhelming. Additionally, please avoid submitting support tickets regarding your application, as our support team is not involved in the hiring process. Rest assured, our recruitment team is diligently reviewing all applications and will reach out directly if there is a match.來源: Jobicy — United Kingdom查看職缺/前往原網站應徵 ↗
已發布: