Role pages with pay ranges
Each apiary and swarm role shows its schedule, vehicle needs, physical demands and pay range.
SIZ Group builds a beekeeper job application website with a page for each apiary role, an application form that asks job-specific questions and routing that sends every applicant to the lead who runs that crew.
Many beekeeping companies still hire by word of mouth, a text to a former helper or a post on a local group page. That works until the spring swarm season needs four people before the first swarm call. Then the owner is answering the same question from six people and still has no list of who applied.
The gap usually sits between the post and the interview. A candidate who reads about a swarm technician role wants to know the start date, the lifting load and whether a truck is provided. Most beekeeper job postings read like a list of duties with no schedule, so the candidate moves on to the next listing.
Apiary technician hiring needs one page per role, covering swarm responder, extraction helper and crew lead too. Each page lists the schedule, the vehicle requirements, the physical demands and the pay range. A short application form follows, with questions about availability, a valid driver's license for van runs and experience handling colonies.
Later phases can add a candidate talent pool, reference requests after an offer and a seasonal rehire list. Those help a company that hires every year, but they do not fill the crew that starts in April. If the company already keeps a candidate list in a spreadsheet, the site can add applicants to it instead of starting a new list.
Pay transparency laws in several states, including California, Colorado and New York, require a pay range on many job postings, so the page should show one even where a state does not yet require it. Work authorization questions should be limited to asking whether the applicant is legally able to work, with I-9 checks made after an offer.
Health questions are restricted before an offer under federal disability rules, so the form should describe the physical tasks, such as lifting a 40 pound box, and ask whether the applicant can perform them with or without accommodation. Allergy and medical questions do not belong on the application. Applicant data should be deleted on a set schedule, and state privacy laws can apply to candidates who live in those states.
Each apiary and swarm role shows its schedule, vehicle needs, physical demands and pay range.
Questions cover availability, driving, colony experience and the physical tasks, with no medical or citizenship questions.
Each applicant goes to the lead who runs that crew, with the time of the message kept on record.
Applicants learn when to expect a call, which cuts the number of follow-up texts to the owner.
Staff can change a start date, close a role or add a late opening without calling a developer.
Records are kept for the period you set and deleted on schedule, with access limited to hiring staff.
The first mistake is a single job page that describes the company rather than the role. Candidates want to know the crew, the sites and the first-day plan, and a page that opens with a company history gets skipped.
The second is a form that asks for a full resume and three references for a seasonal helper. Keep the first step to contact details and availability, then collect the rest when the lead calls back. A third is asking for citizenship or national origin in the form itself. Applicant routing for field teams should send each form to the lead who will interview that candidate, not to a general inbox.
Websites range from $300 to $2,200, depending on scope. A handful of role pages with one application form and one routing rule sits near the lower end. More roles, separate forms for each apiary site and a custom applicant tracking step push the scope upward.
Agree the role list, the questions for each role and the routing table in writing before design starts, so later changes are priced as named edits. The free scoping call is where the company's own tools and hiring steps are mapped out. A pay range should also match what the company really offers, since a number that changes at the interview loses candidates quickly.
Track how many visitors open each role page, how many start the form, how many finish it and how long a lead takes to reply. Those numbers come from analytics and the shared inbox, so the owner can see where the funnel leaks without an outside benchmark.
The number that matters most is hires per season against the crew size the company needed. Seasonal beekeeping crew applications should be counted by role, not as one total. If the apiary crew is full before the first swarm call, the site did its job. Remove any role page that stays unopened, so the list stays short and current.
We recommend it. Several states require pay ranges on many postings, and candidates skip roles without one. The range goes on the role page and in the confirmation, so the number stays consistent from the first click to the offer.
The form describes the physical tasks, such as lifting and working outdoors, and asks whether the applicant can perform them with or without accommodation. It does not ask about allergies or medical history. We review the final question list with you before launch, and your employment adviser should confirm it.
Yes. The form is built for phones first, with large fields and one column, so a candidate can finish it on a lunch break. Anyone who does not want to use the form can still call the number on the page.
Applications are kept for the period you choose and deleted on that schedule. Candidates who are not hired can ask for their record to be removed. The exact retention rule is agreed during the scoping call and written into the project plan.
Book a free scoping call and we will map your roles, application questions and routing rules before any design work begins.