Domain Architect
Listed on 2026-02-16
-
IT/Tech
Systems Engineer, Data Engineer
Later is the enterprise leader in social media and influencer marketing software, services, and data, trusted by leading brands and agencies worldwide. Following our acquisition of Mavely, the Everyday Influencer Platform®, Later enables brands to scale creator partnerships from nano to premium influencers while managing social media content and campaigns across all major social and affiliate networks. Through proprietary performance data, marketing leaders can drive attributable sales and optimize social commerce with our software platform or award‑winning services.
Later is founded on two success stories that began in 2014:
Mavrck, the industry‑leading influencer marketing solution (now Later Influence™), and Later, the best social media management platform (now Later Social™) and first‑to‑market link‑in‑bio tool, Later Link in Bio. In 2024, Mavrck and Later officially joined together as one unified business, with a shared vision: to enable the world to make a living with their creativity.
We’re trusted by the top social platforms, with partnerships and integrations with Meta, Tik Tok, Linked In, You Tube, and Pinterest.
We enable marketers to create high‑performing content and engage in authentic collaborations with creators to reach new audiences, drive engagement, and generate predictable ROI.
About this position:We’re looking for a deeply technical, strategically minded Domain Architect to lead the next evolution of our platform architecture. In this role, you’ll rapidly assess our existing systems, define convergence opportunities between key domains, and shape the integration strategy that drives scalability, velocity, and long‑term technical excellence. You’ll bridge product, engineering, and data to define clear domain boundaries, establish technical standards, and guide the modernization of our architecture—ensuring we balance innovation with business impact.
This role is ideal for an experienced architect who thrives in fast‑moving environments, understands the trade‑offs between pragmatism and purity, and can translate complex technical concepts into clear, actionable decisions across teams.
What you'll be doing:- Evaluate and define the target‑state domain architecture across multiple products, identifying convergence opportunities and technical debt reduction paths.
- Design and lead a scalable integration strategy between heterogeneous systems (e.g., Rails Node/React Native via APIs, Kafka, or event streams).
- Define domain boundaries and service ownership models that enable sustainable growth and platform flexibility.
- Partner with Product and Engineering leadership to align architectural priorities with product roadmaps and business outcomes.
- Lead cross‑functional discussions on modernization strategy, balancing short‑term delivery with long‑term scalability.
- Decompose monolithic applications (Rails, Django, Laravel) into domain‑based services or bounded contexts, using domain‑driven design principles.
- Define integration and data synchronization patterns between distributed systems, ensuring schema evolution and API versioning best practices.
- Architect core platform services—authentication, identity, content, and analytics—shared across web and mobile products.
- Apply deep hands‑on knowledge of AWS (EC2, ECS/EKS, Lambda, S3, RDS/Postgre
SQL, Event Bridge/SNS/SQS) and IaC tools (Terraform, Cloud Formation). - Introduce observability, monitoring, and CI/CD standards (Datadog, Open Telemetry, Git Hub Actions, Circle
CI) that support secure, high‑quality releases. - Provide technical mentorship and architectural reviews to ensure strong engineering standards and knowledge transfer across teams.
- Partner with Product, Design, and Engineering leaders to guide architecture decisions that optimize both user experience and technical sustainability.
- Contribute to architecture guilds and domain working groups, defining shared frameworks and principles for system evolution.
- Communicate architectural trade‑offs clearly—speed vs scalability, build vs buy, monolith vs microservice—to technical and non‑technical stakeholders.
- Author and socialize Architecture Decision Records (ADRs), domain maps,…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).