MIDAS Business Solutions

From applicant
to everyday
operations.

I connected the careers website, recruitment and workforce tools in Odoo, so hiring information can carry into the working day.

Visit the MIDAS website

The public MIDAS careers homepage — The public MIDAS website: the front door to the platform.

My role

Senior Odoo Developer

Architecture, implementation and integration

Context

Internal business platform

Recruitment and workforce operations for MIDAS

Foundation

Odoo 18 Community

Python · PostgreSQL · QWeb · JavaScript

Two audiences.
One connected system.

Candidates need a clear way to find and apply for a role. The internal team needs structured information to review, hire and plan the work that follows.

I built the public candidate experience and connected it to Odoo’s recruitment and employee records. Custom screening, skills and shift workflows extend that foundation.

The candidate journey

From the website
to the hiring team.

Four stages, with the application carrying the context forward.

Find a role that fits.

Candidates search by role or skill and filter by department and employment type. Every opening leads to its own brief.

Careers search with department filters and fictional open roles — Job search and role filters on the careers website.

The brief comes before the form.

Responsibilities, location, experience and the closing date sit together, with a direct route to apply.

A fictional Client Operations Specialist role with requirements and an application link — A dedicated role page with the context needed to apply.

Ask questions specific to the work.

Each role can have its own questions. Written answers and structured choices become useful recruitment information alongside the CV.

Role-specific application questions with fictional written answers and availability — An application for a fictional operations role, with its own screening questions.

Pick up the application in Odoo.

The hiring team sees applications across roles and interview stages. Candidate details, skills and follow-up activities stay with the record.

Fictional applicants across departments and interview stages in Odoo recruitment — The internal recruitment board, populated with fictional candidates.

Recruitment with context

The CV is only
part of the picture.

I brought application answers and skill proficiency into the review, so the team can inspect the fit and see what is missing.

Skills you can compare.

Required proficiency sits alongside candidate skills. The team can also consider applicants from other roles without losing their original application.

Missing information remains visible. A score supports the review; it does not replace the person making the decision.

Required skill levels compared with fictional applicant proficiency — Required skills, candidate proficiency and visible gaps.

Inspect the application and follow-up views

Role-specific application answers carried into the recruitment record — Role-specific answers become structured applicant information.

A fictional candidate record with skills and planned follow-up activities — Candidate details, skills and planned follow-ups together.

The hiring handoff

Hire the person.
Keep the context.

The hired applicant becomes a linked employee. Role, department and skills continue into staff administration.

A repeat action should be safe.

Repeating the hiring action reuses the existing employee link instead of creating another person.

A hired applicant linked to an employee record with role, department and skills — One applicant connected to one employee record.

Workforce operations

Then the working
day begins.

Schedules, task time and reporting continue the story after hiring. Each is part of the same operational platform.

01 Schedules & attendance

A schedule that makes room for change.

Staff work across shifts and time zones. I built the planning and request flows around those working patterns, with manager scope and review steps.

The schedule shows who is planned, present, late or absent. A change request keeps the reason and approval state alongside the shift.

Fictional schedules, attendance exceptions and shift change requests — Schedules, attendance exceptions and reviewed shift changes.

02 Tasks & time

Hours with a record behind them.

Task timers connect the work to its time entry. Start, pause, resume and stop events explain how the recorded time was calculated.

Breaks are excluded from working time. The session history remains linked to the task and employee.

Task timer sessions and the time entries they produce, using fictional records — Task sessions and their corresponding time records.

03 Management reporting

A summary you can look into.

Managers can compare planned hours with weekly targets, then inspect the records behind the totals.

The reporting views bring operational workload and financial activity into the same platform, while keeping the underlying records available for review.

Workload planning and financial detail with fictional demonstration records — Workload comparisons and the records behind financial activity.

Implementation

Built around the
way the team works.

I combined my custom development with Odoo and adapted open-source modules. The core design work was connecting the workflows and making their boundaries explicit.

Shared records, different interfaces: The public website serves candidates. Odoo serves staff. Applications enter the recruitment model, rather than becoming a separate list to transfer later.
Screening on the server: Role-specific questions and geographic eligibility belong in the application workflow. Server-side checks support the public form’s guidance.
Permissions follow responsibility: Shift planning and change requests use roles and manager scope, so the review follows the people responsible for the work.
Clear ownership of the build: My custom work includes the careers experience, screening, skill matching and shift workflows. Odoo supplies core recruitment and employee models; adapted community modules support other parts of the platform.

The homepage image is from the public MIDAS website. Application and operations screens use fictional demonstration records. Open any visual to inspect it in full.

Next projectQuotation platform Formulas, costing and approvals

From applicant to everyday operations.