You have opted out of job matches in .
To undo this, go to the 'Skills and Interests' section of your preferences.
Shared by 
8 days ago
warning
Heads-up
Requirements and responsibilities
About SweedSweed is building an all-in-one cannabis retail platform used by dispensaries across the United States.Our platform combines POS, eCommerce, Marketing, Analytics, Inventory Management, and customer engagement tools into a single ecosystem, helping retailers operate more efficiently and grow their businesses.Today, our team consists of 200+ people working remotely around the world. Product and engineering teams collaborate closely with our US-based business teams to build and scale the future of cannabis retail.About the TeamYou’ll join the OMS (Order Management System) team, one of the core engineering teams behind our e-commerce platform.The team owns critical customer-facing flows, including:order management and order lifecyclecheckout and purchase flowsuser accounts and authenticationorder status managementcustomer-facing APIsintegrations with other e-commerce servicesThe team works closely with other e-commerce teams across the platform, and engineers often collaborate beyond their immediate product boundaries.What You’ll DoDesign and develop backend services within our microservices ecosystem.Build and improve APIs used by internal and external customers.Participate in architectural discussions and technical decision-making.Refactor and optimize existing services.Improve performance, reliability, and maintainability.Review code and share engineering best practices.Collaborate with engineers across multiple product teams.What You’ll Be Working OnSome of the team’s current initiatives include:building and expanding our Public API platformimproving performance and reducing latency across critical customer journeysrefactoring cart and checkout servicesimproving system observability and metricsevolving parts of our monolith into independent servicesmoving synchronous communication toward asynchronous patternsoptimizing caching strategies and reducing cache-related issuessupporting CMS capabilities for e-commerce experiencesTech StackC#, .NET 8+, ASP.NET Core, Microservices, gRPC, MS SQL, PostgreSQL, RabbitMQ, Redis, SignalR, EF Core, Dapper, Docker, Kubernetes, AWS, Grafana, Git, GitLab CI/CD.What We’re Looking For5+ years of backend development experience.Strong commercial experience with C# and .NET.Experience building and maintaining production systems.Experience with microservices architectures.Strong knowledge of relational databases.Experience with RabbitMQ or similar messaging systems.Experience working with Redis or other caching solutions.Ability to troubleshoot performance and production issues.Experience making technical decisions and owning solutions.Good communication skills and collaborative mindset.English level sufficient for written communication and occasional calls with international teammates.Experience using AI tools in software development workflows.Nice to HaveExperience with high-load systems.Experience in e-commerce, payments, checkout, or order management domains.Experience decomposing monolithic applications.Experience with asynchronous architectures.Kubernetes and CI/CD experience.Experience improving observability and monitoring.What Matters Beyond TechnologyOwnershipWe’re looking for engineers who can independently drive solutions and make technical decisions.CommunicationStrong collaboration skills are important. We value people who communicate openly, share ideas, and work well across teams.CuriosityWe appreciate engineers who want to understand the product, not just complete tasks.AdaptabilityOur business moves quickly, and priorities can sometimes change rapidly. We value people who are comfortable working in a dynamic environment.Working StyleFully remote.Flexible schedule.Core collaboration hours are 10:00–16:00 CET, when the team overlaps for meetings, discussions, and collaboration.Outside of these hours, engineers have flexibility to organize their own working schedule.Two-week sprint cycles.Regular technical discussions, retrospectives, and planning sessions.The team also has a rotating weekly support duty approximately once every two months. During these weeks, engineers help investigate and route technical issues during normal working hours. This is not an on-call rotation.What We OfferCompensation in USD.B2B contract with a US company.100% remote work.Flexible working hours.20 paid vacation days.12 company holidays.3 sick leave days.Medical insurance after probation.Equipment reimbursement.Hiring ProcessRecruiter Call (45 minutes)Introduction, role overview, experience discussion, English check.Technical Interview (90 minutes)Live coding and technical discussion.No algorithmic tasks.Backend System Design (60 minutes)Architecture discussion and problem-solving session.Team Introduction (Optional)An opportunity to meet future teammates and learn more about the team.
Optionally, you can add more information later (benefits, pre-screening questions, etc.)