Careers at Kepler Communications: Teams, Pay and How to Get Hired

Career Opportunities at Kepler Communications — The Definitive Guide to Getting Hired

The founding template

Kepler Communications operates 23 satellites from a former General Electric factory in Toronto, having raised more than $200 million since four University of Toronto engineers founded the company in 2015. This guide maps who Kepler hires onto which teams, what the compensation looks like, how the hiring process works, where the work happens across its sites, and which personal traits lead to success at the company.

The founding team set the template. Mina Mitry, now CEO, grew the University of Toronto's aerial robotics club from five members to over 100 and raised millions in sponsorship before dropping out of a Pratt & Whitney-funded PhD five days in — the IP would have belonged to the engine maker. His co-founders, Jeffrey Osborne, Mark Michael, and Wen Cheng Chong, came from the same design team. Mitry's pre-Kepler resume reads like a startup sampler: TeaBot (robotic tea kiosks), Brizi (arena AR cameras), a master's optimizing aircraft engines. That mix of hands-on hardware, software, and scrappy commercialization still shapes who Kepler hires.

Today the workforce sits around 200 people. The board's live postings show the current hiring focus: Senior Embedded Software Designer, Embedded Software Designer, Senior Electrical Design Engineer, Senior Electrical Engineer & Team Lead, Senior Program Manager, and Staff Program Manager. These roles map directly to the three pillars Kepler builds on: flight software that runs onboard computation and optical routing, electrical subsystems that survive launch vibration and orbital thermal cycles, and program management that coordinates launches, regulatory filings, and customer deliveries across Canadian and European space agency contracts.

Team structure follows the hardware-software boundary. Embedded software designers own the real-time operating systems, protocol stacks, and payload applications that turn a 300-kilogram bus into a node in an optical mesh. Electrical engineers own power, RF front ends, and payload interfaces — the Globe and Mail described staff debugging specialized computer components beside a wall of screens monitoring active satellites. Program managers sit across both, tracking the critical path from cleanroom integration through environmental test to launch vehicle integration. The "Team Lead" designation on the senior electrical role signals that Kepler expects individual contributors to grow into people leadership without leaving the technical track.

Candidate backgrounds cluster around three vectors. First, aerospace-adjacent hardware experience: engineers who have taken a board from schematic through vibration test and thermal vacuum, preferably on small satellites or constrained-form-factor systems. Second, embedded software fluency in C/C++ on RTOS, bare-metal, or Linux, with a bias toward developers who have shipped code that runs without a reboot for months. Third, program management that speaks both engineering and regulatory: ITAR/EAR compliance, FCC and Innovation, Science and Economic Development Canada licensing, and the documentation discipline that defense contracts demand. The company's October 2023 DRDC award for Arctic monitoring demonstrates the latter; optical inter-satellite links demonstrated on orbit prove the former two.

Kepler's open-architecture pitch, interoperable with Tesat, SpaceX, and Lockheed Martin terminals, also means they hire for interface discipline. Engineers who treat ICDs as contracts, not suggestions, thrive here. The Canadian sovereignty angle matters too: the company controls satellites and data routing under Canadian law, a selling point for non-U.S. customers wary of American export controls. That regulatory fluency is a hiring criterion, not a compliance afterthought.

Compensation at a glance

Kepler's public job postings show a compensation structure clustering in the low- to mid-six figures for engineering and program roles, with a board-wide salary band running roughly $80k–$184k and a median near $170k across 20 salaried listings, Zero G Talent's board data shows.

The consistency across roles shows Kepler prices for scope and experience rather than function alone: senior individual-contributor engineering positions and program-management tracks occupy overlapping bands. The "Contingent" suffix on several listings indicates contract or project-based engagements that still carry the same base range as full-time equivalents — a signal that the company budgets for talent density regardless of employment model.

Equity and benefits detail is absent from the board data. Kepler's careers page, which the research did not surface, would be the authoritative source for stock-option grants, vesting schedules, health coverage, retirement matching, and any space-industry perks. Without that primary source, any description of the total-rewards package would be speculative. Candidates should treat the posted base ranges as the floor and request the equity and benefits summary early; Canadian space-sector peers typically offer option pools in the 0.1–0.5% range for senior hires, but Kepler's exact structure remains undocumented.

Geographically, every current listing is anchored to Toronto, Ontario. That single-site concentration simplifies compensation benchmarking, with no geographic differentials to decode, but it also means remote or hybrid negotiators have less leverage to argue for location-based adjustments. The board's median of $170k places Kepler competitively against other Toronto-area space hardware firms.

