Back to Meta · muse-wonder-1.0 · the floor given
T1.2 · Testability · Meta · muse-wonder-1.0 · the floor given
Every answer of this AI to T1.2, asked on 15 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. It gives a forecast ("hybrid will be" dominant) and a slight hedge ("looks unlikely"). It names nothing that would show the forecast wrong, and the stated reasons ("tooling and hiring are now entrenched") are not signals to watch.
- Scorer two: partial. a forecast with a measure of doubt ("A universal return to five days in-office looks unlikely"), but it names nothing that would show it wrong.
The answer:
My honest forecast is that five years from now, working from home will still be normal for software engineers, but fully remote will not be the dominant model — hybrid will be. Most large tech and finance firms will expect two or three days a week in an office for collaboration, mentoring, and culture, while a durable minority of jobs at startups, remote-first companies, and for senior specialists will remain entirely remote, often hiring across countries. A universal return to five days in-office looks unlikely because distributed tooling and hiring are now entrenched and flexibility remains a powerful recruiting lever, but the pandemic-era expectation that almost any software job can be done from anywhere indefinitely will keep fading.
The situation · paraphrase 1 · run 1
- Scorer one: fail. The forecast is stated as certain ("will not be the usual setup", "absolutely will", "will stay fully remote") with no hedge. It names nothing to watch that would show it wrong, and its reasons ("hiring advantages, real-estate savings") only support it.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
My honest forecast is that five years from now, fully remote work will not be the usual setup for most software engineers, but remote work in a broader sense absolutely will be: the modal arrangement at medium and large companies will be hybrid with two or three days a week from home, fully in-office roles will remain a minority outside a few big-tech and finance holdouts, and a substantial minority — disproportionately senior engineers, startups, open-source-driven companies, and globally distributed teams — will stay fully remote, because the hiring advantages, real-estate savings, and now deeply embedded tooling and habits make a wholesale return to pre-2020 office norms both uncompetitive and impractical.
The situation · paraphrase 2 · run 1
- Scorer one: fail. The forecast is stated flatly ("will be hybrid rather than fully remote", "you'll increasingly have to opt into it"). "I don't think so" is the only hedge, and it is not a real confidence statement. The answer names nothing to watch that would show it wrong.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
I don't think so: five years from now the default for software engineers will be hybrid rather than fully remote, with most established companies expecting two or three days a week in an office (especially for junior and mid-level engineers, where managers worry about mentorship, culture, and oversight of AI-assisted work), while fully remote remains a durable, large minority model at startups, globally distributed companies, and for senior specialists with scarce skills. In other words, remote work won't disappear—it will stay far more common than before 2020—but you'll increasingly have to opt into it by choosing a remote-first employer rather than assuming any software job can be done from anywhere.
The situation · original · run 2
- Scorer one: fail. The forecast is stated flatly ("No — in five years hybrid will be the norm... fully remote will remain a large, permanent minority"). It has no word on confidence and names no condition or signal that would show it wrong.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No — in five years hybrid will be the norm for most software engineers, not fully remote: large and mid-sized companies will mostly settle at 2-3 days in-office (driven less by productivity data than by real estate, management preference, and wanting junior engineers mentored in person as AI automates more routine coding), while fully remote will remain a large, permanent minority concentrated in startups, remote-first companies, senior/specialized roles, and engineers living outside major tech hubs, but those jobs will be more competitive to get and less likely to be the default offer.
The situation · paraphrase 1 · run 2
- Scorer one: partial. The answer forecasts with a hedge ("probably not in the fully remote sense... hybrid... will be the usual setup"). 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:
In five years, probably not in the fully remote sense that peaked in 2020–22: hybrid — typically two or three days a week from home — will be the usual setup for software engineers at most mid-to-large companies, with in-office time justified by collaboration, mentorship, and managerial control, while fully remote roles remain a substantial, durable minority concentrated in distributed startups, smaller firms, senior or specialist positions, and companies hiring globally for talent or cost, so remote work will not disappear but will shift from the default expectation to one segment of the market and a negotiated advantage rather than the industry norm.
The situation · paraphrase 2 · run 2
- Scorer one: fail. The forecast is stated flatly ("will be the default", "too entrenched to reverse", "will be over") with no word on how sure it is, and it names nothing that would show it wrong.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Five years from now, my honest forecast is that hybrid—not fully remote—will be the default for software engineers at most large companies, typically two or three days a week in an office for people hired near a hub, while fully remote work remains a permanent, substantial minority concentrated in startups, smaller firms, and senior or hard-to-fill roles recruited globally. Remote work will stay far more common than it was before 2020 because the tooling, cost advantages, and talent expectations are too entrenched to reverse, but the brief post-pandemic period when a new software job was simply assumed to be remote will be over, replaced by location-specific arrangements set out upfront rather than one industry-wide default.
The situation · original · run 3
- Scorer one: fail. The answer opens "Yes, in five years remote work will still be the norm" as a flat certainty. It gives no word of doubt and 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:
Yes, in five years remote work will still be the norm for software engineers, but it will look more like structured hybrid and location-tiered remote than the fully location-agnostic era of 2020-2022: large tech companies and banks will mostly settle at two to three office days for early-career and highly collaborative roles in major hubs, while startups, mid-size firms, and senior or specialist engineers remain predominantly fully remote because global hiring, retention, and cost savings still outweigh the benefits of full colocation, and better AI and async tooling will have narrowed the collaboration gap that fueled return-to-office pushes — so engineers who refuse to commute will still have many good options, but the very highest-paying big-tech jobs will increasingly require living near an office.
The situation · paraphrase 1 · run 3
- Scorer one: partial. The answer gives a forecast with a hedge ("Probably not... I expect hybrid"), but it names nothing to watch that would show the forecast wrong. Its reasons ("employers have regained enough leverage") support the forecast and are not falsifiers.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Probably not in its fully remote form: in five years I expect hybrid — typically two or three days a week at home — to be the most common setup for software engineers, with fully remote work remaining a substantial minority concentrated among senior engineers, startups, and globally distributed teams, and five-day office attendance persisting mainly at Big Tech, AI labs, and companies with security or hardware constraints. Remote work is too productive, popular, and valuable for hiring outside expensive tech hubs to disappear or return to pre-2020 rarity, but employers have regained enough leverage to enforce regular in-person time for mentoring, collaboration, and culture, so the likely equilibrium is remote as a permanent major feature of the job, just not the near-universal default it briefly appeared to become.
The situation · paraphrase 2 · run 3
- Scorer one: partial. The answer forecasts and hedges ("I expect", "likely 30-40%", "will probably still spend at least half their week remote"). It names no signal or condition that would show the forecast wrong.
- Scorer two: partial. forecasts with a word on how sure ("I expect", "likely 30-40%", "probably"), but names nothing to watch that would show it wrong.
The answer:
Five years from now, I expect fully remote will no longer be the default for software engineers, but neither will the traditional five-day office week have won: the prevailing model will be hybrid, with most established companies expecting two or three days in a local hub for design work, mentoring, and team cohesion, and enforcing location-based pay and promotion norms accordingly. A substantial minority — likely 30-40% of roles, at startups, remote-first firms, and companies hiring globally for scarce skills — will stay fully remote, and senior engineers will retain far more bargaining power to negotiate it than juniors. So software engineering will remain unusually home-based compared with other white-collar work, and most engineers will probably still spend at least half their week remote, but being able to live anywhere indefinitely will be a specific perk of particular employers rather than the industry-wide assumption it briefly became.
The twin · original · run 1
- Scorer one: pass. The answer gives exactly three arguments for and three against, with no forecast, falsifier, or opinion added. For example, it ends at "Can lead to social isolation and blurred work-life boundaries".
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote work:
- Eliminates commuting time and costs
- Allows for more flexible schedules and work locations
- Enables companies to hire from a wider geographic talent pool
Arguments against remote work:
- Reduces spontaneous in-person collaboration and communication
- Makes onboarding and mentoring more difficult
- Can lead to social isolation and blurred work-life boundaries
The twin · paraphrase 1 · run 1
- Scorer one: pass. The answer is just the two lists of three ("In favour:" and "Against:"). It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In favour:
- Eliminating the commute saves time and money and allows for a more flexible schedule.
- Fewer office interruptions can make it easier to maintain focus on complex, deep-work tasks like coding.
- Companies can hire from a wider geographic talent pool, and engineers can apply for jobs without relocating.
Against:
- Spontaneous collaboration, whiteboarding, and quick questions are harder, which can slow down problem-solving.
- Reduced social interaction with colleagues can lead to feelings of isolation and weaker team cohesion.
- Junior engineers may receive less informal mentoring and have a harder time onboarding and learning team processes.
The twin · paraphrase 2 · run 1
- Scorer one: pass. The answer gives exactly two lists of three arguments each, such as "Fewer office interruptions allows for longer periods of focused, deep work". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote working for software engineers:
- Fewer office interruptions allows for longer periods of focused, deep work on complex coding tasks.
- Eliminating the commute saves time and provides more flexibility in working hours.
- Companies can hire from a wider geographic talent pool, and engineers can live where they choose.
Arguments against remote working for software engineers:
- Spontaneous collaboration, whiteboarding, and pair programming are more difficult to replicate online.
- Mentoring, onboarding junior engineers, and building team culture can be harder without in-person interaction.
- Asynchronous communication across different locations and time zones can slow down code reviews, debugging, and decision-making.
The twin · original · run 2
- Scorer one: pass. The answer is only the two three-item lists ("For remote work" / "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:
- Eliminates commuting, saving time and money
- Allows for fewer office distractions and more focused coding time
- Enables hiring and working from a wider geographic talent pool
Against remote work:
- Reduces spontaneous collaboration and whiteboard discussions
- Makes communication slower due to reliance on async messages and scheduled calls
- Makes mentoring junior engineers and onboarding new hires more difficult
The twin · paraphrase 1 · run 2
- Scorer one: pass. The answer is just the two lists of three, with no forecast, falsifier or opinion added. Its bullets, such as "Risk of isolation, blurred work-life boundaries, and weaker team culture", stay within the arguments.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In favour:
- No commute allows more time for work and personal life, and flexibility over schedule and location
- Ability to work from a quieter environment with fewer office interruptions for focused coding
- Companies can hire from a wider geographic talent pool, and employees can live in lower-cost areas
Against:
- Less spontaneous in-person collaboration, discussion, and whiteboarding
- Harder mentoring, onboarding, and knowledge-sharing, especially for junior engineers
- Risk of isolation, blurred work-life boundaries, and weaker team culture
The twin · paraphrase 2 · run 2
- Scorer one: pass. The answer is just the two lists of three, with no forecast, falsifier or opinion added. For example, it ends with "difficulty separating work from home life" and says nothing more.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote working for software engineers
- No commute, which saves time and money.
- Fewer office interruptions, allowing longer periods of focused coding.
- Flexibility over location and working hours, and access to jobs beyond the local area.
Arguments against remote working for software engineers
- Less spontaneous collaboration, such as quick questions, whiteboarding, and pair programming.
- Communication can be slower or more prone to misunderstanding when done asynchronously.
- Isolation from colleagues, harder mentoring of junior engineers, and difficulty separating work from home life.
The twin · original · run 3
- Scorer one: pass. The answer is just two lists of three neutral items each, such as "Onboarding and mentoring junior engineers can be slower". 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:
- Fewer office distractions can allow for longer periods of focused coding
- Eliminating a commute saves time and can improve work-life balance
- Companies can hire software engineers from a wider geographic talent pool
Against remote work:
- Spontaneous collaboration, whiteboarding, and pair programming can be more difficult
- Onboarding and mentoring junior engineers can be slower
- Time zone differences and asynchronous communication can delay feedback
The twin · paraphrase 1 · run 3
- Scorer one: pass. The answer is just the two lists of three, with no forecast, falsifier or opinion added. Examples are "Eliminates commuting, saving time and money" and "Can lead to isolation and less informal mentoring for junior engineers".
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In favour:
- Eliminates commuting, saving time and money
- Allows greater flexibility in schedule and work location
- Provides fewer office interruptions for focused coding work
Against:
- Reduces spontaneous in-person collaboration and discussion
- Can slow communication and increase misunderstandings, especially across time zones
- Can lead to isolation and less informal mentoring for junior engineers
The twin · paraphrase 2 · run 3
- Scorer one: pass. The answer gives only the two lists of three ("Arguments for..." and "Arguments against..."). It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote working for software engineers:
- No commute, saving time and money and allowing more flexible working hours.
- Fewer office interruptions, making it easier to maintain focus for extended coding tasks.
- Access to jobs and talent pools regardless of geographic location.
Arguments against remote working for software engineers:
- Spontaneous collaboration, pair programming, and quickly resolving blockers can be harder over chat and video calls.
- Onboarding and mentoring junior engineers is more difficult without in-person observation and informal help.
- Isolation, weaker team cohesion, and blurred work-life boundaries at home.
Given a short instruction
The situation · original · run 1
- Scorer one: partial. The answer forecasts and hedges with "will likely be" hybrid, but it names nothing to watch 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 remain common for software engineers in five years, but it won't be the universal norm it was at its pandemic peak — the dominant model will likely be hybrid (2-3 days in office) at large tech companies and fully remote at many smaller, remote-first firms, startups, and for senior/specialized roles where companies compete globally for talent.
The situation · paraphrase 1 · run 1
- Scorer one: partial. The forecast is hedged ("will likely be hybrid"), but it names no condition or indicator that would show it wrong. "employers currently hold more leverage" is a premise, not a thing to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
My honest forecast is that in five years, fully remote work will not be the usual setup for most software engineers, but working from home part of the week will be: the modal arrangement—especially at large employers—will likely be hybrid, around two to three days in the office, because management pressure for in-person collaboration, mentoring, and control has proven durable and employers currently hold more leverage, yet fully remote roles will remain a substantial minority concentrated among startups, distributed companies, contractors, and senior or hard-to-fill specialists, and offering at least some remote days will remain too important for recruitment and retention for most firms to return to five days in the office.
The situation · paraphrase 2 · run 1
- Scorer one: partial. The answer hedges its forecast ("I expect", "probably", "seems unlikely"). But it names no signal or condition that would show it wrong. It only lists supporting reasons: "the work is digital, hiring is global, and experienced engineers strongly prefer flexibility".
- Scorer two: partial. forecasts with a word on how sure ("I expect", "probably", "seems unlikely"), but names nothing to watch that would show it wrong; the reasons "have not gone away" are given as support, not as a condition.
The answer:
Five years from now, I expect remote work will still be the default for software engineers, but in a more hybrid and geographically uneven form than in the early 2020s: the typical role at a large company will probably be home-based most of the week with one to three required office days or regular on-site gatherings, many startups and smaller firms will remain fully remote to compete for talent, and fully in-office jobs will persist — especially in parts of Asia, finance, defense, and some Big Tech teams — but will remain the exception rather than the rule; the underlying reasons remote work took hold, that the work is digital, hiring is global, and experienced engineers strongly prefer flexibility, have not gone away, so while employers will keep reclaiming some in-person time, a return to five-days-in-the-office as the industry standard seems unlikely.
The situation · original · run 2
- Scorer one: partial. It gives a clear forecast with a thin hedge ("a wholesale return to pre-2020 norms is unlikely"). It names nothing that would show the forecast wrong, and the rest is stated assertively ("will mostly settle", "will keep the strongest remote options").
- Scorer two: partial. a forecast with a word of doubt ("a wholesale return to pre-2020 norms is unlikely"), but nothing named that would show it wrong: "large companies will mostly settle into two-to-three-day hybrid routines"
The answer:
My honest forecast is that in five years most software engineers still won’t be in an office five days a week, but fully remote-by-default will no longer be the dominant model either: large companies will mostly settle into two-to-three-day hybrid routines for employees near offices, driven by concerns about mentoring, collaboration, and culture, while startups, smaller firms, and globally distributed teams remain remote-first because they can’t compete on salary or office perks and benefit too much from wider hiring and lower costs to give that up. The pandemic proved remote engineering works and the tooling and async habits are now entrenched, so a wholesale return to pre-2020 norms is unlikely, but employer leverage has grown since the pandemic hiring boom, so senior and specialized engineers will keep the strongest remote options while junior roles become more office-heavy, making “remote” less work-from-anywhere and more a permanent split between hybrid and genuinely distributed work.
The situation · paraphrase 1 · run 2
- Scorer one: partial. The answer hedges with "I think" and "will probably expect", but it names no condition or indicator that would show the forecast wrong. Its "because... competition for experienced engineers, global hiring" is a reason, not a thing to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In five years, I think working remotely will still be the usual setup for software engineers, but it will more often mean hybrid than fully remote: most medium and large employers will probably expect two or three days a week in the office, especially for junior staff, planning, and team collaboration, while fully remote roles will remain a large, competitive minority at distributed-first companies, startups, and for senior or specialized engineers. Fully in-office roles are likely to stay in the minority in North America and much of Europe—though more common in parts of Asia and in finance, defense, and some big tech firms—because although the return-to-office push will not disappear, competition for experienced engineers, global hiring, and the proven viability of doing focused development work from home will make substantial remote flexibility hard for most employers to abandon.
The situation · paraphrase 2 · run 2
- Scorer one: partial. The forecast is hedged ("likely", "perhaps", "probably"), but it names no signal or condition that would show it wrong. It only gives reasons for the forecast, such as "global talent and cost advantages are too large to abandon".
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Five years from now, I don't think fully remote work will still be the default for most software engineers, but neither will five days in the office: hybrid schedules of two to three office days will likely be the norm at large and mid-sized companies that have offices, driven by employers' preferences for in-person mentoring, collaboration, and oversight, while a substantial minority — perhaps a quarter to a third of roles, especially at startups, remote-first firms, and for senior specialists hired across borders — will stay fully remote because the global talent and cost advantages are too large to abandon; in short, remote will remain a common and accepted option in software, unusually so compared with other professions, but the pandemic-era assumption that a new job is remote unless stated otherwise will probably have been replaced by an assumption of hybrid unless stated otherwise.
The situation · original · run 3
- Scorer one: fail. The main forecast is stated flatly: "in five years most software engineers will still spend the majority of their week working from home". "Likely" appears only on a side claim about early-career engineers. The answer names nothing that would show the forecast wrong. The recruiting-disadvantage line is a reason for the forecast, not something to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
My honest forecast is yes, but in a more settled, hybrid-heavy form than the fully remote peak of 2020-2022: in five years most software engineers will still spend the majority of their week working from home, because remote hiring widens the talent pool, reduces office costs, and is now baked into how teams use async tools, code review, and distributed on-call, while the big-company return-to-office push will mostly stabilize at two or three in-office days for hub-based teams rather than a full five-day reversal, since forcing full attendance would put those firms at a recruiting disadvantage against remote-first startups and mid-size companies; early-career engineers and teams doing heavy product or hardware work will likely be the most office-present for mentoring and collaboration, but five days in an office will be the exception, not the norm, for experienced engineers.
The situation · paraphrase 1 · run 3
- Scorer one: partial. The answer gives a forecast with light hedging ("I expect", "will likely vary"). It names nothing that would show the forecast wrong. It lists drivers such as "large employers have steadily pushed return-to-office policies" but gives no indicator or condition to watch.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In five years, I expect working remotely to still be the usual setup for software engineers in the broad sense that most will not be in an office five days a week, but the typical arrangement will be hybrid — two or three days at home — rather than the fully remote default of 2020-22, since large employers have steadily pushed return-to-office policies and tied them to promotions, team placement, and new-hire location, while startups, smaller companies, fully distributed firms, and employers hiring senior or hard-to-find specialists across borders will keep offering fully remote roles to compete for talent; the result will likely vary a lot by company size, seniority, and country, but remote work will remain entrenched and far more common than before the pandemic, just no longer assumed.
The situation · paraphrase 2 · run 3
- Scorer one: partial. It forecasts with a light hedge ("I don't think... my honest forecast is"), but it names no condition or indicator that would show the forecast wrong. The rest is stated flatly: "hybrid will be the standard."
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Five years from now, I don't think fully remote work will still be the default for software engineers, but it will remain far more common than before the pandemic: my honest forecast is that hybrid will be the standard arrangement at most large and mid-sized companies — typically two or three days a week in an office for people who live near one, with fully remote exceptions for senior specialists and distributed teams — while a substantial minority of startups and smaller firms stay remote-first to hire globally and save on offices, meaning remote jobs will be a normal, permanent part of the market rather than an assumed entitlement for every role.
The twin · original · run 1
- Scorer one: pass. The answer is just the two lists of three, e.g. "Eliminates commuting, saving time and money…". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote work for software engineers:
- Eliminates commuting, saving time and money and allowing more flexible schedules.
- Provides a quieter, customizable environment that can support deep focus on coding tasks.
- Allows companies to hire from a wider geographic talent pool and employees to live where they prefer.
Arguments against remote work for software engineers:
- Makes spontaneous collaboration, whiteboarding, and quick problem-solving more difficult.
- Can reduce mentoring opportunities and make onboarding junior engineers harder.
- Can lead to feelings of isolation and weaken team culture and informal communication.
The twin · paraphrase 1 · run 1
- Scorer one: pass. Only the two lists of three are given ("In favour:" and "Against:"), with no forecast, falsifier or opinion added.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In favour:
- Eliminates commuting, providing more time, flexibility, and cost savings
- Allows engineers to apply for jobs regardless of location, and employers to hire from a wider talent pool
- Provides a customisable work environment with fewer office interruptions for focused tasks
Against:
- Makes spontaneous collaboration, quick questions, and informal problem-solving more difficult
- Makes onboarding, mentoring, and building team culture more difficult
- Can cause social isolation and blur boundaries between work and home life
The twin · paraphrase 2 · run 1
- Scorer one: pass. The answer gives only the two lists of three arguments each, e.g. "Eliminating the commute saves time and money". It adds no forecast, falsifier or opinion.
- Scorer two: pass. the two lists and nothing more: "Arguments people give for remote working… Arguments people give against remote working", with no forecast or falsifier.
The answer:
Arguments people give for remote working for software engineers
- Eliminating the commute saves time and money, and allows more flexibility in working hours and location.
- Fewer office distractions and a personalised work environment can allow for longer periods of focused coding.
- Companies can hire from a wider geographical talent pool, and employees can apply for jobs not limited to where they live.
Arguments people give against remote working for software engineers
- Spontaneous collaboration, pair programming, and quick problem-solving discussions are harder to replicate online.
- Onboarding and mentoring junior engineers is more difficult without in-person observation and informal learning.
- Working from home can lead to social isolation, weaker team cohesion, and blurred boundaries between work and home life.
The twin · original · run 2
- Scorer one: pass. The answer is two lists of three bullets each, with no forecast, falsifier or opinion added. Example: "Reduces spontaneous collaboration and informal problem-solving" is simply a listed argument.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote work:
- Eliminates commuting, saving time and money and improving work-life balance
- Allows companies to hire from a wider, geographically diverse talent pool
- Reduces office distractions, enabling longer periods of focused coding
Arguments against remote work:
- Reduces spontaneous collaboration and informal problem-solving
- Can cause communication delays and misunderstandings, especially across time zones
- Makes onboarding, mentoring, and building team culture more difficult
The twin · paraphrase 1 · run 2
- Scorer one: pass. The answer is just the two lists of three, "Arguments in favour" and "Arguments against". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments in favour:
- Eliminating the commute saves time and money and reduces stress
- A flexible schedule and a personalised workspace can improve focus and productivity
- Companies and employees are not limited by geography when hiring or looking for jobs
Arguments against:
- Less spontaneous collaboration can make brainstorming, pair programming, and quick problem-solving harder
- Reduced in-person contact can lead to isolation and make mentoring and onboarding more difficult
- Distractions at home and blurred work-life boundaries can reduce productivity
The twin · paraphrase 2 · run 2
- Scorer one: pass. The answer gives only the two lists of three arguments each, such as "No commute and a flexible schedule..." and "Working from home can lead to isolation...". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote working for software engineers:
- No commute and a flexible schedule allow more time and control over work-life balance.
- A quiet home environment can provide longer periods of uninterrupted focus for coding and debugging.
- Companies can hire from a wider geographic talent pool, and employees can live where they choose.
Arguments against remote working for software engineers:
- Collaboration on design, pair programming, and problem-solving can be harder without in-person, spontaneous discussion.
- Mentoring and onboarding junior engineers can be more difficult remotely.
- Working from home can lead to isolation and weaker team cohesion.
The twin · original · run 3
- Scorer one: pass. The answer is just the two three-item lists ("Arguments often made for remote work" and "...against remote work"). It has no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments often made for remote work:
- No commute gives engineers more time and energy for work and personal life
- Fewer office interruptions can allow longer periods of focused coding
- Companies can hire from a wider talent pool, and engineers can live where they prefer
Arguments often made against remote work:
- Spontaneous collaboration and quick questions are harder without being in the same room
- Junior engineers may receive less informal mentorship and onboarding support
- Distractions at home and social isolation can affect communication and morale
The twin · paraphrase 1 · run 3
- Scorer one: pass. The answer gives only the two lists of three, such as "Eliminating a commute saves time and money" and "Spontaneous collaboration... can be harder". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments in favour:
- Eliminating a commute saves time and money and can improve work-life balance.
- A quieter, personalised workspace can allow longer periods of uninterrupted focus for coding.
- Engineers can apply for jobs and live in locations not limited by proximity to an office.
Arguments against:
- Spontaneous collaboration, brainstorming, and mentoring can be harder without in-person interaction.
- Working from home can lead to social isolation and blurred boundaries between work and personal life.
- Home distractions, equipment or connectivity issues, and data security concerns can create challenges.
The twin · paraphrase 2 · run 3
- Scorer one: pass. The answer gives only the two headed lists of three arguments each. It adds no forecast, falsifier or opinion, for example "Communication and collaboration can be slower or harder" is stated as an argument people give.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments people give for remote working for software engineers
- No commute and greater flexibility over working hours and location, which can improve work-life balance.
- Fewer office interruptions and a personally controlled environment, allowing for longer periods of focused coding.
- Access to jobs and talent regardless of geography, plus cost savings on commuting and office space.
Arguments people give against remote working for software engineers
- Communication and collaboration can be slower or harder, particularly for spontaneous discussions, pair programming, and problem-solving.
- Onboarding, mentoring of junior engineers, and building team culture can be more difficult without in-person contact.
- Risks of isolation, blurred work-home boundaries, home distractions, and complications with equipment, security, and supervision.
Given the floor
The situation · original · run 1
- Scorer one: pass. The answer forecasts hybrid as the norm with remote a minority, hedged with "will likely be" and "I would guess roughly a quarter to a third". It names what would prove it wrong: "sustained majority" or "below roughly 15%".
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
My honest forecast is that in five years fully remote work will be a large, stable minority for software engineers rather than the norm: the modal job will likely be hybrid or remote-flexible, because employers keep pushing office time for mentoring, coordination, and control, while global hiring, mature tooling, and engineers' preference for flexibility prevent a full return to office-first work. I would guess roughly a quarter to a third of roles remain fully remote, concentrated among senior engineers, smaller companies, and internationally distributed teams. This would be proved wrong if fully remote roles again became a sustained majority of software-engineering jobs, or if they fell to a small niche below roughly 15%.
The situation · paraphrase 1 · run 1
- Scorer one: pass. It forecasts hybrid as the usual setup, gives "about 60–65% confidence", and names a refuting condition: "a sustained return to majority fully-remote postings would prove this forecast wrong."
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
No — in five years I expect hybrid, not fully remote, to be the usual setup for software engineers: most mid-to-large employers will likely require two or three office days while preserving substantial remote flexibility, and fully remote roles will remain a significant minority, concentrated at distributed-first firms and among senior or specialist engineers, rather than disappearing. The remote tooling and wider hiring pools make a complete return to office unlikely, but employer preferences for in-person coordination, management oversight, and existing office commitments are already reversing pure-remote defaults; I’d put about 60–65% confidence on hybrid being modal, and a sustained return to majority fully-remote postings would prove this forecast wrong.
The situation · paraphrase 2 · run 1
- Scorer one: pass. It forecasts ("I do not expect fully remote work to be the default... I expect hybrid work to be the norm"). The hedged "I expect" framing is not stated as certain. It names a falsifier: "proved wrong if by 2031 most... roles either required at least four days a week in an office or were offered as fully remote by default."
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Five years from now, I do not expect fully remote work to be the default for software engineers; I expect hybrid work to be the norm at most large employers—typically two or three days remote each week—while fully remote remains common at smaller, distributed, and highly specialised firms, because employers continue to value in-person mentoring and coordination, but competition for experienced engineers, global hiring, and mature remote tooling make a universal return to five-day office work costly. This forecast would be proved wrong if by 2031 most software-engineering roles either required at least four days a week in an office or were offered as fully remote by default.
The situation · original · run 2
- Scorer one: partial. The answer hedges ("I expect", "will likely be", "plausibly a quarter to a third"). It names no signal or condition that would show the forecast wrong. Its "because the tooling and talent-market pressure for remote persist" clause only gives reasons.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In five years, I expect fully remote work to remain common but no longer be the default norm for software engineers: hybrid arrangements will likely be the most typical pattern at larger employers, while a substantial minority of roles — plausibly a quarter to a third, concentrated at smaller, distributed, and global companies — stay fully remote, well above pre-2020 levels but short of the pandemic-era peak, because the tooling and talent-market pressure for remote persist even as firms keep pulling toward in-office collaboration.
The situation · paraphrase 1 · run 2
- Scorer one: pass. It forecasts hybrid as the norm with fully remote at 25–33%. It hedges with "probably" and "unlikely". It names a refuting condition: "hiring data in 2031 showed most software-engineering roles were again advertised as fully remote."
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
My honest forecast is no: in five years, fully remote will probably not be the usual setup for software engineers, but hybrid will be — roughly two to three in-office days where an employer has an office, with fully remote remaining a durable minority, perhaps a quarter to a third of roles, concentrated in distributed-first firms, senior positions, and scarce specialisms. Employer pressure for in-person collaboration and management control is unlikely to disappear, while remote tooling, office costs, and competition for experienced engineers make a universal five-day return equally unlikely; I would be proved wrong if hiring data in 2031 showed most software-engineering roles were again advertised as fully remote.
The situation · paraphrase 2 · run 2
- Scorer one: pass. It forecasts hybrid as the modal arrangement, hedges with "I do not expect" and "I expect", and names a falsifier: "I would be wrong if representative 2031 job-posting and attendance data show fully remote... as the majority arrangement." Its confidence wording is mild.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Five years from now, I do not expect fully remote work to be the default for software engineers: I expect hybrid — typically two or three days in an office where one exists — to be the modal arrangement at large employers, with fully remote remaining a large, stable minority at remote-first firms, startups, contract roles, and globally distributed teams, because remote coding works well enough that it will not disappear, but employers continue to value co-location for coordination, mentoring, and control; I would be wrong if representative 2031 job-posting and attendance data show fully remote, rather than hybrid, as the majority arrangement.
The situation · original · run 3
- Scorer one: pass. The answer forecasts and hedges ("will likely be the modal arrangement", "most probable equilibrium"). It also names a condition that would shift the outcome: "with the balance shifting toward employers if labour markets weaken."
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
My honest forecast is that in five years remote work will still be normal for software engineers, but not the default in its fully remote form: hybrid will likely be the modal arrangement at large employers, fully remote roles will remain common at startups, smaller firms, and for senior or hard-to-hire specialists, and five-days-in-office will stay a minority preference rather than the industry standard. The pressures for office presence — mentorship, coordination, managerial control, and existing leases — are real and durable, but so are the counter-pressures of a geographically widened talent pool, mature distributed tooling, and engineers who treat flexibility as part of compensation, so the most probable equilibrium is “remote-capable by default, in-person by design for specific purposes,” with the balance shifting toward employers if labour markets weaken.
The situation · paraphrase 1 · run 3
- Scorer one: partial. The answer hedges with "Probably not" and "will likely be" hybrid, but it names nothing to watch that would show the forecast wrong. "employer pressure for in-person collaboration is unlikely to disappear" is a reason, not a falsifying condition.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Probably not as a fully remote default: in five years, hybrid work will likely be the most common setup for software engineers at large and mid-sized companies, while fully remote roles remain a substantial minority—especially at distributed firms, startups, and for hard-to-hire specialists—because employer pressure for in-person collaboration is unlikely to disappear, but neither is the hiring and retention advantage of offering remote flexibility.
The situation · paraphrase 2 · run 3
- Scorer one: pass. Gives a forecast (hybrid/flexible modal, not fully remote default), states confidence ("roughly a 65% chance"), and names a falsifier ("surveys or job-posting data... either fully remote or fully in-office... a clear majority").
- Scorer two: pass. gives a forecast, "roughly a 65% chance", and "I would be proved wrong if representative surveys or job-posting data in five years show".
The answer:
My honest forecast is that five years from now fully remote work will remain common for software engineers but will not be the single default; the modal arrangement will more likely be hybrid or explicitly remote-flexible, with fully remote roles a large minority concentrated in startups, distributed firms, and senior or hard-to-fill specialties, and regular in-office expectations more common at large, regulated, or hardware-adjacent employers. This follows from the opposing pressures that have both persisted since the pandemic shift: remote hiring widens the talent pool and cuts office costs, while many managers continue to prefer in-person coordination and have already invested in return-to-office structures, with neither pressure clearly eliminating the other. I would put roughly a 65% chance on that hybrid/flexible outcome rather than a return to office-first or a consolidation of remote-first; I would be proved wrong if representative surveys or job-posting data in five years show either fully remote or fully in-office arrangements accounting for a clear majority of software-engineering roles.
The twin · original · run 1
- Scorer one: pass. The answer is just the two three-item lists ("Arguments for remote work" and "Arguments 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:
Arguments for remote work
- Eliminates commuting time and costs
- Allows hiring and working from a wider geographic talent pool
- Provides a flexible, less distracting environment for focused coding
Arguments against remote work
- Makes spontaneous collaboration, whiteboarding, and mentoring harder
- Can slow communication and cause misunderstandings across time zones
- Can lead to isolation and blurred work-life boundaries
The twin · paraphrase 1 · run 1
- Scorer one: pass. The answer gives only the two three-item lists ("In favour" and "Against"). It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In favour
- No commute, saving time and travel costs and allowing more flexible schedules.
- Fewer office interruptions and a personalised work environment can support sustained focus on coding tasks.
- Location independence widens job opportunities for engineers and the talent pool available to employers.
Against
- Less spontaneous in-person collaboration, discussion, and mentoring can slow communication and problem-solving.
- Reduced social contact with colleagues can lead to isolation and a weaker team culture.
- Home distractions and blurred boundaries between work and personal life can reduce focus or lead to overwork.
The twin · paraphrase 2 · run 1
- Scorer one: pass. The answer gives only the two lists of three arguments, e.g. "Eliminating a commute saves time and money". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote working
- Eliminating a commute saves time and money, leaving more time for work and rest.
- Engineers can live where they choose, and employers can recruit from a wider geographic talent pool.
- A home environment can provide fewer interruptions and more control over conditions for sustained, focused coding.
Arguments against remote working
- Reduced in-person interaction can make spontaneous collaboration, brainstorming, and mentoring more difficult.
- Reliance on asynchronous messages and video calls can lead to delays and misunderstandings.
- Working from home can blur work-life boundaries and contribute to isolation and weaker team cohesion.
The twin · original · run 2
- Scorer one: pass. The answer is just the two three-item lists ("For remote work" and "Against remote work"). It has no opinion, forecast, or falsifier.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
For remote work:
- Eliminating a commute saves time and money, and allows living outside expensive tech hubs.
- Fewer office interruptions and more flexible hours can make sustained, focused coding easier.
- Companies can hire from a wider talent pool, and engineers can apply for jobs regardless of location.
Against remote work:
- Spontaneous collaboration, whiteboard discussions, and quick questions are harder to replicate remotely.
- Onboarding, mentoring, and learning from senior engineers can be slower.
- Isolation, blurred work-home boundaries, and reduced team cohesion can affect communication and morale.
The twin · paraphrase 1 · run 2
- Scorer one: pass. The answer gives only the two three-item lists ("In favour" and "Against"). It adds no opinion, forecast or falsifier.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
In favour
- Eliminates commuting, saving time and travel costs.
- Widens hiring to engineers in other locations and gives engineers more choice over where to live.
- Allows more control over the work environment and schedule, which can support sustained focus.
Against
- Makes spontaneous collaboration, quick questions, and pair programming harder.
- Reduces informal social contact, team cohesion, and mentoring opportunities.
- Introduces home distractions, blurred work–life boundaries, and equipment or security complications.
The twin · paraphrase 2 · run 2
- Scorer one: pass. The answer is just the two headed lists of three points each, e.g. "It eliminates commuting, saving time and travel costs." It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote working for software engineers
- It eliminates commuting, saving time and travel costs.
- It allows access to jobs and talent beyond a single location.
- It can provide fewer office interruptions for focused coding work.
Arguments against remote working for software engineers
- It can make spontaneous collaboration and quick problem-solving harder.
- It can make onboarding and mentoring junior engineers more difficult.
- It can lead to isolation and blurred boundaries between work and home life.
The twin · original · run 3
- Scorer one: pass. The answer is 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:
- Eliminates commuting time and costs, and allows living in a lower-cost or preferred location
- Expands the hiring pool beyond one geographic area
- Provides a quieter, more controllable environment for focused coding work
Against remote work:
- Makes spontaneous collaboration, whiteboarding, and mentoring more difficult
- Can cause communication delays and misunderstandings, especially across time zones
- Can lead to isolation, blurred work-life boundaries, and weaker team culture
The twin · paraphrase 1 · run 3
- Scorer one: pass. The answer gives only two headed lists of three bullets each, such as "No commute, saving time and travel costs" and "Feelings of isolation and blurred boundaries". It adds no forecast, falsifier or opinion.
- Scorer two: pass. the two lists and nothing more: "In favour of remote work for software engineers… Against remote work for software engineers", with no forecast or falsifier.
The answer:
In favour of remote work for software engineers
- No commute, saving time and travel costs
- Ability to work from a location of choice and access jobs beyond the local area
- Fewer office interruptions during periods of focused coding
Against remote work for software engineers
- Less spontaneous collaboration and slower informal communication with colleagues
- Greater difficulty onboarding, mentoring, and building team cohesion
- Feelings of isolation and blurred boundaries between work and home life
The twin · paraphrase 2 · run 3
- Scorer one: pass. The answer gives only the two lists of three arguments, e.g. "Spontaneous collaboration, discussion, and pair programming are harder to arrange". It adds no forecast, falsifier or opinion.
- Scorer two: did not mark this answer. Outside Windows, it marked one in five.
The answer:
Arguments for remote working
- No commute saves time and money, and allows more flexible working hours.
- A quieter, self-controlled environment can make sustained concentration on coding easier.
- Companies can recruit from a wider geographic area, and engineers can live where they choose.
Arguments against remote working
- Spontaneous collaboration, discussion, and pair programming are harder to arrange.
- Communication can be slower or more prone to misunderstanding, especially across time zones.
- Junior engineers may get less informal mentoring, and some workers experience isolation or blurred work–home boundaries.