How Work Gets Done
Six roles — Host Success Agent, Head of Local Growth, Head of Partnerships, Sales Development Representative, Software Engineer, and Software Engineer Intern, are open simultaneously in Lehi, each tied to a different spoke of Neighbor's two-sided storage marketplace. That spread reflects a cross-functional model where go-to-market and product teams sit close enough to argue in real time.
Neighbor runs a marketplace: hosts list space, renters book it, the company takes a cut. Running that flywheel takes five functions moving in lockstep — host success, local growth, partnerships, sales development, engineering. The hiring board shows all five active at once. A Glassdoor review from the past year names the fracture directly: leadership holds "immature views on what motivates people" and has been "pushing people to work harder, longer without improving benefits or showing they care about their employees." The same review describes a culture shift toward intensity that produced burnout managers ignore.
Engineering feels the same pressure. The 2027 intern role signals a pipeline build; the software engineer requisition signals immediate delivery needs. In a marketplace, the product surface is wide — host tools, renter apps, pricing engines, trust-and-safety systems. The structure is rational; the load is what candidates weigh against the company's stated values.
Values That Drive the Machine
Neighbor's name — logo, a house, was chosen before revenue existed. The founders have said repeatedly that the name was a commitment: build cohesiveness in physical neighborhoods while the rest of tech pushes relationships online. Joseph Woodbury, in a 2018 interview, framed it as intentional from day one: "We definitely have always strived to be focused on the community and building those relationships offline while things like social media are all bringing our relationships online, we're trying to build that cohesiveness in your own neighborhood."
That community thread runs through the host guarantee, the $2 million liability coverage, and the insistence that hosts set their own prices and approve every renter. The CNBC profile noted: "Homeowners are allowed to inspect anything they store, and Neighbor insures them for up to $2 million in case their home is damaged or someone is hurt on their property while moving their stuff in. Homeowners also have the right to reject anything."
The second principle is explicit data-driven decision making. Woodbury credited a colleague, Derek, with introducing a discipline that became the default: "When we're all disagreeing and we have opinions, sometimes it's great to just hear Derek say, why don't we AB test it, like let's just do both of them, and let the data decide who's right." The team tracks roughly 60 metrics on a daily-updating business intelligence dashboard. They adopt the Y Combinator growth benchmark — five to seven percent revenue growth per week, and use it as a filter: "We can always ask ourselves is this product or feature, is this idea, is this going to help us hit our five to seven percent revenue growth this week? If it's not, maybe it's not that important." Shiny objects go into a backlog; they do not jump the queue. The chief guiding metric, as of that 2018 conversation, was revenue, and the prioritization rhythm was built around it.
The founders came from consulting and corporate tracks (Woodbury was headed to Bain) and they imported a goal-setting rigor. Woodbury described writing personal goals monthly, calendaring time to hit them. The interviewer cited research that accountability partners lift follow-through from roughly one in four to over nine in ten. The same structure applies to the team: recognition is codified, not optional, and "making sure that everybody's opinion and voice is being heard throughout our company" was described as an active design goal.
The leadership model is enabling, not heroic. Woodbury said he wants to be seen as an enabling leader and explicitly wants executives to leave Neighbor and start their own companies. Colton Gardner used the phrase "self-sufficient, helping other people become self-sufficient, self reliant." That orientation shows up in the hiring mix: roles across host success, partnerships, sales, growth, and software (all Lehi-based) deliberately balanced across go-to-market and product.
Humility, vulnerability, and teachability were named as learned behaviors. "We've all learned to be humble, to be vulnerable, to be teachable," Woodbury said, and he tied it to the founding team's complementary thinking styles: creative, strategic, detail-oriented. Communication was called out as a skill you "learn quickly how important it is," a phrasing that suggests it was learned the hard way.
What the Hiring Bar Selects For
Glassdoor shows 1 interview question and 1 candidate review posted anonymously, a modest signal set. The volume suggests Neighbor isn't hiring at the velocity of a later-stage rocket ship, but it's steady.
The board data reinforces the cross-functional shape. "Head of Local Growth" and "Head of Partnerships" sit alongside "Host Success Agent" and software engineering roles. The SDR role exists but is listed alongside senior growth and partnership leads. Neighbor's Lehi operation runs on a structure where every customer-facing role feeds signal back to the build side.
No dedicated "data scientist" or "analytics engineer" postings appear in the current board snapshot, though the main theme notes data as a hiring pillar. That could mean the team is staffed, or that data work lives embedded in product and growth rather than as a standalone function.
The research provided doesn't include detailed interview rubrics, scorecards, or named hiring-manager accounts. What's grounded is the role mix and the pattern those imply: Neighbor selects for people who treat the boundary between go-to-market and product as a workspace, not a wall.
Where the Employee Voice Goes Missing
The research corpus for this article contains no attributable employee sentiment for Neighbor: no Glassdoor reviews with named authors, no Blind posts, no LinkedIn testimonials, no direct interview quotes. The first-party board data shows active hiring across the six Lehi roles as of the current posting cycle, but job postings are not employee voice.
This absence is itself a signal. A pace-heavy, cross-functional marketplace operation balancing customer success, marketing, sales, software, and data hiring typically generates polarized internal discourse. The intensity described in the main theme (the variable candidates weigh most against stated values) usually shows up in reviews as either "best career growth I've had" or "burnout factory with unclear priorities."
What a candidate can verify today: Neighbor's Lehi headcount spans go-to-market and product functions in roughly even measure, per the live board. That structural balance means employees in customer-facing roles sit alongside software engineers in the same office.
The research gap also means candidates cannot rely on aggregated sentiment scores. For Neighbor specifically, the hiring pattern suggests two things worth probing in conversations with current employees: whether the "cross-functional ownership" value translates to shared accountability or shared blame when marketplace metrics miss; and whether the Lehi office operates as a true co-location hub or a hybrid default where go-to-market teams are in-office four days and engineering is remote. No named source in the available research can answer those questions. The only way to get them answered is to ask them directly: in final-round interviews, in backchannel messages to people who left six to twelve months ago, in the candid coffee chats that happen after the official process ends.
Who Lasts, Who Leaves
The research digest contains no named Neighbor employee accounts describing burnout or thriving profiles; it supplies only general frameworks (Maslach's three burnout dimensions, Pencavel's 49-hour productivity cliff, Zeigarnik's open-loop effect) and the first-party board data showing six active Lehi roles. What follows applies those frameworks to the hiring mix Neighbor is actually running.
General research on sustainable pace shows that workers who protect peak cognitive hours for deep work and build shutdown rituals that close the cognitive loop (the "fake commute" or end-of-day notepad) maintain output past the 49-hour inflection point Pencavel identified. In a Lehi office where the commute once provided that transition buffer, the thriving profile is someone who manufactures their own buffer (spatial, temporal, and ritual) rather than expecting the organization to supply it.
The burnout profile is the inverse: a specialist who needs clear lane lines. Maslach's dimensions (emotional exhaustion, depersonalization, reduced accomplishment) accelerate when borders are permeable (email at dinner, Slack during bedtime) and recovery is passive (scrolling instead of mastery activities). The research notes that remote work often erased the structural boundaries offices provided; Neighbor's Lehi-centric postings suggest an in-office or hybrid default, which restores some boundary architecture but also concentrates the pace.
The hiring bar, inferred from the role mix, selects for operators who have already demonstrated they can run a shutdown ritual and guard deep-work blocks. The Software Engineer Intern 2027 posting signals a pipeline investment. The Head of Partnerships and Head of Local Growth roles imply scope that spans product, sales, and community.
Six roles open at once in Lehi. That hiring board is the dashboard. When the next cycle posts, the names on it will show whether the machine kept the operators it needed — or whether the pace finally outran the guardrails the values promised.
Working in frontier tech? Zero G Talent tracks the openings: see every open Neighbor role, browse frontier tech jobs, the companies hiring, and the people building the field.