Job search
HERC Dual-Career Search: Build a Commutable Shortlist for Two Job Seekers
A documented search boundary and four current university staff postings show how two job seekers can build independent role reviews and a conditional household shortlist.
HERC’s Dual Career Search can help two job seekers find roles near each other, but a useful shortlist still needs two separate qualification reviews and a realistic travel plan. Start with each person’s work requirements, then compare the actual workplaces, schedules, and application instructions. A pair of nearby listings is a research lead; each person still needs an appropriate opening and an independent hiring decision.
This guide checked public sources on October 20, 2026. HERC’s current guidance describes selecting the distance between jobs. Its live search interface presented a verification challenge during our review, so we did not submit a search or test results. Below, we use independently checked university postings to build a completed planning example. For a broader search alongside higher education, browse recent roles on LandOffer.ai; our job-discovery service does not arrange dual-career placements.

What HERC’s dual-career tool actually contributes
HERC’s dual-career resource page describes a search that combines both partners’ criteria and lets them select the distance between jobs. It encourages academic and nonacademic searches, including exploration outside higher education. For HERC’s purposes, at least one partner in a dual-career couple works in higher education; formal campus support has its own institutional guidelines.
The tool can reduce the back-and-forth of checking one person’s results against another person’s map. Keep the occupational searches separate: a developer might search software or data systems while a partner searches administration, museum operations, or technical support. Do not force both careers into one keyword query merely because you want one household location.
The search-service copy of the dual-search interface, crawled three months before this review, showed separate named searches, keywords, optional job-type and discipline controls, an optional location, and a displayed 25-mile radius. It explicitly described mileage as an approximation based on ZIP codes. These are documented interface details, not a verified current default, available-radius list, or account-free functionality test. The live challenge prevented that verification.
Distance between jobs is only the first geographic check
Two workplaces being close does not establish that either commute works from a particular home. Your household needs a third point: a plausible residential base. You also need the actual office or campus, required attendance, start and end times, and the route available to each person.
Treat a radius as a way to reduce the research pile. After that, ask whether both trips fit your limit on a day when both people must attend. A hybrid label may still require frequent attendance, multiple sites, evening work, or a schedule determined by the supervisor. A remote label leaves questions about permitted residence and occasional travel.
Choose a planning rule before looking at attractive titles. For example: “Each person needs an ordinary one-way trip within our assumed 45-minute ceiling; neither can rely on the other person’s remote day for transportation.” That is a household preference, not a HERC setting or measured journey. Test it later with the precise address, relevant travel times, parking or transit connections, and an alternative when the usual route fails.
A completed four-role shortlist from original employer pages
The following is a bounded example, not a HERC results export or a complete Ann Arbor inventory. We checked four University of Michigan staff or technical postings directly. The fictional job seekers are Alex, a full-stack developer with six years of relevant experience, and Priya, an administrator with seven years supporting leadership. Neither is an enrolled UM-Flint student. Their experience descriptions are assumptions for demonstrating the review, not candidate testimonials.
| Employer opening checked | Decisive public detail | Completed shortlist decision |
|---|---|---|
| Full-Stack Developer, 284511 | Ann Arbor; hybrid; five-plus years of full-stack work; two-year term subject to stated conditions | Alex: retain for closer review of technical evidence, office attendance, and term risk |
| Executive Secretary, 284567 | Kelsey Museum; Ann Arbor; more than five years of required experience; four in-person days with possible remote day | Priya: retain; the administrative career and attendance pattern merit independent review |
| Service Center Consultant Associate, 284558 | Full-time remote IT support; troubleshooting and customer communication; possible nonstandard shifts or on-call duty | Alex: separate alternative, not interchangeable with the developer role; residence and schedule remain questions |
| Administrative Specialist Intermediate, Troy Campus, 284598 | Detail field says Michigan Medicine–Ann Arbor, but duties and work-location section specify Troy Medical Campus | Priya: remove from the Ann Arbor pair until the actual site and travel plan support it |
The four decisions preserve both careers while removing a misleading location match. A promising location tag can hide a different workplace. A technical-support opening can be a real staff opportunity without offering the engineering work someone wants. Two jobs at one university can have different conditions and selection processes.
The posting windows also differ: the developer page showed October 16–30, the executive-secretary page October 19–29, and both the support and Troy pages October 19–November 2. These public date ranges were checked on October 20; availability can change before an advertised closing date. Recheck the employer page before preparing a submission.
Read the work before deciding that both people fit
Alex’s retained developer opening concerns secure public-health data systems. It calls for front-end and back-end experience, relevant programming and database skills, cloud familiarity, and security knowledge. Six years in software alone does not establish all of that evidence. Alex’s completed next step is to select a truthful project example covering both application layers and identify any missing privacy or deployment experience.
Priya’s retained museum role includes leadership calendars, meeting support, confidential records, procurement, and unit communications. Seven years of administration makes the required experience worth examining; it does not establish every responsibility. Her completed next step is to identify examples of complex scheduling and confidential record handling, then distinguish direct ownership from tasks she supported.
The support alternative has its own substantive work: assisting users, investigating issues, and improving documentation. Alex would keep it only if interested in that occupation, rather than treating “IT” as a synonym for software development. Priya would not automatically qualify because customer service appears in her background. Each person needs to read the full requirements and make their own evidence-based decision.
A completed household decision with explicit travel assumptions
Here is the second worked asset: Alex and Priya’s finished pair-selection record. They are exploring an Ann Arbor residential base; they have not chosen an address, signed a lease, received offers, or measured routes. The minutes below are invented planning assumptions used to expose dependencies. They are not map estimates, HERC calculations, or claims about normal Michigan traffic.
| Pair considered | Assumed one-way trips from proposed base | Household rule applied | Decision recorded |
|---|---|---|---|
| Developer plus museum administration | Alex 30 minutes; Priya 25 minutes | Both below their 45-minute planning ceiling; assess days both attend | Preferred research pair, conditional on exact addresses and schedules |
| Remote support plus museum administration | Alex no ordinary office commute assumed; Priya 25 minutes | Remote residence permission and required travel still unknown; shifts may conflict | Hold as a different career option, not an automatic upgrade |
| Developer plus Troy administration | Alex 30 minutes; Priya 75 minutes | Priya exceeds their assumed ceiling | Exclude from this household plan; revisit only if the base or limits change |
Their completed decision reads: “Research the developer and museum roles independently. Do not make a housing commitment from campus labels. Keep support work separate until Alex decides whether its daily responsibilities fit. Exclude the Troy pairing under our current travel assumption, without asserting an actual route time.”
This record is useful even if the assumptions later change. It shows which conclusion depends on which input. If the museum attendance pattern changes, revisit that pair’s travel plan. If Alex prefers support work, review its residence and shift conditions. If a verified Troy journey fits a different base, reassess it rather than treating the initial exclusion as a permanent verdict.

