Member of Technical Staff, Machine Learning (remote, Spain)
Free to start · No card · 5 credits the moment you sign up
Job description
About the Client
Our client is an AI-native product company built to replace how billions of people manage their digital lives — starting with email, notes, and task tools that were never designed to be AI-native. It's backed by multi-million-dollar investment and built remote-first from day one, with a clear target: cut the time it takes users to get everyday things done by roughly 90%. That means solving the problems most AI products avoid — long-running workflows, persistent context, and reliable behavior under real-world, non-deterministic conditions. The team is small and high-talent-density by design, not by necessity, and moves at a pace that matches the scale of what it's building.
About the Role
As a Member of Technical Staff, Machine Learning, you'll build core ML components and work on real production systems from day one — learning how large-scale ML behaves outside of research settings. This role is for engineers who want to develop strong systems judgment by shipping, debugging, and iterating on real-world ML.
What You'll Work On
Build and improve ML components across data, training, evaluation, and inference
Fine-tune and adapt models as part of larger production systems
Implement evaluation and testing to understand model behavior
Help build and maintain data pipelines for real-world and synthetic data
Debug model issues, performance problems, and production incidents
Ship improvements iteratively and learn from real user feedback
Work closely with senior ML engineers and product teams
Work under real production constraints: latency, cost, reliability, and safety
Requirements
Strong foundations in machine learning and modern neural architectures
Some hands-on experience training, fine-tuning, or deploying ML models
Comfortable writing production-quality code and learning new tools quickly
Curious, coachable, and eager to learn from real production systems
Able to work through ambiguity with guidance, growing ownership over time
A bias toward shipping, iteration, and continuous improvement
Tech Stack
Python · PyTorch / JAX · production ML systems running on GPUs
What Success Looks Like
ML models in production meet accuracy, latency, and reliability targets
Production issues are found quickly, debugged effectively, and root-caused
Data pipelines, training loops, and inference systems stay robust, reproducible, maintainable
Effective collaboration with engineers, product, and research to ship reliable ML-powered features
Iteration is driven by real-world signals and measurable improvement
What to Expect
The best products in the world are built by small, world-class teams. Decisions are made collectively, at rapid speed — balancing high-quality shipping with fast learning. You'll be expected to bring structure, exercise judgment, and execute independently.
Compensation and benefits are competitive and vary by location; the package includes base salary and equity, discussed openly with you as part of the process.
If there's a fit, expect 3–4 interviews total, followed by a prompt, transparent decision. To be considered, please make sure to answer the screening questions in the application form — we're not able to review submissions that skip them.
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for DNA325. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.