Role pages
Each opening has its own page with the space, hours, duties and the pay range where it must be shown.
A coworking space is hired one role at a time, from a community manager who runs member events to a front desk host who greets every visitor. SIZ Group builds a recruitment website for coworking spaces that presents each role clearly and sends every application to the person who will actually interview the candidate.
A coworking operator may run one building or several, and it often hires for different roles at the same time. Community managers, front desk hosts, events coordinators and cleaners rarely share one job description. A single generic careers page makes it hard for a candidate to see what the work involves, so the site has to describe each job in the words a candidate would type into a search box.
Candidates also judge the space by its website. Someone applying for a community manager role is checking whether the members look like a group they could serve, whether the design feels current and whether the application respects their time. A coworking careers page that reads like a warehouse listing gives the wrong first impression before anyone has walked through the door.
Most hiring starts when a community manager leaves, a new floor opens or an events peak needs extra hands. The usual steps are a posting on a job board, a screening call by the operations lead, and an emailed application that lands in one shared inbox. That inbox is often read well after the candidate has accepted another offer.
The breakdown points match most small employers, and front desk host hiring is no exception. The role is not described clearly, the application lands with whoever checks email first, and nobody tells the candidate what happens next. In a coworking space the cost is higher, because a weak first impression from a host is felt by every member who walks in afterwards.
Candidates usually search for a coworking community manager job by title and city, often on a phone while commuting. They compare each role with two or three other openings, then look for the space's own page to confirm the hours, the duties and what the pay covers. If that page is missing or vague, they move on to the next result.
That shapes the build. Each role needs a page with a plain title, a short summary of duties, the shift pattern and the pay range where it must be shown. The apply button should sit above the fold on a phone, and the form should save progress so a candidate can finish after a shift. A coworking team that answers the phone and the careers page with the same details also avoids a second round of questions.
Each opening has its own page with the space, hours, duties and the pay range where it must be shown.
A short form that works on a phone, with a saved draft and a clear indicator of how far along the candidate is.
Applicant routing by location sends each application to the operations lead for that space, with a copy to the regional lead when one exists.
Candidates receive a confirmation on submit, then an email when the application is reviewed or closed.
Reusable role templates keep descriptions consistent across locations and across every job board you use.
The first release should put every open role on its own page, collect applications through a mobile form and send each one to the manager responsible for that space. Those three pieces cover most of the hiring work, and they can launch without a new applicant tracking system.
Later phases can add short video introductions, skills tasks, interview scheduling for each location and a talent pool for future openings. Each of those touches candidate data and staff permissions, so it gets its own scope rather than being folded into the launch.
Applications collect contact details, work history and, in some cases, identity documents or a right-to-work confirmation. The site needs a clear privacy notice, a retention period for candidates who are not hired and a route for candidates to request deletion. Ask only for what the role needs, and keep equal opportunity questions voluntary and separate from screening.
Accessibility is both a legal and a practical requirement. A careers site that a screen reader cannot navigate may fall short of the ADA, and it turns away capable people. We build to WCAG 2.2 AA and test the application form with a keyboard alone. If you run background checks, the Fair Credit Reporting Act expects a standalone disclosure and written authorization before a check runs.
Track whether the site moves hiring rather than just attracting visits. Useful measures are applications per role, the share of applications that reach a screening call and the average time before a candidate hears back. Compare them with the same months a year earlier where you have records, so seasonal hiring peaks are not mistaken for the effect of the site.
Read the candidate feedback and the questions that reach the office each month during the first stretch. Those often reveal a missing detail, such as parking or shift length, that the role page should already have answered.
Our websites are priced between $300 and $2,200, depending on scope. The number of locations, role templates and system connections moves the price the most. We send the written figure after the scoping call.
Yes. Each role maps to one space, and each space maps to a named lead, so applications arrive in the right inbox. Anyone who covers for that lead can be added as a backup. Access inside your tracking tool follows the permissions already in place.
No. Applying without an account keeps the form short, which matters for someone checking their phone between meetings. If you want candidates to return and update their details later, an optional sign-in can be added after the first release.
It can remove the delays that come from unclear roles and lost emails. Speed still depends on your interview process, which the site does not control. The clearest gain is that every application has a routed owner and a confirmation, so nothing waits unnoticed in a shared inbox.
Keep their data only for the period your privacy notice states, then delete it. Some teams keep a talent pool with explicit consent, which can be added as an optional step. Ask your employment counsel to confirm the retention period for your state before launch.
Our team in Austin, Texas can scope the role pages and routing table in a single call, with the written quote to follow.