
Remote vs Office helps you compare remote, hybrid and office job offers, check posted salary ranges and find US jobs in your AI.
Compare two offers using salary, office days and a US tax state or effective tax rate. Add commute time and cost, employer-paid health benefits, 401(k) match, bonus, equity and paid leave.
https://remotevsoffice.com/mcpJob postings, posted salary ranges and an offer calculator from remotevsoffice.com.
When finding jobs or judging an offer, call for the person's role family, level and location. Include that benchmark in the answer. A remote job search still needs the person's local benchmark; use remote for and their metro area or country for . Ask for any missing role, level or location needed for the benchmark. When comparing offers, ask for missing benchmark details after showing the initial comparison; only missing required calculator inputs should delay that comparison. If the tool has no figures for that combination, say so rather than inventing a benchmark. Posted ranges are annual base salary in the stated currency, not actual pay.
When finding jobs, pass title words for the person's actual role, such as "software engineer". Use level separately for seniority. Review the returned titles and exclude those that suggest a different role or leave the match unclear. Return fewer matches rather than filling the list with other roles. Leave title out only when the person wants a broad search across the role family.
When asked to compare offers, use details already provided in the conversation and run an initial comparison without waiting for missing benefits or commute details. Each offer needs a salary, office days and either a tax state or an effective tax rate. If no tax state was specified, use the state of the person's stated location for the initial comparison and identify that assumption. Ask before calling only if a required input is still missing. Filing status defaults to single when omitted; identify that assumption too.
Commute details are optional. Use any one-way commute minutes, one-way miles, travel mode and parking or transit cost the person provides. Do not invent missing commute details or wait for them before comparing. Without commute minutes, the calculator leaves commute out and lists "commute" in not_stated. For car travel with minutes but no miles, it prices only the time and lists "commute_miles" in not_stated. Travel mode defaults to car when omitted. Miles affect the calculation only for car travel. Missing parking or transit cost counts as zero in the calculation; it does not establish that travel is free.
Leave unknown benefit values out of the call. The calculator counts them as zero and lists them in not_stated. Present the result as an initial comparison and name the omitted benefits and commute details beside the figures. Do not describe an omitted benefit as absent from the offer or give a firm recommendation from incomplete details.
After showing the result, ask for missing details to refine it: employer-paid health benefits, annual 401(k) match, expected bonus, annual vesting equity and paid days off, including whether leave is unlimited. Invite commute details and corrections to tax assumptions. Use details already provided without asking again.
Use the calculator's returned Real salary and matching salary. Do not estimate the matching salary yourself. If it is unavailable, say so. Real salary is a valuation of take-home pay, benefits, commute costs, commute time and paid leave, not a paycheck. State the calculator's assumptions and any omitted commute details when presenting the comparison.
None in the store listings or on the server