કામનું વર્ણન

Role Overview

Ashby is looking for a Design Engineer in Toronto who is equally strong in visual product design and hands-on coding. This is not a frontend role with a design label, and it is not a pure designer role focused only on prototyping. The expectation is that you can think through UX, shape the interface, and then build the experience end to end.

The company has formally established Design Engineering as a discipline that works closely with the co-founder and VP of Engineering. The team has been in place for over five years and is planned to grow from five people to more than ten within the next year.

What You’ll Be Working On

You will take on the hardest design challenges in the product, strengthen and extend the internal design system, and advise product engineers on custom design work. The role combines product thinking, system design, implementation, and collaboration across disciplines.

Redesign and improve the mobile web experience by speaking with frequent users, sketching new flows, building out the design system, and turning those wireframes into a polished interface.
Create flexible, reusable UI building blocks that help other engineers ship consistent and attractive setup experiences across the product.
Support product engineers by refining layout, structure, and readability so information is easier to scan and anomalies are easier to spot.

Why This Role Is Different

You will work on a mature product used at scale, with more than 100,000 weekly active users and millions of candidates each week. The work impacts well-known customers such as Notion, Linear, Shopify, and Snowflake, and feedback often comes back very quickly after release.

Leadership remains strongly committed to this discipline, and the role has been protected rather than diluted as the company has grown. The product itself is complex: it needs to feel approachable for first-time users while still offering deep customization and automation for advanced workflows.

Who This Role May Not Suit

Ashby is clear that this position is not ideal for everyone. You may not enjoy it if you want to focus only on design systems, prefer long research cycles before shipping, want every detail perfected before release, or rely heavily on structured process and project management to move work forward.

The team also expects strong visual judgment and the ability to handle a variety of work, including customer issues and investigations, rather than only the most exciting feature projects.

Level Expectations

The company is recruiting across multiple levels, from junior to staff, and asks applicants to choose the level that best matches their experience.

Junior Design Engineer: Up to 2 years of industry experience as either a designer or an engineer. Applicants should be able to show personal or professional projects with at least a couple of users that demonstrate strong visual taste and emerging strength in both UI/UX and engineering.
Design Engineer: At least 2 years of continuous experience as an engineer or designer, not counting internships. Candidates should be solid in both design and engineering and excellent in the area they practice full time. Experience should include designing products and shipping code to hundreds of users, even if that came through side projects.
Staff Design Engineer: Intended for people who have already been practicing this style of design engineering professionally. This may not have been their official title, but they should have made major contributions to a design system and repeatedly designed, implemented, and improved features for hundreds of users using feedback.

Product Context

Ashby was built because recruiting teams needed software that actually improved how they worked instead of slowing them down. The company focuses on building high-quality tooling for talent acquisition teams so they can move faster, gain insight into bottlenecks, and automate or simplify the work that usually consumes them.

One example is scheduling a final round interview, which normally involves collecting availability, identifying interviewers, finding mutual openings, booking the earliest possible slot, and adjusting schedules as things change. Ashby is designed to help recruiting teams handle that kind of work with much better software.

Engineering Culture

The engineering organization is built around a belief that a small, talented team can produce excellent software quickly while still keeping working hours reasonable. The environment emphasizes minimal process, strong ownership, deliberate communication, leverage through tooling, and building a diverse team.

Engineers own decisions that are often handled by product or design in other companies.
Collaboration is natural, but communication is intentional and well documented.
The team invests in tools and reusable abstractions that increase leverage across the product.
Diversity is treated as an active priority, not a passive goal.

Ownership and Workflow

Engineers are expected to run their projects with a high degree of independence. Product Managers and Designers set strategy, do customer research, and provide problem briefs. Engineers then take the work forward by researching the issue, writing product specifications, creating wireframes, and delivering the solution end to end.

Stakeholders are kept informed without heavy process overhead. The company believes strong engineers should be coached and trusted rather than wrapped in process as a substitute for ownership.

Collaboration and Communication

The team is described as humble, kind, and strong in cross-functional collaboration. They use research, prototyping, and written proposals to gather feedback across time zones while protecting focus time.

Engineers typically spend under 2 hours per week in meetings. The company also meets in person at least twice a year, once as a department and once as a full company, and employees receive a small budget to meet colleagues in their city or region.

Tools, Systems, and Leverage

Ashby has invested heavily in systems that help the team move quickly and maintain quality. This includes fast CI/CD, strong developer tooling, reusable platform building blocks, and AI-assisted workflows that help automate routine work such as issue triage, fix suggestions, prototype generation, production-ready code generation, and code review support.

Engineers have an unlimited token budget for AI tools, though usage is not a measured performance metric.

Diversity and Inclusion

The company says it is intentionally building opportunities for underrepresented groups and points to its current engineering makeup as evidence of progress. It also mentions efforts such as sourcing diverse candidates, offering generous paid family leave, and avoiding leetcode-style interviews.

Interview Process

The interview experience is designed to let candidates show their actual work and thinking. There are no leetcode rounds or whiteboard exercises. Instead, the process focuses on collaboration, design judgment, technical execution, and discussion of past decisions.

An introductory conversation with the co-founder and VP of Engineering, lasting 30 minutes and conducted live, during which candidates should be ready to screen-share examples of their work.
A second stage that is either a 1-hour live technical screen or a design take-home assignment of about 3 hours followed by a 30-minute live discussion.
Three further interviews, including a deep dive into a past design system or design project.

Additional Notes

The company explicitly says that internally it does not use the public junior/mid/senior/staff titles in the same way; leveling is based on proficiency. Applicants should select the level that sets accurate expectations for their background.

The role is based in Toronto, Ontario, Canada, and is a full-time onsite position.

Design Engineer, Canada

તમે ક્યાં કામ કરશો