> Markdown version of [/jobs/ext/4505478-senior-software-engineer](https://www.wearedevelopers.com/jobs/ext/4505478-senior-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer - **Company:** SEDNA INC. - **Location:** Denmark, SC, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Query Performance, Java (Programming Language), Adobe InDesign, Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Automation of Tests, Unit Testing, Software Quality, Code Review, Continuous Integration, Relational Databases, Java Virtual Machine (JVM), PostgreSQL, Oracle (Applications), Regression Testing, Standard Sql, Scala (Programming Language), Software Engineering, Postman, ReactJS, Technical Debt, Backend, Kotlin, Gitlab-ci, Playwright, Front End Software Development, Restful APIs - **Published:** November 2, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-software-engineer-denmark-sc--0608d10f-c3b4-4b44-a12b-4ce099e02382 ## About the Role Software Engineering, Operating Systems, Artificial Intelligence (AI), VMS Operating System, Billing, Cargo/Freight, REST (Representational State Transfer), Java, Amazon Web Services (AWS), Application Programming Interface (API), Essential experience Candidates typically bring three+ years of professional engineering experience from a comparable environment. Experience working on production systems where quality and reliability are important. Familiarity with a JVM language (Java, Kotlin, Scala) or a similar backend language, React or another modern frontend framework. Strong SQL and relational database skills, ideally Oracle or PostgreSQL, including query performance. Experience supporting production systems: diagnosing incidents from logs and metrics. Prior on-call experience is a plus. Critical skills A strong grasp of building and maintaining features within a larger system is helpful. Confidence with automated testing, CI/CD pipelines, and code review workflows is expected. Clear thinking, good problem-solving ability, and the capacity to work with domain-heavy logic contribute to success in the role. Experience with enterprise or workflow-driven applications is an advantage. Traits and mindset Curiosity and a willingness to learn the maritime domain are appreciated. A collaborative working style, comfort sharing ideas in cross-functional settings, and the ability to work independently when needed all support strong performance. Adaptability is important as the product and architecture continue to evolve. Core competencies Systems thinking, ownership of outcomes, strong communication skills, and effective collaboration are central to this role. A motivation to create value for customers and contribute to a stable, evolving platform is essential. ## Description The role includes participating in ongoing efforts to refine and modernise the platform. This involves contributing to technical upgrade work, improving system structure, and supporting longer-term architectural direction as the product grows. Opportunities exist to participate in design discussions and help shape solutions that improve system performance, reliability, and extensibility. Quality, testing, and delivery practices The team maintains a focus on software quality. We combine unit tests, API regression tests (Postman) and UI tests (Playwright) with peer code review on every merge request. Releases are built and tested through GitLab CI/CD. We're actively improving here: getting more of our test suites running automatically in CI and making them reliable. Engineers who want to drive that, will have room to do it. Collaboration with product and customer-facing teams The role involves close collaboration with product managers through refinement, planning, and solution discussions. Engineers also interact with Customer Support on cases that need engineering input, and, for larger projects, join customer conversations to validate technical approaches. Continuous improvement and documentation We treat documentation, including API references, design decisions and runbooks, as part of delivering a change. Much of VMS's knowledge still sits with experienced team members, and capturing it in written, searchable form is an active priority. We also reserve time for technical debt and internal improvements. In your first 90 days, you can expect * Month 1: Build your understanding of Sedna's architecture and our products. Get set up with the VMS codebase, your dev environment and the release process, and ship your first changes. Meet your team, product manager and key customer-facing colleagues. Learn the maritime workflows our customers depend on. * Month 2: Take ownership of a well-scoped piece of work from refinement with product through to release. Contribute to design discussions, give timely and constructive code review feedback. Shadow the on-call rotation and get familiar with runbooks and production tooling. * Month 3: Lead the technical approach on a complex feature or improvement within your team, working independently and raising risks and dependencies early. Join the on-call rotation. Contribute improvements to tests, runbooks or documentation based on what you found hard to learn, and support technical validation in a customer conversation where relevant.