Infinity Quest
Lead Service Architect
Get notified of more jobs like this · No spam, ever
How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Role purpose
The Service Architect will design the target service for privileged access, server access, cloud administration, database administration, network access, emergency access, third-party access, break-glass access, and just-in-time access. The role defines the service blueprint, access patterns, process flows, approval paths, team responsibilities, metadata, control points, integrations, operating model, and transition roadmap.
Key responsibilities
- Design the end-to-end service architecture for infrastructure access and privileged access.
- Define the target service model, including processes, roles, controls, data flows, integrations, and operational hand-offs.
- Create a risk-based access model that sets the access pattern, approval route, monitoring level, and review frequency.
- Define patterns for standing access, time-bound access, just-in-time access, emergency access, third-party access, cloud access, and privileged administration.
- Define how identity, application, infrastructure, entitlement, account, risk, and control data are used in access decisions.
- Identify trusted data sources, data owners, data quality rules, and exception handling.
- Design controls for least privilege, authorised access, traceability, monitoring, timely removal, access reviews, and audit evidence.
- Define how evidence is produced through workflows, logs, approvals, access records, and session records.
- Identify current-state gaps and define steps to move to the target service.
- Work with IAM, PAM, infrastructure, cloud, application, cyber security, risk, audit, service management, and engineering teams.
- Challenge access processes that are inconsistent, too manual, poorly owned, or designed around individual tools.
Reasons to use Rodeo
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
It searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
Key deliverables
The role will produce:
- Service blueprint and privileged access service model
- Access pattern catalogue and risk-based decision model
- Process maps, RACI, and ownership model
- Metadata, data, control, and evidence models
- Integration architecture and operating model
- Exception, break-glass, and onboarding designs
- Reporting requirements and transition roadmap
Experience and capability
Candidates should have experience in several of the following areas:
- Service architecture or service design in a large organisation.
- IAM, PAM, infrastructure access, or security architecture.
- Designing services across people, process, technology, data, and controls.
- Risk-based access models and control design.
- Infrastructure platforms, including servers, databases, cloud platforms, network devices, containers, and administrative tooling.
- Using data from identity systems, application inventories, CMDBs, infrastructure inventories, entitlement stores, or control platforms.
- Designing access request, approval, fulfilment, monitoring, review, revocation, and exception processes.
- Working in regulated, audited, or control-heavy environments.
Get help with your application
Your very own career expert that helps elevate your application to the next level.
Experience with cloud IAM, secrets management, zero standing privilege, just-in-time access, attribute-based access control, service accounts, non-human identities, security monitoring, session recording, or financial services would be useful.
Success measures
Success will be measured by:
- Less standing privileged access.
- More risk-based and time-bound access.
- Better traceability of privileged activity.
- Stronger audit evidence.
- Clearer ownership across service, technology, control, and operations teams.
- Better use of trusted identity, application, and infrastructure data.
- Less manual effort in fulfilment and evidence gathering.
- Fewer bespoke access processes.
- Faster onboarding of applications and infrastructure platforms.
Role boundaries
This role owns the service architecture and service design.
It does not own day-to-day privileged access operations, the PAM engineering backlog, individual access approvals, or production support queues.
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Skills