Working at Solo: Culture, Pace and Who Thrives

How Work Actually Gets Done at Solo

The Solo page on Zero G Talent’s board lists all eight advertised salaried roles as remote within the United States, but the location tag says little about who decides what happens next.

Solo’s public footprint—four listed founders, remote openings across several functions and no reporting lines in the job records—points to a founder-led team with a loose structure. That kind of arrangement can reward people who create their own momentum, but it can strain people who need explicit priorities, regular feedback and a stable chain of command.

The openings extend well beyond code, so a job title alone does not reveal how far a role’s remit reaches.

The job records are silent on the daily meeting rhythm, planning cycle, code-review process, release schedule and approval thresholds. They do not identify reporting lines, team leads or a named owner for architecture, hiring and budget. A remote location tells you where an employee works; it does not reveal how often someone checks in, how work reaches a founder or what happens when priorities collide.

Glassdoor lists 34 Solo reviews, but the available material preserves none of their text, dates or job functions. The reviews cannot fill those gaps. The evidence supports a narrower conclusion: Solo advertises remote roles across specialized functions, but no source documents the routines around their decisions.

If that apparent model leaves decisions with a small group, some of the work can shift to the employee. A hire may have to draft the brief, choose an implementation, define completion criteria and identify who can remove a blocker without waiting for a scheduled approval meeting. For a builder who wants control over method and pace, that can be an advantage. Remote work does not remove the need for process; where reporting lines are sparse, it can leave the employee responsible for supplying missing coordination.

The board identifies four founders—Scott Erickson, George Simons, Dan Larkin and Jeremy Smith—but does not say who owns technical decisions, how competing founder opinions get resolved or what authority remains during absences. If the decision path is short, it can mean quick judgment. It can also concentrate knowledge in a few people, making delays visible when one of them steps away.

The practical fit test: Is the decision path short because the work is clear, or because the work has not been made clear?

An interview should turn that uncertainty into specifics. The candidate needs to know who sets priorities and can change them after work begins, which decisions fall within the hire’s authority, and how much synchronous overlap the role requires. The same conversation should expose what happens when a brief is incomplete or two functions disagree, and how performance is assessed when roles produce different outputs.

Ask for a recent project that changed direction mid-cycle, then learn who chose the new priority, who approved the technical trade-off, where the decision was recorded and how the team learned about it. If the answers describe a stable process, the remote setup includes support for the work. If they say each part had to be chased by a founder, the job grants autonomy but leaves the employee with a heavy coordination burden.

Values and Operating Principles

A company’s coordination system has to be made explicit. The public record contains job openings and four listed founders, not a Solo manifesto. Those openings show the company hiring across several disciplines, but they do not show how founder judgment becomes shipped work.

The record also omits an employee handbook, management chart, decision rights, team rituals and a review cadence. A candidate should not read concentrated founder authority as “undefined.” Concentrating judgment in the founders does not remove the need for context, priorities or feedback. In a remote team, the company must write that context down because a vague brief cannot be repaired by a hallway conversation.

Control and speed

The Solo Founders project says AI gives a solo founder capacity that once required whole departments, while ownership and control stay concentrated and decisions can move faster. That evidence concerns solo founders in general, not Solo’s own operating model. The capacity described there belongs to the founder, not automatically to the hire. For a hire in such a structure, the path from technical feedback to a product change can be short, but only when founder direction arrives with enough context. When it does not, the employee must interpret the gap.

Operating principle: Speed works only when the team can challenge bad assumptions.

An August 4, 2026 independent YCInsight solo-founder interview guide draws on YC partner accounts and founder stories to name emotional isolation and delayed decision-making—not poor execution—as central solo-founder risks. Although it addresses founders rather than employees, the finding matters here because speed alone does not show that a decision system is healthy. A fast team still needs friction when product or technical choices are wrong, and remote work cannot assume that casual conversation will supply that friction. The guide does not establish that Solo has a formal challenge process.

The guide’s illustrative answers pair a monthly decision-log review with a customer and an outside founder who challenge assumptions; another suggests narrow, one-feature-at-a-time delivery and customer input on what not to build. These examples come from the guide, not from Solo. They offer a model for self-direction with explicit checks: make the choice, write down the reasoning, and bring both to people who can say the choice is wrong.

