Senior Tech Lead / Architect
Confirmed on the employer's own hiring board on Oct 31, 2026. First seen by Alion on Oct 28, 2026. Dedagroup scores A on the Alion truth index.
We are one of the leading technology groups in Italy, with operations in the United States. We operate as a Business & Technology Accelerator for companies, financial institutions, and public sector organizations, supporting the evolution of their IT and digital strategies. Through an ecosystem of companies that share values, business strategies, and a common vision, we enable our clients to unlock the full potential of technology, amplifying its positive impact on both the economy and society. This role is dedicated to our US market.
What to expect
As a Tech Lead / Architect, you own the technical design of one of our products and the quality of what its team ships. Our products give US credit unions analytics, lending and marketing decisions built on their own core banking data, and they stand on shared foundations: identity and SSO, authorization, multi-tenancy, entitlements, audit logging and metering, one data platform, and common ML and LLM components. All of it runs on an open-source stack split by a red line between a private datacenter, where member data stays, and a public cloud for the workloads that do not need it. You break the architecture into components, set the interfaces between them, review code and design, and make the build-versus-reuse calls on that stack- and you write code part of the time. One of these posts is the platform architect, who works across the products rather than inside one. The data is regulated (GLBA, FCRA, ECOA), so tenant isolation and a lending decision that can be reconstructed months later are design constraints, not afterthoughts. Our stack is Java/Spring Boot, Python, PostgreSQL, Kubernetes, Keycloak and Dagster, but we hire for the understanding underneath the tool and expect you to carry it across. Your ultimate goal is a product whose design every engineer on the team can explain, and whose quality does not depend on you reviewing every line.
What you will do
AArchitecture & Interfaces: Break the product’s architecture into components with clear responsibilities, and set the interfaces between them-API contracts, events, data ownership-so that the team can build in parallel and change one part without breaking another.
Design & Code Review: Review designs before they are built and code before it ships, and set and hold the team’s standards for testing, review and recording decisions; you lead from inside the codebase, writing code part of the time.
Build Versus Reuse: Decide when to adopt, wrap or write a component on our open-source stack, and record each call with its reasons and its exit cost, so that the next engineer knows why it was made and when to revisit it.
Quality & Delivery: Own the quality of what the team ships-test strategy, CI gates, performance and security review, release readiness-and give the product manager estimates and trade-offs they can plan against.
Tenancy & Auditability: Make sure the design scopes every request to the right credit union, keeps member data on the right side of the red line, and records what a regulated decision needs-inputs, reasons, model version-so that it can be reconstructed for a dispute or an examiner.
Platform Architect: In the platform architect post, own the red line between the datacenter and the public cloud, the multitenancy model, data governance and the shared components every product depends on, and keep the product teams’ designs consistent with them-spending most of your time on design decisions rather than code.
Risk & Communication: Explain trade-offs to engineers and product managers in their own terms, and raise technical risk early, with an alternative attached.
What we expect from you
Scope You Have Owned: Experience as a tech lead or architect-or as a senior engineer who held that role in practice-in which you owned the technical design of a production system end to end: decomposed it, set its interfaces, and lived with the consequences after go-live. We weigh what you have owned, not the years it took.
Hands-On Engineering: You still write production code and review others’ with authority, in a backend stack-Java/Spring Service & Multi-Tenant Design: You have designed service boundaries, API contracts and data ownership for a multi-tenant system, and can argue the trade-offs between row-level, schema-per-tenant and database-per-tenant isolation, and between a modular monolith and services.
Data & Relational Depth: Strong relational modeling and SQL-PostgreSQL preferred; SQL Server, Oracle or MySQL count -and a working understanding of how pipelines, a shared data model and ML or LLM components fit into a product.
Cloud-Native & Identity: Experience designing for containers on Kubernetes, object storage and CI/CD, and for authentication and authorization with OIDC and OAuth2-Keycloak preferred; Okta, Auth0, Entra ID or Cognito count.
Security by Design: You treat least privilege, tenant isolation, encryption, audit trails and data residency as inputs to a design rather than findings in its review.
Decisions in Writing: You write architecture down-decision records, diagrams, interface specifications-so that it outlives the meeting, and you can explain a trade-off to an engineer, a product manager and an auditor.
Ownership & Judgment: You say no to a design with a reason and an alternative, make the call when the team is split, and change your mind when the evidence does.
Nice to Haves: For the platform architect post, having designed a platform that several product teams build on; Hybrid architectures that split workloads between a private datacenter and a public cloud by data sensitivity; Financial services or credit unions, particularly lending decisions and the record-keeping they require (ECOA/Reg B, FCRA, GLBA); Multi-tenant SaaS with SSO, entitlements and usage metering; Keycloak in depth (realms, federation, fine-grained authorization); Selfmanaged Kubernetes and PostgreSQL operators; Dagster or another orchestrator, and governing a data model shared by several products; ML or LLM features in production, including how they are evaluated and released; SOC 2 or ISO 27001 audits in which the architecture had to answer the questions.