iconicompany
Back to the blog

/en/blog · writing

Why We Build Teams Faster Than You Can Open a Vacancy

We didn't build another recruiting service. We built a distributed system for hiring - where AI is just an execution layer, and a team is automatically generated for the task.

Authors: slavb18
  • AI
  • Agents
  • HR
  • HRTech
  • Startups
  • Strategy

You're still hiring people. We're already assembling teams as a system.

The difference isn't in AI. The difference is in architecture.

1. Teams Are No Longer Formed - They're Generated

How it is for you now:

  • vacancy → recruiter → funnel → interview → offer
  • 2-3 months
  • and in the end - "well, the candidate seems okay"

With us:

  • specification → system → ready team for the task

Not "by roles". But by functions, dependencies, and actual work.

2. Inside - Not an HR Process. But a Distributed System

We didn't build "just another recruiting service".

We built a distributed system for hiring:

  • each stage - a separate service
  • each service - a separate agent
  • failure of one doesn't bring everything down

Like in normal engineering architecture. Not like in an ATS, where one field broke - and everything died.

3. Microservices That Are Already Replacing Roles

Examples:

Analyst-Agent

  • reads specifications
  • decomposes tasks
  • forms a development plan
  • pushes everything to GitHub

Screening-Agent

  • receives resumes
  • conducts voice interviews
  • evaluates fit by task, not by keywords

And this isn't "in the future". This is already being written by voice in Google AI Studio.

The market's problem right now isn't AI. The problem is - there's no surrounding infrastructure:

  • authentication
  • roles
  • integration
  • orchestration

We're covering that.

4. Orchestration Is More Important Than the Models Themselves

LLMs are a commodity.

What's truly difficult:

  • how services interact
  • how they don't break each other
  • how they survive errors

With us:

  • synchronous - REST (where speed is needed)
  • asynchronous - Temporal (so one service doesn't bring everything down)

This turns hiring into:

not a chain of people, but a managed pipeline

5. The Infrastructure That Supports This

  • k8s (self-hosted)
  • build via werf + GitHub Actions
  • end-to-end authentication via authentik

This isn't "we tried AI".

It's:

we initially built a system where AI is simply an execution layer

6. The Main Point

CEOs think they have a hiring problem. CTOs think they have a people problem.

In reality:

you have a process architecture problem.

Conclusion

While the market:

  • optimizes recruiters
  • speeds up interviews
  • adds AI to ATS

we did it differently:

we eliminated the hiring process itself as a bottleneck

And replaced it with a system, that automatically assembles teams for a task.

@iconicompany

📚 Read also

Back to the blog