{"id":137676,"date":"2026-09-10T20:26:19","date_gmt":"2026-09-10T14:56:19","guid":{"rendered":"https:\/\/www.guvi.in\/blog\/?p=137676"},"modified":"2026-09-10T20:26:21","modified_gmt":"2026-09-10T14:56:21","slug":"forward-deployed-engineer-interview-guide","status":"publish","type":"post","link":"https:\/\/www.guvi.in\/blog\/forward-deployed-engineer-interview-guide\/","title":{"rendered":"The Complete Forward Deployed Engineer Interview Guide"},"content":{"rendered":"\n<p>Preparing for a <strong>forward deployed engineer interview<\/strong> requires more than practicing coding questions. FDEs are expected to understand technical problems, build practical solutions, work with customers, and communicate complex ideas clearly. That means your interview may test several skills at once.<\/p>\n\n\n\n<p>Unlike a traditional software engineering interview, you may be given an unclear customer problem and asked how you would approach it. You could also face questions about coding, APIs, cloud infrastructure, system design, debugging, and your previous projects.<\/p>\n\n\n\n<p>So, how should you prepare? The key is to combine strong engineering fundamentals with structured problem-solving and communication skills. This <strong>forward deployed engineer interview guide<\/strong> explains what to expect, which areas to prepare, how to approach customer scenarios, and how to demonstrate the mindset companies look for in successful FDE candidates.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>TL;DR Summary<\/strong><\/h3>\n\n\n\n<ul>\n<li>A <strong>forward deployed engineer interview guide<\/strong> should cover both technical engineering and customer-facing problem-solving.<\/li>\n\n\n\n<li>Expect questions on coding, APIs, databases, cloud, debugging, system design, and software architecture.<\/li>\n\n\n\n<li>You may also face ambiguous business scenarios where you need to clarify requirements before proposing a solution.<\/li>\n\n\n\n<li>Your projects can become a major part of the interview, so understand your technical decisions deeply.<\/li>\n\n\n\n<li>Communication matters because FDEs often explain technical solutions to customers and non-technical stakeholders.<\/li>\n\n\n\n<li>The best preparation combines technical practice, realistic problem-solving, and clear explanations rather than memorizing interview answers.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is a Forward Deployed Engineer Interview Like?<\/strong><\/h2>\n\n\n\n<p><strong>A <\/strong><a href=\"https:\/\/www.guvi.in\/blog\/what-is-a-forward-deployed-engineer\/\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Forward Deployed Engineer<\/strong><\/a><strong> interview usually evaluates your ability to build technical solutions, solve ambiguous problems, and communicate effectively with customers or stakeholders.<\/strong><\/p>\n\n\n\n<p>Unlike a purely coding-focused software engineering interview, an FDE interview can test how you approach a problem from beginning to deployment.<\/p>\n\n\n\n<p>A typical process may include:<\/p>\n\n\n\n<ol>\n<li>Resume or application screening<\/li>\n\n\n\n<li>Technical assessment<\/li>\n\n\n\n<li>Coding interview<\/li>\n\n\n\n<li>System design or architecture discussion<\/li>\n\n\n\n<li>Problem-solving or customer scenario<\/li>\n\n\n\n<li>Behavioral interview<\/li>\n\n\n\n<li>Final interview<\/li>\n<\/ol>\n\n\n\n<p>The exact process varies between companies.<\/p>\n\n\n\n<p>So, don&#8217;t prepare only for coding questions. You need to demonstrate that you can <strong>understand a problem, design a solution, build it, and explain it clearly<\/strong>.<\/p>\n\n\n\n<p>Prepare for emerging AI engineering opportunities with <strong>HCL GUVI&#8217;s <\/strong><a href=\"https:\/\/www.guvi.in\/mlp\/artificial-intelligence-and-machine-learning?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=forward-deployed-engineer-interview-guide\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Artificial Intelligence &amp; Machine Learning Course<\/strong><\/a>. Build practical skills in AI, machine learning, and real-world application development through hands-on projects.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Are Coding Skills Tested?<\/strong><\/h2>\n\n\n\n<p><strong>Coding questions usually evaluate whether you can write correct, readable code and explain your reasoning.<\/strong><\/p>\n\n\n\n<p>You may encounter traditional algorithm questions, but practical coding tasks can also be relevant.<\/p>\n\n\n\n<p>For example:<\/p>\n\n\n\n<p>&#8220;Build a Python service that receives customer data through an API and stores the results in a database.&#8221;<\/p>\n\n\n\n<p>The interviewer may care about more than whether your code works.<\/p>\n\n\n\n<p>They may evaluate:<\/p>\n\n\n\n<ul>\n<li>Code structure<\/li>\n\n\n\n<li>Input validation<\/li>\n\n\n\n<li>Error handling<\/li>\n\n\n\n<li>Testing<\/li>\n\n\n\n<li>Security<\/li>\n\n\n\n<li>Database design<\/li>\n\n\n\n<li>API design<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>How Should You Approach a Coding Problem?<\/strong><\/h3>\n\n\n\n<p>Use a simple process:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code><strong>Understand \u2192 Clarify \u2192 Design \u2192 Code \u2192 Test \u2192 Explain<\/strong><\/code><\/pre>\n\n\n\n<p>Before writing code, make sure you understand the requirements.<\/p>\n\n\n\n<p>If something is unclear, ask questions.<\/p>\n\n\n\n<p>That&#8217;s particularly important for FDE interviews because real customer requirements are rarely perfectly defined.<\/p>\n\n\n\n<div style=\"background-color: #099f4e; border: 3px solid #110053; border-radius: 12px; padding: 18px 22px; color: #FFFFFF; font-size: 18px; font-family: Montserrat, Helvetica, sans-serif; line-height: 1.6; box-shadow: 0 4px 12px rgba(0, 0, 0, 0.15); max-width: 750px;\"> \n  <strong style=\"font-size: 22px; color: #FFFFFF;\">\ud83d\udca1 Did You Know?<\/strong> \n  <br \/><br \/> \n  FDE interviews can vary significantly between companies because the role itself can range from software-heavy implementation to AI integration and customer-focused solution engineering.\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What System Design Questions Can Appear?<\/strong><\/h2>\n\n\n\n<p><strong>System design questions test whether you can break a complex problem into practical components.<\/strong><\/p>\n\n\n\n<p>For example:<\/p>\n\n\n\n<p>&#8220;Design a system that allows a company to upload documents and ask questions about them.&#8221;<\/p>\n\n\n\n<p>You might discuss:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code><strong>User \u2192 API \u2192 Document Processing \u2192 Storage \u2192 Retrieval \u2192 AI Model \u2192 Response<\/strong><\/code><\/pre>\n\n\n\n<p>Then explain:<\/p>\n\n\n\n<ul>\n<li>Why you selected each component<\/li>\n\n\n\n<li>How data flows through the system<\/li>\n\n\n\n<li>How authentication works<\/li>\n\n\n\n<li>How failures are handled<\/li>\n\n\n\n<li>How the system could scale<\/li>\n\n\n\n<li>How you would monitor it<\/li>\n<\/ul>\n\n\n\n<p>You don&#8217;t need to design the most complicated architecture.<\/p>\n\n\n\n<p><strong>The goal is to show structured technical reasoning.<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-pullquote\"><blockquote><p><strong>Best Practice: <\/strong>During system design interviews, don&#8217;t immediately start drawing architecture. First ask questions about users, scale, data, requirements, constraints, and expected outcomes.<\/p><\/blockquote><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Are Customer Problem-Solving Skills Tested?<\/strong><\/h2>\n\n\n\n<p><strong>FDE interviews often test whether you can turn an unclear business problem into a clear technical plan.<\/strong><\/p>\n\n\n\n<p>Consider this scenario:<\/p>\n\n\n\n<p>&#8220;A customer says their employees spend too much time processing invoices. What would you build?&#8221;<\/p>\n\n\n\n<p>Don&#8217;t immediately answer, &#8220;I&#8217;ll build an AI application.&#8221;<\/p>\n\n\n\n<p>Start with questions.<\/p>\n\n\n\n<p>You might ask:<\/p>\n\n\n\n<ul>\n<li>How are invoices currently processed?<\/li>\n\n\n\n<li>How many invoices are handled each month?<\/li>\n\n\n\n<li>What systems are involved?<\/li>\n\n\n\n<li>Which step takes the most time?<\/li>\n\n\n\n<li>What errors occur?<\/li>\n\n\n\n<li>What security requirements exist?<\/li>\n\n\n\n<li>What would success look like?<\/li>\n<\/ul>\n\n\n\n<p>Only after understanding the problem should you recommend a solution.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What Is the Interviewer Looking For?<\/strong><\/h3>\n\n\n\n<p>They may be evaluating whether you can:<\/p>\n\n\n\n<ul>\n<li>Ask useful questions<\/li>\n\n\n\n<li>Identify constraints<\/li>\n\n\n\n<li>Break down ambiguity<\/li>\n\n\n\n<li>Prioritize requirements<\/li>\n\n\n\n<li>Explain trade-offs<\/li>\n\n\n\n<li>Recommend a practical solution<\/li>\n<\/ul>\n\n\n\n<p>This is one of the biggest differences between preparing for an FDE interview and preparing only for a traditional coding interview.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Questions Can Interviewers Ask About Your Projects?<\/strong><\/h2>\n\n\n\n<p><strong>Expect interviewers to explore your projects deeply, especially if you have limited professional experience.<\/strong><\/p>\n\n\n\n<p>Don&#8217;t assume your project section is just something recruiters glance at.<\/p>\n\n\n\n<p>You could be asked:<\/p>\n\n\n\n<ul>\n<li>Why did you build this project?<\/li>\n\n\n\n<li>Why did you choose this technology?<\/li>\n\n\n\n<li>Why did you use this database?<\/li>\n\n\n\n<li>How does the architecture work?<\/li>\n\n\n\n<li>What was the hardest problem?<\/li>\n\n\n\n<li>What would you change?<\/li>\n\n\n\n<li>How did you test it?<\/li>\n\n\n\n<li>How did you deploy it?<\/li>\n\n\n\n<li>What happens if traffic increases?<\/li>\n\n\n\n<li>What security issues did you consider?<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Example<\/strong><\/h3>\n\n\n\n<p>Suppose your resume says:<\/p>\n\n\n\n<p>Built a Python API for an AI application.<\/p>\n\n\n\n<p>Be ready to explain:<\/p>\n\n\n\n<p><strong>Why Python?<\/strong><\/p>\n\n\n\n<p><strong>Why that API framework?<\/strong><\/p>\n\n\n\n<p><strong>How did the application communicate with the AI model?<\/strong><\/p>\n\n\n\n<p><strong>How did you handle failures?<\/strong><\/p>\n\n\n\n<p><strong>Where was it deployed?<\/strong><\/p>\n\n\n\n<p><strong>How did you evaluate the results?<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-pullquote\"><blockquote><p><strong>Pro Tip: <\/strong>Before an interview, pick your two strongest projects and practice explaining each one in three versions: <strong>30 seconds, 2 minutes, and 5 minutes<\/strong>.<\/p><\/blockquote><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Should You Prepare for the Interview?<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1200\" height=\"630\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/09\/image-301-1200x630.png\" alt=\"How Should You Prepare for the Interview?\" class=\"wp-image-137679\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/09\/image-301-1200x630.png 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/09\/image-301-300x158.png 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/09\/image-301-768x403.png 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/09\/image-301-1536x807.png 1536w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/09\/image-301-150x79.png 150w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/09\/image-301.png 1731w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<p><strong>Prepare across four areas: coding, engineering fundamentals, real-world problem-solving, and communication.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Week 1: Strengthen Fundamentals<\/strong><\/h3>\n\n\n\n<p>Review:<\/p>\n\n\n\n<ul>\n<li><a href=\"https:\/\/www.guvi.in\/hub\/python\/\" target=\"_blank\" rel=\"noreferrer noopener\">Python<\/a> or your primary language<\/li>\n\n\n\n<li>Data structures<\/li>\n\n\n\n<li>Algorithms<\/li>\n\n\n\n<li>SQL<\/li>\n\n\n\n<li>APIs<\/li>\n\n\n\n<li>Git<\/li>\n\n\n\n<li>Debugging<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Week 2: Practice Building Systems<\/strong><\/h3>\n\n\n\n<p>Work on:<\/p>\n\n\n\n<ul>\n<li>REST APIs<\/li>\n\n\n\n<li><a href=\"https:\/\/www.ibm.com\/think\/topics\/data-integration\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Database integration<\/a><\/li>\n\n\n\n<li>Authentication<\/li>\n\n\n\n<li><a href=\"https:\/\/www.guvi.in\/blog\/what-is-docker-in-devops\/\" target=\"_blank\" rel=\"noreferrer noopener\">Docker<\/a><\/li>\n\n\n\n<li>Cloud deployment<\/li>\n\n\n\n<li>Basic system design<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Week 3: Practice FDE Scenarios<\/strong><\/h3>\n\n\n\n<p>Take ambiguous business problems and practice turning them into technical solutions.<\/p>\n\n\n\n<p>For each scenario:<\/p>\n\n\n\n<ol>\n<li>Clarify the problem.<\/li>\n\n\n\n<li>Identify requirements.<\/li>\n\n\n\n<li>Ask about constraints.<\/li>\n\n\n\n<li>Propose a solution.<\/li>\n\n\n\n<li>Explain trade-offs.<\/li>\n\n\n\n<li>Discuss deployment.<\/li>\n\n\n\n<li>Define how success would be measured.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Week 4: Mock Interviews<\/strong><\/h3>\n\n\n\n<p>Practice explaining your projects and solving problems out loud.<\/p>\n\n\n\n<p>Ask a friend or mentor to challenge your assumptions.<\/p>\n\n\n\n<p>You can also record yourself answering questions and identify areas where your explanations become unclear.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Should You Answer Behavioral Questions?<\/strong><\/h2>\n\n\n\n<p><strong>Use real examples and focus on what you personally did.<\/strong><\/p>\n\n\n\n<p>Common questions include:<\/p>\n\n\n\n<ul>\n<li>Tell me about a difficult technical problem.<\/li>\n\n\n\n<li>Describe a time you worked with a difficult stakeholder.<\/li>\n\n\n\n<li>Tell me about a project that failed.<\/li>\n\n\n\n<li>How do you handle changing requirements?<\/li>\n\n\n\n<li>Describe a time you had to learn something quickly.<\/li>\n\n\n\n<li>How do you prioritize competing requests?<\/li>\n<\/ul>\n\n\n\n<p>A simple structure is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code><strong>Situation \u2192 Problem \u2192 Action \u2192 Result \u2192 Lesson<\/strong><\/code><\/pre>\n\n\n\n<p>Don&#8217;t spend most of your answer describing the situation.<\/p>\n\n\n\n<p>Focus on your actions and what you learned.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Questions Should You Ask the Interviewer?<\/strong><\/h2>\n\n\n\n<p><strong>Ask questions that help you understand the actual FDE role and how engineers work with customers.<\/strong><\/p>\n\n\n\n<p>Useful questions include:<\/p>\n\n\n\n<ul>\n<li>How much of the role involves software development?<\/li>\n\n\n\n<li>How are customer requirements translated into engineering work?<\/li>\n\n\n\n<li>What technologies do FDEs use most frequently?<\/li>\n\n\n\n<li>How long does a typical customer engagement last?<\/li>\n\n\n\n<li>How is FDE performance measured?<\/li>\n\n\n\n<li>What does success look like in the first six months?<\/li>\n\n\n\n<li>How much travel or customer interaction is expected?<\/li>\n<\/ul>\n\n\n\n<p>These questions also help you determine whether the role matches what you&#8217;re looking for.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Start Your Learning Journey with GUVI<\/strong><\/h2>\n\n\n\n<p>Prepare for emerging AI engineering opportunities with <strong>HCL GUVI&#8217;s <\/strong><a href=\"https:\/\/www.guvi.in\/mlp\/artificial-intelligence-and-machine-learning?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=forward-deployed-engineer-interview-guide\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Artificial Intelligence &amp; Machine Learning Course<\/strong><\/a>. Build practical skills in AI, machine learning, and real-world application development through hands-on projects.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>A successful FDE interview requires more than strong coding ability. You need to demonstrate that you can understand an unclear problem, ask the right questions, design a practical solution, and communicate your decisions clearly.<\/p>\n\n\n\n<p>Use this <strong>forward deployed engineer interview guide<\/strong> as a preparation framework rather than a list of answers to memorize. Strengthen your programming and engineering fundamentals, practice system design, and prepare realistic customer scenarios. Most importantly, know the projects on your resume inside out.<\/p>\n\n\n\n<p>The best preparation is to practice thinking like an FDE: <strong>understand the problem first, build only what is needed, explain your trade-offs, and stay focused on the outcome.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>FAQs<\/strong><\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1788778524574\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>What is included in a Forward Deployed Engineer interview?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>FDE interviews can include coding, technical fundamentals, system design, debugging, customer problem-solving, behavioral questions, and discussions about previous projects.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1788778529359\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>Is coding required for a Forward Deployed Engineer interview?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>For engineering-focused FDE roles, coding ability is generally important. The exact depth depends on the company&#8217;s role requirements.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1788778564956\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>What system design questions are asked in FDE interviews?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Questions may involve designing APIs, AI applications, data platforms, integrations, or customer-specific systems. Interviewers usually evaluate your reasoning and trade-offs.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1788778574360\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>How should I prepare for an FDE interview?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Practice coding, APIs, SQL, cloud fundamentals, system design, debugging, customer scenarios, and project explanations. Research the specific job description as well.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1788778582861\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>What makes FDE interviews different from software engineering interviews?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>FDE interviews can place greater emphasis on customer requirements, ambiguity, communication, system integration, and practical solution design alongside traditional engineering skills.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1788778591990\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>What should I ask at the end of an FDE interview?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Ask about the technical responsibilities, customer interaction, typical projects, technologies used, performance expectations, travel requirements, and what success looks like in the role.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Preparing for a forward deployed engineer interview requires more than practicing coding questions. FDEs are expected to understand technical problems, build practical solutions, work with customers, and communicate complex ideas clearly. That means your interview may test several skills at once. Unlike a traditional software engineering interview, you may be given an unclear customer problem [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":137680,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1043],"tags":[],"views":"111","authorinfo":{"name":"HCL GUVI","url":"https:\/\/www.guvi.in\/blog\/author\/guvipr\/"},"thumbnailURL":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/09\/The-Complete-Forward-Deployed-Engineer-Interview-Guide-300x116.webp","_links":{"self":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/137676"}],"collection":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/comments?post=137676"}],"version-history":[{"count":2,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/137676\/revisions"}],"predecessor-version":[{"id":138525,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/137676\/revisions\/138525"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media\/137680"}],"wp:attachment":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media?parent=137676"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/categories?post=137676"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/tags?post=137676"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}