Build the platform you would want to learn on

What you will do

• Design and ship backend services with clear data contracts and migrations.
• Keep deploys small, reversible and boring; exercise rollback on ordinary days.
• Instrument request rate, error rate and duration for every endpoint you own.

What we look for

• Three or more years building and operating production services.
• Comfortable with SQL schema design, indexing and query analysis.
• A written record of decisions you have made and revised.

What you will do

• Implement editorial and product interfaces from a strict design system.
• Hold a real accessibility bar: keyboard paths, contrast, reduced motion.
• Measure and defend page performance budgets.

What we look for

• Strong React and TypeScript; comfort with SSR and routing internals.
• Portfolio showing at least one interface you designed and shipped.
• Care about detail at the pixel and at the interaction level.

What you will do

• Build evaluation harnesses with fixed seeds, pinned data and slice reporting.
• Take models from notebook to a served endpoint with measured cost.
• Review project briefs and the work submitted against them.

What we look for

• Production experience serving models, not only training them.
• Fluency with leakage, sampling and reproducibility failure modes.
• Clear writing; you will publish in the journal.

What you will do

• Run threat modelling sessions and turn each ranked risk into a test.
• Review authorisation on every server-side data path, not just the UI.
• Lead incident retrospectives and publish what changed.

What we look for

• Hands-on application security in a shipping engineering team.
• Fluent with authentication, session handling and row-level access rules.
• Calm, specific communication under incident pressure.

What you will do

• Interview engineers and shape their reasoning into publishable pieces.
• Hold the editorial standard: problem, constraint, outcome, trade-off.
• Maintain the journal's structure, tags and cross-links.

What we look for

• Published technical writing you can point to.
• Enough engineering literacy to read a diff and ask the right question.
• Reliable, self-directed cadence.

What you will do

• Programme quarterly build reviews and weekly challenges end to end.
• Moderate discussion spaces with published, consistent standards.
• Report on participation and act on what the numbers say.

What we look for

• Experience running a technical community or developer programme.
• Comfortable in engineering conversations without being the engineer.
• Organised in public: agendas, notes, follow-through.