Solution Architect (SA)

1. Role Summary

The Solution Architect (SA) is the central translator and design authority connecting Oncoshot’s pharmaceutical customers, hospital partners, and internal core development team. Customers award oncology-related studies to Oncoshot, and hospitals supply and own the clinical data that powers those studies. The SA converts these varied business outcomes and operational needs into a coherent set of functional and technical requirements, and then designs common core product capabilities that serve every hospital and customer on a single, unified platform.

Working across business and engineering, the SA harmonises study-specific and hospital-specific demands into reusable capabilities, defines the high-level requirements and user stories, and collaborates with the core-dev team through the sprint cycle to bring them to life. Success in this role is measured by how fragmented, one-off requirements are shaped into scalable common capabilities within the platform.

2. Key Responsibilities

• Bridge across stakeholders: Serve as the connective link between customers, hospital partners, and the internal core development team, ensuring alignment across all three.
• Translate customer study outcomes: When customers award studies to Oncoshot, translate the desired business outcomes into clear functional and technical capability requirements for the core-dev team.
• Translate hospital operational needs: Hospitals are the suppliers and owners of the data that supports studies. Translate their day-to-day operational needs, covering both executing the studies and supporting daily operations, into functional and technical capability requirements for the core-dev team.
• Harmonise into a single common product: The core-dev team builds new capabilities into one common platform for all hospitals. Reconcile the differing requirements across studies and hospital operations, and translate them into common core capabilities.
• Design and specify core capabilities: Design the common core capabilities and work directly with the core-dev team to specify high-level requirements as user stories, delivered iteratively through sprints.

3. Preferred Qualifications

• Bachelor’s or Master’s degree in Computer Science, Software/Systems Engineering, Information Systems, Biomedical Informatics, or a related field.
• 5+ years of working experience and at least 3+ years in solution architecture, systems analysis, technical product ownership, or a senior business/systems analyst role, ideally on multi-tenant or platform products.
• Experience in healthcare, clinical research, life sciences, or health-data domains is strongly preferred (e.g., EMR/EHR, clinical trials, real-world data, oncology, or registries).
• Familiarity with health data standards and privacy frameworks — e.g., HL7/FHIR, DICOM, ICD/SNOMED coding, and data-governance obligations such as PDPA/HIPAA/GDPR.
• Track record of writing clear user stories and functional specifications and working within Agile/Scrum sprint delivery.
• Working knowledge of modern software architecture (APIs, data models, integration patterns, cloud-based platforms, certified AWS or Azure architect).

4. Core Competencies

• Requirements translation: Ability to convert ambiguous business outcomes and operational needs into precise, buildable functional requirements.
• Architectural thinking: Designs for reuse and scale — abstracts many specific needs into a common core rather than point solutions.
• Stakeholder management: Communicates credibly with clinical, commercial, and engineering audiences and drives alignment among them.
• Harmonisation & prioritisation: Reconciles competing requirements and makes clear trade-off decisions in service of one shared product.
• Agile delivery partnership: Writes strong “user stories” and collaborates closely with engineers across sprints to ship the right capabilities at the right time by balancing studies dependencies and resource capacities.
• Domain empathy: Understands hospital operations and study workflows well enough to anticipate real-world constraints and data-governance concerns.

5. Success Measures (First 3 Months during Probation Period)

• Produced a clear baseline high-level solution/architecture of the current platform that the core-dev team is actively building against.
• Delivered a documented, prioritised backlog of common core capabilities derived from current studies and hospital operational needs.
• Successfully translated at least one capability needs into functional requirements and user stories and endorsed by core-development team into their sprints.

6. Working Model

• Probation period: First 3 Month probation period and conversion to permanent staff after passing the probation.
• Location & arrangement: Hybrid working, based in Singapore, with a mix of on-site collaboration and remote work.
• Hospital engagement: Periodic on-site presence at hospitals may be required to understand operational workflows and gather requirements.
• Team structure: Works cross-functionally between commercial/customer teams, hospital partners, and the internal core development team.
• Cadence: Operates within an Agile/Scrum delivery model, participating in sprint planning, refinement, and reviews.

7. Salary Range

Indicative monthly gross salary: SGD8,500 – SGD10,000 (exclude CPF for PR/Singaporean and performance bonus/benefits/Employee Equity Share), commensurate with experience and seniority.