Recruitment & HR Tech

App Maintenance & Support for Recruitment & HR Tech

App Maintenance & Support for recruitment & hr tech, built around the constraint that defines the sector: any screening automation must be tested for bias and be explainable to a rejected candidate.

Regulations in scope
4
Systems we integrate
4
Typical first release
6 weeks

What changes when it is recruitment & hr tech

An app is not a delivered artefact; it is a running commitment. Two OS releases a year, SDK deprecations and shifting store policy mean a neglected app breaks on its own, without anyone touching it.

In recruitment & hr tech, any screening automation must be tested for bias and be explainable to a rejected candidate. That single fact reshapes how app maintenance & support has to be built here, the guardrails, the approval points and the evidence trail are design inputs rather than things bolted on before go-live.

The workload we are most often asked to take on first is job description drafting, usually integrated against HRMS. Integration comes before intelligence. A model that cannot reach your systems of record is a demo with good manners.

Multi-model by default, so a provider outage is a routing decision rather than an incident. We hand over with runbooks, tests and a team that knows how it works, not a dependency.

The sector constraints we design around

Defining constraint
any screening automation must be tested for bias and be explainable to a rejected candidate
Regulations in scope
labour laws · DPDP Act 2023 · equal opportunity obligations · EU AI Act high-risk classification for hiring
Systems of record
ATS · HRMS · assessment platforms · background verification services
Where we usually start
CV parsing and structured screening

App Maintenance & Support workloads in recruitment & hr tech

  • CV parsing and structured screening
  • interview scheduling
  • candidate communication
  • job description drafting
  • interview note summarisation

What is included

  • OS version testing ahead of each major Android and iOS release
  • SDK and dependency upgrades before they become forced
  • Store policy compliance monitoring and required changes
  • Crash triage with prioritisation by user impact
  • Regular release cadence rather than emergency-only updates
  • A named contact, not a ticket queue

Questions from this sector

Is AI screening legal?

In India, with care; under the EU AI Act hiring is classified high-risk with specific obligations. Either way, bias testing, explainability and human review of rejections are the baseline we build to.

How do you prevent bias?

Testing outcomes across demographic groups, excluding proxy features, and keeping a human decision on every rejection. We report the test results rather than asserting fairness.

What typically needs updating?

OS compatibility twice a year, SDK and dependency upgrades, store policy changes, and whatever real users surface that testing missed. Most of it is predictable and schedulable.

What if we do nothing?

The app degrades and eventually gets pulled. Missing a required target-SDK deadline results in removal from the store, which is not recoverable quickly.

Do you maintain apps you did not build?

Yes, after a code and dependency audit. We need to see what we would be taking responsibility for, and sometimes that audit changes the advice.

App Maintenance & Support for recruitment & hr tech, worth a conversation?

Tell us the workload and the regulation it sits under. We will tell you what is realistic.

Or email bd@dtrasglobal.com · call +91 74118 77878