Firmware Development for Premium Motorsport Device

We’re building a premium motorsport device. We need a hands-on firmware freelancer to help bring our first prototypes to life and then carry it through to production. You’ll work at the same time as our PCB is being built, help us get a bench demo running, and support early on-car tests.

This starts as a paid trial to prove fit. If it goes well, we want you on the team long-term.

What you’ll do

Work with our hardware designer while the board is still being made so the software and hardware come together smoothly. Work with our design and software team on getting the app and the design on point on the device to match the app.

Get a bench prototype turning on, showing a simple status screen, and talking to test signals.

Build a quick test mode so we can check the unit fast (does it turn on, show something, react to inputs, pass data).

Find and fix first-power issues, and write down what you did so we can repeat it.

Package your work so a teammate can build and run it without you sitting next to them.

What you need on your bench (must have)

You’ll start before our custom PCB arrives, so you must already have (or can quickly set up):

An STM32 dev board you know well, with a debugger (e.g., ST-Link) and a USB-to-serial dongle.

Power: bench power supply with current limit and a switch.

Vehicle data bus (CAN-FD) test setup (small adapter or dev board) with 120 Ω terminators and short cables.

A screen to prove “first pixels”:

Minimum: a small plug-in screen you can draw text/graphics on.

Better: any LCD with a simple driver board to show a test/status page.

Bonus if you have LVDS gear; not required, but helpful.

Basic tools: multimeter, and access to a scope or logic analyzer.

A couple of buttons/LEDs/sensors for input→on-screen demos.

Optional but nice: inline USB power meter, electronic load, spare CAN nodes.

(We’ll share the right bits of our schematics under NDA so you can mirror the essentials on your bench.)

What success looks like

The unit (or your bench setup) starts cleanly, shows a basic screen, and responds to inputs without freezing.

We can see test data flowing through.

You provide a short video and a simple checklist proving it.

Problems come with a clear note of cause and fix.

How we work

Short calls, clear tickets, quick demos.

Direct line to our hardware designer and entire team.
We are strong collaborators

Full technical details after NDA. Publicly, we keep it high-level.

Quality & price rules

We buy quality and value. We expect fixed outcomes for fixed fees on the trial and milestones.

No scope creep: changes are small, agreed in writing, and priced before work.

Code must be clean, readable, and easy to hand over, with short “how to build/run” notes.

Strict No-AI-Coding policy

Human-written code only.

You’ll attest in writing that your code is not AI-generated.

We may review commits. If we find AI-generated code, the engagement ends.

Engagement & pay

Paid trial (fixed fee): bench “smoke test” + simple test mode + short video + basic notes.

If we both like how it’s going, we continue with fixed-fee milestones through prototype and beyond.

High performers become long-term team members as the product launches and grows.

What to send us (keep it brief)

Two examples where you got a brand-new device working (what it was, what you did, how you proved it).

A few lines on how you avoid the classic “black screen” during bring-up.

Your availability and fixed price for the trial.

A one-line attestation that you deliver human-written, non-AI code.

Any early risks you’d check on day one.

Privacy

Shortlist → quick intro call → NDA → trial kickoff.

Please keep our details private; portfolios and public posts should not include our specifics.

—

If you can turn a pile of parts into a reliable demo—and you already have the bench to start now—we’d love to hear from you.