lovable
Jobs & hiring outlook.
Explore 78 grouped openings and the hiring signals in lovable’s public postings. Compare the work, the locations, and the requirements before your next move.
Openings over time.
Daily observations of lovable’s public job board. Advertised postings, rather than headcount or completed hires.
Tracking since 27 Oct 2026. The latest successful check on each UTC day replaces that day’s observation. Failed checks do not record zero openings.
View the recorded data (5 days)
Swipe the table to see all workplace counts.
| Day (UTC) | All postings | Remote | Hybrid | Onsite | Unstated |
|---|---|---|---|---|---|
| 2026-10-31 | 80 | 1 | 5 | 72 | 2 |
| 2026-10-30 | 79 | 1 | 5 | 71 | 2 |
| 2026-10-29 | 82 | 1 | 5 | 74 | 2 |
| 2026-10-28 | 82 | 1 | 5 | 74 | 2 |
| 2026-10-27 | 82 | 1 | 5 | 74 | 2 |
A closer look at the work.
The workplace mix and role categories in lovable’s verified inventory.
Workplace mix
80 verified postings
- Remote11%
- Hybrid56%
- Onsite7290%
- Not stated23%
Role categories
Grouped openings; title-based categories
Open jobs at lovable
No openings match these filters. Clear the filters to see this company’s jobs.
Check a public job to get started →What the postings actually say.
These counts describe 80 verified postings. Policies may differ between roles and do not establish an individual candidate’s eligibility.
Does lovable offer visa sponsorship?
Across 80 verified postings at lovable, 0 explicitly state visa sponsorship is available, 0 state sponsorship is unavailable, 0 contain conditional or conflicting language, and 80 do not mention sponsorship.
What is lovable’s remote work and location policy?
1 postings are labeled remote (0 explicitly worldwide), 5 hybrid, and 72 onsite.
Evidence review from Luxembourg
Selected sponsorship need: yes. This selection does not assess citizenship or personal permission to work.
0 postings have no identified conflict; 1 conflict with the selection; 79 leave conditions unresolved.
Work authorization, citizenship & clearance breakdown
0 postings contain an explicit work authorization requirement.
Citizenship: 0 required, 0 preferred, 0 explicitly not required, 80 unstated, 0 conflicting, 0 not assessed.
Clearance: 0 required, 0 preferred, 0 explicitly not required, 80 unstated, 0 conflicting, 0 not assessed.
0 postings explicitly describe worldwide remote applicant policies. Named applicant countries: None assessed.
Employer office countries, separate from remote applicant policies: Not available.
Read 2 examples from original postings
Examples below; the counts above cover all qualifying postings.
- APPLICANT LOCATIONS
Brand & Integrated Marketing Lead, Europe
“You must be based in Stockholm (or ready to be) and have experience launching campaigns in Europe, although the scope of the role will be global.”
Read original posting ↗ - APPLICANT LOCATIONS
Product Experience Specialist (Part Time)
“This is a 3-month contract with a potential 12-month extension and expanded responsibilities, on a part-time basis, based in Lund, Stockholm, or remotely in Sweden.”
Read original posting ↗
Dated source evidence · tracking since 27/10/2026
Most recent observations of source wording. These are separate from daily opening counts and do not reconstruct earlier employer policies.
- Product Partnership Manager
Observed 31/10/2026, 14:22:10 UTC
Original posting ↗ - Head of Technical Accounting & Reporting
Observed 31/10/2026, 14:22:10 UTC
Original posting ↗ - Accounting Close Lead
Observed 31/10/2026, 14:22:10 UTC
Original posting ↗ - Staff Forward Deployed Engineer
Observed 31/10/2026, 14:22:10 UTC
Original posting ↗ - Technical Writer
Observed 31/10/2026, 14:22:10 UTC
Original posting ↗ - Recruiting Operations Specialist | FTC
Observed 31/10/2026, 14:22:10 UTC
Original posting ↗
Observed openings. Clear boundaries.
Counts cover this tracked company board, not every vacancy across the employer. Location variants are grouped in the job list; trend charts count individual source postings. A removal does not prove a hire. Unknown dates, pay and policies stay unknown.
Read our source methodology ↗