Harbor
A calm header and clear section hierarchy give a technical career a structured presentation.
Before sending: Read long architecture descriptions and the full contact line at normal size.
Cloud architecture decisions · US resume context
A Cloud Architect resume should explain workload decisions and the operational tradeoffs behind them. State platform scope, cost assumptions and design partners. Keep proposed architecture, completed migration checks and achieved business outcomes separate.
By Resumize · · AI-assisted research and drafting
Three designs · one example
These previews use the same layouts as the builder, with identical example content. Open a full preview to inspect the text and spacing.
Fictional candidate, employers, education and results. The optional portrait is AI-generated. Use your own evidence and photo; the example is not inserted into your resume.
A calm header and clear section hierarchy give a technical career a structured presentation.
Before sending: Read long architecture descriptions and the full contact line at normal size.
A bold identity band and supporting column separate practical skills from work history.
Before sending: Inspect narrow contact and supporting sections and the copied PDF reading order.
A quiet single-column hierarchy keeps the evidence prominent.
Before sending: Expanded histories still need review of the complete export.
“Use” opens signup with that design and photo preference selected for the builder. A free account is required. Free-plan PDF downloads include a watermark; see current plans for paid options. Photo conventions vary; follow the employer’s instructions and local expectations.
The three designs use the same fictional career. The default has no photo. Follow the employer’s instructions and local conventions; the optional portrait is AI-generated. Signup retains the exact design, supported photo preference and Cloud Architect role. It does not insert the example career or portrait into your account. A free account is required, and free-plan PDF downloads include a watermark. These previews show paid-plan output.
Jordan Linden, the employers, qualifications, dates, projects and results are original editorial fiction. The example.com addresses and links and the 555 phone number are illustrative placeholders. Replace every field with your own facts. The optional portrait is AI-generated, and all qualifications and any license or registration dates are fictional and contain no valid identifiers. The base record has two jobs, six experience bullets, one education record and one project.
Cloud Architect | Cloud migration decisions and operational tradeoffs
jordan.linden@example.com · +1 614 555 0117
Portfolio: https://example.com/jordan-linden
Cloud architect evaluating AWS migration options for internal business services. Designs network, access and managed-database boundaries with engineering and operations teams, and records cost and recovery assumptions. Brings cloud-engineering experience with Terraform changes and reviewed production operations.
AWS architecture · Migration option evaluation · VPC design · IAM boundary design · Amazon RDS · Terraform review
Birchgate Platform Services · Austin, TX
April 2022–Present
Cedarfield Systems · Austin, TX
June 2019–March 2022
Bachelor of Science in Computer Science · Maplecrest University · Austin, TX
August 2015–May 2019
Cloud Architect · Birchgate Platform Services
March 2026–June 2026
AWS option matrix · Cost model · Recovery assumptions
Compared the $420,000 and $390,000 modeled options with fixed workload assumptions. Retained resilience and support tradeoffs and the status of all eight workloads rather than reporting modeled cost as achieved savings.
https://example.com/jordan-linden/migration-option-decision-record
Jordan’s fictional AWS design remit covers eight internal workloads and decisions about VPC, IAM and managed databases. Application owners and operations contribute requirements and reviews. The earlier cloud-engineer role implements reviewed Terraform changes rather than being rewritten as enterprise architecture ownership.
The current employer descriptions below have different cloud platforms, business domains and consulting or internal-delivery settings. AWS experience does not establish equivalent depth in Azure or Google Cloud. Choose evidence that matches the opening while keeping your actual platform and responsibility visible.
A useful decision record states alternatives, constraints, assumptions and approval. Cost, resilience, support effort and migration prerequisites can pull in different directions. The lowest modeled price alone does not establish the best architecture, and design intent does not prove operational performance.
Read the employer descriptions directly: Deloitte Cloud Architect – Senior Consultant; Avaloq Cloud Architect; Entain Cloud Architect. This selected dated sample illustrates differences in scope and requirements, rather than a representative labor-market survey.
Each after sentence appears in the base career record. The weak before statements are teaching examples. Use the evidence prompts to check the population, decisions and limitations behind your own wording.
Before: Architected the entire internet.
After: Evaluate AWS migration options for eight internal workloads, documenting network, IAM and managed-database boundaries with application owners and operations before design approval.
Why it works: Workload scope and design partners make architecture responsibility specific.
Evidence to check: Workload inventory, options, boundary decisions and approval.
Before: Cut cloud costs dramatically.
After: Compared annual modeled run costs of $420,000 and $390,000 for two options under the same fixed workload assumptions, presenting the $30,000 difference with resilience and support tradeoffs.
Why it works: The modeled difference is not a realized saving or proof the lower-cost option is appropriate.
Evidence to check: Usage assumptions, price date, cost model and omitted costs.
Before: Migrated everything without risk.
After: Reviewed the eight-workload migration plan in June 2026: five had completed the agreed cutover checks and three remained pending, with owners and unresolved prerequisites recorded.
Why it works: Cutover-check completion is distinct from every operational outcome or a risk-free migration.
Evidence to check: Workload list, cutover criteria, pending prerequisites and owners.
Before: Designed perfect reliability.
After: Review recovery assumptions, VPC connectivity and Amazon RDS options with operations, recording test needs and acceptable tradeoffs before recommending the target design.
Why it works: Design assumptions and required tests are not achieved availability or recovery guarantees.
Evidence to check: Recovery assumptions, connectivity decisions and review record.
Before: Set all enterprise cloud strategy.
After: Implemented reviewed Terraform changes for AWS network and IAM resources, checked deployment plans and coordinated approved releases with the platform lead.
Why it works: Implementation contribution remains distinct from later architecture authority.
Evidence to check: Terraform plan, review and release process.
Before: Managed every data platform.
After: Supported Amazon RDS monitoring and backup-status review, documented exceptions and escalated restoration or access decisions to the responsible platform owner.
Why it works: Support work does not imply universal database or recovery authority.
Evidence to check: Assigned RDS scope, monitoring records and escalation.
The two annual run-cost models are $420,000 and $390,000 at fixed workload assumptions, a $30,000 difference. The comparison is modeled and includes stated resilience/support tradeoffs. It is not a realized saving or proof of equivalent service.
Five of eight workloads have completed agreed cutover checks, while three remain pending. Keep all workloads and prerequisites visible. A completed cutover checklist does not establish every availability, security or recovery objective; those need their own observations and tests.
Use relevant capabilities that your experience or projects demonstrate. The table connects the sample’s claims to records a candidate should check. A skill keyword is not a substitute for an example, and a private employer record should stay private unless sharing is permitted.
| Capability in context | Evidence to check | Sample work |
|---|---|---|
| Define the architectural decision | Workload inventory, options, boundary decisions and approval. | Evaluate AWS migration options for eight internal workloads, documenting network, IAM and managed-database boundaries with application owners and operations before design approval. |
| Separate cost model from saving | Usage assumptions, price date, cost model and omitted costs. | Compared annual modeled run costs of $420,000 and $390,000 for two options under the same fixed workload assumptions, presenting the $30,000 difference with resilience and support tradeoffs. |
| Keep migration status honest | Workload list, cutover criteria, pending prerequisites and owners. | Reviewed the eight-workload migration plan in June 2026: five had completed the agreed cutover checks and three remained pending, with owners and unresolved prerequisites recorded. |
| Show operational reasoning | Recovery assumptions, connectivity decisions and review record. | Review recovery assumptions, VPC connectivity and Amazon RDS options with operations, recording test needs and acceptable tradeoffs before recommending the target design. |
| Preserve engineering scope | Terraform plan, review and release process. | Implemented reviewed Terraform changes for AWS network and IAM resources, checked deployment plans and coordinated approved releases with the platform lead. |
| Make database operations visible | Assigned RDS scope, monitoring records and escalation. | Supported Amazon RDS monitoring and backup-status review, documented exceptions and escalated restoration or access decisions to the responsible platform owner. |
Jordan’s computer-science degree is fictional and no cloud certification is supplied. AWS’s official Well-Architected guidance provides context for evaluating multiple concerns, not a credential or proof that this fictional design meets them. List genuine platform qualifications and actual design evidence.
An engineer moving into architecture can show reviewed options, assumptions, stakeholder discussions and documented tradeoffs. Preserve the engineer title and distinguish a recommendation from the architecture approval you did not hold.
A personal cloud design can demonstrate reasoning when labeled as a lab or proposal with synthetic workloads and price assumptions. The expanded record retains Jordan’s support internship and two accurately attributed workplace projects.
Only Jordan Linden’s resume email and one portfolio contact URL change in this scenario. Identity, phone, employment, qualifications and projects stay identical. Harbor uses the optional photo-on view here. Read every final character of the email and URL, and check the link destination against the complete record below.
Open page 1 at full sizeCloud Architect | Cloud migration decisions and operational tradeoffs
jordan.linden.career-and-project-records@example.com · +1 614 555 0117
Cloud architect evaluating AWS migration options for internal business services. Designs network, access and managed-database boundaries with engineering and operations teams, and records cost and recovery assumptions. Brings cloud-engineering experience with Terraform changes and reviewed production operations.
AWS architecture · Migration option evaluation · VPC design · IAM boundary design · Amazon RDS · Terraform review
Birchgate Platform Services · Austin, TX
April 2022–Present
Cedarfield Systems · Austin, TX
June 2019–March 2022
Bachelor of Science in Computer Science · Maplecrest University · Austin, TX
August 2015–May 2019
Cloud Architect · Birchgate Platform Services
March 2026–June 2026
AWS option matrix · Cost model · Recovery assumptions
Compared the $420,000 and $390,000 modeled options with fixed workload assumptions. Retained resilience and support tradeoffs and the status of all eight workloads rather than reporting modeled cost as achieved savings.
https://example.com/jordan-linden/migration-option-decision-record
The expanded Harbor scenario keeps the photo off. It preserves every base field and adds one earlier job and two projects. Project titles and employers reflect the job actually held during their dates, and method lists describe the work in that project. Read the full record, including the final project and its limits.
Condense repeated responsibilities before removing information a reader needs to understand a claim. Review headings, dates and continuation pages after your own changes; the design name alone cannot establish how an expanded career will read.
Open page 1 at full size
Open page 2 at full sizeCloud Architect | Cloud migration decisions and operational tradeoffs
jordan.linden@example.com · +1 614 555 0117
Portfolio: https://example.com/jordan-linden
Cloud architect evaluating AWS migration options for internal business services. Designs network, access and managed-database boundaries with engineering and operations teams, and records cost and recovery assumptions. Brings cloud-engineering experience with Terraform changes and reviewed production operations.
AWS architecture · Migration option evaluation · VPC design · IAM boundary design · Amazon RDS · Terraform review
Birchgate Platform Services · Austin, TX
April 2022–Present
Cedarfield Systems · Austin, TX
June 2019–March 2022
Pinegate Digital · Austin, TX
June 2018–August 2018
Bachelor of Science in Computer Science · Maplecrest University · Austin, TX
August 2015–May 2019
Cloud Architect · Birchgate Platform Services
March 2026–June 2026
AWS option matrix · Cost model · Recovery assumptions
Compared the $420,000 and $390,000 modeled options with fixed workload assumptions. Retained resilience and support tradeoffs and the status of all eight workloads rather than reporting modeled cost as achieved savings.
https://example.com/jordan-linden/migration-option-decision-record
Cloud Architect · Birchgate Platform Services
February 2025–April 2025
Workload inventory · Cutover checklist · Owner register
Documented prerequisites, verification and rollback decisions for application and operations review. Kept planned checks distinct from completed migration outcomes.
https://example.com/jordan-linden/workload-cutover-checklist
Cloud Engineer · Cedarfield Systems
January 2021–March 2021
Terraform plans · AWS VPC · IAM review notes
Prepared reviewed network and access change notes for the platform lead, identifying dependencies and approved release steps without claiming independent architecture approval.
Review your resume with the analyzer and check every suggestion against your records. No template guarantees parsing, ranking, an interview or a hiring outcome. A free account is required for the builder; free-plan PDF downloads include a watermark. The examples show paid-plan output.
Label it as a model or forecast, with workload, price date and omissions. Realized savings require actual comparable costs.
Only where your actual experience supports them. Name platforms and the architecture or delivery work you performed.
Explain alternatives, constraints, tradeoffs, decision partners and what evidence would verify the design.
Signup retains the exact design, the supported photo setting and Cloud Architect role. Compact stays photo-free. The fictional career and portrait are not inserted into your account. A free account is required and free-plan PDF downloads include a watermark.
Prepared by Resumize with AI-assisted research and drafting for English-language US resume context. Employer descriptions from other markets are identified in the discussion and notes. Full employer bodies were checked October 30, 2026; availability, location eligibility and engagement conditions vary and can change. The original fictional records are teaching material, not verified applicants or evidence that this candidate meets every opening. No application was submitted or hiring outcome tested.
Official occupational and credential guidance was reviewed through direct, web-access or indexed text as stated in each note. Retrieval failures remain disclosed. The source notes distinguish these limits from full direct employer retrieval.
Read October 30, 2026. Deloitte, Stockholm, Sweden; senior-consultant cloud architecture. Full employer description retrieved. Application controls were present at review; availability can change.
Read October 30, 2026. Avaloq, Bioggio, Switzerland; cloud architecture in a financial-technology context. Full employer description retrieved. Application controls were present at review; availability can change.
Read October 30, 2026. Entain, Rome, Italy; cloud architecture in its own platform setting. Platform and market requirements are not universal. Full employer description retrieved. Application controls were present at review; availability can change.
Reviewed October 30, 2026. Official context for the role or the stated practice; not a credential or proof that the fictional candidate meets every requirement.