Design Engineer, Frontend / Full-Stack (US)
Lola • New York City Metropolitan Area
Company
Lola
Annual salary
$150k – $350k/yr
Location
New York City Metropolitan Area
Listed
27d ago
- Experience:
- 1+ years
- Workplace:
- In person at the New York office 4-5 days a week. No relocation support.
- Equity:
- None
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in New York City Metropolitan Area.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
Lola is looking for a Design Engineer who pairs strong frontend skills with design judgment. You'll own interfaces from early concept through shipped product, and you'll be Lola's first dedicated design engineer. Frontend engineering experience is required. Full-stack experience is a plus. You should be AI-native and use a range of AI design and coding tools every day.
More information here: https://notes.granola.ai/t/edf23f34-c321-45e0-81d1-030fc048bb58-008umkv4
Common questions
How do I apply for the Design Engineer, Frontend / Full-Stack (US) role at Lola? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Lola role pay? +
The listing gives $150k – $350k/yr.
Is this role remote? +
The listing gives the location as New York City Metropolitan Area. In person at the New York office 4-5 days a week. No relocation support.
Full-Stack Developer interview prep
Questions Full-Stack Developer interviewers often ask. They aren't taken from this listing.
How do you decide where a piece of logic belongs, on the frontend or the backend, when either could technically handle it?
I put anything involving trust, validation, or business rules on the backend, since frontend logic can always be bypassed by a direct API call, and I keep the frontend focused on presentation and responsiveness. Duplicating critical logic on both sides just creates two places it can drift out of sync.
What's your approach to designing an API that a frontend team you don't control will consume?
I design around the frontend's actual use cases rather than just mirroring the backend's internal data model, and I version the API from the start so backend changes don't silently break a frontend I'm not there to coordinate with in real time.
How do you debug an issue when you can't tell if it originates in the frontend, the backend, or the data layer?
I check the actual data at each boundary, what the frontend sent, what the backend received, and what the database returned, rather than guessing based on where the symptom is visible. The layer where a bug shows up and the layer where it originates are often different.
How do you balance page load performance against the amount of client-side interactivity a feature needs?
I default to server-rendering the initial content that users need immediately and load interactive pieces progressively, rather than shipping one large client bundle upfront. Interactivity that isn't needed on first paint shouldn't be part of the cost of first paint.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →