• Design, build, test, and deploy IOT features and services using the .NET stack. • Assist in the development of robust Integration and End-to-End (E2E) tests to ensure system reliability in complex automated environments. • Implement solutions that scale in high-transaction, real-time warehouse environments. • Write clean, maintainable, and well-documented code following established standards. • Participate in peer code reviews, providing constructive feedback and incorporating feedback from others. • Assist in writing technical designs and implementation plans for assigned features. • Troubleshoot, analyze, and resolve application and system issues, including production incidents. • Support, maintain, and document existing IOT functionality. • Follow secure programming and web application security best practices. • Work closely with Product Owners and senior engineers to understand requirements, break down work, and estimate effort. • Collaborate with other engineering teams (WES, TMS, SAP, 3PL integrations) to ensure smooth system interactions. • Provide regular updates on progress, risks, and blockers to the team. • Maintain high standards of software quality through testing, refactoring, and adherence to best practices. • Identify opportunities to improve system performance, reliability, and maintainability. • Learn and apply new tools, frameworks, and patterns as guided by senior team members.

• Code, test, debug, implement, and document low to moderately complex programs • Create appropriate documentation in work assignments such as program code and technical documentation • Design systems and programs to meet business needs • Prepare detailed specifications from which programs are developed and coded • Ensure programs meet standards and technical specifications; performs technical analysis and component delivery • Gather information from existing systems, analyzes program and time requirements • Assist project manager in preparing time estimates and justification for assigned tasks • Develop test plans to verify logic of new or modified programs • Conduct quality assurance activities such as peer reviews

• transformar datos en reportes y dashboards útiles en Power BI • análisis, visualización, automatización básica y soporte a decisiones • Crear y mantener reportes en Power BI • Conectar fuentes de datos • Limpiar y transformar datos • Crear medidas y métricas básicas • Validar información con negocio • Dar soporte en cambios menores de reportes • Documentar dashboards y procesos

• PostHog has a forum, a Discord, a subreddit, a newsletter, and a lot of content — but conversations between users are sparser than they should be. Forum traffic has declined year-over-year. Reddit engagement is low. You'll own growing the volume and quality of conversations across all three surfaces: • Forum — slow, indexed depth. Concrete opening project: clean up out-of-date questions, clarify what the forum is for, start actively triaging and seeding. The decline isn't because users don't want to talk; it's because no one is doing the maintenance and hosting work. • Discord — raw, real-time, not indexed. Currently in test mode; you take it over fully and aim for the 20% DAU default-alive benchmark. We haven't proven Discord will compound for us long-term, but the size of comparable companies' servers says it should. If it doesn't, you're the person who calls it. • Reddit — public, discoverable. Narrow scope: recruit passionate community members to help run the subreddit, and personally lead high-leverage moments like AMAs. Not daily triage. • You'll also seed conversations on hub topics like growth engineering, design for product engineers, and fundraising for founders, and figure out the strategic question hiding underneath: when does each surface get used, for what? • We have founders who are fans, OSS contributors, event organizers, forum power users, builder group leaders, and customers doing interesting work. Right now nobody keeps a list, the relationships are personality-dependent, and we mention great customers once in a case study and then never again. You'll build the system — identify, spotlight, enable, reward. • One specific track within this: a consistent flow of people engaging in the forum, open source contributions, users sharing what they're building in chat and livestreams. Make it easy to start in all these online spaces, recognize existing contributors meaningfully, and develop a reward system that goes beyond a merged PR. You'll also deal with potential negative incidents or breaking of guidelines that may invariably happen. • You'll also work closely with the IRL events team on the bridge between offline and online (builder groups becoming online regulars, online conversations seeding meetups), organizing online "events," and pick up sidequests such as a new community surface all together (would building our own social network be the best way to achieve these goals?)