Software Architect

The Collaboration

As the Architect for the Marketplace Platform, you will set the technical direction for our core products, including Acute Care and our next-generation Credentialing systems. Your primary focus will be improving platform modularity and reducing tight coupling within our current architecture. You will help ensure consistency and reliability across our teams, supporting more effective management of complex logic while identifying "quick wins" to reduce technical risk and operational exposure.

We're looking for a collaborative architect who believes in engineer-led architecture and uses documentation as a key tool for alignment. You're comfortable making timely decisions backed by clear technical rationale and risk assessment. Rather than relying on veto power, you use your ability to influence and align multiple development teams working in parallel. You value different perspectives, enjoy solving complex structural puzzles, and are focused on driving cross-team collaboration.

Location

You must be located in Poland to be considered for this position.

Scope of Services

• Set the technical direction for the Marketplace Platform, ensuring architectural consistency across our core products and new versions.

• Improve modularity by identifying and reducing tight coupling within our current systems to make changes safer and more scalable.

• Drive strategy and service design, creating a roadmap that addresses immediate pain points while reducing long-term technical risk.

• Influence and align multiple development teams through clear technical rationale and documentation (RFCs/ADRs) rather than veto power.

Technical Profile

• A strong background as an Architect or Principal Engineer, with a focus on system design over specific languages, and a proven track record of improving modularity and decoupling complex systems.

• Deep experience in a major cloud environment (AWS or Azure), including designing core services and leveraging Infrastructure as Code (IaC).

• Solid understanding of messaging patterns (e.g., Kafka) and document-based databases, with the judgment to explain when to use specific patterns - and when to avoid them.

• The ability to decompose complex problems and secure buy-in from engineering teams and stakeholders through clear technical rationale and documentation.

• A proactive, engineer-led approach to architecture, guiding teams through technical shifts without relying on veto power.