AI System for Automatic Job Description Generation

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
AI System for Automatic Job Description Generation
Simple
~2-3 days
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1360
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

Job Descriptions That Find the Perfect Candidate

Every HR manager knows: a single job description takes 30–90 minutes to write. Yet 70% of texts on hh.ru and LinkedIn look like template copies — same phrases, no tone of voice, and SEO ignored. Candidates scroll past such ads in seconds. We developed an AI system that generates a structured job description in 15–30 seconds based on the job title, tech stack, and requirements — with gender neutrality control, SEO optimization for each platform, and alignment with the employer brand.

How Generation Works

At the core is a fine-tuned GPT-4o model with prompt engineering for HR tasks. We pass a JobBrief dataclass with fields for title, department, tech_stack, responsibilities, and tone parameters (professional, startup, corporate, creative). The model returns JSON with sections: title_seo, about_company, responsibilities, requirements_hard, requirements_soft, nice_to_have, conditions, and cta. The generator uses asyncio to process up to 10 requests in parallel. We use the OpenAI API with temperature and top_p settings to balance creativity and accuracy.

from openai import AsyncOpenAI
from dataclasses import dataclass, field

client = AsyncOpenAI()

@dataclass
class JobBrief:
    title: str
    department: str
    employment_type: str          # full-time, part-time, contract, freelance
    experience_years: tuple       # (min, max)
    tech_stack: list[str]
    responsibilities: list[str]
    company_description: str
    tone: str = "professional"    # professional, startup, corporate, creative
    language: str = "ru"
    include_salary_range: bool = False
    salary_range: tuple = None

async def generate_job_description(brief: JobBrief) -> dict:
    response = await client.chat.completions.create(
        model="gpt-4o",
        messages=[{
            "role": "system",
            "content": f"""Ты — HR-копирайтер, специалист по employer branding.
            Создай описание вакансии для job-агрегаторов (hh.ru, LinkedIn, Habr Career).

            ТРЕБОВАНИЯ:
            - Заголовок: должность + ключевые технологии (для SEO в поиске)
            - О компании: 2–3 предложения, конкретные факты, без «лидер рынка»
            - Обязанности: 5–7 пунктов с глаголами действия, конкретных
            - Требования: hard skills отдельно от soft skills, must-have vs nice-to-have
            - Условия: без воды, только факты
            - Гендерно нейтральные формулировки (не «программист», а «разработчик/разработчица» или нейтрально)
            - Tone of voice: {brief.tone}

            Верни JSON: {{title_seo, about_company, responsibilities, requirements_hard, requirements_soft, nice_to_have, conditions, cta}}"""
        }, {
            "role": "user",
            "content": f"""
            Должность: {brief.title}
            Отдел: {brief.department}
            Тип занятости: {brief.employment_type}
            Опыт: {brief.experience_years[0]}–{brief.experience_years[1]} лет
            Стек: {', '.join(brief.tech_stack)}
            Ключевые задачи: {', '.join(brief.responsibilities)}
            О компании: {brief.company_description}
            {"Зарплата: " + f"{brief.salary_range[0]}–{brief.salary_range[1]} руб." if brief.include_salary_range and brief.salary_range else ""}
            """
        }],
        response_format={"type": "json_object"}
    )
    import json
    return json.loads(response.choices[0].message.content)

Why Adapt Descriptions for Each Platform?

hh.ru, LinkedIn, and Habr Career have different requirements for structure and style. hh.ru values brevity — a maximum of 100 characters for the title and strict sections. LinkedIn, on the other hand, encourages expanded descriptions with keywords for search. Habr Career requires technical details and metrics. We implemented platform templates with constraints and stylistic rules — the adaptation code uses the same model with an additional prompt.

JOB_PLATFORM_FORMATS = {
    "hh.ru": {
        "max_title": 100,
        "sections": ["about_company", "responsibilities", "requirements_hard", "conditions"],
        "style": "структурированный, без маркетинга"
    },
    "linkedin": {
        "max_title": 120,
        "sections": ["about_company", "responsibilities", "requirements_hard", "requirements_soft", "nice_to_have"],
        "style": "профессиональный, с ключевыми словами для LinkedIn Search"
    },
    "habr_career": {
        "max_title": 100,
        "sections": ["responsibilities", "requirements_hard", "nice_to_have", "conditions"],
        "style": "технический, для IT-аудитории, конкретные метрики"
    }
}

