--- title: "You get what you hire" url: https://daily.dev/posts/you-get-what-you-hire-vpbpyvocv source_url: https://swizec.com/blog/you-get-what-you-hire type: article source: "swizec.com" published: 2026-06-23T16:42:42.993Z updated: 2026-06-23T16:43:14.873Z tags: ["leadership", "company-culture"] reading_time: 5 upvotes: 32 comments: 3 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # You get what you hire **[swizec.com](https://daily.dev/sources/swizec)** · 5 min read · 32 upvotes · 3 comments ## Summary Engineers naturally gravitate toward solutions that match their expertise — a backend developer will fix your backend, a frontend developer will fix your frontend. Using two real examples of logistics dashboards built by different engineers, the author illustrates how hiring decisions effectively determine the technical direction of your product. The takeaway: be intentional about who you assign to a problem, because their specialty shapes the outcome as much as the requirements do. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@jeanne** · 3 upvotes > It is strange how it feels like a tautology and at the same time I got the aah moment. > > Great point to keep in mind! Imo this is award material 😉 **@baptistecrouzet** · 0 upvotes > Maybe AI can help to counterbalance some points : your backend engineer have some notions about CSS. With AI, he can at least better understand your front, and even help the team on this side. > > Not something really magic. > > But I agree with the fact that your product will be shaped by the team you hire. --- Tags: [#leadership](https://daily.dev/tags/leadership), [#company-culture](https://daily.dev/tags/company-culture) [View this post on daily.dev](https://daily.dev/posts/you-get-what-you-hire-vpbpyvocv)