Company Description
Integrated Aviation Solutions is a technology-focused company dedicated to improving efficiency, safety, and reliability across the aviation sector. The organisation delivers software solutions and integrated systems that support airlines, airports, and aviation service providers in managing complex operations. By combining industry knowledge with advanced engineering practices, Integrated Aviation Solutions helps clients optimise workflows and data usage.
What you'd own
- Architectural decisions across the platform — runtime type systems, workflow engines, configuration compilation, multi-tenancy boundaries. The big structures that everything else builds on.
- Design for configurability. Our customers define their own permit types, workflows, and approval chains. You'd shape how that configuration space works, what's extensible, what stays locked down, and where the platform draws the line.
- Cross-module integration. Changes that touch the ORM layer, API surface, and Angular frontend simultaneously. The kind where getting one layer wrong breaks customers silently.
- Design standards and patterns. When someone asks "how should we handle this?" — permissions, async operations, state transitions — you decide and document the pattern. Those patterns are what every engineer and model here builds from.
- Reviewing designs before code. Most work starts as a written proposal. You'd review for architectural coherence, edge cases in the design itself, and whether it stays within the platform's constraints and philosophy.
What we need
- Bachelor’s degree or higher in Computer Science, Software Engineering, or a related field, or equivalent practical experience.
- Experience in aviation, transportation, or mission-critical systems is a plus.
- You have made architectural decisions on a system serving real customers and remember what broke.
- You think about extensibility, constraints, and how to make configuration spaces work. You can explain why you chose one design over another.
- You write specifications other people can build from. This role writes prose as often as code.
- You understand how large language models behave in practice: context limits, tool use, why they hallucinate, and how written specs and conventions ground them.
- You know agentic loops: plan, act, verify, repeat. You can design the checks, guardrails and stop conditions that keep a loop honest, and you know when to split work across subagents.
- You work with AI tooling daily and are hard to fool.
- You know C#/.NET and a modern component framework well enough to judge the code that gets written, whether by a person or a model. Typing speed is not the point.
Nice, not necessary
- Real SQL fluency, or cross-engine experience, or a genuine grasp of why portability is an engineering constraint.
- NHibernate specifically. ORM fluency plus a willingness to read the mappings is enough.
- Regulatory, government or aviation domain experience.
- Multi-tenant SaaS or runtime-configurable product experience.
- Experience building agent tooling, MCP servers, or internal developer platforms.
Team
You would report to a manager and work alongside other engineers, with direct access to the people running the authorities we serve.
This role is not for you if
- Your first instinct on a mature codebase is a rewrite.
- You want to avoid writing documentation and specifications.
- You would rather ship quickly than leave the codebase safer than you found it.
- You want a clean, small, single-engine system. This is not that, and pretending otherwise would waste your time and ours.