async def adapt_for_platform(job_data: dict, platform: str) -> str:
    fmt = JOB_PLATFORM_FORMATS.get(platform, JOB_PLATFORM_FORMATS["hh.ru"])
    response = await client.chat.completions.create(
        model="gpt-4o",
        messages=[{
            "role": "system",
            "content": f"Адаптируй описание вакансии для платформы {platform}. Стиль: {fmt['style']}. Используй разделы: {fmt['sections']}."
        }, {
            "role": "user",
            "content": str(job_data)
        }]
    )
    return response.choices[0].message.content

Mass Generation for Hiring: When You Need to Fill 50+ Positions

For mass hiring, the system accepts a CSV with a list of positions and tech stacks, generates descriptions in batches of 10–15 vacancies in parallel via asyncio.gather, and saves the result in formats for all platforms. For companies hiring more than 50 people per year, this saves 200–300 hours of HR team time. Below is a comparison of effort:

Stage Manual Process AI System
Writing one description 30–90 min 15–30 sec
Adaptation for 3 platforms 20–40 min 1–2 min
Gender neutrality check 5–10 min automatic
SEO tuning for job aggregators 10–15 min built-in

The AI system is 10x faster than manual drafting — confirmed by our measurements on client projects.

Evaluation and Iterations: How to Ensure the Text Works

async def score_job_description(text: str) -> dict:
    """Оцениваем описание по факторам привлечения кандидатов"""
    response = await client.chat.completions.create(
        model="gpt-4o",
        messages=[{
            "role": "system",
            "content": """Оцени описание вакансии по критериям (1–10):
            - clarity: ясность требований
            - appeal: привлекательность для кандидата
            - seo_score: SEO для job-агрегаторов
            - gender_neutrality: гендерная нейтральность
            - specificity: конкретность (vs абстрактные требования)
            Верни JSON с оценками и рекомендациями."""
        }, {
            "role": "user",
            "content": text
        }],
        response_format={"type": "json_object"}
    )
    import json
    return json.loads(response.choices[0].message.content)

The system doesn't just generate text — it evaluates it on a scale of 1–10 by criteria: clarity, appeal, seo_score, gender_neutrality, and specificity. Based on the evaluation, we adjust the prompt and consistently achieve high quality. Our experience shows that after 3–4 iterations, the text quality matches the best manual samples.

What's Included in Our Development

  • Architecture design: LLM selection (GPT-4o or LLaMA 3), dataset preparation for few-shot learning.
  • Module development: generator, platform adapter, quality analyzer.
  • Integration with ATS (Huntflow, Talantix, Greenhouse) and HRM systems.
  • Testing and A/B testing of generated descriptions on real vacancies.
  • Deployment in your infrastructure (Kubernetes, SageMaker, or on-premise).
  • API documentation and HR team training.

Implementation Stages

  1. Analysis of the current HR process and gathering requirements for tone of voice, platforms, and ATS.
  2. Architecture design and LLM selection — we recommend GPT-4o or LLaMA 3 depending on confidentiality requirements.
  3. Development of generation, platform adaptation, and quality evaluation modules.
  4. Integration with your ATS via REST API.
  5. Testing on 5–10 vacancies, prompt adjustments.
  6. Deployment to cloud or on-premise, team training.

Timelines and Cost

MVP development with support for one platform takes 1–2 weeks. Integration with ATS and mass generation takes another 2–3 weeks. The exact cost is calculated individually after an audit of your HR infrastructure. We guarantee text quality on par with manual drafting — confirmed by over 30 projects completed in 5 years of work in the AI HR solutions market.

Why Implement AI Generation Now?

The job market is changing — candidates choose companies that speak their language. An automatic job description generation system gives a competitive advantage: speed, quality, and a consistent tone of voice across all postings. Request a demo — we'll show you on your data.

