Most companies debate remote vs. in-office — the ones winning treat them as complementary tools, each assigned to the work it does best.
Fraction runs a 50% remote team. That is not the result of a policy debate — it is the result of being deliberate about which work happens where, and for whom. The hybrid model works when companies stop treating it as a compromise and start treating it as a system.
Hybrid work means different things to different companies. Some split by day of the week — everyone in Tuesday through Thursday. Others split by role — senior engineers remote, junior staff in-office. Others let individuals choose, which sounds flexible but often produces inequity: employees who show up get visibility, employees who stay home get overlooked.
Hybrid work model: a structured arrangement in which employees divide their time between remote and in-office work, with the split designed around the specific demands of each role, the career stage of the employee, and the type of work being done — rather than an arbitrary schedule applied uniformly across the team.
The common thread in models that actually work is intentionality. The question is not “how many days in-office?” — it is “what genuinely requires physical proximity, and what is better done without it?” In-person interaction has real advantages: spontaneous problem-solving, mentorship through observation, the social glue that holds culture together. Remote work has real advantages too: deep focus, access to a wider talent pool, and the autonomy that drives high performers.
The companies that treat those advantages as mutually exclusive are the ones struggling. The companies designing around both — assigning the right work to the right environment — are the ones building durable teams.
Senior employees thrive remotely because knowledge work requires uninterrupted focus, and the modern office is not built for uninterrupted focus. Open floor plans, impromptu meetings, and social noise are antithetical to the sustained concentration that deep technical and strategic work demands.
A senior engineer architecting a system, a senior marketer building a campaign strategy, a senior product manager writing a PRD — all of these benefit from quiet, control over their environment, and the ability to structure their day around their own cognitive rhythms. A home office or a self-selected remote setting delivers that. A shared office rarely does.
Beyond focus, remote work for senior staff signals trust. High performers with options — and senior people reliably have options — will leave organizations that demand presence as proof of effort. Managing remote development teams effectively means extending the same professional trust to remote engineers that you extend to in-office ones: evaluate the work, not the location.
Fraction’s approach reflects this. Senior fractional engineers, designers, and growth operators work embedded in client companies without being physically co-located. What makes them effective is not proximity — it is clear deliverables, strong communication norms, and the professional experience to execute independently.
Fraction does not hire junior employees for fully remote fractional roles. That is a deliberate policy, not a bias toward in-person work. The reasoning is developmental: junior employees learn differently than senior employees, and the learning that matters most at early career stages is nearly impossible to replicate asynchronously.
What in-office time gives junior employees that remote work cannot:
The in-office investment for junior employees pays dividends not just for the individual but for the organization: teams with strong mentorship cultures produce better senior employees five years later.
The worst response to hybrid work is introducing productivity monitoring — screenshot software, activity trackers, login timestamps. These tools destroy trust, produce gaming behavior, and measure the wrong things entirely. They are the management equivalent of equating presence with performance, just in digital form.
Outcome-based measurement is the alternative. It asks: what did this person produce, and was it good? That requires being explicit about what good looks like before the work starts — not after.
| Dimension | Presence-based measurement | Outcome-based measurement |
|---|---|---|
| What is tracked | Hours online, login times, office attendance | Deliverables, milestones, quality of output |
| Employee response | Gaming behavior, visible busyness, resentment | Ownership, efficiency, autonomy |
| Effect on hiring | Repels high performers with options | Attracts high performers who value trust |
| Management overhead | Low setup, high noise signal | High setup (clear specs), low noise |
| Works for remote? | Poorly — requires physical presence proxies | Yes — location-agnostic by design |
Implementing outcome-based measurement in a hybrid team means investing in clarity upfront: defining what a sprint, a quarter, or a project looks like when it succeeds. That investment pays back in reduced management overhead, higher employee satisfaction, and the ability to catch underperformance on substance rather than on optics.
Fraction places senior engineers, designers, and growth marketers who work embedded in your team — remote, outcome-driven, and available faster than a full-time hire.
Book an Intro CallNo lock-in. 7-day risk-free start.
Two failure modes account for most hybrid dysfunction, and they sit at opposite ends of the same spectrum.
Presence bias. This is the manager who — consciously or not — favors the employees they see every day. Remote workers get fewer stretch assignments, are left out of informal decisions made in hallways, and receive less candid feedback because the relationship never deepens. Over time, remote employees feel second-class, and the best ones leave. Presence bias is not always intentional, but it is always damaging.
Remote neglect. This is the opposite failure: going hybrid without the infrastructure to support it. No documented norms around response times. No asynchronous-first communication culture. Meetings scheduled with no agenda that could have been an email. Remote employees feel disconnected not because of malice but because the team never built the scaffolding that makes distributed work functional.
Both failures stem from treating hybrid as a location policy rather than a work design. The fix is not a new policy — it is a different operating model: clear expectations, equitable visibility, and communication norms that work equally well whether someone is in the office or not. Effective communication practices that reduce rework and iterations are foundational to hybrid success, not a nice-to-have.
The manager who navigates this well has internalized one rule: judge the work, not the location. Everything else — the cadences, the tools, the norms — follows from that principle.
Full in-office mandates are a talent filter — and not always in the direction founders intend. They exclude candidates who cannot or will not relocate: experienced engineers in markets where your office isn’t located, senior operators with family constraints that make commuting impractical, and high performers in lower cost-of-living regions who have no reason to move to an expensive city when remote roles are available elsewhere.
Hybrid removes that filter for the roles where physical presence isn’t load-bearing. A senior engineer contributing to your codebase from a different city is producing the same output as one sitting in your office. A senior growth marketer running experiments from home is running the same experiments. Forcing them to relocate or commute is not adding value — it is subtracting candidates from your pool without a corresponding gain.
For startups competing with large companies that offer higher base salaries, the ability to recruit remotely is a genuine advantage. A candidate choosing between a Google offer and a startup offer may choose the startup if the startup offers more flexibility, more meaningful work, and more direct impact — but only if the startup is actually organized to support remote employees, not just theoretically open to it. Building the right PTO and team policies for your startup is part of the same package: flexible work without coherent people ops is a half-measure that sophisticated candidates will see through.
Adaptability is the competitive edge. Fraction’s hybrid model demonstrates that companies don’t have to choose between talent density and talent diversity — they can design for both, deliberately.
Praveen Ghanta is a five-time founder and serial entrepreneur. He is the founder of DevHawk.ai, an AI-powered engineering management platform, and Fraction.work, which connects fast-growing companies with top fractional tech and growth marketing talent. Previously, he founded HiddenLevers, a risk analytics platform for wealth management that he bootstrapped from inception to acquisition by Orion Advisor Solutions in 2021, serving thousands of advisors and $600B in assets. He earlier founded SmartWorkGroups, acquired by Intralinks in 2000.
Connect on LinkedIn →Describe your software or AI project. Get a full scope with story-point pricing, sprint estimates, and a downloadable plan in minutes. No calls, no waiting.
Scope Your Project for FreeWorking on a data strategy? Talk to a Fraction CTO. → Book an intro call