The program manager band ($132k–$182k) sits below the senior engineering bands — a reminder that Kepler values technical depth over management track at the individual-contributor level.

Inside the hiring loop

Kepler Communications does not publish a public interview playbook. The company's careers page lists open roles and benefits but does not detail stages, timelines, or scoring rubrics. Public interview reviews for Kepler are sparse and generic, without stage-by-stage breakdowns. That silence is a signal: Kepler hires like a hardware startup that moves fast, keeps process lightweight, and expects candidates to demonstrate competence through work samples rather than whiteboard puzzles.

The Zero G Talent board shows 20 salaried postings in the current cycle, clustered in embedded software, electrical design, RF/payload, flight software, and program management. Every listing carries a "Senior" or "Staff" prefix except the Embedded Software Designer role. The salary bands map to five to ten years of direct hardware-in-the-loop experience. Kepler is not hiring juniors into flight-critical subsystems. A candidate who clears the resume screen has already shipped a PCB that flew, written flight code that passed vibration test, or managed a satellite program through CDR.

The "Contingent" tag on two postings (Staff Program Manager, Senior Electrical Design Engineer) suggests roles tied to specific contract milestones or funding gates. That means the hiring bar includes program-risk awareness: recruiters will probe whether you've worked under ITAR, managed export-controlled supply chains, or delivered to a launch-slot deadline that cannot slip.

Strong applications share three traits visible in the job descriptions. First, they name the bus: CubeSat, ESPA-class, or custom, and the orbit (LEO, SSO, VLEO). Second, they cite a specific subsystem owned end-to-end: ADCS firmware, power-conditioning unit, S-band transceiver, thermal strap qualification. Third, they show test evidence with concrete details rather than generic claims. Kepler's integration floor in Toronto runs daily hardware-in-the-loop tests; candidates who speak the language of flight hardware advance faster.

Disqualifiers are the inverse. So do candidates who cannot explain a failure they root-caused — Kepler's culture rewards post-mortem rigor. The company also screens for ITAR eligibility early; non-U.S. persons without Canadian permanent residency or citizenship face extra steps on roles touching controlled technical data. The Toronto site handles most RF and payload work; candidates unwilling to be on-site for integration weeks self-select out.

Candidates who frame answers around mission risk, linking technical choices to link margin, downlink closure, or customer delivery, score higher than those who optimize for cleverness. The company also checks references from prior flight programs; a former mission lead who vouches for your anomaly response carries more weight than a generic manager reference.

Bottom line: Kepler hires people who have already done the job they're applying for, on hardware that left the ground. The process filters for that proof. If you haven't flown, your path in is through a contractor role on the integration floor, the "Contingent" postings, where you earn flight heritage on Kepler's dime. That floor sits in the same former GE factory where the founding team now runs mission control.

Where the work gets done

Kepler's headquarters sits in Toronto, Ontario — a location the company has occupied since its early days above a nail salon and Wild Wing restaurant downtown, as a 2017 SpaceNews profile of co-founder Mina Mitry noted. The operation has since expanded into vertically integrated production facilities that let it manage the full lifecycle of satellite development and operations in-house. Kepler representatives described building their own S-band and Ku-band flight hardware with "significant flight heritage" on those radios in a January 2024 Breaking Defense interview. The same source notes the company has launched 21 satellites as part of its first-generation constellation and recently added two optical Pathfinder satellites equipped with RF payloads and optical communications terminals compatible with the Space Development Agency's constellation.

A U.S. office opened to focus on serving the U.S. government and what Kepler calls "U.S. flagship companies that support the government," per the same Breaking Defense piece. The company frames its Canadian headquarters as a strategic advantage: "The capabilities we're bringing to the U.S. industrial base use the engineering we do in Canada," and U.S.-domiciled companies face regulations that prevent them from launching with certain countries that have strong launch capabilities — a constraint Kepler avoids as a Canadian entity. Canada's status as the only non-European cooperating state of the European Space Agency also enabled the HydRON Element 3 contract, worth 18.6 million euros, where Kepler serves as prime contractor manufacturing and launching a host platform for multiple European optical terminals and payloads from Tesat, Mbryonics, Astrolight, and a space situational awareness payload from Vyoma.

