Developing a job portal using 1C-Bitrix

Job Portal Development on 1C-Bitrix

HR manager publishes vacancy on five platforms, receives 200 responses in five different personal cabinets, consolidates them in Excel, loses half, forgets to call back three candidates, and the best one goes to competitor because they didn't get an answer for a week. Own job portal on 1C-Bitrix is a single entry point for job seekers and single interface for recruiters: publishing, responses, recruitment funnel, analytics — without tab zoo.

Portal Architecture

Job portal operates four main entities, each modeled as separate infoblock:

• Vacancies — what employer publishes
• Resumes — what job seeker publishes
• Responses — link between vacancy and resume with status funnel
• Companies — employer cards

Vacancy — element structure:

Resume — element structure:

Search and Matching

Search is key scenario for both sides: job seeker searches vacancies, employer searches resumes.

Vacancy search:

• Full-text search by title and description
• Filters: professional field, city, salary (from), employment type, schedule, experience, remote
• Sorting: by date, salary, relevance
• Saved searches with email notifications about new vacancies

Resume search (for employers):

• Full-text search by skills, position, experience description
• Filters: specialization, city, experience, salary expectations, update date
• Contact access — after payment or subscription

For portals with 50,000+ vacancies/resumes — Elasticsearch. Standard 1C-Bitrix search won't provide needed filtering speed and ranking quality. Elasticsearch gives: fuzzy search (typo correction), synonyms (PHP developer = PHP programmer), weights (job title more important than description).

Recommendations and matching:

• Viewing vacancy — "Similar vacancies" block (by category + city + salary range)
• Viewing resume — "Matching vacancies" block (by skills + desired position)
• Email newsletter "Vacancies for you" — personalized selection based on seeker profile

Matching implemented via skill tag comparison between resume and vacancy requirements. Basic variant — tag set intersection ranked by match count. Advanced — ML model trained on successful response data.

Responses and Recruitment Funnel

Response is central entity of hiring process. "Responses" infoblock element links vacancy to resume and tracks interaction history.

Response funnel:

New → Viewed → Invited to interview → Test assignment →
Final interview → Offer → Accepted / Rejected

Each transition — with date, recruiter comment, candidate notification.

Funnel implementation:

• "Status" property as List with preset values
• Business process on status change: send candidate notification, create recruiter task, update analytics
• Kanban-style board — custom component in employer cabinet, drag cards between columns

Bulk actions: reject unsuitable, send template letter to candidate group, export to Excel for management.

Employer Cabinet

Employer is portal's paying customer. Their cabinet must be functional.

Functions:

• Vacancy management — create, edit, duplicate, archive, statistics (views, responses, conversion)
• Responses — list with filters by vacancy, status, date. Kanban board for visual funnel management
• Resume search — database access, saved queries, vacancy invitations
• Company card — description, logo, office photos, benefits, social links. Displayed on vacancy page and company catalog
• Employees — multiple recruiters from one company with different rights (publishing, response viewing, database access)
• Statistics — dashboard: recruitment funnel, average vacancy closing time, response sources
• Plans and payment — balance, payment history, active services

Job Seeker Cabinet

• My resumes — create, edit multiple resumes (for different specializations), manage visibility
• Responses — list with statuses, chat history with employer
• Saved vacancies — bookmarked for later response
• Search subscriptions — notifications about new vacancies matching saved filters
• Invitations — from employers who viewed resume

Monetization

For employers:

For job seekers portal usually free — source of content (resumes) and traffic.

Payments — via 1C-Bitrix sale module. Internal balance topped up via payment system, services deducted from balance. Recurring subscription payments — via card tokenization (YuKassa, CloudPayments).

Integrations

• Vacancy import — XML feed for bulk upload from large employers (compatible with hh.ru, SuperJob formats)
• Vacancy export — XML feed for aggregators (Yandex.Jobs, Google for Jobs)
• Email parser — responses from external platforms arriving by email automatically create funnel records
• ATS integration — for large companies: bidirectional sync with internal recruitment system (Huntflow, E-Staff, Talantix)
• Messengers — Telegram notifications for recruiters and job seekers

SEO for Job Portal

• Landing pages — /vacancies/programmer/minsk/, /vacancies/sales-manager/moscow/ — generation from specialization + city combinations
• Google for Jobs — JobPosting micromarkup by Schema.org: title, description, datePosted, validThrough, hiringOrganization, jobLocation, baseSalary
• Company cards — Organization with aggregateRating
• Clean URLs — /vacancy/job-title-company-id/
• Sitemap — dynamic, split by categories, update on vacancy post/close
• Noindex for closed vacancies and hidden resumes