The Solution Architect will design and oversee cloud environments, data architectures, and security models while providing reasoned recommendations for platform paths. They are responsible for defining naming conventions, network models, and cost structures while leading architecture reviews and producing technical documentation.
Established in 1997, Softeq was built from the ground up to specialize in new product development and R&D, tackling the most difficult problems in the tech sphere. Now we've expanded to offer early-stage innovation and ideation plus digital transformation business consulting. Our superpower is to deliver all of this under one roof on a global scale. So let's get started and build a better future together!
What the role does here:
Reviews the current cloud environments: subscriptions, resource groups, networking, access and security models, workspace structure, compute patterns, storage, deployment, monitoring and cost controls;
Produces reasoned recommendations on the platform path: modify the existing environments, build new ones, or take a phased hybrid approach, with risks, dependencies and cost considerations;
Decides the number and purpose of workspaces and the catalog structure: where the line runs between environments, where between data domains, and how that interacts with permissions and cost;
Designs the target data architecture: raw, cleaned, curated and serving layers, a feature layer for models, ingestion, transformation, orchestration, semantic layer, reporting support;
Defines naming, ownership, classification and lineage conventions, and the rules for granting access;
Designs the data security model: managed versus external tables, external locations and storage credentials, row filters and column masks, and a separate scope for external consumption;
Defines the platform network model: deployment into a customer-managed virtual network, private access to storage and to the control plane, and removal of public exposure;
Builds the compute and cost model: cluster and warehouse types, policies, tags, spend forecasting and a chargeback mechanism;
Designs the production landing zone for the external application: an isolated subscription, virtual network, private endpoints, a separate tenant for external users, and dedicated container registry and secrets store;
Owns application and integration architecture: service layer, data consumption, external authentication, perimeter protection, observability;
Produces decision records, diagrams and a traceability matrix from requirements to deliverables; leads architecture reviews.
Must have:
Databricks at platform rather than user level: the account and workspace split, metastores and catalogs, workspace strategy, environment isolation, and running the permission model in practice;
Unity Catalog end to end: managed and external tables, external locations, row and column protection, lineage, system tables, and sharing data with external consumers;
The platform compute and consumption model: cluster and warehouse types, serverless options, policies, pools, tagging, spend analysis and forecasting.
Platform network isolation: customer-managed networking, private endpoints, removal of public access, storage-level restrictions, audit logging;
Medallion architecture and semantic layer design for application and reporting consumption;
Ingestion approaches and how to choose between them: incremental file ingestion, streaming and declarative pipelines, change data handling, federated access without copying;
Delivery and environment promotion: portable project bundles, source control integration, catalog parameterization, automated tests;
Azure at design depth: App Service, Front Door and WAF, Key Vault, Container Registry, App Insights, Log Analytics, Entra ID;
Infrastructure as code, preferably Bicep;
External identity design: registration and invitation, MFA and conditional access, organization association, role-based access, account lifecycle, audit logging;
A real practice of architecture review and written argument for decisions.
Nice to have:
Migrating or consolidating multiple workspaces and metastores;
Rolling out Unity Catalog on an already running platform rather than greenfield;
External customer portals with a separate tenant for external users;
Change data capture and Oracle experience;
Platform cost modeling and cloud spend optimization;
Working alongside a client-side architect in an advisory capacity.
Softeq communicates only from @softeq.com email addresses. We never request payments or fees for any reason during hiring — including trainings or courses to be completed, equipment, onboarding, or background checks — and we will not ask for banking information, cryptocurrency or gift cards. If you receive a message from any other domain or requesting payment, do not respond and report it to abuse@softeq.com
“I was the first applicant for a remote marketing position that got listed on the company website the same day I applied. Had an interview within 48 hours!”