Generative AI Development: From Prompt to Production API

We often receive a task "generate a product image" — on the surface it seems simple. But behind this lies a choice between dozens of models, configuring the inference pipeline, manually solving consistency issues, integrating into the product backend, and answering why the model generates hands with six fingers in staging but not in production. Let's break down the directions we work with.

Image Generation: From Prompt to Production API

The current landscape includes FLUX.1 [dev/schnell/pro] from Black Forest Labs and Stable Diffusion 3.5. FLUX.1 [schnell] takes 4 steps instead of 20–50 for SDXL — 5–12 times faster — while maintaining higher quality. On an A100 80GB — 1.2–1.8 s per 1024×1024 image at batch_size=4.

A typical deployment issue: FLUX.1 [dev] requires 24+ GB VRAM in fp16. On A10G 24GB it fits tightly; at batch_size>1 — OOM. Solution: torch_dtype=torch.bfloat16 + enable_model_cpu_offload() from diffusers, or quantization via bitsandbytes to NF4 — minimal quality drop, memory consumption drops to 12–14 GB.

ControlNet and IP-Adapter are key tools for production tasks where controllability is needed. ControlNet with Canny/Depth/Pose maps provides structural control. IP-Adapter (especially IP-Adapter-FaceID) allows transferring character identity to generations — this is the foundation for personalized content. More about ControlNet can be found on Wikipedia.

Case study: e-commerce photography. A retailer with 8000 SKUs needed lifestyle photos for each product. Pipeline: product segmentation (Segment Anything Model 2) → background removal → inpainting with FLUX.1 [dev] using product image as IP-Adapter reference → upscale via RealESRGAN_x4plus. The generation cost is negligible compared to professional photography, providing huge savings. Throughput — 200 images/hour on 2× A100. Our extensive experience from 30+ projects ensures we select the optimal model for your task — an evaluation can be obtained upfront.

Why Is Model Selection Only Half the Battle?

Fine-tuning for a Specific Style or Character

Dreambooth and LoRA are the standard for adapting to a specific visual style or object. LoRA trains in 2–4 hours on 20–30 reference images on a single A100. Rank 16–32 is usually sufficient for style; rank 64+ is needed for precise face reproduction.

A common mistake: training LoRA too long — the model overfits to references, losing the ability to vary. Sign: at cfg_scale=7, all images look like copy-paste of references. Solved by early stopping (usually 1500–2000 steps for 20 images) and prior_preservation_loss.

For deeper customization — full fine-tuning via diffusers + accelerate with FSDP on multiple GPUs. But that already takes 40–80 hours of training and requires a truly large dataset (1000+ images).

Comparison of Image Generation Approaches

Model Speed (1024×1024, A100) Quality (CLIP score) Controllability (ControlNet, IP-Adapter) VRAM (fp16)
Stable Diffusion 3.5 2.0–3.5 s 0.28–0.31 via ControlNet (allowed) 16–20 GB
FLUX.1 [schnell] 0.8–1.2 s 0.30–0.33 limited (no ControlNet) 12–14 GB (4‑step)
FLUX.1 [dev] 3–5 s (50 steps) 0.32–0.34 via IP-Adapter, ControlNet (adapter) 24+ GB
Midjourney (API) 5–10 s (queue) 0.31–0.33 prompt + style reference not required

Video Generation: Which Models Are Best?

Model Availability Duration Resolution Controllability
Sora (OpenAI) API (limited) up to 60 s 1080p prompt, image-to-video
Wan2.1 (Alibaba) open weights up to 81 frames 720p prompt, I2V, V2V
CogVideoX-5B open weights 6 s 720p prompt, I2V
Kling 1.6 API up to 30 s 1080p prompt, I2V
Mochi-1 open weights 5.4 s 480p prompt

Open-weight video models still lag behind commercial ones in stability and length. Wan2.1 is the best choice for self-hosting: 14B parameters, runs on 2× A100, delivers acceptable quality for short clips.

The main pain of video generation is temporal consistency: the character changes clothing color at the third second, objects "drift." Partial solution — generation with motion_bucket_id and noise_aug_strength in Stable Video Diffusion, or using I2V (image-to-video) instead of pure text-to-video. As noted in VideoPoet research, consistency is achieved by training on long sequences.

