Deciding on a Dev Agency name
January 2025
The name is DiligenceAI
graph TB
subgraph "Client Layer"
UI[React Frontend]
JobPage[Job Details Page]
ImportModal[Candidate Import Modal]
ConfigDialog[Field Mapping Dialog]
end
subgraph "API Layer"
APIGateway[Express API Gateway]
JobController[Job Controller]
ATSController[ATS Controller]
FieldMappingController[Field Mapping Controller]
WebhookController[Webhook Controller]
end
subgraph "Service Layer"
JobService[Job Service]
SyncProcessor[ATS Sync Processor]
FieldMappingService[Field Mapping Service]
RecruitCRMClient[Recruit CRM Client]
end
subgraph "Background Jobs BullMQ"
CandidateImport[Candidate Import Queue]
AppProcessing[Application Processing Queue]
AudioDownload[Audio Download Queue]
AgentEval[Agent Evaluation Queue]
EvalSummary[Evaluation Summary Queue]
ResultExport[Result Export Queue]
end
subgraph "External Services"
RecruitCRM[Recruit CRM API]
ElevenLabs[ElevenLabs API]
S3[AWS S3]
end
subgraph "Database PostgreSQL"
Jobs[(jobs)]
Candidates[(candidates)]
Applications[(job_applications)]
Interviews[(interviews)]
ATSConnections[(ats_connections)]
FieldMappings[(ats_field_mappings)]
end
UI --> JobPage
JobPage --> ImportModal
UI --> ConfigDialog
ImportModal --> APIGateway
ConfigDialog --> APIGateway
JobPage --> APIGateway
APIGateway --> JobController
APIGateway --> ATSController
APIGateway --> FieldMappingController
APIGateway --> WebhookController
JobController --> JobService
ATSController --> SyncProcessor
FieldMappingController --> FieldMappingService
SyncProcessor --> RecruitCRMClient
FieldMappingService --> RecruitCRMClient
RecruitCRMClient --> RecruitCRM
ATSController --> CandidateImport
CandidateImport --> AppProcessing
AppProcessing --> SyncProcessor
WebhookController --> AudioDownload
AudioDownload --> ElevenLabs
AudioDownload --> S3
AppProcessing --> AgentEval
AgentEval --> EvalSummary
EvalSummary --> ResultExport
ResultExport --> SyncProcessor
JobService --> Jobs
SyncProcessor --> Candidates
SyncProcessor --> Applications
SyncProcessor --> Interviews
FieldMappingService --> ATSConnections
FieldMappingService --> FieldMappings
AudioDownload --> Interviews
The story behind the name is. That for past few days I was strongly searching for a name for the agency.
However nothing was striking or clicking. Then suddenly while reading the autobiography of Benjamin Franklin.
I read a line from Benjamin Franklin’s book
Let us then up and be doing, and doing to the Purpose; so by Diligence shall we do more with less Perplexity.
The word diligence striked a lot.
It captures how we work with energy and devotedly.
So that’s how the first word comes from. The second word AI, because most of the projects we work on have an AI element.
So that’s how the name got decided, DiligenceAI
Happy to have you all be a part of this!
Also soon, will be having the website ready for this, was able to get the domain DiligenceAI.dev.
Which signales dev agency too!