Build Product, Not Pressure: Inside easyWerkstatt’s UX-First, Weekly-Release Engineering Culture

Takeaways from “Thomas Grömer, Founder von easyWerkstatt”

If you’re a software engineer tired of rotating client projects, artificial deadlines, and weekend fire drills, the session “Thomas Grömer, Founder von easyWerkstatt” will catch your attention. Thomas Grömer outlines a product company that deliberately works differently: small, focused, user-centric—and with plenty of room for engineering voices to matter. At easyWerkstatt, three developers and one full-time UX professional build and operate an online software product, shipping on a weekly cadence. The result is a way of working that prizes stability, learning, and product quality over speed for speed’s sake.

From our DevJobs.at editorial seat, we listened closely as Thomas explained easyWerkstatt’s culture, hiring approach, and technical choices—and why the combination of product focus, experimentation, and a rural location is compelling for engineers who want ownership without sacrificing work-life balance.

Product company, not agency: How that changes everyday engineering

The key difference is the model: easyWerkstatt isn’t an agency delivering projects for single clients. It’s a product company. That shapes everything—from releases to team composition.

• Weekly releases: “We do an update once a week,” Grömer says. Whatever is finished and tested ships; whatever isn’t rolls into the next update. No drama, no synthetic crunch.
• No deadlines, no weekend work: “We don’t really have overtime, working on weekends …” Time can be arranged reasonably.
• Many small customers, not one boss: Because there are “very many small customers,” the product roadmap serves the majority. The team decides what delivers the most value.

This structure creates an environment where quality and prioritisation matter more than theatrical launches. The cadence is the backbone: weekly updates, frequent team discussions, and clear criteria for what gets built next.

A small, high-impact team—with a serious UX seat at the table

At the moment, the engineering team is three developers plus a full-time UX professional. In a team this size, that’s a strong signal: usability is not an afterthought; it’s core to the product.

For engineers, that means:

• Requirements are anchored in user needs, not only tickets.
• Decisions about “what, how, and in which order” happen collaboratively—with UX in the room.
• User experience improvements are explicitly part of the prioritisation conversation.

The effect is tangible product impact. Code goes live weekly, and developers see their work change the user experience in production.

Rhythm over adrenaline: How weekly shipping actually works

The team ships once a week. The rule is simple: finished and tested goes in; unfinished waits one week.

• Testing is standard: What ships has been tested. No duct tape, no Hail Mary’s.
• Predictable focus blocks: Work is scoped to what can be reasonably completed in a week.
• Experiments are welcome: Exploration doesn’t have to block the release.

This sentence is telling. easyWerkstatt isn’t chasing a mythical perfect roadmap. They want a team that loves continuous product work and is willing to learn, discard, and persist.

It’s one product, but not one track: Web, mobile, and backend playgrounds

Product work can feel repetitive—unless you intentionally build breadth. easyWerkstatt has done just that: alongside the web app, there’s a mobile app, and “quite a lot going on in the background.” If you’re looking for variety, you’ll find it across platforms and system layers.

• Web app with a React frontend
• Mobile apps in React Native
• Backend on “Core”—“basically, more or less, a successor of Express”
• MongoDB, Docker, Elasticsearch

This stack opens up hands-on engineering space—from UI refinements to mobile components, from search (Elasticsearch) to containerisation (Docker). The goal remains consistent: make the same product better every week.

Tech choices with restraint: From Meteor/Angular 1 to React

easyWerkstatt made a hard, necessary shift early on. Their initial stack—Meteor Framework with Angular 1—hit limits.

Together with the team, easyWerkstatt chose React—for two reasons:

• Product performance and stability
• Hiring leverage: “We figured we’ll do well with React and maybe find more people.”

Today, that reasoning holds up. The balance between modern and mature is not an accident; it’s a principle.

That’s a textbook definition of pragmatic product engineering strategy: community maturity, ecosystem readiness, and hiring are part of the tech decision—not an afterthought.

Managing tech debt and priorities: Discipline without dogma

A growing product inevitably generates debt. The difference is whether you manage it or let it manage you. easyWerkstatt’s approach is clear:

• Keep technical debt low
• Continuously prioritise “what gets done now”
• Order features by customer value—“what brings the most to our customers”
• Improve UX continuously

Prioritisation here isn’t an annual exercise; it’s daily leadership work within the team—joint, transparent, with UX in the loop.

Conversations that matter: Collaboration in a small team

If you’ve been limited to a narrow slice of the stack in a big org, this is the opposite. At easyWerkstatt, the team discusses “a lot”—what to build, how to build it, which technologies to use, and in which order. The outcome:

• Real say from day one: As an engineer “you can immediately have a big voice.”
• Shared responsibility: Decisions are made together and owned by the team.
• Learning opportunities arise organically: Experiments are encouraged—even if they never ship.

This collaboration style only works if the people fit—technically and personally. That’s why hiring puts so much emphasis on team fit and motivation to learn.

Rural by design: Lifestyle as a meaningful advantage

A distinctive, concrete USP: easyWerkstatt is located “in the countryside.” That’s not a compromise; it’s an offer.

The message is clear: If you value calm, nature, and more space, you’ll find not just a job but a setting that fits your life. For many engineers, that’s not a perk—it’s decisive.

Hiring in progress: From first contact to optional trial days

The recruiting process is “still in the making,” yet already structured. The steps:

1. Application materials: The formal starting point.
2. Short phone interview: To see if it’s “principally interesting for both sides.”
3. In-depth onsite meeting (at least half a day):

• Conversations with team members—“alone,” candid, and authentic.
• First-hand insight into how work happens, what the team does.
• Space for all questions.

1. Optional trial work: If the candidate wants it—no obligation.
2. Contract and start: When it’s a mutual fit.

What matters most is crystal clear:

Exact stack matching is secondary. Interest and the will to learn take precedence.

For candidates, that means: if you like product work and you’re eager to learn, you’re in a strong position.

The current stack: Focused, mainstream, and well-combinable

To help engineers self-select, stack clarity matters. Thomas Grömer sketches it succinctly:

This selection is deliberate: widely used technologies with strong communities and package ecosystems—and, as Grömer stresses, better hiring chances. The history behind it is equally telling: moving away from Meteor/Angular 1 because performance and the migration path didn’t fit the product. It’s not anti-new; it’s pro-product.

Experiments welcome—no shipping pressure attached

Innovation rarely comes from roadmaps alone. easyWerkstatt invites experiments—even those that never become features. This form of freedom matters:

• It lowers the risk of exploration.
• It keeps the team “on the ball” and prevents getting rusty.
• It surfaces ideas that wouldn’t appear in a strict priority queue.

Crucially, this is anchored in the release discipline: experiments don’t derail shipping. They integrate if they prove out—or get dropped if they don’t. Both outcomes are fine.

Why engineers should take a closer look

From the session, clear reasons emerge for product-minded engineers:

• Influence from day one: “In a small company, you can immediately have a big say.”
• Predictable time: Weekly updates instead of sprint-end theatrics and weekend work.
• UX at the core: A full-time UX role in a four-person product team is a statement.
• Sensible modern stack: React, React Native, Core (as an Express successor), MongoDB, Docker, Elasticsearch—modern, common, and learnable.
• Learning over pedigree: Motivation and curiosity trump a perfect stack match.
• Freedom to experiment: Not every idea must ship to be valuable.
• Rural lifestyle advantage: Countryside location with affordable, larger housing and scenic views.

Who will thrive here? Product builders who prefer steady impact over big-bang project finales. Pragmatists who enjoy modern tech but value stability, community, and team fit over hype. And anyone who appreciates focused work in a calm setting.

Leadership through clarity: Principles behind the practice

The approach Thomas Grömer describes rests on straightforward leadership principles:

• Product responsibility over project delivery
• Cadence over deadline drama
• User focus with real UX capability in the team
• Technology choices guided by product maturity, community, packages, and hiring
• Continuous prioritisation by customer value
• Culture of learning and team fit over CV checklists

These principles aren’t flashy, but their consistency is rare—especially in a small team at a rural location. That combination is exactly what makes easyWerkstatt attractive.

What stood out to us at DevJobs.at

From “Thomas Grömer, Founder von easyWerkstatt,” one impression stands above the rest: this team wants to build a good product for the long haul—and shapes its organisation so that this is actually possible. The cornerstones are clear:

• Weekly releases instead of heroic late nights
• A small team with a strong UX function
• Technology choices that prioritise the product and the people building it
• Hiring that emphasises team fit and the will to learn
• A location that treats quality of life as a real advantage

That’s exactly what easyWerkstatt does—technically, organisationally, and culturally.

Closing thoughts: A home for product-minded engineers who want ownership

easyWerkstatt shows how small product teams can have outsized impact: regular, tested releases; a modern yet pragmatic stack; discussions that genuinely set direction; and a hiring approach that seeks people eager to learn and collaborate. If this working mode resonates with you, take the opportunity to speak with the team—and use the half-day onsite to experience the culture firsthand. In our view, this is a setup where talent can compound—without the usual project theatrics, and with real ownership.