Technical Support Engineer at Posthog
Posthog is hiring a Technical Support Engineer in Remote. The role details below come from the employer’s posting. You apply on the employer’s own site, and TechJobs360 never charges candidates.
On this page
1. Job details
Posthog
Technical Support Engineer
Remote
Not disclosed by employer
See the job description
On the employer’s site
2. Job description from Posthog
ABOUT POSTHOG
PostHog is your product’s context layer. It ingests and stores your analytics, errors, replays, and business data so you and your agents can query and act on it.
We launched out of Y Combinator's W20 cohort https://posthog.com/handbook/story. We've since shipped more than a dozen products, including:
– A suite of analytics and observability tools, including product analytics https://posthog.com/product-analytics, replay vision https://posthog.com/replay-vision, AI observability https://posthog.com/ai-observability, and error tracking https://posthog.com/error-tracking
– PostHog MCP https://posthog.com/mcp for users and their agents to query and act on their product and business data
– Data warehouse https://posthog.com/context-warehouse/managed-warehouse so users can query product and customer data together using custom SQL insights.
We are:
1. Product-led. More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
2. Default alive https://paulgraham.com/aord.html. Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
3. Well-funded. We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible https://posthog.com/deskhog.
THINGS WE CARE ABOUT
– Transparency: Everyone can read about our roadmap, how we pay (or even let go of) people, our strategy, and how we work, in our public company handbook https://posthog.com/handbook. Internally, we share revenue, notes and slides from board meetings, and fundraising plans, so everyone has the context they need to make good decisions.
– Autonomy: We don’t tell anyone what to do. Everyone chooses what to work on next based on what's going to have the biggest impact on our customers, and what they find interesting and motivating to work on. Engineers lead product teams https://posthog.com/handbook/wide-company and make product decisions https://posthog.com/handbook/which-products. Teams are flexible and easy to change when needed.
– Shipping fast: Why not now? https://posthog.com/handbook/values#why-not-now We want to build a lot of products; we can't do that shipping at a normal pace. We've built the company around small teams – autonomous, highly-efficient groups of cracked engineers https://posthog.com/founders/cracked-manifesto who can outship much larger companies because they own their products end-to-end.
– Time for building: Nothing gets shipped in a meeting. We're a natively remote company. We default to async communication – PRs > Issues > Slack. Tuesdays and Thursdays are meeting-free days https://posthog.com/handbook/company/culture#were-on-the-makers-schedule, and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.
– Being weird: Weird means redesigning an already world-class website for the 5th time. It means shipping literally every product that relates to customer data. It means building an objectively unnecessary developer toy https://posthog.com/deskhog with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.
WHO WE’RE LOOKING FOR
We're looking for a Technical Support Engineer who loves helping customers and can't leave a problem alone until it's solved.
You're an engineer who happens to do support. You pick up new things fast and you're comfortable with a problem nobody has seen before. That matters more to us than your previous job title, and people on our team came to support from various backgrounds.
You care about how a customer feels when they leave the conversation, not only whether the ticket closed. You take feedback well, say when you don't know something yet, and learn from anyone on the team.
WHAT YOU’LL BE DOING
– Helping customers across all of PostHog's products, in the app and in shared Slack channels with our bigger customers
– Owning your tickets from beginning to end, and keeping customers updated along the way
– Shipping fixes to the PostHog codebase and docs when you find something broken or unclear
– Becoming the support expert for a product area: owning its queue, working closely with the engineering team behind it, and spotting the patterns that turn into fixes
– Improving how we do support, including the tooling and workflows we build on PostHog itself
– Passing customer pain points and feature requests to engineering teams with enough context for them to prioritize
WHAT YOU WON’T BE DOING
You won't be routing tickets, or forwarding hard questions to engineering because they look hard.
You won't say "that's not my job". If you can't solve something, you find who can and make the connection.
You also won't be pasting AI answers back to customers. We use AI every day, but we expect you to test things out for yourself and write a reply to the customer that's better than the one it would write. Here's more on how we think about that https://www.linkedin.com/pulse/stop-adding-ai-between-you-your-customers-posthog-gkxle/.
HOW WE WORK
You'll be the face of PostHog for many of our customers. Most of them are engineers, so they want help from someone who understands the technical detail and writes back like a person.
We want support to be part of why people choose PostHog.
3. Skills that usually matter in software engineering roles
General guidance from TechJobs360, not part of Posthog’s posting. The job description above is what counts for this role.
| Area | What to be comfortable with |
|---|---|
| Languages | Java, Python, Go, C# or C++ |
| Frameworks & tools | A web framework, SQL and NoSQL databases, Git, cloud basics |
| Computer science basics | Data structures, algorithms, complexity |
| Ways of working | Version control, code review, testing, reading other people's code |
4. How to prepare for a Technical Support Engineer interview
Interview formats differ by company and team, so confirm the rounds with the recruiter. Most hiring loops for roles like this cover:
A recruiter call or an online test. Read the job description twice and be ready to explain how your experience matches it.
Often coding problems on arrays, strings, trees, graphs or dynamic programming, solved while you explain your thinking.
Often design and trade-off questions sized to the role: an API, a component, or a small system.
Answer with the STAR method (Situation, Task, Action, Result). Prepare two or three real stories: a hard problem you solved, a disagreement you handled, and something you learned quickly.
5. Take-home pay example (FY 2026–27, new tax regime)
An example for two common package sizes, not this job’s salary. Under the new tax regime (Section 115BAC) salaried employees get a standard deduction of ₹75,000.
| Component | Example: ₹12 LPA | Example: ₹24 LPA |
|---|---|---|
| Basic salary (40% of CTC) | ₹40,000 / mo | ₹80,000 / mo |
| Employee EPF (12% of basic) | -₹4,800 / mo | -₹9,600 / mo |
| Income tax (TDS) | -₹6,933 / mo | -₹32,450 / mo |
| Professional tax | -₹200 / mo | -₹200 / mo |
| Approx. in-hand | ₹81,344 / mo | ₹1,44,304 / mo |
Work out the take-home pay for your own offer, in either tax regime.
Open the salary calculator →6. Questions and how to apply
How do I apply?
Use the apply button below. It opens Posthog’s own application page.
Does TechJobs360 recruit for this job or charge a fee?
No. We list openings from employers’ career sites. Posthog runs the hiring, and nobody should ask you to pay to apply.
Is this job still open?
We check listings against the employer’s page every day and take down jobs that have closed.
Should I apply if I don’t match every requirement?
Usually yes, if you meet most of the core requirements and can show you learn quickly. A referral from someone on the team can help your resume get read.
Apply for Technical Support Engineer at Posthog
Apply on the employer’s site →