#shapingryd is one of our values, as we believe that transforming from Start-up to Scaleup can only be achieved together.
We trust that #bettertogether can only be achieved by you taking ownership from day one.
We want to have our employees with us for the long haul. You get a permanent employment contract, competitive salary and a company pension scheme.
As a Ryder, you work flexibly from home up to two days a week and enjoy three team days in the Munich office (S-Bahn Donnersberger Brücke).
Professional onboarding package and buddies: From day one, you will be part of our monthly onboarding and buddy programme. Special: In addition to a buddy from the team, you will get to know a buddy from another area of the company on your first day, which will make it easier for you to get started with us.
The professional and personal development of our Ryders matters to us. We recognise potential and enhance it. Join us and write your own success story.
Never Stop Learning! You will get a training budget per year that you can freely allocate to our professional development.
You want to work from anywhere for a change? With RydFlex you can work abroad for upto 6 weeks anywhere within the EU.
You work closely with partner-facing teams (business development, partner success, product) and engineering teams.
Conduct technical discovery with partners — understand their tech stack, architecture, APIs, authentication model, data requirements, and constraints.
Map the partner's business goals to technical integration requirements.
Identify potential integration blockers early: incompatible auth models, missing APIs, data format mismatches, latency constraints, compliance issues (GDPR, PCI-DSS).
Document the partner's current state architecture — what they have, what they need, what they can and cannot change.
Example: A fleet management SaaS wants ryd transactions in their dashboard. You analyze: Do they have a webhook receiver? Can they consume our Kafka events? Do they need pull (API) or push (webhook)? What data format do they expect? What's their latency tolerance? What auth do they use?
From ryd's catalog of integration approaches, select the best fit for the partner.
Justify the recommendation with technical reasoning — not just "this approach works," but "this approach works best because X, and here's why approach Y doesn't fit because Z."
When no existing approach fits perfectly, identify the gap and propose an adaptation or a new approach pattern — and feed it back to the System Architect.
Estimate integration effort, timeline, and risks.
Example recommendation: "For this partner, the Webhook Push approach is best because they already have a webhook ingestion pipeline. We'll map ryd's order.completed event to their fuel_expense schema. Auth via API key + HMAC signature verification. Estimated: 3 sprints for full integration."
Create the high-level integration architecture document: system context diagram, data flow diagram, sequence diagrams for key flows, component mapping.
Define the API contract: request/response schemas, event payloads, error codes, rate limits, idempotency keys.
Specify the authentication and authorization model: OAuth 2.0, API keys, mTLS, JWT — whatever the partner's context requires.
Define the error handling and retry strategy: what happens when the partner's system is down? When our system is down? When data is malformed?
Specify non-functional requirements: latency SLAs, throughput, data retention, logging, monitoring.
Create low-level technical design for the integration: which ryd services are involved, which APIs are called, which Kafka topics are consumed/produced, which databases are read/written.
Build proof-of-concept integrations to validate the architecture before full development.
Write integration test suites — simulate the partner's system, test the integration end-to-end.
Create sandbox configurations for the partner to test against.
Demonstrate the POC to the partner and to ryd's engineering team.
Hand off the validated architecture to the development team with clear implementation guidance.
Provide structured feedback from every integration: what worked, what didn't, what the partner needed that wasn't in the catalog.
Identify patterns across integrations: "Three fleet SaaS partners all needed the same data enrichment step — this should be a platform capability."
Suggest improvements to integration approaches based on real-world usage.
Contribute to the integration catalog — when you create a new approach or adaptation, document it for reuse.
Participate in architecture reviews — share learnings with other Solution Architects and the System Architect.
Present integration architectures to partners' technical teams — clearly, confidently, and in their language.
Translate between partner business needs and ryd technical capabilities.
Manage technical expectations — be honest about what's possible, what requires compromise, and what's out of scope.
Support pre-sales activities — provide technical credibility in partner meetings.
Contribute to partner-facing documentation — integration guides, API references, best practices.
5+ years of software engineering experience, with at least 2 years in a solution architecture, technical consulting, or integration engineering role.
Strong analysis and design skills — you can look at a partner's system, understand it quickly, and map integration points.
Hands-on coding ability — you build POCs, write integration tests, and validate your architecture with working code (Node.js/TypeScript preferred).
API design expertise — REST, GraphQL, webhooks, event-driven patterns. You know when to use each and how to design them well.
Communication and presentation skills — you can whiteboard an integration architecture for a partner's CTO and also write clear technical documentation.
Stakeholder management — you've worked directly with external partners, customers, or clients.
Cloud-native understanding — you understand microservices, containers, message queues, and the patterns that make integrations reliable.
Willingness to continually learn AI (Must) — you use AI tools in your daily work, you understand AI-assisted development, and you actively explore how AI can improve partner integrations.
Hands-on, get-things-done attitude — you don't wait for perfect information. You build a POC, test it with the partner, and iterate.
Integration experience — you've integrated systems with external partners before. You know the pain points, the patterns, and the pitfalls.
Fintech or payment processing experience — understanding of payment flows, PCI-DSS, and financial data handling.
B2B SaaS experience — you've worked with business customers and understand B2B integration patterns.
Fleet management or mobility domain knowledge — fuel cards, fleet expenses, EV charging, telematics.
Node.js / TypeScript experience — ryd's backend stack.
Experience with Kafka or event-driven architectures — ryd's event bus.
Experience with multiple integration patterns — you've done API integrations, webhook integrations, SDK integrations, embedded/iframe integrations, and file-based integrations.
Experience with OAuth 2.0, OpenID Connect, and API security patterns.
AI practical experience (Plus) — you use AI coding assistants to accelerate your POC development and documentation.
Confident communication in English.
This is a remote position with the requirement that you live in Portugal or Germany.
#shapingryd is one of our values — you directly shape how partners experience ryd.
We trust that #bettertogether can only be achieved by you taking ownership from day one.
Permanent employment contract and competitive salary.
Flexible working hours and home office.
Training budget per year for professional development.
Opportunity to work with diverse partners — fintech, fleet SaaS, ERP, automotive, and more.
EGYM Wellpass