hr
Posted 3 hours agoSenior AI Builder - Talent Pool
at Wrike
Hybrid
Responsibilities
- Make technical and product tradeoff calls yourself, manage the risk, and push things over the finish line
Requirements
- Wrike is opening a new talent track for builders- senior engineers who take a feature from a rough idea to a production system on their own, and who use AI as a genuine multiplier rather than a buzzword.
- AI is not optional here.
- You’re expected to work AI-native: using it daily to move faster, and knowing when to push back when it suggests something that doesn’t hold up.
- Designed, built, and shipped end-to-end features across the full stack- including a Java/Spring backend, REST APIs, data layer, testing, infrastructure touches, and rollout- while utilizing modern frontend technologies like TypeScript, React 19, Microfrontends, and Module Federation, alongside legacy Dart components.
- Use AI tools (Cursor, Claude/Codex, our internal AI portal and MCP) as a daily part of how you build- including writing your own automations and skills where they save real time
- Challenge AI output and product asks alike when they don’t hold up- critical thinking is part of the job, not a side skill Your
- Strong full-stack engineering experience, with deep comfort in Java (21), Spring, REST APIs, and SQL, TypeScript, React 19
- Advanced, hands-on use of AI coding tools as part of your daily workflow- you’re past the learning curve already
- Java (21), Spring, REST APIs, SQL
- TypeScript, React 19, Redux, Dart
- PostgreSQL, Redis, RabbitMQ
- Unit/integration testing, Java web stack
- AI tooling: Cursor, Claude/Codex, Zencoder, internal AI portal, internal MCP Why Join Wrike?
- Interested in joining Wrike when the right opportunity opens up? Apply to our Senior AI Builder today.
Benefits
- Built for teams and organizations looking to collaborate, create, and exceed every day, Wrike brings everyone and all work into a single place to remove complexity, increase productivity, and free people up to focus on their most purposeful work. Our vision: A world where everyone is free to focus on their most purposeful work, together. About the role:
- 25 calendar days of paid vacation
- Sick Leave Compensation (5 Paid Uncertified Sick Days)
- Parental Leave: 18 Weeks Maternity / 4 Week Paternity 2 Volunteer Days
- Medical Insurance (Employees + Dependents)
- School Allowance (Up to €600/month for school aged kids)
- Office Lunch Allowance (via Wolt) on Wednesdays / Thursdays
Contact
- Check out our LinkedIn Life Page , Company culture page , Instagram , Wrike Engineering Team , Medium , Meetup.com , Youtube for a feel for what life is like at Wrike.
Additional details
- It’s a newly created role for someone who already operates autonomously and wants to keep doing that inside a company with real scale, real users, and daily production deployments. You take a high-level idea, figure out what actually needs to be built by talking to the right people, and ship it end-to-end: backend logic, frontend touches where needed, automated and manual testing, infra, and the dozen adjacent things a real feature needs.
- You read the existing codebase with judgment- reusing what’s solid, rebuilding what isn’t, and refusing to leave tech debt for the next person.
- If you’ve written your own automation, scripts, or internal tooling to remove friction from your own workflow, that’s exactly the instinct we’re hiring for. Your Impact:
- Take ambiguous, high-level product ideas and turn them into a concrete technical plan- by asking the right people the right questions, not waiting for a fully written spec
- Navigate a real, living codebase- deciding what to reuse, what to rebuild, and holding the line against unnecessary tech debt
- Think in systems: anticipate second-order effects before they become incidents
- A track record of owning features or systems end-to-end, not just executing a fully-specified ticket •
- Experience navigating and improving an existing, non-trivial codebase- this isn’t a greenfield role
- Comfort making decisions under ambiguity and owning the outcome, good or bad
- Backgrounds we tend to see succeed here: technical founders, early engineers at startups who built the first version, small-company CTOs/Heads of Engineering, or senior engineers with active, recent open-source or side-project work Our stack: