The Role:.
The Developer Portal Architect will lead the technical design of this portal, from the frontend architecture through to the backend service layer and its integrations, and existing workflow systems. This role requires someone who combines strong frontend architecture skills with a solid understanding of backend API design and cloud-native hosting patterns.
Key duties and responsibilities:
• Define how OpenAPI specifications will be published, versioned, and rendered within the portal, including multi-API structures and 'try it' patterns if needed.
• Design the SPA hosting and delivery architecture: evaluate hosting patterns (S3 static hosting + CloudFront CDN vs container hosting such as ECS Fargate), define deployment topology, build/release approach, and observability expectations.
• Define the content model and information architecture: content hierarchy (APIs, products, getting started, onboarding, policies/standards, support), metadata model (tags, categories, owner, lifecycle state), and docs conventions.
Backend Service Design
• Design the portal backend service ('control plane') that orchestrates onboarding, credential management, and workflow state, built on AWS Lambda with a DynamoDB datastore.
• Define the data model: minimum persistent entities (developer, organisation, client application, credential/API key reference, API subscription/access request, workflow state), lifecycle rules, relationship mapping, and access controls.
• Design integration flows for onboarding and credential issuance across DCR and AWS API Management APIs, clarifying synchronous vs asynchronous steps and how state propagates.
• Design the Jira integration that preserves the DSP workflow that Office uses
• Define service contracts (API endpoints/events) between the frontend and backend.
Transition Planning
• Contribute to the portal cutover approach and coexistence plan, defining how the new portal will be introduced alongside the existing portal during transition.
• Identify data requirements and design the approach for onboarding existing DSP registrations, credentials, and access entitlements onto the new platform.
Skills and Experience Required:
• Strong frontend architecture experience with modern single-page application (SPA) frameworks such as React, Angular and Vue.
• Solid understanding of SPA hosting patterns on AWS, including S3 static hosting with CloudFront, ECS Fargate container hosting, and the trade-offs between them.
• Experience designing backend REST APIs that serve SPA frontends, including authentication/authorisation flows (OAuth 2.0, token-based auth), CORS configuration, and API contract design.
• Understanding of core SPA authentication and authorisation patterns including token management, session handling, and secure credential storage in browser contexts.
• Experience with OpenAPI specifications: authoring, rendering, and integrating OpenAPI documentation into developer-facing portals.
• Ability to produce architecture artefacts (TA210, TA220, ADRs, data models) to a standard suitable for government assurance and endorsement.
• Experience designing serverless backend services on AWS, particularly Lambda functions.
Location and Contract Term: This role is Sydney, Melbourne, Brisbane, Adelaide and Canberra only . 6 month contract
with 2 x 6 month contract extension options
pending budget and delegate approval.
Security Requirements: Applicants must be Australian Citizens and hold a baseline security clearance (NV1 desirable)
How to Apply:
Applications close 25 May.
Please upload your resume to apply. Candidates will need to be willing to undergo pre-employment screening checks which may include, ID and work rights, security clearance verification and any other client requested checks
Please note you may need to complete selection criteria to complete this application process. We will be in touch with instructions for suitably skilled candidates
Call Kelly 0480 002 457 or email kelly@whizdom.com.au for any further information