AnimateDiff remains a working tool for short loops and motion effects on top of SD/FLUX. Not Sora, but deployable locally and predictable.

Music and Audio Generation

AudioCraft from Meta (MusicGen + AudioGen) is a production-ready stack for music generation. musicgen-large (3.3B) generates 30 s of music in ~8 s on A100. Control via text prompt and melody conditioning — you can specify a melody by humming.

Stable Audio Open from Stability AI is an alternative with length up to 47 s, better structural control (intro/verse/chorus). Deployment is similar: diffusers + FastAPI.

For voice-over and dubbing — ElevenLabs API or self-hosted XTTS v2 (see Speech AI service). For sound design and foley — AudioGen.

3D Generation: Current Practical State

3D generation has not yet reached the same maturity as 2D. But for specific tasks, tools are already working:

TripoSG and Shap-E — text/image-to-3D. Shap-E from OpenAI generates simple 3D meshes in seconds, but geometry is rough. TripoSG gives more detailed results but requires post-processing (remeshing, UV unwrapping).

Wonder3D and Zero123++ — 3D reconstruction from a single image. They work by generating multi-views (6–8 views) and then 3D reconstruction via NeuS or instant-ngp.

Gaussian Splatting (3DGS) — not generation, but reconstruction from a series of photos/videos. For product cards and real estate it's already production: 50–200 photos → 3DGS model in 15–30 min on RTX 4090 → interactive 3D viewer in browser.

What Infrastructure Is Needed for Generative AI Deployment?

Critical for generative models:

  • Task queue — Celery + Redis or Ray Serve. Synchronous HTTP for image generation is unacceptable with >5 concurrent requests.
  • Caching — similar prompts yield similar results. Semantic cache via embeddings (faiss + sentence-transformers) can reduce GPU load by 20–40%.
  • Quality monitoring — CLIP score for text-image alignment, FID for evaluating generation distribution. Integrate into MLflow or Weights & Biases.
  • Storage — generated images immediately to S3/MinIO, not on the inference server disk.

What's Included in the Deliverables

We take the project turnkey — from model selection to deployment and monitoring. The result includes:

  • Model (or API integration) with performance benchmarks (latency p99, throughput).
  • Pipeline documentation (prompt engineering guide, model card, dependency versions).
  • Integration with your backend (REST/gRPC, queues).
  • Configured monitoring (dashboards, alerts for quality drift).
  • Training workshop for the team (2–4 hours).
  • Warranty support for 3 months after launch — as part of our quality certificate.

We have completed 30+ projects in generative AI — this gives us the right to guarantee results.

How Is the Generative AI Development Process Structured?

  1. Analysis (1–2 days): audit of current architecture, clarification of use case, selection of models and success metrics. We evaluate the project free of charge.
  2. Proof of Concept (1–3 weeks): quick prototype on your data — to see real quality, not blog demos.
  3. Design (1–2 weeks): pipeline architecture, infrastructure (GPU cluster/API), A/B testing plan.
  4. Implementation and fine-tuning (4–12 weeks): development, LoRA/full fine-tuning, integration with queue and cache.
  5. Testing (1–2 weeks): load tests, metric validation, edge-case verification (negative scenarios).
  6. Deployment and monitoring (1–2 weeks): production deployment, monitoring setup, documentation.
What We Verify at the Proof of Concept Stage
  • Alignment of expectations and actual generation quality (CLIP score, user study).
  • Inference speed at different batch sizes and GPU types.
  • Likelihood of toxic/incorrect generations — checking safety filters.
  • Scalability: will the model handle peak load.

Timeline Estimates

Integration of a ready API (DALL·E 3, Midjourney API, Stability API) — 1–2 weeks. Self-hosted pipeline with fine-tuning — 6–12 weeks. Full platform with UI, queues and monitoring — 3–6 months. The specific cost is calculated individually after analyzing your scenario.

Contact us — order a consultation, and we will select the optimal architecture for your project. Get a preliminary cost and timeline estimate for free.