higharc
Jobs & hiring outlook.
Explore 12 grouped openings and the hiring signals in higharc’s public postings. Compare the work, the locations, and the requirements before your next move.
Openings over time.
Daily observations of higharc’s public job board. Advertised postings, rather than headcount or completed hires.
Tracking since 26 Oct 2026. The latest successful check on each UTC day replaces that day’s observation. Failed checks do not record zero openings.
View the recorded data (2 days)
Swipe the table to see all workplace counts.
| Day (UTC) | All postings | Remote | Hybrid | Onsite | Unstated |
|---|---|---|---|---|---|
| 2026-10-27 | 12 | 12 | 0 | 0 | 0 |
| 2026-10-26 | 12 | 12 | 0 | 0 | 0 |
A closer look at the work.
The workplace mix and role categories in higharc’s verified inventory.
Workplace mix
12 verified postings
- Remote12100%
- Hybrid00%
- Onsite00%
- Not stated00%
Role categories
Grouped openings; title-based categories
Open jobs at higharc
- remoteOlder posting · still listedChecked
What the postings actually say.
These counts describe 12 verified postings. Policies may differ between roles and do not establish an individual candidate’s eligibility.
Evidence review from Canada
Selected sponsorship need: no. This selection does not assess citizenship or personal permission to work.
1 postings have no identified conflict; 11 conflict with the selection; 0 leave conditions unresolved.
Work authorization, citizenship & clearance breakdown
0 postings contain an explicit work authorization requirement.
Citizenship: 0 required, 0 preferred, 0 explicitly not required, 12 unstated, 0 conflicting, 0 not assessed.
Clearance: 0 required, 0 preferred, 0 explicitly not required, 12 unstated, 0 conflicting, 0 not assessed.
0 postings explicitly describe worldwide remote applicant policies. Named applicant countries: Canada, United States
Employer office countries, separate from remote applicant policies: Not available.
Read 6 examples from original postings
Examples below; the counts above cover all qualifying postings.
- APPLICANT LOCATIONS
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Read original posting ↗ - APPLICANT LOCATIONS
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Read original posting ↗ - APPLICANT LOCATIONS
Software Engineer, Home Design Experience
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Read original posting ↗ - APPLICANT LOCATIONS
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Read original posting ↗ - APPLICANT LOCATIONS
Sr. Software Engineer, Structural
“Provider location: Remote (United States) • We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Read original posting ↗ - APPLICANT LOCATIONS
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Read original posting ↗
Dated source evidence · tracking since 26/10/2026
Most recent observations of source wording. These are separate from daily opening counts and do not reconstruct earlier employer policies.
- Machine Learning Engineer
Observed 27/10/2026, 20:03:12 UTC
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Original posting ↗ - Forward Deployed Engineer
Observed 27/10/2026, 20:03:12 UTC
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Original posting ↗ - Software Engineer, Home Design Experience
Observed 27/10/2026, 20:03:12 UTC
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Original posting ↗ - Sr. Software Engineer, Structural
Observed 27/10/2026, 20:03:12 UTC
“Provider location: Remote (United States) • We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Original posting ↗ - Sr. Product Manager, Studio
Observed 27/10/2026, 20:03:12 UTC
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Original posting ↗ - Sr. Product Manager - Studio Data Platform
Observed 27/10/2026, 20:03:12 UTC
“We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs.”
Original posting ↗
Remote applicant locations
Countries included by at least one explicit country, region, or worldwide policy. Confirm authorization and sponsorship for each role.
United States (12 postings)
Canada (1 postings)Observed openings. Clear boundaries.
Counts cover this tracked company board, not every vacancy across the employer. Location variants are grouped in the job list; trend charts count individual source postings. A removal does not prove a hire. Unknown dates, pay and policies stay unknown.
Read our source methodology ↗