EU remote
Staff Software Engineer
About this role
Shine is the financial copilot for entrepreneurs and small business owners. Founded by serial entrepreneurs Rico Andersen and Martin Hegelund, Shine is a leading European fintech unicorn on a mission to restore the joy of running a business, by ending wasted time on financial admin. Shine offers a connected solution for invoicing, accounting, payroll, business accounts, payments, and financing, meaning business owners can focus their energy on growing a healthy business, not held back by manual admin.
Part of something bigger Today we're part of Cegid, a European leader in cloud software for finance and accounting. Together we're building Europe's leading financial copilot for small businesses and their accountants. Shine already supports more than 400,000 small businesses. As part of Cegid, we now reach over one million small businesses and 15,000 accountants across Europe. We're a multicultural team working from France, Germany, Denmark and the Netherlands, contributing to a wider European network that spans Spain, Portugal.
Your hiring experience matters Just as we respect our customers' time, we respect yours. Your experience with Shine and Cegid should feel simple, transparent and genuinely supportive. If this sounds like somewhere you want to grow, we'd love to hear from you. The ERP Engineering Team at Shine We're a fast-growing engineering team on a mission to build the best ERP for Small Businesses in Europe. We work in a domain-based structure, where each domain has real ownership over its area — from architecture to quality and technical roadmap.
Your Role as a Domain Engineer As a Domain Engineer, you're the technical reference for the product: you define architecture direction, ensure engineering standards, and work closely with team managers and Senior Engineers to make sure technical decisions serve the business goals. This is a senior IC role, focused on cross-cutting technical impact, not people management. We're modernizing our stack and expanding into new markets, which means real problems around scale, multi-tenancy, and domain complexity — not greenfield, but not paralyzing legacy either.
What You'll Do Own the target architecture of your domain and the realistic path to get there. Ensure reliability, scalability, security, and compliance are design constraints from day one, not afterthoughts. Maintain living architecture documentation (C4 model diagrams, ADRs) as part of the engineering workflow. Set and calibrate design review thresholds, delegating to senior engineers as their judgment grows. Spend roughly half your time embedded with engineering teams, and half on cross-engineering work — standards, the Golden Path, and the Architecture Forum.