{"id":68347,"date":"2024-12-12T12:15:18","date_gmt":"2024-12-12T06:45:18","guid":{"rendered":"https:\/\/www.guvi.in\/blog\/?p=68347"},"modified":"2026-03-18T10:17:01","modified_gmt":"2026-03-18T04:47:01","slug":"golang-interview-questions-and-answers","status":"publish","type":"post","link":"https:\/\/www.guvi.in\/blog\/golang-interview-questions-and-answers\/","title":{"rendered":"Top 40 Golang Interview Questions and Answers"},"content":{"rendered":"\n

Preparing for a Go interview isn\u2019t just about memorizing syntax, it\u2019s about understanding why the language was built the way it was. Interviewers rarely care if you remember every keyword, but they care a lot about whether you understand concurrency, simplicity in design, and writing predictable backend systems.<\/p>\n\n\n\n

So here\u2019s the real question: can you explain how Go handles real-world problems like scale, performance, and reliability, not just how to write a loop?<\/p>\n\n\n\n

This article is structured exactly the way interviews happen. We start from core language basics, move into practical programming concepts, then reach advanced concurrency and real production scenarios. By the end, you won\u2019t just recognize answers, you\u2019ll know how to reason through them.<\/p>\n\n\n\n

Quick Answer:<\/em><\/strong>
Golang interviews focus on core language concepts, problem-solving skills, and how well you use Go\u2019s concurrency model. Be ready to explain goroutines, channels, interfaces, error handling, and how memory management works.<\/p>\n\n\n\n

Beginner Level Golang Interview Questions and Answers (The Basics)<\/strong><\/h2>\n\n\n\n
\"Beginner<\/figure>\n\n\n\n

This section checks whether you actually understand the language or just copied syntax from tutorials. Interviewers use these questions to see if you know how Go thinks, packages, types, functions, and basic data handling. If you can explain these clearly, you prove you won\u2019t struggle with everyday coding tasks in a Go codebase.<\/p>\n\n\n\n

1. What is the <\/strong>Go programming language, and what makes it unique?<\/strong><\/h3>\n\n\n\n

Go (or Golang)<\/a> is a general-purpose programming language that Google developed. The language stands out because it emphasizes simplicity and efficiency. Here’s what makes Go special:<\/p>\n\n\n\n

The language delivers high performance and handles parallel tasks efficiently. Go provides built-in support for concurrent programming with a simple, concise syntax. You’ll find static typing with garbage collection that makes development smoother.<\/p>\n\n\n\n

2. What are the key features of Go?<\/strong><\/h3>\n\n\n\n

Go combines performance with simplicity. It compiles to machine code like C\/C++<\/a> but avoids complex features that slow development.<\/p>\n\n\n\n

Important features include garbage collection, strong static typing, fast compilation, built-in concurrency using goroutines, and a powerful standard library. These make Go particularly suitable for large scalable backend systems.<\/p>\n\n\n\n

3. What are the basic data types in Go?<\/strong><\/h3>\n\n\n\n

Go comes with several built-in data types:<\/p>\n\n\n\n

Category<\/strong><\/td>Types<\/strong><\/td><\/tr>
Numeric<\/td>int, int8\/16\/32\/64, uint8\/16\/32\/64, float32\/64<\/td><\/tr>
String<\/td>string<\/td><\/tr>
Boolean<\/td>bool<\/td><\/tr>
Complex<\/td>complex64, complex128<\/td><\/tr><\/tbody><\/table>
Basic data types in Go?<\/strong><\/figcaption><\/figure>\n\n\n\n

4. What is a package in Go?<\/strong><\/h3>\n\n\n\n

A package is a collection of related source files grouped together. Every Go program begins execution from the main<\/code> package, which acts as the entry point of the application.<\/p>\n\n\n\n

Packages help organize code into reusable modules and improve maintainability. Go also provides a large set of standard packages such as f<\/code><\/p>\n\n\n\n

package main\nimport \"fmt\"\n\nfunc main() {\n    fmt.Println(\"Hello Go\")\n}\n<\/code><\/pre>\n\n\n\n
A package groups Go source files in the same directory that compiles together. Packages serve multiple purposes. They manage dependencies effectively and organize code logically. Your code becomes reusable, and you get better scope control for variables and functions.<\/p>\n\n\n\n
Master Golang with HCL GUVI\u2019s <\/strong>Golang Course<\/mark><\/strong><\/a>, designed to help you build robust applications and ace Golang interviews! Learn core concepts, real-world applications, and essential tools like Go Modules, Goroutines, and Channels. Get hands-on practice, interview prep, and lifetime access to industry-relevant content. Perfect for aspiring developers!<\/p>\n\n\n\n
5. How are variables declared in Go?<\/strong><\/h3>\n\n\n\n
Variables in Go can be declared in multiple ways depending on context. The language supports explicit typing as well as automatic type inference.<\/p>\n\n\n\n
Inside functions, short declaration syntax is most commonly used because it reduces verbosity and improves readability.<\/p>\n\n\n\n
The compiler automatically determines the type when not specified.<\/p>\n\n\n\n
var age int = 25\nvar name = \"Kiran\"\ncity := \"Chennai\"<\/code><\/pre>\n\n\n\n
6. What are constants in Go?<\/strong><\/h3>\n\n\n\n
Constants represent fixed values that cannot be modified after declaration. They are defined using the const<\/code> keyword and are evaluated at compile time.<\/p>\n\n\n\n
Constants are useful for values like configuration settings or mathematical values that should never change during execution.<\/p>\n\n\n\n
const PI = 3.14<\/code><\/p>\n\n\n\n
Go also supports untyped constants, allowing flexible usage across multiple types.<\/p>\n\n\n\n
7. How does Go implement error handling?<\/strong><\/h3>\n\n\n\n
Go takes a straightforward approach to error handling through explicit error values instead of exceptions. Functions typically return an error as their last value:<\/p>\n\n\n\n
func divide(x, y float64) (float64, error) {\n    if y == 0 {\n        return 0, errors.New(\"division by zero\")\n    }\n    return x\/y, nil\n}<\/code><\/pre>\n\n\n\n
8. What is a function in Go?<\/strong><\/h3>\n\n\n\n
A function is a reusable block of code that performs a specific task. Functions in Go can accept parameters and return values, including multiple return values.<\/p>\n\n\n\n
Multiple return values are commonly used for returning results along with error information, which is a standard Go design practice.<\/p>\n\n\n\n
func add(a int, b int) int {\n    return a + b\n}\n\nfunc swap(a, b int) (int, int) {\n    return b, a\n}\n<\/code><\/pre>\n\n\n\n
9. What is a map in Go?<\/strong><\/h3>\n\n\n\n
A map stores key-value pairs and allows very fast lookup operations. It works similarly to dictionaries in other languages.<\/p>\n\n\n\n
Maps are commonly used in caching, counting frequency, configuration storage, and indexing data efficiently.<\/p>\n\n\n\n
student := map[string]int{\n    \"math\": 90,\n    \"science\": 85,\n}\n<\/code><\/pre>\n\n\n\n
Question 10: <\/strong>What is the significance of the ‘main’ package in Go?<\/strong><\/h3>\n\n\n\n
The main package holds special importance in Go. It defines a standalone executable program and must contain a main() function that serves as the program’s entry point.<\/p>\n\n\n\n
Intermediate Level Golang Interview Questions and Answers<\/strong><\/h2>\n\n\n\n
\"Intermediate<\/figure>\n\n\n\n
Now the focus shifts from writing code to writing maintainable code. Here you\u2019re expected to understand structs, interfaces, pointers, and how Go programs are structured internally. Most candidates fail here because they know what works<\/em> but not why it works<\/em>. This level separates learners from developers who can contribute to real projects.<\/p>\n\n\n\n
11. What is a pointer in Go?<\/strong><\/h3>\n\n\n\n
A pointer stores the memory address of a variable instead of the value itself. It allows functions to modify original data without copying it.<\/p>\n\n\n\n
Go supports pointers but deliberately avoids pointer arithmetic, making memory handling safer compared to C\/C++.<\/p>\n\n\n\n
x := 10\np := &x\nfmt.Println(*p)\n<\/code><\/pre>\n\n\n\n
12. What is a struct in Go?<\/strong><\/h3>\n\n\n\n
A struct is a user-defined data type that groups related fields together. It serves the role of classes in Go but without inheritance.<\/p>\n\n\n\n
Structs are commonly used to model real-world entities like users, orders, or API responses.<\/p>\n\n\n\n
type User struct {\n    Name string\n    Age  int\n}\n<\/code><\/pre>\n\n\n\n
13. What are methods in Go?<\/strong><\/h3>\n\n\n\n
Methods are functions attached to structs, allowing behavior to be defined for custom types. They help implement object-like behavior in Go.<\/p>\n\n\n\n
This approach promotes composition rather than inheritance and keeps the language simple yet powerful.<\/p>\n\n\n\n
func (u User) greet() {\n    fmt.Println(\"Hello\", u.Name)\n}\n<\/code><\/pre>\n\n\n\n
14. What is an interface in Go?<\/strong><\/h3>\n\n\n\n
An interface defines behavior using method signatures. Any type implementing those methods automatically satisfies the interface.<\/p>\n\n\n\n
This implicit implementation removes tight coupling and improves flexibility in program design.<\/p>\n\n\n\n
type Shape interface {\n    Area() float64\n}\n<\/code><\/pre>\n\n\n\n
15. What is a goroutine?<\/strong><\/h3>\n\n\n\n
A goroutine<\/a> is a lightweight thread managed by the Go runtime instead of the operating system. They consume very little memory and can run in thousands simultaneously.<\/p>\n\n\n\n
They are created using the go<\/code> keyword and form the foundation of Go\u2019s concurrency model.<\/p>\n\n\n\n
go sayHello()\n<\/code><\/pre>\n\n\n\n
16. What is a channel in Go?<\/strong><\/h3>\n\n\n\n
Channels allow goroutines to communicate safely by sending and receiving data. Instead of sharing memory directly, goroutines exchange messages.<\/p>\n\n\n\n
This approach reduces bugs like race conditions and simplifies concurrent programming.<\/p>\n\n\n\n
ch := make(chan int)\nch <- 5\nvalue := <-ch\n<\/code><\/pre>\n\n\n\n
17. What is the difference between buffered and unbuffered channels?<\/strong><\/h3>\n\n\n\n
Unbuffered channels require both sender and receiver to be ready at the same time. They synchronize execution between goroutines.<\/p>\n\n\n\n
Buffered channels allow limited messages to be stored without blocking immediately, improving performance in producer-consumer scenarios.<\/p>\n\n\n\n
ch := make(chan int, 2)<\/code><\/p>\n\n\n\n
18. What is defer<\/code> in Go?<\/strong><\/h3>\n\n\n\n
defer<\/code> schedules a function call to run after the surrounding function finishes execution. It is commonly used for cleanup tasks like closing files or releasing locks.<\/p>\n\n\n\n
Deferred calls execute in reverse order of declaration, similar to a stack.<\/p>\n\n\n\n
defer file.Close()<\/code><\/p>\n\n\n\n
19. How does error handling work in Go?<\/strong><\/h3>\n\n\n\n
Go avoids exceptions and instead returns errors explicitly as values. This forces developers to handle failures intentionally and keeps control flow predictable.<\/p>\n\n\n\n
file, err := os.Open(\"test.txt\")\nif err != nil {\n    fmt.Println(err)\n}\n<\/code><\/pre>\n\n\n\n
This design improves reliability in large systems.<\/p>\n\n\n\n
20. What is the init()<\/code> function in Go?<\/strong><\/h3>\n\n\n\n
The init()<\/code> function runs automatically before the main()<\/code> function. It is executed when the package is loaded.<\/p>\n\n\n\n
It is commonly used for initializing configuration, establishing database connections, or preparing dependencies before execution begins.<\/p>\n\n\n\n
func init() { fmt.Println(\"Setup complete\") }<\/code><\/p>\n\n\n\n
Advanced Level Golang Interview Questions and Answers<\/strong><\/h2>\n\n\n\n
\"Advanced<\/figure>\n\n\n\n
At this point the interview is about engineering decisions, not syntax. Topics like concurrency control, memory behavior, synchronization, and performance start appearing. The goal is to check whether you can build reliable systems that won\u2019t break under pressure, the real reason companies choose Go in the first place.<\/p>\n\n\n\n
21. What is the difference between concurrency and parallelism in Go?<\/strong><\/h3>\n\n\n\n
Concurrency means multiple tasks are in progress at the same time, but not necessarily executing simultaneously. Go achieves this using goroutines and the scheduler which switches execution between them efficiently.<\/p>\n\n\n\n
Parallelism means tasks actually run simultaneously on multiple CPU cores. In Go, this depends on GOMAXPROCS<\/code> and available cores. So Go guarantees concurrency, and enables parallelism when hardware allows.<\/p>\n\n\n\n
22. What is a race condition and how does Go prevent it?<\/strong><\/h3>\n\n\n\n
A race condition occurs when multiple goroutines access and modify shared data at the same time, leading to unpredictable results. This usually happens when synchronization is missing.<\/p>\n\n\n\n
Go prevents this using channels and synchronization primitives like mutex. Additionally, Go provides a race detector:<\/p>\n\n\n\n
go run -race main.go<\/code><\/p>\n\n\n\n
This helps identify unsafe memory access during development.<\/p>\n\n\n\n
23. What is a mutex in Go?<\/strong><\/h3>\n\n\n\n
A mutex (mutual exclusion lock) ensures only one goroutine accesses a shared resource at a time. It prevents data corruption in concurrent programs.<\/p>\n\n\n\n
import \"sync\"\n\nvar mu sync.Mutex\nvar count int\n\nfunc increment() {\n    mu.Lock()\n    count++\n    mu.Unlock()\n}\n<\/code><\/pre>\n\n\n\n
Mutex is useful when channels are not practical for shared state control.<\/p>\n\n\n\n
24. What is a WaitGroup?<\/strong><\/h3>\n\n\n\n
WaitGroup waits for multiple goroutines to finish execution before continuing. It is commonly used in parallel processing tasks.<\/p>\n\n\n\n
var wg sync.WaitGroup\n\nwg.Add(1)\ngo func() {\n    defer wg.Done()\n    fmt.Println(\"Task done\")\n}()\n\nwg.Wait()\n<\/code><\/pre>\n\n\n\n
Without WaitGroup, the program may exit before goroutines complete.<\/p>\n\n\n\n
25. What is the difference between slice length and capacity?<\/strong><\/h3>\n\n\n\n
Length is the number of elements currently present in the slice. Capacity is the total space allocated in the underlying array.<\/p>\n\n\n\n
s := make([]int, 2, 5)\nfmt.Println(len(s)) \/\/ 2\nfmt.Println(cap(s)) \/\/ 5\n<\/code><\/pre>\n\n\n\n
When capacity is exceeded, Go allocates a new array and copies data.<\/p>\n\n\n\n
26. What are anonymous functions and closures in Go?<\/strong><\/h3>\n\n\n\n
Anonymous functions are functions without a name. Closures are anonymous functions that capture surrounding variables.<\/p>\n\n\n\n
func counter() func() int {\n    i := 0\n    return func() int {\n        i++\n        return i\n    }\n}\n<\/code><\/pre>\n\n\n\n
Closures help maintain state without global variables.<\/p>\n\n\n\n
27. What is the blank identifier (_) in Go?<\/strong><\/h3>\n\n\n\n
The blank identifier ignores values returned by functions. It is useful when certain return values are not needed.<\/p>\n\n\n\n
value, _ := strconv.Atoi(\"10\")<\/code><\/p>\n\n\n\n
It is also used to avoid unused variable compilation errors.<\/p>\n\n\n\n
28. What is type assertion in Go?<\/strong><\/h3>\n\n\n\n
Type assertion extracts the underlying value from an interface.<\/p>\n\n\n\n
var i interface{} = \"hello\"\ns := i.(string)\n<\/code><\/pre>\n\n\n\n
Safe assertion:<\/p>\n\n\n\n
s, ok := i.(string)\n<\/code><\/pre>\n\n\n\n
This prevents runtime panic if type mismatches.<\/p>\n\n\n\n
29. What is the difference between new<\/code> and make<\/code>?<\/strong><\/h3>\n\n\n\n
new<\/code> allocates memory and returns a pointer. It works for any type.<\/p>\n\n\n\n
make<\/code> initializes built-in reference types like slice, map, and channel.<\/p>\n\n\n\n
p := new(int)\ns := make([]int, 5)\nm := make(map[string]int)\n<\/code><\/pre>\n\n\n\n
In short, new<\/code> allocates, make<\/code> initializes.<\/p>\n\n\n\n
30. What is garbage collection in Go?<\/strong><\/h3>\n\n\n\n
Garbage collection automatically frees unused memory so developers don\u2019t manually manage memory like in C\/C++.<\/p>\n\n\n\n
Go uses a concurrent mark-and-sweep collector that runs alongside program execution. This minimizes pause time and improves performance in backend services.<\/p>\n\n\n\n
\ud83d\udca1 Did You Know?<\/strong> 

Go was originally created because Google engineers were tired of waiting for builds to finish. Large C++ projects took so long to compile that developers would literally start a build and go grab coffee. Go\u2019s compiler was intentionally designed to be insanely fast, which is why even huge codebases compile in seconds today. Ironically, one of the language\u2019s biggest selling points in interviews, fast development, exists because engineers were simply impatient.<\/div>\n\n\n\n
Scenario-Based Golang Interview Questions and Answers<\/strong><\/h2>\n\n\n\n
These questions simulate real production problems. Instead of definitions, you\u2019ll be asked how you would design, debug, or stabilize a Go service. Interviewers want to understand your thinking process, how you approach failures, scale applications, and write safe concurrent code. This is where strong candidates stand out.<\/p>\n\n\n\n
31. How would you safely share data between goroutines?<\/strong><\/h3>\n\n\n\n
The safest approach is to use channels because they follow Go\u2019s principle: \u201cDo not communicate by sharing memory; share memory by communicating.\u201d<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
ch := make(chan int)\n\ngo func() {\n    ch <- 10\n}()\n\nvalue := <-ch\n<\/code><\/pre>\n\n\n\n
Channels eliminate the need for manual locking in many cases.<\/p>\n\n\n\n
32. Your API server crashes under heavy traffic. What Go feature helps?<\/strong><\/h3>\n\n\n\n
You should use goroutines and worker pools. Instead of spawning unlimited goroutines, limit concurrency using buffered channels.<\/p>\n\n\n\n
This prevents memory exhaustion and stabilizes performance during high load.<\/p>\n\n\n\n
33. How would you handle a timeout in an API call?<\/strong><\/h3>\n\n\n\n
Use context.WithTimeout<\/code>. It cancels long running operations automatically.<\/p>\n\n\n\n
ctx, cancel := context.WithTimeout(context.Background(), 2*time.Second)\ndefer cancel()\n<\/code><\/pre>\n\n\n\n
This prevents resource leaks and improves system reliability.<\/p>\n\n\n\n
34. How do you avoid memory leaks in Go?<\/strong><\/h3>\n\n\n\n
Memory leaks happen when goroutines never stop or channels remain open. Always close channels and cancel contexts when done.<\/p>\n\n\n\n
Long-running goroutines should listen to a done<\/code> signal to terminate gracefully.<\/p>\n\n\n\n
35. When should you use a mutex instead of channels?<\/strong><\/h3>\n\n\n\n
Use mutex when multiple goroutines frequently update shared state and channels would add unnecessary overhead.<\/p>\n\n\n\n
Channels are better for communication flow, mutex is better for protecting shared memory.<\/p>\n\n\n\n
36. Your program prints inconsistent results during parallel execution. Why?<\/strong><\/h3>\n\n\n\n
This usually indicates a race condition. Multiple goroutines are modifying the same variable simultaneously.<\/p>\n\n\n\n
You must synchronize access using mutex, atomic operations, or channels.<\/p>\n\n\n\n
37. How do you design a worker pool in Go?<\/strong><\/h3>\n\n\n\n
Create a job channel and multiple worker goroutines consuming from it.<\/p>\n\n\n\n
jobs := make(chan int, 10)\n\nfor i := 0; i < 3; i++ {\n    go worker(jobs)\n}\n<\/code><\/pre>\n\n\n\n
This controls concurrency and improves throughput.<\/p>\n\n\n\n
38. How would you gracefully shut down a Go server?<\/strong><\/h3>\n\n\n\n
Use context cancellation and listen for OS signals like SIGINT. Then stop accepting requests and finish ongoing ones.<\/p>\n\n\n\n
This avoids killing active user operations abruptly.<\/p>\n\n\n\n
39. When should you use pointers in structs?<\/strong><\/h3>\n\n\n\n
Use pointers when struct size is large or when changes must reflect across functions. Passing by value copies data and increases memory usage.<\/p>\n\n\n\n
Pointers improve performance and allow mutation.<\/p>\n\n\n\n
40. Your Go service must handle millions of requests. Why is Go suitable?<\/strong><\/h3>\n\n\n\n
Go\u2019s lightweight goroutines, efficient scheduler, and low memory overhead allow massive concurrency. Unlike thread-heavy languages, Go can handle thousands of connections with minimal resources.<\/p>\n\n\n\n
That is why Go powers systems like Kubernetes, Docker, and cloud infrastructure.<\/p>\n\n\n\n
If you\u2019re serious about mastering Golang in full-stack development and want to apply it in real-world scenarios, don\u2019t miss the chance to enroll in HCL GUVI\u2019s IITM Pravartak Certified Online MERN Full Stack Development Course<\/a> with AI Integration. Build full stack skills in MERN with expert guidance, hands-on projects, and career support. Master in-demand tools like Git, MongoDB, Express, React, Node.js, and more!<\/p>\n\n\n\n
Conclusion<\/strong><\/h2>\n\n\n\n
In conclusion, Go interviews reward clarity of thinking more than clever tricks. The strongest candidates are usually the ones who write readable code, understand concurrency trade-offs, and choose the simplest working solution instead of the smartest-looking one.<\/p>\n\n\n\n
If you can comfortably explain slices vs arrays, when to use channels vs mutex, and how Go behaves under load, you\u2019re already ahead of most applicants. At that point, interviews stop feeling like theory exams and start feeling like technical conversations, which is exactly where you want to be.<\/p>\n\n\n\n
Keep revisiting these questions, try small implementations, and most importantly, practice explaining concepts aloud. In Go interviews, explanation ability often matters as much as coding ability.<\/p>\n","protected":false},"excerpt":{"rendered":"
Preparing for a Go interview isn\u2019t just about memorizing syntax, it\u2019s about understanding why the language was built the way it was. Interviewers rarely care if you remember every keyword, but they care a lot about whether you understand concurrency, simplicity in design, and writing predictable backend systems. So here\u2019s the real question: can you […]<\/p>\n","protected":false},"author":22,"featured_media":104104,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[719,294],"tags":[],"views":"19568","authorinfo":{"name":"Lukesh S","url":"https:\/\/www.guvi.in\/blog\/author\/lukesh\/"},"thumbnailURL":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2024\/12\/Top-40-Golang-Interview-Questions-and-Answers-300x116.png","jetpack_featured_media_url":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2024\/12\/Top-40-Golang-Interview-Questions-and-Answers.png","_links":{"self":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/68347"}],"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\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/comments?post=68347"}],"version-history":[{"count":22,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/68347\/revisions"}],"predecessor-version":[{"id":104109,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/68347\/revisions\/104109"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media\/104104"}],"wp:attachment":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media?parent=68347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/categories?post=68347"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/tags?post=68347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}