> Markdown version of [/jobs/ext/2712800-solution-architect](https://www.wearedevelopers.com/jobs/ext/2712800-solution-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Solution Architect - **Company:** Lynx Llc - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Amazon Web Services, Component-Based Software Engineering, Microsoft Azure, Continuous Integration, Information Engineering, Extract Transform Load (ETL), Python (Programming Language), Lynx, Software Engineering, Systems Architecture, TypeScript, Information Technology, Api Design, Data Pipelines - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/solution-architect-us-lynx-analytics-9605397 ## About the Role * Bachelor's degree in Computer Science, Engineering, or a related field. * 5-8+ years of experience spanning data engineering and software engineering, with demonstrated experience moving into solution or systems architecture. * Track record of designing data models, system architectures, and integration patterns for production systems, not just diagramming them. * Hands-on proficiency in at least one modern language (e.g., Python, Typescript, or similar) and comfort prototyping pipeline or application components personally. * Solid grounding in data engineering fundamentals (pipeline design, data modeling, ETL/ELT) and software engineering fundamentals (API design, testing, CI/CD). * Experience working in a consulting or client-facing environment - comfortable leading discovery conversations, presenting trade-offs, and managing ambiguity. * Experience with cloud platforms (AWS, GCP, or Azure) is a plus. KEY COMPETENCIES * Architectural Judgment: Balances build speed, cost, scalability, and maintainability, and knows when to prototype personally versus hand off to a data or software engineer. * Stakeholder Mentality: Treats the company's and client's goals as their own and is genuinely motivated by delivery success. * Technical Communication: Translates complex architectural decisions clearly for both engineers and non-technical business stakeholders. * Discretion & Integrity: Handles sensitive client and technical information with professionalism and sound judgement. * Problem Solving: Approaches ambiguous technical challenges proactively and with a solution-oriented mindset, taking initiative rather than waiting to be directed. * Collaboration: A team player who builds strong working relationships with delivery teams and communicates effectively across all levels. WHY YOU WILL LOVE IT HERE * A collaborative and global culture that values real outcomes * High ownership, zero micromanagement * Rapid learning opportunities and diverse challenges * Flat organisational hierarchy with high visibility and accessibility to our leaders ## Description Solution Architecture * Own solution architecture for client engagements: data models, system design, integration patterns, and technology choices, translated into designs delivery teams can build from. * Lead technical discovery with clients: understand requirements, assess existing systems, and present architectural options and trade-offs to technical and non-technical stakeholders. * Define standards, reusable patterns, and reference architectures that other engineers at Lynx can build on across engagements. * Make pragmatic trade-offs between build speed, cost, scalability, and maintainability, and clearly explain the reasoning behind them. * Review technical designs and key implementation decisions from delivery teams to ensure they stay aligned with the intended architecture. Hands-On Validation & Enablement * Validate architectural decisions hands-on - building prototypes, proofs of concept, and early data pipeline or application components to test feasibility before full-scale build. * Partner with data engineers and software engineers to unblock them on ambiguous technical problems, then hand off cleanly once the direction is proven. * Set up early evaluation, testing, or monitoring approaches so delivery teams inherit a working foundation, not just a diagram. * Contribute to internal tooling, accelerators, and knowledge-sharing that raise the technical bar across the practice. ## Related Videos - [Lynx: Native for More](https://www.wearedevelopers.com/videos/1445-lynx-native-for-more) - [API Design - Getting Started](https://www.wearedevelopers.com/videos/33-api-design-getting-started) - [Do TypeScript without TypeScript](https://www.wearedevelopers.com/videos/327-do-typescript-without-typescript) - [Solution Architecture: A Startup Perspective](https://www.wearedevelopers.com/videos/778-solution-architecture-a-startup-perspective) - [Rest API Antipatterns](https://www.wearedevelopers.com/videos/100208-rest-api-antipatterns) - [Vuejs and TypeScript- Working Together like Peanut Butter and Jelly](https://www.wearedevelopers.com/videos/127-vuejs-and-typescript-working-together-like-peanut-butter-and-jelly) ## Related Articles - [What Are The Top Skills Required For Azure Developers?](https://www.wearedevelopers.com/magazine/77-what-are-the-top-skills-required-for-azure-developers) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)