Review attendance and employment conditions together
The developer page names a main workspace in the Leinweber Computer Science and Information Building, possible travel to other locations, and nonbusiness-hours or weekend work when required. Its two-year term depends on performance, work availability, and funding. The museum role describes regular weekday hours with occasional evenings. Those facts deserve a joint scheduling discussion before the couple treats the pair as workable.
They should not assume two hybrid roles provide synchronized remote days. Nor should they turn the developer’s term into a claim that Priya’s position has the same duration. Keep each employment condition attached to its own requisition.
Before choosing a residential base, record the unresolved attendance and worksite questions for each requisition. For Alex and Priya, it contains the developer’s expected onsite pattern, exact locations and travel frequency, both roles’ evening obligations, and their independent readiness for each opening. None of those questions requires disclosing a partner’s private employment history merely to organize the research.
Campus dual-career services require a separate eligibility check
A public job search and a university’s formal partner-support program are different routes. HERC’s current resource page says support varies by institution. Its 2019 introduction to dual-career services explains that offices can provide guidance and contacts while offering no job guarantee. Treat that older article as background, not current eligibility policy for any particular campus.
Alex and Priya have not established eligibility for a formal program. Their completed record therefore says “campus support unknown” rather than “partner placement included.” If a future institution offers support, they would need its current rules: which hires or employees qualify, who can initiate the service, what assistance exists, and whether information is shared with recruiting departments.
Share personal information only when needed for the specific recruiting or support process. A joint household planning document can stay private while each person maintains an independent professional application. Do not assume a search name, saved alert, uploaded resume, and institutional referral all have identical visibility. We did not create a HERC account, upload materials, or inspect private sharing controls.
Keep two independent application records
The retained pair needs two document checks. The developer posting requires a cover letter as the first resume page and states a maximum of three pages. The museum posting also requires a cover letter as the first resume page, but its instructions must be reviewed on their own. A shared university employer does not make one submission cover both people or both requisitions.
Alex’s record contains 284511, the employer URL, the public posting window, his technical-evidence gaps, and the term and attendance questions. Priya’s contains 284567, its URL and window, her administrative examples, and its work pattern. Both are marked “research retained; not submitted.” A future receipt belongs to the person and opening it actually confirms.
Use the paired shortlist to coordinate research, then preserve each person’s career choice and hiring process. If one opening closes or one application progresses first, the other person’s position remains independently unresolved. Keep searching while either person’s employment remains unresolved. For additional leads outside this campus example, explore LandOffer.ai and evaluate each role against the same work, location, and schedule criteria.
Sources and Further Reading
- HERC dual-career resources and distance-between-jobs description
- HERC dual-search interface; live review blocked by verification challenge
- HERC introduction to dual-career services, dated July 23, 2019
- University of Michigan Full-Stack Developer 284511
- University of Michigan Executive Secretary 284567
- University of Michigan Service Center Consultant Associate 284558
- University of Michigan Administrative Specialist, Troy Campus 284598


