{"id":1828,"date":"2026-08-14T10:51:40","date_gmt":"2026-08-14T10:51:40","guid":{"rendered":"https:\/\/findr-tech.com\/?p=1828"},"modified":"2026-08-14T10:51:40","modified_gmt":"2026-08-14T10:51:40","slug":"when-should-you-hire-a-specialist-vs-a-generalist","status":"publish","type":"post","link":"https:\/\/findr-tech.com\/de\/when-should-you-hire-a-specialist-vs-a-generalist\/","title":{"rendered":"When Should You Hire a Specialist vs a Generalist?"},"content":{"rendered":"

When companies start hiring for a technical role, one of the first questions should be relatively simple: do we need someone who can do several things well, or someone who can do one thing exceptionally well?<\/strong><\/p>\n

In practice, that question isn\u2019t always asked.<\/p>\n

Job descriptions grow as different stakeholders add their requirements. Before long, a company is looking for a software engineer with deep backend expertise who also understands cloud infrastructure, security, architecture, DevOps, data and perhaps AI as well.<\/p>\n

There is nothing wrong with wanting a broad skill set. The problem comes when companies expect specialist-level expertise across every one of those areas.<\/p>\n

It Depends on the Team You\u2019re Building<\/strong><\/p>\n

There is no universal answer to the specialist versus generalist question.<\/p>\n

For a small technology company with five engineers, a strong generalist can be incredibly valuable. They can move between problems, take ownership outside a narrow remit and help wherever the business needs them.<\/p>\n

Hiring six different specialists simply isn\u2019t realistic, and probably isn\u2019t necessary.<\/p>\n

As organisations grow, that equation changes.<\/p>\n

A larger engineering organisation may already have people covering the broader technical landscape. At that point, adding someone with genuinely deep expertise in cybersecurity, platform engineering, machine learning or another specialist area can solve problems that generalist knowledge cannot.<\/p>\n

The right profile depends heavily on the maturity of the team and the problem you\u2019re actually trying to solve.<\/strong><\/p>\n

The Problem With Hiring \u201cUnicorns\u201d<\/strong><\/p>\n

The difficulty comes when the two profiles get confused.<\/p>\n

I\u2019ve seen plenty of searches where the requirements effectively describe four different people.<\/p>\n

The company wants breadth because it needs someone adaptable, but it also expects ten years of specialist-level experience in several different technologies.<\/p>\n

Unsurprisingly, the candidate pool becomes extremely small.<\/p>\n

Even when somebody appears to tick every box on their CV, there is usually a difference between having worked with something and having genuine depth in it.<\/p>\n

That\u2019s why prioritisation matters.<\/p>\n

If cybersecurity is the problem keeping the CTO awake at night, perhaps deep security expertise matters more than finding somebody who can also cover infrastructure and backend development.<\/p>\n

If the challenge is that a small engineering team needs somebody capable of taking ownership wherever problems arise, a broader engineer may provide considerably more value than a narrow specialist.<\/p>\n

Start With the Problem, Not the Profile<\/strong><\/p>\n

Before writing the job description, it is worth asking what you actually need this person to achieve.<\/p>\n

What problem should they solve in their first six months?<\/p>\n

What expertise already exists within the team?<\/p>\n

Where are the genuine gaps?<\/p>\n

And which requirements could somebody reasonably learn after joining?<\/p>\n

Those questions usually tell you far more about the person you need than an increasingly long list of technologies.<\/p>\n

Specialists and generalists both have enormous value. The mistake isn\u2019t choosing one over the other. It\u2019s hiring one when you actually needed the other.<\/strong><\/p>\n

 <\/p>","protected":false},"excerpt":{"rendered":"

When companies start hiring for a technical role, one of the first questions should be relatively simple: do we need someone who can do several things well, or someone who can do one thing exceptionally well? In practice, that question isn\u2019t always asked. Job descriptions grow as different stakeholders add their requirements. Before long, a company is looking for a software engineer with deep backend expertise who also understands cloud infrastructure, security, architecture, DevOps, data and perhaps AI as well. There is nothing wrong with wanting a broad skill set. The problem comes when companies expect specialist-level expertise across every one of those areas. It Depends on the Team You\u2019re Building There is no universal answer to the specialist versus generalist question. For a small technology company with five engineers, a strong generalist can be incredibly valuable. They can move between problems, take ownership outside a narrow remit and help wherever the business needs them. Hiring six different specialists simply isn\u2019t realistic, and probably isn\u2019t necessary. As organisations grow, that equation changes. A larger engineering organisation may already have people covering the broader technical landscape. At that point, adding someone with genuinely deep expertise in cybersecurity, platform engineering, machine learning or another specialist area can solve problems that generalist knowledge cannot. The right profile depends heavily on the maturity of the team and the problem you\u2019re actually trying to solve. The Problem With Hiring \u201cUnicorns\u201d The difficulty comes when the two profiles get confused. I\u2019ve seen plenty of searches where the requirements effectively describe four different people. The company wants breadth because it needs someone adaptable, but it also expects ten years of specialist-level experience in several different technologies. Unsurprisingly, the candidate pool becomes extremely small. Even when somebody appears to tick every box on their CV, there is usually a difference between having worked with something and having genuine depth in it. That\u2019s why prioritisation matters. If cybersecurity is the problem keeping the CTO awake at night, perhaps deep security expertise matters more than finding somebody who can also cover infrastructure and backend development. If the challenge is that a small engineering team needs somebody capable of taking ownership wherever problems arise, a broader engineer may provide considerably more value than a narrow specialist. Start With the Problem, Not the Profile Before writing the job description, it is worth asking what you actually need this person to achieve. What problem should they solve in their first six months? What expertise already exists within the team? Where are the genuine gaps? And which requirements could somebody reasonably learn after joining? Those questions usually tell you far more about the person you need than an increasingly long list of technologies. Specialists and generalists both have enormous value. The mistake isn\u2019t choosing one over the other. It\u2019s hiring one when you actually needed the other.  <\/p>","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-1828","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"acf":[],"yoast_head":"\nWhen Should You Hire a Specialist vs a Generalist? - Findr<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/findr-tech.com\/de\/when-should-you-hire-a-specialist-vs-a-generalist\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"When Should You Hire a Specialist vs a Generalist? - Findr\" \/>\n<meta property=\"og:description\" content=\"When companies start hiring for a technical role, one of the first questions should be relatively simple: do we need someone who can do several things well, or someone who can do one thing exceptionally well? In practice, that question isn\u2019t always asked. Job descriptions grow as different stakeholders add their requirements. Before long, a company is looking for a software engineer with deep backend expertise who also understands cloud infrastructure, security, architecture, DevOps, data and perhaps AI as well. There is nothing wrong with wanting a broad skill set. The problem comes when companies expect specialist-level expertise across every one of those areas. It Depends on the Team You\u2019re Building There is no universal answer to the specialist versus generalist question. For a small technology company with five engineers, a strong generalist can be incredibly valuable. They can move between problems, take ownership outside a narrow remit and help wherever the business needs them. Hiring six different specialists simply isn\u2019t realistic, and probably isn\u2019t necessary. As organisations grow, that equation changes. A larger engineering organisation may already have people covering the broader technical landscape. At that point, adding someone with genuinely deep expertise in cybersecurity, platform engineering, machine learning or another specialist area can solve problems that generalist knowledge cannot. The right profile depends heavily on the maturity of the team and the problem you\u2019re actually trying to solve. The Problem With Hiring \u201cUnicorns\u201d The difficulty comes when the two profiles get confused. I\u2019ve seen plenty of searches where the requirements effectively describe four different people. The company wants breadth because it needs someone adaptable, but it also expects ten years of specialist-level experience in several different technologies. Unsurprisingly, the candidate pool becomes extremely small. Even when somebody appears to tick every box on their CV, there is usually a difference between having worked with something and having genuine depth in it. That\u2019s why prioritisation matters. If cybersecurity is the problem keeping the CTO awake at night, perhaps deep security expertise matters more than finding somebody who can also cover infrastructure and backend development. If the challenge is that a small engineering team needs somebody capable of taking ownership wherever problems arise, a broader engineer may provide considerably more value than a narrow specialist. Start With the Problem, Not the Profile Before writing the job description, it is worth asking what you actually need this person to achieve. What problem should they solve in their first six months? What expertise already exists within the team? Where are the genuine gaps? And which requirements could somebody reasonably learn after joining? Those questions usually tell you far more about the person you need than an increasingly long list of technologies. Specialists and generalists both have enormous value. The mistake isn\u2019t choosing one over the other. It\u2019s hiring one when you actually needed the other.  \" \/>\n<meta property=\"og:url\" content=\"https:\/\/findr-tech.com\/de\/when-should-you-hire-a-specialist-vs-a-generalist\/\" \/>\n<meta property=\"og:site_name\" content=\"Findr\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-14T10:51:40+00:00\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Verfasst von\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#\\\/schema\\\/person\\\/a6ac3ffe65bdd72f7dec3109357d992c\"},\"headline\":\"When Should You Hire a Specialist vs a Generalist?\",\"datePublished\":\"2026-08-14T10:51:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/\"},\"wordCount\":492,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#organization\"},\"articleSection\":[\"Uncategorized\"],\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/\",\"url\":\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/\",\"name\":\"When Should You Hire a Specialist vs a Generalist? - Findr\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#website\"},\"datePublished\":\"2026-08-14T10:51:40+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/findr-tech.com\\\/when-should-you-hire-a-specialist-vs-a-generalist\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/findr-tech.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"When Should You Hire a Specialist vs a Generalist?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#website\",\"url\":\"https:\\\/\\\/findr-tech.com\\\/\",\"name\":\"Findr\",\"description\":\"Cyber Security & AI Talent\",\"publisher\":{\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/findr-tech.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#organization\",\"name\":\"Findr\",\"url\":\"https:\\\/\\\/findr-tech.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/findr-tech.com\\\/wp-content\\\/uploads\\\/2023\\\/08\\\/fav.png\",\"contentUrl\":\"https:\\\/\\\/findr-tech.com\\\/wp-content\\\/uploads\\\/2023\\\/08\\\/fav.png\",\"width\":199,\"height\":212,\"caption\":\"Findr\"},\"image\":{\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/findr-tech.com\\\/#\\\/schema\\\/person\\\/a6ac3ffe65bdd72f7dec3109357d992c\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/375aa53cbdf04b7b48b104a36f3e22a6903215729c36533b1aa604e314c5428d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/375aa53cbdf04b7b48b104a36f3e22a6903215729c36533b1aa604e314c5428d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/375aa53cbdf04b7b48b104a36f3e22a6903215729c36533b1aa604e314c5428d?s=96&d=mm&r=g\",\"caption\":\"admin\"},\"url\":\"https:\\\/\\\/findr-tech.com\\\/de\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"When Should You Hire a Specialist vs a Generalist? - Findr","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/findr-tech.com\/de\/when-should-you-hire-a-specialist-vs-a-generalist\/","og_locale":"de_DE","og_type":"article","og_title":"When Should You Hire a Specialist vs a Generalist? - Findr","og_description":"When companies start hiring for a technical role, one of the first questions should be relatively simple: do we need someone who can do several things well, or someone who can do one thing exceptionally well? In practice, that question isn\u2019t always asked. Job descriptions grow as different stakeholders add their requirements. Before long, a company is looking for a software engineer with deep backend expertise who also understands cloud infrastructure, security, architecture, DevOps, data and perhaps AI as well. There is nothing wrong with wanting a broad skill set. The problem comes when companies expect specialist-level expertise across every one of those areas. It Depends on the Team You\u2019re Building There is no universal answer to the specialist versus generalist question. For a small technology company with five engineers, a strong generalist can be incredibly valuable. They can move between problems, take ownership outside a narrow remit and help wherever the business needs them. Hiring six different specialists simply isn\u2019t realistic, and probably isn\u2019t necessary. As organisations grow, that equation changes. A larger engineering organisation may already have people covering the broader technical landscape. At that point, adding someone with genuinely deep expertise in cybersecurity, platform engineering, machine learning or another specialist area can solve problems that generalist knowledge cannot. The right profile depends heavily on the maturity of the team and the problem you\u2019re actually trying to solve. The Problem With Hiring \u201cUnicorns\u201d The difficulty comes when the two profiles get confused. I\u2019ve seen plenty of searches where the requirements effectively describe four different people. The company wants breadth because it needs someone adaptable, but it also expects ten years of specialist-level experience in several different technologies. Unsurprisingly, the candidate pool becomes extremely small. Even when somebody appears to tick every box on their CV, there is usually a difference between having worked with something and having genuine depth in it. That\u2019s why prioritisation matters. If cybersecurity is the problem keeping the CTO awake at night, perhaps deep security expertise matters more than finding somebody who can also cover infrastructure and backend development. If the challenge is that a small engineering team needs somebody capable of taking ownership wherever problems arise, a broader engineer may provide considerably more value than a narrow specialist. Start With the Problem, Not the Profile Before writing the job description, it is worth asking what you actually need this person to achieve. What problem should they solve in their first six months? What expertise already exists within the team? Where are the genuine gaps? And which requirements could somebody reasonably learn after joining? Those questions usually tell you far more about the person you need than an increasingly long list of technologies. Specialists and generalists both have enormous value. The mistake isn\u2019t choosing one over the other. It\u2019s hiring one when you actually needed the other.  ","og_url":"https:\/\/findr-tech.com\/de\/when-should-you-hire-a-specialist-vs-a-generalist\/","og_site_name":"Findr","article_published_time":"2026-08-14T10:51:40+00:00","author":"admin","twitter_card":"summary_large_image","twitter_misc":{"Verfasst von":"admin"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/#article","isPartOf":{"@id":"https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/"},"author":{"name":"admin","@id":"https:\/\/findr-tech.com\/#\/schema\/person\/a6ac3ffe65bdd72f7dec3109357d992c"},"headline":"When Should You Hire a Specialist vs a Generalist?","datePublished":"2026-08-14T10:51:40+00:00","mainEntityOfPage":{"@id":"https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/"},"wordCount":492,"commentCount":0,"publisher":{"@id":"https:\/\/findr-tech.com\/#organization"},"articleSection":["Uncategorized"],"inLanguage":"de","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/","url":"https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/","name":"When Should You Hire a Specialist vs a Generalist? - Findr","isPartOf":{"@id":"https:\/\/findr-tech.com\/#website"},"datePublished":"2026-08-14T10:51:40+00:00","breadcrumb":{"@id":"https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/findr-tech.com\/when-should-you-hire-a-specialist-vs-a-generalist\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/findr-tech.com\/"},{"@type":"ListItem","position":2,"name":"When Should You Hire a Specialist vs a Generalist?"}]},{"@type":"WebSite","@id":"https:\/\/findr-tech.com\/#website","url":"https:\/\/findr-tech.com\/","name":"Findr","description":"Cyber Security & AI Talent","publisher":{"@id":"https:\/\/findr-tech.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/findr-tech.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/findr-tech.com\/#organization","name":"Findr","url":"https:\/\/findr-tech.com\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/findr-tech.com\/#\/schema\/logo\/image\/","url":"https:\/\/findr-tech.com\/wp-content\/uploads\/2023\/08\/fav.png","contentUrl":"https:\/\/findr-tech.com\/wp-content\/uploads\/2023\/08\/fav.png","width":199,"height":212,"caption":"Findr"},"image":{"@id":"https:\/\/findr-tech.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/findr-tech.com\/#\/schema\/person\/a6ac3ffe65bdd72f7dec3109357d992c","name":"admin","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/secure.gravatar.com\/avatar\/375aa53cbdf04b7b48b104a36f3e22a6903215729c36533b1aa604e314c5428d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/375aa53cbdf04b7b48b104a36f3e22a6903215729c36533b1aa604e314c5428d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/375aa53cbdf04b7b48b104a36f3e22a6903215729c36533b1aa604e314c5428d?s=96&d=mm&r=g","caption":"admin"},"url":"https:\/\/findr-tech.com\/de\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/posts\/1828","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/comments?post=1828"}],"version-history":[{"count":1,"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/posts\/1828\/revisions"}],"predecessor-version":[{"id":1829,"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/posts\/1828\/revisions\/1829"}],"wp:attachment":[{"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/media?parent=1828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/categories?post=1828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/findr-tech.com\/de\/wp-json\/wp\/v2\/tags?post=1828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}