Balance 💼/🏡

Template Version: 2.1 | Last Updated: 2025-06-01

The following are my work-life balance preferences. They may evolve over time, so check back occasionally.

⚖️ TL;DR: Message me anytime, anywhere—no need to use delayed sending. I'll respond appropriately. Please minimize meetings. My response times vary, especially during crunch periods. I have an unconventional working style, often sending messages and emails at all hours, but I'm adaptable to anyone's communication style. I value directness, candor, and honesty over diplomacy.

Communication

My preferred communication channels, in order:

1. 💬 Chat
2. 📩 Email
3. 📅 Meeting

💬 Chat

• Message anytime—during meetings, PTO, or outside typical work hours is completely fine.

• Avoid using delayed sending services; I prefer quick pings and will manage responses appropriately.

  • However, I'll use delayed sending for non-work-related topics.

• I don't expect immediate replies unless it's critical.

  • Generally, I reply within a week, though this might extend to two weeks or a month if I'm in deep-focus mode.
  • I keep messages marked unread when they contain action items.

• Please avoid messages that only say "hello".

📩 Email

• I typically don't check emails outside of working hours, but do send emails anytime.
• I greatly appreciate a clear TL;DR at the top.

Core hours represent my standard availability window when you can reliably expect me to be online and responsive. These are the designated times during which:

• I’m consistently available for meetings
• I maintain regular communication and respond promptly
• My work schedule is most predictable

Please note: While I may occasionally be available outside of core hours, availability during these times is less guaranteed and subject to variability. For time-sensitive matters or scheduled meetings, I recommend booking within core hours to ensure reliable connectivity.

My core working hours (PST):

Preferences:

• Schedule at least a 5-minute break between meetings.
• Provide at least 12 hours’ notice before scheduling meetings.
• Always include permission to modify the event.
• I prefer walking meetings whenever possible.
• I use metadata for the following:
  • #moveable for meetings easily rescheduled (e.g., 1:1s).
  • 🔄 for recurring meetings

Working

• I typically...

  • complete code reviews within 24 hours.
  • review tickets within 24 hours.
    • respond to tickets within 8-24 hours.

• Plain, direct communication suits me best. I tend to speak very straightforwardly, which can occasionally come across bluntly—this isn't intentional, just my natural style. If subtlety or context cues are unclear, be direct. It helps everyone stay aligned.

  • Honesty over diplomacy—clarity and truthfulness lead to better outcomes.

• I prefer detailed and accurate world models. Expect me to ask probing questions about technical topics to ensure full understanding.

• I occasionally have irregular working hours. If my schedule or timing is problematic, please let me know—I’m flexible.

Interviewing

• I complete initial interview ratings within 24 hours and provide full feedback within 48 hours.

• I use "TC" (The Candidate) to anonymize feedback and minimize bias.

• My rating system uses the following markers:

  • + Positive trait
  • - Negative trait
  • -+ Mixed (positive and negative)
  • * Additional comment or context

• Example rating could be:

+ Correctly identified the optimal data structure [XOR Linked List]
+ Choose optimal algorithm [Bogosort],
  + weighted pros [Ω(1) runtime] and cons [O(∞)] of algorithm

- Got the average Θ(n × n!) runtime incorrect,
	+ but TC got the memory complexity correct O(1),
	+ and correctly explained why constant space: sorts in-place

-+ Got 75% of the unit tests cases correct, 
   which is average for this problem

* TC had internet issues for 5 minutes in the beginning,
  granted them 5 extra minutes for problem (with TC's permisson)

Interview Feedback Template:

# ---------------------------------------------- Setup
You can find more info about this template at 
starikov.co/balance#interviewing

<SCRIPT>
Hi, my name is [Illya]! Is this [TC]? Excellent! 
Today we'll be conducting a 
[INTERVIEW TYPE: programming, leadership, system design] interview.

- Confirm programming language.
- Are you comfortable? Water, break?
- Any questions?

Let's begin!
</SCRIPT>

# ---------------------------------------------- Question Asked
<Fizz-buzz>
- Q1: Fizz
- Q2: Buzz

# ---------------------------------------------- Interview Notes
// Observations (noun)
- Communication:
  - Receptiveness:
  - Clarification:
  - Planning:
- Approach:
  - Pivot:
  - Openness:
- Technical:
  - Code quality:
  - Debugging:
- Other:


// Notes (verb)
- 00:00 Interview start:
-

// Recurring Questions
- O(time):
- O(space):
- Test Cases:
- Edge Cases:

# ---------------------------------------------- Candidate Code
// Candidate's code below verbatim


# ---------------------------------------------- Teardown
<SCRIPT>
We're approaching the end of our time.
We have a few minutes left,
I'd be happy to answer any questions you may have.

Questions asked:
- Q:
- Q:

Thank you for your time today.
Your recruiter will follow up with you with next steps.
Have a great day, [TC]!
</SCRIPT>

# ---------------------------------------------- Comments
// The following are all comments post interview
- 

Changelog

• 2.0 | STAR🌻KOV implementation
  • 2.1 | Proofreading via ChatGPT GPT-4.5. Added interview template.
• 1.0 | Google implemenation