Senior Software Engineer - Customer Engineering (Support)
⚲ Toruń, Bydgoszcz, Poznań, Gdańsk
25 000 - 35 000 PLN netto (B2B)
Wymagania
- C#
- .Net
- .NET C#
Opis stanowiska
RavenDB is a high-performance, transactional NoSQL document database running in production at companies worldwide, with a fully managed cloud (DBaaS) offering. We're an established, fast-growing and engineering-led company and we are currently looking for Software Engineer - RavenDB Support.
You will investigate complex production issues, reverse-engineer failures, analyze distributed system behavior, and dive deep into C# internals to uncover root causes.
Success in this role is measured not only by solving today's hardest problems, but by reducing the number of hard problems that reach support tomorrow. You will work closely with customers, developers, and product teams to turn insights from the field into lasting improvements across the organization.
Key Responsibilities:
•
Investigate & Diagnose: Tackle complex customer issues across RavenDB clusters, from log forensics to source-code-level root cause analysis.
• Log Forensics: Analyze large-scale distributed system logs to reconstruct incident timelines and draw definitive conclusions.
• Code-Level Debugging: Read and reason through C#/.NET internals to identify bugs, propose fixes and produce actionable bug reports for the core dev team.
• Technical Communication: Translate complex technical findings into clear, structured, and professional written explanations for clients.
• Broad Ownership: Handle a wide technical surface across the database ecosystem, including replication, indexing, memory management, ETL, backups, and client integrations.
• Navigate Ambiguity: Work independently on complex problems where the answer isn’t obvious, the evidence is incomplete, and you must decide when to escalate vs. when to call a theory confirmed.
• Customer Partnership: Work directly with customers to understand both the technical and business impact of issues, set expectations, communicate progress and guide investigations to successful outcomes.
• Process & Tooling Improvements: Identify recurring support challenges and proactively improve workflows, tooling, diagnostics, documentation, and automation to reduce resolution times and improve customer experience.
• Knowledge Sharing: Build and maintain internal knowledge, troubleshooting guides, postmortems, and best practices that enable the entire team to operate more effectively.
What We’re Looking For:
• Strong proficiency in C# and the .NET ecosystem (specifically understanding memory management, async programming, and concurrency) - 5+ years of experience
• Experience with distributed systems concepts (replication, consensus, networking).
• A "detective" mindset - someone who loves reading logs and tracking down elusive edge cases.
• Strong customer orientation with the ability to understand both the technical and business impact of an issue, ensuring customers receive the optimal solution within the appropriate timeframe.
• Excellent communication skills, capable of translating complex technical findings into clear, structured, and professional explanations for customers while setting accurate expectations and guiding them through the investigation process.
• A strong sense of urgency, ownership, and accountability, with the ability to prioritize effectively, make sound judgment calls, and drive issues to resolution without sacrificing technical quality.
• A proactive improvement mindset - someone who looks beyond individual issues, identifies recurring patterns and drives improvements in tooling, automation, documentation and processes.
• The ability to work independently on complex problems where evidence may be incomplete, balancing investigative depth with timely customer outcomes and knowing when to escalate versus when to confidently conclude an investigation.
You will investigate complex production issues, reverse-engineer failures, analyze distributed system behavior, and dive deep into C# internals to uncover root causes.
Success in this role is measured not only by solving today's hardest problems, but by reducing the number of hard problems that reach support tomorrow. You will work closely with customers, developers, and product teams to turn insights from the field into lasting improvements across the organization.
Key Responsibilities:
•
Investigate & Diagnose: Tackle complex customer issues across RavenDB clusters, from log forensics to source-code-level root cause analysis.
• Log Forensics: Analyze large-scale distributed system logs to reconstruct incident timelines and draw definitive conclusions.
• Code-Level Debugging: Read and reason through C#/.NET internals to identify bugs, propose fixes and produce actionable bug reports for the core dev team.
• Technical Communication: Translate complex technical findings into clear, structured, and professional written explanations for clients.
• Broad Ownership: Handle a wide technical surface across the database ecosystem, including replication, indexing, memory management, ETL, backups, and client integrations.
• Navigate Ambiguity: Work independently on complex problems where the answer isn’t obvious, the evidence is incomplete, and you must decide when to escalate vs. when to call a theory confirmed.
• Customer Partnership: Work directly with customers to understand both the technical and business impact of issues, set expectations, communicate progress and guide investigations to successful outcomes.
• Process & Tooling Improvements: Identify recurring support challenges and proactively improve workflows, tooling, diagnostics, documentation, and automation to reduce resolution times and improve customer experience.
• Knowledge Sharing: Build and maintain internal knowledge, troubleshooting guides, postmortems, and best practices that enable the entire team to operate more effectively.
What We’re Looking For:
• Strong proficiency in C# and the .NET ecosystem (specifically understanding memory management, async programming, and concurrency) - 5+ years of experience
• Experience with distributed systems concepts (replication, consensus, networking).
• A "detective" mindset - someone who loves reading logs and tracking down elusive edge cases.
• Strong customer orientation with the ability to understand both the technical and business impact of an issue, ensuring customers receive the optimal solution within the appropriate timeframe.
• Excellent communication skills, capable of translating complex technical findings into clear, structured, and professional explanations for customers while setting accurate expectations and guiding them through the investigation process.
• A strong sense of urgency, ownership, and accountability, with the ability to prioritize effectively, make sound judgment calls, and drive issues to resolution without sacrificing technical quality.
• A proactive improvement mindset - someone who looks beyond individual issues, identifies recurring patterns and drives improvements in tooling, automation, documentation and processes.
• The ability to work independently on complex problems where evidence may be incomplete, balancing investigative depth with timely customer outcomes and knowing when to escalate versus when to confidently conclude an investigation.
🔍 Dekoder Ogłoszenia
🔴
reverse-engineer failures
Będziesz musiał analizować i odtwarzać problemy, które nie są łatwo powtarzalne, często bez jasnych przyczyn.
🔴
dive deep into C# internals
Oczekuje się od Ciebie bardzo głębokiej wiedzy o wewnętrznym działaniu .NET, a nie tylko umiejętności pisania kodu.
🟡
Success in this role is measured not only by solving today's hardest problems, but by reducing the number of hard problems that reach support tomorrow.
Twoim głównym celem jest zapobieganie problemom, a nie tylko ich rozwiązywanie, co może oznaczać potrzebę tworzenia nowych narzędzi lub procesów.
🟢
turn insights from the field into lasting improvements across the organization
Będziesz miał wpływ na rozwój produktu i procesy firmy, ale wymaga to proaktywności i umiejętności przekonywania innych.
🔴
Log forensics
Będziesz spędzał dużo czasu na analizie logów, często w poszukiwaniu subtelnych wskazówek dotyczących awarii.