דרושים » תוכנה » Software Architect

Required Principal Software Architect
About the Role:
This is a rare, high-leverage role at the intersection of deep technical craft and strategic platform thinking. As our Principal Software Architect, you will own the technical vision for our foundational infrastructure and shape how engineering works across every team in R&D.
You won't be embedded in a single product team - you'll operate across the entire R&D organization, tackling the hardest architectural challenges: data modeling at scale, integration system design, enterprise readiness, performance, and cost efficiency. You'll report directly to the VP of R&D and serve as a technical force-multiplier for our directors and team leads.
If you want to architect systems that serve thousands of engineering organizations - and leave fingerprints on every layer of a fast-scaling SaaS platform - this role is for you.
What You'll Do:
System Design & Scaling:
Architect robust, high-performance, and scalable systems across our entire platform.
Lead the design of resilient, performant, and maintainable core infrastructure as we evolve our SaaS ecosystem.
Design a more robust, performant, and generic integration layer - making our 3rd-party integrations more scalable, easier to build, and higher quality.
Architect high-throughput data and messaging pipelines to support robust, real-time data ingestion and event-driven architectures.
Data Modeling & Analytics:
Redesign and optimize our data modeling layer - including hierarchies, entity types, and relationships - to improve flexibility and scale.
Architect a comprehensive data analytics pipeline capable of handling large-scale data source processing and aggregated metric calculations.
Design effective engineering metrics delivery pipelines - enabling framework-level measurement of developer productivity and platform health.
Enterprise Readiness & Security:
Drive technical planning, tracking, and execution of cross-functional enterprise initiatives including FedRAMP compliance and SSDLC practices.
Design and implement robust security frameworks aligned with enterprise customer requirements.
Reliability & Quality:
Conduct deep-dive root cause analyses on production incidents and drive structural improvements to system reliability.
Design and implement a comprehensive end-to-end load and performance testing ecosystem.
FinOps & Cost Architecture:
Analyze cloud infrastructure spend and identify architectural changes that optimize cost without compromising performance.
Challenge existing storage and infrastructure decisions - asking the right questions about where data lives, why, and at what cost.
Technology Strategy & Mentorship:
Periodically review and recommend technologies, SDKs, and platforms to support our evolving architectural standards.
Mentor and uplevel technical leads across R&D teams, raising the bar for engineering quality and architectural thinking.
Push for the adoption of AI-SDLC practices within R&D to improve engineering velocity.
Participate in senior technical hiring to help us attract world-class engineers.

We are looking for a Senior Software Architect to help define and evolve the architecture of our SaaS platform and core products. You will work closely with product, delivery, and engineering squads to design scalable, reliable systems, set technical direction, and guide teams in making high‑quality architectural decisions that balance delivery speed with long‑term sustainability.
This is a hands‑on, senior technical leadership role: you will spend most of your time shaping architectures with teams, reviewing designs and critical code, and driving shared standards and patterns across the organization, all in an advance agentic environment.
Responsibilities:
Architecture & technical leadership:
Define and evolve the architecture for key domains in our platform (APIs, services, data flows, integration, observability, security).
Translate business and product requirements into clear, pragmatic technical designs and architecture roadmaps.
Create and maintain architecture artefacts: diagrams, decision records (ADRs), reference implementations, and guidelines.
Evaluate design options and technology choices, articulate trade‑offs, and lead the decision‑making process with stakeholders.
Push forward the agentic mindset and implementation.
Working with squads (R&D):
Partner with squad leads and senior engineers to design solutions, break down complex problems, and keep implementations aligned with the target architecture.
Participate in design / tech reviews, ensuring non‑functional requirements (performance, resilience, security, operability) are addressed early.
Provide hands‑on support where it matters most: spike and prototype critical flows, review complex pull requests, and help debug tricky production issues.
Partnering with Product:
Collaborate with Product to shape technical feasibility, sequencing, and scope for roadmap items and cross‑squad initiatives.
Communicate complex technical topics in simple language to non‑technical stakeholders when discussing roadmap options and trade‑offs.
Standards, reuse, and platform mindset:
Define and promote architecture principles, coding standards, and reusable patterns (modules, libraries, services) that reduce duplication and technical debt.
Champion platform thinking: design services and components that can be safely reused across teams and products.
Drive adoption of shared platform capabilities (observability, CI/CD, authentication, data, DevOps tooling) across squads.
Quality, reliability, and continuous improvement:
Ensure architectures are observable, operable, and resilient by design; partner with DevOps/SRE on deployment, monitoring, and incident response.
Identify areas of high technical debt or architectural risk and lead structured remediation initiatives.
Help define and track technical KPIs (e.g., performance, reliability, incident volume) tied to architecture decisions.
Mentoring and leadership:
Act as a technical mentor and sounding board for senior engineers and tech leads, helping them grow their architecture skills.
Foster a culture of thoughtful design, documentation, and constructive technical debate.
Lead by influence rather than authority: you help teams make better decisions instead of making every decision for them.