Senior Software Engineer (Remote)

C Teleport; Netherlands; Remote; EUR 80,000 - 120,000; Full time

Job summary

C Teleport is seeking a Staff Software Engineer to own a component end-to-end, ship production-ready code, and keep systems healthy in a remote-first, CET-overlap team.

You’ll mentor others, translate business needs into solid technical plans with Product, and apply OOD/TDD/SOLID/CQRS to drive platform improvements in a multinational, travel-industry context.

Qualifications

• Independent ownership of a production component or service.
• Turn a business requirement into a technical plan with Product.
• Mentor teammates and raise others' skills through example.

Responsibilities

• Own a component or service in production and keep it healthy.
• Turn business needs into a technical plan with Product.
• Mentor teammates and share knowledge.
• Deliver what you commit and flag slips early.
• Work within ±2 hours of CET for team overlap.

Skills

Production ownership

C#/.NET

AI coding agents

OOD design

Test-driven development

SOLID principles

CQRS

Analytical skills

Mentoring

Tools

NoSQL databases

RabbitMQ

Travel APIs

Job description

Reports to an Engineering Manager · Remote (working hours within ±2 hours of CET)

You\'ll own a slice of our platform outright, not just the tickets in it. Can you make the sound call, ship it, and leave the code healthier than you found it? Read on.

Why this role exists

We\'re growing Engineering\'s capacity. As the platform and team scale, we need engineers who can take a component and run with it independently — spotting risks early and raising the people around them.

About C Teleport

We move maritime, aviation, and energy crews around the world, automating high-stakes travel that used to be run by hand. We\'re a lean, international company: small squads, real ownership, decisions made close to the work.

What you\'ll own

• A component or a slice of the system, independently. Make the technical calls, keep it healthy, and know it well enough to catch problems before they become incidents.

• Production. Ship what you build and keep it running for real users, not just "done" in a ticket.

• Requirements, not just tickets. Turn a business need into a clear technical plan with Product, and flag gaps early.

• Raising the bar around you. Teach what you know, exchange feedback across the team, and document so your team isn\'t stuck without you.

• Your own delivery, reliably. Deliver what you commit to, and flag a slip early.

• Making the team\'s practices better. Improve a process, tool, or approach that no longer fits.

Must-haves (these are gates)

1. You\'ve independently owned a component or service in production — you made the calls, kept it healthy, and were accountable when something broke.

2. You can turn a business requirement into a technical plan yourself, working directly with Product or another stakeholder.

3. You mentor as you go; you can point to specific examples of raising another engineer\'s skill or judgment.

4. You deliver what you commit to, and say so early when you won\'t.

5. You\'re comfortable working within ±2 hours of CET, for real-time overlap with the team.

6. 4+ years of hands-on .NET and C\#, as your active day-to-day language.

7. You actively use AI coding agents for implementation and code review. You can guide them effectively, critically assess their output, and take ownership of the resulting code.

8. You apply OOD, TDD, SOLID, and CQRS deliberately; the right pattern, not just the first one.

9. Strong analytical skills, proactive, and quick to pick up new concepts.

Nice-to-haves (bonus, genuinely not required)

• Experience working fully remote in a distributed team.

• A track record of landing a tool, pattern, or process change that became your team\'s standard.

• Experience owning a production incident end to end, including the postmortem and fix.

• Proficiency with NoSQL databases.

• Experience with message brokers (RabbitMQ or similar).

• Experience with Galileo, Amadeus, or other travel-industry APIs — a strong plus given our domain.

This is not…

• …an entry-level seat. You\'ll own a component early on, not a queue of pre-specified tickets.

• …a people-management role. No direct reports — your influence comes from your ownership and how much you raise the people around you.

• …the technical ceiling. The next step is Staff Software Engineer, owning a whole domain\'s technical direction. This is the runway to it.

Remote and working hours

Fully remote, with working hours within ±2 hours of CET/CEST for real-time overlap with the team. For operational and tax compliance reasons, this role is open exclusively to international applicants based outside the Netherlands.

What you get

• A remote-first setup, built for distributed work.

• A clear next step: Staff Software Engineer, owning a whole domain\'s direction.

Hiring process

1. Recruiter / HR call — role, motivation, and logistics.

2. Technical interview — a deep dive on how you\'ve owned production systems, plus a technical exercise.

3. Final call with the Engineering Manager you\'d report to.

Target: ~2–3 weeks end to end.

Pre-employment screening

If your application is successful, we may conduct a pre-employment screening through a trusted third party, in line with applicable laws. This may include employment history, education, and other relevant publicly available information to help us understand your suitability for the role.

Equal opportunity and privacy

C Teleport is an equal-opportunity employer. We assess every application on merit and handle your data in line with GDPR.