promenade - Sr. Software Engineer, Internal Apps

• Talk to people, then build things. You'll work directly with business and engineering teams to understand what's slowing them down. You'll figure out whether the fix is traditional software, an AI integration, or some combination. Then you'll turn vague requirements into something you can actually build. • Own the whole thing. Prototype it, harden it, deploy it, monitor it. These are internal tools, so you move fast, but they still need to work reliably. • Build fast with AI-assisted development. We use tools like Claude Code to move quickly. You should be comfortable using them to scaffold, iterate, and ship. But you also need to read what they produce, catch what they get wrong, and know when to write it yourself. These tools make good engineers faster. They don't replace knowing how software works. • Use AI where it actually helps. Integrate LLM APIs (OpenAI, Anthropic, Gemini, etc.) when language understanding or probabilistic reasoning genuinely improves the outcome. Design prompt strategies and evaluation methods when you do. Skip the model call when a conditional statement would work better. Keep an eye on cost, latency, and reliability. • Write code other people can maintain. Build clean systems. Establish practical patterns for secure AI usage. Contribute to standards around observability, safety, and data handling. • Work with data. Write SQL against MySQL/ Snowflake, build internal dashboards, and turn business questions into lightweight data tools.