Job Summary

We are looking for a hands-on Tech Lead with a strong background in SaaS

platforms and mobile application development, who will own the technical

direction of one of our product teams (Team Loopym or Team Knightriders) within

Company OS. This role owns the overall health of the codebase, drives

engineering excellence, and ensures high standards in quality, security, and

performance. You will lead by example, writing code, guiding architecture, and

mentoring engineers, while integrating modern tooling, including AI/automation

agents, to improve development velocity and product reliability. You can

articulate why each agile practice exists, when it's the right tool, and when

it isn't, we hire judgment, not certifications. Our tech leads are a healthy

blend of eternal idealism and pragmatism, who have a track record of making

good judgement decisions based on data.

Key Responsibilities

1. Codebase Ownership

Take full ownership of the architecture, structure, and maintainability of the

codebase.

Enforce coding standards, code reviews, and best practices.

Drive refactoring and technical debt management.

2. Architecture & Technical Leadership

Design scalable, resilient architectures for SaaS platforms and mobile apps

(iOS/Android).

Make key technical decisions on frameworks, APIs, and infrastructure.

Ensure systems are designed for scalability, reliability, and extensibility.

Think about software, organization, and product as one system.

3. AI/Automation Agents & Tooling

Implement and manage AI-driven or automated engineering agents (e.g., for code

generation, testing, monitoring).

Evaluate and integrate tools that improve developer productivity and software

quality.

Establish guardrails for safe and effective use of automation/AI in development

workflows.

Run evals on agent output so we can tell when an agent-owned workflow is

regressing.

4. Quality Engineering

Champion a quality-first mindset across teams.

Implement robust testing strategies (unit, integration, end-to-end, automated

testing).

Ensure CI/CD pipelines enforce quality gates before deployment 5. Security

& Compliance.

Embed security best practices in development (secure coding, vulnerability

management, data protection).

Conduct code audits and ensure compliance with relevant standards (e.g.,

OWASP).

Collaborate with DevOps on secure infrastructure and deployment.

6. Performance & Scalability

Optimize system performance across backend, frontend, and mobile platforms.

Monitor application performance and resolve bottlenecks.

Ensure systems can scale efficiently with user growth.

7. Team Leadership & Mentorship

Lead and mentor engineers through technical guidance and coaching.

Conduct code reviews and provide constructive feedback.

Foster a culture of ownership, accountability, and continuous improvement.

8. Cross-Functional Collaboration

Work closely with Product Managers, Designers, and DevOps teams.

Translate product requirements into technical solutions.

Align engineering efforts with business goals and timelines.

Partner with the other Tech Lead and the Engineering Manager on shared Agent

Platform decisions, we don't want N divergent stacks across product teams.

Leverage data and dashboards to drive continuous improvement decisions based on

evidence rather than blind adherence to a process.

Requirements:

Bachelor's degree in Computer Science, Engineering, or

related field (or equivalent experience).

6–10+ years of software development experience, including

leadership responsibilities.

Proven experience in SaaS platforms and mobile application

development.

Strong experience with modern frameworks, APIs, and

cloud-based architectures.

Experience scaling systems in high-growth SaaS environments.

Background in observability tools (e.g., logging,

monitoring, tracing systems).

You've shipped non-trivial software across at least two

different production stacks, our stack today will not be our stack in 2 years.

You've used AI coding agents, skills in an orchestrated

agentic ecosystem on production code and can describe what they're good at,

what they're not, and how you measured their output, and guardrails you can

place to protect quality.