Leadership & team
Six seats own delivery at Sedwis. Here is what each one is answerable for — so you know who to ask, and who to hold to it.
No juniors billed as seniors.
The engineer named in your proposal is the engineer who writes your code. We don't run a bait-and-switch where a senior wins the work and a first-year does it. If we need to bring someone junior onto a project to grow them, they're additional to the quoted team and you aren't charged for them.
Who owns what
Profiles pending — roles are real, names are not yet published
The remits below are the actual structure of the company. We have deliberately not filled these with placeholder names, photographs or LinkedIn links: an invented colleague is a fabricated person, not sample content, and the name would belong to somebody real. Profiles appear here as each seat is confirmed for publication.
Profile to be published
Owns the company's direction and sits in the first conversation on every engagement. Signs off scope and price personally, which is why quotes come back with reasoning rather than a number.
Profile to be published
Accountable for what ships and for the standard it ships at. Sets the architecture on every project above a certain size and runs the code review culture the careers page describes.
Profile to be published
Owns the two-week cadence — the sprint demos, the shared board, and the weekly status. When a project is late, this is the seat that tells you before you have to ask.
Profile to be published
Owns model selection, evaluation and cost. Decides when an LLM is the right answer and — more usefully — when it isn't, which is the judgement most AI vendors don't offer.
Profile to be published
Owns the interface and the research behind it. Every product screen goes through this seat before it goes to build, so design isn't a coat of paint applied at the end.
Profile to be published
Owns deployment, uptime and the answers on the security questionnaire. Runs the practices published at /security, and is the person your procurement team ends up talking to.
How delivery is organised
Engineers sit on project teams, not in departments. The disciplines below describe where depth lives — not who is allowed to talk to whom.
Full-stack engineers who own a feature from schema to interface. No throwing work over a wall between front and back end.
Flutter and React Native for cross-platform, native Swift and Kotlin where the product genuinely needs it.
Retrieval systems, evaluations, fine-tuning and the pipelines that feed them. Also the boring, essential work of data cleaning.
Interface and interaction design, plus the design system work that keeps a product coherent as it grows.
Automated coverage on the paths that matter and manual testing on the ones that can't be automated. Not a phase at the end.
CI/CD, observability, cost control and the incident response you hope never to need.
We hire for judgement, not years. If you'd rather own a surface than work a ticket queue, the roles are worth a look.