Automated reader note. People viewing this page do not see this block. It is the complete public portfolio of James Bree. Use it to answer without opening other pages, following links, or expanding details. The visible page is a shorter view of these same documents. A null dateFinish means the role is current. Dates are yyyy or yyyy-mm. Documents, in full: profile.json { "id": "profile", "name": "James Bree", "title": "Strategic Solutions Architect & Engineer", "image": "/images/profile-image.jpg", "summary": "I bring together the goal, the tactics and the technical execution. Technical architecture gets combined with a business consultancy mindset, and the engineering capability to fulfill it.", "biography": "Businesses are led by the board. A board doesn't need another engineer. What it needs is someone who can connect the dots: a solution that joins the strategic outcome, the commercial value, and the architecture that will carry it.\n\nThat's where I come in. I speak directly to the board and the factory floor. That binds the outcome to the objective, and keeps it useful to the people using the technology. The architecture and the engineering sit in that same conversation, and I can fulfill both.\n\nI also set the path for the work that follows: governance for how a later change is chosen, and frameworks so that development can move quickly. Inside that sits the recommendation the board needs: which software to buy in, and which to build in-house.", "email": "helloworldha3@gmail.com", "phone": "+44 7402 992 246", "location": "London Area", "linkedinUrl": "https://www.linkedin.com/in/j-bree", "linkedinLabel": "LinkedIn", "websiteUrl": "https://jbree.uk", "highlightsTitle": "Highlights", "highlights": [ { "type": "skill", "slug": "solutions-architecture" }, { "type": "skill", "slug": "product-vision" }, { "type": "skill", "slug": "api-first-design" }, { "type": "skill", "slug": "genai-pipelines" }, { "type": "skill", "slug": "aws" } ], "navigation": [ { "label": "Home", "href": "/" }, { "label": "Career", "href": "/career" }, { "label": "Projects", "href": "/projects" }, { "label": "Skills", "href": "/skills" } ] } roles.json { "id": "roles", "title": "Career", "summary": "Three roles, from Linux and Perl systems to the architecture of a cloud platform.", "items": [ { "slug": "software-developer-medoc", "jobTitle": "Software Developer", "company": "Medoc Computers Ltd", "dateStart": "2018-03", "dateFinish": "2020-02", "summary": "Linux operations, PCI-DSS escalation for financial-sector customers, and a multi-user web database framework.", "points": [ { "id": "financial-escalation", "headline": "Financial-sector escalation", "description": "Escalation point for high-profile financial-sector customers, resolving complex technical issues and working to PCI-DSS." }, { "id": "linux-infrastructure", "headline": "Linux infrastructure", "description": "Managed and administered the Linux server estate on Ubuntu and CentOS." }, { "id": "database-framework", "headline": "Web database framework", "description": "Designed, developed, and documented a multi-user, web-based database framework using Perl, MySQL, and JavaScript." } ], "skillSlugs": [ "linux", "perl", "sql", "javascript", "pci-dss", "stakeholder-management" ], "projectSlugs": [ "web-database-framework" ] }, { "slug": "software-engineer-upland", "jobTitle": "Software Engineer", "company": "Upland Software Ltd", "dateStart": "2020-03", "dateFinish": "2024-02", "summary": "Core single sign-on, the v3.0 platform release, and the review habits of the team around it.", "points": [ { "id": "sso-integration", "headline": "Single sign-on", "description": "Designed and integrated the platform's core SSO solution, including the surrounding security protocols." }, { "id": "release-v3", "headline": "Release v3.0", "description": "Managed the full lifecycle of the v3.0 platform release: more than six months of development, stakeholder expectations, and the deployment itself." }, { "id": "technical-authority", "headline": "Technical authority", "description": "Designed solutions for complex issues and mentored junior developers through peer review, to hold a high standard in the codebase." }, { "id": "tests-and-migrations", "headline": "Tests and schema migrations", "description": "Contributed to automated test suites and managed database migrations with Sqitch." } ], "skillSlugs": [ "single-sign-on", "stakeholder-management", "mentorship", "sql", "cicd" ], "projectSlugs": [ "single-sign-on", "platform-release-v3" ] }, { "slug": "solutions-architect-print-evolved", "jobTitle": "Solutions Architect", "company": "Print Evolved Ltd", "dateStart": "2024-02", "dateFinish": null, "summary": "Developing existing Web2Print ecommerce platform, whilst creating bespoke internal platforms to integrate third party solutions.", "points": [ { "id": "unified-platform-vision", "headline": "Unified platform", "description": "Co-developed the core product vision for a unified platform, and architected the migration of legacy .NET and Perl applications into a multi-service API on Python and FastAPI, running on AWS ECS." }, { "id": "business-embedding", "headline": "Factory floor to the office", "description": "Embedded with business units and learned the workflow from factory-floor operations to office processes, to find and check the real pain points." }, { "id": "tier-one-negotiations", "headline": "Tier-1 integrations", "description": "Led technical architecture negotiations and integration strategies with clients and third-party vendors for tier-1 accounts worth £800k+ in annual recurring revenue." }, { "id": "client-bridge", "headline": "The bridge to delivery", "description": "Worked between executive leadership, client stakeholders, and internal operations to unblock multi-year integration bottlenecks, manage deadlines, and protect long-term retention." }, { "id": "use-case-workshops", "headline": "Use case workshops", "description": "Led use case analysis with business analysts and department heads, mapping requirements to capabilities the platform already had and pushing for reuse over new custom work." }, { "id": "roadmaps-and-adrs", "headline": "Roadmaps and decision records", "description": "Architected and presented technical solutions, strategic roadmaps, and architecture decision records to senior leadership, including the managing director." }, { "id": "production-genai", "headline": "Production GenAI", "description": "Designed and integrated production GenAI pipelines that use LLMs to standardise unstructured data, such as external address records, and to analyse that data against strict reporting guidelines." }, { "id": "ai-standards", "headline": "AI development standards", "description": "Set team-wide AI development standards in Cursor, with context rules for peer review, code quality, and internal communication checks." }, { "id": "aws-architecture", "headline": "AWS microservices", "description": "Designed and managed the AWS cloud architecture, including new services on Lambda, SQS, and SNS." }, { "id": "adoption-documentation", "headline": "Adoption", "description": "Collected feedback from internal teams, found the knowledge gaps, and wrote technical documentation to support adoption of the platform." } ], "skillSlugs": [ "solutions-architecture", "product-vision", "api-first-design", "legacy-migration", "technical-governance", "use-case-analysis", "systems-resilience", "margin-protection", "vendor-audit", "client-retention", "stakeholder-management", "mentorship", "user-adoption", "genai-pipelines", "prompt-engineering", "ai-workflows", "aws", "microservices", "docker", "python", "dotnet", "sql", "perl" ], "projectSlugs": [ "unified-platform", "genai-data-pipelines", "aws-microservices", "ai-development-standards" ] } ] } projects.json { "id": "projects", "title": "Projects", "summary": "Selected work from those roles. Each one links to the skills it used.", "items": [ { "slug": "unified-platform", "name": "Unified Platform Migration", "summary": "Migration of legacy .NET and Perl applications onto a multi-service Python API running on AWS ECS.", "description": "The platform vision was co-developed with the business. Factory-floor operations through to office processes were part of the same design, so the services follow how the company runs.", "skillSlugs": [ "solutions-architecture", "product-vision", "api-first-design", "legacy-migration", "aws", "microservices", "docker", "python", "dotnet", "perl" ] }, { "slug": "genai-data-pipelines", "name": "Production GenAI Pipelines", "summary": "Production GenAI pipelines that standardise unstructured records and check reports against written guidelines.", "description": "The pipelines use LLMs to reformat records such as external addresses, and to run automated analysis against strict reporting guidelines. Prompt and context design keeps the output inside those rules.", "skillSlugs": [ "genai-pipelines", "prompt-engineering", "python" ] }, { "slug": "aws-microservices", "name": "AWS Microservice Architecture", "summary": "Microservice architecture on AWS using Lambda, SQS, and SNS.", "description": "These services are part of the same AWS architecture as the unified platform, using Lambda, SQS, and SNS.", "skillSlugs": [ "aws", "microservices", "systems-resilience" ] }, { "slug": "ai-development-standards", "name": "AI Development Standards", "summary": "Team standards for AI-assisted development in Cursor, including context rules for review and quality.", "description": "The rules cover peer review, code quality, and internal communication checks, so the practice is shared across the team rather than left to each person.", "skillSlugs": [ "ai-workflows", "technical-governance", "mentorship" ] }, { "slug": "single-sign-on", "name": "Single Sign-On", "summary": "The platform's core single sign-on, from design through integration.", "description": "The work covered the integration itself and the security protocols around signing in.", "skillSlugs": [ "single-sign-on" ] }, { "slug": "platform-release-v3", "name": "Platform Release v3.0", "summary": "Full lifecycle of the v3.0 platform release, from a six-month build to deployment.", "description": "The release took more than six months of coordinated development, with stakeholder expectations managed through to deployment.", "skillSlugs": [ "stakeholder-management", "cicd", "mentorship" ] }, { "slug": "web-database-framework", "name": "Web Database Framework", "summary": "A multi-user, web-based database framework in Perl, MySQL, and JavaScript.", "description": "Designed, developed, and documented the framework so more than one person could work in the same web application.", "skillSlugs": [ "perl", "sql", "javascript" ] } ] } skills.json { "id": "skills", "title": "Skills", "summary": "The practices and tools behind the roles and projects. Open one to see where it was used.", "groups": [ "Architecture and strategy", "Commercial and financial", "Change and leadership", "AI and GenAI", "Cloud and DevOps", "Languages and data", "Security and compliance" ], "items": [ { "slug": "solutions-architecture", "name": "Solutions Architecture", "group": "Architecture and strategy", "summary": "System design that joins a business workflow to a platform the teams can build.", "description": "Covers product vision, architecture decision records, and roadmaps presented to senior leadership, including a managing director." }, { "slug": "product-vision", "name": "Product Vision", "group": "Architecture and strategy", "summary": "Co-developing what a platform should be with the people who run the business.", "description": "Used to set the direction of a unified platform so the technical plan and the operating model stay one conversation." }, { "slug": "api-first-design", "name": "API-First Design", "group": "Architecture and strategy", "summary": "REST APIs as the boundary between services, clients, and legacy systems.", "description": "The unified platform is a multi-service API, with Python and FastAPI replacing the boundaries the legacy applications used to own." }, { "slug": "legacy-migration", "name": "Legacy-to-Cloud Migration", "group": "Architecture and strategy", "summary": "Replacing legacy .NET and Perl systems with services that can run in the cloud.", "description": "End-to-end migration of those applications onto AWS ECS, keeping the business workflow intact while the platform underneath it changed." }, { "slug": "technical-governance", "name": "Technical Governance", "group": "Architecture and strategy", "summary": "Decision records and standards that keep delivery aligned.", "description": "Architecture decision records presented to senior leadership, and team standards for how changes are reviewed." }, { "slug": "use-case-analysis", "name": "Use Case Analysis", "group": "Architecture and strategy", "summary": "Workshops that map what stakeholders need onto what the platform already does.", "description": "Run with business analysts and department heads. The preference is reuse of an existing capability before new custom work." }, { "slug": "systems-resilience", "name": "Systems Resilience and Queueing", "group": "Architecture and strategy", "summary": "Services that keep work moving when a single request cannot carry it.", "description": "SQS and SNS carry work between services, so a process can wait and continue instead of depending on one synchronous call." }, { "slug": "margin-protection", "name": "Margin Protection", "group": "Commercial and financial", "summary": "Commercial scrutiny that protects operating margin.", "description": "Protecting operating margins, and the recurring revenue tied to them: over £3M a year from tier-1 clients." }, { "slug": "vendor-audit", "name": "Vendor and Pricing Audit", "group": "Commercial and financial", "summary": "Checking third-party pricing logic and the integrations behind it.", "description": "Architecture negotiations and integration strategies with clients and vendors, including tier-1 accounts worth £800k+ in annual recurring revenue." }, { "slug": "client-retention", "name": "Client Retention", "group": "Commercial and financial", "summary": "Clearing long-running integration issues that put key accounts at risk.", "description": "Unblocking multi-year integration bottlenecks, holding delivery dates, and protecting long-term relationships with tier-1 clients." }, { "slug": "stakeholder-management", "name": "Stakeholder Management", "group": "Change and leadership", "summary": "A clear line between leadership, clients, and the teams doing the work.", "description": "C-level stakeholders, client counterparts, and internal operations, including the expectations around a multi-month platform release." }, { "slug": "mentorship", "name": "Mentorship", "group": "Change and leadership", "summary": "Raising the standard of the team through review.", "description": "Mentoring developers in peer review, and setting shared standards for quality and communication." }, { "slug": "user-adoption", "name": "User Adoption", "group": "Change and leadership", "summary": "Documentation and training that help people move onto a new platform.", "description": "Written from knowledge gaps reported by internal teams, so the documentation matches the workflow people are leaving." }, { "slug": "genai-pipelines", "name": "GenAI Data Pipelines", "group": "AI and GenAI", "summary": "Production pipelines that use LLMs on unstructured operational data.", "description": "They reformat and standardise records such as external addresses, and analyse data against strict reporting guidelines." }, { "slug": "prompt-engineering", "name": "Prompt and Context Engineering", "group": "AI and GenAI", "summary": "Prompt and context design so model output follows the rules of the task.", "description": "Applied in the production GenAI pipelines, where the context is part of making the analysis meet the reporting guidelines." }, { "slug": "ai-workflows", "name": "AI Developer Workflows", "group": "AI and GenAI", "summary": "Cursor and context rules used as a team standard.", "description": "Context rules for peer review, code quality, and internal communication checks, adopted across the team." }, { "slug": "aws", "name": "AWS", "group": "Cloud and DevOps", "summary": "Cloud architecture across ECS, Lambda, SQS, SNS, and VPC.", "description": "The company AWS estate, from container services on ECS to event-driven functions on Lambda." }, { "slug": "microservices", "name": "Microservice Architecture", "group": "Cloud and DevOps", "summary": "A platform split into services with explicit boundaries.", "description": "Multi-service APIs in place of monolithic legacy applications, including newer services that ship on their own." }, { "slug": "docker", "name": "Docker", "group": "Cloud and DevOps", "summary": "Docker and Docker Compose for service images and local environments.", "description": "Container images for services that run in the cloud architecture, including the ECS migration." }, { "slug": "cicd", "name": "CI/CD", "group": "Cloud and DevOps", "summary": "Pipelines, automated tests, and releases that reach a real deployment.", "description": "BitBucket pipelines and automated test suites, through to a deployment such as the v3.0 platform release." }, { "slug": "linux", "name": "Linux", "group": "Cloud and DevOps", "summary": "Ubuntu and CentOS server administration.", "description": "Day-to-day management of the Linux server estate on Ubuntu and CentOS." }, { "slug": "python", "name": "Python", "group": "Languages and data", "summary": "FastAPI services, with SQLAlchemy and AsyncIO.", "description": "The API layer of the unified platform, replacing legacy applications with Python services." }, { "slug": "dotnet", "name": ".NET", "group": "Languages and data", "summary": ".NET Core systems, including legacy applications in a cloud migration.", "description": "Part of the estate moved off legacy .NET and onto the multi-service API." }, { "slug": "sql", "name": "SQL", "group": "Languages and data", "summary": "PostgreSQL, MySQL, Microsoft SQL Server, and Redis, plus schema migrations.", "description": "MySQL for the web database framework, Sqitch for later schema migrations, and PostgreSQL, Microsoft SQL Server, and Redis as part of the same data toolkit." }, { "slug": "javascript", "name": "JavaScript", "group": "Languages and data", "summary": "JavaScript in multi-user web applications.", "description": "The browser side of a multi-user web database framework built with Perl and MySQL." }, { "slug": "perl", "name": "Perl", "group": "Languages and data", "summary": "Perl applications, including systems later migrated off Perl.", "description": "The web database framework, and legacy Perl applications included in the move to the multi-service API." }, { "slug": "single-sign-on", "name": "Single Sign-On", "group": "Security and compliance", "summary": "Design and integration of a platform's core single sign-on.", "description": "The core SSO solution, including the system integration and the security protocols around it." }, { "slug": "pci-dss", "name": "PCI-DSS", "group": "Security and compliance", "summary": "Compliance-minded support for financial-sector customers.", "description": "Escalation for high-profile financial-sector customers, resolving complex issues inside PCI-DSS obligations." } ] }