Role Summary A junior engineer who owns product across multiple live surfaces: keeping an existing app with ~2,000 users running and improving, while shipping new MVPs and features fast using AI coding tools. Jack of all trades, but the trade is engineering.
Key Responsibilities
Own & Maintain
- Triage and fix bugs, monitor for errors/downtime, keep the app stable and running
- Ship small-to-medium features and improvements without breaking what's already live
- Practice safe deploys: know how to roll back, back up data, and avoid taking down a product real users depend on
Build & Ship
- Go from idea to working MVP same-day using AI coding tools
- Know when a prototype is "good enough to test" vs. when it needs to be built properly
- Move between unrelated products/projects in the same week without losing quality
Judgement & Triage
- Decide in real time whether a request is a 5-minute fix, a same-day build, or needs to be pushed back
- Prioritize across multiple products competing for the same hours in a day
- Know when to escalate/hand off vs. solve it solo
Operations / Glue Work
- Coordinate across teams (ops, clinical, sales, engineering) to unblock issues
- Set up automations, dashboards, and reports that the team actually needs
- Document processes, create SOPs, maintain internal knowledge base
Required Profile
- Builder first: default instinct is to open the editor and try something, not write a spec and wait
- Has owned or maintained something in production before — has broken something and had to fix it
- Generalist by preference for variety — comfortable being the only engineer on multiple things at once
Skills
- Proficient with AI coding tools; can independently build and ship functional web apps, automations, and integrations
- Solid basics: HTML/JS, APIs/REST, databases, Git (branching, safe deploys)
- Can read error logs/monitoring and debug a live issue without hand-holding
- Clear, direct communication — written and verbal
- Fluent in English, French preferable.
Experience
- At least one year building or shipping product-facing work (internships, freelance, side projects, or a job)
- Can point to something real: a live app, a shipped feature, a project with actual users — not just coursework
Idóneo Candidate Signals
- Has been the only engineer on something live with real users, and it didn't fall over
- Reaction to ambiguity is "let me try something" not "who owns this?"
- Has shipped side projects with AI tools and can talk through the decisions, not just show the demo
📌 Junior Developer (Madrid)
🏢 Chedar
📍 Madrid