Discord Interview Process: 4 Stages, TCP Chat Server Round & US Pay
Discord interview process for 2026: recruiter screen, hiring manager round, live TCP chat server build, final loop, 12 questions and posted US pay.
Last updated: November 2026
TL;DR
The Discord interview process runs in four stages after you apply on its Greenhouse job board: a recruiter screen, a hiring manager round (for engineers this is often technical, with web service design or coding), a role-specific technical round (the build-it-live TCP chat server for many software engineers, SQL and a case for data scientists, a portfolio review and skills challenge for designers), and a final loop (virtual in candidate reports) that combines coding, system design and behavioral interviews. Discord does not publish a timeline; Glassdoor’s candidate-reported average is about 27 days. Rehearse the socket-server build and your project deep dive in OphyAI Interview Practice, and use OphyAI Interview Copilot for real-time answer suggestions on live Zoom, Microsoft Teams or Google Meet rounds.
Quick Answer: Discord Interview Process
| Stage | What to prepare |
|---|---|
| Application on Discord’s Greenhouse job board | A resume naming the posting’s stack (React, TypeScript, Python, Rust) and one project with a user metric |
| Recruiter screen | A 60-second story, a specific “why Discord,” location fit and pay inside the posted range |
| Hiring manager round | One project told end to end, plus a web service design or coding discussion for engineers (candidate-reported) |
| Role-specific technical round | A live TCP chat server build (software), SQL and a case (data science), or a portfolio review and skills challenge (design) |
| Final loop | Coding, real-time system design and behavioral interviews (prepare stories for Discord’s seven principles) |
Action Plan: Prepare for Discord by Round
| Round | What Discord tests | What to do before the interview |
|---|---|---|
| Recruiter screen | Match to the posting, motivation, location and level | Read the posting’s office line (it varies from no office requirement to 3 days a week) and decide your answer first |
| Hiring manager | Depth on your best project and how you work with Product and Design | Pick two projects and write the problem, your decision, the trade-off and the metric for each |
| Chat server build | Whether you can ship working networked code fast, with concurrency handled | Build a multi-client socket chat server from a blank file three times in your main language, testing with telnet or netcat |
| System design | Real-time messaging, fan-out, presence and storage at Discord scale | Read Discord’s engineering posts on Elixir and ScyllaDB and practise a chat fan-out design aloud |
| Data science case | Experiment design, SQL fluency and product judgment | Design an A/B test for a Nitro or onboarding change, including guardrail metrics |
| Behavioral round | Fit with Discord’s seven principles | Map one STAR story to each principle |
With one week as an engineer, spend half of it on the chat server build, because candidates report rejections for speed even with working code. Spend the rest on one real-time design and your project deep dive.
What Makes Discord Different
Discord is a voice, video and text chat platform built around communities called servers, and its postings say “nearly everyone” on it plays video games. Its headquarters is at 444 De Haro Street in San Francisco, the address on its SEC filings. The careers page says “We have one office in San Francisco and one in Amsterdam,” and calls Lisbon “home to our newest engineering hub.”
Discord reported “more than 200 million monthly active users” in April 2025, and a November 2026 posting cites “more than 90M daily active users.” The company is private. Bloomberg reported on January 7, 2026 that Discord had filed confidentially for a US IPO with Goldman Sachs and JPMorgan Chase, adding that it “could decide not to proceed.” On November 10, 2026, SEC EDGAR showed only Form D filings for Discord Inc., with no public S-1.
Humam Sakhnini, formerly Vice Chairman at Activision Blizzard, became CEO on April 28, 2025, and co-founder Jason Citron moved to the board and an advisor role. In January 2024 Discord cut about 170 jobs, roughly 17% of staff; the CEO’s memo said headcount had grown “5x since 2020.” Its Greenhouse board listed 26 open roles on November 10, 2026, all in the US, so each requisition is competitive.
Traits that shape what Discord interviewers look for:
- Shipping over polish. The “Progress Over Perfection” principle says “All big things start small.” The chat server round rewards working code first.
- Data in every decision. A data science posting says Discord runs “hundreds of experiments at any given time.” Bring a metric to every story.
- Real-time engineering. Discord’s engineering blog describes scaling Elixir to 5,000,000 concurrent users and moving messages from 177 Cassandra nodes to 72 ScyllaDB nodes, with Rust data services in between.
- Users who care. Postings ask for “empathy for your internal and external users.”
Rehearse your project deep dive and the chat server walkthrough aloud in OphyAI Interview Practice. On live video rounds, OphyAI Interview Copilot in the desktop app gives real-time answer suggestions on Zoom, Microsoft Teams or Google Meet in a window excluded from screen sharing and recording. It is not hidden from your webcam, anyone in the room, or proctoring software.
Interview Process Overview
Discord does not publish a standard loop. Its careers FAQ says “your recruiter will share all the details you need to know about the entire interview process - including how to prepare for each stage.” The table combines that page with candidate reports, labelled as such.
| Stage | Format | Duration | Timeline |
|---|---|---|---|
| Application | Greenhouse job board; referred candidates do not need to apply separately | Not published | Discord aims to respond “within two weeks” |
| Recruiter screen | Phone or video | Not published | Not published |
| Hiring manager round | Video; for engineers often web service design and coding (candidate-reported) | Not published | Not published |
| Role-specific technical round | Chat server build, SQL and case, or portfolio review and skills challenge | Not published | Not published |
| Final loop | Virtual; one senior engineer reported seven interviews after a phone screen (candidate-reported) | Not published | About 27 days on average across 202 Glassdoor reports (candidate-reported) |
Recruiter screen. What they test: whether your level, location and background match the requisition. Red flags: a generic “I love gaming” with no product detail, or a base ask far above the posted range. How to prepare: write a 60-second answer that names the squad (Consumer Revenue, Safety, Growth, Ads) and rehearse it in a voice session of OphyAI Interview Practice.
Hiring manager round. What they test: depth on one project and how you work with Product, Design and Data Science. A senior software engineer who interviewed in March 2026 described an in-depth hiring manager round on web service design and coding (candidate-reported). Red flags: a team result with none of your own decisions in it. How to prepare: run a technical mock in OphyAI Interview Practice that keeps asking “why that choice?”
Role-specific technical round. What they test: hands-on skill in the job’s format. Red flags: setup trouble and silent coding. How to prepare: see the chat server section below, and rehearse coding aloud in OphyAI Coding Interview.
Final loop. What they test: technical depth, real-time system design, collaboration and fit with Discord’s principles. Red flags: stories with no metric. How to prepare: book two back-to-back mocks, then use Interview Copilot on the live video loop for real-time suggestions when a follow-up goes past your notes. Afterwards, draft thank-you notes with OphyAI Application Assistant.
The Build-It-Live Chat Server Round
The round that most separates Discord from a generic big-tech loop is a practical build. Glassdoor question entries describe it as “Build chat server handling multiple TCP clients,” “Design a chat server using sockets that can accept multiple client connections via telnet,” and “Using Telnet or NetCat, create a chat server that allows multiple clients to connect and send messages to one another” (all search excerpts, candidate-reported).
One candidate was limited to Node’s built-in net module, one tested with several PuTTY windows in “Raw” mode, and a staff-level candidate was asked for forwarding to all clients and a clean shutdown. One candidate had working code and was rejected the next day; another was rejected for not being fast enough (search excerpts, candidate-reported).
What they test: going from a blank file to a working networked program that handles many connections, while you keep talking.
Red flags: long scaffolding, echoing to the sender, crashing on disconnect, ignoring partial reads, and never testing with two clients.
How to prepare: install telnet or netcat before the call and check your firewall. In your strongest language, build the server three times from scratch: accept connections, keep a set of clients, read lines, broadcast to everyone except the sender, remove clients on disconnect, and shut down cleanly. Then add names, a /quit command and a message limit as likely follow-ups. Practise narrating it in OphyAI Coding Interview; in the live round, Coding Copilot in the desktop app (Premium) snaps the problem window and shows how it read the problem, the code, a dry run with edge cases and the Big O in an overlay excluded from screen sharing, which does not hide it from a webcam, a person in the room or proctoring software.
Role-Specific Breakdowns
Software Engineer (Product Engineering)
The Senior Software Engineer, Consumer Revenue posting covers “Nitro, shop, boosting, user identity, and more” and says “We work primarily in the web (React, TypeScript), mobile (React Native, with a small amount of Kotlin, Objective-C, and Swift), and backend (Python).” It asks for “5+ years of software engineering experience” and “React performance and client-server performance optimization.”
What they test: full-stack fluency, product sense and shipping speed. Red flags: backend-only answers to a full-stack role, or no idea how you measured a launch. Rehearse a feature walkthrough from spec to experiment result in OphyAI Interview Practice, and see our technical interview prep guide.
Backend, Infrastructure and Safety Engineering
The Staff Software Engineer, Safety Processing posting describes “processing signals from user reports and automated systems to identify and remove harmful or illegal content,” “primarily using Python,” and asks for an “adversarial mindset” and 24/7 on-call experience. A security posting says “we use Python, Typescript, and Rust.”
What they test: pipeline design, failure handling and thinking like an attacker. Red flags: a design with no abuse case. Practise a report-processing design in a system design session of OphyAI Interview Practice, and read our system design interview guide.
Machine Learning Engineer
The Senior Machine Learning Engineer (Growth) posting asks for “5+ years” shipping recommendation or personalization systems, “embedding-based retrieval (e.g. two-tower models),” and solving “cold-start personalization for users with little or no history on Discord.” What they test: retrieval and ranking design and online experiments. Red flags: a model with no serving story. Talk through a cold-start recommender in OphyAI Interview Practice and review our machine learning interview questions.
Data Scientist
The Staff Data Scientist, Causal Inference and Experimentation posting mentions a “Data Science team (50+ members).” One candidate reported a recruiter screen, a hiring manager screen, a 45-minute technical screen with simple SQL and a case, then a four-interview onsite with behavioral, SQL and two case rounds; designing an A/B test for a Discord product change comes up repeatedly (search excerpts, candidate-reported).
What they test: SQL, experiment design and product judgment. Red flags: p-values with no decision attached. Run a Nitro experiment case in OphyAI Interview Practice, and drill our SQL interview questions.
Product Manager
The Group Product Manager, Data/ML posting asks for “8+ years of combined experience in data science and product management.” Candidates report “what’s your favorite digital consumer product, and why?” and a prompt to improve a product and set a metric goal for its subscription offering (search excerpts, candidate-reported). What they test: product sense, metrics and deep familiarity with Discord. Red flags: never having used servers, Nitro or voice channels. Run a product sense mock in OphyAI Interview Practice, and see our product manager interview questions.
Product Designer
The Senior Product Designer, Consumer Revenue posting asks designers to “Connect consumer and business goals through design decisions you can clearly articulate.” One designer reported a recruiter screen, a portfolio review with the hiring manager, a skills challenge and a virtual onsite (search excerpt, candidate-reported). What they test: product thinking, craft and the reasoning behind each decision. Red flags: final screens with no problem, data or trade-off. Present two case studies in OphyAI Interview Practice and let it challenge every decision.
Common Questions with Frameworks
Candidate-reported questions plus labelled practice questions, each with what Discord tests, the red flags and how to answer.
1. “Build a chat server that handles multiple TCP clients.” (Coding, candidate-reported)
What they test: working networked code, concurrency and speed. Red flags: echoing to the sender, crashing on disconnect, no live test. Approach: State the plan in 30 seconds (listen, track clients, broadcast lines, clean up), build the smallest version that works, test it with two telnet sessions, then add names, commands and graceful shutdown. Narrate trade-offs (event loop versus a thread per client).
2. “Design a web service for this feature, then code part of it.” (Hiring manager, candidate-reported)
What they test: API design, data modelling and moving from boxes to code. Red flags: skipping the data model, or designing for a billion users when the feature has ten thousand. Approach: Clarify users and scale, define endpoints and the schema, call out the hot path and caching, then write the core handler with validation and error cases.
3. “Design message fan-out for a server with hundreds of thousands of members.” (System design, practice question)
What they test: real-time delivery, fan-out cost and back pressure. Red flags: one database write per recipient, or no plan for offline users. Approach: Store the message once, partitioned by channel and time bucket, and push it through gateway sessions to online members only. Discuss batching and slow nodes. Our system design interview questions page has a chat app prompt to practise.
4. “Design a per-user rate limiter for sending messages.” (Coding or design, practice question)
What they test: algorithm choice and distributed thinking. Red flags: a global lock, or no answer for many servers. Approach: Compare fixed window, sliding window and token bucket, pick one and say why, return the time until the next allowed send, then move state to a shared store and discuss clock skew.
5. “Design an A/B test for a change to a Discord product.” (Data science, candidate-reported)
What they test: hypothesis, unit of randomization and metrics. Red flags: randomizing by user when the feature works at server level, or no guardrail metric. Approach: State the hypothesis, choose the unit (user, server or channel) and explain network effects, define a primary metric and guardrails such as retention and safety reports, size the test, then say what result ships the change.
6. “Write SQL to find daily active users and seven-day retention.” (Data science, practice question)
What they test: SQL fluency with dates, joins and window functions. Red flags: counting events instead of distinct users. Approach: Define “active” first, build a cohort table by first-seen date, join on day plus seven, and check time zones and duplicate events.
7. “What’s your favorite digital consumer product, and why?” (Product, candidate-reported)
What they test: product taste and structured critique. Red flags: a famous app with generic praise. Approach: Pick a product you use weekly, name the user and the job it does, give one thing it does unusually well and one you would change, and attach a metric to the change.
8. “How would you improve Nitro and set a metric goal for it?” (Product, adapted from a candidate-reported prompt)
What they test: monetization judgment that protects free users. Red flags: a price increase as the whole answer. Approach: Segment subscribers and non-subscribers, pick one problem (discovery, perceived value, churn), propose an experiment, and set a primary metric with a guardrail on free-user engagement.
9. “Walk us through a project in your portfolio.” (Design, candidate-reported)
What they test: problem framing, process, craft and use of data. Red flags: only final screens, or no failed direction. Approach: Problem, constraints, research, two directions you rejected and why, the shipped design, and the result in numbers. Keep each case to about ten minutes.
10. “Tell me about a time a project went wrong.” (Behavioral, practice question)
What they test: honesty and learning, which Discord’s “Embrace the Brutal Facts” principle names. Red flags: blaming others. Approach: Use the STAR method: what broke, the data that showed it, your part and what you changed. Our guide to answering the failure question has examples.
11. “How would you build a system to process user reports of harmful content?” (Safety engineering, practice question based on the posting)
What they test: pipeline design, prioritization and adversarial thinking. Red flags: one first-in, first-out queue for everything, or no thought about people abusing the report button. Approach: Ingest reports and automated signals, deduplicate, score severity, route the worst cases first, keep audit logs, and plan for attackers who flood reports.
12. “Why Discord?” (Motivation)
What they test: product and team knowledge. Red flags: “I play games” and nothing else. Approach: Name the squad, a feature you use and one change you would test, linked to your work. For more practice, see our common interview questions and answers.
Culture Fit: Discord’s Seven Principles
Discord published “The Seven Principles of Working at Discord” in April 2024, and the careers page links to them. Prepare one story for each.
Cultivate Belonging. “Start from a place of trust, assume good intent.” Show a time you changed your mind after listening.
Deliver for Customers. “Focus on their needs, not what the competition is doing.” Bring a decision you made from user feedback.
Surprise and Delight. It “comes from caring about the million little details.” Show one detail you sweated.
Debate, Decide, Commit. “Transparency is our goal, not consensus.” Tell a time you disagreed, lost the argument and helped the decision succeed.
Progress Over Perfection. “All big things start small.” Show a small first version you shipped.
Embrace the Brutal Facts. Inspect reality, with data where you can. Tell a story where data killed your idea.
Strive for Excellence. Show work you are proud of and how you raised the bar.
What interviewers screen for: real product familiarity, a metric in every story, comfort shipping small, and honesty when your work did not land.
Compensation Overview (2026 Estimates, USD)
Figures below are posted base ranges from US postings on Discord’s Greenhouse job board, checked November 10, 2026. Postings say each role is “eligible for equity and benefits” and that “the compensation details listed in role postings reflect the base salary only, and do not include equity, or benefits.” Discord does not publish grant values.
| Role | Base Salary | Total Compensation (Base + Bonus + Equity) |
|---|---|---|
| Senior Software Engineer, Consumer Revenue (SF Bay Area) | $196,000-$245,000 | Equity, not published |
| Staff Software Engineer, Safety Processing (SF Bay Area or Los Angeles) | $279,000-$341,000 | Equity, not published |
| Staff Software Engineer, Machine Learning (SF Bay Area) | $272,000-$340,000 | Equity, not published |
| Senior Machine Learning Engineer, Growth (SF Bay Area) | $220,000-$275,000 | Equity, not published |
| Senior Data Engineer, Ads (remote US) | $196,000-$245,000 | Equity, not published |
| Staff Data Scientist, Causal Inference (SF Bay Area) | $248,000-$310,000 | Equity, not published |
| Group Product Manager, Data/ML (SF Bay Area) | $304,000-$380,000 | Equity, not published |
| Senior Product Designer (SF Bay Area) | $188,000-$235,000 | Equity, not published |
| Strategic Finance Analyst (SF Bay Area) | $116,000-$130,500 | Equity, not published |
For total pay, Levels.fyi lists a candidate-reported US median of $373,000 a year for Discord software engineers, $153,749 at L1 (entry) and $364,205 at L3 (Senior), updated November 9, 2026. US benefits on the careers page include four weeks of PTO, 16 paid holidays and 12+ weeks of parental leave. Ask your recruiter for the level, the equity grant value and the vesting schedule before you answer a number, and read our salary negotiation guide.
Preparation Timeline: 4-6 Weeks
| Week | Focus | Activities |
|---|---|---|
| 1 | Product and posting | Use Discord daily (servers, voice, Nitro). Write a “why Discord” that names the squad. |
| 2 | Chat server and coding | Build the multi-client TCP chat server from scratch three times; solve 15-20 medium problems in OphyAI Coding Interview, then re-solve unaided. |
| 3 | Real-time system design | Practise chat fan-out and a rate limiter; read Discord’s Elixir and ScyllaDB posts. Data scientists: A/B cases and SQL. Designers: two portfolio cases. |
| 4 | Principles and stories | Write seven STAR stories, one per principle, each with a metric. Drill them in OphyAI Interview Practice. |
| 5-6 | Mock loop | Run back-to-back mocks covering coding, design and behavioral. Prepare one question for each interviewer from our questions to ask the interviewer. |
Common Mistakes
Practising only LeetCode. The chat server round is about sockets, concurrency and shipping working code under time, not about a clever algorithm.
Not testing your environment. One candidate found their firewall blocked local telnet connections (candidate-reported). Test telnet or netcat, your editor and screen sharing the day before.
Talking about gaming instead of the product. Interviewers want to hear what you would build, measure or fix in Discord itself.
Stories without numbers. A company running hundreds of experiments at once expects a metric in your answers.
Prepare for Discord with OphyAI
Discord’s loops reward candidates who can build working code live, design for real-time scale and back every story with data.
Use OphyAI Interview Practice for voice or text mock interviews with follow-up questions, a transcript and per-answer feedback in behavioral, technical, system design and case formats; the free plan’s credits cover one session of up to 15 minutes. On live video rounds, Interview Copilot gives real-time answer suggestions and a live transcript in 35 languages, and runs on the web or in the Mac and Windows desktop app. Pro is $29 a month with 300 credits and Premium is $59 a month with 500 credits (there is no $9 OphyAI plan; the Basic plan was retired in July 2026). Premium includes OphyAI Coding Interview for the chat server and coding rounds, and OphyAI Resume Builder tailors your resume to each Discord posting. Start practicing →
Start Your Discord Application
Ready to apply? OphyAI can help at every stage:
- Search for open roles at Discord and similar companies with AI-powered job matching
- Generate a tailored cover letter that highlights your fit for the role, plus follow-up emails and thank-you notes for after your interviews
- Track your application status alongside every other role you’re pursuing
Pair these with Interview Copilot for structured live interviews, or practise first with OphyAI Interview Practice.
Related company guides
- Reddit interview guide
- Roblox interview guide
- Snap interview guide
- Figma interview guide
- Spotify interview guide
Frequently Asked Questions
What is the Discord interview process?
After an application on Discord’s Greenhouse job board, candidates usually go through a recruiter screen, a hiring manager round, a role-specific technical round and a final virtual loop. Many software engineers report building a multi-client TCP chat server live, data scientists report SQL and case rounds, and designers report a portfolio review and skills challenge. Recruiters share the full process with each candidate.
How long does the Discord hiring process take?
Discord does not publish a timeline. Glassdoor’s candidate-reported average is about 27 days across 202 reports (search excerpt), and one senior engineer described about three weeks including seven interviews. Discord’s careers FAQ says it tries to respond to each applicant within two weeks but cannot guarantee a reply.
What is the Discord chat server interview question?
Candidates describe building a chat server that accepts several clients over TCP, tested with telnet, netcat or raw PuTTY sessions, that forwards each message to the other clients and handles disconnects and shutdown cleanly. One candidate was limited to Node’s built-in net module. Practise it from a blank file and test your local tools first.
How much does Discord pay software engineers in the US?
Posted base ranges checked in November 2026 run from $196,000-$245,000 for a senior software engineer to $279,000-$341,000 for a staff engineer on Safety Processing, plus equity that postings do not quantify. Levels.fyi lists a candidate-reported US median total compensation of $373,000 a year for Discord software engineers, including stock.
Does Discord hire remote employees and sponsor visas?
Some roles are remote within the US, others require the San Francisco Bay Area, and office expectations range from none to three days a week. Discord hires full-time staff in the US, Canada (Ontario and British Columbia only) and the Netherlands. Its careers FAQ lists continued sponsorship for current O-1, TN, E-3, H-1B1 or H-1B holders and Green Card sponsorship after six months.
How does OphyAI work in a Discord interview?
OphyAI Interview Practice runs voice or text mock interviews with follow-up questions and per-answer feedback, which suits rehearsing a project deep dive or portfolio review. On live Zoom, Microsoft Teams or Google Meet rounds, Interview Copilot gives real-time answer suggestions from a live transcript, and Coding Copilot in the desktop app (Premium) helps on coding rounds. The desktop overlay is excluded from screen sharing and recording, but not from a webcam, a person in the room or proctoring software.
Sources and verification notes
Sources checked November 2026. Discord’s careers page, its Greenhouse job board (public API), engineering blog, CEO press release, SEC EDGAR and Levels.fyi were read directly. Glassdoor returned HTTP 403, so every Glassdoor figure here (the 27-day average, round formats, the chat server task, interview questions) is a search excerpt and candidate-reported. Questions marked “practice question” are ours. Discord does not publish a standard loop or timeline.
- Discord careers page: offices, Lisbon hub, hiring countries, immigration policy, two-week response aim, recruiter prep line, benefits.
- Discord Greenhouse job board API: 26 open roles on November 10, 2026, base ranges, stack, office lines and duties, including Senior Software Engineer, Consumer Revenue, Staff Software Engineer, Safety Processing and Staff Data Scientist, Causal Inference (90M daily actives, hundreds of experiments, 50+ data scientists).
- The Seven Principles of Working at Discord (April 2024).
- Discord appoints Humam Sakhnini as CEO (April 2025): effective April 28, 2025; more than 200 million monthly active users.
- How Discord Stores Trillions of Messages (2023) and How Discord Scaled Elixir to 5,000,000 Concurrent Users (2017).
- SEC EDGAR filings for Discord Inc.: 444 De Haro Street address; only Form D filings on November 10, 2026.
- Bloomberg Law on the confidential IPO filing (January 2026).
- VGC on the January 2024 layoffs: about 170 jobs, 17%, headcount up 5x since 2020.
- Levels.fyi, Discord software engineer pay: US median $373,000, L1 $153,749, L3 $364,205, updated November 9, 2026 (candidate-reported).
- Glassdoor Discord interview pages (search excerpts only), for example overview, the TCP chat server question and data scientist reports (all candidate-reported).
Tags:
Share this article:
Interviewing at Discord? Rehearse the rounds, then get live help on the call.
Practice free for up to 15 minutes, then use Interview Copilot in the OphyAI desktop app: real-time answer suggestions on Zoom, Teams and Google Meet, in a window hidden from screen sharing.
On your phone? Practice Discord questions in the OphyAI app.
Hidden from screen share and recording; a webcam or a person in the room can still see your screen.
Related Articles
Canadian Tire Interview Process: 4 Steps, Dealer Hiring & 20 Questions
Company Guides
Canadian Tire interview guide 2026: the 4-step hiring process, how Associate Dealer stores hire, 20 store and corporate questions, CAD pay and a prep plan.
Read more →
CIBC Interview Process 2026: 5 Steps, Assessments & 18 Questions
Company Guides
CIBC interview guide 2026: the 5-step hiring process, attribute-based and video assessments, branch role-plays, Capital Markets rounds, coding tests, CAD pay.
Read more →
Hydro One Interview Process 2026: JAC Apprenticeships & 20 Questions
Company Guides
Hydro One interview guide 2026: the PWU/Hydro One JAC powerline apprentice route, new grad engineering, call centre testing, 20 questions and posted CAD pay.
Read more →