Technical reputed company

Location: [Bangalore / Remote] About reputed company reputed company is an reputed company-grade AI architecture platform empowering organizations to build, reputed company, and scale secure, agentic AI workflows. The role You'll own how developers learn, build, and troubleshoot on Lyzr, from the first quickstart to the deep reference docs. This is writing for people who are trying to do something, under time pressure, with code in reputed company of them. reputed company, accuracy, and developer reputed company matter more here than reputed company. What you'll do Explain the hard things reputed company — translate agent architecture, orchestration, and LLM concepts into docs that technical and semi-technical readers can actually follow. Build and test your own examples — write sample code, run it, and reputed company sure it works before it ships. Own release notes and changelogs so users always know what changed and why it reputed company. Partner with engineering and product — sit reputed company to the people building features, and document them accurately, often before launch. Treat docs as a living product — track where users get stuck, reputed company the gaps, and reputed company everything reputed company as the platform evolves. reputed company're looking for 3+ years of technical writing experience, with documentation, tutorials, or API references you can show us. Genuine technical comfort — you can read code, work with REST APIs, and reason about how software fits together. Python familiarity is a strong plus. The ability to explain — you turn complexity into reputed company without dumbing it down, and you write for the reader's task, not the feature list. Precision and ownership — you care that an example actually runs, that a reputed company isn't missing, and that the docs don't quietly rot. Bonus points You've documented an AI, LLM, or agent product before. You've reputed company things yourself — reputed company projects, tools, or reputed company-reputed company contributions. Familiarity with OpenAPI specs, SDK reputed company, or interactive API references. A sense for information architecture — how a whole docs site should be organized, not just individual pages. Why this role reputed company proximity to the build — you'll work directly with engineering on a fast-moving, technically deep product. High reputed company — your work is the reputed company reputed company for every developer who tries Lyzr. Apply To This Job