The public record does not specify clean-room classifications, thermal-vacuum chamber dimensions, vibration-table specs, RF anechoic chamber details, or optical test-range capabilities at either site. It does not name the Toronto building's address, square footage, or whether machine shops and integration floors share one facility or span multiple. What the record does show is a production flow that moves from in-house radio development through satellite assembly, integration, and test, culminating in 21 launched spacecraft and a manifest that now includes a dedicated Rocket Lab Neutron launch as network expansion accelerates. The company's own careers page lists roles such as Senior Electrical Design Engineer, Senior Embedded Software Designer, and Staff Program Manager all based in Toronto, Ontario, suggesting the bulk of hardware and software engineering remains concentrated there.

For candidates, the takeaway is concrete: Kepler builds and tests its own satellites in Toronto, runs U.S.-facing business development from a stateside office, and uses its Canadian jurisdiction to access both U.S. defense contracts and European programs like HydRON. The facilities are the enabler of that vertical integration — but the public record stops at the capability claim, not the floor plan. The culture that fills those facilities is what determines who stays.

Who stays and why

Kepler's own communications, including job postings, public statements from CEO Mina Mitry, and the company's external positioning, converge on a handful of traits that separate people who stay from people who churn. The through-line is mission alignment expressed through technical pragmatism.

Mitry's background sets the tone. Before co-founding Kepler in 2015, his fourth startup and first in space, he built TeaBot (automated loose-leaf tea kiosks) and Brizi (augmented-reality camera systems for sports arenas). Neither was aerospace. Both required shipping hardware-software products to paying customers on tight timelines. That pattern recurs in Kepler's hiring: the company values engineers who have taken a physical system from concept to fielded operation, even if the domain was terrestrial.

The mission language is specific: "ubiquitous connectivity for the devices that gather the world's information." Not "democratizing space" or "making life multiplanetary." The initial service targets terrestrial IoT data backhaul; satellite-to-satellite relay comes later. Mitry told SpaceNews the constellation scales "from two to 20" spacecraft to meet commercial milestones, not an arbitrary coverage map. Employees who thrive treat each satellite as a revenue-generating asset, not a science platform. That mindset shows up in the hosted-payload pitch, "reduce cost, schedule risk, and technical complexity," and in the compute layer: "bring advanced processing closer to the source to enable faster decisions and more autonomous systems." The person who succeeds here asks "what does the customer need this quarter?" before "what is theoretically optimal?"

Canadian identity is a strategic lever, not a cultural accident. Mitry noted the investor split (60% U.S., 40% Canadian) and the launch-flexibility advantage: U.S.-domiciled companies face restrictions on certain launch providers that Canadian firms do not. Sara Seager, MIT professor and Kepler admirer, cited the company as proof Canada can "think big," her phrase for taking risks on "crazy ideas" and executing. That duality, Canadian incorporation for regulatory agility and U.S. capital for scale, attracts people comfortable operating across export-control boundaries (ITAR, CGP) without letting compliance become a velocity killer.

Speed with discipline defines the engineering culture. The Kepler space telescope (NASA's mission, namesake only) lost two reaction wheels in 2013; engineers salvaged the mission by using solar photon pressure as a third-axis stabilizer, extending operations from 10 planned campaigns to 19, NASA's Kepler mission's figures put it at 19. Kepler Communications references that heritage implicitly: "Built for Time-Critical Missions," "When Every Second Matters," "Detect, process, and deliver critical insights without delay." The lab and integration floor in Toronto remain the synchronization point for hardware milestones.

Equity is meaningful but not a lottery ticket. The board's salary bands sit above Canadian market for comparable roles, and the contingent-program-manager and contingent-electrical-engineer listings suggest project-based engagements that convert to full-time when milestones hit. People who stay treat equity as alignment, not exit strategy — the constellation's commercial milestones (first two spacecraft launched, then scaling to 75–140 operational) are the vesting schedule.

Disqualifiers are the inverse: resume-driven aerospace purists who wait for requirements documents; engineers who need a dedicated test team to validate their own code; managers who optimize for headcount over throughput. Kepler's lean history, seven people raising $5.5M as SpaceNews reported and ordering two demo satellites from Clyde Space within 22 months, still shapes the culture. The company hires builders who treat constraints as design inputs. Four engineers in a university room became 200 people operating 23 satellites from a former GE factory. The same constraint that forced them to build their own radios still filters every hire: show us the hardware that flew, and we'll talk.

Analysis of Kepler's discoveries concludes that 20 to 50 percent of the stars visible in the night sky are likely to have small, possibly rocky planets similar in size to Earth, and located within the habitable zone of their parent stars, as NASA's Kepler mission found.

Working in frontier tech? Zero G Talent tracks the openings: see every open Kepler Communications role, browse frontier tech jobs, the companies hiring, and the people building the field.