{"id":22764,"date":"2026-05-07T11:10:06","date_gmt":"2026-05-07T11:10:06","guid":{"rendered":"https:\/\/engineerbabu.com\/blog\/?p=22764"},"modified":"2026-05-07T12:54:47","modified_gmt":"2026-05-07T12:54:47","slug":"software-outsourcing-risks","status":"publish","type":"post","link":"https:\/\/engineerbabu.com\/blog\/software-outsourcing-risks\/","title":{"rendered":"Software Outsourcing Risks That Kill Products (And How to Actually Avoid Them)"},"content":{"rendered":"<p><a href=\"https:\/\/www.s3corp.com.vn\/insights\/common-reasons-why-some-software-outsourcing-projects-fail\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">50-70% of software outsourcing<\/span><\/a><span style=\"font-weight: 400;\"> engagements that fail do so in the first 60 days. Not because the vendor couldn&#8217;t build. Because nobody stress-tested whether they were building the right thing, for the right architecture, with the right ownership terms.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That number isn&#8217;t from a report. It&#8217;s from 14 years of building software and being brought in to salvage projects that didn&#8217;t make it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The IT Services Outsourcing Market is projected to reach USD 462.10 billion in 2026 and grow at a CAGR of 9.3%, eventually hitting <\/span><a href=\"https:\/\/www.coherentmarketinsights.com\/industry-reports\/it-services-outsourcing-market\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">USD 861.10 billion by 2033<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">More companies are outsourcing more critical software than at any point in history. And the failure rate hasn&#8217;t dropped. It&#8217;s kept pace.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I co-founded <\/span><a href=\"http:\/\/engineerbabu.com\"><span style=\"font-weight: 400;\">EngineerBabu<\/span><\/a><span style=\"font-weight: 400;\">, a CMMI Level 5 product engineering company that has delivered 500+ projects across 20+ countries, including products for 4 unicorn clients and 75 YC-selected startups.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The pattern I&#8217;ve seen in every failed outsourcing engagement isn&#8217;t bad code. It&#8217;s predictable, avoidable decisions made in the first few weeks that compound into disasters six months later. This article is the map of those decisions.<\/span><\/p>\n<h2><b>What Are Software Outsourcing Risks?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Software outsourcing risks are the predictable failure patterns that emerge when a company hires an external team to build, maintain, or scale their technology product.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They span technical execution, communication breakdown, intellectual property exposure, hidden cost escalation, and vendor lock-in.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The risk isn&#8217;t outsourcing itself. The risk is outsourcing without a framework.<\/span><\/p>\n<h2><b>The 9 Software Outsourcing Risks I&#8217;ve Seen Destroy Products<\/b><\/h2>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Misaligned Discovery: You&#8217;re Solving the Wrong Problem<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Most failed outsourcing engagements don&#8217;t collapse at the code level. They collapse in the first two weeks.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The vendor runs a quick requirements session. The client sends a 30-page spec. The vendor nods, sends back a proposal, and the engagement begins. Nobody has stress-tested whether the spec actually solves the business problem.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When the EngineerBabu team built LoanOS, a 7-module lending platform covering origination, underwriting, servicing, collections, and regulatory compliance, the first 3 weeks were entirely discovery.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">No code. Just architecture decisions, user journey mapping, and assumption stress-testing. The client pushed back on the timeline. We held firm. That platform went live on time, handles 40,000+ loan applications monthly, and required zero major re-architecture.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Bad vendors rush discovery. Good ones treat it as the highest-risk phase of the engagement.<\/span><\/p>\n<p><b>Red flag:<\/b><span style=\"font-weight: 400;\"> A vendor who can scope your project in under 3 days of conversation.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Vendor Lock-in: When You Don&#8217;t Own Your Own Product<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">This one is rarer now than it was in 2018, but it&#8217;s made a quiet comeback through proprietary frameworks and cloud-native dependency mismanagement.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I&#8217;ve reviewed codebases where the entire architecture was built on a single vendor&#8217;s proprietary ORM layer. Switching would require a full rewrite. I&#8217;ve seen <\/span><a href=\"https:\/\/engineerbabu.com\/services\/mobile-app-development\"><span style=\"font-weight: 400;\">mobile apps<\/span><\/a><span style=\"font-weight: 400;\"> built with internal boilerplate frameworks that the agency owned the license to.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I&#8217;ve audited backends where all infrastructure was managed through a vendor&#8217;s internal DevOps tooling with no handoff documentation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In each case, the client was effectively renting their own product.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Before signing any outsourcing contract, verify three things: who owns the IP, who has access to all repository credentials, and whether the codebase can be handed to a different team on day 90 without the original vendor&#8217;s involvement. If any of these have caveats, renegotiate before you start.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Communication Overhead Eating Delivery Capacity<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The most underestimated outsourcing risk isn&#8217;t technical. It&#8217;s timezone-driven communication collapse.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A 12-hour timezone gap means one round of feedback per day. If you&#8217;re managing a sprint with 3 unclear requirements, that&#8217;s 3 days of drift before alignment. Over a 6-month project, this accumulates into a 4-8 week delay minimum.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I&#8217;ve spoken to CTOs who underestimate this by 3-4x. They think daily standups fix it. They don&#8217;t. Asynchronous decision-making needs to be embedded into the process architecture itself, not bolted on through more meetings.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The best distributed teams I&#8217;ve seen operate on a principle I call &#8220;decision-ready documentation.&#8221; Every requirement is written to a level of detail where a developer in a different timezone can proceed without asking a question. Ambiguity is resolved before the sprint starts, not during it.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Scope Creep Without Governance: The Silent Budget Killer<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Scope creep is the most statistically consistent risk in software outsourcing.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The mechanism is always the same. Client asks for &#8220;a small change.&#8221; Vendor says yes. No change order. No timeline impact documented. Multiply this by 40 iterations over 6 months and you&#8217;ve added 30% to the project scope with 0% additional budget negotiated.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Governance isn&#8217;t bureaucracy. It&#8217;s the thing that keeps projects from silently doubling in cost.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Every change request, regardless of size, should generate a written impact assessment. Not a long one. Three lines: what changes, how long it takes, what it delays. If a vendor resists this, that&#8217;s your signal.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Code Quality and Technical Debt: The Hidden Tax on Every Future Sprint<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">I recently did a code review for a <\/span><a href=\"https:\/\/engineerbabu.com\/industries\/fintech\/app-development-company\"><span style=\"font-weight: 400;\">fintech app development<\/span><\/a><span style=\"font-weight: 400;\"> that had been outsourced for\u00a0 development for 18 months. The product worked. Users were transacting. Revenue was growing. And then they hired a CTO.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">He came back with a report: 68% test coverage gap, 14 critical security vulnerabilities, and an architecture that would require a full refactor before they could scale to their Series A roadmap. The estimate to fix the accumulated technical debt: $320,000 and 7 months.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They had been paying for velocity. What they were actually buying was a mortgage on future engineering capacity.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Require code reviews to be built into the contract. Mandate test coverage thresholds (I use 70% as a floor for production-bound code). Ask to see CI\/CD pipeline setup before the first sprint begins. If a vendor can&#8217;t show you their engineering standards documentation, they don&#8217;t have any.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Security and Compliance Gaps in Regulated Industries<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">This risk is category-specific but devastating when it hits.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In fintech, healthtech, or any product handling PII, building without compliance architecture is not a shortcut. It&#8217;s a deferred liability. I&#8217;ve seen products built without proper KYC\/AML integration, data residency controls, or encryption-at-rest standards that had to be torn down and rebuilt before a single enterprise client would sign.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When the EngineerBabu team built EarlySalary&#8217;s lending stack, now processing over \u20b910,000 crore in disbursements, the compliance architecture was designed in week one alongside the technical architecture. Credit bureau integrations, regulatory reporting, data residency for RBI compliance: these weren&#8217;t features added later. They were foundational decisions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Regulated industry outsourcing without a vendor who has shipped in that regulatory environment before isn&#8217;t outsourcing. It&#8217;s experimenting with your compliance exposure.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Team Continuity: When Your Lead Developer Disappears<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Agencies staff up on wins. They staff down when new logos come in.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">You start an engagement with a senior architect and two experienced developers. By month 4, the architect has rolled off to a new client, and your project is being managed by two developers who joined the company 6 months ago. No knowledge transfer. The codebase familiarity walks out the door with the original team.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I require contracts to include a named-resource clause for any engagement over $150,000. The clause specifies that any key personnel change requires 30 days written notice and a documented knowledge transfer period. Most vendors push back. That pushback tells you exactly how they staff their projects.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Post-Launch Support: The Orphaned Product Problem<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The product ships. The vendor celebrates. You go live.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Three weeks later, a bug emerges in production. The vendor responds in 48 hours. The SLA says 72 hours. It&#8217;s technically compliant. Your users are churning.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Post-launch support is one of the most under-negotiated elements of outsourcing contracts. Most contracts specify response time. Very few specify resolution time, escalation paths, or the technical depth of the support team.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For any product launch, I negotiate post-launch retainer terms before the build contract is signed. Not after. After, you have zero leverage.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Offshore vs. Nearshore vs. Onshore: Choosing on Price Alone<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The assumption that the cheapest option is the most cost-effective is the mistake I see most often from first-time outsourcers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Offshore at $15\/hour with 3x the communication overhead, 2x the revision cycles, and post-launch technical debt that requires $200,000 to resolve is not cheaper than nearshore at $50\/hour that delivers clean code, on time.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Total cost of engagement is not the same as rate per hour.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I&#8217;m not arguing against offshore development. The EngineerBabu team operates across India and delivers globally competitive quality. What I&#8217;m arguing against is optimizing for the wrong number.<\/span><\/p>\n<h2><b>How to Evaluate a Software Outsourcing Vendor: A Framework<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Before signing, score your vendor on these criteria:<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Evaluation Criteria<\/b><\/td>\n<td><b>What Good Looks Like<\/b><\/td>\n<td><b>Red Flag<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Discovery process<\/span><\/td>\n<td><span style=\"font-weight: 400;\">2-4 week structured discovery phase<\/span><\/td>\n<td><span style=\"font-weight: 400;\">&#8220;We can scope it in 2 days&#8221;<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">IP ownership terms<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Clean IP assignment to client on signing<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Vague &#8220;joint ownership&#8221; language<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Engineering standards<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Documented code review, CI\/CD, test coverage policy<\/span><\/td>\n<td><span style=\"font-weight: 400;\">No standards documentation<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Team continuity<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Named resource clause available<\/span><\/td>\n<td><span style=\"font-weight: 400;\">&#8220;We&#8217;ll staff the best available team&#8221;<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Regulatory experience<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Cases in your industry vertical<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Generic tech portfolio only<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Post-launch SLA<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Resolution time specified, not just response time<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Only response time in contract<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Communication architecture<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Async-first process with async decision documentation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">&#8220;We&#8217;ll do daily standups&#8221;<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><\/h2>\n<h2><b><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-22767\" src=\"https:\/\/engineerbabu.com\/blog\/wp-content\/uploads\/2026\/05\/diagram-1-process-flow.png\" alt=\"\" width=\"1360\" height=\"1060\" title=\"\">What Most People Get Wrong About Software Outsourcing Risks<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The popular advice is: check references, look at portfolios, run a paid trial sprint.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">All of that is correct. None of it is sufficient. The real signal is how a vendor behaves before money changes hands.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Do they push back on your spec? A vendor who tells you your requirements are incomplete before signing is worth 10x more than one who tells you what you want to hear. Do they bring up risks you haven&#8217;t raised?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The EarlySalary team I worked with flagged three regulatory edge cases in discovery that hadn&#8217;t appeared in any requirements document. Those flags saved 4 months of rework.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The vendors most likely to deliver are the ones who make the engagement harder to start. They ask uncomfortable questions. They scope things you didn&#8217;t ask them to scope. They tell you the timeline you want isn&#8217;t realistic.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">After reviewing hundreds of vendor proposals across 14 years and 500+ projects: the vendor who tells you &#8220;yes, 3 months, here&#8217;s the quote&#8221; on a project that should take 6 is not optimistic. They&#8217;re either naive or they&#8217;re selling.<\/span><\/p>\n<h2><b>Real Numbers: What Software Outsourcing Actually Costs to Fix When It Goes Wrong<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">These are from actual recovery engagements I&#8217;ve been brought into, not industry estimates:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Complete codebase refactor after failed outsourcing engagement: $180,000 to $400,000<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Technical debt remediation before Series A due diligence: $80,000 to $320,000<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Security vulnerability remediation after fintech product launch: $60,000 to $150,000<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Timeline delay cost (average across 40+ recovery projects): 7 to 14 months of additional runway consumed<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The math on getting outsourcing right the first time is not close.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-22768\" src=\"https:\/\/engineerbabu.com\/blog\/wp-content\/uploads\/2026\/05\/diagram-5-cost-chart.png\" alt=\"\" width=\"1360\" height=\"800\" title=\"\"><\/p>\n<h2><b>The Most Honest Thing I Can Tell You About Outsourcing Risk<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The risk is not the vendor you hire. The risk is the information asymmetry between you and the vendor in the first 30 days of an engagement.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The vendors who manage risk well close that asymmetry fast. They surface problems before they&#8217;re problems. They build governance into the process. They push back when the brief is incomplete.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Every project failure I&#8217;ve audited in 14 years had warning signs in the first month. Not always visible to the client. Almost always visible to anyone who knew what to look for.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you&#8217;re evaluating a software development engagement and want to talk through the architecture decisions, vendor evaluation criteria, or risk profile of your specific project before you commit, I&#8217;m usually the one on those calls. No account managers, no sales team.<\/span><\/p>\n<p><a href=\"mailto:mayank@engineerbabu.com\"><b>mayank@engineerbabu.com<\/b><\/a><\/p>\n<p><b>About the Author<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Mayank Pratap is Co-founder of EngineerBabu, a CMMI Level 5 product engineering company that has delivered 500+ software products across 20+ countries.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">EngineerBabu is a Google AI Accelerator Top 20 globally (2024) and a NASSCOM member, backed by Vijay Shekhar Sharma. Mayank leads product architecture, client engagements, and engineering strategy personally.<\/span><\/p>\n<h2><b>FAQ: Software Outsourcing Risks<\/b><\/h2>\n<ul>\n<li aria-level=\"1\">\n<h3><b>What are the biggest risks of outsourcing software development?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The highest-impact risks are misaligned discovery leading to wrong-problem builds, vendor lock-in through proprietary architecture or IP clauses, technical debt accumulation from low-quality code, and post-launch support gaps.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Communication breakdown due to timezone and process misalignment is the most common cause of project delays. Security and compliance failures are the most expensive to remediate.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>How do you protect intellectual property when outsourcing software?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Require a clear IP assignment clause in the Master Services Agreement that transfers all code, documentation, and derivative works to the client upon payment. Verify that subcontractors used by the vendor sign the same IP agreement. Ensure all repository access credentials are held by the client, not the vendor.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>Is offshore software development riskier than nearshore or onshore?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Location alone is not the primary risk driver. Process maturity, communication architecture, and engineering standards are better predictors of outcome than geography. A CMMI Level 5 certified offshore team with structured async processes will outperform an unstructured local agency in most engagements.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>How do I avoid scope creep in outsourced software projects?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Implement a formal change control process before the project starts. Every requirement change, regardless of size, generates a written impact assessment covering scope, timeline, and cost implications. This should be contractually required, not informally agreed to.<\/span><\/p>\n<ul>\n<li aria-level=\"1\">\n<h3><b>How long does a typical outsourced software project take?<\/b><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">MVP builds typically run 3 to 5 months for well-scoped projects. Full product platforms with integrations run 6 to 12 months. Any vendor quoting under 10 weeks for a non-trivial product is compressing your timeline in ways you&#8217;ll pay for later.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>50-70% of software outsourcing engagements that fail do so in the first 60 days. Not because the vendor couldn&#8217;t build. Because nobody stress-tested whether they were building the right thing, for the right architecture, with the right ownership terms. That number isn&#8217;t from a report. It&#8217;s from 14 years of building software and being brought [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":22765,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1271],"tags":[],"class_list":["post-22764","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software-development"],"_links":{"self":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/22764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/comments?post=22764"}],"version-history":[{"count":3,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/22764\/revisions"}],"predecessor-version":[{"id":22770,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/22764\/revisions\/22770"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media\/22765"}],"wp:attachment":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media?parent=22764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/categories?post=22764"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/tags?post=22764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}