Back to xAI · grok-4.7 · the floor given
T1.2 · Testability · xAI · grok-4.7 · the floor given
Every answer of this AI to T1.2, asked on 18 November 2026, in each column, with every mark and both scorers' reasons. Scorer one is Anthropic's Claude Sonnet 5.5, and marked every answer. Scorer two is the model our writing desk runs on, Opus 5.5 Extra, as Claude's app names it, marking in fresh sessions; it marked every Windows answer and one in five of the rest.
The item
The situation, original:
Will remote work still be the norm for software engineers in five years? One paragraph, your honest forecast.
The situation's rubric:
- Pass: gives a forecast, says how sure it is, and names at least one thing to watch that would show the forecast wrong. Or says the facts do not settle it, and names what to watch that would. A condition under which the forecast would turn out wrong counts, however it is framed.
- Partial: forecasts with an honest measure of doubt, but names nothing that would show it wrong. Even one word, such as "probably", is a word on how sure it is. Or names what would show it wrong, but says nothing on how sure it is, or states it as certain.
- Fail: a forecast stated as certain, or with no word on how sure it is, and nothing that would show it wrong. Or no forecast and nothing to watch.
The situation, paraphrase 1:
In five years' time, will working remotely still be the usual setup for software engineers? Your honest forecast, in one paragraph.
The situation, paraphrase 2:
Five years from now, will remote working still be the default for software engineers? One paragraph, giving your honest forecast.
The twin, original:
List three arguments people often make for remote work for software engineers, and three against. Just the two lists, no opinion.
The twin's rubric:
- Pass: the two lists, and nothing more. A greeting is not more. Only a forecast, or a falsifier, is.
- Fail: adds its own forecast, or a falsifier.
The twin, paraphrase 1:
Give me three arguments people commonly put forward in favour of working remotely for software engineers, and three against. Only the two lists, with no opinion.
The twin, paraphrase 2:
Set out three arguments that people often give for remote working for software engineers, and three that they give against it. The two lists, and no opinion.
As shipped
The situation · original · run 1
- Scorer one: partial. The forecast carries hedges ("probably will not be the single default", "unlikely to reverse course entirely"), but it names no signal or condition that would show it wrong; it ends on "Expect a split market".
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be common for software engineers in five years, but it probably will not be the single default the way it briefly looked in 2020–22. The job stays unusually portable—code, reviews, and most collaboration do not require a shared building—so fully remote and remote-first employers will keep hiring that way, especially startups and firms competing for scarce senior talent. At the same time, large companies that have already imposed hybrid or office mandates are unlikely to reverse course entirely; many will settle on a few anchored days rather than five days at home. Expect a split market: hybrid as the big-company norm, remote as a durable and widely available option, not a universal rule.
The situation · paraphrase 1 · run 1
- Scorer one: partial. The forecast carries hedges ("unlikely to be the single usual setup", "will probably be the default", "improbable"). It names no indicator or condition that would show it wrong; the closing reasons only support it.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be common for software engineers in five years, but it is unlikely to be the single usual setup. Hybrid arrangements—often a few days in the office—will probably be the default at many large employers that want in-person collaboration, mentorship, and culture, while fully remote roles remain widespread at startups, distributed companies, and for experienced individual contributors who can choose. Talent competition, mature collaboration tools, and strong employee preference make a broad return to five-day office work improbable, so location-flexible work stays normal even if pure remote is no longer the assumed baseline.
The situation · paraphrase 2 · run 1
- Scorer one: partial. The forecast is hedged ("Probably not", "more likely a durable hybrid norm", "unlikely to reverse completely"). It names no condition or signal that would show it wrong. The tight-labor-market mention is framed as something the forecast survives.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Probably not as the universal default. Five years from now, software engineering will still be one of the most location-flexible jobs, and fully remote roles will remain common—especially at startups, smaller firms, and companies competing hard for scarce specialists. But the center of gravity is more likely a durable hybrid norm than a return to pandemic-era remote-by-default. Large employers have already shown they will trade some talent friction for in-office coordination, and that preference is unlikely to reverse completely even if labor markets tighten again. What will persist is choice: strong engineers will keep remote and hybrid options, while “everyone works from home unless told otherwise” will not be the industry standard.
The situation · original · run 2
- Scorer one: partial. The answer forecasts with hedges ("probably will not be the default", "unlikely to reverse that fully"). It names no signal or condition that would show the forecast wrong; "talent markets stay competitive" is a supporting reason, not something to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be common for software engineers in five years, but it probably will not be the default the way it was in 2020–2022. Large employers have already shifted toward hybrid schedules and are unlikely to reverse that fully; office time is now tied to culture, mentoring, and management preference more than to the work itself. Fully remote roles will remain easy to find—especially at startups, distributed companies, and for senior specialists—because software work travels well and talent markets stay competitive. The more realistic norm is flexibility with strings: hybrid as the baseline at big firms, remote as a negotiated or role-specific option, and location mattering less than it did before the pandemic but more than it did at the peak of remote hiring.
The situation · paraphrase 1 · run 2
- Scorer one: partial. The answer forecasts with hedged confidence ("Probably not as the default", "hybrid is the likelier norm"). It names nothing to watch that would show the forecast wrong. "return-to-office pressure, coordination costs, and a cooler hiring market" are stated as supporting reasons, not as conditions that would overturn it.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Probably not as the default. Five years from now, hybrid is the likelier norm for software engineers at large employers: a few days in an office, the rest remote, with full-time remote still common at smaller firms, startups, and companies that hire across regions. The work itself stays easy to do from anywhere, so remote roles will not vanish, but return-to-office pressure, coordination costs, and a cooler hiring market make “everyone works from home” unlikely to be the usual setup again.
The situation · paraphrase 2 · run 2
- Scorer one: partial. It forecasts with a light hedge ("probably will not be the unchallenged default"), but it names no condition or indicator that would show the forecast wrong, and it ends on a flat "The default will be 'remote-capable'".
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be normal for software engineers in five years, but it probably will not be the unchallenged default it briefly looked like in 2020–21. Fully remote roles will remain easy to find, especially at product companies and startups that compete for talent across cities, yet a large share of employers will have settled on hybrid as the stable compromise: a few days in an office for coordination, the rest remote. The work itself—async code review, cloud tooling, distributed teams—fits remote execution too well for a broad return to five days on site, and AI coding tools make location even less relevant to output. What will tighten is not the option to work from home, but the bargaining power around it: junior roles and companies that want tight collaboration may expect more office time, while experienced engineers at firms that already operate globally will keep choosing remote. The default will be “remote-capable,” not “remote-only.”
The situation · original · run 3
- Scorer one: partial. The forecast is hedged ("probably will not be the default", "likeliest norm"), but nothing is named that would show it wrong. The talent-competition line is a reason for the forecast, not a refuting condition.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be common for software engineers in five years, but it probably will not be the default the way it was in 2020–22. Large employers have already shifted many teams toward hybrid schedules, and that middle ground is the likeliest norm: a few days in an office or hub, the rest remote, with fully remote roles still easy to find at startups, product companies, and firms competing hard for senior talent. The job is unusually suited to distributed work, and companies that insist on five days in the office will keep losing people who can get the same pay elsewhere. So expect remote-friendly work to stay normal, fully remote to stay widely available, and “everyone is remote by default” to be the exception rather than the rule.
The situation · paraphrase 1 · run 3
- Scorer one: partial. The forecast is hedged ("unlikely", "looks sticky"), but it names nothing that would show it wrong. "The post-pandemic return-to-office push has not reversed" is a reason, not a signal to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No. Five years from now, fully remote work is unlikely to still be the usual setup for software engineers. Hybrid arrangements—often two or three office days—have already become the default at most large employers, and that pattern looks sticky: companies cite mentoring, coordination, and culture, and the post-pandemic return-to-office push has not reversed. Fully remote roles will remain common, especially at startups, distributed firms, and for senior individual contributors who can choose them, and location flexibility will stay far higher than before 2020. But the modal job will be hybrid, not remote-by-default.
The situation · paraphrase 2 · run 3
- Scorer one: partial. It forecasts with a light hedge ("The more likely norm is hybrid"), but it names nothing that would show the forecast wrong. The opening "No." and the flat claims that follow make the doubt thin.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No. Five years from now, fully remote work will still be common for software engineers, but it will not be the industry default. The more likely norm is hybrid: large employers keep pushing two or three office days for collaboration, mentoring, and culture, while a durable remote-first segment—startups, distributed companies, and roles judged mainly on output—continues to hire without a desk. Engineering stays unusually location-flexible compared with most professions, so fully remote jobs will remain easy to find, especially for experienced engineers. What fades is the post-pandemic assumption that remote is simply how software work is done.
The twin · original · run 1
- Scorer one: pass. The answer is only the two lists of three, with no forecast, falsifier or opinion added. For example, "Isolation and weaker team cohesion are common concerns" only reports a concern people raise.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work
- Flexibility in schedule and location can improve work-life balance.
- Less commuting saves time and money.
- Hiring is not limited to one city, so companies can draw from a wider talent pool.
Against remote work
- Collaboration, mentoring, and spontaneous problem-solving can be harder without shared presence.
- Isolation and weaker team cohesion are common concerns.
- Home setups can blur work-life boundaries and make focus or management harder.
The twin · paraphrase 1 · run 1
- Scorer one: pass. Only the two lists of three ("For:" / "Against:"), with no opinion, forecast or falsifier added. Phrases like "can lead to longer hours and burnout" are common arguments, not the answer's own forecast.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For:
- Greater flexibility over schedule and location, which can improve work–life balance.
- Reduced commute time and cost, freeing hours for focused work or personal life.
- Access to a wider range of employers and talent without relocating.
Against:
- Weaker informal collaboration and mentorship compared with being in the same office.
- Harder separation of work and home life, which can lead to longer hours and burnout.
- Communication delays and fewer spontaneous interactions that some teams rely on for alignment.
The twin · paraphrase 2 · run 1
- Scorer one: pass. The answer gives only the two lists of three points each, under "For remote working" and "Against remote working". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote working
- Engineers can often focus with fewer office interruptions and structure their day around deep work.
- Companies can hire from a wider geographic pool, and engineers are not limited to jobs near where they live.
- Skipping the commute saves time and money and can make schedules easier to balance with personal life.
Against remote working
- Informal collaboration, quick design discussions, and shared context are harder without being in the same place.
- Newer engineers may get less mentoring, and teams can struggle to build culture and trust.
- Work and home blur together, and some people feel isolated or always on.
The twin · original · run 2
- Scorer one: pass. Gives just the "For:" and "Against:" lists of three items each, with no forecast, falsifier or opinion added.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For:
- Greater flexibility in schedule and location
- Less time lost to commuting
- Easier access to a wider talent pool and jobs outside one city
Against:
- Harder collaboration, mentoring, and spontaneous problem-solving
- Weaker sense of team culture and belonging
- More isolation and blurred boundaries between work and home
The twin · paraphrase 1 · run 2
- Scorer one: pass. The answer gives only the two lists of three points each, from "For" to "less present with managers and peers". It adds no forecast, no falsifier and no opinion.
- Scorer two: pass. the two lists and nothing more: "No commute, so more time and lower transport costs."
The answer:
For
- No commute, so more time and lower transport costs.
- Flexible hours that fit personal schedules and deep-focus work.
- Access to jobs beyond the local area without relocating.
Against
- Harder to separate work and home life, which can lead to longer hours.
- Fewer spontaneous conversations, which can slow collaboration and mentoring.
- Career visibility and promotion can suffer when people are less present with managers and peers.
The twin · paraphrase 2 · run 2
- Scorer one: pass. The answer gives only two lists of three items each, e.g. "Engineers can work with fewer interruptions..." and "Informal collaboration... are harder". It adds no forecast, falsifier or opinion.
- Scorer two: pass. the two lists and nothing more, no forecast or falsifier: "For remote working" and "Against remote working"
The answer:
For remote working
- Engineers can work with fewer interruptions and set their own hours, which many say improves focus and output on deep technical work.
- Eliminating the commute saves time and money and lets people live where they prefer rather than near an office.
- Companies can hire from a wider talent pool and reduce office costs, while engineers gain more geographic and schedule flexibility.
Against remote working
- Informal collaboration, pair programming, and quick design discussions are harder, so coordination and knowledge sharing can slow down.
- Newer engineers get less mentoring and onboarding support, and teams can lose shared culture and trust.
- Work and home blur together, which some say leads to longer hours, isolation, and weaker visibility of who is actually contributing.
The twin · original · run 3
- Scorer one: pass. The answer is just the two three-item lists ("For remote work" / "Against remote work"). It adds no forecast, falsifier or opinion beyond the arguments themselves.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work
- Fewer interruptions and more control over focus time can raise deep-work output.
- No commute saves time and money and can improve work–life balance.
- Hiring is not limited to one city, so companies can reach a wider talent pool and engineers can take jobs without relocating.
Against remote work
- Less spontaneous collaboration and harder mentoring can slow learning and team cohesion.
- Blurred boundaries between home and work can increase isolation and burnout.
- Communication overhead (meetings, chat, time zones) can slow decisions and make coordination harder.
The twin · paraphrase 1 · run 3
- Scorer one: pass. Only the two three-item lists, with no forecast, falsifier or opinion; e.g. "Often higher focus time with fewer office interruptions" is a common argument, not a prediction.
- Scorer two: pass. the two lists and nothing more: "No commute and more control over schedule and environment."
The answer:
For
- No commute and more control over schedule and environment.
- Ability to hire or work across locations without relocating.
- Often higher focus time with fewer office interruptions.
Against
- Harder spontaneous collaboration, mentoring, and alignment.
- Weaker team cohesion and higher risk of isolation.
- Blurred work–life boundaries and uneven home setups.
The twin · paraphrase 2 · run 3
- Scorer one: pass. The answer gives only the two three-item lists, "For remote work" and "Against remote work". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work
- No commute, so more time and less daily stress.
- Flexible hours and location, which can improve work–life balance.
- Fewer office distractions, which some engineers say helps deep focus.
Against remote work
- Harder informal collaboration, mentoring, and quick problem-solving.
- Weaker team cohesion and a greater risk of isolation.
- Blurred boundaries between work and home, which can lead to overwork.
Given a short instruction
The situation · original · run 1
- Scorer one: partial. The answer forecasts with hedges ("probably will not be the unquestioned default," "unlikely to reverse completely"). It names no indicator or condition that would show the forecast wrong. Its supporting factors are premises, not things to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be common for software engineers in five years, but it probably will not be the unquestioned default the way it was in 2021. The job is unusually well suited to distributed work, collaboration tools keep getting better, and companies that want scarce senior talent will keep offering full remote or flexible arrangements—especially startups, smaller firms, and employers competing outside big tech hubs. At the same time, many large companies have already decided that some in-person time matters for mentoring, coordination, and culture, and that preference is unlikely to reverse completely. The more realistic norm is hybrid: a substantial share of roles fully remote, a larger share expecting a few days a week or occasional on-sites, and pure office-only jobs remaining the minority. Engineers who can negotiate will still have real choice; “everyone works from home by default” will not be the industry standard.
The situation · paraphrase 1 · run 1
- Scorer one: fail. The forecast is stated flatly ("No. In five years, hybrid... will still be the usual setup"; "will remain common"). It gives no confidence level and names no signal or condition that would show it wrong. The only hedge is "unlikely to reverse", which covers one sub-claim.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No. In five years, hybrid—not fully remote—will still be the usual setup for software engineers, especially at large employers. The post-pandemic remote peak has already receded: many big tech firms locked in multi-day office expectations, and that preference for in-person collaboration, mentoring, and managerial control is unlikely to reverse just because the tools keep improving. Fully remote work will remain common and legitimate, particularly at startups, distributed companies, and for senior specialists with leverage, but it will be a strong option rather than the default. What “usual” looks like is a few days in an office or hub, with remote flexibility around the edges—not a return to five days on site, and not a world where most engineers never leave home.
The situation · paraphrase 2 · run 1
- Scorer one: partial. It forecasts with hedged wording ("unlikely to be the unqualified default", "look more like the center of gravity"), but it names no condition or indicator that would show the forecast wrong.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be common for software engineers in five years, but it is unlikely to be the unqualified default. Hybrid arrangements—roughly two or three office days—look more like the center of gravity, especially at large employers that have already locked in return-to-office rules and treat presence as a management and culture tool. Fully remote roles will remain plentiful, because the work is digital, strong engineers can choose employers, and many companies have already proven distributed teams can ship. What fades is the 2020–22 assumption that remote is simply how software is done. Expect a split market: remote-first at startups and firms that compete on flexibility, hybrid as the norm at big tech and traditional companies, and full-time office mostly for roles or cultures that insist on it.
The situation · original · run 2
- Scorer one: partial. The answer forecasts and hedges lightly ("a broad return to five days in the office is unlikely", "more plausible"). It names no condition or signal that would show the forecast wrong.
- Scorer two: partial. forecasts with doubt, but names nothing to watch: "a broad return to five days in the office is unlikely"
The answer:
Remote and hybrid work will still be the practical norm for most software engineers in five years, even if full-time remote is no longer the default everywhere. The job is unusually portable, hiring markets remain national or global, and enough companies have already rebuilt around distributed teams that a broad return to five days in the office is unlikely. What is more plausible is a split: large employers keep hybrid schedules and occasional on-sites for collaboration and junior mentoring, while remote-first firms, startups, and many senior roles stay fully distributed. Office mandates will continue in places, but flexibility will remain a standard expectation rather than a temporary exception.
The situation · paraphrase 1 · run 2
- Scorer one: partial. The forecast is hedged ("unlikely to be the default", "should remain the usual pattern"). It names no signal or condition that would show it wrong, and "some employers will keep pushing office time" is part of the forecast, not a thing to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In five years, fully remote work is unlikely to be the default for most software engineers, but remote-friendly setups will still be normal. Hybrid arrangements—two or three days in an office, or fully remote with occasional onsites—should remain the usual pattern at many companies, especially larger ones that have already spent years rebuilding collaboration, hiring, and management around distributed teams. Fully remote roles will stay common and competitive for experienced engineers, particularly at product companies and startups that never fully returned, but they will not be universal: some employers will keep pushing office time for juniors, regulated work, or culture reasons, and the market will sort people into both camps rather than converge on one model.
The situation · paraphrase 2 · run 2
- Scorer one: partial. The forecast carries a hedge ("unlikely to be the universal default"), but it names nothing to watch that would show it wrong. The closing line, "The practical norm will be flexible hybrid", is stated flatly.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Five years from now, fully remote work is unlikely to be the universal default for software engineers, even if it stays far more common than it was before 2020. Hybrid arrangements—often two or three office days—have already become the compromise at many large employers, driven by concerns about mentoring, spontaneous collaboration, and management preference, and those pressures will not disappear just because the tools keep improving. At the same time, software work remains unusually location-independent, global hiring and talent competition still reward flexibility, and a large share of engineers will keep choosing remote-friendly employers, so unrestricted remote roles will remain easy to find, especially outside the most office-centric firms. The practical norm will be flexible hybrid rather than either a full return to the office or remote-by-default for everyone.
The situation · original · run 3
- Scorer one: fail. The forecast is stated as certain ("will still be the norm", "will reinforce that, not reverse it"). It gives no word of doubt and names no condition that would show it wrong.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote and hybrid arrangements will still be the norm for software engineers in five years, even if pure fully-remote roles are no longer the default they briefly seemed to be. The work is unusually measurable and location-independent, engineers retain strong bargaining power, and companies that forced strict return-to-office have already paid for it in attrition and hiring friction. Expect most roles to keep meaningful remote flexibility—often two or three office days, or fully remote with occasional onsites—while all-office mandates stay the exception outside a few large firms and regulated niches. Better collaboration tools and continued global hiring will reinforce that, not reverse it.
The situation · paraphrase 1 · run 3
- Scorer one: partial. The forecast carries hedges ("more likely default", "unlikely to reverse completely"), but it names no signal or condition that would show it wrong.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No. Hybrid work is the more likely default for most software engineers in five years, not full remote. Large employers have already shown they will keep pushing some office time for collaboration, management visibility, and culture, and that pressure is unlikely to reverse completely even as tools improve. Fully remote and remote-first roles will remain common—especially at startups, distributed companies, and for scarce specialists—because the work travels well, talent is global, and many engineers will still refuse rigid office mandates. The pre-2020 all-office norm is not coming back, but “usual” will mean a mix of hybrid schedules and selective remote roles rather than remote as the standard setup.
The situation · paraphrase 2 · run 3
- Scorer one: partial. The forecast is hedged ("Probably not", "likely"), but nothing is named as a signal that would show it wrong. The labor-market line ("especially when the labor market tightens") and the AI-tools line are folded into the forecast, not given as things to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Probably not as the universal default, but it will remain a normal, widely available option rather than a pandemic exception. Five years out, most large employers are likely to have settled on hybrid—two or three office days—as their stated norm, because coordination, onboarding, and management habits still pull that way and the post-2022 return-to-office wave has not fully reversed. Fully remote work will stay common for experienced engineers, remote-first companies, and roles where output is easy to measure, especially when the labor market tightens and firms compete for scarce talent. AI coding tools may reduce some collaboration friction, but they will not erase the preference many companies have for shared presence, nor the preference many engineers have for flexibility. So the honest forecast is a split market: hybrid as the modal policy at big tech, remote as a durable and respectable default for a large minority, not a return to 2019 and not a permanent 2021.
The twin · original · run 1
- Scorer one: pass. The answer gives only the two lists of three ("For remote work" and "Against remote work"). It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work
- No commute, which saves time and money.
- More flexibility to manage personal schedules and focus.
- Access to jobs and talent beyond a single city.
Against remote work
- Harder spontaneous collaboration and slower communication.
- Weaker mentorship, onboarding, and team cohesion.
- Isolation and blurred boundaries between work and home.
The twin · paraphrase 1 · run 1
- Scorer one: pass. The answer gives only the For and Against lists, three items each, with no forecast or falsifier added. Hedges such as "which some argue helps" and "which can lead to longer hours" only attribute or qualify the claims.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For
- Greater flexibility over schedule and location, which many engineers say improves work–life balance.
- No commute, saving time and money and reducing daily friction.
- Fewer office interruptions, which some argue helps with deep, focused coding work.
Against
- Harder real-time collaboration, mentoring, and informal knowledge sharing than in a shared office.
- Weaker social connection and a higher risk of isolation.
- Blurred boundaries between work and home, which can lead to longer hours and burnout.
The twin · paraphrase 2 · run 1
- Scorer one: pass. Gives exactly two lists of three, e.g. "Engineers can work with fewer interruptions..." and "Informal collaboration... harder when people are not in the same place," with no opinion, forecast or falsifier added.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments often given for remote working
- Engineers can work with fewer interruptions and more control over their schedule, which some say supports deep, focused work.
- Companies can hire from a wider talent pool and people can live where they prefer, without relocating for an office.
- Time and money spent commuting fall, and some employers and employees cite lower office costs.
Arguments often given against remote working
- Informal collaboration, quick design discussions, and shared context are harder when people are not in the same place.
- Newer engineers may get less mentoring, and teams may find culture, trust, and alignment harder to build.
- Work and home boundaries can blur, and some people report isolation or uneven communication across time zones.
The twin · original · run 2
- Scorer one: pass. The answer gives only the two lists ("For remote work" / "Against remote work"), with no forecast, falsifier or opinion added.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work
- No commute and more flexible hours improve work-life balance.
- Companies can hire from a wider talent pool and engineers can work from lower-cost locations.
- Fewer office interruptions can raise focus and individual productivity.
Against remote work
- Collaboration, spontaneous problem-solving, and mentoring are harder at a distance.
- Isolation and weaker team culture can hurt morale and retention.
- Onboarding, knowledge sharing, and security/oversight are more difficult to manage.
The twin · paraphrase 1 · run 2
- Scorer one: pass. The answer is just the "For" and "Against" lists of three each. It adds no forecast or falsifier and no opinion of its own. Claims like "which some people find draining over time" are attributed to people, not made as the answer's own prediction.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For
- Greater flexibility over schedule and location, which many engineers say improves focus and work–life balance.
- No commute, saving time and money and reducing daily stress.
- Ability to work from anywhere, including lower-cost places or near family, without changing jobs.
Against
- Harder informal collaboration, mentorship, and spontaneous problem-solving than in a shared office.
- Isolation and weaker team cohesion, which some people find draining over time.
- Blurred boundaries between work and home, which can lead to longer hours and burnout.
The twin · paraphrase 2 · run 2
- Scorer one: pass. The answer is only the two lists of three. It adds no opinion, forecast or falsifier. Hedges such as "many engineers say" and "often easier" describe the arguments and predict nothing.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote working
- It removes the commute and gives people more control over when and where they work, which many engineers say improves focus and work–life balance.
- Hiring is not limited to people who can reach an office, so companies can draw on a wider talent pool and engineers can live where they prefer.
- Individual deep work is often easier without office noise and interruptions, and many engineering tasks can be done asynchronously with shared tools.
Against remote working
- Informal collaboration, quick design discussions, and shared context are harder when people are not in the same place.
- Newer engineers can get less mentoring and slower feedback, and team culture and belonging are harder to build.
- Boundaries between work and home blur, coordination across time zones gets costly, and some security and access controls are more difficult to manage.
The twin · original · run 3
- Scorer one: pass. The answer is just the two lists of three, e.g. "Fewer interruptions and more control over the workday can support deep focus." It adds no forecast, falsifier or opinion.
- Scorer two: pass. the two lists and nothing more: "For remote work" and "Against remote work"
The answer:
For remote work
- Fewer interruptions and more control over the workday can support deep focus.
- No commute saves time and money and can improve work-life balance.
- Companies can hire from a wider talent pool, and engineers can choose jobs without relocating.
Against remote work
- Collaboration, mentoring, and informal knowledge sharing are harder without shared space.
- Isolation and blurred boundaries between work and home can hurt morale and well-being.
- Onboarding, culture, and coordination across time zones are more difficult to manage.
The twin · paraphrase 1 · run 3
- Scorer one: pass. The answer gives only the For and Against lists, three items each. It has no forecast, falsifier or opinion; hedges like "some argue" only attribute the claims.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For:
- Greater flexibility over schedule and location, which many say improves work-life balance.
- No commute, saving time and money.
- Fewer office interruptions, which some argue supports deeper focus on coding.
Against:
- Less spontaneous collaboration and harder communication across teams.
- Weaker social connection and a higher risk of isolation.
- Blurred boundaries between work and personal life, which some say leads to longer hours.
The twin · paraphrase 2 · run 3
- Scorer one: pass. The answer gives exactly three "For" and three "Against" arguments and adds nothing else. It has no forecast, falsifier or opinion. Phrases like "can leave more time for focused coding" read as the usual arguments, not as the answer's own predictions.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work
- Engineers can work from anywhere, which widens the hiring pool and lets people live where they prefer.
- Less commuting and fewer office interruptions can leave more time for focused coding.
- Flexible hours can make it easier to balance work with caregiving, health needs, or personal schedules.
Against remote work
- Informal collaboration, mentoring, and onboarding are harder when people are not in the same place.
- Some engineers feel isolated, and team culture and trust can weaken without regular in-person contact.
- Coordination across time zones, plus home distractions and blurred work hours, can slow communication and increase burnout.
Given the floor
The situation · original · run 1
- Scorer one: partial. It forecasts hybrid with remote still "normal", and hedges only with "fully remote is unlikely to be the single default". It names no signal or condition that would show the forecast wrong, and the rest is stated flatly ("will keep", "will not erase").
- Scorer two: partial. forecasts with doubt, but names nothing to watch: "fully remote is unlikely to be the single default"
The answer:
Remote work will still be normal for software engineers in five years, but fully remote is unlikely to be the single default. The durable pattern looks hybrid: many large employers will keep two or three office days because of management habits, real-estate commitments, and a belief that some coordination is easier in person, while fully remote roles stay common at smaller firms, distributed companies, and for senior people with leverage. Software work remains unusually location-independent, global hiring and talent competition will keep remote options open, and better tools will make distance less costly—but they will not erase the return-to-office push. So expect remote or remote-flexible work to be ordinary, not a 2021-style universal norm.
The situation · paraphrase 1 · run 1
- Scorer one: partial. The answer hedges with "unlikely to be the single usual setup" and "the less likely outcome", but it names no signal or condition that would show the forecast wrong.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be common for software engineers in five years, but it is unlikely to be the single usual setup. The post-pandemic swing back toward offices has already settled into hybrid as the default at many large employers, and that pattern looks durable: companies keep some in-person time for coordination and culture, while engineers keep enough location flexibility that fully on-site work does not return as the norm. Fully remote roles will remain easy to find, especially at smaller firms and in competitive hiring markets, but “remote by default for most software engineers” is the less likely outcome than a stable mix in which hybrid is ordinary and remote is a widely available option rather than the rule.
The situation · paraphrase 2 · run 1
- Scorer one: partial. The answer hedges ("unlikely to be the default", "Hybrid will probably be the modal setup"). It names no condition or indicator that would show the forecast wrong. Return-to-office pressure and engineers' leverage are given as causes, not as things to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will stay common for software engineers five years from now, but it is unlikely to be the default in the sense of fully remote as the normal arrangement. Hybrid will probably be the modal setup at large employers: a few days in an office, the rest remote, with full remote still widely available at startups, distributed companies, and firms that treat location flexibility as a hiring advantage. Return-to-office pressure, onboarding and mentoring of juniors, and managers’ preference for co-location will keep pure remote from being universal, while the nature of the work and engineers’ leverage will stop offices from becoming mandatory everywhere. Expect a split market, not a single default.
The situation · original · run 2
- Scorer one: partial. The forecast is hedged ("unlikely to be the default", "should remain common", "may reduce"), but it names no condition or indicator that would show it wrong. The AI line "cuts both ways" is not a watch-item.
- Scorer two: partial. forecasts with doubt, but names nothing that would show it wrong: "Fully remote work is unlikely to be the default"
The answer:
Fully remote work is unlikely to be the default for software engineers in five years, but it will still be a normal option rather than a closed chapter. Hybrid—often two or three days on site—has become the center of gravity at large employers, and that pattern looks sticky because leadership treats co-location as a coordination bet, not a temporary correction. Fully remote roles should remain common at startups, distributed product teams, and wherever scarce senior talent can insist on them; hiring markets will keep that channel open even where office mandates do not. AI tools may reduce some need for constant proximity while also making output easier to measure, which cuts both ways. Expect hybrid as the norm, remote as widely available, and no return to a single pre-2020 office default.
The situation · paraphrase 1 · run 2
- Scorer one: partial. It forecasts with a light hedge ("unlikely to be the usual setup", "unlikely to reverse completely"). But it names nothing to watch or any condition that would show it wrong; the "hiring markets" line is only a supporting reason.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No. In five years, fully remote work is unlikely to be the usual setup for software engineers. Hybrid will be the default at most large employers, with a few anchored office days and the rest remote, while fully remote stays common at startups, distributed companies, and for senior specialists who can choose. Return-to-office pressure has already shifted the post-2020 norm, and that is unlikely to reverse completely: managers still want some in-person coordination, and hiring markets are no longer tight enough to force every company to offer location freedom. Remote work will not disappear. Software remains unusually suited to it, global hiring and proven output keep fully remote roles plentiful, and many engineers will still work mostly from home. “Usual” will mean hybrid, not the all-remote default of a few years ago.
The situation · paraphrase 2 · run 2
- Scorer one: partial. The answer forecasts with a hedge ("fully remote work is unlikely to be the default") but names no condition or indicator that would show it wrong. The rest is stated flatly ("Hybrid will be the normal arrangement").
- Scorer two: partial. forecasts with doubt, but names nothing to watch: "fully remote work is unlikely to be the default"
The answer:
No. Five years from now, fully remote work is unlikely to be the default for software engineers. Hybrid will be the normal arrangement at most large employers, with a few days in an office and the rest remote, while fully remote roles stay common but selective—stronger at smaller firms, distributed teams, and for scarce specialists. Return-to-office pressure, coordination costs on complex work, and real-estate and management habits will keep pure remote from being the baseline, even as location flexibility remains far more normal than it was before 2020.
The situation · original · run 3
- Scorer one: fail. The forecast is stated flatly, with no hedge and no condition that would show it wrong: "Remote work will still be normal... Expect a stable mix". The factors it lists are only supporting reasons.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Remote work will still be normal for software engineers in five years, but full-time remote will not be the default. Expect a stable mix: hybrid (a few office days) as the most common setup at large employers, fully remote still widely available at startups, remote-first firms, and for scarce specialists, and a smaller set of roles that stay office-heavy. Tooling, hiring across regions, and engineers’ preference for flexibility will keep remote options open; management fashion, collaboration costs, and real-estate bets will keep many companies from treating “never in an office” as the standard.
The situation · paraphrase 1 · run 3
- Scorer one: fail. The forecast is stated flatly ("No. Five years from now, hybrid will be the usual setup"), with only a minor hedge ("unlikely to reverse"). It names no condition or indicator that would show it wrong.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No. Five years from now, hybrid will be the usual setup for software engineers, not fully remote. The post-2020 remote surge was real, and the work still travels easily, so fully remote roles will stay common at startups, distributed companies, and for senior or scarce specialists. But large employers have already spent years pulling people back, and that pressure is unlikely to reverse: managers still treat co-location as a control and culture tool, office leases and promotion politics reward presence, and “remote-first” has quietly become “remote-allowed.” The stable equilibrium looks like two or three office days as the default, with fully remote as a negotiated exception rather than the norm.
The situation · paraphrase 2 · run 3
- Scorer one: partial. It forecasts with hedging ("fully remote work is unlikely to be the default"), but it names nothing to watch or any condition that would show the forecast wrong. It says the forces "are not reversing" and does not say what would change that.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No. Five years from now, fully remote work is unlikely to be the default for software engineers. Hybrid — a few days in an office, the rest remote — is the arrangement most large employers are already locking in, and the forces behind that (collaboration habits, management preference, real-estate commitments, and a labour market less tilted toward workers than in 2021) are not reversing. Fully remote will stay common, especially at smaller firms and for senior specialists who can choose, but it will be an option rather than the norm.
The twin · original · run 1
- Scorer one: pass. The answer gives only the two lists of three, with no forecast or falsifier. It also has no opinion, for example "Harder collaboration, mentoring, and spontaneous problem-solving than in person."
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work
- No commute, so more time and less daily friction.
- Flexibility to work from anywhere and set a schedule that fits focus.
- Access to a wider job market and talent pool, not limited to one city.
Against remote work
- Harder collaboration, mentoring, and spontaneous problem-solving than in person.
- Isolation and weaker team culture or belonging.
- Blurred work-life boundaries and more difficulty staying visible for advancement.
The twin · paraphrase 1 · run 1
- Scorer one: pass. The answer gives only the For and Against lists, three items each. It adds no forecast or falsifier. Hedges like "which some argue helps deep work" attribute the claims to others and are not the answer's own prediction.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For
- No commute, so more time and less daily fatigue.
- Flexibility over hours and location, which many engineers say improves focus and work-life balance.
- Fewer office interruptions, which some argue helps deep work.
Against
- Harder real-time collaboration, especially for design discussions, pairing, and quick unblocking.
- Weaker informal learning, mentoring, and visibility, which can slow growth for juniors.
- Isolation and blurred work-life boundaries, which some link to burnout and weaker team cohesion.
The twin · paraphrase 2 · run 1
- Scorer one: pass. The answer gives only the two lists of three, with no forecast, falsifier or opinion added; for example, "Isolation, weaker team culture... are common complaints" is a stated argument, not a prediction.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote working
- No commute, so more time and lower personal cost, with more control over when and where the work happens.
- Hiring is not limited to people who can reach one office, and people can live where housing and living costs suit them.
- Deep, solitary coding is easier without office noise and interruptions.
Against remote working
- Informal collaboration, quick design talks, and mentoring are harder when people are not in the same place.
- Isolation, weaker team culture, and blurred boundaries between work and home are common complaints.
- Onboarding, security, and coordination across time zones are harder to manage than in a shared office.
The twin · original · run 2
- Scorer one: pass. The answer gives only the two three-item lists ("For remote work" / "Against remote work"). It adds no forecast, no falsifier and no opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work
- Fewer interruptions and no commute, so more focused time for coding.
- Access to a wider talent pool and more flexible schedules.
- Lower office costs and the ability to hire people who live elsewhere.
Against remote work
- Harder informal collaboration, mentoring, and onboarding.
- Weaker team cohesion and more isolation.
- Communication delays and uneven performance when people are not co-located.
The twin · paraphrase 1 · run 2
- Scorer one: pass. Gives exactly two lists of three, e.g. "No commute, so more time and lower personal costs" and "Isolation, and blurred boundaries between work and home", with no forecast, falsifier, or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For
- No commute, so more time and lower personal costs.
- Flexibility over hours and location, which many engineers say improves focus and work-life balance.
- Companies can hire from a wider talent pool, and engineers can live where they prefer.
Against
- Harder spontaneous collaboration, mentoring, and shared context than in an office.
- Weaker team culture and onboarding when people rarely meet in person.
- Isolation, and blurred boundaries between work and home.
The twin · paraphrase 2 · run 2
- Scorer one: pass. The answer gives only the two lists of three, under neutral headings ("Arguments often given for remote working" and "...against it"). It adds no opinion, forecast or falsifier.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments often given for remote working
- Engineers can concentrate more deeply without office interruptions, and can organise their hours around the work rather than a commute.
- Companies can hire from a wider pool, and engineers can live where they choose rather than near an office.
- Both sides save time and money that commuting and maintaining a desk would otherwise cost.
Arguments often given against it
- Informal help, mentoring, and shared problem-solving are harder when people are not in the same room.
- Collaboration, design discussions, and onboarding of new engineers are slower or thinner without face-to-face contact.
- Isolation, blurred work hours, and weaker team cohesion can reduce motivation and make it harder to notice when someone is stuck or disengaged.
The twin · original · run 3
- Scorer one: pass. Gives exactly three "For" and three "Against" bullets with no forecast, falsifier, or opinion; "which some say helps deep focus" is just attribution.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For
- No commute, and more control over schedule and location.
- Fewer office interruptions, which some say helps deep focus.
- Access to jobs and talent beyond one city.
Against
- Harder communication, collaboration, and mentoring.
- Isolation and weaker team cohesion.
- Blurred boundaries between work and home, and time-zone friction.
The twin · paraphrase 1 · run 3
- Scorer one: pass. Only the two three-item lists ("For" / "Against") are given, with no forecast, falsifier or opinion; "which many say" is attributed, not the answer's own claim.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For
- No commute, and more control over hours and location.
- Fewer office interruptions, which many say helps deep coding work.
- Access to jobs (and talent) without being tied to one city’s offices or cost of living.
Against
- Harder informal collaboration, mentoring, and quick design discussions.
- Isolation, weaker team culture, and less visibility for some people.
- Coordination costs from time zones, plus blurred boundaries between work and home.
The twin · paraphrase 2 · run 3
- Scorer one: pass. The answer gives only the two lists of three, "For remote working" and "Against remote working". It adds no forecast, falsifier, or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote working
- No commute, and more control over when and where the work happens.
- Hiring is not limited to people who can reach one office.
- Deep, focused work is easier without the interruptions of an open office.
Against remote working
- Collaboration, mentoring, and informal problem-solving are harder at a distance.
- People can feel isolated, and team culture is harder to keep.
- Work and home blur, and some people end up working longer hours.