licksoft
Job seekers Hire talent →
Home/Selected work
Selected work

Two engagements, described properly.

What the requirement was, what we actually did about it, and what the client was left with. Client names are withheld under the confidentiality terms we sign on every engagement.

Financial services

Four senior developers on the floor before the audit window closed.

A national mortgage lender had a fixed regulatory reporting date, a platform team four senior engineers short, and an internal search that had already run two months without a single hire.

Client
National mortgage lender
Engagement
Contract staffing
Time to fill
14 days
Consultants placed
4 senior engineers

The challenge

The reporting deadline was set by the regulator and could not move. Internal recruiting had been screening generalist .NET and Java applicants for eight weeks, and every shortlist stalled at the same point: candidates could code, but none had worked inside a mortgage servicing platform before.

Onboarding a developer with no domain background would have consumed four to six weeks of ramp-up the client did not have.

Our approach

We ran a calibration session on day one with the engineering manager and the compliance lead together, so the requirement reflected the audit obligation rather than a generic job description.

  • Searched our existing consultant bench first rather than posting the role cold
  • Screened for prior mortgage or lending platform exposure before assessing technical depth
  • Presented four profiles with written notes on domain fit, not forwarded resumes
  • Ran interview scheduling and feedback collection daily to stop candidates going cold

The results

  • All four consultants offered, cleared and onboarded inside two weeks
  • The client met the regulatory reporting deadline
  • Two of the four extended into longer engagements after the initial term
  • No permanent headcount added to hit a temporary peak
14
Days to fill
4
Senior roles
2
Later extended
Insurance

Regression testing moved from a manual pass to a pipeline run.

A personal lines carrier was shipping state compliance changes to its agent portal with no automated regression coverage, which made small regulatory updates disproportionately expensive to release.

Client
Personal lines carrier
Engagement
Embedded QA team
Duration
Multi-sprint
Handover
Suite retained in-house

The challenge

Every release needed a full manual test pass across policy, coverage selection and billing. A one-line rate change carried the same testing cost as a major feature, so the team batched regulatory updates and shipped late.

The client wanted automation but had no capacity to build it while also keeping up with the compliance calendar.

Our approach

We embedded automation engineers alongside the existing developers rather than running a separate testing workstream, so the suite was built against the code as it actually behaved.

  • Mapped the critical paths through policy, coverage selection and billing first
  • Built regression coverage around those flows before widening scope
  • Added smoke tests to catch breakage on the highest-traffic journeys
  • Documented the suite and trained the in-house team throughout, not at the end

The results

  • Regression moved into the delivery pipeline instead of a manual pass
  • State compliance changes became a routine release rather than a project
  • The suite and its documentation stayed with the client's own team
  • No downtime windows required during rollout
3
Core flows covered
0
Downtime windows
100%
Suite handed over

Client names and identifying details are withheld under the confidentiality terms we sign with every client. Named references can be arranged during a procurement process. Figures relate to the engagement described and are not a promise of comparable results elsewhere.

The pattern

What these have
in common.

01

We start from what exists

Both of these built around working systems rather than replacing them. Rip and replace is occasionally right, but it is rarely the fastest route to the outcome you asked for.

02

The team hands over

Test suites, documentation and process knowledge stay with your team when the engagement ends. You should not need us to keep the result running.

03

Domain screening comes first

For regulated sectors we screen for prior domain exposure before technical fit, because the ramp-up on compliance context is the longer of the two.

Tell us the role. We will send names, not a brochure.

One call, one requirement sheet. We come back with screened people and a realistic timeline, or an honest answer that we are not the right fit.

Start a requirement →