This standard matters most in technical work. An engineer can produce a clean implementation of the wrong priority, while a founder can mistake visible motion for progress. A decision log gives both one record to review; a customer conversation can stop work before more code gets written; a regular outside check can expose a blind spot that an internal remote team may normalize. Autonomy without review becomes self-confirmation, and self-confirmation is expensive when it determines the roadmap.

Sustainability is an operating concern

The guide treats the founder’s resilience, support network and self-awareness as factors in whether a solo company can continue. An employee does not carry the founder’s emotional load, but remote work can make workload and uncertainty harder to see. The board data contains no workload, tenure or retention figures, so it cannot establish whether Solo has a burnout problem. Still, a culture that prizes autonomy needs clear ways to surface overload. In a company, people can easily mistake silence for alignment.

Those safeguards provide a way to test the values implied by Solo’s public structure. A named way to surface overload, reverse a priority and bring outside judgment into consequential choices is evidence of a process. Without one, the employee is left to interpret ambiguity and carry the resulting risk. That process has to be visible in the hiring bar, too.

What the Hiring Bar Selects For

The board’s recent Solo postings show which roles are being advertised, not how it screens candidates. Because the listings do not identify reporting lines, the relevant test is whether a candidate can move an incomplete problem forward without waiting for a detailed brief or a chain of approvals.

A broad mandate, not a published rubric

Solo’s public role list shows which jobs it is trying to fill. It does not explain how candidates are assessed. No Solo-specific interview scorecard or published list of required traits appears in the record, and the public material cannot establish whether the company screens for a particular tool, framework or coding style.

The board sets out each opening and its listed pay band:

The spread across levels and disciplines shows the range of work the company is trying to staff. The surrounding functions can determine how much business context and cross-functional communication a technical hire must handle, even when the final deliverable is code.

The openings are specialized rather than all-purpose: creditor relations, software engineering, growth marketing, executive support and product management each have distinct functions. If a hire operates without detailed reporting lines, the behavior worth testing is how they orient the work, make smaller decisions and keep moving.

Judgment is the useful signal

Judgment test: When judgment is concentrated in a small team, the valuable signal is not whether a candidate can execute a brief. It is whether the candidate can turn an incomplete brief into a sensible decision and then own the result.

That distinction should be tested against Solo’s hiring footprint. A candidate should show that they can make day-to-day decisions without waiting for a manager while keeping those decisions visible enough for a founder to review.

Strong evidence is an example of shipped work with the decision process attached. A candidate who can explain the constraints, options considered and the reason for choosing one path reveals more than a list of tasks. The same account helps assess whether that person will keep working after the initial brief ends.

The business-facing openings offer useful test cases. A campaign launched under shifting constraints would demonstrate independent execution rather than waiting for daily check-ins. For product work, shaping an unclear request into coherent direction shows the ability to create a process where none exists. For a support hire, ask how much context is needed to represent the company without several layers of management.

What the record does not establish

A May 24, 2018 CNBC report quoted recruiter Carolyn Betts, who said the difference lies in using work to see how a candidate thinks rather than asking for a full day’s unpaid output. The report did not document a take-home assignment at Solo, and treating a general recruiting trend as Solo practice would distort the record. A well-designed work sample can expose judgment and fit; an open-ended assignment can test endurance for unpaid work instead. If Solo uses one, its value depends on the company stating what the sample is meant to reveal.

A founder-led, self-directed operating approach would favor candidates who can handle ambiguity without becoming passive. They need to propose a path, make reversible decisions, communicate the reasoning and adjust when a founder redirects priorities. Someone who does excellent work only after every task has a detailed owner, deadline and approval layer may be less able to show fit for such a model, even if that person is highly capable.

Before an interview, a candidate can prepare stronger evidence than a résumé alone. Choose one shipped project and write up the original problem, missing information, decision made, work required and result. Note what changed afterward and what you would do differently with more time. That exercise gives the team concrete evidence of the trait the operating approach rewards: self-direction that survives contact with an underspecified problem.

What Current and Former Employees Say

Even a convincing candidate account is second-hand. The sourced material contains no attributable comment from a Solo employee. Solo’s public materials list remote roles and founders, but they do not include an employee account of how much autonomy a hire has.

The available descriptions can show how work is offered, not what it feels like to do. They do not reveal whether remote staff receive useful feedback when priorities change. Those answers should come from workers.

The closest public evidence comes from a broader question about workplace performance systems. Deloitte’s March 2025 Global Human Capital Trends analysis, which combines Deloitte’s own survey with findings from Betterworks and Gallup, said managers and workers alike were deeply skeptical of performance management:

These figures do not describe Solo, so they cannot substitute for employee testimony. They do show why the missing accounts matter. In a company with a conventional management layer, a manager or formal review may catch unclear goals and weak feedback. Where a remote company’s public materials do not reveal a conventional management layer, the worker may get less help interpreting what the founder wants.

Without worker accounts, it is not possible to say whether that gap reads as freedom to one hire or missing supervision to another at Solo.

Deloitte says:

“We need to live with some kind of process. But we need to design it in a way that is cost and time effective, builds trust, and if possible, promotes personal growth and development.”
— Deloitte

For Solo, that principle cuts against treating flexibility as an absence of structure. A small team still needs clear decision rights, goals and feedback. Formal performance ratings are one tool, but removing them does not remove the need for alignment. Autonomy breaks down when nobody can tell which decision has already been made or whose judgment governs the next one.

Before accepting an offer, make that missing evidence part of the evaluation. Ask to speak with a worker inside Solo and someone who has left. The first can explain how decisions and feedback travel now; the second can show how the model felt over time and whether leadership acknowledged problems. Compare their answers rather than listening for rehearsed praise. If the company cannot provide access or cannot answer consistently, treat that uncertainty as information about the culture. Until those accounts exist, Solo’s advertised remote model is an untested proposition, not a proven employee benefit.

Who Thrives Here and Who Burns Out

Solo’s eight remote postings describe where the work is done, not how much direction a hire receives. The public record contains no Solo burnout data, so the profiles below describe fit risks for a founder-led model rather than measured outcomes at Solo.

Autonomy and shared control are not the same thing here. The board does not say who sets the roadmap or grants latitude. If those decisions sit with the founders, a hire may have wide control over method while the roadmap remains elsewhere. That split can give a self-directed person room to move, while leaving someone who relies on regular coaching without a dependable way to get oriented.

The self-starting builder

The self-starting builder treats an undefined task as a problem to shape, not a reason to wait. Given a broad objective, the work calls for forming a hypothesis, identifying the next useful piece and creating enough structure for other people to follow. If a founder changes direction, the builder can revise the plan without treating the change as a personal affront. That ability to move from instruction to action matters most in the job.

Remote work can leave stalled tasks and open questions on the remote hire to repair. A nearby manager might notice them; a remote employee often cannot. Short written updates, explicit assumptions and clear requests for decisions become part of the work. The goal is not constant reporting. It is making progress legible without waiting for someone to notice.

Because the role mix spans technical, commercial and operational functions, candidates comfortable moving between those questions have more room to contribute, while people who need a stable specialty boundary may find the work less comfortable.

There is also a trap for capable self-starters. Because they can fill gaps, they may end up carrying every gap. Saying yes to unclear work can feel like competence while quietly adding invisible load. Healthy autonomy requires a person to set limits, state when a priority has changed and ask for the next priority in writing. A builder who never signals that the workload is full is not showing resilience; they are accumulating burnout risk.

The person who needs rails

The person who needs rails wants to know what success means, who owns each decision, how feedback will arrive and what happens when dependencies move. They do better with clear priorities, regular manager coaching and a defined way to escalate. These are work-style needs, not signs of weakness. The problem is that a system built around self-direction can leave those needs unmet without making that expectation explicit.

When priorities remain unspoken, silence can look like a lack of direction; delayed work can look like weak execution. That gap can appear as disengagement before anyone calls it burnout. A candidate whose development depends on close mentorship may strain in a model that selects for self-direction rather than operating as a guided apprenticeship. A candidate can build feedback loops instead of waiting for one to appear.

Control is another source of strain. A founder-led structure can give someone a deadline while reserving the right to change the target. If that person has responsibility without matching authority, repeated changes can become exhausting. They may still deliver, but they have no clear way to renegotiate the work. A candidate who can execute a well-reasoned decision without owning every decision will adapt better than someone whose motivation depends on control.

Test that profile against the actual process, not the personality label. Ask how the company handled a recent priority reversal. A clear answer identifies who reset the work and how affected deadlines changed. A vague answer points to where the burden landed.

The blank space in a brief is the test. A self-starting builder can turn it into a plan; for someone who needs rails, it must be filled by someone else. At Solo, the line between autonomy and abandonment will be the company’s willingness to put priorities in writing before the work starts.

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