Planned hiring
Platform Engineer
Lucy is a proactive AI coach from Lucy Labs that lives on your desktop as a cloud-backed app.
Planned hiring. This description explains the work we are preparing to hire for; it is not a confirmed start date or offer.
Build the shared infrastructure and release paths that let Lucy's engineers deliver a trustworthy desktop and connected services. Your work makes it straightforward to create an environment, ship an identifiable build, understand its behavior and recover when a change fails. Start with a dependable path for the funded product slice, then extend it as teams and customer needs grow.
The role
Build the shared infrastructure and release paths that let Lucy's engineers deliver a trustworthy desktop and connected services. Your work makes it straightforward to create an environment, ship an identifiable build, understand its behavior and recover when a change fails. Start with a dependable path for the funded product slice, then extend it as teams and customer needs grow.
What you will build
- Create reproducible development, test and production environments, with versioned infrastructure and configuration, clear access boundaries and documented recovery procedures.
- Build CI/CD that connects a source revision to tested artifacts, required security and quality evidence, deployment approval and rollback. Make missing or failed checks visible and prevent them being treated as a successful release.
- Partner with Desktop Engineering on signing, distribution and update delivery. Provide protected build credentials and artifact provenance; Desktop owns installation behavior and operating-system compatibility, with QA validating the supported matrix.
- Provide service deployment patterns, secrets storage and rotation, service identity integration and least-privilege access with Product Security. Exercise credential changes and rollback before relying on them with customer data.
- Build content-minimized logs, metrics and traces that help teams diagnose failures across capture, ingestion, inference and coaching without exposing private work. Give service owners useful dashboards and a clear route to add instrumentation.
- Measure infrastructure usage, bottlenecks and recurring developer friction. Improve build speed and operating cost with evidence; document the limits of supported environments and remove manual steps that repeatedly cause mistakes.
How ownership works
Product and data engineers own their components, tests and production defects. AI Engineering owns inference runtime and model-serving behavior; you provide the shared service platform. Product Security defines and verifies technical control requirements with you. SRE owns service objectives, incident learning and recovery engineering when staffed; any earlier reliability duties need a named, bounded allocation that transfers explicitly. Shared operational work reduces available delivery time. Corporate IT and the customer support queue sit outside this role.
What you bring
- Experience building and operating reproducible service infrastructure and deployment pipelines, with examples of a release failure you made easier to diagnose or recover from.
- Practical programming and automation skills, including testing infrastructure changes and reviewing generated code rather than trusting it by default.
- Working knowledge of service identity, network boundaries, secrets, artifact integrity and observability, and the ability to explain tradeoffs to component owners.
- Clear written documentation and a habit of improving the developer experience through actual use and feedback. Experience supporting desktop release distribution is useful; mastery of every tool is not expected.
Your first 90 days
Map the initial product's build, deployment and access dependencies with its owners. Deliver one repeatable release path with traceable checks and demonstrate rollback in the required environment. Establish useful telemetry, a secrets-rotation exercise and an environment runbook another engineer can follow. Agree the next improvements against measured friction, product risk and available capacity.
Next step
Express your interest
Email people@lucylabs.ai with the role title, a short introduction and relevant CV or portfolio. This is planned hiring; we will confirm current availability and the individual working arrangement.
Lucy Labs confirms the working arrangement, employer, location, eligibility, compensation and terms for each role. Our mailing address does not determine the job location or guarantee remote employment, worldwide eligibility or visa sponsorship.
Do not send passwords, government identifiers or bank details. Read the application privacy notice.
Frequently asked questions
Is this role open at Lucy Labs?
Lucy Labs lists this role as planned hiring. Availability depends on the need, team readiness and individual arrangement; it does not promise an immediate vacancy or start date.
Where does this work take place at Lucy Labs?
Lucy Labs confirms the working arrangement, employer, location, eligibility, compensation and terms for each role. Our mailing address does not determine the job location or guarantee remote employment, worldwide eligibility or visa sponsorship.
What does this role own at Lucy Labs?
Lucy Labs: Build the shared infrastructure and release paths that let Lucy's engineers deliver a trustworthy desktop and connected services. Your work makes it straightforward to create an environment, ship an identifiable build, understand its behavior and recover when a change fails. Start with a dependable path for the funded product slice, then extend it as teams and customer needs grow.
How do I express interest in Lucy Labs?
Email people@lucylabs.ai with the role title, a short introduction and relevant CV or portfolio. Lucy Labs uses the application to assess and respond to it; retention for future opportunities is a separate explained purpose and choice.
