Find a job 
Featured Companies 
Featured Universities 
For Companies At a Glance
- Tasks: Own product problems from start to finish, building solutions in Laravel.
- Company: Fast-scaling AI tech company focused on impactful product development.
- Benefits: Competitive salary, flexible work environment, and opportunities for rapid growth.
- Why this job: Make a real impact by shipping solutions weekly and owning outcomes.
- Qualifications: 5+ years of Laravel experience and strong backend skills required.
- Other info: Join a dynamic team that values speed, clarity, and simplicity.
The predicted salary is between 36000 - 60000 £ per year.
AIApply is scaling fast. What we need now is product clarity, ruthless prioritisation, and fast shipping — not process for process’ sake. This role is for a Product Engineer: someone who can own product problems end-to-end, make strong decisions, and build the solution themselves in Laravel. If you like owning outcomes, shipping weekly, and sweating details, keep reading.
What you’ll own
- You will own core product surfaces from problem → solution → impact.
- Examples:
- Activation & onboarding flows (first 24h experience)
- Retention loops (day 7 / day 30)
- Auto-Apply workflows (quality, confidence, transparency)
- Core dashboard UX and system clarity
- Monetisation & plan boundaries (what users actually understand)
You will:
- Identify the highest-leverage product problems
- Define the simplest possible solution
- Build it yourself (Laravel + frontend)
- Measure impact and iterate quickly
What you’ll do day-to-day
Product
- Turn fuzzy problems into clear, testable product bets
- Kill ideas that don’t move activation, retention, or revenue
- Write concise specs only when useful (often a few bullets is enough)
- Make trade-offs without needing consensus
Engineering
- Ship production-quality Laravel code
- Improve and extend existing systems (not rewrite for fun)
- Work directly with Stripe, analytics, AI workflows, queues, cron jobs
- Debug real user issues, not theoretical ones
Data & outcomes
- Think in funnels, cohorts, and deltas
- Obsess over activation, retention, LTV, and churn
- Use data to decide what not to build
- Own results, not just delivery
Required background
- You must have:
- 5+ years experience with Laravel in production
- Strong SQL and backend fundamentals
- Frontend competence (enough to ship clean UX without hand-holding)
- Experience owning features end-to-end in a real product
- Product intuition grounded in user behaviour, not opinions
- Bias toward speed, clarity, and simplicity
You likely have:
- Worked at an early-stage or scaling SaaS
- Strong opinions about bad UX and bloated products
- Shipped things that materially moved metrics
- Little patience for bureaucracy
What we explicitly don’t want
- “Pure” PMs who don’t build
- Process-heavy frameworks without output
- Jira theatre and over-documentation
- People optimising for optics over impact
- People uncomfortable saying “no”
Product Engineer (Senior Laravel) — AIApply in York employer: AIApply
Contact Detail:
AIApply Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land Product Engineer (Senior Laravel) — AIApply in York
✨Tip Number 1
Get your hands dirty with the tech! If you're applying for a Product Engineer role, show us you can build solutions in Laravel. Share your GitHub projects or any side hustles that demonstrate your coding skills and problem-solving abilities.
✨Tip Number 2
Be ready to talk about your past experiences. We want to hear how you've owned product problems from start to finish. Prepare some solid examples of how you’ve made tough decisions and shipped features that had a real impact on users.
✨Tip Number 3
Show us your data-driven mindset! Be prepared to discuss how you've used metrics to inform your decisions. We love candidates who can think in funnels and cohorts, so bring those numbers to the table when we chat.
✨Tip Number 4
Apply through our website! It’s the best way to ensure your application gets seen by the right people. Plus, it shows us you’re genuinely interested in being part of our fast-paced team at AIApply.
We think you need these skills to ace Product Engineer (Senior Laravel) — AIApply in York
Some tips for your application 🫡
Be Authentic: When you're writing your application, let your true self shine through. We want to see your personality and passion for the role, so don’t be afraid to show us what makes you tick!
Tailor Your Application: Make sure to customise your application to highlight your experience with Laravel and product ownership. We’re looking for someone who can own outcomes, so showcase your relevant achievements and how they align with our needs.
Keep It Concise: We appreciate clarity and simplicity, just like in our products. Avoid lengthy paragraphs and get straight to the point. Use bullet points if it helps convey your message more effectively!
Apply Through Our Website: Don’t forget to submit your application through our website! It’s the best way for us to receive your details and ensures you’re considered for the role. Plus, we love seeing applications come directly from our site!
How to prepare for a job interview at AIApply
✨Know Your Laravel Inside Out
Make sure you brush up on your Laravel skills before the interview. Be ready to discuss specific projects where you've used Laravel to solve real problems. Highlight your experience with production-quality code and how you've improved existing systems.
✨Showcase Your Problem-Solving Skills
Prepare examples of how you've turned fuzzy problems into clear, actionable solutions. Think about times when you identified high-leverage product issues and how you defined and built the simplest possible solutions yourself.
✨Be Data-Driven
AIApply values data-driven decision-making, so come prepared to discuss how you've used metrics to inform your product decisions. Talk about your experience with activation, retention, and how you've measured impact in previous roles.
✨Emphasise Speed and Clarity
This role is all about fast shipping and clarity. Be ready to explain how you've prioritised speed over process in your past work. Share instances where you've made trade-offs without needing consensus and how that led to successful outcomes.
