Discipline 03
Two disciplines, one engineer.
Aerospace and technical engineering alongside software and digital aviation products — because aviation problems rarely sit cleanly on one side of the hardware/software line.
What this is
Built by someone who has to use it afterwards.
A great deal of aviation software is written by teams who have never operated to the process they are automating. It shows: forms that take twenty minutes, reports nobody reads, and workflows quietly bypassed within a month.
The same is true in reverse on the technical side. Modifications get scoped without anyone asking how the aircraft is actually flown, and the answer arrives as a surprise during implementation.
Working both sides is the whole argument here. PlaneSell is the clearest evidence — a production marketplace designed, built and operated in-house rather than a portfolio piece.
Scope
What the work covers.
Technical assessment
Airframe, systems and installation questions answered by someone who also operates the aircraft.
Modification scoping
Working out what a change actually involves before it becomes a project with a budget attached.
Airworthiness documentation
The paperwork trail that has to exist around a technical change, written to be traceable.
Operations / maintenance interface
The seam between flight ops and engineering, where most avoidable findings originate.
Digital aviation products
Aviation software built end to end by someone who has to use it afterwards.
Operational tooling
Replacing spreadsheet-and-email processes with systems that keep their own audit trail.
Data and workflow
Structuring operational data so it can be reported on rather than re-entered.
R&D and prototyping
Research and prototyping support for innovation projects that need aviation domain depth.
Tell us what needs to happen.
Describe the operation, the standard you are working to, and the deadline. We reply within one working day.