Astera Labs Tech Lead Automation Engineer at Astera Labs responsible for owning and building internal automation platforms and developing new operational systems. This role involves architectural decisions, designing data models and APIs, and shipping production features using AI coding tools.
Responsibilities
We're looking for a hands-on Tech Lead, Software Engineer to own and build the platforms that power how our company operates. You'll evolve existing production systems, develop new applications from the ground up, and set the technical direction for solutions spanning workflow automation, integrations, identity, and operational data.
This is a builder's role. You'll make architectural decisions, design data models and APIs, write code, and ship production features yourself. You'll also use AI coding tools like Claude Code, Cursor, and GitHub Copilot as part of your daily workflow to accelerate development and delivery.
You'll have the autonomy to identify problems, decide what to build, and turn business needs into reliable software that teams across the company use every day.
Role responsibilities:
Platform Ownership
Take technical ownership of our internal automation platforms end-to-end — architecture, data model, background sync/scheduling, and roadmap.
Design and ship full-stack features: backend services, role-based access control, approval workflows, and frontend UI.
Maintain and extend integrations with the external systems these platforms depend on — SaaS tools, cloud infrastructure, and internal directory/identity services.
Qualification
Exposure to licensingA strong bias toward automating manualWhat strong candidates often look likeWhy this role is interesting
Required
BS/MS in Computer Science with 7+ years of professional software engineering experience.
Demonstrated ownership of a production web application end-to-end: backend (Python; FastAPI or similar), relational database design (PostgreSQL, SQL, schema migrations), and frontend work.
Experience integrating with enterprise SaaS APIs (e.g. Atlassian suite, Microsoft 365, GitHub/Bitbucket) and cloud infrastructure APIs (compute/storage, job schedulers).
Working knowledge of identity and access management — RBAC, SSO/OAuth2, and group provisioning via a directory service (LDAP or equivalent).
Design and build new operational systems from the ground up in response to emerging business needs, including systems of record for tracking assets and entitlements, and dashboards that give teams visibility into usage, cost, and status.
Grow existing tooling in these areas from functional-but-narrow into fuller self-service products.
SG&A & Cross-Functional Automation
Experience designing systems of record or inventory/asset-tracking tools, and the dashboards that surface their data to different audiences.
Exposure to licensing, entitlement, or lifecycle-tracking systems (software licenses, IP/asset lifecycle, or similar compliance-adjacent tracking) is a strong plus.
Fluency with AI-assisted coding tools (Claude Code, Cursor, GitHub Copilot) as part of a daily development workflow.
A strong bias toward automating manual, cross-functional processes, and comfort scoping those flows directly with non-technical stakeholders (IT, HR, Finance).
A track record as a hands-on technical lead — someone who owns architecture decisions and personally builds a meaningful share of the system, not just one who delegates.
What strong candidates often look like
They've owned an internal platform end-to-end before — not just contributed features to one — and are as comfortable designing a database schema as they are debugging a flaky integration with a third-party API. They understand that access provisioning, asset tracking, and building insights are fundamentally the same problem — manual handoffs that should be code — and they get energy from turning that insight into a working system. They use AI coding tools fluently as part of how they build, not as an occasional aid. They can sit with an IT or Finance stakeholder, map out a manual process on a whiteboard, and walk away knowing exactly what to build — and they're just as comfortable being the only engineer on the project as they are pulling in help when the roadmap demands it.