Senior Software Engineer

ABOUT DATSUGI Datsugi is a small but growing data engineering and system integration consulting firm. You would be our first senior hire, and the person who owns the overall architectural approaches to system integration as we develop to become a key data player in Europe. We connect the systems companies run on (ERPs, accounting tools, CRMs, data warehouse and in-house platforms) so their data moves reliably, without manual work. Our focus are unified data warehouses, integrating legacy installations and modern cloud APIs into a single view. THE ROLE You will become the technical owner of our largest production system, then take on a second product. This is an architect's role with real delivery and real clients, not a slide-deck architecture job.
• First product: a production system integration platform. It connects various ERPs and accounting systems through on-premise local agents and cloud API connectors. It is already live and is growing as new connectors are added every month. You take over its day-to-day technical leadership, its client relationship on the technical side, and its architecture roadmap.
• Second product: data warehouse for manufacturing SMEs. Once the first platform is stable in your hands, you take on a second one, and implement its architecture with the same standards. This is a new product that will require coming up with a new architecture from scratch, learning from the lessons of previous projects and continuously improving it month over month. You will report directly to the founder who is technical. You will have real authority over technical decisions, and you will be expected to use it. WHAT YOU'LL WORK ON The work is systems design and architecture for a large-scale sync application: moving business data reliably between systems that were never designed to talk to each other. Some run on-premise inside client networks, others are modern cloud services, others more require reverse proxies — the architecture has to treat all of them as first-class.
• Hybrid architecture — components that run on machines we don't control
• Reliable sync — idempotent operations, retries, conflict resolution and full observability
• Legacy data — old schemas, inconsistent records and drift you have to design around
• Extensibility — a model where each new system is cheaper to add than the last The wider stack is a monorepo:
• Backend: Python, FastAPI on Cloudflare Python Workers, Hono on Cloudflare Workers (TypeScript)
• Frontend: TypeScript, React, MUI, Astro
• Data: Cloudflare D1, Durable Objects, KV, SQL Server, PostgreSQL (PlanetScale)
• Systems: Windows Server, Linux VMs (Fly.io)
• Engineering: GitHub, Linear
• AI: Claude Code We use Cloudflare technologies heavily, but also expand onto AWS where necessary. Claude Code is normal part of our development process but we expect clear systems design thinking WITHOUT use of AI. Claude Code is meant as an accelerator — not a decision-making tool. RESPONSIBILITIES We expect you to own the platform within month 1, and to be shaping the second product by month 4.
• Weeks 1–2: learn. Get to know the codebase, the architecture and the client's workflows alongside the founder. Observe potential improvements along the way.
• Weeks 3–4: stabilise. Design architectural improvements that would provide immediate benefits (e.g. cost cutting, better performance, higher reliability). Start taking over maintenance.
• Months 2–3: lead and improve. Become the client's main technical contact and run the monthly scope reviews. At the same time, make real weekly decisions to improve the platform.
• From month 4: maintain and grow. Keep the platform healthy, deliver new functionality from the backlog, and work with the founder to expand its footprint. Start architecting the second product. Ongoing, you will:
• Own architecture decisions and keep them written down
• Design and build new integrations, from on-premise to cloud
• Talk directly with client stakeholders, in English, about scope, risks and priorities
• Keep systems secure and GDPR-compliant, including components running inside client networks
• Set the engineering standards future hires will work to WHAT WE'RE LOOKING FOR You have designed integration systems that ran in production for years, and you have demonstrably fixed and / or improved the ones other people designed. Must have
• 5+ years in software engineering, with at least 1 in a technical lead role
• Strong C#/.
NET, including services that run on Windows Server
• Strong Python and TypeScript knowledge
• Deep SQL Server, relational data modelling experience and NoSQL experience
• Comfortable owning a client relationship on the technical side, in fluent English
• Works independently: you plan your own week, flag risks early and document everything Nice to have
• Built data integrations or sync systems: retries, idempotency, conflict handling, observability
• ERP, CRM or accounting system experience (e.g. NetSuite, HubSpot, Salesforce, Xero)
• Cloudflare Workers or other edge / serverless platforms, e.g. AWS Lambda
• Experience with ELT tooling, batch processing, real-time processing and data warehousing HOW WE WORK AND

WHAT WE OFFER
You work to clear monthly goals, not timesheets. You decide how to get there, with direct access to the founder and no layers of management in between.
• Contract: 6-month fixed contract, then 1-2 years based on performance
• Compensation: €48k to €60k gross depending on experience – we pay out in EUR
•

Location:
Fully remote (must manage your own taxes) or within Italy (must be Italian resident)
• Hours: Full time; on call for the production systems you own
• Tools: the hardware and software you need, including IDE, AI, and a company laptop
• Growth: as Datsugi grows, we expect you to grow into leading its engineering team

HOW TO APPLY
Send your resume and a short note on why you would like to apply. In the note, describe one system you designed or rescued that is similar to the ones above — the more detailed the better. The process has 4 steps, usually within 3 weeks:
• A 1–hour call with the founder to assess your systems design thinking.
• A 45-minute practical code session: we give you a challenge to think through live and you write code live, describing your thought process out loud and why your solution is ideal.
• A 45-minute business context conversation, assessing how deep your understanding of the domains we treat is and whether you would fit within our consulting culture.
• A final 30-minute conversation about scope, compensation and start date. Please apply directly and we can schedule your first interview call. We're looking forward to hearing from you