Engineering Services

Engineering depth, down to the driver.

From Windows kernel drivers and ARM devices to modern C++ migrations and libraries an OEM no longer supports, our engineers take on the work that needs real systems knowledge, and can join your team as dedicated capacity.

Illustration of a Windows driver stack with test resultsA driver stack runs from the application through a user-mode driver built on UMDF and a kernel-mode driver built on KMDF to firmware and an ARM system on a chip. Driver Verifier, static analysis and power-transition tests have passed and a 72-hour stress run is in progress.Device driverBuild 1.4.2ApplicationUser modeUser-mode driverUMDFKernel-mode driverKMDFFirmwareBoot and powerARM system on a chipHardwareChecksDriver VerifierStatic analysisPower transitions72-hour stress runIllustration of a Windows driver stack with test resultsA driver stack from the application through UMDF and KMDF drivers to firmware and an ARM chip, with test results below.Device driverApplicationUser modeUser-mode driverUMDFKernel-mode driverKMDFFirmwareBoot and powerARM system on a chipHardwareDriver VerifierStatic analysisPower transitions72-hour stress

Problems we solve

Sound familiar?

  • Finding it hard to migrate to the latest C++ standards?

    We'll help you with a risk assessment and a plan to get there.

  • Stuck with an OEM that no longer supports its libraries?

    We'll help you fix them.

  • Need systems engineers faster than you can hire them?

    We'll help you with dedicated engineers who join your team.

What we deliver

Work that needs real systems knowledge.

  • Windows driver development

    Kernel-mode and user-mode drivers on the Windows Driver Frameworks, KMDF and UMDF.

  • Embedded and IoT on ARM

    Software for ARM-based processors, from device code to the data it sends upstream.

  • Modern C++ migration

    Codebases moved to the latest C++ standards, starting with a risk assessment and a staged plan.

  • Unsupported OEM libraries

    When a vendor stops supporting libraries you depend on, we maintain, patch or replace them.

  • Product engineering

    Complete product builds across UI, database and application layers.

  • Dedicated engineers

    Engineers from P-CS working inside your team, on your roadmap and in your tools, with senior oversight from us.

Modern C++ migration

Assess the risks. Then migrate in stages.

Moving a large codebase to C++17, C++20 or later is rarely one change. We find what will break, rank it, and plan the migration in stages that keep your product shipping.

An example of the risk register we produce.

Risk register · ExampleC++11 to C++20

Migration risks for a Windows desktop application

  • High
    Removed language features in useauto_ptr, dynamic exception specifications and similar, replaced module by module with tests around each change.
  • High
    Vendor binaries built for an old toolchainRebuilt where source exists, otherwise wrapped behind a stable interface or replaced.
  • High
    Undefined behaviour exposed by newer compilersSanitizers and static analysis in CI before each stage goes live.
  • Medium
    Stricter conversions and new warningsFixed in bulk with automated refactoring, then warnings treated as errors.
  • Low
    Build scripts tied to one compilerMoved to a portable build definition.

Unsupported OEM libraries

When a vendor stops supporting a library, we don't.

Products often depend on drivers, SDKs and libraries from an OEM that has moved on. We choose the least disruptive way forward and write down why.

Maintain

Keep the library building and running on current compilers and operating systems.

Patch

Fix defects and security issues, in the source where you have it and at the boundary where you don't.

Wrap

Put a stable interface in front of it, so the rest of your product stops depending on its internals.

Replace

Move to a supported or open alternative in stages, behind that same interface.

Dedicated engineers

Capacity inside your team, with our oversight.

Our engineers work on your roadmap, in your tools and to your process. A P-CS principal reviews their work and stays accountable for it.

  1. Match

    We propose engineers whose experience fits your stack and your problem.

  2. Onboard

    They join your repositories, tickets and ceremonies from the first week.

  3. Deliver

    Work lands in your sprints, with code review and design input from a P-CS principal.

  4. Review

    A monthly review of output and fit, with billing on the same monthly cycle.

At a glance

Technologies
  • C and C++
  • KMDF
  • UMDF
  • Windows SDK
  • MFC
  • .NET and C#
  • ARM
  • IoT
Industries
Ways to engage

Let's talk about what you're building.

Tell us about the system, the problem or the decision in front of you. A principal reads every enquiry and replies personally.